AnsweredAssumed Answered

IGL 7.0.2 Configuring fulfilment WFs for local AND collected applications

Question asked by Andy Cheek on Jul 28, 2017
Latest reply on Aug 3, 2017 by Andy Cheek

Urgently need some help here! We are migrating from IMG 6.9.1 to IGL 7.0.2 and replacing a custom fulfilment handler (as provided years ago by then Aveksa PS) with calls to the Remedy webservice that the handler invoked (old code, custom code, not supported, etc.).

 

The WS node is straightforward and that works. The issue we have is with getting the changes updated to reflect the correct state, i.e.

 

Current version - Local application

  • The local entitlement collector is configured with Apply User-Entitlement Changes Immediately = false and Generate user entitlements = true
  • The fulfilment handler is configured with Change Item Succeeds Alwaystrue and Verification = false

This means that changes BEFORE the fulfilment handler are marked Pending Action. AFTER the fulfilment handler they go straight to Completed AND are assigned to the user (as no further fulfilment processing required).

 

Current version - Collected application

  • The fulfilment handler is configured with Change Item Succeeds Always = false and Verification = true

This means that changes BEFORE the fulfilment handler are marked Pending Action. AFTER the fulfilment handler they go to Pending Verification and the WF moves to a Wait for Verification node (as it has to see the change collected back into IMG before completing. Only once the change is collected is new access assigned to the user or revoked access removed from the user.

 

Our understanding was that these were standard settings, states, etc. ... so how do we achieve the same result in IGL 7.0.2 when we are not calling this custom fulfilment handler any more?

 

Frank Schubert, Sean Miller, Jamie Pryer

Outcomes