Process definitions - Field evaluations for multi-select fields

RE: Process definitions - Field evaluations for multi-select fields

Jacquelyn Lane — Thu, 16 May 2019 21:32:53 GMT

Aaron, we utilize the following workaround:

- Create a hidden checkbox field for each multi-select value that needs to trigger a workflow

- The checkbox contains the following calculated value formula, which toggles the checkbox to "true" if the relevant multi-select value is added: ifElse(contains($mutli_field_c,"Multi Value"),true,false)

- A true value in the check box is then used to trigger the start event in the workflow

Hope that helps.

RE: Process definitions - Field evaluations for multi-select fields

Aaron Riley — Thu, 16 May 2019 08:53:13 GMT

I am looking for exactly the same functionality within one of my own definitions. As Scott mentions above, it will only start if I have only one option in each section of the divergent gateway. I can workaround this, but it will make my workflow much less simple to manage going forward. Does anyone know if an enhancement has been logged for this? If so, its getting a +1 from me.

RE: Process definitions - Field evaluations for multi-select fields

Scott Oldfield — Sat, 17 Mar 2018 17:00:47 GMT

I came here with a similar question to the OP. I've got a multiselect question and like to kick off a process when one of the items is selected, but the process will only kick off it it's the ONLY one selected. There is no "includes" option in the module field evaluation, only "is" or "is not". Unfortunately, I don't know enough about coding within Sugar to go down that route at this time.

RE: Process definitions - Field evaluations for multi-select fields

Francesca Shiekh — Wed, 03 Jan 2018 16:10:27 GMT

If the field is a multi-enum you should have contains and not contains options.

See: clients/base/filters/operators/operators.php

$viewdefs['base']['filter']['operators'] = array(

'multienum' => array(

'$contains' => 'LBL_OPERATOR_CONTAINS',

'$not_contains' => 'LBL_OPERATOR_NOT_CONTAINS',

'enum' => array(

'$in' => 'LBL_OPERATOR_CONTAINS',

'$not_in' => 'LBL_OPERATOR_NOT_CONTAINS',

'$empty' => 'LBL_OPERATOR_EMPTY',

'$not_empty' => 'LBL_OPERATOR_NOT_EMPTY',

I assume your "Field" dropdown is an enum so it's using the enum operators.

By default something like what you have in the image would be trying to filter the "Field" not that fields' values

I suppose you could try to force the "Field" to be a multienum or define your own field type with its own operators.

It's not very clear to me how you are filtering that field's values as opposed to the filed names.

If instead you were to filter things at code-level:

multiselect values are encoded into a string where the values are comma separated and delimited with a ^

For example: if you select A and C the value of the field in the database will be the string:

^A^,^C^ or possibly ^C^,^A^ depending in which order you selected them.

There are functions to decode and encode multienums

See include/utils.php

function unencodeMultienum($string)

and

function encodeMultienumValue($arr)

unencodeMultienum('^A^,^C^') will give you an array with two values: A and C

So you can unencode the value of the multienum and then check the array values for the relevant criteria.

HTH,

FrancescaS