We're currently doing a POC for a customer here in the UK and we have the following Case design:
Find Customer and Contract
Enter Order Detail
Currently, when creating an order we have three possible stories:
A) If the user finds the customer and contract they proceed directly to 4. Enter Order Detail and then to 5. Validate Order
B) If the user finds the customer but not the contract then they go to 3. Add Contract then to 4. Enter Order Detail and then 5. Validate Order
C) If the user can't find the customer then they go to 2. Add Customer then to 3. Add Contract then to 4. Enter Order Detail and then to 5. Validate Order
The customer would like this functionality delivered so that they can select a customer or contract pair from a grid and then click a button to either create a new customer, contract or order.
I have attempted to use an activity and New-Flow to call the respective flows however some of the information is not being passed across as well as ResumeFlow.
Is there a standard way to move between steps within a stage and resume flow processing? I know there is the pxChangeStage activity which I have used before but I feel there ought to be something as simple to use for changing stages?
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
I have worked a solution out that allows you to skip through the steps when needed, it does not allow you to move back to a previous step.
On the button actions, use Finish Assignment. Call a Data Transform which sets one of two values (IsNewCustomer and IsNewContract). Create two when rules and place them on the step configurations for 2 and 3. The when rules look at the flags and if they're set to true, it should allow the step to be completed. If false it will skip the step.
So when the user clicks the button, a flag is set and the system works through the stage and decides if it needs to complete the step.
your found it yourself. Using when rules in the step behaviours is the right thing to do. As long as you only move forward and don't have to move back to a previous step.
Moving backwards is possible with some limitations at the moment, 7.1.8 or later release will have some new features that will allow to re-start a stage and to move back to a previous step within a stage.
That project was delayed to 7.2, but you won't have to wait long! We're putting on the finishing touches now. Basically we combined the Stage Designer and Outline View, so now you can go back a step easily using the Previous flow action, since steps are shapes in flows. Let me know if you would like a sneak preview.