Navigation:  Release Manager >

Import Overviews

Previous pageReturn to chapter overview

For each entity (form, process, datastore parameter and web service), a detail page is available to see elements to be imported and their individual notifications, warnings and errors:

 

clip0569

For each item in the list:

buttons are available to
oReplacing: Open the (local) item on another tab
oDetails: See the details of the import action
clip0570

 

When clicking on the 'Check again' button, the quality review is done again for the items in the list. After finishing, the import home screen is shown.

When clicking on the 'Details' button an overlay popup is opened that shows the import impact for the individual element.

Import impact details

Each element that is included in the release can be checked in detail. The following information is shown (when available for the element):

Information if element is added or replaced
Error messages
Warning messages
Notifications
Information stored with import file element
Information stored with local element

Starting the import

Once all errors have been fixed, the import of the release can be started. The import will not start immediately and will be scheduled. Once the import task runs, the import is done in this order:

1.Web Services
2.Datastore parameters
3.Forms
4.Processes
5.Link between Forms and Processes

Adding new elements

In case an element is added to the target system, the standard import process takes place, with the following specifics per entity:

Forms
oLinked to Topic
oLinked to process
Process
oIn case a form is embedded in the process, references to form Ids are resolved for the target environment
oIn case of decisions points, wait steps and actor references, field Id will be converted into internal label reference.
Datastore parameter
oLinked to Category

Replacing elements

The replacing of existing elements always happens in this order:

Original element is renamed
oTimestamp is added to internal label or name (for example 20190215110000)
Original element is retired.
New element is imported
References are resolved
oForms
Topic is linked
Process is linked
Role access rights are updated
oProcess
References to form Ids are set
IDs should refer to the active version of the form, not retired!
References to global mail templates are set
Role access rights are updated
oDatastore parameter
Role access rights are updated

Retirement of replaced items

Forms

After a form is imported and it replaces an existing form, the old form is moved into retirement mode. Retired forms will have no linked topic. Retired forms can never be active. Within a form, retired versions can be found in a new tab:

clip0571

When going to this tab, a list with forms is shown with the following information:

Retirement date
Edit button
oForm can be viewed, but changes can’t be saved
Preview button
Export button
Delete button

 

Processes

After a process is imported and it replaces an existing process, the old process is moved into retirement mode. Retired process versions can be found within the current process version:

clip0572

 

The tab is only shown in case there are retired versions. When going to the tab, a list with processes is shown, that can be opened from that place. For the retired versions the following information is shown:

Retirement date
Edit button
oProcess can’t be saved
Export button
Delete button

 

Datastore parameters

In case an imported datastore parameter replaces an existing datastore parameter, no archiving is done for the old datastore parameter. The definition is overwritten and the old datastore parameter is removed from the database.

Web Service

In case an imported web service replaces an existing web service, no archiving is done for the old web service. The definition is overwritten and the old web service is removed from the database.