Remote query deployment

Remote queries can be deployed with Perfion Deployment. This step in the wizard allow the user to select which remote queries should be deployed.

Selection

The wizard page for remote query selection is shown below.

The selection list contains all remote queries declared in the source system. Multiple remote queries can be selected.

Required remote queries

Remote queries can be required by feature definition deployment. The required remote queries will automatically be resolved, checked and greyed out in the selection list. The required remote queries cannot be unchecked in the selection.

Matching in target system

Remote queries are matched to remote queries in the target system. It is done by comparing the remote query name to the name of the remote query in the target system.

The match is done case sensitive. Some examples below:

If a match is found, the remote query is flagged for update instead of creation.

Remote Connections

Remote connections are also transferred with Perfion Deployment. They are deployed as a part of a remote query, so they are not selectable individually.

When a remote query is selected and it has an attached remote connection, the deployment will check it the remote connection exists in the target system. The existence check is done bare comparing the names of the remote connections in the target system. This is done case sensitive.

When the deployment finds a match in the target system, the remote query will point to the target remote connection and use this. If the remote connection is not found in the target, a new remote connection is created in the target system. Its values are copied from the source remote connection. See some examples below.

Example 1

Remote requires connection that does not exist.

Before deployment:

After deployment:

Example 2

Remote requires connection that exist.

Before deployment:

After deployment:

Data transfer

All data values for remote queries are deployed when a remote query is transferred.