Adam Arrowsmith -
We are experiencing issues trying to use ExecutionUtil.getProcessProperty() with an error stating that "component does not exist." We are passing in the component ID for the process property and the key for the actual property we want to get.
Looking at the above comments, it looks like there is actually a different ID that should be referenced. However, that was in 2013!
Was this ever fixed? Are we possibly doing something incorrectly? Here is an example of our method call:
String coolProp = ExecutionUtil.getProcessProperty("49acebce-2689-480e-b216-abe0e5f189b4", "580e32d9-5247-40ef-b33b-f002c7e6ee76");David Darnell FYI
componentId is the Process Property's Component ID (can be found in that component's Revision History dialog) and propertyKey is the "Key" value displayed in the Process Property component UI (this was added at some point):
Fun tech note: Interestingly enough, when initially researching this for my reply, I too ran into a "component xxxx does not exist" error. After scratching my head a bit I realized it was because my super simple test process with only a Start shape and a Data Process shape did not have an explicit component reference to the Process Property component. So when the process and its dependent components were shipped to my atom for execution, the Process Property component was not included, and hence the error. So I added a Set Properties shape that referenced said Process Property component and found success.
Aha! That was the issue then. I can see that it isn't even an option to extend the property without a reference outside of the script. Thanks, Adam!
David Darnell - it looks like the process property could simply be referenced somewhere in the process (the shape doesn't even need to be connected in the flow). I tested this as well and it works just fine.
Retrieving data ...