Opened 7 years ago

Closed 7 years ago

# Use saved form field value in subsequent triage workflow

Reported by: Owned by: canh.tran@… Eli Carter normal AdvancedTicketWorkflowPlugin normal 0.11

I set up triage workflows based on custom field values. I have one custom field value being used for 2 different triage workflows. I wonder if the form field value can be used to automatically go to the 2nd triage condition without going through this triage to recheck the value of field again.

Here is the example:

Ticket form has custom field

Engineer Manager Approval Yes/No

Triage workflow:

engmgr_pre_approve.name = Check if Engineer Manager Pre-Approval Needed
engmgr_pre_approve.operations = triage
engmgr_pre_approve.triage_field = engmgr_approve
engmgr_pre_approve.triage_split = Yes->do_pre_approval, No->implementation
...
engmgr_approve.name = Check if Engineer Manager Approval Needed
engmgr_approve.operations = triage
engmgr_approve.triage_field = engmgr_approve
engmgr_approve.triage_split = Yes->do_approval, No->next_step


If Engineer Manager is Yes, I can go through step "Check if Engineer Manager Pre-Approval Needed" but I should automatically go to do_approval step.

### comment:1 Changed 7 years ago by Eli Carter

Description: modified (diff)

### comment:2 follow-up:  3 Changed 7 years ago by Eli Carter

I'm sorry, but I don't understand what you are trying to accomplish here. Can you provide more of the workflow configuration so I have more context to understand this?

### comment:3 in reply to:  2 ; follow-up:  4 Changed 7 years ago by anonymous

I'm sorry, but I don't understand what you are trying to accomplish here. Can you provide more of the workflow configuration so I have more context to understand this?

I have a sequence of workflows based on form field's values. Since you know these form field's values, I shouldn't be prompted to submit to see if field A's value is Y, then do this. If value is N, do that. I want to be directed the next state without clicking submit to verify field A's value.

### comment:4 in reply to:  3 ; follow-up:  5 Changed 7 years ago by Eli Carter

I have a sequence of workflows based on form field's values. Since you know these form field's values, I shouldn't be prompted to submit to see if field A's value is Y, then do this. If value is N, do that. I want to be directed the next state without clicking submit to verify field A's value.

The workflow code isn't going to automatically trigger a second action. It sounds like you need to move your triage operation to the previous action so you can move directly to the state you need based on that field's value.

### comment:5 in reply to:  4 ; follow-up:  6 Changed 7 years ago by anonymous

I have a sequence of workflows based on form field's values. Since you know these form field's values, I shouldn't be prompted to submit to see if field A's value is Y, then do this. If value is N, do that. I want to be directed the next state without clicking submit to verify field A's value.

The workflow code isn't going to automatically trigger a second action. It sounds like you need to move your triage operation to the previous action so you can move directly to the state you need based on that field's value.

The pre-approval step (#1) and approval step (#2) are 2 different states happenning at 2 different times. If I move 2nd triage to the 1st triage, how do I set that up to ensure proper execution sequence ?

### comment:6 in reply to:  5 ; follow-up:  7 Changed 7 years ago by Eli Carter

The pre-approval step (#1) and approval step (#2) are 2 different states happenning at 2 different times. If I move 2nd triage to the 1st triage, how do I set that up to ensure proper execution sequence ?

If they happen at two different times, then why are you complaining about having two actions? It seems like that's what you would want.

I really need a fuller explanation of what you are trying to accomplish. I'd suggest attaching the complete workflow you are currently using (and since you are using custom fields, that part of your config, too), and explain what series of actions you are currently taking, then explain what the change is that you want to accomplish and why you can't get it to work.

### comment:7 in reply to:  6 Changed 7 years ago by anonymous

The pre-approval step (#1) and approval step (#2) are 2 different states happenning at 2 different times. If I move 2nd triage to the 1st triage, how do I set that up to ensure proper execution sequence ?

If they happen at two different times, then why are you complaining about having two actions? It seems like that's what you would want.

I really need a fuller explanation of what you are trying to accomplish. I'd suggest attaching the complete workflow you are currently using (and since you are using custom fields, that part of your config, too), and explain what series of actions you are currently taking, then explain what the change is that you want to accomplish and why you can't get it to work.

Sorry I'm not allowed to post detail of trac.ini from work. There is nothing wrong with the way the triage works. My setup works too but I'm looking for perhaps an option to execute different path for this plugin based on programming logic.

Let say there a list of states to go through. Some must go no matter what. Some are based on field values.

state_1 state_2 if (field1_value == 'Y') state_3 state_4 if (field1_value == 'Y' && field2_value == 'Y') state_5 ...

I'm just thinking of different ways of doing things. If you don't think this is a good idea, please close the ticket. Thanks.

### comment:8 Changed 7 years ago by Eli Carter

Resolution: → wontfix new → closed

I think if you're looking for that level of customization, it makes more sense to write that logic in a plugin that is specific to your case, rather than trying to extend the more generic operations.

### Modify Ticket

Change Properties