Hi,

Have you captured the approval debug logs? I would suggest you to capture one good set of logs where the approvals are getting attached and then capture the bad set of logs. It will help you in finding the exact flaw.

Cheers!!

Shantanu

Hello,

This is strange use case.

Please check following steps.

1) Did you go to CHG:ChangeAPDetailSignature form and checked if approval signature is generated after 9th support group is mapped for business approval phase?

2) Also, compare server side filter logs for 8 support group approval Vs 9 suport group approval use case.You should be able to figure out workflow filters on CHG:Infrastructure Change form which fires "Add - Sig" command to generate approval signatures for both use cases.

3) Do you see any records in "Application Pending" form for 9 support groups use case?

Regards,

Sachin

Sounds interesting. Would like to see the logs.

Would like to check the below as well.

Does the problem also happen if you add an individual approver as the 9th approver? Or does this happen only when the nith approver is a Group? Does the problem occur for any group or just for one particular group?

Looks like some sort of approval server error is occuring in this case. Load the logs if possible.

Hi,

These are only active link and filter logs. I would again suggest you to capture the approval debug logs as it will throw more light on the behavior.

make sure there are some individuals who are having infrastructure change approver role in that 9th group....

Hi,

Is this still an issue in your enviornment?

-Shantanu

In my perception there are two reasons to get the reported behavior.

Reason 1:  When you add 9th group that time Approval user member list might have exciding 255 character limits. If Approval server workflow finds member list more than 255 char then it will bypass the approval process. In this we can see exactly same behavior as like reported.

Reason2: When you add 9th group that might not have any valid approvers which will execute the Change Approval error rule. If this rule execute then change will bypass the approval process. In this we can see exactly same behavior as like reported. <This seems to be with less possibility based upon the provided screenshot>

If you could provide the approval debug log while moving the change request in both case then would certainly help to indentify the root cause of the behavior.

HTH,

Shiv