We have a need to customize a modal in the HR Agent Workspace. ServiceNow has rebuilt the main case page for this workspace as a Standard Record Page (SRP), which leverages UX controllers and UX component presets to bind components to data and logic. Documentation on how this exactly works is sparse however.
We need to customize the Transfer Case modal. In the SRP, this modal is configured as follows:
- From the Case SRP page, the modals can be accessed in the Modal Container (Viewport):
- From there, the Transfer Case Default modal can be accessed:
- In this modal, there's an OK button component:
- This OK button fires two events when clicked:
- These events are bound to this OK button component via a UX component preset in the HR Case UX controller:
- The events themselves are defined in the UX events, like the first one (HR_UI_CTRL#TRANSFER_CASE):
My question is: how is this event tied to a data resource or client script that takes care of the actual execution of the action? As said, there's little to no documentation on how this works and I've been unable to figure this out.
Best regards,
Pascal Frencken
I have found out how this works. The UX controller comes with a UX macroponent definition also called HR Case, which contains all the data resources and client scripts used in the pages and subpages. The challenge is that there is no UX screen associated with this UX macroponent definition, so you cannot find these in UI Builder.
The workaround is to create a temporary UX screen and connect it to the macroponent:
This allows the UI controller to be accessed in UI Builder so the data resources and client scripts can be modified:
Apparently in the Yokohama release there will be capabilities to create controllers and presets from UI Builder. I'm not sure if that will also allow editing of existing controllers, guess we'll see.
Best regards,
Pascal Frencken
I have found out how this works. The UX controller comes with a UX macroponent definition also called HR Case, which contains all the data resources and client scripts used in the pages and subpages. The challenge is that there is no UX screen associated with this UX macroponent definition, so you cannot find these in UI Builder.
The workaround is to create a temporary UX screen and connect it to the macroponent:
This allows the UI controller to be accessed in UI Builder so the data resources and client scripts can be modified:
Apparently in the Yokohama release there will be capabilities to create controllers and presets from UI Builder. I'm not sure if that will also allow editing of existing controllers, guess we'll see.
Best regards,
Pascal Frencken
