• State Verified Answer
  • Locked Locked
  • Replies 15 replies
  • Answers 2 answers
  • Subscribers 94 subscribers
  • Views 8887 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Attestation not working ver 8.0

Aadvik17
over 5 years ago

Hi Experts,

Attestation for Custom target system was working good, suddenly it's stopped working.

When I attest a single object from manager, No DecissionRequired is not  getting triggered and triggers the abort request.

Says no approver found. I have given recipient manager's approval and the manager is already assigned.

Any pointers.

Thanks,

Aad

Parents
  • 0 over 5 years ago

    The approval method DM is only able to find an approver if the attestation case is based on either the Person table or the PersonInDepartment table. To be specific AttestationCase.ObjectKeyBase has to point to objects from one of those two tables. In your case of a system entitlement attestation, this will never be the case.

    I doubt that your workflow has ever produced viable results for that kind of attestation.

    But let's assume it does, it might do because you had some people assigned to the application role Identity & Access Governance\Attestation\Chief approval team which is meant to avoid aborts due to an insufficient amount of approvers. This would explain your observation that you have nothing changed but it stopped working. Someone removed all members of that application role, and that's why your faulty approval policy is now unable to find any approvers.

     

     

Reply
  • 0 over 5 years ago

    The approval method DM is only able to find an approver if the attestation case is based on either the Person table or the PersonInDepartment table. To be specific AttestationCase.ObjectKeyBase has to point to objects from one of those two tables. In your case of a system entitlement attestation, this will never be the case.

    I doubt that your workflow has ever produced viable results for that kind of attestation.

    But let's assume it does, it might do because you had some people assigned to the application role Identity & Access Governance\Attestation\Chief approval team which is meant to avoid aborts due to an insufficient amount of approvers. This would explain your observation that you have nothing changed but it stopped working. Someone removed all members of that application role, and that's why your faulty approval policy is now unable to find any approvers.

     

     

Children
No Data