Service Operations Workspace - Declarative Actions troubleshooting guideSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Declarative Actions are much more flexible, powerful, and can be used in many additional locations in Next Experience-based interfaces along with UI Actions.For example when an agent loads an incident record in workspace and would like to resolve the incident then there is a declarative action in place to resolve the incident record.Below is the flow for declarative action configuration: Please find references for the tables mentioned in above flow. Frequent Issues: 1.Declarative actions not visible.2.Change declarative actions order.3.Declarative action is visible in overflow or group but it should be independent.4.Declarative action not processed after clicking on button5.Incorrect view getting rendered in modal 1.Declarative actions not visible. Verify the Declarative Action Inspect the sys_id. Check Activation and View Settings Ensure the declarative action is active.Confirm that view and table fields are correctly selected.Steps to validate the view: i. Navigate to the Experiences table and search for the workspace name.ii. Go to UX Page Properties related list and look for the property named “view”.iii. Verify that the value field matches the correct view name. Validate Form Action Layout Item Confirm the linked declarative action is active = true.Check that order and table fields have appropriate values.If the item type is Group, ensure the group field in the Form Action Layout Item table is correct.Check if overflow is enabled. If so, the declarative action will appear under “…”. Form Action Layout Link Ensure the Form Action Layout Item is linked to a valid Form Action Layout Advanced Conditions Verify that Script Condition and Scripted Client Condition are enabled in the advanced view of the declarative action.Verify the "required role" field which controls the visibility of ui action. 2.Change declarative actions order. A. The actions that occur outside of the group and overflow can only be arranged in a sequence. B. However, actions within the group can only be organized among the items inside the group. C. For overflow, the actions cannot be arranged in any order. D. Change the order field in declarative action/ui action which will reflect the changes. 3.Declarative action is visible in overflow or group but it should be independent. Either of below ways can convert an declarative action to independent button instead of group action. A. Create an new form action layout item with type =action and deactivate the existing layout item that has type=group. B. Edit the existing form action layout item and change the action field from group to action. 4.Declarative action not processed after clicking on button Declarative action with uxf type is failing : Ensure that for every UXF client action type, a corresponding client action is created.Verify that the route mentioned in the client action is active. Ex: "route": "create_case", "fields": { "table": "{{table}}", "sysId": "{{sysId}}"Confirm that there is an event mapping for the client action to be triggered.If the event is not fired, verify that the target event is linked to the UX add-on event mapping.If the target event is not fired, check if it is linked to the parent page or macro component. Declarative Action with Server Type Script Validation Add logs to check if the script mentioned in the server script is failing.Verify if the following are enabled in the advanced view of the declarative action: Requires WriteRequires ReadRequires CreateRequires Delete Access Evaluation Ensure the access permissions are correctly configured as required. 5.Incorrect view getting rendered in modal Identify Implementation Type. Check if the affected declarative action is implemented as: Client ScriptUXF Client Action If UXF Client Action then check below details: Route/View Validation. Confirm that the route or view mentioned in the client action is active. Field Configuration. Ensure that the fields are explicitly mentioned in the same client action responsible for displaying them. If Client Script then check below details: Modal Definition Verify the modal defined in the client script. Modal Presence Check if the modal exists in the UI pages.