Hi all, I have a WebServices source that requires a “lastProcessedID” parameter be passed at each aggregation. I have considered defining a connectorAttribute and setting it using an after operation rule, but after rereading the rule guidelines, I’m not confident that setting an attribute on the so…

hey @MattUribe , got it! so its not application.setAttribute like i thought. you can set ConnectorAttributes via a response object so: something like this: ... processedData.put("data", returnObj); Map connectorStateMap = new HashMap(); connectorStateMap.put("moop","Stephen Was Here"); …

Hey Matt, You can use the transientValues attribute to store data in between runs. There was actually just a presentation utilizing this feature at SailPoint’s Developer Days that might be a helpful guide. Video here Additionally, there are some other threads about folks using this attribute if yo…

Thanks Zach. I do have some experience using the transientValues, but what I have seen is that the data stored therein does not persist between aggregations, only throughout the duration of each aggregation. I have a before operation rule that checks for transientValues and pulls the data if it exi…

That is a Negative. Transient values survive from start-of-aggregation to end-of-aggregation. for my presentations that were linked above, I do not trust HR not to change things… thus, I lookup data at the start of each aggregation and (temporarily) store it. if you truly need reasonably persiste…

Thank you Stephen. What you’re describing about transientValues is exactly what I’ve experienced. Thank you for the presentation, by the way. Before posting, I had added a connector attribute to the source using PATCH /v3/sources/:id [ { "op": "add", "path": "/connectorAttributes/deltaA…

i would DEFINITELY avoid trying to call a patch from your rule. Let me mock up a test here and see what I can see.

hmm. not finding anything obvious from my testing. let me reach out to one of the product teams, and see what i can find out re: “Persistent” storage from your rule

Store an Attribute on WebServices Source Between Aggregations

Identity Security Cloud (ISC) ISC Discussion and Questions

MattUribe (Matt Uribe) April 17, 2024, 4:17pm 10

Wow, thank you @StephenHolinaty

I’ve been through that doc but somehow missed “the connectorStateMap values are updated in the application object permanently”.

Thanks again. That looks like exactly what I need.

Matt

1 Like

Topic		Replies	Views
Before and After Operation Rules - Web Services ISC Discussion and Questions webservice-connector , identity-security-cloud	13	774	October 11, 2024
Using WebService connector rules to streamline and accommodate “interesting” sources Video Library identity-security-cloud , developer-days-2024-isc , developer-days	3	1338	April 17, 2024
Set attribute back to Source Config with web service after operation rule ISC Discussion and Questions webservice-connector , rules , identity-security-cloud	2	437	July 13, 2023
Save an attribute from the response body to the Source parameters ISC Discussion and Questions webservice-connector , aggregation , identity-security-cloud	5	79	December 8, 2024
Transientvalue in before operation rule ISC Discussion and Questions identity-security-cloud	8	368	November 30, 2024

Store an Attribute on WebServices Source Between Aggregations

Related topics