-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Context:
When adding support for native JSON variables we altered the ObjectVariableService in a way that some object variables that do not have the appropriate JSON serialisation are still imported due to an incorrect if/else condition. This needs adjusted to exclude this type of variable from being imported.
This should also resolve the issue with UpgradeEsSchemaIT failing with an incorrect variable count.
AT:
- Optimize does not import non JSON serialized object variables
- This is asserted in IT
- UpgradeEsSchemaIT variable count assertion is reverted to equals rather than gte
For QA: This can be tested by checking that Optimize does not import any object variables that do not have the json serialisation type. The default engine processes come with a variable called "approverGroups" that is an example of this, or alternatively this can be tested with external variable ingestion.
This is the controller panel for Smart Panels app
[OPT-5923] Optimize wrongly imports non JSON object variables
| Rank | New: Ranked higher |
| Rank | New: Ranked higher |
| Rank | New: Ranked higher |
| Status | Original: Open [ 1 ] | New: In Development [ 10312 ] |
| Assignee | Original: Helene Waechtler [ helene.waechtler ] | New: Sebastian Bathke [ sebastian.bathke ] |
| Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
| Assignee | Original: Sebastian Bathke [ sebastian.bathke ] | New: Helene Waechtler [ helene.waechtler ] |
| Status | Original: In Review [ 10212 ] | New: Rework [ 11413 ] |
| Status | Original: Rework [ 11413 ] | New: In Development [ 10312 ] |
| Description |
Original:
*Context:*
When adding support for native JSON variables we altered the ObjectVariableService in a way that some object variables that do not have the appropriate JSON serialisation are still imported due to an incorrect if/else condition. This needs adjusted to exclude this type of variable from being imported. This should also resolve the issue with UpgradeEsSchemaIT failing with an incorrect variable count. *AT:* * Optimize does not import non JSON serialized object variables * This is asserted in IT * UpgradeEsSchemaIT variable count assertion is reverted to equals rather than gte |
New:
*Context:*
When adding support for native JSON variables we altered the ObjectVariableService in a way that some object variables that do not have the appropriate JSON serialisation are still imported due to an incorrect if/else condition. This needs adjusted to exclude this type of variable from being imported. This should also resolve the issue with UpgradeEsSchemaIT failing with an incorrect variable count. *AT:* * Optimize does not import non JSON serialized object variables * This is asserted in IT * UpgradeEsSchemaIT variable count assertion is reverted to equals rather than gte For QA: This can be tested by checking that Optimize does not import any object variables that do not have the json serialisation type. The default engine processes come with a variable called "approverGroups" that is an example of this, or alternatively this can be tested with external variable ingestion. |
| Mentioned Roles |
| Mentioned Groups |