Once people use an app, they ask for changes. Here’s how to ship one, and undo it.
Ship a change
Your CSMs want to see which renewals are at risk:
Add an "at risk" flag: an account is at risk when it renews in the next 45 days and its note mentions "risk", or when it has no note. Show at-risk rows first and add a toggle to show only those. Test it locally, then deploy it.The URL, the Salesforce alias, the access you set and the morning schedule all carry over. The new deploy shows up on the project’s Deployments tab.
Roll it back
If a change breaks the page, roll back in the Helix dashboard. No prompt needed.
- 1
Open Deployments
In the Helix dashboard, open the renewal tracker and go to Deployments.
- 2
Restore the last good one
Choose Restore on the last deployment that worked. It’s live again in a few minutes.
Then have your assistant fix the bug before you deploy again, so it doesn’t ship twice.
That’s the path
You took one app from a first prompt to production. Every app you build next goes the same way.