Unable to display custom declarative action in Service operations workspace

[SujaniC]

Hi everyone,

I’m trying to add a custom Related List Declarative Action in Service Operations Workspace for the Change Request table.

Requirement:
I have a Parent → Child Change Request related list (using the parent reference field). I want to add an Add button that opens a Multi Record Associator (MRA) so users can select Change Requests and set their parent field to the current Change Request.

What I’ve done:

* Created a new Action Payload Definition by copying the OOTB Change Request MRA.
* Updated the payload to use:
* userGivenTable = change_request
* referenceFieldName = parent
* parentFieldName = parent
* type = o2m
* Created a new Action Assignment:
* Implemented as: UXF Client Action
* Client Action: Child Change Request MRA
* Table: change_request
* Copied both OOTB UX Add-on Event Mappings and updated them to reference my new Action Assignment.
* Verified the target event is [Record Page] Open modal.
* Cleared cache and refreshed the workspace.

Issue:
The Add button never appears on the related list in Service Operations Workspace.

Question:
Is there any additional configuration required for custom Related List Declarative Actions in SOW (such as Action Models, Action Configurations, UI Builder configuration, or registration with the related list)? Has anyone implemented a custom MRA-based related list action for Change Request successfully?

Any guidance would be appreciated.

[Vikram Reddy]

Hi @SujaniC,

Before you dig any deeper into UI Builder, pull up your Action Assignment record directly (sys_declarative_action_assignment.LIST, filtered on table=change_request) and check two fields on it: Action Model and the Source element ID on both Event Mapping records. Nine times out of ten when a button silently never renders (as opposed to rendering but failing on click), it's one of those two, not the payload.

A few things I'd check in order:

• Action Model on the Action Assignment must be Related List, not just any generic action. This gets set correctly for you when the record is created through Workspace Experience > Actions & Components > Related List Actions. If yours was created by cloning the OOB record directly rather than through that module, double check this field explicitly, it's easy for it to carry over wrong.
• Source element ID on the sys_ux_addon_event_mapping records should be list_related. Older OOB actions (and some OOB configs you may have copied from) still reference record_page_tabs_1, which was the element id before the related list component was refactored. If both of your copied mappings still point at the old id, the framework has nothing to attach the button to on your record page and it just never shows up, no error, nothing in the log.
• Confirm there's no Action Exclusion record against change_request hiding your assignment, and that the Condition script (if any) actually evaluates true for a parent change_request record, not just for the child.
• Since this is self-referencing (change_request pointing back at change_request), that part of your setup is actually fine, this pattern works the same way OOB does it for parent/child HR Cases, where parentFieldName and referencedFieldName are both set to "parent" against the same table.
• Fix the payload key while you're in there: the correct property is referencedFieldName, not referenceFieldName. You've got it spelled without the "d" in your payload, which won't stop the button rendering but it will break the association once a user actually picks records, so it'll bite you right after you fix the visibility problem.

If Action Model and the element id both check out and it's still not showing, clone the OOB Change Request MRA action assignment itself (not just its payload) and only swap the payload reference and label, that way you inherit the model, roles, and mapping wiring exactly instead of rebuilding it by hand.

Thank you,
Vikram Karety
Octigo Solutions INC

[Aditya_hublikar]

Hello @SujaniC ,

Earlier i have also worked on one use case its documentation is attach once refer this , it might help you :

You can refer this for declarative ui action :

https://www.servicenow.com/community/developer-blog/declarative-actions-in-servicenow-the-complete-g...

https://youtu.be/Nk7iHn38AD0?si=ljD75JAWpVf3r_QO

If this helps you then mark it as helpful and accept as solution.

Regards,

Aditya