Power DevBox Docs
  • Power DevBox
  • Getting Started
    • Install Chromium Extensions
    • Access Web App
    • Power Platform Connector
    • Visual Studio Code Extension
  • AutoReview
    • AutoReview - Chromium Extension
    • AutoReview - App
    • AutoReview - Power Platform Connector
      • Using Connector
      • Info (v1 & v2)
      • JSON (v1 & v2)
      • File (v2)
      • Diagam (v2)
      • HTTP
      • File (v1)
    • AutoReview - VS Code Extension
    • API
      • V1
        • Information API (v1)
        • Data API (v1)
        • Files API (v1)
      • V2
        • Information API (v2)
        • Data API (v2)
        • Files API (v2)
        • Diagram API (v2)
    • Menu
    • Files
      • Review
      • Report
      • Diagram
      • Exceptions
      • Solution
      • Compare with Previous
      • CSV Files
    • Configs
      • Complexity
        • Complexity Default Values
        • Complexity Template
      • Naming Convention
        • Naming Convention Default Value
        • Naming Template
      • Ratings
        • Ratings Default Value
        • Ratings Template
      • Scoring
        • Scoring Default Values
        • Scoring Template
    • Data JSON
  • V2 / V3.2.0 Update
  • AppReview
    • AppReview - Chromium Extension
      • Known Bugs/Limitations
      • Report Sections
      • App Settings
      • Components
      • Variables
      • Code Block
      • Solution
      • Connections
      • Data Source
      • Diagram
      • Flags
  • Flow Utilizer
    • Flow Utilizer - Start
    • Install
    • Flow Screen
      • Flow Tags
      • Solution Download
    • Solution Screen
    • Charts
    • Account
      • Account Download
  • Dev Tools
    • Power DevBox Chromium Extensions
      • Exception
      • Share
        • Share Demo Videos
      • Shortcut
      • Utility
        • Classic UI Clipboard
        • New UI Clipboard
        • Utility Demo Videos
Powered by GitBook
On this page
  1. AutoReview
  2. Configs

Complexity

The Complexity is a value set to give higher weights to certain connectors. As certain connectors use more api calls or require higher technical understanding to debug.

Negative values can be given, in default scopes are given negative values as they help make the flow more organised and easy to debug

The connection information can be seen in the definition file, this information is then used in the config file.

Example

 "type": "OpenApiConnection",
    "inputs": {
        "host": {
        "apiId": "/providers/Microsoft.PowerApps/apis/shared_excelonlinebusiness",
        "connectionName": "shared_excelonlinebusiness_1",
        "operationId": "GetItems"
        },

The information above can be found in your flows definition file. AutoReview has an export definition feature so you can see your flows definition.

There are 3 levels to the scoring

1. Action specific

If you have a particular action you want to score e.g. SharePoint get_items, then you need to set the name as 'operationId' & 'connectionName' (this is because different connections share same operation e.g. bot excel and SharePoint have GetItems opertionId).

In the example you would set the name to 'GetItemsshared_excelonelinebusiness' (the '_1' should be ignored, as this is a reference to a connection reference as the example is in a solution).

Action specific should be the top of the array, as AutoReview will pick the first found, and if its below a Type it will return the type complexity score instead.

2. Type

So in the above example the name would be 'OpenApiConnection'

3. Default

If a Action Specific value or Type cant be found a value of 1 will be given.


Next Step - Naming Convention

Additional Reading - Default values

Last updated 9 months ago

All actions fall into a type category. The full list can be found her

Power Automate Schema
Naming Convention
Complexity Default Values