Transport register

A transport is a package of IFS configuration that moves between environments. The app records it and checks the rules. It never applies anything to IFS.

This page applies to every stage.

Page in the app: /p/{projectId}/r/transport

Life of a transport

You can withdraw a transport from draft, ready or approved. Give a reason.

  1. Draft
  2. Ready
  3. Approved
  4. Superseded

Life of an application in one environment

A failed application can be retried. An applied one can be reverted with a reason.

  1. Planned
  2. Applied
  3. Failed
  4. Skipped
  5. Reverted

How to do it

  1. Add the transport. Describe it, choose its kind and attach the package file. The file must pass the malware scan.
  2. Mark it ready. The app stores the name and the hash of the newest clean file. You cannot edit them.
  3. Get it approved. The customer project manager, the system owner or the IT manager approves. Whoever marked it ready cannot decide.
  4. Record each application. For every environment add an application. When you apply it, record the time, the person and the hash.

Good to know

  • For production the transport must be approved, the hash must match the file and it must have been applied in a non-production environment first.
  • A production application during a freeze period needs a reason.
  • A linked CRIM object must be accepted or handed over before the transport can be approved.
  • After a data copy the app lists transports applied before the copy that the source lacks. The refresh cannot finish while any remain, unless you give a reason.

Related topics

Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.

Last updated: