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
  • Inputs (required)
  • Inputs Optional
  • Outputs
  1. AutoReview
  2. AutoReview - Power Platform Connector

File (v2)

Last updated 2 months ago

A fully working flow can be found here

Inputs (required)

Display Name

Display name of the flow

Flow ID

Unique ID of the flow, recommend using Resource id or workflowid

Owner

Flow owner/maker

Environment

Environment name

Definition

Flow definition/clientData

Inputs Optional

AutoReview allows configuration of the review metrics, if left blank the review will follow the default values.

  • Complexity

  • Naming Convention

  • Ratings

  • Scoring

Complexity

New complexity items can be added with the 'Add new item' button. Though we recommend using the text mode (small pen in top right corner).

Naming Convention

  • Naming Char - char

  • Data - data array

Ratings

Scoring

Outputs

The File api returns the following

  • Data/File

  • Data/Info

File

The file key returns a HTML pile that can be used to create a file. There are 4 different file types:

  • Review

  • Report

  • Diagram

  • Exceptions

Info

Data is a stringified json and once parsed returns different values depending on the file selected.

Review and Report

Key
Description
Example

Complexity*

Complexity score

100

Actions

Count of all actions

40

Variables

Count of variables

4

Exceptions

Count of exception actions (runAfter Failed)

2

Connections

Count of connections

2

Premium

Uses premium actions

true

*Review only

Diagram

#fillArrows: true
#lineWidth: 2
#fill:#569AE5
#background: white
#acyclicer: greedy
#ranker: tight-tree
#.data: visual=database fill=#EBDAF9
#.trigger: visual=roundrect fill=#569AE5
#.if: visual=rhomb fill=#2596be
#.switch: visual=ellipse fill=#2596be
#.scope: visual=frame fill=#808080
#.foreach: visual=transceiver fill=#00C1A0
#.until: visual=sender fill=#00C1A0
#.var: visual=input fill=#9925be
#.terminate: visual=receiver fill=#cc4747
#.var: visual=input fill=#EBDAF9

[<trigger> *Recurrence]->[HTTP]
[<foreach>Apply_to_each]--:>[<terminate>Terminate]
[HTTP]->[<data>Parse_JSON]
[<data>Parse_JSON]->[<foreach>Apply_to_each]


Next Steps - Diagram

Next Steps - Files

The object can then be edited in a source code editor (like Visual Studio Code or Notepad++) and then pasted in its entirety into the aComplexityTemplate input. With the reference inputted to the Reference Complexity.

The has to be placed in 2 inputs.

Each needs to be entered into the relevant inputs.

The follows same pattern as complexity, with the reference input separately from the aScoringTemplate array.

Returns the file. This file is similar to mermaid and creates a text file that is rendered as a diagram. The text can be pasted into nomnoml site or a site using the library.

complexity json
naming convention json
rating key
scoring json
nomnoml
Diagam (v2)
Files
https://powerdevbox.com/assets/AutoReviewDemo_2_0_0_1.zip
Use text mode for easier editing