Work up a draft of the process with pencil and paper. Map out key decisions, notification points, routing needs and closure points.
Keep in mind that the process will eventually need to function within PerfectApps using workflow stages and logical paths based on the data you collect on the app.
Do not try to manage multiple process points within one stage.
If the same role is involved at several different points in a process, don't try to manage those points from a single stage in your diagram.
For example, you have a customer service person who deals with issues relating to sales orders. There could be several process points related to the customer service representative:
•There is a special shipping cost and the customer must accept the fee in order for the process to continue. Does the customer agree to the fee?
•The order will be delayed due to insufficient stock. Does the customer want to wait or choose a different product?
•The customer has been sent a proof but is not happy with it. Customer Service needs to take action.
In this example, each of these scenarios should be an individual stage. The fact that they are all dealt with by the same customer service representative does not mean that there is one Customer Service stage. Setting the stage that way may limit your overall control.
You are not required to define workflow stages, but it is recommended.
You could manage workflow solely using ordinary behaviors but that could limit scalability of your app as it develops over time. Diagrams force you to organize your thinking. All notifications are organized behind the join lines of your workflow diagram. In addition, you will need stages and roles to properly manage field states that are dependent on an app instance being in a certain stage.
See also: App Layout and Workflow Needs
Return to: Adding Workflow, Designing an App
