Details
-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Description
What is the desired functionality that you are missing?
In the Optimize configuration, I can configure if variables of type "object" are imported to Optimize.
Eventually it would be nice to allow the user to distinguish between different object types, e.g. XMLs or JSONs are eventually fine to request, but not Files - in the end it depends on use-case at the customer.
Which problem are you going to solve with this functionality?
Currently Optimize requests all variables from the engine (including complex objects).
Some objects can be very large (e.g. large XML, JSON documents or even Files?) and this leads potentially to issues with the import - or at least slows down the import - even if it would not be necessary.
Additionally in Cloud Environments users usually pay for ingress and egress a lot of money and wasting "traffic" is a bad practice because of this.
AT:
- Optimize should still Fetch complex/object variables and their value by default, because:
- non-breaking change => existing customers with complex variable plugins don't need to change the config
- if customers want to save overhead they can now opt for deactivating it
- the log message: "Refuse to add variable [locationDetails] from variable import adapter plugin. Variable has no type or type is not supported" should get improved towards stating which type the ignored variable has.