Dear Developers,
For those who have worked with IIQ know what custom objects are. For those who didn’t here is a link (very old link btw) : Leveraging the custom object in IdentityIQ - Compass
So my question is, when there is a use case to store a set of values for reference to be used in Rules/Transforms, how are you doing it in IDN? Or do you know of any workaround?
Thanks!
-Tamalika
Hi @tamalika01 , from what I remember back to my IIQ days, we used the custom objects to store a list of key-values that we could reference in a rule or a workflow later on. This can be easily done using a Lookup transform Lookup | SailPoint Developer Community.
Hi @tamalika01 ,
If you want to hardcode some values and use them in rules , you can follow the approach:
In source json add those values under connectorAttributes , lets say “companyLocation”:“ABC”
Inyour rule you can get those vals by using : String companyLocation = application.getStringAttributeValue(“companyLocation”);
This method is very helpful for cloud rules. Those hardcoded values can be easily change by just updating the source from api.
Adding to @gourab point, below is the how you can add values on source
PATCH: /sources/:id
[
{
“op”: “add”,
“path”: “/connectorAttributes/attributeName”,
“value”: “attributeValue”
}
]
Thanks