OrganizationNorthstar Health
ProjectService Modernization
FoundryDeveloper Sandbox

Forge

What environment are you trying to build?

Forge handles build, provision, seed, retrieve, and deploy work. The legacy /data-loader route remains as a compatibility path for Environment Builder flows.

Back to Plan

Stage 1 / Define

What environment do you need?

Stage 2 / Shape

What should this environment support?

Selecting a business solution drafts the environment shape: data scope, metadata categories, policies, and evidence expectations.

Stage 3 / Review

Forge Intelligence recommendations

Recommendations

Recommendation

Include Price Books in the CPQ blueprint.

Why
Opportunity Products require Products, Price Books, and Price Book Entries to remain usable.
Evidence
Relationship Intelligence
Confidence
98%
Risk
Low

Recommendation

Mask PII for Training environments.

Why
Training policies prioritize realism and privacy together.
Evidence
Environment Policy
Confidence
96%
Risk
Medium

Warnings

Owner mapping needs review

OwnerId has no final target mapping.

Reference data warning

Expired price book entries should be refreshed.

Objects included8
Estimated Records184K
Runtime6m
API Calls312
Plan Health96%

Stage 4 / Build

Final preview

What will changeTraining environment refreshed from blueprint
Data includedCore objects, relationships, reference data, synthetic contacts
Metadata includedObjects, fields, layouts, flows, validation rules, permission sets
Policies appliedMask PII, reset owners, randomize emails, preserve relationships
Evidence capturedDiffs, validations, tests, approvals, recommendations, decisions