L3 - Default Environment (Required on creation):
Camunda Platform 7.18.0
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):
// GIVEN
- When defining a form with a multi-select component that has static options (cf. attached screenshot)
- AND a to-be-bound variable of type Json or Json serialized Object is yet not created in C7
// WHEN
The form is submitted.
// THEN
- A new variable is created that contains the user selection, but the wrong type String is assigned.
- Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON.
Steps to reproduce (Required on creation):
- Deploy the attached form and BPMN model
- In Tasklist, start a process instance, make a selection, and click the "Start" button
- In Tasklist, navigate to the created User Task
Observed Behavior (Required on creation):
The previously entered data is not reflected in the form.
Expected behavior (Required on creation):
The previously entered data is reflected in the form.
Root Cause (Required on prioritization):
The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a valuesKey.
Solution Ideas (Optional):
Create a Json-typed variable for multi-select types, that form definition has static options.
Hints (optional):
-
This is the controller panel for Smart Panels app
[CAM-14926] In Camunda Forms, variable of type String instead of Json created for multi-select types with static options
| Attachment | New: image-2022-10-06-14-48-22-942.png [ 55175 ] | |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When defining a form with a multi-select component that has static options and a to-be-bound variable of type Json or Json serialized Object is yet not created in C7, String is assigned as type. Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
New:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When defining a form with a multi-select component that has static options and a to-be-bound variable of type Json or Json serialized Object is yet not created in C7, String is assigned as type. Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. !image-2022-10-06-14-48-22-942.png|thumbnail! h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
| Attachment | New: Screenshot 2022-10-06 at 14.48.46.png [ 55176 ] | |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When defining a form with a multi-select component that has static options and a to-be-bound variable of type Json or Json serialized Object is yet not created in C7, String is assigned as type. Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. !image-2022-10-06-14-48-22-942.png|thumbnail! h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
New:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When defining a form with a multi-select component that has static options and a to-be-bound variable of type Json or Json serialized Object is yet not created in C7, String is assigned as type. Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. !Screenshot 2022-10-06 at 14.48.46.png|thumbnail! h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
| Attachment | Original: image-2022-10-06-14-48-22-942.png [ 55175 ] |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): When defining a form with a multi-select component that has static options and a to-be-bound variable of type Json or Json serialized Object is yet not created in C7, String is assigned as type. Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. !Screenshot 2022-10-06 at 14.48.46.png|thumbnail! h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
New:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): // GIVEN * When defining a form with a multi-select component that has static options ** !Screenshot 2022-10-06 at 14.48.46.png|thumbnail! * AND a to-be-bound variable of type Json or Json serialized Object is yet not created in C7 // WHEN The form is submitted. // THEN * {{String}} is assigned as type. * Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): // GIVEN * When defining a form with a multi-select component that has static options ** !Screenshot 2022-10-06 at 14.48.46.png|thumbnail! * AND a to-be-bound variable of type Json or Json serialized Object is yet not created in C7 // WHEN The form is submitted. // THEN * {{String}} is assigned as type. * Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
New:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): // GIVEN * When defining a form with a multi-select component that has static options !Screenshot 2022-10-06 at 14.48.46.png|thumbnail! * AND a to-be-bound variable of type Json or Json serialized Object is yet not created in C7 // WHEN The form is submitted. // THEN * {{String}} is assigned as type. * Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): // GIVEN * When defining a form with a multi-select component that has static options !Screenshot 2022-10-06 at 14.48.46.png|thumbnail! * AND a to-be-bound variable of type Json or Json serialized Object is yet not created in C7 // WHEN The form is submitted. // THEN * {{String}} is assigned as type. * Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
New:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): // GIVEN * When defining a form with a multi-select component that has static options (cf. attached screenshot) * AND a to-be-bound variable of type Json or Json serialized Object is yet not created in C7 // WHEN The form is submitted. // THEN * {{String}} is assigned as type. * Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
| Description |
Original:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): // GIVEN * When defining a form with a multi-select component that has static options (cf. attached screenshot) * AND a to-be-bound variable of type Json or Json serialized Object is yet not created in C7 // WHEN The form is submitted. // THEN * {{String}} is assigned as type. * Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
New:
h3. Environment (Required on creation):
Camunda Platform 7.18.0 h3. Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket): // GIVEN * When defining a form with a multi-select component that has static options (cf. attached screenshot) * AND a to-be-bound variable of type Json or Json serialized Object is yet not created in C7 // WHEN The form is submitted. // THEN * A new variable is created that contains the user selection, but the wrong type {{String}} is assigned. * Camunda Forms cannot display the data entered by the user since the variable is not parsed to JSON. h3. Steps to reproduce (Required on creation): # Deploy the attached form and BPMN model # In Tasklist, start a process instance, make a selection, and click the "Start" button # In Tasklist, navigate to the created User Task h3. Observed Behavior (Required on creation): The previously entered data is not reflected in the form. h3. Expected behavior (Required on creation): The previously entered data is reflected in the form. h3. Root Cause (Required on prioritization): The implementation only creates a Json-typed variable for dynamic multi-select components, which form definition has a {{valuesKey}}. h3. Solution Ideas (Optional): Create a Json-typed variable for multi-select types, that form definition has static {{options}}. h3. Hints (optional): - |
| Attachment | New: static-component-options.bpmn [ 55177 ] | |
| Attachment | New: static-component-options.form [ 55178 ] |