Why aren't custom rules for variable and argument naming conventions added to an Automation OPS policy, reflected in UiPath Studio?
Issue Description
Custom rules for variable and argument naming conventions added to an Automation Ops policy are not reflected in UiPath Studio.
Root Cause
The issue occurred due to a mismatch between the parameter keys in the Automation Ops policy JSON file and the default keys that the Workflow Analyzer expects for recognizing custom rules. This mismatch is causing the rules to fail when accessed.
Example: From the screenshot below, the highlighted ones are the default parameter key names. If these are modified, they fail to reflect in UiPath Studio.
Resolution
Rename the parameter keys in the Automation Ops policy JSON file to align with the default keys expected by Workflow Analyzer. This resolves the mismatch, ensuring that the custom regex rules are correctly recognized and displayed in Studio.