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.
Versions
Section titled “Versions”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.
| State | What it means |
|---|---|
| Open | The working version. The only state that accepts changes. |
| In sign-off | Approval was requested. Everything is frozen while the approvers decide. |
| Signed off | Every approver approved. |
| Closed | The delivery is preserved, read-only. |
A rejection, or withdrawing the request, takes the version back to Open.
What a version holds
Section titled “What a version holds”| Item | What it is |
|---|---|
| Documents | A file, kept revision by revision, or a link to an external document. |
| Connected objects | A reference to something the sync found in the environment. Only its details are kept, not its source. |
| Planned interfaces | Interfaces the project will build and that do not exist in the environment yet. |
| Role | Can |
|---|---|
| Admin | Everything a Contributor can, plus tags, members, approvers, requesting approval, closing and opening versions. |
| Contributor | Add and remove content, edit the architecture and the guide, review proposals, while the version is open. |
| Approver | A 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.
What it needs
Section titled “What it needs”The Projects module must be enabled for your environment.
Next steps
Section titled “Next steps”- Use Projects: create a project and fill the repository
- Sign off a version: approve, close and start the next version