Multi step modal for Record Producer varables

[NazeerM]

A Record Producer contains approximately 30 variables. A Service Portal widget must be added to the Record Producer form that displays a clickable link or button. When the user selects this link/button, a modal window should open.

The modal will display specific variables from the same Record Producer, organized into a four-step wizard. Each step of the wizard should show only a selected subset of the variables. For example, Step 1 may contain 2–3 variables, while the remaining variables will be distributed across Steps 2, 3, and 4. The assignment of variables to each step will be handled programmatically within the widget.

The modal must provide navigation controls such as Next, Previous, and Cancel/Close. Moving between steps should dynamically update the modal content to show the variables associated with that step. Any values entered in the modal should be reflected in the corresponding variables on the Record Producer form, ensuring data consistency.

The widget should retrieve and bind the Record Producer variables so that the modal fields interact directly with the same variables present on the form.

Is this feasible? If yes, How can we achieve this?

[Ankur Bawiskar]

@NazeerM 

this is heavy customization and I won't recommend this as it will lead to technical debt going forward considering upgrades etc

Please stick to OOTB methods available on catalog items.

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[John Gilmore]

Instead of using a modal popup I would recommend simply breaking your steps into sections within the record producer.

You could provide a button/checkbox on the producer that linked to a parameter that could be leveraged to offer the user a guided experience. With proper use of parameters and ui policies you could create almost the same experience leveraging OOTB functionality rather than requiring a whole bunch of customization that would be a failure point during upgrades. It would still be a lot of configuration but could be done. I recommend using a strong naming convention to keep it as clean as possible.

Depending on the specifics of the use case you may be better off splitting it and offering one record producer without this experience and another that is built to provide exactly the experience you are looking for. With the same consideration you may want to look at leveraging a playbook experience for this. Look at how ServiceNow has leveraged playbooks for multi-page forms in PSDS for an example.