Use Request Change Category for all RAID (Risk, Action, Issues, and Decisions).

[Leviathan]

Will using Category dropdown from Request Change in other RAID (Risk, Action, Issue, and Decision) items create referential integrity problems or problems with RIDAC?

Background: PPM users are requesting an enhancement.  They desire adding the Category (Resource, Scope, Schedule, and Cost) to all other RAID (Risk, Action, Issue, and Decision) items.  This is also referred to as RIDAC (Risk, Action, Issue, and Decision) in ServiceNow.

The RAID items also affect Demand management so changes to table enhancement beyond OOB functionality is approached with caution.

[SasankaV]

Hi @Leviathan ,

I think I worked on a similar use case in my experience with Work4flow. Give the below steps a try:

1. Log in to your ServiceNow instance and navigate to the configuration for RAID items.
2. Identify and review the Category dropdown in the Request Change table.
3. Create a new Category field in the RAID items tables with the same options (Resource, Scope, Schedule, Cost).
4. Map the new Category field to each RAID item without altering the original Request Change table.
5. Test the new Category field in RAID items to ensure functionality and integrity.
6. Verify that Demand management processes are not affected by these changes.

Let me know if stuck, I'll be happy to assist.

[mmeazza]

Hello @SasankaV,
I have a similar need of a category/subcategory field on all RIDAC tables.

Could please you provide more details about point nr.4?

Thank you in advance!