Odoo Connector
📈 Marketplace❓ Support❤️ Feedback🏠 META-INF Apps
  • General Product Information
    • Odoo Confluence Connector Overview
  • User Guide
    • How to connect Confluence and Odoo
    • Odoo Connector for Confluence
      • Odoo Connector for Admins
        • Adding a New Odoo Server
      • Odoo Connector for Users
        • Authenticating to an Odoo Server
        • Adding the Odoo Connect Macro
    • Confluence Connector for Odoo
      • Confluence Connector for Admins
        • Installation
        • Application settings
        • Model scheme settings
        • Model configuration settings
        • Revoke User Authorizations
      • Confluence Connector for Users
        • Review and Revoke Your Authorizations
    • Troubleshooting guide
      • How to Check Your Own Odoo OAuth2 Tokens
      • I cannot authenticate to the server, even though I have configured it on both sides. Why is that?
      • I have used the macro before, but now it says "Need to authenticate to server!". What to do?
    • Use Cases
      • Current Use Cases
        • Follow up Confluence Meeting Notes
        • Creating a gateway between Confluence Pages and Product details
      • Potential Future Use Cases
    • Odoo Connector for Confluence Cloud
      • Install Odoo Connector on Confluence Cloud
      • Install Confluence Connector on Odoo
Powered by GitBook
On this page
  • Model configurations menu
  • Model configuration list
  • Model configuration settings
  1. User Guide
  2. Confluence Connector for Odoo
  3. Confluence Connector for Admins

Model configuration settings

PreviousModel scheme settingsNextRevoke User Authorizations

Last updated 3 years ago

This section offers information for Odoo users on how to set up model configurations for the Oregional REST API.

Model configurations allow to refine how a model should be made available to a remote application.

Highlights:

  • add an icon to the model that can be sent to the remote application to help users visually to identify quickly the type of Odoo record they see on a Confluence page

  • change the display name of the model, e.g.: for res.partner instead of "Contacts" you might want to display "Partners" in Confluence

  • limit the list of fields that can be displayed in Confluence (you might not want to allow certain sensitive fields to be able to be accessible from Confluence)

  • link a model configuration to any model scheme

The app is shipped with the Default partner configuration scheme to give you an idea about this feature.

Model configurations menu

Model configuration list

The list of active model configurations is displayed by default.

Inactive model configurations can be opened using search filter and search for field Active with value is false.

Model configuration settings

Only users with Oregional Odoo App administrator permission can make settings for model configurations

Item
Description
Notes

Icon

Custom icon for the model in this configuration

Can be made available for external applications

Name

The name of the model

Translatable

Active button

Archive / Unarchive a model scheme

Model

Linked Odoo model object

A records from ir.module.module model

Model Technical Name

The technical name of the linked Odoo model

It is a related field, so it is computed automatically

Model Display Name

Custom display name for the model in this configuration

Description

Additional information about the model scheme

Translateable

Fields tab

Fields for the selected model that are allowed to be used in Confluence.

There are three ways to limit the list of fields:

  • None: there is no limit, all fields are available for the model

  • Blacklist: all fields except for the listed fields are available for the model

  • Whitelist: only the listed fields are available for the model

Not all fields make sense or advised to be used in Confluence, but it is up to you, what you allow. Just give it some thoughts before allowing all fields.

Model schemes tab

You may link the configuration to model schemes by clicking on Add a line and unlink configurations by clicking on the x on the right end of the line.

Audit tab

On the audit tab admins can find information about:

  • creation timestamp

  • user who created the record

  • last modification timestamp

  • user who last modified the record