In 16.1.1 release, the business rules were enhanced to allow setting a field based on another field. However, when a static dependent lookup is selected as the "targeted attribute " no values display in the condition. I tried this with different static dependent lookups and the result was the same. I let it sit for over 4 minutes, so if it is a performance lag, then that must be fixed too (this used to be an issue when these lookups were first put into the application)
The value in the screenshot uses the OOTB lookup ID = INV_TYPE and is the OOTB field "stage".
STR:
1. In studio, add a new lookup attribute (invlkp) to the project object and use the static dependent lookup (Investment Type - INV_TYPE)
2. Go back into MUX and add a rule of type "Attribute Update" and select "invlkp" as the target attribute
Expected: When you try to add a condition, the drop down loads the options
Actual: When you try to add a condition, the drop down loads nothing and you are given a console error
Release : 16.1.1
DE68621, Fixed in 16.1.2 and also targeted for patch 16.1.1.1.
Additional information about the feature is here Set Field Values Based on Another Field