How to configure the request workflow?
The state flow for requests can be changed to be in line with the organization's working method.
To create or change the new state configurations, you must access Definitions | Requests | Workflow
- The state list is presented;
- To create new states, press the button create, to change the state configuration already defined, select the desired state.
When creating or editing the states, you must consider the following points:
- A start and final state must exist for each entity.
- By default, the entities are created in the state defined as initial.
- The final state defines the end of the entity's flow of states because there can be no more state transitions.
- To fill in the remaining languages of the description, you must edit the state with a user with the language configured on its profile.
- To create or configure request states, select the entity “REQUESTS.REQUESTS”
Maintenance configuration for the Requests states
- Requests
- Start SLA– when active, when changing to this state, the SLA start date of the request is filled in;
- End SLA– when active, when changing to this state, the SLA end date of the request is filled in;
- Change WO state to – when active, when changing to this state, the associated WO is changed for the selected state;
- Start Down Time:
- If you define a state as Start Down Time, and there is no state defined as End Down Time the final request state is automatically defined as End Down Time.
- If a state is no longer defined as Start Down Time, and there are no states defined, all Request states are no longer defined as End Down Time.
- It is not possible do set the Final state with Start Down Time if there are not one or more states defined with End Down Time. This means that the final state will be defined automatically with End Down Time and it is not allowed to have a defined state with Start and End Down Time
- End Down Time:
- If you define a state as End Down Time, and there are no states defined with Start Down Time, the start Request date will be automatically defined as Start Down Time.
- If a state is no longer defined as End Down Time, and there are no states defined, all Request states are no longer defined with Start Down Time.
- It is not possible to set the Start state with End Down Time if there are not one or more states defined with Start Down Time. This means that the start state will be defined automatically with Start Down Time and it is not allowed to have a defined state with Start and End Down Time
- Copy Reason between technicians
- when changing to this state, the justification is copied (feedback) inserted in the connected WO.
Related Articles
How to change the state transition dates of a request?
The state transition dates can be changed, for that select the option Work | Work | Request Management The request list is presented Select the request you wish to change the state to On the "Operations" link, select the option "Change State ...
How to set up the contract workflow?
The state flow for contracts can be changed to be in line with the organization's working method. To create or change the configurations for a new state, you must access Settings | Contracts | Workflow; 1. The state list is presented; 2. To create ...
How to create a request type?
After being configured, the request types allow you to classify requests and apply specific behaviors. To create a request type, select the option Settings | Requests | Request Types: The list of request types is displayed; Press the "Create" button. ...
How to configure the work order workflow?
The state flow for work orders can be changed to be in line with the organization's working method. To create or change the new state configurations, you must access Definitions | Work | Workflow The state list is presented; To create new states, ...
How to view the state transitions of a request?
A request is created in the initial state and until it is finished, it goes through different states. The requester or the maintenance manager has the chance to view all the states the request went through. For the requester to view the request ...