Flow has custom workflow and can be used to design features such as work review, data management, etc.
Zdoo Pro 1.1+ added Flow module.
Zdoo Pro 1.2+ added the data source, custom database, cross-table update, etc.
Zdoo Pro 1.4+ added specification tables, child flows, optimized privilege control, and etc.
Take the flow of internal referral as an example and see how to design a flow in Zdoo.
1. Collect and organize requirements of the flow
The information that will involve in this flow includes,
- Field: Name, Amount, etc.
- Review: who will review and what is in the review
- Privilege: privileges of all the staff involved in the flow
Internal Referral Fields: Referrer, Job Position, Name, Age, Gender, Email, Mobile Phone, Resume, Ceritficate, Document. Job position related fields: Title, Department, Number of user, Job Description, Benefits. Status: Draft, In Review, Pass Review, Pass Interview, Joined, Rewarded, Rejected. Status related fields: Status, Reviewer, Interviewer, Onboard Handler, Reward Handler, and all the date and time related. Workflow: (all staff)Create an internal referal(draft)->(create by) Submit the application(in review)->(HR) Review (pass review)->(interviewer) Interview(pass interview)->(HR) Onboard (joined)->(Dept manager)Reward (rewarded). Privileges: all staff can check the internal referral they submitted; reviewers can check and review the application that is related to themselves.
The flow mentioned above in Zdoo would look like the screenshot below.
2. Add the flow and fields according to requirements
Create the flow and put it to the right application. If there is information that has to be managed separately, create a child flow for it (for example, job position management). If there is any information that can be changed in terms of numbers, create a specification table (for example, resume and certificate).
Create the flow
Add a field
Add a sub flow that is linked to a filed.
Create a flow and link it to a sub flow.
Create a sub table.
Create fields for a sub table.
3. Create actions for status
Each operation is an action in the flow. For example, submit an application, review, reject, etc.
Set the interface when creating a referral
The current login user is the default Referrer
Add the action to submit an application
Add the action to review
4. Add labels according to privileges
Each type of list has a label in the flow. For example, My Application, Wait, etc.
Add a label for My Referral
5. Set actions and extended actions(results) according to privileges
When it comes to the status, it is necessary to decide whether to allow the current action and set the mark of the next status. For example, only the draft application can be submitted. After the application is submitted, specify the reviewer of the next reviewer and record the time of the current action.
Set the trigger condition for submitting an application
Set the status of the next action after reviewing
6. Set privileges
Actions and labels can be set in Admin->Privilege.