Updates (Evergreen)
IFS Cloud updates arrive on a regular rhythm. Plan each update so that your tailored objects keep working.
This page applies to the Maintained after go-live stage.
IDK templates: IDK-23
Page in the app: /p/{projectId}/updates
Update cycle
Six steps, repeated for every release.
Release
- Read notes
- Check impact
- Update TEST
- Retest
- Decide
- Update PROD
How to do it
- Set the policy. Choose the rhythm, the roles and the environments.
- Run a cycle. Check each CRIM object and interface for impact.
- Log the decision. Write what you decided and why.
Good to know
- The fewer tailored objects you have, the cheaper each update is.
- Production is updated only after one person records the backup and a second person confirms it.
- The cycle shows the IFS check of the interfaces. A person still records the results.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: