Kensho Tsuchihashi (KenshoTsuchihashi)
Project Delivery Leader
Pegasystems Inc.
KenshoTsuchihashi Member since 2010 141 posts
Posted: June 13, 2017
Last activity: June 18, 2017
Posted: 13 Jun 2017 1:13 EDT
Last activity: 18 Jun 2017 21:37 EDT

The task with label 'ASSIGNMENTXX' and id 'XYZ' could not be found in this flow.


We have MyApp:01.01 in production and we are going to import a new enhanced version MyApp:01.02. There is a workflow which has small changes (We have just overrode the flow rule to add local actions to Assignment shape). Since customers don't want to resolve all open cases before import, and also the changes are minimum, I would expect the old assignment (created in prior MyApp:01.01 version) for this flow to be still openable / performable after new version is imported. However, there is only one flow rule that is giving error when user tries to open this assignment that says, "The task with label 'ASSIGNMENTXX' and id 'XYZ' could not be found in this flow." and assignment can't be performed. There are also some other flows but they are fine and only this flow is problematic. My guess is, when developer overrode this flow rule, he might have deleted the assignment shape and added a new shape. Each assignment shape has some internal (in this case "63") and that shape is gone. The old assignment is created based on this old "63" assignment shape but after new version is released, user would open this same assignment object in new assignment shape (maybe different number?) and PRPC throws an error. Am I correct? If so, why isn't PRPC built such way that this kind of migration would be handled correctly? If my guess is incorrect, can anyone direct me how to fix this error?

*Details are attached in the excel file and please take a look.


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.