Editing a PowerPack

This section describes how to edit a PowerPack, assign a new license key to a PowerPack that has already been installed, how to delete a PowerPack, and how to remove content from a PowerPack.

Use the following menu options to navigate the SL1 user interface:

• To view a pop-out list of menu options, click the menu icon ().
• To view a page containing all of the menu options, click the Advanced menu icon ().

Caveats

• Content can be included in only a single PowerPack. For example, if you include the Dynamic Application "Cisco: Summary Statistics" in the PowerPack "networking_powerpack", you cannot include that Dynamic Application in another PowerPack. If you want to include content in a second PowerPack, you must first remove the content from the first PowerPack. This is described in the section Removing Content from a PowerPack.
• When you delete a PowerPack, SL1 automatically deletes the associated content from the SL1 system and all data associated with it. For example, if a PowerPack includes a Dynamic Application, when you delete the PowerPack, the Dynamic Application is removed from SL1. If you go to the Dynamic Applications Manager page (System > Manage > Applications), that Dynamic Application will not appear. In addition, all data collected from all devices with that Dynamic Application will also be deleted.
• Device Classes and Device Categories are an exception to bullet above. When a PowerPack includes Device Classes or Device Categories, those Device Classes and Device Categories are not removed from the SL1 System when you delete the PowerPack.
• If you must delete a PowerPack but want to keep the installed content, you should first remove the content from the PowerPack. This is described in the section Removing Content from a PowerPack. To remove content from a PowerPack, you must either have administrator/owner privileges for the PowerPack or you must be the creator of the PowerPack. For details on privileges associated with PowerPacks, see the section on privileges in this chapter.
• If you want to include content in a second PowerPack, you must first remove the content from the first PowerPack. This is described in the section Removing Content from a PowerPack. To remove content from a PowerPack, you must either have administrator/owner privileges for the PowerPack or you must be the creator of the PowerPack. For details on privileges associated with PowerPack, see the section on privileges in this chapter.
• The privileges associated with a PowerPack's license key control the actions that users can perform after they install a PowerPack.
• Authors of PowerPacks are allowed to perform all editing actions on the PowerPack and its content. On the SL1 system where the PowerPack was created, only authors can edit the Publisher field for a PowerPack.
• If content in PowerPacks uses Intellectual Property Protection, you will not be able to edit the content on any system other than the system where the content was authored. This is true regardless of the license key associated with the PowerPack.
• If you include organization-specific credentials in a PowerPack, the credentials cannot be preserved by that organization when the PowerPack is installed on another environment. The credentials in a PowerPack are the responsibility of the customer, and cannot be guaranteed to be organization-specific in another SL1 system.

Privileges for Editing a PowerPack

On the system where the PowerPack is created, privileges are controlled by user-type (user or administrator) and access keys. Additionally, on the author system, the license key for a PowerPack endows author privileges.

On the system where the PowerPack is installed, privileges are controlled by the license key, and/or Intellectual Property Protection. When creating a PowerPack or a revision of a PowerPack, the author can assign privileges and capture those privileges in a license key. The following table describes privileges on the system where the PowerPack is installed.

NOTE: If the PowerPack contains one or more Dynamic Applications or event policies that use Intellectual Property Protection, users will not be able to edit the Dynamic Applications or event policies when they are installed on another system, even if the PowerPack includes Administrator/Owner privileges. 

