Inserting the Confluence Parameter
The Confluence Integration settings can be found in "Settings > Export > Path Settings".
In order to enable Confluence integration, the Confluence Type (Server or URL) must be chosen and your Confluence URL must be entered.
Where do you find your Confluence Parameters?
Based on this URL, entities and Scenarios can be assigned to a specific Confluence page.
Confluence Cloud users must create an API Token here.
The token replaces the usual confluence password.
Difference between Specific Confluence Path and General Confluence Path:
Specific path: Existing Confluence pages can be assigned to specific entities and Scenarios (documentation is directly uploaded to the assigned page).
General path: The documentation is uploaded to an existing Confluence page (subpages are created automatically) based on the defined Space Key and optional Confluence Parent Page.
No further specific entity- or Scenario assignment is needed.
The following parameters must be entered to enable the integration of the documentation into Confluence:
Parameter | Relevant for specific path | Relevant for general path |
---|---|---|
Confluence Type (Server vs. Cloud) | ||
Confluence URL | ||
Confluence Space Key | ||
Confluence Root or Parent Page |
When "Global Path for all users" is enabled, the defined Confluence path is set for all Performer Suite users and the standard users can no longer change the parameters (setting is only visible to users with permission in the role).
For more information see: General Role Authorizations
The connection can be tested via the "Test connection" button. Afterward, a login window appears, in which, depending on the Confluence solution, the user name/email and the password/token must be entered:
If the test was successful, your settings can be saved:
The entered parameters are used to create the documentation of BW, HANA, SAC, and BO objects.
The export of documentation to Confluence is described here: Confluence Integration
The automated Confluence export can also be realized via the AutomationTool: Automated Export