Question
Interaction Manager property key becoming null
Hello folks,
I am using interaction manager at various places in my solution consisting of multiple projects.
I observe that various interaction properties while dragged into automation prompts a requirement for key while others in the same automation considers key automatically and code works fine.
But if a part od code is changed in that automation, the key value is set to none abruptly for some properties in that automation. Have anyone else came across this behavior? Or what is the key providing correct mechanism in pega robotics studio?
Pegasystems Inc.
US
Key fittings are inherited downstream in automations. As you disconnect and connect execution paths, these key fittings are re-calculated. It is best practice to use any keyed components at the beginning of an automation to ensure that they are not affected by deleting and adding execution links (yellow lines). Retrieve the values needed at the beginning and store them in local variables for use later. Set any values at the end so that you have a single place where you'll need to provide the key to perform any updates.