Custom RequestType not displayed correctly in UI

IdentityIQ (IIQ) IIQ Discussion and Questions
1

I’m using IdentityIQ 7.2p3.

I created a custom requestType, i.e. when I invoke workflow “Identity Request Initialize”, I passed a custom value in “flow” argument.

However this new value isn’t displayed properly in UI:

image
image433×687 23.4 KB

First request for Man, Noble has requestType “AccessRequest”.
The others use a custom value and shows up as empty string.

I located the message key in iiqMessage.properties, e.g.
request_type_access_request=Request Access

So I added mine:
request_type_[custom value]=[Custom string]

and I restarted Tomcat.

But the UI keeps showing empty string. How do I add a new request type properly?

2

If I remember correctly, your custom flow name must also be added to the accessRequestTypes entry in the SystemConfiguration object like below. I believe adding spaces also causes the custom types to not render correctly. There is probably some additional customization need to make that happen.

image
image880×796 64.4 KB

1 Like
3

Unfortunately that’s still not enough.

  1. My custom request type is named “RetainAccount”.

  2. I added in iiqMessage.properties:
    request_type_retain_account=Retain Account Request

  3. I added in accessRequestTypes list:
    RetainAccount

  4. I restarted Tomcat and tested with existing and new request of the custom type. They are still displayed as empty string.

Adding the accessRequestTypes did add something though.

image
image1908×537 30.7 KB

The filter drop down list now contains my custom request types, but for the request list it is still not working.

4

@patrickboston

Thanks to you mentioning “accessRequestTypes” I managed to find this:
https://community.sailpoint.com/t5/IdentityIQ-Wiki/Adding-a-new-access-request-type-in-IdentityIQ-7-2/ta-p/82587

Turns out since 7.2 you must edit “SailPointClassicBundle.js” directly to add a new type, which points to a key in message bundle.

This is so bothersome… why isn’t that JavaScript creating the list out of SystemConfiguration and the message bundles like in pre 7.2?

5

That’s interesting. I was able to achieve this in 8.0 without modifying any javascript (as long as my custom types didn’t have spaces). Are you sure you are setting the “flow” variable to match one of the entries you added to the SystemConfiguration? Also, if you haven’t tried testing a new workflow after the entries were added, and you were expecting it to be applied retroactively, I don’t think that is the case. So try with a new workflow case.

6

That’s because I’m using 7.2p3! Upgrade to 8.1 is underway, hopefully that JS has been improved there.

Edit: Maybe not… I checked the 8.1’s JS file, that array is still there.

@ patrickboston
If you can, check your \Tomcat\webapps\identityiq\ui\js\bundles\SailPointClassicBundle.js and see if your custom request types are found inside.

1 Like