Jump to content

Human Task Outcome Fields using Simple List populating with Default Display and not Value - need the ability to control whether Value (Raw) or Display stored in the field


Recommended Posts

Since @samwoo post back in December 2021, the behaviour of the use of Outcome Fields with simple list seem to have changed from inserting the 'Value' column to that of the 'Default Display' column. 

Can we request an enhancement request to have this configurable on the Human Task Outcome Field configuration to control whether the 'Value' or the 'Default Display' values are inserted in the variable when selecting from a simple list. This will allow use control at the variable level how we want it to be populated.

In our example of the moment we are want to use a simple list to allow the analyst to set the Resolution Category, for which we need to pass into the node a numeric value, so would want the 'Value' column from the simple list, not the human readable 'Display Value' (example below). However at the moment you get the latter textual value which you cannot use with the BPM node.

Cheers

Martyn

 

image.png.839f0f8873e8c8c75983db7c6570ae06.png

 

 

  • Like 1
Link to comment
Share on other sites

  • Martyn Houghton changed the title to Human Task Outcome Fields using Simple List populating with Default Display and not Value - need the ability to control whether Value (Raw) or Display stored in the field

Having set the Outcome Field to static list drop down and then back to dynamic drop down one, it now seems to be inserting the Value and not the Display Value from the simple list, so I am even more confused than before! :blink:

 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...