V3: Internal debug system to investigate states and their workflow

Version 4 V4 Question
4

Hello @niceguy thank you very much for the suggestions. What you’ve requested sounds great however it might take a while until we find enough free time to implement that.

I generally use Show Message action to ensure I can capture correct state change event.

I agree our documentation is not complete but I believe state tracking is not hard to understand as it seems. As new feedbacks comes I can update state documentation to cover more topics or give better examples.

Let me give an example…

States works like traffic lights. It can be red, yellow or green. There are two things you can do with states.

  1. You can handle the moment it changes from red to yellow or yellow to green with Ticket State Updated rule and execute specific actions to handle that change.
  2. You can display specific buttons for specific states. For example you can display “double horn” button when “state” is “red”

So you can create a new state called Delivery Status and have it two states such as Waiting and Delivered. You can:

  1. Display Deliver button when Delivery Status is Waiting.
  2. When Deliver button clicked you can change ticket state to Delivered.
  3. When Delivery Status changes from Waiting to Delivered you can execute an action that sends e-mail or sms message to customer.

If you ask the point you don’t understand I can try to give more specific example. We can talk about it under What does State mean? topic .

2 Likes