Confluence Integration Settings
The Confluence Integration settings can be found in "Settings > Export > Path Settings".
In order to enable Confluence integration, your correct Confluence Type (Server or Cloud) must be chosen and your Confluence URL must be entered.
We recommend creating 1 dedicated Confluence-user and add this central Confluence-user to the Performer Suite for everyone.
The Confluence Parent Page you enter must exist and therefore be created manually beforehand
(the Performer Suite does not create a parent page in this case)The Parent Page is case sensitive
(Confluence makes a difference between each letter)
If your 'Test Connection' was successful, your settings can be saved.
How to find your correct Confluence URLs, Space Key, and Parent Page?
Login to your Confluence:
Based on this URL, entities and Scenarios can be assigned to a specific Confluence page.
Confluence Cloud users must also create an API Token here.
The token replaces the usual confluence password.
Difference between General Path and Specific Path
General path:
Your documentation is uploaded to an existing Confluence page based on your defined Space Key and optional Confluence Parent Page (subpages are created automatically).
Additional entity- or Scenario assignment is not needed.
Specific path:
Already existing Confluence pages can be assigned via the 'Column Chooser' to very specific entities and Scenarios.
The documentation is directly uploaded to the assigned page.
The following parameters must be entered to successfully export the document to your Confluence:
Parameter | Relevant for general path | Relevant for specific path |
|---|---|---|
Confluence Type (Server vs. Cloud) |
|
|
Confluence URL |
|
|
Confluence Space Key |
|
|
Confluence Root or Parent Page |
|
|
When 'Global Confluence Path for all users' is enabled, the path is set for all Performer Suite users and the standard users can no longer change the parameters (option will be hidden).
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