Hello Everyone! I am trying to implement a web services connector. All the configurations are complete but I am facing an issue with the “Account Enable Status Attribute” in the source config page. Issue Faced: In my existing configuration, the “Account Enable Status” attribute is left as blank. …

Hi Arshad, Sorry, I was reading too quickly this morning and missed that line on the article… My apologies. You’re right, you will need to use a WebServiceAfterOperationRule on the account aggregation operation to set the IIQDisabled flag as either false or true. Here’s an example of evaluating U…

[image] Arshad: gest me with a solution on how to handle th Use afteroperation rule,create another attribute in schema and populate the value of it as yes/no or active/inactive based on “interface” attribute. Use that attribute as status attribute.

[image] cpatel: ve based on “interface” attri Hi Chirag, Thank you for your response. From the web service source reference documentation, It is mentioned that “Account Enable Status Attribute” is checked while loading the accounts itself (ie. in parallel with aggregation.) From your feedb…

Hi Arshad, Are you sure the OR (||) operation does not work? I found the documentation - Server and Common Configuration Parameters - and it has an example: status=Active || status=Pending Note that you will also need to configure the enable/disable operations: Supported Operations Thanks, Lisa …

Hey Lisa, From the web service source documentation, it says " The Account Enable Status Attribute field supports only single value for status attribute, for example: ‘status=Active’. Conditional operators are not applicable for the field as displayed in the following examples: status=Active || sta…

Hi @Arshad , Were we able to answer your question? If so, can you mark the comment that solved your question? Thank you, Colin

Hey @colin_mckibben Thanks for following up. I somehow missed on replying back to this topic. Hi @lisa.ivy, thank you so much for the code snippet. I made few tweaks upon your code and it worked! Appreciate your quick response! Thanks.

Glad we could help @Arshad . Would you mind sharing the tweaks you made for future viewers of this thread?

Sure @colin_mckibben , We need to ensure that the Account Id in the source schema and the unique id from the target API response are the same (case sensitive). Here’s the snippet : Map updatedMapInfo = new HashMap(); List list = new ArrayList(); List response = (List) JsonUtil.toList(rawResponseO…

Web Services Connector | | Account Enable Status Attribute

SailPoint Human Fabric (SHF) SHF Discussion and Questions

cpatel (Chirag Patel) May 2, 2022, 10:03am 11

I developed this generic rule so everyone can reuse same rule: Generic after rule for account status in webservice source

Topic		Replies	Views
Account status in web service source not reflecting attribute value SHF Discussion and Questions webservice-connector , aggregation , identity-security-cloud	10	326	July 11, 2025
Onboard application using Web Service Connector - status field issue SHF Discussion and Questions identity-security-cloud	6	152	June 12, 2026
WebServiceAfterOperationRule - IIQDisabled not functioning as expected SHF Discussion and Questions webservice-connector , identity-security-cloud	4	422	May 27, 2025
ISC Web Services SaaS connector does not properly handle enable/disable status Bugs webservice-connector , identity-security-cloud , accounts , fixed , sources	11	761	November 19, 2024
Webservice connector account is not set to disable in accounts tab SHF Discussion and Questions webservice-connector , identity-security-cloud , provisioning	3	504	December 28, 2023

Web Services Connector | | Account Enable Status Attribute

Related topics