Not everything you build in the Dev stage needs to be published to Live. Only specific artifacts must be deployed so they are available for actual usage in the Live environment. This controlled publishing approach lets you test changes safely before exposing them to end users.
Publishing moves selected artifacts from the Dev stage to the Live stage. After publishing, these artifacts are available for real-time usage, transactions, and reporting.
¶ 1. Where Publishing Is Done
Publishing is performed from the Artifact Summary page in the Dev stage. From this page, you can:
- View all artifacts created or modified in Dev
- Select only the required artifacts
- Deploy them to the Live stage
¶ 1.2. What Happens After Publishing
After publishing is completed:
- Artifacts become available in the Live stage
- End users can access and use them
- Dev artifacts remain editable without affecting Live
¶ 2. Artifacts That Require Publishing
Not every configuration on the platform requires publishing. Only the artifacts listed below must be explicitly published for their changes to appear in the Live stage. Artifacts that are not published remain available only in the Dev stage.
The following artifacts require publishing:
| S. No | Artifact | S. No | Artifact |
| 1 | Apps | 13 | Data source Add-Ons |
| 2 | Data tables | 14 | External Lookups |
| 3 | Data sources | 15 | External App References |
| 4 | DS-Reports | 16 | User Manuals |
| 5 | DS-References | 17 | App Reports |
| 6 | DS-Views | 18 | Toaster Configurations |
| 7 | App Events | 19 | Organization Themes |
| 8 | Lookups | 20 | Workspaces |
| 9 | Public Dashboards | 21 | Data table Sync |
| 10 | Custom Menu | 22 | Report Schedulers |
| 11 | Data table Functions | 23 | Role |
| 12 | Payment Gateways | 24 | Low Code Function |