Workflow Editor

The workflow editor is an editor used for the following purposes:

1. Organize the design by illustrating the workflow. It is to be used only as a design document.
2. Automatically create a definition that serves as the skeleton of the workflow from the contents of the workflow editor. (Workflow generator wizard)

How to use the Editor

1. Click the "Workflow" menu located on the side menu
2. The workflow editor opens in the right panel.
3. Drag and drop the left node component into the editor.
4. Drag and drop connection points on the edges of nodes to connect them to each other.
5. Single click on node or operation will bring up the "Edit Properties" menu and the "Delete" menu. "Edit Properties" opens the properties dialog. On the other hand, "Delete" deletes nodes and operations.
6. Click the "Save" button in the upper right corner to save the drawing.
7. Click the "Generate Workflow" button at the top to launch Workflow Generator Wizard

Tips

Tips

The workflow editor can save only one data per application.

Commit

The user can commit an app definition to repository with the application definition against commit.

Node

Node is a generic term for the "Start", "End" and "Status" objects placed in the workflow editor.

Start

Indicates the start of a workflow. The "start" is usually assigned a UI that will be a new form. The status connected from the "start" node is the first status. The "start" node must be included in the Workflow Editor.

Property

Item	Description	Remarks
UI	UI to be a new form	- The UI must be created in advance. (An empty UI is fine) - The Workflow Generator Wizard creates a Create form button for this UI

Tips

Tips

At the start of the program, there are no case records registered yet and no status. The case must be created by the operation from the start. $fn.createCase(/en/manuals/workflow/built-in-functions/#fn.createCase) The type of operation from “start” node can only be set for “Create”.

End

Indicates the end of the workflow. There are no properties to assign to termination. The "end" node must be included in the workflow editor.

Status

Indicates the status during the workflow. The status must have an ID and label that uniquely identifies the status, and a UI to be displayed for this status. One or more Status nodes must be included in the Workflow Editor.

Properties

Item	Description	Remarks
ID	ID that uniquely identifies the status	- It is used in the processing of actions created from the Workflow Generator Wizard. - Initial values are automatically assigned by the system. It can be changed.
Label	Display string for status	It is used only as an identifier within the workflow editor.
UI	UI to be displayed for the status in question	- The UI must be created in advance. (An empty UI is fine) - As a rule, there will be multiple statuses. For each status, it is possible to set a different UI or the same UI. If the same UI is set up, status-based controls must be implemented within each UI.

Tips

Tips

In the status during the workflow, a record indicating the case is already registered in the $case table. Workflow operations will update this record.

Operations

Indicates workflow operation. The status and the person in charge are updated by the operation, and the user is redirected to the UI set for the status.

Properties

Item	Description	Remarks
ID	ID that uniquely identifies an operation	This will be the ID of the button generated by the workflow Generator wizard. Initial values are automatically assigned by the system. Can be changed.
Label	Display string for operations	It is used as an identifier within the workflow editor. This will be the label for the button generated by the Workflow Generator Wizard.
Type	Type of workflow processing	Choose from the following types: For operations starting at the "status" node None No operations are performed Update The case moves forward in the forward direction of the workflow. $fn.updateCase will be written on the button created by the Workflow Creation Wizard. Remand Refer the case back to the previous person in charge. Button created by the workflow creation wizard will contain $fn.remandCase Reject Reject the case. $fn.rejectCase will be written on the button created by the Workflow Creation Wizard. For operations starting at the "start" node read only description Create The case moves forward in the forward direction of the workflow. $fn.createCase will be written on the button created by the Workflow Creation Wizard.
User	Select next person in charge	Select the next person in charge from the following only when the workflow process is of type [Create][Update] Selction Description None [owner_id] property value of the button action definition $fn.createCase or $fn.updateCase created in the Workflow Creation Wizard is set to empty data. Select User Workflow creation wizard will create a user-selected item. Also, the [owner_id] property value of the action definition $fn.createCase or $fn.updateCase of the created button is set to the value selected from the user selection. Current User [owner_id] property value of the action definition $fn.createCase or $fn.updateCase of the button created in the workflow creation wizard is set to the sign-in user. Tips Running the Workflow Creation Wizard does not include controls that allow only designated personnel to operate the workflow.

Tips

Tips

Withdraw cannot be set from within the Workflow Editor. If used, the built-in function $fn.withdrawCase or its equivalent must be written directly in the action.