Business justification on workflow request

[Anon Anon]

Hi,

 

I am searching for a solution on how to capture the business justification when a user requests for an application role.

 

The flow requested is as below:

-> Tom adds access roles to Bob. Tom puts a comment of "I want it by FY15"  against this request for the approver to see.

-> As part of assigning the access role, a workflow approval is trigger, and approval is sent to Mary

-> Mary views the comment "I want it by FY15", and then proceeds to approve or reject the request

-> If Mary rejects the request, then she should be able to provide the rejection reason of "It is FY14, please re-raise this in FY15".

-> Tom receives an email with rejection reason of  "It is FY14, please re-raise this in FY15".

 

Question: How do I store the comments in the OOTB CA IM product both when a request is raised, as well as when the workflow is rejected?

Is it possible to do this without creating a physical attribute in the database?

 

Any assistance would be appreciated.

 

Regards

Kathleen

[Chris_Stallone]

Anybody have any insight to offer Kathleen?

 

Kathleen Silveira wrote:

 

Hi,

 

I am searching for a solution on how to capture the business justification when a user requests for an application role.

 

The flow requested is as below:

-> Tom adds access roles to Bob. Tom puts a comment of "I want it by FY15"  against this request for the approver to see.

-> As part of assigning the access role, a workflow approval is trigger, and approval is sent to Mary

-> Mary views the comment "I want it by FY15", and then proceeds to approve or reject the request

-> If Mary rejects the request, then she should be able to provide the rejection reason of "It is FY14, please re-raise this in FY15".

-> Tom receives an email with rejection reason of  "It is FY14, please re-raise this in FY15".

 

Question: How do I store the comments in the OOTB CA IM product both when a request is raised, as well as when the workflow is rejected?

Is it possible to do this without creating a physical attribute in the database?

 

Any assistance would be appreciated.

 

Regards

Kathleen

[Sagi Gabay]

There is no Out Of The Box solution to this. Most chances you'll need to introduce an attribute and capture the change there. There may be ways to use Logical Attributes so that they're not persisted to the storage but I'm not too sure. You may want to open a support case if you can't figure it out.

 

Sagi