I need to identify the user running the process and can't find a way to get to this underlying data.
If you extended the properties, you can make a call against the Atomsphere API Environment Extensions object
Would you happen to know of a good example of this in Groovy?
Are you looking for the user who executed the Boomi process or the user ID configured for a given connection?
In Lee's suggestion, you technically wouldn't need to use Groovy, just the AtomSphere API connector.
Can you share a little more about your overall objective/requirement? Perhaps there's another way to approach it...
I'm trying to get the userID of the person running the process. This is an extensible Process Property so I believe I have to go through the Environment Extensions API object.
I'm now attempting to set the userID as a Dynamic Process Property using an Atomsphere API Connector call within the Set Properties shape. When I test my process I get an error for which I can find absolutely no documentation: ID of object to get must not be blank or null.
The ID in the shape's input parameter is the only value available. I would imagine this is the ID with the null value, but I'm not really even sure what this ID is or where it comes from.
See the attached images for the Set Properties shape parameters.
Thanks for any help you may be able to offer.
A couple of comments:
I'm trying to get the userID of the person running the process. This is an extensible Process Property...
Based on this comment, it sounds like you're actually looking for the user ID configured in the connection vs. the AtomSphere that manually executed the process, for example. That's fine, and you can obtain that using the EnvironmentExtensions API call and grab the user ID value from the desired connection.
You should be setting the connection's user ID as a Connection extension. You will not be able to dynamically "override" the connection component's settings with an arbitrary value, say from a process property. This is because the connection settings are related to licensing.
Lastly the "ID" input for GET connector actions is to be used to supply a single record's ID (e.g. "get me record ID 123"), not the user ID to authenticate the call.
Retrieving data ...