Evaluating the Impact of Adding a New Option to the "Category" Field in Demands

[romenr]

A client has requested to add another choice to the "Category" field on the Demands module. Currently, the available options are "Strategic" and "Operational."

Before proceeding, I want to ensure that adding a new option will not cause any downstream issues. Specifically, I am concerned about the potential impact on any existing workflows, reporting structures, or integrations that rely on this field.

Could anyone with experience or insight into the system’s architecture share whether this change could create any problems or if it’s safe to add another category option?

[Dr Atul G- LNG]

Hi @romenr 

Adding a new choice isn’t an issue, unless the existing choice has already been used in a flow or OOTB reports. In your case, you need to check if the existing types are being used in any flow. If they are, you’ll need to update the flow, reports, or integrations to take advantage of the new value. This will be a significant amount of work and will require thorough testing as well. If there is no flow or logic tied to the existing choice, then I think you can simply add a new choice and use it.