Establish the single asset-management release covered by this run. Record the business outcome, in-scope asset classes, and accountable people before design begins. Use named members who can make decisions during this run; resolve unclear ownership now because later security, acceptance, and release assignments depend on these fields.
1
End-user computing equipment
2
Network and infrastructure equipment
3
Facilities and building equipment
4
Vehicles and mobile equipment
5
Tools and production machinery
6
Software and digital assets
Confirm environments licensing and governance
Confirm where development, testing, and production will occur and whether the proposed connectors and Dataverse capabilities are licensed. Capture governance constraints, including managed-environment, data-loss-prevention, regional, and tenant boundaries. Do not build in the default environment unless organizational policy explicitly allows it.
1
Dedicated development test and production
2
Development and production only
3
Managed development test and production
4
Existing governed enterprise environments
5
Exception pending governance decision
1
Confirmed for all users
2
Confirmed for pilot users
3
Premium licensing required
4
Capacity review required
5
Blocked pending licensing decision
Design the asset data model
Define the system of record and a normalized asset model before building screens. Model stable identifiers as text so leading zeros and mixed formats survive, distinguish current state from event history, and document ownership, location, assignment, maintenance, and disposal relationships. Avoid collecting personal or sensitive data that the process does not need.
1
Microsoft Dataverse
2
SharePoint Online lists
3
Azure SQL Database
4
Existing enterprise asset platform
5
External system through connector
1
Standard operational records
2
Financially controlled records
3
Regulated personal information
4
Security-sensitive infrastructure records
5
Retention decision pending
Configure solution packaging and pipeline
Place the app, tables, flows, and related components in an unmanaged development solution with an intentional publisher. Externalize environment-specific values and connections, then choose a governed promotion path. Validate dependencies before continuing; missing connection references or environment values commonly break deployment.
1
Power Platform pipeline
2
Azure DevOps pipeline
3
GitHub Actions pipeline
4
Manual managed solution promotion
5
Governed pipeline decision pending
Build asset tables and validation
Implement the approved schema and enforce data quality at the source. Use text for asset tags, serial numbers, purchase-order numbers, and other identifiers; add requiredness and uniqueness only where the business rule is genuine. Enable auditing where accountability requires it and test representative values, including blanks, duplicates, leading zeros, and retired assets.
1
Enabled for required tables
2
Enabled for selected sensitive fields
3
Covered by external audit controls
4
Not required with rationale
5
Blocked pending compliance decision
Configure access and data protection
Implement least-privilege access across environment roles, app sharing, connector permissions, and Dataverse security roles. Test cumulative role effects, record scope, and restricted operations rather than checking only that authorized users can open the app. Record any exception and its compensating control.
1
Policy verified compliant
2
Connector reclassification required
3
Policy exception approved
4
Sensitive connector removed
5
Blocked pending governance review
Build asset capture experience
Build the asset intake and update experience around the operators' real context. Minimize required entry, expose validation near the field, prevent duplicate tags, and support barcode or mobile capture only when devices and operating conditions justify it. Test intermittent connectivity before promising offline operation.
1
Desktop manual entry
2
Mobile manual entry
3
Barcode or QR scan
4
Bulk import process
5
Automated system integration
1
Not required
2
Read-only offline access
3
Create records offline
4
Create and update offline
5
Requirement pending field validation
Build asset search and lifecycle views
Provide fast ways to find an asset, understand its current custodian and location, and trace lifecycle changes. Use controlled status values, preserve history instead of overwriting evidence, and make exceptional states such as lost, quarantined, or retired visible without deleting the record.
1
Ordered
2
In stock
3
Assigned
4
In repair
5
Lost or quarantined
6
Retired or disposed
Configure automation and notifications
Add automation only where it removes a repeatable handoff or control gap. Use solution-aware flows, connection references, explicit owners, and observable failure handling. Keep destructive or high-impact changes behind a human decision, and avoid notifications that provide no action or owner.
Test functions and data integrity
Execute traceable tests for create, read, update, search, assignment, transfer, maintenance, loss, and retirement scenarios. Include invalid, duplicate, blank, and concurrency cases and confirm automation side effects. Link each unresolved defect to an owner and release decision.
1
Passed
2
Passed with accepted risks
3
Blocked by critical defect
4
Failed remediation required
5
Not run
Validate security and access boundaries
Test representative users for every defined role, including attempts to read, create, edit, delete, assign, share, and export outside their allowed scope. Confirm app sharing and data access together; successful app launch does not prove the underlying data boundary is correct.
1
Passed
2
Passed with accepted risks
3
Blocked by access defect
4
Failed remediation required
5
Not run
1
All attempts denied as designed
2
Minor overpermission corrected
3
Accepted exception documented
4
Critical overpermission remains
5
Test not completed
Validate performance accessibility and monitoring
Use Monitor and App checker to investigate slow calls, delegation warnings, formula errors, and accessibility findings. Test with realistic data volume, network conditions, keyboard navigation, and screen-reader expectations. Record evidence and separate accepted limitations from release blockers.
1
Passed
2
Passed with accepted risks
3
Blocked by performance issue
4
Blocked by accessibility issue
5
Not run
Conduct user acceptance testing
Have representative users complete realistic asset scenarios in the test environment without maker assistance. Capture whether the release meets the defined business outcome, which risks are accepted, and which findings must be fixed. Do not treat general enthusiasm as acceptance evidence.
1
Accepted for production
2
Accepted with documented risks
3
Rejected for workflow defects
4
Rejected for usability defects
5
Testing not completed
Resolve release blockers and retest
This task appears when testing records a blocking or failed outcome. Triage the cause, implement the smallest controlled correction, repeat the affected tests, and attach evidence that the blocker is closed. If the result still fails, do not seek release approval.
1
Functional defect
2
Data integrity defect
3
Security or privacy defect
4
Performance defect
5
Accessibility defect
6
User acceptance defect
1
Passed after remediation
2
Passed with accepted risks
3
Blocked by unresolved defect
4
Failed after remediation
5
Retest not completed
Approval: Production release
Will be submitted for approval:
Test functions and data integrity
Will be submitted
Validate security and access boundaries
Will be submitted
Validate performance accessibility and monitoring
Will be submitted
Conduct user acceptance testing
Will be submitted
Resolve release blockers and retest
Will be submitted
Deploy the approved production release
Deploy only the solution version approved in the preceding gate. Run pipeline preflight checks, confirm target connection references and environment values, capture the deployment record, and stop if the target or artifact differs from the approved release. Avoid direct unmanaged changes in production.
1
Deployment succeeded
2
Deployment succeeded with warning
3
Deployment rolled back
4
Deployment failed
5
Deployment not started
Verify production and close handover
Run production smoke tests with controlled records, verify monitoring and support ownership, and confirm that users can access only the intended app and data. Link the final implementation record and escalate any production failure through the documented route before closing the run.
Optional cookies and similar technologies support analytics, advertising and visitor identification, and embedded content. Change or withdraw consent in Cookie settings. Cookie policy.