Power Platform Booster is in public preview. Documentation will always reflect the latest version.

The activities related to Power Platform Booster can be split in 2 categories:

  • Admin activities
  • Maker activities

An admin is a member of the team responsible for the Power Platform having the admin role. A maker is an employee who has created a canvas app/cloud flow.

Admin activities

The following operational activities apply:

  1. Manually determine and configure the environments that are suited for processing.
  2. Manually determine and configure the canvas apps/cloud flows which are suited for clean-up.
  3. Analyze the API requests and optimize them.
  4. Manually delete completed actions.

Besides these activities, there is a canvas app for admin clean-up activities.

Manually determine and configure the environments that are suited for processing

The cloud flow “PP Booster – Environments” retrieves data about all environments the PP Booster account has access to. The data is stored in the list “Environments”. This list has many fields an one of them is called “Process”. The default value is “False” which means that the cloud flows “PP Booster – Apps to process” and “PP Booster – Flows to process” ignore that environment.

When an environment is suited for processing, the field “Process” must manually be changed to “True”.

Manually determine and configure the canvas apps/cloud flows which are suited for clean-up

Below, canvas apps are explained but the same approach applies to cloud flows.

When an environment is suited for processing, the cloud flows “PP Booster – Apps to process” will act on that environment. This cloud flow will write data about canvas apps in the list “Apps to process”.

The cloud flows “PP Booster – Apps” acts on items in the list “Apps to process”. Per app, detailed data is retrieved and stored in the list “Apps”. This list has many fields an one of them is called “No clean-up”. The default value is “True” which means that no clean-up tasks will be created for those apps.

When a canvas app is suited for clean-up, the field “No clean-up” must manually be changed to “False”. There must also be a correct value inserted in the field “Clean-up date”. At that date, a clean-up task will be created.

Analyze the API requests and optimize them

A dedicated page is related to this top. Click here to go to that page.

Manually delete completed actions

Actions are not automatically deleted because they can prove to be useful when analyzing issues. That’s why they must be deleted manually to clean-up the related list.

Maker activities

There are 2 reasons why Power Platform Booster interacts with a maker:

  • (S)he is a new maker.
  • A clean-up task.

Part of both reasons is sending an email. By using a shared mailbox, a maker can more easily see that an email (new maker/clean-up task) is sent from the team who is responsible for the Power Platform.

New maker email

The first time that an employee is marked as a maker, (s)he gets an email. The content of this email is organization specific and needs to be created before using Power Platform Booster for production. The following components are usually part of a new maker email:

  • Corporate branding.
  • The reason why the employee gets the email.
  • A link to a webpage with governance topics.
  • A link to an internal community site.
  • Internal examples.
  • A link to Microsoft Learn.

The new maker email has 2 settings:

  • newmakeremailbody
  • newmakeremailsubject

Clean-up task

When a canvas app/cloud flow is marked for clean-up, a clean-up task will be created for it. The owner and possible co-owners will receive an email about this. The content of this email is organization specific and needs to be created before using Power Platform Booster for production. The following components are usually part of a clean-up task email:

  • Corporate branding.
  • The reason why the employee gets the email.
  • Details about the clean-up task:
    • Canvas app/Cloud flow
    • Name
    • Environment
  • A link to the canvas app “PP Booster – Clean-up task” which is used to complete clean-up tasks.
  • Information what happens when the clean-up task is not completed.
  • Information what happens when someone else already completed the task.