Package Manager
Overview
Package Manager is an Import/Export functionality that allows you to view, create, edit, delete, download, upload, and install packages of content. The Package Manager allows transfer of content from one Resolve Actions Pro installation to another.
It is an alternative to GIT Runbook and Action Task content exchange and in addition it extends the platform capabilities to exporting-importing content and system components that are not under GIT synchronization (Properties, Gateway Filters, Menus, Users, System Properties, Forms, etc.).
Package Manager Introduction
The Package Manager allows you to archive or transfer Actions Pro components, and to:
- Create a backup of your content;
- Copy your content to another Actions Pro installation, such as a backup machine or a new installation;
- View packages that have been created, downloaded, or installed on the system.
- Select which component/s to include or exclude from your package.
- See the dependencies of an object hierarchically.
- Filter and preview the components prepared for export by types.
- Set global or individual export options to ensure the proper parts of the components are in the package.
Accessing the Package Manager
As the Package Manager is based on access rights, you will be able to see only content or Namespace to which you have at a minimum read access.
To access this functionality, go to Main Menu > Import Export > Package Manager.
The Package Manager Dashboard appears.
Package Manager Dashboard
The Package Manager Dashboard displays a paginated list of all packages that are installed or created in the system. By default, 20 packages are displayed per page. You can see a package's name and Actions Pro version, whether it has been installed, short description and latest update of a package, and who made the latest update. From this Dashboard you can also create, edit, download, upload, install, or delete packages.
The Installed column shows the package status. The green checkbox icon means "installed" and the grey crossed-out icon means "not-installed". The icons are used according to the package state as follows:
- Locally created and exported package - not installed
- Locally created and installed package - installed
- Re-installed package - installed
- Package which failed to be installed - not installed
- Uploaded package - not installed
- Edited package which is re-exported - installed
The Refresh button refreshes the list of packages so that the last updated package is ordered on top of the grid.
Search Options
In the Package Manager Dashboard, you can search for packages by a keyword that is part of the package name or description. To search for a specific package in the system, enter your query in the Search field. The search is case insensitive and returns partial and full matches to a query.
Package Actions
From the Actions drop-down menu, you can create a new package, edit an existing package, download a package, or delete a package.
Creating New Package
Allows you to start a new package creation from local content.
To create a package that you can install on other Actions Pro systems:
- Go to the Actions drop-down menu and click New Package.
The Create Package page opens at step 1, Select Components, with all Actions Pro component types available to be added to a package. - Select components to include in the package: Runbooks, Page Resources, ActionTasks, Forms, and so on.
You can search for objects, such as namespaces, Runbooks, ActionTasks, Forms, and Properties. You can also search for a specific component by component name or namespace. Use the dot notation for namespaces. For example:System.Doc. The search is case insensitive and returns partial and full matches to a query.- Some components allow you to select subcomponents. Use the arrow next to the component name to expand the list.
- Click Continue.
The Configure screen appears. - Review the components and subcomponents that you selected. note
A component could appear in a hierarchy more than once.
- In the right panel, provide a Name for the .zip file.
The Description field is optional. - Set package options.
- Click Export.
A Created Package window appears, allowing to download it or view the results. The new package is displayed at the top of the Package Manager list.
During the package creation process, you can switch to another screen or do another task, while the process is running in the background.
Once the creation process is completed, you can open or download the package. Select the package name in the Package Manager, open the Actions menu, and click Download.
When saving a package, the following message may be displayed: "Upload File IMPEX operation by user admin is in progress, please try later". If such message appears, simply repeat the operation at a later point.
Component Types
Use the following table to identify the various component type that you can export using a package.
| Component tab | Sub-tab | Description |
|---|---|---|
| Runbooks | no | Lists all Runbooks with their Pages, Decision Trees and Automations in a nested tree structure sorted by the timestamp of last updated Runbook from top to bottom. The three Runbook components are only indicative and cannot be selected separately. A Runbook is listed here if it contains a standalone Automation, standalone Decision Tree or a combination of Page + Automation, Automation + Decision Tree, Page + Automation + Decision Tree. |
| Action Tasks | no | Lists all ActionTasks sorted by the timestamp of the last updated task from top to bottom. |
| Namespaces | no | Lists all namespaces that contain at least one Action Task, Runbook, or Property sorted by the timestamp of last updated namespace from top to bottom. Empty namespaces are not present. |
| Properties | no | Lists all ActionTask properties sorted by the timestamp of the last updated Action Task Property from top to bottom. |
| Forms | no | Lists all Forms sorted by the timestamp of the last updated one from top to bottom. |
| Tables | no | Lists all custom tables sorted by the timestamp of the last updated one from top to bottom. |
| Gateway FiltersGateway Companion Filters | no | Lists all Gateways with their deployed Gateway Filters and Runbooks that are associated with the filters in a nested tree structure sorted by the timestamp of last updated Gateway Filter from top to bottom. The Gateway structure is expandable and the next level of the nested structure represents the Gateway Filters related to the Gateway. |
| Resolution Routings | Mappings Schemas | Mappings lists all Resolution Routing Mappings sorted by the timestamp of last updated one from top to bottom. It is an expandable component which allows the user to preview its Schema dependencies and schema fields and values associated with that mapping. Schemas lists all Resolution Routing Schemas sorted by the timestamp of last updated one from top to bottom. |
| Page Resources | Pages Page Lookups Page Templates Catalogs | Runbooks that contain only Page content are listed in the Pages sub-tab and are sorted by the timestamp of last updated one Page top to bottom. Page Lookups are sorted by the timestamp of the last updated one from top to bottom. Page Templates are sorted by the timestamp of the last updated one from top to bottom. Catalogs are sorted by the timestamp of the last updated one from top to bottom. |
| Menus | Menu Sets Menu Definitions Menu Items | Menu Sets lists all menu sets sorted by the timestamp of last updated one from top to bottom. It is an expandable component which allows the user to preview the Menu Definitions that belong to that set. Menu Definitions lists all Menu Definitions sorted by the timestamp of last updated one from top to bottom. Each Menu Definition item can be expanded/collapsed which allows the user to see all Menu Groups and individual Menu Items that are part of the Menu Definition. The nested items under Menu Definition (Menu Groups and Menu Items) are not selectable. They are all selected as one entity. Each Menu Group can be expanded/collapsed to provide visibility of the Menu Items in it. Menu Items are sorted by the timestamp of last updated one from top to bottom. |
| Users | Users Groups Roles | Users are sorted by the timestamp of last updated one from top to bottom. Groups are sorted by the timestamp of the last updated one from top to bottom. Roles are sorted by the timestamp of the last updated one from top to bottom. |
| System | System Properties System Scripts Metric Thresholds Schedulers Tags | Lists all system properties sorted by the timestamp of the last updated one from top to bottom. Lists all system scripts sorted by the timestamp of the last updated one from top to bottom. Lists all metric threshold rules sorted by the timestamp of the last updated one from top to bottom. Lists all schedulers sorted by the timestamp of the last updated one from top to bottom. Lists all tags sorted by the timestamp of the last updated one from top to bottom. |
Setting Package Options
After providing the package Name and an optional Description and selecting all the necessary components for the new package, you can specify the export options that need to be applied to the entire group of items per component type or set individual export options that will be applied per single item.
The size of the package can be increased significantly based on the export options applied to the selected items as it allows export of additional components which were not initially selected at step 1, but are needed in order to preserve the content integrity. Preserving the overall stability and integrity of the components and content is responsibility of the administrator user setting the export options entirely. It is possible to exclude essential components that are part of the items selected for export, which can introduce risks to the exported content.
Most of the component types that are subject of export support a list of global export options that add flexibility to the package and ability to customize the content that will be exported. However, there are components that are exported as is. The list of components that do not any support export options is:
- Properties
- Wiki Lookups
- Menu Items
- Schedulers
- System Properties
- System Scripts
- Tags
Use the Configuration by component drop-down list to preview and filter the different component types and their option, and then use the check boxes to set global export options for the selected type.
Use the Edit link next to each exported item on the left to edit export options individually. Setting an individual export option is making an exception from the general export rules. The individual export options always take precedence over the global export options.
Package Options for Runbooks
| Export options | Selected by default | Description |
|---|---|---|
| Include Sub Runbooks and Sub Decision Trees | yes | Exports all sub-Automations and sub-Decision Trees linked the main model and decision tree model. The sub components could be part of a Runbook that resides in a different Namespace. |
| Include Action Tasks | yes | Exports all Action Tasks from the Runbook. The Action Tasks could be in a separate Namespace. |
| Include Custom Forms | yes | Exports all Custom Forms assigned to the Page of the Runbook. |
| Include Tags | yes | Exports all Tags assigned to the Runbook. |
| Include Catalogs | no | Exports all Catalogs associated with the Runbook. |
Package Options for ActionTasks
| Export options | Selected by default | Description |
|---|---|---|
| Include all Properties related to Action Tasks | yes | Exports all Action Task Properties. The properties could be in a separate Namespace. |
Package Options for Namespaces
| Export options | Selected by default | Description |
|---|---|---|
| Include all Runbooks in Namespace | yes | Exports all Runbooks that belong to the selected Namespace. |
| Include all Action Tasks in Namespace | yes | Exports all Action Tasks that belong to the selected Namespace. |
| Include all Properties in Namespace | yes | Exports all Properties that belong to the selected Namespace. |
| Include all Properties related to Action Tasks | yes | Exports the Properties which are assigned to work with the Action Tasks in the selected Namespace. The namespaces in which these Properties reside might not be selected in the export list but the properties are exported in order to grant the user that the Action Tasks will continue working. |
| Include all Custom Forms related to Runbooks | yes | Exports the Forms which are assigned to work with the Runbooks in the selected Namespace. The namespaces in which these Forms reside might not be selected in the export list but the Forms are exported in order to grant the user that the Runbooks will continue working. |
| Include all Action Tasks related to Runbooks | yes | Exports the Action Tasks which are assigned to work with the Runbooks in the selected Namespaces. The Namespaces in which these Action Tasks reside might not be selected in the export list but the Action Tasks are exported in order to grant the user that the Runbooks will continue working. |
| Include all Sub Runbooks and Sub Decision Trees | yes | Exports the sub-Runbooks and sub-Decision Trees which are assigned to work with the Runbooks in the selected Namespaces. The namespaces in which these sub-Runbooks and sub-Decision Trees reside might not be selected in the export list but the sub-Runbooks and sub-Decision Trees need to be exported in order to grant the user that the Runbooks will continue working. |
| Include all Tags related to Runbooks | yes | Exports all Tags which are assigned to the Runbooks in the selected Namespaces. |
Package Options for Properties
No export options. Exports all selected Properties.
Package Options for Tables
| Export options | Selected by default | Description |
|---|---|---|
| Include Custom Tables | yes | Exports all the Tables in the select Forms. |
| Include Data | yes | Exports all the data from the Tables included in the selected Forms. |
| Include Runbooks | yes | Exports all Runbooks that have Pages containing the selected Forms. |
| Include System Scripts | yes | Exports all System Scripts associated with the selected Forms. |
| Include Action Tasks | yes | Exports all Action Tasks associated with the selected Forms. |
Package Options for Forms
| Export options | Selected by default | Description |
|---|---|---|
| Include Custom Forms | yes | Exports all the Forms containing the selected Tables. |
| Include Data | yes | Exports all the data from the selected Tables. |
Package Options for Gateway Filters
If a Gateway Filter is associated with an Automation then the exported package includes the Automation, its Action Tasks and if other sub-Runbooks are related to the exported Action Tasks they are included in the package as well. The same is valid for the Properties - if the Action Tasks are associated with some Properties they are exported. The Action Tasks and Properties under the sub-Runbooks are included in the package as well.
| Export options | Selected by default | Description |
|---|---|---|
| Include Email Addresse(s) Items | no | Exports Email Addresses |
| Export Remedyx Form | no | Export Remedyx Form |
| Include EWS Addresse(s) | no | Export EWS Addresses. |
Package Options for Resolution Routing Mappings
All exported Resolution Routing Mappings always include the Schemas that are referenced within.
| Export options | Selected by default | Description |
|---|---|---|
| Include UI Page | yes | Exports the Page that is assigned in the "UI Display" tab of the mapping. |
| Include UI Automation | yes | Exports the Automation that is assigned in the "UI Display" tab of the mapping. |
| Include Gateway Automation | yes | Exports the Automation that is assigned in the "Gateway" tab of the mapping. |
Package Options for Resolution Routing Schemas
| Export options | Selected by default | Description |
|---|---|---|
| Include Mappings | yes | Export the Resolution Routing Mappings that reference all the selected Schemas. |
Package Options for Pages
| Export options | Selected by default | Description |
|---|---|---|
| Include Sub Runbooks and Sub Decision Trees | yes | Exports all sub-Automations and sub-Decision Trees that are part of Runbooks added as components to the Page. The sub components could be part of a Runbooks that resides in a different Namespace. |
| Include Action Tasks | yes | Exports all Action Tasks added as components to the Page. The Action Tasks could be in a different Namespace. |
| Include Custom Forms | yes | Exports all the Forms added as components to the selected Pages. |
| Include Tags | yes | Exports all Tags which are assigned to the Action Tasks. |
| Include Catalogs | no | Exports all Catalogs associated with the Action Tasks. |
Package Options for Page Templates
| Export options | Selected by default | Description |
|---|---|---|
| Include Custom Forms | yes(since Resolve v7.1) | Exports all the Forms added as components to the selected Page Templates. |
| Include Page Template | yes | Exports all the Templates. |
Package Options for Page Lookups
No export options. Exports all selected Page Lookups.
Package Options for Catalogs
| Export options | Selected by default | Description |
|---|---|---|
| Include Pages | yes |
Package Options for Menu Sets
| Export options | Selected by default | Description |
|---|---|---|
| Include Menu Definitions | yes | When only "Include Menu Definitions" export option is selected it exports all definitions (menus) added to the selected menu sets without the menu items in them. |
| Include Menu Items | yes | When only "Include Menu Items" export option is selected it exports all items included in the menu definitions that are included the selected menu sets but without the menu definitions themselves. It exports only the sets and the items.When both "Include Menu Definitions" and "Include Menu Items" export options are selected it exports all items along with their definitions that are added to the selected menu sets.When both "Include Menu Definitions" and "Include Menu Items" export options are deselected it exports only the menu sets but empty - no definitions and no items in them. |
Package Options for Menu Definitions
| Export options | Selected by default | Description |
|---|---|---|
| Include Menu Items | yes | Exports all items that are added to the selected Menu Definitions. |
Package Options for Menu Items
No export options. Exports all selected menu Items.
Package Options for Users
| Export options | Selected by default | Description |
|---|---|---|
| Include Role Relations | no | Exports all role relations that are assigned to that user.Exporting role relations means the User is exported with all its mappings to the roles assigned to that group at the moment of the export. This does not mean it exports the role objects but only the existing relations between them and the users. |
| Include Group Relations | no | Exports all user groups to which that user belongs to.Exporting group relations means the User is exported with all its mappings to the groups to which it belongs to at the moment of the export. This does not mean it exports the groups objects but only the existing relations between them and the users. |
| Insert Only If Not Present | no | Determines what user data will be overwritten on import on another Actions Pro instance if the user account already exists there. If the option is unchecked, all user attributes are overwritten with the data from the export package, including user profile information, groups, roles, and organizations. If the option is checked, only groups, roles, and organizations are overwritten with the data from the export package. The import process uses the User ID to determine if the user is the same. |
Package Options for Groups
| Export options | Selected by default | Description |
|---|---|---|
| Include User Relations | no | Exports all user relations to the selected user groups.Exporting user relations means the Group is exported with all its mappings to the users assigned to that group at the moment of the export. This does not mean it exports the user objects but only the existing relations between them and the groups. |
| Include Role Relations | no | Exports all role relations to the selected user groups.Exporting roles relations means the Group is exported with all its mappings to the roles assigned to that group at the moment of the export. This does not mean it exports the role definitions but only the existing relations between them and the groups. |
Package Options for Roles
| Export options | Selected by default | Description |
|---|---|---|
| Include User Relations | no | Exports all relations to the users that are assigned with that role.Exporting user relations means the Role is exported with all its mappings to the users assigned with that Role at the moment of the export. This does not mean it exports the user objects but only the existing relations between them and the Role. |
| Include Group Relations | no | Exports all relations to the groups that are assigned with that role.Exporting group relations means the Role is exported with all its mappings to the groups assigned with that role at the moment of the export. This does not mean it exports the Group definitions but only the existing relations between them and the roles. |
Package Options for System Properties
No export options. Exports all selected System Properties.
Package Options for System Scripts
No export options. Exports all selected System Scripts.
Package Options for Metric Threshold
| Export options | Selected by default | Description |
|---|---|---|
| Include All Versions | yes | Exports all versions of the Metric Threshold rules that are selected. |
Package Options for Schedulers
No export options. Exports all selected Schedulers.
Package Options for Tags
No export options. Exports all selected Tags.
Namespaces export options specifics
When exporting entire Namespace but there are only Action Tasks in it, these are the two export options that will be applied to the selected list :
- Include all Action Tasks in Namespace
- Include all Properties related to Action Tasks
When exporting entire Namespace but there are only Runbooks in it these are the five global export options that will be applied to the selected list :
- Include all Runbooks in Namespace
- Include all Custom Forms related to Runbooks
- Include all Action Tasks related to Runbooks
- Include all Sub Runbooks and Sub Decision Trees
- Include all Tags related to Runbooks
When exporting entire Namespace but there are only Properties in it, there is one global export option that will be applied to the selected list:
- Include all Properties in Namespace
The following table explains the global namespace export options applied to the package in the context of the exported content.
Content type in the Namespace | Runbook | Action Task |
|---|---|---|
Property | Include all Runbooks in Namespace | Include all Action Tasks in Namespace |
Action Task | Include all Runbooks in Namespace | - |
Menu Sets export options specifics
When only "Include Menu Definitions" export option is selected it exports all definitions (menus) added to the selected menu sets without the menu items in them. After a successful package import :
- the imported Menu Set/s are represent in the Menu Set main page.
- the imported Menu Definition/s are present in the Menu list when creating new menu set or updating an existing one.
- the imported Menu Definition/s are represent in the Menu Definition main page.
When only "Include Menu Items" export option is selected it exports all items from the menu definitions that are included the selected menu sets but without the menu definitions themselves. It exports only the sets and the items. After a successful package import:
- the imported Menu Set/s are represent in the Menu Set main page.
- the imported Menu Item/s are found only in Package Manager "Menu Items" sub-tab. They are not listed anywhere else in the UI because their definitions were excluded on export.
When both "Include Menu Definitions" and "Include Menu Items" export options are selected it exports all items along with their definitions that are added to the selected menu sets. After a successful package import:
- the imported Menu Set/s are present in the Menu Set main page.
- the imported Menu Definition/s are present in the Menu list when creating new menu set or updating an existing one.
- the imported Menu Definition/s are present in the Menu Definition main page.
- the imported Menu Item/s are present in their parent Menu Definition page.
When both "Include Menu Definitions" and "Include Menu Items" export options are deselected it exports only the Menu Sets but empty - no definitions and no Items in them. After a successful package import:
- the imported Menu Set/s are present in the Menu Set main page.
- the menu definitions are not there, so they are not listed in the Menu Set details page when creating a new menu set or updating an existing one.
Users export options specifics
When "Include Role Relations" export option is selected it exports the User with all its mappings to the roles assigned to that group at the moment of the export.
- If the user explicitly includes the roles from "Roles" sub-tab and exports them in the same package, then the roles and the specific users assigned with these roles are imported on the target system.
- If the role objects are not included in the package but they pre-exist on the target system, they are automatically related to the users after successful package import because the relations between the users and the roles were exported.
When "Include Group Relations" export option is selected it exports the User with all its mappings to the roles assigned to that group at the moment of the export.
- If the user explicitly includes the groups from "Groups" sub-tab and exports them in the same package, then the users and the specific groups to which they belong to are imported on the target system.
- If the group objects are not included in the package but they pre-exist on the target system, they are automatically related to the users after successful package import because the relations between the groups and the users were exported.
- When both export options are unselected only the Users are exported without the mapping to their roles or groups.
Groups export options specifics
When "Include User Relations" export option is selected it exports the Group with all its mappings to the users assigned to that group at the moment of the export.
- If the user includes the users from "Users" sub-tab and exports them in the same package, then the groups and the specific users added to the groups are imported on the target system.
- If the user objects are not included in the package but they pre-exist on the target system, they are automatically related to the groups after successful package import because the relations between the groups and the users were exported.
When "Include Role Relations" export option is selected it exports the Group with all its mappings to the roles assigned to that group at the moment of the export.
- If the user includes the roles from "Users" sub-tab and exports them in the same package, then the groups and the specific roles added to the groups are imported on the target system.> If the role definitions are not included in the package but they pre-exist on the target system, they are automatically related to the groups after successful package import because the relations between the groups and the roles were exported.
When both export options are unselected only the Groups are exported without the mapping to their roles or users.
Roles export options specifics
When "Include User Relations" export option is selected it exports the Roles with all its mappings to the users assigned with that Role at the moment of the export.
- If the user includes the users from "Users" sub-tab and exports them in the same package, then the Roles and the specific users assigned with the Roles are imported on the target system.> If the user objects are not included in the package but they pre-exist on the target system, they are automatically related to the Roles after successful package import because the relations between the Roles and the users were exported.
When "Include Group Relations" export option is selected it exports the Roles with all its mappings to the groups assigned with that role at the moment of the export.
- If the user includes the groups from "Groups" sub-tab and exports them in the same package, then the groups and the specific roles assigned to the groups are imported on the target system.> If the group definitions are not included in the package but they pre-exist on the target system, they are automatically related to the roles after successful package import because the relations between the groups and the roles were exported.
When both export options are unselected only the Roles are exported without the mapping to their groups or users.
Editing Packages
Editing allows you to modify the content of existing packages and prepare it for re-export.
To edit an existing package, select it, go to the Actions drop-down and click Edit. You can edit only one package at a time and only packages that were created using the Package Manager. The Edit option is disabled for packages created using the Import-Export Module.
A new dialog window appears. To add components to the ones already existing in the package, click the Select Components tab at the top of the dialog window. Once you have finished selecting additional components, go back to the Configure tab and make any changes to the package name or options. Click the Export button to complete the operation. For further details about the export options, how to apply them, and component specifics refer to Setting Package Options.
This action is available only if:
- The selected package is not form the default Resolve system packages.
- There is only one selected package. If more than one package is selected in the Package Manager Dashboard, the "Edit" action is disabled and grayed out.
- The content from the selected package is present on the instance locally. This can be any installed package or a package that is exported from this instance and marked as not installed.
- The package is exported from version 7.1 or later. Editing an installed package which is exported from an instance running a version prior to 7.1 is not possible.
Downloading Packages
You can download one or more packages available in the Package Manager list. To do this, select the required package/s, go to the Actions menu and click Download.
Deleting Packages
Deleting permanently removes the package from the Actions Pro instance. Deleting a package does not affect the content that is installed from it. All packages, regardless if custom or default Resolve, can be deleted at any time.
You can delete packages from the dashboard. To do it, select one or more packages, select the Delete option under the Actions menu, and then confirm the action.
Uploading Packages
To upload a .zip file as a package, go to the Actions drop-down and click Upload. You can upload one package at a time. All packages, regardless if custom or default Resolve, can be uploaded at any time.
If the .zip file does not match the Actions Pro package structure, the upload fails.
A new dialog window appears. Click the Browse your device link to select a package, or drag and drop a file for upload.
After a successful unzip of the resolve .zip package an Upload Package pop-up appears on screen. The package can be installed directly on the system or the user can inspect the package content, making sure that everything needed is in place and then proceed with the package installation.
Click Upload Only to upload the package and postpone the content installation. After successful package upload the package appears at the top of the dashboard grid list. The icon in the Installed column indicates that the package is not yet installed.
Click Overwrite to overwrite the old package with the new one. Click Do not overwrite and save as new package button to upload the new package as a copy. Regardless of the .zip file original name, it is automatically replaced same as the one of the package that already exists on the system with an added suffix -1. This provides a hint to the user that the content of both packages is duplicated and one of the packages is a copy.
There is a system property setting for the maximum size of the package that can be uploaded. This is a configurable setting in System Properties page:
fileupload.max.size =100
It is the maximum allowable size, in MBytes, for an item. The max file size can be increased or reduced at any time but this may lead to a decrease in the upload time and performance. The recommended .zip size is 100 MBytes.
Packages that are uploaded but not yet installed cannot be edited. However, the user can proceed with the installation by selecting the dedicated Install action option.
Installing Packages
The Install option is suitable for packages that are uploaded but not yet installed or packages that are already installed but the content has been deleted and a package re-install is required. Only one package can be installed at a time.
To install a package, go to the Actions drop-down and click Install. You can install only one package at a time. All packages, regardless if custom or default Resolve, can be installed at any time. Installed packages can be re-installed.
Click Preview Package to preview the package content in a hierarchical grid view before installation. Click Install to start the installation process. Each time a package is installed successfully the "Installed On" date and time stamp is updated. The icon in the Installed column reflects the success status.
The components which are new to this Actions Pro instance are marked with label new, components which are not new but are different form the ones that exist locally are labeled different, the components that are the same as the ones on the local instance are labeled same. This is an indicator to the user that some of the content might already exist but will be overwritten. This carries risks of losing some customized content or breaking a functional Runbook.
To exclude those items that are not needed, click on the checkbox before the item. By default all items in the "Preview Package" are selected but they can all be deselected one by one or with the "Select/Deselect all" global option. The "Select/Deselect all" option is applied to all content on all pages.
In case you attempt to install a package that has been created in a legacy version of the Import/Export functionality, a warning message appears. You can still install the package or selected objects that are part of it, but it is recommended that you use the Import Export Module for this purpose.
Additionally, you can use the Search Components box on the dialog window to find specific component/s to install. While you search for components, the selected one/s remain in this status and switching between pages does not deselect them. In the above dialog window, you can see the subcomponents to be installed, by clicking the Expand All button. To close them, simply click on the Collapse All button.
Once you are finished selecting the components to install, click the Install button. The install package dialog window is closed and the Import Export Status window displays the status of your installation.
Once the installation is completed, you can view the system's log information regarding the installation. To do this, click on the name of the package or on the status of the installation, whether it is Done, Warning or Error, in the Import Export Status window.
In case you attempt to import existing content, a warning for the risk of the content override will appear. This way you will be able to inspect the content prepared for import and, if necessary, customize it.
Import Export Log
The Import Export Log is a convenient log that lists all importing and exporting activities. To access it, go to Main Menu > Import Export > Import Export Log.
Troubleshooting
The rsview.log is where Package Manager ERRORs are printed. IT can be accessed on the local Actions Pro instance with:
tail -f /opt/resolve/tomcat/logs/rsview.log