What a publish actually does

What MOVES, what DOES NOT, and WHAT THE USERS GET. The step people treat as A BUTTON and should treat as A RELEASE. Publishing is one action and it is the moment your work becomes the thing other people depend on, which is a different category from every other action in this course. WHAT MOVES IS THE APPLICATION DEFINITION: PAGES, FLOWS, CHAINS, VARIABLES, THE SERVICE CONNECTIONS AS CONFIGURED. Everything you built. It becomes the live version and every user who loads the application from that moment gets it. WHAT DOES NOT MOVE IS THE DATA. Business object rows stay where they are — publishing does not copy them and does not delete them. Which is right, and it is also the thing people are surprised by when they expect a publish to reset something. AND WHAT ALSO DOES NOT MOVE, WHICH IS THE DANGEROUS HALF, IS THE ENVIRONMENT-SPECIFIC CONFIGURATION UNLESS…

In this module: Module 14 · Source control, environments and publishing

1. 1What a publish actually doesFree preview
2. 2Versions, and living with two
3. 3Source control, and why a visual tool still needs it
4. 4Branching and more than one developer
5. 5Environments, and what differs between them
6. 6Making endpoints configurable
7. 7The promotion checklist
8. 8Rolling back
9. 9Automating it
10. 10What breaks: four promotion failures
11. 11Lab briefing · Promote and prove it is isolated