Submissions — Environment Switcher Integration & Component Workflows
This release updates the Submissions guide in the Developer Console with separate Aspect, Widget, and Feature submission workflows, a Domain Allowlist for GitHub repository access, and environment-aware deployment. The Environment Switcher guide adds notes on verifying the active environment and clarifies that switching does not require signing out.
What's New
Submissions Guide Updates
- Submission Capabilities — Separate Aspect, Widget, and Feature sections replace the single submission form flow.
- New Submission — Financial institution (FI) teams that have already completed onboarding choose a component type from New Submission instead of going through Build Component setup again.
- Submission Dashboard timeline — The Submission Dashboard timeline now uses PR Merged and Deployed to Environment as stage names, replacing the older separate Staging and Production labels.
- Domain Allowlist — FI administrators request approved domains under Manage Collaborators → Domains. Candescent Super Admin approval usually takes 3–5 business days.
- Host Allowlist — Refreshed screenshot aligned to the current console UI.
- Updated graphics — Refreshed screenshots across Build Component, submission forms, the dashboard, Aspect, Widget, and Feature flows, allowlists, and the Environment Switcher.
Environment Switcher Guide Updates
- Environment verification — Verify the active environment before administrative or production-related actions.
- No sign-out required — Switching environments does not require signing out or logging in again.
Get Started
- Submissions — Follow the Aspect, Widget, or Feature submission flow, then track status on the Submission Dashboard.
- Environment Switcher — Confirm Sandbox, Staging, or Production is active before creating submissions or deploying components.
The Candescent Developer Experience Team