Maintenance
Update incident
Updates an existing incident: status, priority, affected resource, dates and costs.
At a glance
Link to this section: At a glance| Property | Value |
|---|---|
| Domain | incidents |
| Group in the editor | Maintenance › Incidents |
| Runs as | The owner of the workflow, with their permissions |
| Permission | Edit access to Incidents. Administrators always pass; a module outside the plan blocks everyone. |
| Add-on | Maintenance |
| Destructive | No: the public MCP catalogue does not mark it as destructive |
| Also available in | REST API, MCP (filmo_incidents_update) |
Inputs
Incident
Incident type
Available options: damage, loss, malfunction, cosmetic, theft, custom
Available options: draft, open, waiting, repairing, complete, lost
How urgently it has to be handled.
Available options: urgent, high, medium, low, none
The incident's impact. With «High» it appears in the escalation views.
Available options: low, high
Internal if you repair it yourselves; external if it is sent to a supplier.
Available options: internal, external
While the incident is open, the resource cannot be reserved on new orders.
How many units of the item are affected. Only for bulk items.
Limits: max 10000
Owners
Limits: advanced
Deadline
Limits: advanced
Limits: advanced
Limits: advanced
Limits: advanced
Estimated repair cost
Actual repair cost
The cost will be passed on to the customer on the source order.
**Source order.** The order in which it was detected. If you give it, the incident inherits that order's project.
Limits: advanced
Project
Limits: advanced
Outputs
Was this page helpful?