In short: the "not-optimized" warnings shouldn't be too much of a concern for you as a Strategy designer, if the "Set Property" feature is not used by the Decision Table rule.
We are continuously converting more shapes into the optimized engine - hence the "not-optimized" warnings about components are just indications that our progress hasn't reached that component type yet.
Posted: 1 year ago
Updated: 1 year ago
Posted: 20 May 2022 4:33 EDT Updated: 20 May 2022 4:35 EDT
I want to update this issue. I've solved the issue by changing the function in one of the decision table that I created. I replaced the empty property checks from "!=" into "PropertyhasValue()" function.
Also, this is the link that might be helpful related to global optimized strategies: