Versions Compared

Old Version 3

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

compared with

New Version Current

changes.mady.by.user Annegret Bernhardt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WDESIGNER and version 24.0

To exchange Designer content between systems or namespaces, or simply to create a copy of something, you can export and import the contents of the explorer tree. However, import and export are not equally allowed for all elements. The table below lists the available options for each element:

(tick)(tick)

NamespaceFolderServiceModelsSingle BPMN ModelFormsSingle Form
Export(error)(tick)(tick)
Import(tick)(tick)(error)
Import(tick)(tick)(error)(tick)(error)(tick)(error)

Version Considerations

By exporting and importing, you can transfer Designer contents between PAS installations. These installations may have divergent versions.

Info

As of Designer 21.1.3, import will perform migrations on the imported service if the data to be imported is not older than Designer 21.1.3 (2.0.165).
If there is a version gap of more than one version, multiple migrations will be applied if necessary.

Limitations

  • You cannot import newer versions to a system having an older version installed.

    • Version Considerations

    Multiexcerpt include
    SpaceWithExcerptINTERNAL
    MultiExcerptNameversion_considerations
    PageWithExcerptINTERNAL:_designer_excerpts

    Limitations

    Multiexcerpt include
    SpaceWithExcerptINTERNAL
    MultiExcerptNameimport_limitations
    PageWithExcerptINTERNAL:_designer_excerpts

    There are no migrations if importing Designer content from versions prior to Designer 21.1.3 (2.0.165). This may result in the imported service not working.
    In the future, importing data from a version older than 21.1.3 will be disabled.

    Exporting Explorer Content

    If you want to export an element, for example to create a backup copy of your model, choose option select Export from the context menu.

    If you choose to export On exporting from a Folder or Service, you have the choice whether or not to include the libraries used in the export.
    By default libraries are included in an export.

    Click Export to confirm your choice and start the actionexporting process.

    		During the export a message Generating file... is displayed.

    		A toast message also confirms the a successful export.

    Importing Explorer Content

    Image Modified

    If you want to import an element, for example to transfer a backup copy to another namespace, choose option select Import from the context menu.

    A pop-up Import will open opens.

    Click button Browse to select the file you want to import.

    The name of the chosen selected file is displayed. If you want to To change your selection, use button click Change File.

    If the correct file has been selected, start Start the import by clicking the Import button.

    		A toast message confirms the a successful import.

    Export files can may contain necessary libraries. If you import an export file containing libraries, you will be notified by a pop-up notice.

    Two different notes are possible:

    • Libraries imported successfully: The listed library versions The listed library versions have not already been available in the namespace and namespace and have been imported successfully.

    • Libraries already present in the namespace: The library version to be imported is already present in the namespace, and is therefore ignored. This applies to libraries of the same version, no matter if the imported library has the same or a different timestamp.

      Info

      Please check the imported service for functionality as the existing library will be assigned to the new service.

    Image Modified

    		The imported element is displayed in the tree.
    Panel
    titleOn this Page:
    Table of Contents
    Panel
    titleRelated Pages:

    Otp
    Floatingfalse
    maxHLevel2

    rp