Normal Change Form used for two different teams

[Roshni1]

I have been able to create a new change team that will be use the IT CAB process and workbench.  

I am having trouble seperating the 2 types of changes 

The change is still going to IT CAB and not the new group. 

Need help with what or why Change Policy is not working. 

Thank you

[Omender Singh · Accepted solution]

Hi @Roshni1 

I faced the same issue recently after creating a new change team that uses the IT CAB workbench. Even though everything looked fine, changes were still routing to the default IT CAB group instead of the new one.

Here’s what I did to fix it:

---

✅ 1. The condition in the decision table wasn’t triggering

In my case, the rule was checking:

change_request.u_choice_1=acturis

But this field wasn’t filled when the Change Policy ran — so the rule didn’t match, and the default IT CAB rule kicked in.
Make sure your condition field is populated before the policy evaluates.

---

✅ 2. I missed the Policy Input

Go to Change Policy → Policy Inputs and check if the field you’re using in your condition (like u_choice_1) is added there.
Without it, the condition won’t work even if the field has a value.

---

✅ 3. All rules had Order = 0

That caused conflicts. I updated my custom rule’s Order to 1 so it runs after the general IT CAB rule. This ensured the right one was picked.

---

✅ 4. Approval definition was still pointing to old CAB

Double-check your custom Change Approval Definition. Mine was still linked to CAB Approval group.
I updated it to point to the new group and set the approver type to Group.

---

After doing all this, it started working as expected — changes now go to the correct team.

If this helps, please mark my response as ✅ Helpful or Correct — so it helps others too.
Thanks!

[Omender Singh · Accepted solution]

Hi @Roshni1 

I faced the same issue recently after creating a new change team that uses the IT CAB workbench. Even though everything looked fine, changes were still routing to the default IT CAB group instead of the new one.

Here’s what I did to fix it:

---

✅ 1. The condition in the decision table wasn’t triggering

In my case, the rule was checking:

change_request.u_choice_1=acturis

But this field wasn’t filled when the Change Policy ran — so the rule didn’t match, and the default IT CAB rule kicked in.
Make sure your condition field is populated before the policy evaluates.

---

✅ 2. I missed the Policy Input

Go to Change Policy → Policy Inputs and check if the field you’re using in your condition (like u_choice_1) is added there.
Without it, the condition won’t work even if the field has a value.

---

✅ 3. All rules had Order = 0

That caused conflicts. I updated my custom rule’s Order to 1 so it runs after the general IT CAB rule. This ensured the right one was picked.

---

✅ 4. Approval definition was still pointing to old CAB

Double-check your custom Change Approval Definition. Mine was still linked to CAB Approval group.
I updated it to point to the new group and set the approver type to Group.

---

After doing all this, it started working as expected — changes now go to the correct team.

If this helps, please mark my response as ✅ Helpful or Correct — so it helps others too.
Thanks!

[Roshni1 · Accepted solution]

Hi Omender 

Thank you so much I can't even explain have been fighting with this for weeks... 

Cheers

Roshni 

[Omender Singh]

your welcome @Roshni1 . All The Best !!!