SaaS platform template selection workflow¶
This workflow supports Backend Developer Agent and Frontend Developer Agent when implementing SaaS products that use the SaaS platform template program. It is design-time guidance; it does not create repositories.
When to use¶
- The architecture blueprint names a bounded context in Tenants, Product catalog, Entitlements, Billing, or Metering.
- The UI is a portal composed of Blazor MFEs with a shared shell.
Selection rules¶
| Need | Template / artifact |
|---|---|
| New backend microservice for an in-scope context | ConnectSoft.Saas.<Context>Template (e.g. ConnectSoft.Saas.ProductsCatalogTemplate) — includes ConnectSoft.BaseTemplate submodule |
| Portal host (navigation, MFE registry, tenant/edition) | ConnectSoft.Blazor.Shell.Saas |
| Feature UI for a context | Blazor MFE template (same patterns as Identity / Authorization Server MFEs); consumes ServiceModel NuGet packages only |
| Cross-cutting tenant resolution, options, tests | ConnectSoft.Extensions.Saas.* packages (Phase 2); Phase 1 may use inlined stubs in generated solutions |
Out of scope¶
Do not select ConnectSoft.Saas.*Template for Audit, Notifications, or Configuration platforms as part of this program—they belong to separate initiatives unless the backlog explicitly expands scope.
References (ConnectSoft.Documentation)¶
- SaaS platform — solution plan (
Docs/starters/saas-platform-solution-plan.md) - SaaS bounded contexts and template matrix (
Docs/starters/saas-bounded-contexts-and-templates.md) ConnectSoft.Extensions.Saas.*libraries (Docs/starters/saas-extensions-saas-libraries.md)- Epics and Azure DevOps mapping (
Docs/starters/saas-extensions-and-templates-epics.md)
Company framework¶
- Implementation mapping: ConnectSoft Company documentation —
docs/saas/framework/saas-platform-template-program-implementation-mapping.md