Workflow Analyzer settings

I need to update the workflow analyzer settings for all the existing projects. Are the workflow analyzer settings saved in a file locally in the project?


UiPath Studio does not natively provide a built-in feature to universally apply Workflow Analyzer rules to all projects across the entire environment automatically. Workflow Analyzer rules need to be applied on a per-project basis within UiPath Studio.

To configure Studio to export the results of each workflow analysis to the project folder, go to Studio Backstage View > Settings > Design and enable the Export Analyzer results option.

When this option is enabled, the results of each workflow analysis are saved in the \.local\.analysis\ subfolder of the project folder in a file named with the timestamp of the analysis followed either by project_analysis_results.json (when the Analyze Project option is used) or file_analysis_results.json (when the Analyze File option is used).

Note : The .local folder is hidden. You can enable viewing hidden items from the Windows File Explorer settings.

Hope it helps!!


If you want to update the Workflow Analyzer settings for all existing projects, you would need to open each project individually in UiPath Studio, navigate to the Workflow Analyzer settings, and make the necessary changes.

rules are generally locally stored in the userprofile folder under app data/UiPath/ruleconfig file…please check the same

also there is automation ops where centrally we can configure as well

Hope this helps


Hi ,

Would you be able to explain in more detail about the requirement?

Are you trying to ensure that existing projects also are analyzed and validated per rules to ensure a consistency across projects in terms of rules?

Please note that to apply rules to the projects doesn’t mean attaching/mapping rules file to the project.

Here is how it works:

  1. to apply rules to project means to have certain set of rules enabled against which your project would be validated and be made compliant.

  2. rules can have different levels of restrictions, you can either choose to have strict rules which should not be bypassed in any case and then are few warning rules which is just kind of info and it’s really up to the user to decide whether they would want to make changes to their project per those rules, so basically these set of rules can be bypassed even if enabled.

  3. So to apply rules to existing projects you would need to open each and every project in your studio once you have enabled rules.

  4. then analyze your project against those rules, correct the errors highlighted by rules and the proceed with publishing again.

  5. there is a catch in step 4 here. User can choose here if rules analysis should be a mandate before publishing each project. Now here also there are different routes possible, either you can choose to give this control to developer or you can choose to keep it with the orchestrator admin. I can explain about this in detail if needed.

As I said in my reply in your another post regarding workflow analyzer, this enablement really depends on at which level you are trying to apply rules.

So if you can explain me the end goal for these queries, I would be able to assist you accordingly.

Hope it helps.


Thank you for your great information!

Thank you. That is very helpful. I found the ruleconfig.jason file. And found out the workflow analyzer settings are machine based. We are still using local studio to develop our projects. So that means we can distribute the updated rule config file to everyone in the team.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.