Navigation:  Release Manager >

Import Release

Previous pageReturn to chapter overviewNext page

The importing of a release will be done in another environment. The release ZIP can be uploaded, and the import function will show the results of a quality analysis done on the loaded ZIP file.

Open from admin the section 'Import package'.

An overview of recent imports are shown:

clip0567

Any import will first be automatically validated. Administrators should check the warnings after validation before starting the actual import.

After validation, this screen is shown:

clip0568

 

Order of import result:

1.Forms
2.Processes
3.Datastore parameters
4.Web Services

Quality Analysis

General message agreements

Error: Something is wrong and import will not continue
Warning: Something is wrong and import can continue
Notification: A special situation has been dealt with, or a non-critical issue has been discovered

Forms

For forms the following information is checked:

Can the internal label of the form be found?
oNo or always add option is true: Form will be added
oYes and always add option is false: Form will be replaced
In case the form will be added these additional message are shown:
oNotification in case of:
When internal label was found but adding of form is done due to always-add option enabled.
Internal label is extended with a number
Form was not found and a new form is added
Messages for both replace as add:
oWarnings in case of
Datastore parameter fields do not match source structure and datastore parameter definition is not in import file
Webservice fields do not match source structure and webservice definition is not in import file
References to non-existing ticketing custom fields
Roles that refer directly to the form are not found (searched on name)
In case of update: Show roles that currently refer to the form to be replaced.
oErrors in case of
Person field references not found
Web service references not found and web service definition is not in import file
Datastore parameter references not found and datastore parameter definition is not in import file
Webservice references not found and webservice definition is not in import file
Linked process is not found (on name) and process definition is not in import file
Used subform is not found and subform definition is not in import file
Subforms will have their own checks done in a similar way as main forms.

Process

Can the name of the process be found or always add is off?
oNo: Process will be added, also in case of always add
oYes: Process will be replaced
In case the process will be added these additional message are shown:
oNotification in case of:
When name was found, but adding of process is done due to always-add option enabled.
When new process is added
Messages for both replace as add:
oWarnings in case of
Webservice fields do not match source structure
Datastore parameter fields do not match source structure
Roles that refer directly to the process are not found (searched on name)
In case of update: Show roles that currently refer to the process to be replaced.
oErrors in case of:
References to fixed group can’t be found
Actors
Responsible Group
References to address book entry (email address) can’t be found
Actors
References to web services not found
Web service step
Global process webservice definitions
References to datastore parameter not found
In action steps
References to form not found
In action steps
References to person attributes not found
In variables initial value
In Variable definition steps
In action steps
Reference to global email templates not found
In notification, action and approval steps
Reference to layout not found (matched on name)
In notification, action and approval steps

Datastore parameters

Can the name of the datastore parameter be found?
oYes: datastore parameter will be replaced
oNo: datastore parameter will be added
In case the datastore parameter will be added
oNotification in case of:
When name was found but adding of process is done due to always-add option enabled.
New datastore is added
Messages in all cases:
oWarnings in case of:
Category doesn’t exist
oErrors in case of:
Connection string can’t be found (matched on name)
In case the import property category name can’t be found

Web Service

Can the name of the Web Service be found?
oYes: Web Service will be replaced
oNo: Web Service will be added
In case the Web Service will be added
oNotification in case of:
When name was found but adding of process is done due to always-add option enabled.
In case a web service is added
Messages in all cases:
oErrors in case of:
Connection string can’t be found (matched on name)