About Audit
Keep a revision history of every iFlow by content, and see what changed in its design, parameters and deployment.
Audit keeps a history of every iFlow and tells you what changed since you last looked. A new revision is recorded when the content changes, not when SAP reports a new version number:
- two exports of the same design with a different timestamp are the same revision;
- a design changed without a version bump is a new revision.
Three histories per iFlow
Section titled “Three histories per iFlow”| History | What a revision means |
|---|---|
| Design | The iFlow’s files changed: steps, scripts, mappings, adapters. |
| Parameters | One or more externalised parameters changed: keys added, modified or removed. |
| Deployment | The deployed artifact changed: who deployed it and when. |
All content is stored encrypted. Parameter values are kept but not shown on screen.
When changes are captured
Section titled “When changes are captured”Audit has no schedule of its own. Revisions are captured during the Discovery sync, at the interval set in Settings → Discovery → General.
A redeploy without any change in design or parameters is recorded in the history but does not ask for a review. Redeploying the same content is routine in development and test tenants, and a queue full of items with nothing to do hides the ones that matter.
When to use which
Section titled “When to use which”Use the review queue when you need to answer questions like:
- What changed in our tenant since yesterday?
- Who deployed this iFlow, and when?
- Which steps changed between these two revisions?
- Which parameters were added or removed?
Use Git publishing when you need:
- the history in the tools your developers already use;
- a copy of every design outside SAP, one commit per change.
What it needs
Section titled “What it needs”The Audit module must be enabled for your environment, and the Discovery sync must be running with active SAP Cloud Integration credentials.
Next steps
Section titled “Next steps”- Review changes: work through the queue
- Publish to Git: send the design history to a repository