Versions Compared

Old Version 12

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

Saved on

compared with

New Version 13

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

Saved on

Key

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

...

  1. in the toolbar, click the' copy to another project' button.

    Image RemovedImage Added

  2. a window will open where you can select up to three actions:

    • make a single copy

    • propose the content (see content proposal)

    • impose content (see content imposition)

  3. Select the content destinations

  4. Setting up the new objects (optional step see setting up the new objects)

  5. Confirm the action to be performed

  6. A result page shows the objects created

...

Within these JSPs, you can work with the following variables:

form_object

nature of the current object in short declination

activeRefererObject

reference object in declination

itemValue

CTObjectField corresponding to the current property

colfield

name of the current property

nature

nature of the object pointed out in the context of an attribution relationship

forcedValues

java.util.HashMap properties to force

...

Here are the error codes you may encounter:

not_connected

Your session has expired, you need to log in again.

function_not_activates

The project declination function is disabled. You must refer to your administrator.

object_not_found

The object to translate does not exist.

not_authorized

You don’t have the necessary rights to see the instance. The destination project must be accessible to the user, make sure that he has access to it.
Security is tested in the init of the datatranslate action, by default we test the action view of the objectdata domain, check the security rules or overload this boolean with a rule specific to your developments.

not_compliant

The requested object does not have the necessary properties for the declination function (see technical prerequisites).

mandatoryFields

The object could not be created because some mandatory fields are empty. This error is often solved because a match could not be found on an association. The value associated with this error is the list of fields that are empty.
Decline the associations before declassifying the requested object.
The error is removed by a structural obligation. If this obligation is only functional, you can create a facet to make it mandatory only as a back-office contribution.
Customize the field to manage a default value.

...