What is wrong with my Citeria
Hi,
Attached above is a screenshot of the criteria I’ve set to route the workflow into a different approver. But it doesn’t seem to work. When I click the next status, system will route it to my set approver but the approver from another criteria is also there.
You may check the setting of “Status Criteria Matching Type” on the workflow configuration. The status may not be getting picked due to that configuration and condition of the change. I guess this since you mentioned that approver from one status criteria was picked.
Most likely, as Patrick suggested, multiple status criteria are being matched. Just to provide a little explanation on this – lets say I have two different status criteria added to the review status of my workflow (each status criteria has a different approver populated):
1- Production Requests (Approver – John Snow)
2- Production Request that start with “SI-CONFIG” (Approver – Ned Stark)
When a Production Request that starts with “SI-CONFIG” enters this status – both Ned AND John will be added as approvers. This is because it is a Production Request (criteria 1 matched) AND it is a Production Request that starts with “SI-CONFIG” (criteria 2 is matched).
When a Production Request that does not start with SI-CONFIG enters this status – only John will be added as an approver (only Criteria 1 is matched)
If you want an either/or type of situation – you would need to set each criteria so they could not both be matched.
I.E.
Production Requests that start with SI-CONFIG (Approver – Ned Stark)
Production Requests that do not start with SI-CONFIG (Approver – John Snow)
Thank you for your replies. Below is a screenshot of my criteria matching type:
Did I set it correctly?
Hi,
As explained here the Some matching criteria should be correct in your case.
Also your expectation should vbe correct looking the criteria. Could you please add an example of Change Number that you are using that should match the “start with” condition?
I had bad issues with Start With in a Criteria because sometimes this condition was always false even though it was satisfied. There are a couple of bugs in OTN about that.
Try to use another Criteria for testing (for example: equal to ‘exactnumber’) to check that you are not affected by this issue.
