There are a few steps in this process. For Flow support, ServiceNow transitioned to a process that uses Model instead of Type as the driver for the various Flows. The Flows are built with triggers that look for the Model field so they will not run if this feature isn't enabled. To enable it, you need to set a couple of new system properties:
com.snc.change_management.change_model.hide - set to false
com.snc.change_management.change_model.type_compatibility set to false
Once this is done, when you create a new Change Request you will see a different interceptor that looks like the below:
By selecting one of the above, the Model field on the Change Request gets set, which then allows the trigger for the Flow(s) to kick in.
There are other potential considerations though. You may need to update the conditions on your workflows to exclude changes where the Model is set. The out of the box workflow has had this condition added, but if you've customized it, you will need to do this yourself - otherwise both the Flow and Workflow will execute. You should also review UI Policies, business rules, scripts, etc. for any logic that was based on Type since you may need to update it. Type did not go away though, so it's possible that you won't have to change that logic.
Good luck!
Please mark as helpful/correct if this answered your question.
There are a few steps in this process. For Flow support, ServiceNow transitioned to a process that uses Model instead of Type as the driver for the various Flows. The Flows are built with triggers that look for the Model field so they will not run if this feature isn't enabled. To enable it, you need to set a couple of new system properties:
com.snc.change_management.change_model.hide - set to false
com.snc.change_management.change_model.type_compatibility set to false
Once this is done, when you create a new Change Request you will see a different interceptor that looks like the below:
By selecting one of the above, the Model field on the Change Request gets set, which then allows the trigger for the Flow(s) to kick in.
There are other potential considerations though. You may need to update the conditions on your workflows to exclude changes where the Model is set. The out of the box workflow has had this condition added, but if you've customized it, you will need to do this yourself - otherwise both the Flow and Workflow will execute. You should also review UI Policies, business rules, scripts, etc. for any logic that was based on Type since you may need to update it. Type did not go away though, so it's possible that you won't have to change that logic.
Good luck!
Please mark as helpful/correct if this answered your question.
