Versions Compared

Old Version 4

changes.mady.by.user Jules DELEUZE (Unlicensed)

Saved on

compared with

New Version 5

changes.mady.by.user Jules DELEUZE (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Operation

When synchronization is active on content, a button Propagate update appears on the display screen of this object.

This button is used to select:

  • the type of propagation

  • projects impacted by this update (only projects using the content are listed)

There are two ways to propagate an update:


imposition

the update will directly propagate on the "whisper" versions of the content for the selected projects.
Projects will be notified that an update of the content has been required. They will be able to hide the alert after learning about it.

proposal

the update will only impact the "drop-down" versions of the content for selected projects when it is accepted.
Project managers will be able to accept/reject/hide this update.


Security

It is possible to secure the different synchronization actions.
For example, it is possible:

  • authorize/prohibit the imposition or proposed update:
    it will be necessary to act in the action INSERT of the domain OBJECTDATA of the security.

  • authorize/prohibit the acceptance or rejection of an update:
    it will be necessary to act in the UPDATE action of the OBJECTDATA domain of the security.

To do this, it is sufficient to create the appropriate safety rules on the mediasharing object whose context is synchro.
⇒ The basis of the security rules will be therefore: lower(objectname) = 'mediasharing' AND object.context='synchro'.

To differentiate between the proposal and the imposition of an update, it will suffice to specify the type of mediasharing object.
⇒ The rules will have to be completed with: AND object.type='impose' OR AND object.type='propose'