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

  1. Read notes
  2. Check impact
  3. Update TEST
  4. Retest
  5. Decide
  6. Update PROD

How to do it

  1. Set the policy. Choose the rhythm, the roles and the environments.
  2. Run a cycle. Check each CRIM object and interface for impact.
  3. 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: