| Info |
|---|
This section offers information for Odoo users on how to configure their Confluence as an application in Odoo.
| Panel | ||
|---|---|---|
| ||
|
Applications menu
Application list
| Info |
|---|
The list of active applications is displayed by default. |
| Note |
|---|
Inactive applications can be opened using seach filter and search for field Active with value is false
|
Application configuration
| Tip |
|---|
Only users with Oregional Odoo App administrator permission can make settings for applications |
General settings
| Info |
|---|
General application configuration |
The name of the application
The client id of the Confluence application
Must be used when setting up the connection in Confluence, more information: Odoo Connector for Admins
Unique identifier of the Confluence application in this Odoo instance.
The Confluence application will use this when identifying itself to the Odoo instance.
The client secret of the Confluence application
Must be used when setting up the connection in Confluence, more information: Odoo Connector for Admins
Unique secret of the Confluence application in this Odoo instance.
The Confluence application will use this when identifying itself to the Odoo instance.
URIs tab
| Info |
|---|
List of valid, available callback URIs for the application defining the callback endpoints of the remote application |
| Warning |
|---|
An application must have at least one URI in order to make the communication work between Odoo and the remote Confluence |
The full path of the URI
The uri is verified as a string when an endpoint is called from Confluence.
Use https in the URI to enforce secure connection
Some applications may provide multiple callback URIs, in such cases it can be useful to have separate authorizations.
For Confluence applications only one URI is needed, so no need to check the checkbox.
Additional information
Settings tab
| Info |
|---|
Perform various settings for the applications |
When should the authorization code expire (expressed in seconds)
Default: 600
How long should the system keep track of issued authorization codes (expressed in days)
Default: 0
When should the access token expire (expressed in seconds)
Default: 3600
When should the refresh token expire (expressed in seconds)
Default: 0 (never expires)
Audit tab
| Info |
|---|
On the audit tab admins can find information about: We have been moved. Please follow the redirect link to the new documentation. |
| Expertisefinder redirect | ||||||||
|---|---|---|---|---|---|---|---|---|
|