Ver 7.10.10 to 7.10.36 workflows that create records default fields to first var in list

LJ-UK · 11 December 2022 21:43

Hmmm. Seems this is related to:

github.com/salesagility/SuiteCRM

Workflow non-value fields ignored for 'Create Record' action

opened 01:48PM - 28 Oct 21 UTC

closed 04:17PM - 14 Mar 23 UTC

ghost

Type: Bug Priority:Critical Area: Workflow

#### Issue When editing a workflow which has a 'Create Record' action, any fiel…d which isn't a 'Value' is ignored when the form is submitted. #### Expected Behavior Fields which are not a 'Value' (i.e. 'Field' or 'Date') should be captured and stored correctly. #### Actual Behavior The form inputs are all being treated as if they are all 'Value' and passed through fixUpFormatting() which then returns a default value for them, not what was submitted. #### Possible Fix Lines 119-123 in modules/AOW_Actions/AOW_Action.php currently contains: ``` if ($post_data[$key . 'param'][$i]['value_type'][$p_id] == 'Value' && is_array($p_value)) { $param_value[$p_id] = encodeMultienumValue($p_value); }else{ $param_value[$p_id] = fixUpFormatting($params["record_type"], $post_data[$key . 'param'][$i]["field"][$p_id], $p_value); } ``` This modification works: ``` if ('Value' === $post_data[$key . 'param'][$i]['value_type'][$p_id]) { if (is_array($p_value)) { $param_value[$p_id] = encodeMultienumValue($p_value); } else { $param_value[$p_id] = fixUpFormatting($params['record_type'], $post_data[$key . 'param'][$i]['field'][$p_id], $p_value); } } else { $param_value[$p_id] = $p_value; } ``` #### Steps to Reproduce 1. Create a workflow with a 'Create Record' action 2. Add a field to copy over any existing field to the new relation 3. Save #### Context This should be high priority as there is no workaround and a risk of existing data getting corrupted. Creating a workflow with the assignment of fields isn't possible and editing an existing one just breaks it. #### Your Environment * SuiteCRM Version used: 7.11.22 * Environment name and version (e.g. MySQL, PHP 7): PHP 7.4 * Operating System and version (e.g Ubuntu 16.04): Debian 11

github.com/salesagility/SuiteCRM

Workflow, create record, not saving parameters

opened 09:00PM - 23 Mar 22 UTC

closed 09:36AM - 16 Aug 22 UTC

andresrom1

Type: Bug Priority:Important Area: Workflow

Hi everybody. I have one custom module, and also added some fields to Opportu…nities. When i save a new Opportunitie this workflow creates a record of custom module if reach certain conditions. In the “Actions” section of the workflow, I select Recod Type: {My custom module} and establish in each field what value or field it should have, as shown in the attached image. There is a particular field called “Monto cuota” (Currency type) in which I select the field that corresponds, and then save. But then I notice that that selection is completely cleared and I can’t assign the desired field to it. Same thing happens to a checkbox field. Can anyone give me some help on this? i’m running Version 7.12.5 in GCP by Bitnami #### Expected Behavior Save correctly the given parameters to the workflow #### Actual Behavior Parameters are not saved in the workflow #### Steps to Reproduce 1. Add to Opportunities module a currency field and a checkbox field 2. Create a new person type custom module 3. In the custom module create a currency field and a checkbox field 4. Relate both module one to many 5. Create a workflow that adds a record of custom module when new opportunitie is saved. #### Context Value in Opportunities currecny field should be saved in the custom module currency field Value in Opportunities clheckbox field should be saved in the custom module checkbox field High priority #### Your Environment i’m running Version 7.12.5 in GCP by Bitnami * Browser name and version: Chrome Versión 99.0.4844.82 (Build oficial) (64 bits) * Environment name and version PHP 7.4.28 * Operating System and version PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian Thanks! ![1](https://user-images.githubusercontent.com/33395068/159794803-1a426fcd-13ba-4efd-a97a-9ad203a8abcd.PNG)

Is this fix likely to work on 7.10.36:

Thanks