Stratus Cloud Solutions Stratus Docs
Documentation / Financial Planner User Guide / Advanced Reference
Page 23 of 23

Platform Administration

Platform Administration

Tasks in this section require FinPlan_Admin or Salesforce administrator access. Standard planners using FinPlan_User should not need these procedures.

Post-install and reference data

  • Post-install handlers seed jurisdiction and reference data per package version.
  • Tax bracket importers (federal, state, provincial) run from admin utilities—not the main planner UI.
  • Retry post-install seed utilities if a sandbox install interrupted metadata deployment.

Run history retention

FinPlan_Orchestration_Run_Retention__mdt controls how long orchestration history rows are kept. Adjust retention for compliance or storage constraints in implementer orgs.

Observability

FinPlan_Orch_Observability__mdt fields include:

  • Enable_Perf_Checkpoints__c — performance checkpoint logging
  • Record_Diagnostic_Events__c — diagnostic event capture

Enable diagnostics only in controlled windows. Even diagnostic modes must avoid logging full projection payloads or PII-sized dumps.

Package upgrades

  1. Test upgrades in a sandbox with production-like data volume.
  2. Run packaged Apex tests via npm run package:version in the release pipeline.
  3. Beta-to-beta upgrades may require uninstall/reinstall in some test orgs (data loss risk—human approval only).
  4. Production subscribers should install released versions.

Destructive maintenance

Action Permission Scope
Clear plan input data Clear_Financial_Plan_Input_Data Deletes child inputs for one plan; keeps Financial Plan record
Package uninstall Salesforce admin Removes package metadata per Salesforce uninstall rules

Validation commands (implementers)

From the package source repository:

  • npm run security:scan — Code Analyzer (AppExchange + security rules)
  • npm run test:unit — LWC Jest tests
  • npm run package:version — 2GP version create with packaged tests

UI label corrections

Navigation label Plan Projections maps to the getting-started checklist page (planCompleteness route)—not a separate “completeness score” product. The checklist page title in code is plan completeness; user-facing nav uses Plan Projections.

Run History nav label: Run History (panel title: Orchestration run history).

Related: Orchestration Internals, Troubleshooting.