Privilege	Actions
License Key from PowerPack Properties page	Provides author-level privileges for the author of the PowerPack on the author system. Authors can edit the content from within the PowerPack and in SL1. Authors are also allowed to edit the properties of the PowerPack, including the Publisher field, delete content from the PowerPack, export the PowerPack, and generate a license key for the PowerPack. For users of the PowerPack, the License Key is a field on the Properties page that displays the license key currently associated with the PowerPack.
License Key - Install and Use Only	Users will be allowed to install this PowerPack on another system (other than the author system). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. Users will not be allowed to edit any of the installed content, either from within the PowerPack manager or in their respective management pages.
Administrative (Including Export & License)	After installation on a system (other than the author system), users will be allowed to edit each of the installed items from this PowerPack. Users can edit the content from within the PowerPack and in SL1. Users will also be allowed to edit the properties of the PowerPack (but cannot edit the Publisher field), delete content from the PowerPack, export the PowerPack, and generate a license key for the PowerPack.
License Key - Dynamic Applications	After installation on a system (other than the author system), users will be allowed to edit the installed Dynamic Applications from the Dynamic Applications Manager page (System > Manage > Applications). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Event Policies	After installation on a system (other than the author system), users will be allowed to edit the installed event policies from Event Policy Manager page (Registry > Events > Event Manager). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access any other pages for the PowerPack.
License Key - Device Categories	After installation on a system (other than the author system), users will be allowed to edit the installed device categories from the Device Category Editor page (System > Customize > Device Categories). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Device Classes	After installation on a system (other than the author system), users will be allowed to edit the installed device classes from the Device Class Editor page (System > Customize > Device Classes). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Device Templates	After installation on a system (other than the author system), users will be allowed to edit the installed device classes from Configuration Templates page (Registry > Devices > Templates). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Device Groups	After installation on a system (other than the author system), users will be allowed to edit the installed device groups from the Device Groups page (Devices > Device Groups). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Reports	After installation on a system (other than the author system), users will be allowed to edit the installed report from the Reports tab. In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Dashboard Widgets	After installation on a system (other than the author system), users will be allowed to edit the installed dashboard-widget from the Dashboard Widgets page (System > Customize > Dashboard Widgets). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Dashboards	After installation on a system (other than the author system), users will be allowed to edit the installed dashboards from the Dashboards tab page. In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - SL1 Dashboards	After installation on a system (other than the author system), users will be allowed to edit the installed SL1 dashboards from the Dashboards page (). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Run Book Policies	After installation on a system (other than the author system), users will be allowed to edit the installed run book policies from the Automation Policy Manager page (Registry > Run Book > Automation). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Run Book Actions	After installation on a system (other than the author system), users will be allowed to edit the installed run book actions from the Action Policy Manager page (Registry > Run Book > Actions). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Ticket Templates	After installation on a system (other than the author system), users will be allowed to edit the installed ticket templates from the Ticket Templates page (Registry > Ticketing > Templates). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Credentials	After installation on a system (other than the author system), users will be allowed to edit the installed credentials from the Credential Management page (System > Manage > Credentials). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack. If the credential is organization-restricted on the author system, these restrictions won't apply on the target system.
License Key - Credential Tests	After installation on a system (other than the author system), users will be allowed to edit the installed credential tests from the Credential Test Management page (System > Customize > Credential Tests). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - UI Themes	After installation on a system (other than the author system), users will be allowed to edit the installed themes from the Theme Management page (System > Customize > Themes). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - IT Services	After installation on a system (other than the author system), users will be allowed to edit the installed IT service policies from the IT Service Manager page (Registry > IT Services > IT Service Manager). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Log File Monitoring Policies	After installation on a system (other than the author system), users will be allowed to edit the installed log file monitoring policies from the Log File Monitoring Policies page (System > Manage > Log File Monitoring Policies). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
License Key - Credential Fields	After installation on another SL1 system (other than the author system), users will be allowed to utilize the content type. In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. Users cannot access or edit any other pages for the PowerPack.
License Key - Guided Discovery Workflow	After installation on another SL1 system (other than the author system), users will be allowed to utilize the content type. In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. Users cannot access or edit any other pages for the PowerPack.
License Key - AP Content Objects	After installation on a system (other than the author system), users will be allowed to edit the installed AP Content Objects from the Content Management page (Manage > Content Management). In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. With only this privilege, users cannot access or edit any other pages for the PowerPack.
Intellectual Property Protection - Dynamic Applications	Adding Intellectual Property Protection to a Dynamic Application prevents users from viewing information required only for editing purposes, and from editing the Dynamic Application on any system except the system where the Dynamic Application was created. After installation on a system (other than the author system), users cannot disable the Intellectual Property Protection feature and can view only the Properties and Subscribers tab of the Dynamic Application (within the PowerPack or in the Dynamic Applications Manager page). Even if the PowerPack is installed with a license key that grants Administrator/Owner privileges, users won't be able to access all tabs for the Dynamic Application. When Intellectual Property Protections is enabled, the tabs below will not be displayed for the Dynamic Application: Collections Presentation Thresholds Snippets (for Dynamic Applications of type "snippet") Requests (for Dynamic Applications of type "SOAP" and "XSLT") Alerts
Intellectual Property Protection - Event Policies	Adding Intellectual Property Protection to an event policy prevents users from viewing information required only for editing purposes, and from editing the event policy on any system except the system where the event policy was created. After installation on a system (other than the author system), users cannot disable the Intellectual Property Protection feature and can view only the Policy and Suppressions tab of the event policy application (within the PowerPack or in the Event Policy Manager page). Even if the PowerPack is installed with a license key that grants Administrator/Owner privileges, users won't be able to access all tabs for the event policy. When Intellectual Property Protections is enabled, the tab below will not be displayed for the event policy: Advanced

Editing a PowerPack

If you have administrator rights for a PowerPack, you can edit an existing PowerPack.

If you have installed a PowerPack on a system other than the author system, your editing privileges are determined by the license key and/or intellectual property protection associated with the PowerPack.

