List of best practices choice values to use on tables that extend task due to task business rules

[corbettbrasing1]

Is there a list or documentation or something to say what the best practice is for state values and server logic that runs against them?   I know there are alot of business rules that run and update based on that field, so if we have a table that extends task I don't want logic chaining things without me knowing etc.

[Chuck Tomasi]

Hi Corbett,

The current technical best practices are documented at the link below. That being said, I'm not familiar with anything around state. If you want to ensure exclusivity to avoid conflict, use numbers (values) that aren't currently in use. For example, 101, 102, 103, 104, etc. for your process. Be sure to review the dictionary attribute   close_states.

ServiceNow Wiki: Technical Best Practices

[corbettbrasing1]

Chuck I am referring to things like the script include: taskStateUtils() which runs via business rules on ALL tables that extend task.

[Chuck Tomasi]

Hi Corbett,

Aside from the product documentation page, there's nothing about best practices that I'm aware of.

Like anything else on the system, going with OOB values (minimal customization) is always recommended,

Did you have any specific concerns or questions?

[YRK]

Hi Tomasi,

is it a best practice to create a choice with 'sys_choice' as table in ServiceNow?

Thanks,

Rama