• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 96 subscribers
  • Views 255 views
  • Users 0 members are here
Options
Related

Assignments not being unsubscribed when attestation denied.

stig ingvar hylen
3 months ago

Hi,

We use the process-step  "Automatic removal of role and system role memberships" (EX - Approvals to be made externally)  when an attestation case ha been denied. This is the final step in the approval process. We expect that this would result in a un-subscription. 

Everything seem to work well in the process, and in the last step the process "VI_AttestationCase_RemoveMembership" is running without any errors. But the System Role is not un-subscribed. 

We have checked the configuration parameter under "QER\Attestation\AutoRemovalScope". But cannot see any obvious parameter that is not checked. 

The attestation-policy is a re-attestation of the users requested System Roles from the IT-Shop.

Version is 9.2

Any idea of why the assignments are not un-subscribed?

Thanks!

With Regards

Stig Hylen

 

Parents
  • 0 1 month ago

    Hi Stig,

    I would take a close look at PersonWantsOrg.  We have come across this situation many times at my customer and we found that the original assignment request IS un-subscribed/aborted BUT ...... the original request has/had a Valid until date set ........ meaning that it is/was possible for a second request for the same assignment to be raised ...... this request would go through the full approval flow but then sit in the system in the state GRANTED/WAITING.  When the original request is un-subscribed/aborted as a result of the attestation deny, the waiting request becomes active.

    This 'might' be what's happening in your case ...... so check PWO for 'duplicate' entries for UID_PersonOrdered and ObjectKeyOrdered (or whatever other UID's represent the ordered product).

    Hope that helps.

    B.

Reply
  • 0 1 month ago

    Hi Stig,

    I would take a close look at PersonWantsOrg.  We have come across this situation many times at my customer and we found that the original assignment request IS un-subscribed/aborted BUT ...... the original request has/had a Valid until date set ........ meaning that it is/was possible for a second request for the same assignment to be raised ...... this request would go through the full approval flow but then sit in the system in the state GRANTED/WAITING.  When the original request is un-subscribed/aborted as a result of the attestation deny, the waiting request becomes active.

    This 'might' be what's happening in your case ...... so check PWO for 'duplicate' entries for UID_PersonOrdered and ObjectKeyOrdered (or whatever other UID's represent the ordered product).

    Hope that helps.

    B.

Children
No Data