How can we help?

Articles in this section

See more

Status Workflows: Setting Up a Single-Level Approval Workflow

Ricky Cecchini
  • Updated

One of the most common use cases for Status Workflows is the single-level approval, where only one approver is needed to send the ticket on to the MSP to fulfill. 

Follow these best practices to get it set up properly.

If you require multiple steps in your approval process, please see this article. 

Step 1: Build Your Approval/Denial Flow

  1. Navigate to Partner > Settings > Status Workflows (on the right-hand column under Configuration)
  2. Select the +Add button at the top right to add a new Status Workflow
  3. Set up your approval flow:
    • For the Label, set it to Approve this Ticket or similar
    • For the PSA Status, set it to an approved status from your PSA
    • Select the checkbox for Log approval on selection

      mceclip0.png
       
    • If desired, fill out the Set Priority field to change the priority of the ticket as it's approved
      • As usual, this must be an existing priority in your PSA.
    • Under the section to Show when ticket has one of these PSA statuses set this to Waiting on Internal Approval (or whatever Status you want as your waiting status that's in the PSA)

    • For Visible only for users with Roles, drag Admins to the selected column and remove Everyone.
       

       
  4. Select Submit to finalize the options. 
  5. Repeat the exact same steps (1-3) for your Deny this Ticket status, with only the following changes:
    • Set the Label to Deny this Ticket or similar
    • For the PSA Status, set it to a denied status from your PSA
    • Select the checkbox for Log denial on selection

In the end, you should find yourself with two statuses (Approve this Ticket and Deny this Ticket) that are triggered by the same PSA status. 

 

mceclip3.png

Step 2: Set Your Default Approval Required Token

In order to expedite approvals in the future, it's a great idea to set up a token for your default (and typically initial) approval required status that you can quickly pop into tickets. This status is what will end up triggering subsequent approval flows, whether they're single-level or multi-level.

Here's how:

  1. Navigate to Partner > Settings > Tokens (on the right-hand column under Configuration)
  2. Find and edit the @DefaultApprovalNeeded token
  3. Set the value to your trigger status (case sensitive) - the status that triggers the Approve/Deny workflows we set up in Step 1. 
    • In our example above, this status would be "Waiting on Internal Approval"
  4. Select Submit to save your settings. 

mceclip2.png

 

Step 3: Mark Statuses as "Ticket Waiting"

You're on a roll - you've gotten the setup of the approval/denial statuses and you've set your token.

Now, you'll want to set your same approval trigger status as a "Ticket Waiting" status - this will ensure that CloudRadial will flag this status as needing attention, which will do the following:

  • Make the status appear orange in the Support > Support Tickets area (for better visibility)
  • Allow the ticket with the trigger status to show up under the Waiting tab (for better ticket organization)

To do so:

  1. Navigate to Partner > Settings > PSA (at the right-hand column, under Setup)

  2. Navigate to the Ticket Settings section and find the

     
  3. Enter in your status that triggers the approve/deny workflow
    • Once again, this is the "Waiting on Internal Approval" status, in our example

      mceclip0.png
       
  4. Select Submit at the bottom to save your settings. 

Now, tickets will be highlighted for better visibility.

 

mceclip1.png

Step 4: Set Your Tickets to Trigger Status Workflows

With all the steps above set, you can go about your portal usage as normal. When a ticket requires approval, you must trigger the approval process by invoking your status workflow. Here's how:

  1. Create a ticket in either the Problem Reports or Service Request areas
  2. On the Routing tab, find and check the Is approval and email notification required? box
    • This will notify the approvers that there's a ticket for approval in the portal.
    • It will also trigger the status workflow setting.

      mceclip2.png
       
  3. Set the PSA Status with your @DefaultApprovalNeeded token we created in Step 2
    • You can also simply write in the status as-is, without a token - but it's recommended to use a token for future flexibility.
    • Note: The @DefaultApproved status will be set if the checkbox for 'Approvers who submit their own requests?' is checked and the requestor is an approver. In effect it skips the 'Approval Needed' status because it is already approved.
  4. The Approver List, if left blank, will use the status workflow approvers we defined earlier.
    • Most choose to leave this section blank.
    • If you write in any specific email(s), the approval workflow will only notify those listed people.
  5. Select Submit at the bottom of the ticket to finalize your settings. 

Note: For status approval labels to appear on tickets, the approvers MUST be listed in the Aprover list, whether via comma separation or token. 

All set! Now that your approval statuses are set up, you only need to repeat step 4 for any tickets that require approval. 

HaloPSA Workflow Support

Approve, Mark Resolved, and Escalate workflow actions are fully supported for HaloPSA tickets. Status and priority updates are applied immediately in Halo when a workflow action is triggered from the portal.

Key details for HaloPSA:

  • When a ticket is resolved through the portal, the closed-ticket flag (Hasbeenclosed) is set correctly in HaloPSA
  • If a workflow action fails (ticket not found, invalid status, API failure), a clear error message is returned to the user
  • Workflow actions use the same status workflow configuration as other PSAs - no Halo-specific setup is required beyond the standard integration

Related articles

Comments

0 comments

Article is closed for comments.