English Boards > V3 Development

Automation Command Values

(1/2) > >>

JohnS:
Emre,

Not sure if this is by design, but if I have an Automation Button set with the following values and tick Toggle Values
Course 1
Course 2
Course 3
Course 4

The Button will show 'Course 1' but when you click the button it changes to 'Course 2' and the value is sent as 'Course 2'.

Should it not send 'Course 1', which is what the button is showing, not what the next value is?

emre:
Yes when thought that makes more sense but I can't remember for what case I've implemented that. I'll check my notes.

sukasem:
Tried to do this as well but I want to click which course first then when order added to ticket read that Automation Command Value but it doesn't work. I change rule New Order Added to Ticket and add update course action to the rule. No course tag. I have to select order line then click Course button then orders will have course state.

JohnS:
If you want to select course first, then Ticket Tags would be better.

sukasem:
I can't figure out easy way to use ticket tag as order state. What I do as set Automation Command button with Visibility->Ticket.
I set New Order Add To Ticket to update Course state to [:CommandValue]. When order added, there is no Course state attach to the order but whenever I click Automation Command Button the Course state display but again, every order will update to the last Automation Command Button.

So, I think when I put [:CommandValue] for Course state, it does pass it as Variable, not the Value read from command button. So whenever I click the button, the previous order that set to course 1 become course 2 and so on.. It's not fixed.

It will work just fine in Order Line mode since (I think) It does pass the Value (even we put State=[:CommandValue]) at the time we click the button.

Navigation

[0] Message Index

[#] Next page