Content synchronization

Content synchronization


A new tool for creating a new collection of content to be synchronized is now available:

From version 3.6 onwards, it is possible to delete synchronized content. This action is irreversible and deletes all content in the selected synchronization, if no other collections are attached.

New definition :

  1. Define name and type

    There are currently 2 types of plugin "Content import".

    • Data source LDAP
      Allows you to define a data source from a LDAP directory.
    • Data source SQL
      Allows you to define a data source from a SQL database. (Only Oracle and MySQL are currently supported).

  2. Synchronized content

    Content typeSelect the type of content to be synchronized with the data source
    Content prefixThis is the prefix that will precede the name of synchronized content when it is stored.
    It cannot be empty or begin with a number or special character.
    Restricted content indicatorThis is a drop-down list that lets you choose a Boolean metadata belonging to the chosen content type.
    This metadata is used to filter synchronized content when searching on the front end.
    Synchronize only existing contentIf this parameter is checked, only existing content will be synchronized. If no synchronization has been performed,
    will prevent the creation of new content. 
    Delete obsolete contentIf this parameter is checked, all existing content that no longer belongs to the data source will be deleted.
    Validate content at creation stageIf this parameter is checked, all content will be validated after synchronization. 

  3. Lifecycle

    LifecycleSelect the lifecycle corresponding to the content you wish to synchronize. The default is the 'Synchronized content' lifecycle provided by this plugin.
    Initial actionThis is the identifier of the lifecycle action corresponding to the creation of synchronized content.
    Validation actionThis is the identifier of the lifecycle action corresponding to the validation of synchronized content.

  4. Complementary operations


    Specific treatmentThis is where you can define an additional operation on content during synchronization(see Integration Manual).
    Error report recipientsHere you define the e-mail addresses (one per line) of the administrators who will receive content synchronization error reports.

  5. Source configuration

    This configuration depends on the type of synchronization and the type of content selected:
    For type :
    • Data source LDAP


      Server LDAPSource definition LDAP
      People DNThe DN relative to the people in the directory LDAP
      Search filterDirectory search filter LDAP
      Search typeDirectory search options LDAP
      IdentifierThe content type metadata defined, which corresponds to the unique identifier of synchronized content

    • Data source SQL

      DatabaseSource definition SQL
      User tableThe SQL table containing the data
      IdentifierThe content type metadata defines the unique identifier for synchronized content.

    The last remaining parameters correspond to the correspondence between the fields of the chosen source and the metadata of the content type:

    Fill in the following table for the metadata you wish to synchronize:

    Content fieldsMetadata label for selected content (except repeater)
    Attribute LDAP (or SQL)The LDAP field or the SQL column corresponds to the associated metadata.
    ReplaceableIf this parameter is checked, the value associated with the metadata can be replaced by a local value.
Back to top

Content IO