Forced to have only one Task Action Field

  • 16 September 2007
  • 3 replies
  • 0 views

Badge +8
Question - it seems that you can only have one task action field in a process.  I have a process that has two levels of approval after submission and in my InfoPath form's data source I have a data element for each approval.  Lets say manager 1 and manager 2 (I am keeping this simple).  On the first client event the task action field to the Manager 1's approval data element.  Then I go to the second client event and set the task action field to Manager 2's approval data element.  Then when I go back to the first client event the task action field has been changed to Manager 2's approval data element.  What would this be occuring?

Thanks,
Jason

3 replies

Badge +9

Hi Jason,


I did a quick test and I believe the limitation is restricted to per view.  You can still use different task action fields as long as they are in different views.

Badge +8

I have a different view from each manager and this behavior was happening.

Badge +9
That is strange, it only happened to me when I used the same view.  Using different views was fine with different task action fields.  Is this a complex form or does it just happen with a simple form with 2 views and 2 fields?

Reply