Hello,
I’m working on a workflow in IdentityNow ISC that is intended to automate the assignment of Scheduled Search subscriptions based on role assignment.
Goal:
When a specific role is assigned to an identity, the workflow should automatically assign that same identity to a Scheduled Search (subscription) with the same name as the role.
Example:
If Role: Reporting123 is assigned, assign the identity to Subscription: Reporting123.
We chose to trigger this on an identity attribute change (for simplicity), which reflects the role update. So far, this part works fine, whether through triggering an Access Request or an Account Aggregation completion. All is working fine.
The issue arises when trying to assign the identity to the Scheduled Search.
We attempted to use the PUT API “Update an existing Scheduled Search” to update the Scheduled Search. However, this API’s issue in here that it replaces the entire recipients list with the payload we provide. So if I only include the newly added identity in the recipients list of the PUT call, it overwrites and removes the existing recipients.
What I’ve tried as workarounds:
- Get the existing Scheduled Search using the GET API “Get a Scheduled Search” first, to fetch the current recipients list.
- Extract the recipients list and append to it the new identity ({ “type”: “IDENTITY”, “id”: "newId” }), and then reuse that combined list in the PUT API.
But here’s where I got stuck:
- There’s no scripting that would support transforming or manipulating this object list before passing it in the PUT API request body. Ref.
- The recipients list returned from the GET call is an object list, not string to be easily manipulated by using the Define Variable Operator. Ref.
- I tried using looping through recipients → Still hits the object vs. string wall. Ref.
I have attached the sample JSON structure of the workflow I’m working on. If anyone has any guidance or suggestions to help solve this, I would really appreciate it. Thanks in advance!