Using Rules

process for using rules there are three high level steps for using rules these are (1) generate rule opportunities, (2) analyze rules, (3) configure rules these are described below generate rule opportunities rules generation parses your imported rpa code and surfaces opportunities for each rule category for example, every custom action blueprint detects, or every unresolved reference found during generation even if you don't configure any of these rules, the lists are useful for planning and estimating a migration you can generate rules from either the rules table or the rules wizard to generate from the rules table click the advanced dropdown in the top right, then select one of generate project rules generates rules for a selected folder or subfolder within your current scope generate rules (bulk) generates rules across multiple blueprint projects in their entirety in the modal that opens, configure the two additional settings at the bottom instance scope when enabled, generated rules apply to all exports across your instance when disabled, rules are scoped to the current project only calltrees with mains only limits rule generation to call trees that include a main process analyze rules generated rule opportunities are disabled by default you need to analyze and decide which ones if any you'd like to configure and enable for use during export rules with many occurrences are usually worth configuring, because the effort to set up the rule can be much less than fixing each occurrence by hand in pad for example, say blueprint reports a custom action used 1,000 times if you don't configure a rule for it, your pad flow will have 1,000 "todo" comments, each of which you'll need to fix manually configuring the rule once and applying it during export resolves all 1,000 automatically on the other hand, if a custom action is used only once, it's faster to fix it directly in pad than to configure a rule you're able to analyze rules using the rules table (see description below) configure rules once you've decided which rules to use, configure each one and enable it for export each rule type behaves differently and requires specific information to work see the table below for details user interfaces in the process as described in the introduction to rules article the three rules user interfaces offer different capabilities the table below summarizes what is possible for each step in each of the user interfaces user interface step 1 generate rules step 2 analyze rules step 3 configure rules rules table all aspects of rule generation can be performed from the rules table this includes generating rules for any folder within a project, for an entire project, or for multiple projects (bulk) details on frequency of rule occurrence and specific processes and steps of the occurrences are available in the rules table the majority of rules configurations can be performed in the rules table rules csv na na any possible rules configuration can be performed using the rules csv rules wizard rule generation for the entire project is the only option in the wizard when initiating the rules wizard if the project has changed since rules were last generated blueprint will ask if you'd like to re generate the rules for the project na rules configuration for only three types of rules can be performed (reuse, unresolved references, queues) guidance is provided to help configure, and live pickers are provided to choose flows, subflows, and queues rule types different rule types are used to resolve the various cases where blueprint is unable to convert these are summarized in the table below for each it is also indicated whether blueprint is able to automatically find and list rules within the source rpa code for each rule type and rpa tool ("auto generated") rule type resolve from uipath resolve from blue prism resolve from a360 custom actions unmapped actions missing compiled libraries (custom actions) custom classes from dll assemblies auto generated yes unmapped actions missing vbo actions custom classes from dll assemblies auto generated yes unmapped actions custom classes from dll assemblies auto generated yes reuse duplicate or reused xamls across multiple calltrees auto generated yes duplicate or reused pages across multiple calltrees auto generated yes duplicate or reused taskbots across multiple calltrees auto generated yes unresolved references missing xaml references (i e invoke workflow) note may be due toby referencing workflow using a variable auto generated yes missing page references auto generated yes missing bot files or dependencies variable/expression references to bot files or dependencies auto generated yes work queues queue references auto generated yes queue references auto generated yes na environment variables na define flow variable for environment variable and initialize it auto generated yes na code replace apply common repairs to todos/errors across entire estate replace code with different code auto generated no apply common repairs to todos/errors across entire estate replace code with different code auto generated no apply common repairs to todos/errors across entire estate replace code with different code auto generated no