Are there risks to adding custom completion codes?

We have been asked to add a custom completion code. Are there risks or concerns we should be aware of when adding custom completion codes? I know there are reference to them in business rules, but I have not been able to find evidence to indicate that adding a custom completion code might paint ourselves into a corner without realizing, such as for example, that we should stick with the existing codes in the product and not try to deviate. 

The request was to add a code for "Duplicate" when a request is found to be a duplicate of another request (same requestor, issue, client, etc.). 

  • 0

    My unofficial 2 cents,

    • Because of localization always keep good naming convention and follow the recommended Logic/automation guidelines for custom values.
    • Keep a configuration log of every change/new field and any other modification as at time of upgrade there is a step asking to address those manually.
    • Keep in mind for future onboarding of the modules that you are not being used currently (PPM, DND,CMS, SACM, FinOps etc) that may or may not have a link to this change.
    • In particular bots(aviator, Virtual agent) may need ingestion of these values for the training (logic, prompt etc..).
    • If you feel this is something lacking in product, I suggest an  ER(idea exchange unfortunately)
  • 0 in reply to 

    Thank you, Misaq. I'm interested what you and other people use for a completion code in the scenario where the request is a duplicate of an existing request open for the requestor. In the previous tool we had a completion code of 'duplicate', I do not recall whether it was a custom addition or OOTB.

  • Verified Answer

    +1  

    There shouldn't be a risk. There are indeed a few business rules mentioning specific completion code values, but those rules would have conditions for explicit checks or setting the field to a specific value.

  • 0 in reply to   

    There are some transitions (automatic and manual) that also consider this field value. Depending on the path you want to take the SR to, they should also be considered.