John Bushey (JohnB381)

JohnB381 Member since 2016 9 posts
Posted: February 13, 2017
Last activity: February 23, 2017
Posted: 13 Feb 2017 15:21 EST
Last activity: 23 Feb 2017 6:25 EST

Processing assignments from a different application creating items with incorrect prefix

I'm having issues where work items are being created with the wrong prefix. They are being created with a default C- prefix. Everything works correctly when I create/update items where the work item is defined (let's call this Application A). I've created a common "support" monitoring application (let's call this application B) where we want to monitor several applications. From App B we would like to perform admin tasks to do things like retry a service call and continue the flow. From App B I can find work that we've routed to support work basket and use actions. However, when the flow reaches the next assignment shape the pxApplication property of the assignment is set to "Application B". Subsequently when the flow tries to create a child item the prefix is not correct.

When I do the same thing from Application A the assignment's pxApplication property is set to "Application A" and the child item is created with the correct prefix. This is expected since the parent and child item are defined in this application but I'm not sure how to explain why this does not work from Application B.

Application B has access to Application A's rules and I can action the items but I'd like some help explaining why the outcome is unexpected.

Low-Code App Development Case Management
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.