Custom Pre/Post Workflows on Ticket Lifecycle
You can now trigger specific Rocketship Workflows immediately before or after an action is executed during a Ticket Status change.
How it works:
When configuring your LifeCycle rules, you will see two new dropdown fields under the Custom Workflows section:
Custom Pre-Workflow: Runs before the primary LifeCycle action.
Custom Post-Workflow: Runs after the primary LifeCycle action is completed.
How to Access the Custom Workflows
To set up your Pre and Post Workflows, follow these steps:
Navigate to Ticket LifeCycle.
Choose a Ticket Status that you wish to modify.
Click Edit
Scroll to the bottom of the configuration page, where you will find the Custom Workflows section to select your inputs.
Related Articles
Ticket LifeCycle Filters
The Ticket LifeCycle Filters allow you to precisely control when automated actions—such as auto-scheduling, auto-closing, or starting next steps are triggered. By applying these filters, you ensure that LifeCycle events only occur for specific ...How to View Ticket History and Notes in the Rocketship Dashboard
How to View Ticket History and Notes in the Rocketship Dashboard Follow these simple steps to view the ticket details: Go to Rocketship Dashboard Enter the Ticket Number on the left-hand side View Ticket Details Access Ticket History/Notes Review ...Autotask API Ticket Description Error on Ticket Update
Sometimes Rocketship can’t update an Autotask Ticket. When this happens, the Autotask API returns an error. We usually log that error to the ticket. Example: { "status": 37, "id": 67706, "httpCode": 500, "response": { "errors": [ "String value ...How to Clone a Ticket in Autotask
You may need to clone tickets in Autotask, whether for your own use or perhaps this is a request by Giant Rocketship’s support team when troubleshooting a support request. To clone a ticket, you can use the built-in tool for this provided by ...Rocketship Ticket Insight Returns an Error
You may see errors in the Ticket Insight in Autotask where Rocketship fails to read the ticket, as shown below.. The primary reason this occurs is that Rocketship does not “see” the ticket because its API user does not have the correct permissions. ...