In Cloud Provisioning and Governance application, "SetValue" rule is evaluated after "TriggerChangeEvent" rule when loading the Stack's FormSummaryBusiness case: in Cloud Provisioning and Governance application, the customer is designing a stack that has pre-filled values in the parameter fields sent to Cloud Provider.The values should be loaded based on the following sequence:1) Dropdown A has some selected items.2) If we select different items from Dropdown A, then the value in Dropdown B should be changed accordingly.3) Depending on the Stack type, the selected item in Dropdown A after the form load should be a "fixed value". The user should not change it manually.Step 3 above can be achieved by using the "SetValue" rule. However, after the form load, the value in Dropdown B will not be changed according to the selection in dropdown A. If you change the selected item in Dropdown A manually, the value in Dropdown B is changed accordingly. This is not the expected scenario as a customer would like to grey out dropdown A and avoid the user's manual interaction.The reason: by design, the "SetValue" rule is evaluated after the "TriggerChangeEvent" rule during the form load. Solution: If you really want to force the user not to select other values, then instead of using "Lookup Select Box" to define the value in the dropdown, use the "Reference" type instead. You can then enhance the "Use reference qualifier" to get the value you want to display/select. Avoid using "SetValue" and "TriggerChangeEvent" rule.