Versions Compared

Old Version 8

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

Saved on

compared with

New Version 9

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

Saved on

Key

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

...

Content imposition is an extension of the content declination in projects. The specificity is to create a strong link between source and declinations, resulting in automatic synchronizations at each source modification. Info

Note

This functionality is intended for certain very specific cases of content declination. This section will describe a set of functional concepts leading to very specific conditions of use. It is therefore advisable to control them well and be very careful when using them.

Technical requirements for imposition

...

  • the object to be declined must include the virtualobject field (child to the same nature)

...

Note

Any object with the virtualobject field is eligible for the imposition functionality. If the field value is specified, it indicates that the object is imposed and its source is the pointed object.

Operation

The creation of the strong link between declination is schematized in this way:

...

The properties report is done field by field, so you can apply a tag to a collection field for example. In this case, the elements collections will not be included in the required declinations.

Warning

Caution

In the case of collections, the application of the tag on an field of the structure in collection is not taken into account: the update of the imposed declinations requires the deletion and re-creation of the set objects the collection.

Note

Important

The application of the wxm_not_imposed_property tag does not have the following properties impact on the declination wizard configuration step. Any field with the tag wxm_manual_forced_value must have the following properties also of wxm_not_imposed_property otherwise the changes would be deleted in the next update.

...