Some Change Requests are creating duplicate approvals

Susmitha1625
Tera Guru

Hello Everyone,

We have noticed a few change requests are creating duplicate approvals. Once the change is moved to the Scheduled state after CAB approval, again a 2nd set of Approvals is created for the CAB team. And this is only happening for a few requests. I've checked the workflow but it's OOB and nothing strange was noticed in the workflow. Has anyone faced this issue or does anyone have any idea about this? Please help me

1 ACCEPTED SOLUTION

Susmitha1625
Tera Guru

Hi @Soufyane EL OMA 

Here is our solution: When a user creates a change request from the Service Operations Workspace, we will have a 'change type' field filled in from the SOW. So this triggers both the Flow and workflow for that particular change request. 

Here are some potential solutions to consider:

  1. Replace the Model Parameter: Change the model parameter to the change type.  this will prevent the flow from triggering.
  2. Remove the "Create Change" Option: If the "Create Change" feature in the SOW is not utilized by the client, consider removing this option entirely from the SOW.
  3. Change the Landing Page: If the SOW is not being used by the client, replace it with an alternative landing page.

We have implemented the third option.

Hope this helps.

View solution in original post

4 REPLIES 4

Mark Manders
Mega Patron

Do you have anything else configured for these changes? Like another flow, other rules, or something like that?


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Susmitha1625
Tera Guru

@Mark Manders No, everything is OOB

Soufyane EL OMA
Tera Contributor

Did you find any solution because we're facing the exact same issue ?

No customization has been done, only OOB

Susmitha1625
Tera Guru

Hi @Soufyane EL OMA 

Here is our solution: When a user creates a change request from the Service Operations Workspace, we will have a 'change type' field filled in from the SOW. So this triggers both the Flow and workflow for that particular change request. 

Here are some potential solutions to consider:

  1. Replace the Model Parameter: Change the model parameter to the change type.  this will prevent the flow from triggering.
  2. Remove the "Create Change" Option: If the "Create Change" feature in the SOW is not utilized by the client, consider removing this option entirely from the SOW.
  3. Change the Landing Page: If the SOW is not being used by the client, replace it with an alternative landing page.

We have implemented the third option.

Hope this helps.