Skip to main content

Processes

The system is designed to capture and transition traditional import/export workflows from priint:planner to the upgraded priint:bpm system, which utilizes the Camunda BPMN standard. It is integrated across various entities, including Users, Roles, and Generic processes.

Consequently, if the system cannot establish a connection with this server, it will display the message: "You have to configure priint:bpm in the system before you can use this feature." Proper configuration of the server is essential to access its capabilities.

Export and Import users​

  • Allows exporting user definitions together with the ISON configuration files. Optionally, you can also export:
    • All roles defined in the system
    • All access rights
    • Projects
    • Teams
    • Publication rights

Export users process

  • The input package for the Import Users process must match the structure and format of a package created by the Export Users process. The following options are available to control the import process:
    • Overwrite existing users
    • Overwrite existing roles

Import users process

Export and Import roles​

  • Allows exporting a selected role or all roles defined in the system. The generated XML file also includes the definitions of all access rights assigned to the exported roles, together with their positions in the access rights container hierarchy.

Export roles process

  • The input package for the Import Roles process must match the structure and format of a package created by the Export Roles process.

Import roles process

Export and Import publication types​

  • Allows exporting a selected publication type defined in the system. Optionally, you can also export the parameter definitions of publications belonging to the selected publication type.

Export publication types process

  • The input package for the Import Publication Types process must match the structure and format of a package created by the Export Publication Types process.

Import publication types process

info

Import behavior​

  • Existing objects are not modified by default. The import process uses a non-overwriting strategy unless explicitly configured otherwise.
  • Duplicate objects are not created. If an object with the same identifier already exists, it is reused instead of creating a copy.
  • Imported objects receive new internal IDs, while references between imported objects are automatically resolved and recreated.