Change Management workflow editor vs flow designer

LS91
Tera Contributor

On our instance, we now also want to start using change management, but we are facing some challenges.

It appears that tasks created from the "Change request - Normal change tasks" workflow are being created from both the flow designer and workflow editor.

 

LS91_0-1679563605017.png

 

I have tried already to change the below property, but this doesn't make any difference:

com.snc.change_management.change_model.type_compatibility > false

 

When I try the same thing on a new developer instance, only the flow from the flow designer is triggered. Is there a system property that I am overlooking? We have never used change management before, and our instance is originally from the Tokyo release.

1 REPLY 1

Aivaras Go
Tera Contributor

We are having same issue in Utah Patch 8. Both workflows and flows are triggering, so we are receiving duplicated change tasks and approvals.

We want to use change models, so ideally it's only flows are fired.

Our current setup:
com.snc.change_management.change_model.hide  = false
com.snc.change_management.change_model.manage_workflow = true
com.snc.change_management.change_model.type_compatibility = false

Out of frustration I tried different variations of these properties, however I noticed just how the interceptor of new change looks like and whether it routes you to change_request via change models or legacy types.