Assistance Needed for Displaying Disclaimer in SailPoint IIQ Provisioning Policy Form for an application

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Hi Team,

I hope you’re doing well.

I am currently working on integrating an application with SailPoint IdentityIQ. As part of this process, I need to display a disclaimer to end users in bold red text within the account provisioning policy form. Despite my efforts, I haven’t been able to achieve this. I tried using the helpKey with HTML tags, but it didn’t work as expected.

Additionally, I want to hide this disclaimer if the user selects “Yes” in response to a specific question. I attempted to implement this using the hidden Key property, but unfortunately, that approach didn’t work either.

Could you please guide me on how to achieve these requirements? Any advice or suggestions would be greatly appreciated. Please find the screenshot below for your reference.

Thank you in advance for your support!

image
image1321×724 55.4 KB

Best regards,
Venu

2

Hi @Venu9000 Here is a working example I have, make sure to add a wf variable for the postBack:

<Section label="Disclaimer.">
    <Field displayName="Selector field" displayType="radio" name="selector" postBack="true" required="true" type="string">
      <AllowedValuesDefinition>
        <Value>
          <List>
            <String>Yes</String>
            <String>No</String>
          </List>
        </Value>
      </AllowedValuesDefinition>
    </Field>
  </Section>
  <Section label="hidden section" type="text">
    <Attributes>
      <Map>
        <entry key="hidden">
          <value>
            <Script>
              <Source>
                import sailpoint.object.Identity;
                 if("Yes".equals(selector)) {

            return true;
            } else {
            return false;
            }

          </Source>
        </Script>
      </value>
    </entry>
  </Map>
</Attributes>
<Field filterString="htmlRender" type="text">
  <Attributes>
    <Map>
      <entry key="contentIsEscaped" value="true"/>
    </Map>
  </Attributes>
  <Script>
    <Source>
      return "&lt;font color='#ff0000'>&lt;strong>This is a disclaimer&lt;/strong>&lt;/font>";

    </Source>
  </Script>
</Field>
</Section>
3

Should I create a separate section for it, or should I add it to the existing section?

4

It is the same issue.

5

A separate section will work best.

6

I created separate sections, but the issue remains. When I select “No,” the hidden section does not appear. Please find the attached ProvisioningForms for your reference.

ProvisioningForms.xml (2.8 KB)

7

@Venu9000 Make sure you have your field in a section and it is set to postBack=true, then add a NEW section with the hidden script and a field as shown with the disclaimer.

image
image1067×323 10.1 KB

image
image1045×235 6.64 KB

8

I can get it to work by removing or escaping the quotes around ACTIVE and INACTIVE.

image
image1043×361 22.5 KB

image
image1043×220 9.7 KB

9

Could you please send me the updated ProvisioningForms.xml

10

Is this part of a workflow? Some form settings will not work as a straight provisioning form but will as a workflow form. I tested it as a workflow form. How are you calling it?

11

We are not calling it from a workflow. During new account creation in the target application, the system prompts for input from the provisioning policy form.

Is there a way to achieve this using the application provisioning policy form?

12

the “entity” here is an entitlement yes? could this be calculated versus having the user select yes/no?

13

Based on the fact that this is a provisioning form, it may not be the best place to present a disclaimer to the user. Disclaimer is shown based on entity selection, however that would already be done at this point. Asking the user to select yes/no would be an extra step here. Nothing preventing a user who selected incorrect entities from selecting “Yes”. That part could be pre-determined.

If the requirement is to display this disclaimer within the UI to end users, then we can discuss different options.

If it is just to alert the user of what state the account was created in (Active / Inactive) based on entity selection, you could handle this via email in an AfterProvisioningRule provided provisioning activities are successful.

I don’t have the full scope of this situation, so feel free to explain more or send me a message to determine how to approach this in the best way.