Introduction
Power Framework is deployed as Managed Solutions into a dedicated Power Apps environment within the customer’s own Microsoft 365 tenant.
Managed Solutions are used to restrict the editing of design elements to prevent uncontrolled changes. This is the standard approach used by Microsoft Independent Software Vendors.
Some configuration is required post-deployment to the individual customer environments such as enabling Power Automate Flows and relinking embedded Power BI reporting.
Deployment activities will be performed or overseen by a Program Framework Solution Consultant in the support team.
Version Control
All Power Framework Managed Solutions are version controlled.
Program Framework will maintain versions of Power Framework in a secure source control environment as part of the agreement with the customer.
Deployment Components
Deployments consist of:
- A core Power Framework solution
- A solution of Power Automate Flows
- Power Apps Component Framework solutions
- Customer Specific Customisations solution
Data is stored in Microsoft Dataverse (formerly named CDS (Common Data Services)).
By default, this Solution deployment does not include connections to other data sources outside of Microsoft 365, Dynamics, or Azure environment.
The Core Power Framework Solution files contain:
- Custom entities
- Default entities
- Web resources and components
- Relationships and security models
- Power Automate Flows
- Program Framework IP components
The design of content is specific to each customer based on the approved functional specification (as agreed by the organisation).
It is expected that the Core solution file will be updated occasionally with the latest upgrades by Program Framework. Likewise, the Customer Specific Customisations solution will be updated to deploy specific features that have been developed for the customer.
Also delivered will be a Power BI Dataset, Reports and App to be published into a dedicated Power BI workspace.
Building, Testing, and Deployment
The core Power Framework App is developed in a dedicated Program Framework Development tenant.
Customer-specific configurations are built in a dedicated Program Framework Sandbox tenant, with customisations built on top of the core application.
- Program Framework set up a dedicated Customer Sandbox environment in the Program Framework Sandbox Tenancy.
- The customer is given access to Power Framework in this Customer Sandbox via two Test User Accounts, the PMO Admin, and Project Manager Roles.
- The Program Framework team runs sandbox UAT with the Customer.
- The approved Core Solution together with the Customisation Solutions will be installed in the Customer Production environment in the Customer’s own Tenant for final UAT.
- The Program Framework support team will advise on the deployment instructions for the final steps of the delivery process.
Data Storage in Dataverse
The Power Framework Solution file designs contain both out of the box data tables as well as custom and managed tables, relationships, business rules, and components designed to meet the requirements of the customer’s functional specification.
The newly created Power Platform environment for Power Framework will include a dedicated Dataverse database, which will be the target for the deployment of the Power Framework data tables. These tables are part of Program Framework’s design IP and their definitions cannot be changed other than through the deployment of a solution update.
Azure Configuration
For customers using the Power Framework Cost Transaction import functionality, Azure Active Directory configurations will be required as it calls an Azure Function within the Program Framework tenant.
This requires the Power Framework App to be registered in the client’s Azure Active Directory, and App ID and Secret supplied to Program Framework.
The Program Framework support team are then able to set up an Application User which is used to call the Azure Service.
The processing of cost transactions import feature is done using an Azure Function so it can scale for large files. All processing is done in memory and nothing is saved to persistent disks.
SharePoint Library
Power Framework stores Project documents in a SharePoint document library inside a SharePoint site.
This SharePoint site can be an existing site or a new one created for this purpose.
To configure document library settings, the Program Framework’s deployment user account requires SharePoint Team Site admin rights. Admin rights can be revoked after deployment.
Power BI
A dedicated Power BI workspace will be created to house the Power Framework dataset and associated reports. A Power BI App will be created to package reports for publication to users.