Myndbend Process Manager (MPM) installs a number of triggers and targets when you first set it up. In this article, we'll go over what the initially installed triggers do. We'll break the triggers into two main categories - those that are active and ones that are inactive by default.
Active triggers are used by MPM for various purposes -- usually for what their name implies. They are active because MPM relies on them for certain parts of our app, although based on your settings, they may or may not be used. In all of the cases, they notify our servers to let them know they need to perform a certain action.
MPM Tag Parent Tickets
When there are child tickets, this trigger will get utilized to let our servers know that we should modify the tags on the parent ticket.
MPM Create Sequenced Tickets When Previous has been Solved/Approved/Partially Approved
This trigger is getting utilized if you are using the Sequenced Actions in Ticket Templates. When you set sequenced child ticket creation based on a certain actions (solved, approved, partially approved) in the template, these triggers will notify our servers to create the child ticket from the specified template.
MPM Initialize Sequenced Approval Process
This trigger is getting utilized if you are using the Sequenced Approvers feature of MPM. It will notify the server and queue up the list of approvers that will be added sequentially to the ticket.
MPM Process Sequenced Approvers
This trigger is getting utilized if you are using the Sequenced Approvers feature of MPM. It will notify the server when someone has approved the ticket so that we can add the next approver in the sequence.
MPM Complete Approval Sequence
If you are using Sequenced Approvers, this trigger gets called when the last approver in the sequence has approved or denied the ticket. When the final approval decision is captured, the ticket's approval status will be updated.
MPM Analyze Approval
This trigger is getting called each time ticket has been updated to ensure the approval status is updated. The MPM app that runs in the ticket sidebar will apply the latest approval status to the current ticket, however, if an agent doesn't view the ticket, the status will not be captured unless this trigger runs.
Note: We advise that you leave these triggers active as certain features of MPM may not work as expected if these triggers are not active.
Triggers that are Inactive by default
Inactive triggers are triggers that our users commonly use for setting up their flows, but will require updates, specific to your business process, before they can be activated.
MPM Create Child Tickets
This trigger used to generate child tickets automatically. You can read more about how to set this trigger up and how it works by clicking here.
MPM Add Approvers
This trigger is used to add approvers automatically. You can read more about how to set this trigger up and how it works by clicking here.
MPM has several other triggers/targets that can be installed, optionally, from the Advanced Config page in the Myndbend admin app (Myndbend circular icon on the left side of Zendesk). For example:
- Add approvers from Zendesk group
- Add approvers by email addresses
- Add approvers from user tags
- Remove approvers
- Update children tickets