To edit a PowerPack:

1. Go to the PowerPack Manager page (System > Manage > PowerPacks).
2. Find the PowerPack you want to edit and click its wrench icon ().
3. You can edit one or more fields in the PowerPack Properties page. For details on the Navbar for a PowerPack and their fields, see the section on Creating a PowerPack.

NOTE: If you edit a content item in the PowerPack (either from the Embedded pane in the Embedded/Available page or from a page in the user interface) after the PowerPack is installed or the last time the PowerPack was compiled (whichever is late), that content item will be highlighted in red and will have an updated date in the Last Edited column in the Embedded/Available page.

4. If you edited the PowerPack, you must rebuild the PowerPack and generate a new license key. For details, see the section Building the PowerPack and Generating a License Key.
5. When you have finished building the PowerPack and generating the license key, you can export the updated PowerPack. For details, see the Exporting a PowerPack section.

NOTE: Any edits applied to the PowerPack before you create a new build will be highlighted in red in the PowerPack pages.

Editing Dynamic Applications in a PowerPack

You cannot use a PowerPack to globally delete an existing collection object. When you install a PowerPack on multiple systems, and you log in to one of those systems and delete a collection object from a Dynamic Application in that PowerPack, you must then log in to each system and manually delete that collection object from each system. Saving the edited PowerPack and re-installing it will not perform a deletion. This is a behavior built into the PowerPack to protect your data.

For example:

• Suppose you have a PowerPack named PowerPack_test.
• Suppose PowerPack_test includes a Dynamic Application named DynApp_test.
• Suppose you install PowerPack_test on two systems, EM7_sys1 and EM7_sys2.
• Suppose you:

• Log in to EM7_sys1.
• Edit PowerPack_test.
• In PowerPack_test, edit DynApp_test.
• In DynApp_test, delete a collection object called my_object.
• Save PowerPack_test with a new version number.
• Export the new version of PowerPack_test.

• Suppose you log in to EM7_sys2 and install the new version of PowerPack_test.
• The updated PowerPack will not delete the existing collection object from EM7_sys2.
• After installing PowerPack_test, go to the Dynamic Applications Manager page (System > Manage > Applications). Open the Dynamic Application DynApp_test. Notice that the Dynamic Application still contains the collection object my_object.
• To remove the collection object, you must manually edit the Dynamic Application and delete the collection object. You cannot use an updated PowerPack to delete the collection object.

Generating a New License Key for the PowerPack

To learn how to generate a new license key for a PowerPack, see the sections on generating embedded and un-embedded license keys after the initial build in the section Creating a PowerPack.

Assigning a New License Key to an Already-Installed PowerPack

Suppose you want to change the privileges associated with an already-installed PowerPack, but you don't want to force the end-user to re-install the PowerPack. To do this, you can generate a new, un-embedded license key for the already-installed revision of the PowerPack.

The user of the PowerPack can then paste the new license key into the License Key field in the PowerPack Properties page for the PowerPack. To assign a new license key to an already-installed PowerPack:

1. Go to the PowerPack Manager page (System > Manage > PowerPacks).
2. Find the PowerPack you want to assign a new license key to. Click its wrench icon ().
3. In the PowerPack Properties page, click Build / Export.
4. In the Compiled PowerPacks / Generate Installation Key page, each revision of the PowerPack is displayed. To select the PowerPacks revision for which you want to generate an installation key, click its pencil and paper icon ().
5. In the License Key type field, you can now select if you want to embed the license key in the PowerPack, and if so, how you would like the embedded key to function. Choices are:

• Install & Use Only. After installation on another SL1 system (other than the author system), users will be allowed to edit only the name and version number of the PowerPack in the PowerPack Properties page. Users will not be allowed to edit any of the installed content, either from within the PowerPack or in SL1.
• Administrative (including export & license). After installation on another SL1 system (other than the author system), users will be allowed to edit each of the installed items from this PowerPack. Users can edit the content from within the PowerPack and in SL1. Users will also be allowed to edit the properties of the PowerPack, delete content from the PowerPack, export the PowerPack, and generate a license key for the PowerPack.
• Manage Content Items of Selected Types. After installation on another SL1 system (other than the author system), users will be allowed to edit the installed content type, from the associated page in the user interface. In the PowerPack Properties page, users will be allowed to edit only the name and version number of the PowerPack. Users cannot access or edit any other pages for the PowerPack.

6. Click the Generate Key button. When the new license key appears in the Generated Install Key field, copy the license key and paste it into a text file.

Deleting One or More PowerPacks

