Question

2
Replies
689
Views
PALANIAPPAN Member since 2011 2 posts
Natraj
Posted: September 13, 2017
Last activity: September 13, 2017
Closed

New Starting Flow is not picked when moved to higher environment

In a development environment , we use New work Gadget to display the start flows in the UI.We had added a new start flow from B and it worked fine in Dev. We created a patch and when testing in SIT, the Flow A is getting called but Flow B is not picked . while running the tracer , we found that in Work- LookupProcessList acitivity which is called from GetStartingFlows activity, when doing an obj- open on Data-Admin-StartingFlows, the result brings Flow A only but not Flow B. The app explorer lists the flows rightly , Flow B is displayed as the start flow. Is there any thing else which needs to be done? Was the DB not updated when we ran the patch in SIT?

Low-Code App Development Installation and Deployment
Moderation Team has archived post
Share this page LinkedIn