Workflow and Non-workflow BPs
Business processes (BPs) can be designed with or without workflows. A workflow specifies how a BP proceeds from start to finish. Workflows define how records are routed and govern the behavior of each step in the BP. Each step uses the forms designed for it in uDesigner.
Most BPs include one or more workflow or workflows. However, some BPs serve only to store data. These BPs are called non-workflow BPs. For example, a non-workflow BP can record Warranty or Estimate information.
when the record contains saved changes that have not been completed by selecting Submit. The icon is not displayed when the record has a status such as Submitted, Terminal, or Initiated. Users can use the Create New View option and the Show Edit Records parameter to filter the log and display editable records. For more information on setting up filtering, see Business Processes in Company Logs and Logs Nodes.
Note:
The following non-workflow BP types require you to select the Edit button in the upper-right corner of the BP record to put the record into an editable state:- PM Book
- PM Book Template
- Lease
After a workflow BP record is created by using a workflow schema (unique combination of Setup Name and Workflow Name), the record continues to reference the workflow schema even if the schema status is changed to Inactive.
This behavior applies to workflow records in the following statuses:
- Draft
- Initiation Step (I-Step)
- Any other workflow step
If an Active BP Template exists, it continues to create records that reference the Inactive workflow schema. For instructions about creating a template, see Creating BP Templates and Scheduling BP Creation.
Behavior of the Due Date (due_date) Field
In the Workflow Settings field in the Workflow Setup of a BP, the Override Workflow Due Date field determines whether users can edit the due date.
If the Override Workflow Due Date field is set to Yes, you can edit the due date in the creation step. The system also uses a due date that is added or updated through a CSV or Microsoft Excel file import.
If the Override Workflow Due Date field is set to No, you cannot edit the due date in the creation step. Also, you cannot edit the due date after work has started or the record has advanced to the next workflow step (is in flight).
When you create workflow BP records through file a CSV or Microsoft Excel file import, the system automatically sets the Due Date according to the Workflow Settings and ignores the Due Date in the input file. When you update workflow BP records through a file import, the system retains the Due Date that was set according to on the Workflow Settings and ignores the Due Date provided in the input file.