How to reorder Add Risk / Add Issue options in the RIDAC More actions menu?

[Ryo14]

Hi everyone,

I would like to customize the order of the RIDAC creation options in Project Workspace.

As shown in the attached screenshot, the More actions drop-down menu currently displays the options in the following standard order:

- Add Risk

- Add Issue

- Add Decision

- Add Action

- Add Request Change

Specifically, I want to reorder the drop-down menu items highlighted in the red box in the attached screenshot.

I would like to change the order so that "Add Issue" appears before "Add Risk".

I have already checked the related RIDAC scripts and found the RidacChoiceOrderImpl Script Include. I tried changing the order array there, but the order in the Project Workspace UI did not change, even after clearing the cache.

Could anyone advise which component, configuration, Script Include, or UI Builder setting actually controls the order of these RIDAC creation menu items in Project Workspace?

Any guidance would be greatly appreciated.

Thanks in advance.

[Ankur Bawiskar · Accepted solution]

@Ryo14 

I found this script in the "Create RIDAC button" within that page which might be rendering, try to play with the JSON array of objects and see if the sequence changes

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

[Tanushree Maiti · Accepted solution]

Hi @Ryo14 

Check this post : Project Workspace 

• After you Click on the Create RIDAC split-button or the More Actions menu component in the center canvas layout.
• Review the right-hand Config panel. Look at the Items JSON array or property fields mapped to that dropdown component.
• If the items are hardcoded in a JSON payload, simply rearrange the code blocks to move the "Add Issue" entry block higher than "Add Risk".

[Ankur Bawiskar]

@Ryo14 

did you check the UI builder variant?

somewhere in this

https://instanceName.service-now.com/now/builder/ui/edit/experience/8f7db3b507223010188ca2324dd300be/576c9b4a07623010188ca2324dd3008c/176c534a07623010188ca2324dd300b0

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

[Ankur Bawiskar · Accepted solution]

@Ryo14 

I found this script in the "Create RIDAC button" within that page which might be rendering, try to play with the JSON array of objects and see if the sequence changes

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

[Ankur Bawiskar · Accepted solution]

@Ryo14 

Did you get a chance to check the solution I shared above?

[Ryo14]

Thank you for your suggestion.

I was able to achieve the desired behavior by customizing the UI Builder configuration.

What I changed:

1. Updated the split button label to use canCreateRIDACList[1].label so that Add Issue is displayed as the primary action.
2. Updated the dropdown items to exclude the Issue entry and keep the remaining RIDAC options in the dropdown.
3. Modified the update Param and Open Modal client script.

Original:

const table = (event.payload.item) ? event.payload.item.id : 'risk';2const actionType = (event.payload.item) ? event.payload.item.label : await helpers.translate('Add risk');

Updated:

const table = (event.payload.item) ? event.payload.item.id : 'issue';2const actionType = (event.payload.item) ? event.payload.item.label : await helpers.translate('Add Issue');

The key issue was that when the main split button was clicked, event.payload.item was undefined, causing the script to always fall back to 'risk'. After changing the default value to 'issue', the primary button correctly opens the Issue modal, while the dropdown options continue to open their respective RIDAC record types.

This solved the problem and the button now behaves as expected.

Thank you for pointing me in the right direction.