Skip to content
Last updated:

About Projects

Keep the specifications, source files, architecture and sign-off of each SAP delivery together, one version per delivery.

A project is the repository of one SAP delivery in one environment. It keeps together:

  • specifications, source files and other artifacts;
  • references to the iFlows, packages, API proxies, queues and systems the sync found;
  • the solution architecture;
  • a guide for the next team;
  • the sign-off that freezes each delivery.

Each delivery is a version. V1 is created with the project; each improvement after it is a new version that starts with everything the previous one had. Changes only shows what a version added or changed.

Only one version can be in progress at a time.

StateWhat it means
OpenThe working version. The only state that accepts changes.
In sign-offApproval was requested. Everything is frozen while the approvers decide.
Signed offEvery approver approved.
ClosedThe delivery is preserved, read-only.

A rejection, or withdrawing the request, takes the version back to Open.

ItemWhat it is
DocumentsA file, kept revision by revision, or a link to an external document.
Connected objectsA reference to something the sync found in the environment. Only its details are kept, not its source.
Planned interfacesInterfaces the project will build and that do not exist in the environment yet.
RoleCan
AdminEverything a Contributor can, plus tags, members, approvers, requesting approval, closing and opening versions.
ContributorAdd and remove content, edit the architecture and the guide, review proposals, while the version is open.
ApproverA mark on top of the role: approves or rejects the version.

Admins of the environment are Admin in every project. Everyone with access to the environment can read every project: there are no private projects.

The Projects module must be enabled for your environment.