If you have the appropriate Access Keys, you can delete one or more PowerPacks from the PowerPack Manager page.

 When you delete a PowerPack, SL1 automatically deletes most PowerPack content from the SL1 system and all data collected by the PowerPack. For example, if a PowerPack includes a Dynamic Application, when you delete the PowerPack, the Dynamic Application is removed from SL1. If you go to the Dynamic Applications Manager page (System > Manage > Applications), that Dynamic Application will not appear. In addition, all data collected from all devices with that Dynamic Application will also be deleted. If you must delete a PowerPack but want to keep the installed content, you should first remove the content from the PowerPack. This is described in the section Removing Content from a PowerPack. To remove content from a PowerPack, you must either have administrator/owner privileges for the PowerPack or you must be the creator of the PowerPack. For details on privileges associated with PowerPacks, see the section on Creating a PowerPack.

When a PowerPack includes Device Classes or Device Categories, those Device Classes and Device Categories are not removed from the SL1 system when you delete the PowerPack. Device Classes and Device Categories are an exception to the Caution above.

To delete a PowerPack:

1. Go to the PowerPack Manager page (System > Manage > PowerPacks).
2. Find the PowerPack you want to delete. Click its checkbox ().
3. Click the checkbox for each PowerPack you want to delete.
4. In the Select Action drop-down field (in the lower right), choose Delete PowerPack(s).
5. Click the Go button.
6. In the pop-up window that appears, click the [OK] button.
7. The selected PowerPacks will be deleted from SL1.

Removing Content from a PowerPack

If you have the license key with author's privileges for a PowerPack or if you have owner/administrator privileges with your license key, you can remove content from a PowerPack. There are two situations where you might want to remove content from a PowerPack.

• If you must delete a PowerPack but want to keep the installed content, you should first remove the content from the PowerPack.
• Each piece of content in SL1 can be included in only onePowerPack. If you want to include content in a second PowerPack, you must first remove the content from the first PowerPack.
• You cannot use a PowerPack to delete existing collection objects from a Dynamic Application. For details, section on Editing a Dynamic Application in a PowerPack.

To remove content from a PowerPack:

1. Go to the PowerPack Manager page (System > Manage > PowerPacks).
2. Find the PowerPack you want to edit. Click its wrench icon ().
3. In the PowerPack Properties page, in the Navbar on the left side, select the option for the content you want to remove:

The entries under the Contents link are dependent upon your Access Hooks. An entry appears only if you have been granted an Access Key that contains the Access Hook that allows you to view the content-type in SL1. For example, the Dynamic Applications entry will appear under the Contents link only if you have permission to view the list of Dynamic Applications in the Dynamic Applications Manager page (System > Manage > Applications) in SL1.

• Dynamic Applications. Select this option to remove one or more Dynamic Applications from the PowerPack.
• Event Policies. Select this option to remove one or more event policies from the PowerPack.
• Device Categories. Select this option to remove one or more device categories from the PowerPack.
• Device Classes. Select this option to remove one or more device classes from the PowerPack.
• Device Templates. Select this option to remove one or more device templates from the PowerPack.
• Device Groups. Select this option to remove one or more device groups from the PowerPack.
• Reports. Select this option to remove one or more custom reports from the PowerPack.
• Dashboard Widgets. Select this option to remove one or more custom dashboard-widgets from the PowerPack.
• Dashboards. Select this option to remove one or more dashboards or device dashboards from the PowerPack.
• Dashboards SL1. Select this option to remove one or more SL1 dashboards from the PowerPack.
• Run Book Policies. Select this option to remove one or more custom run book policies from the PowerPack.
• Run Book Actions. Select this option to remove one or more custom run book actions from the PowerPack.
• Run Book Action Types. Select this option to remove one or more run book action types from the PowerPack.
• Ticket Templates. Select this option to remove one or more custom ticket templates from the PowerPack.
• Credentials. Select this option to remove one or more credentials from the PowerPack. If you delete an Embedded credential that is aligned to an organization you are not a member of, that credential will no longer be available to you.
• Credential Tests. Select this option to remove one or more credential tests from the PowerPack.
• UI Themes. Select this option to remove one or more UI themes from the PowerPack.
• IT Services. Select this option to remove one or more IT Services from the PowerPack.
• Log File Monitoring Policies. Select this option to remove one or more log file monitoring policies from the PowerPack.
• Credential Fields. Select this option to remove one or more credential fields from the PowerPack.
• Guided Discovery Workflow. Select this option to remove one or more guided discovery workflows from the PowerPack.
• AP Content Objects. Select this option to remove one or more AP content objects from the PowerPack.

4. In the Embedded/Available page for the content, go to the Embedded pane at the top of the page.
5. Find the content you want to remove from the PowerPack. Click the bomb icon () for that content. The content will be removed from the PowerPack and will now appear in the bottom pane.