No-Code & Low-Code – Robosme's Intelligent Side
Workflow
Workflow in Robosme is the systematized form of "if-then" statements. It is the system's reflex when something happens to a record."
"If someone does this, you do that."
What is a Workflow?
When a record is:
- created
- updated
- status changed
- owner changed
- deleted
Robosme asks:
"Will I respond to this?" If the answer is "yes", you should prepare a workflow.
- Workflow Identity
- Workflow Name: It is for people. It should be clear what it does when read.
- System Name: It is for the system. Immutable, a reference.
- Concept: "Which record am I dealing with?" Is it a case, sale, or campaign?
- Owner & Access Level: Who owns this workflow and who can see it? Who can make changes to it.
Mentor Note
A workflow is also a record. A workflow left without an owner becomes a problem that no one owns tomorrow.
- When Should It Run?
Here you tell Robosme:
"Not always… run right at this moment."
The options are clear:
- Create
- Update
- Change status
- Assign
- Delete
In field update operations, the conditions under which it will run must be detailed. Two definitions must be made. Multiple values can be selected in the definitions.
- Which field(s)?
- On which change?
- New value assigned to field
- Field value changed
- Field value cleared
- What Should It Do?
The workflow line on the left is your scenario. Readable, simple, clear.
Which operations will be performed in which situation is defined in a flow.
Condition (If)
A condition filter is prepared based on the field values and relationships of the processed record. Actions are performed when this condition filter is met.
Nested if-then conditions can be defined when making definitions.
Defining conditions in workflow is not mandatory.
Action
- Assigns the record to someone or a team
- Changes the status of the record
- Clears, adds, updates fields
- Creates new record
- Sends email
- Sends notification
Either single action or chained actions can be defined. At least one action must be defined.