I am having an application called Genesys that supports SCIM but when it does account aggregation it only pulls in active accounts but not disabled accounts. I tried using the web services connector instead and used two account aggregation operations but that is not working either. It only does one operation and if I chain them together it is not working either. Do I need a rule of some sort to get both account aggregation to operate and pull in all accounts (active and disabled)? Any guidance is appreciated here.
I believe Genesys provides only enabled accounts, check with your application team. Same case with me as well.
The SCIM API allows for a filter to specify if you want Active or Disabled accounts just not both.
I was hoping to get around it with the web services connector.
Thanks for your response. We did put in a request to Genesys for an update to their API to allow for both.
1 Like
I am confused , are you sayiing SCIM API return all the accounts ?
Maybe you can create two sources, one to house active accounts and one to house inactive?
I want all accounts so if people get rehired the account can be enabled as currently it would try create a new account and fails as an account already exists.
That is not really an option but appreciate the suggestion.
- Check with application team if they can change this behavior
- If not then using SCIM connector, disable account deletion, we need to change the filter everyday, run one aggregation for enabled account filter and the other one for disabled accounts, it is manual work and not a good idea to change the configuration(even if it is minor) everyday.
- Webservices connector, have two operations for Account Aggregation, first one reads all enabled users, second one for all disabled users. But you need to get APIs that works like this.
Option 1. It is a commercial product (SaaS solution) so we did out in a request to the vendor.
Option 2 could work indeed with some manual intervention.
Option 3 as I pointed out does not work. Although you can have two account aggregations, they are supposed to work in tandem not by themselves. It is meant for when you have additional details to get about the account from the first operation. I wish it would do what we want to have two separate account aggregations taken place but that is not how it works.
Thanks for your feedback.
yes, It wont work though UI. But you can do that 2nd aggregation through Webservice After Operation Rule, append the response from 2nd aggregation to 1st one. With this you get all the accounts rite.
Yes that is indeed another option but I prefer to stay away from rules where possible. it sounds like a use case that should be supported by the product. Thanks for all the feedback.
filter supports only eq operation, I wish it supported ew (ends with). However see if there is any common attribute for all users like company or division. Then you can get all users irrespective of their status.
Hello @pdegraaffiam,
We deployed our Genesys connector yesterday and we configured the aggregation operations as follow:
The parent endpoint option isn’t configured on the second operation.
For the aggregation operation used for inactive accounts, make sure to add the filter when you build the URL in the pagination parameters:
$endpoint.fullUrl$ = $application.baseUrl$ + “/Users?filter=active eq false&startIndex=” + $sysparm_offset$
Without this filter part, you will aggregate the first page of inactive accounts and then the following pages of active accounts.
In our context, we aggregates with ISC the same accounts as with our postman collection.
Bastien
2 Likes
When I flipped the two account aggregations (inactive first) it works indeed like a dream. No idea why it does not work the other way around but I take it.
Thanks so much for your help. Saves us having to develop a rule for it.
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.