AnsweredAssumed Answered

Implementing different fulfillment workflows for different types of change requests associated with an application

Question asked by Dipankar Ghosh on Aug 2, 2017
Latest reply on Aug 4, 2017 by Edwin Mullie

We are on RSA Identity Governance and Lifecycle version 7.0.1 P02 HF08.

The issue descriptions is as follows:



We have request workflows assigned for all the various ways in which change requests can be created as listed in the Requests->Workflows->Overview tab.(For example - Requests that are explicitly created, Requests created through user access reviews, Requests created due to rule violations etc.)


All of these request workflows have corresponding default fulfillment workflows which are used when an application does not have a specific fulfillment workflow assigned to it.


In scenarios where we are required to implement some application-specific logic, we assign a non-default fulfillment workflow to that application.


As an example, let's say we need a different fulfillment logic implemented for requests that are explicitly created for an application. In order to accomplish, we create a fulfillment workflow with the required logic and assign it to the application. The issue we are facing is that, now every other kind of request for that application, i.e. requests which are NOT explicitly created( for example, requests created from rule violations or requests created from user access reviews etc.), follows the customized fulfillment workflow that we intended to be used only for one type of request.


How can we implement workflows in a way where we can define customized logic for the fulfillment of a certain type of change request while not affecting the default fulfillment path for other types of change requests?