Configuring Save & New is a small but high-impact UX decision. The four-step routine covers: review whether Save & New is appropriate for each object, customize the page layout to include or exclude it, configure field pre-population to reduce per-record typing, and (if needed) build a custom Quick Action for non-standard behavior. Each step is a different lever; together they shape how efficient bulk data entry is for users who actually do it.
- Review whether Save & New is appropriate per object
For each object, identify whether users actually enter records in bulk. Objects with high-volume single-session entry (Tasks, Activities, certain custom objects) benefit from Save & New. Objects with low-volume careful entry (Opportunities, customer-facing Cases) may not. Document the per-object decision: keep, remove, or customize Save & New. Get input from the user community; users who do the entry know what they need. Without their input, the decision is admin-side guesswork that may not match the actual workflow.
- Customize the page layout
For each object where Save & New should appear, confirm it is on the page layout assigned to the relevant profile or record type. For objects where it should not appear, remove it from the Standard Buttons section of the page layout. Save the layout and test with a target user. For Lightning record pages built in Lightning App Builder, the Record Form component includes Save & New by default; custom components may need configuration. Document the per-layout decision in the page layout runbook.
- Configure field pre-population for sticky values
For fields that should carry forward from the previous record (the same Account on the next Contact, the same Status on the next Case), configure them as Sticky in the user personal settings, or use URL parameters in the New button to pre-populate. For high-volume workflows, build a custom Save & New via Quick Action that pre-populates fields based on the source record. Test the pre-population with realistic data; some pre-populations make sense (Account) and others do not (record-specific names). Iterate based on user feedback.
- Build a custom Quick Action for non-standard behavior
If the workflow needs behavior beyond what the standard Save & New offers (open in a Service Console sub-tab, pre-populate from the parent record, run additional Apex on save), build a Quick Action. From Setup, Object Manager, the object, Buttons Links and Actions, New Action: pick the Create type, configure the field layout, add any pre-populated values. Place the custom action on the page layout in place of (or alongside) the standard Save & New. Document the custom action so future admins understand why the standard button was replaced.
- Save & New does not appear when the user creates the record from a related list. The user lands back on the parent record, not on a new blank form. Use a custom Quick Action if bulk creation from a related list is the workflow.
- Save & New respects validation rules. A failing validation blocks the save and keeps the user on the form, which is the same behavior as regular Save.
- Custom Lightning components may not include Save & New automatically. The standard Record Form component does; custom components need explicit configuration or rebuilt buttons.
- Sticky fields differ between Classic and Lightning. The Classic per-user sticky setting does not directly translate; Lightning uses platform-level pre-population behavior. Test in both UIs if both are used.
- Removing Save & New affects user productivity. Before hiding it, confirm with the actual users who do the entry; admins removing it for aesthetic reasons often surprise the team with productivity loss.