Route change requests by the rules — no manual triage

The scenario pulls in change requests, sorts them by risk level and creates tasks, notifies the responsible people and keeps a log.

  • Sorts requests by risk level on its own
  • Creates tasks in the tracker
  • Notifies the right people on the right channels
  • Keeps a change log in a table
Set it up for yourselfScriptera

How it works

To get oneC notifications in exolve, you don't need a developer: a ready-made scenario watches events and sends messages for you.

  1. Starts when: Schedule Trigger
  2. Then: Get many items
  3. Then: Edit Fields
  4. Check: Route by Risk Level
  5. If yes: Notify Stackholder Pending Request
  6. If no: Route Low Risk by Component
  7. If yes: Create an issue
  8. Then: Notify Stackholder Approval Request
  9. Then: Send a message
  10. If yes: Append or update row in sheet
  11. If no: Route High Risk by Component
  12. If yes: Resubmission Request

You can launch this oneC + exolve integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios