Share all details related to your problem, including any error messages you may have received.
When someone (the requester) is requesting access for someone else (the requestee), does the application provisioning policy have access to the requester’s identity? I would like to have a hidden field be made visible based on the requester’s department. Is that possible?
The requester is not available in the provisioning policy, however you can easily get the requester from the provisioning plan in the before provisioning rule.
Thank you for the reply. Getting the requester in the before provisioning rule doesn’t help me though. Guess I will have to come up with some other solution.
You can also take a look at the ‘LCM Provisioning’ or ‘Identity Request Provisioning’ workflows, where you can inject the hidden field in the provisioning plan.
While reading your question again, some extra question: Are you referring to injecting an hidden field via the provisioning policy (to have it provisioned to the application), or do you want to make an hidden field visible during the initial access request (in the form) and show it to the requester?
I created a rule and am still getting the error. Below is the rule I am using. What am I doing wrong?
<?xml version='1.0' encoding='UTF-8'?>
The log object associated with the SailPointContext.
A sailpoint.api.SailPointContext object that can be used to query the database if necessary.
The Identity object that represents the user needing the field value.
The sailpoint.object.Link that is being acted upon. If the link is not applicable,
this value will be null.
The sailpoint.object.ManagedAttribute that is being acted upon. If the managed attribute
is not applicable, the value will be null.
The provisioning project being acted upon. If a provisioning project is not applicable,
the value will be null.
The account request. If an account request is not applicable, the value will be null.
The object request. If an object request is not applicable, the value will be null.
The role with the template we are compiling. If the role is
not applicable, the value will be null.
The sailpont.object.Application with the template we are compiling. If the application
is not applicable, the value will be null.
The Template that contains this field.
The current field being computed.
The current value corresponding to the identity or account attribute that the field represents.
If no current value is set, this value will be null.
The operation being performed.
The string value created.
How I did:
I created a “provisioning policy” for for create user. Raised an access request for an user which in terms executes the policy form and prints the lines in console.
Thank you for the link Kumar. That ended up helping me solve it. The project argument was not being passed to the “Present Provisioning Form” step, which is why it wasn’t working. So simple, yet I completely missed it. Thank you again!!