Power ALM

Adds custom Deploy and Save Work buttons to the PowerApps Solutions page.

The Chrome Extensions will create 3 buttons on our Power Platform IDE. Save Button ------------------------- Function: Adds the solution to GitHub. Detailed Description: When clicked, this button commits the current state of the solution (code, configuration, documentation, etc.) to a GitHub repository. It typically performs the following actions: Stages all relevant changes. Commits the changes with a message (often auto-generated or user-defined). Pushes the commit to a specific branch in the GitHub repository. This ensures that the solution is version-controlled and safely stored in the cloud, making it accessible to collaborators and traceable over time. Use Case: Ideal for saving progress, backing up work, or preparing for a code review or pull request. Release Button ------------------------------------ Function: Deploys the solution to all development environments and UAT environment. Detailed Description: When clicked, this button initiates a deployment pipeline that pushes the current solution to all configured development environments. It may include steps such as: Building the solution (compiling code, bundling assets, etc.). Deploying the build artifacts to Dev and UAT environments Notifying stakeholders or logging the deployment status. Use Case: Used when the solution is ready for testing or demonstration in a development setting. It ensures all dev environments are synchronized with the latest version. ALM Checker Button : Function: Checks the dependencies of solution in all environments including UAT and production environment. What's New : Shows a clear message when Power ALM isn’t licensed for your organization, and confirms requests only once they’ve been accepted. Detailed Description: Catch deployment problems before they happen. Open a solution in Power Apps and click ALM Checker. Power ALM checks it against each of your target environments (UAT and Production) and emails you the results within a minute or two. It looks for: • Components the solution depends on that aren’t in the solution or the target environment • Connection references that are missing, or have no connection, in the target • Environment variables with no value in the target • Child flows that are missing from the target Each issue names the exact component and explains how to fix it. Nothing is deployed or changed: ALM Checker only reads your solution and environments.