Add Artifacts to a Package Template

You can add an item to a package template using the Add to Package Template shortcut menu.

Note: You can package only published artifacts. Thus, the Add to Package Template option is available only for the published items.

In this illustration, Database Lookup is used as an example of list items artifact.

1. Log on to the Enterprise Console.

2. In the Enterprise Console, click the Menu button, click Settings, and then click Lookup Settings.
   The Lookup Settings list appears.

3. Select the Database Lookup that you want to package.

4. Right-click the Database Lookup and then click Add to Package Template.
   The Add to Package Template dialog box appears.

5. Select an existing package template from the Package Template list. Package templates in the Draft status appear in the Package Template list.

   OR

   Create a new package template by performing the following:

   1. Select Create Package Template from the Package Template drop-down list. The New Package Template page appears.

   2. Enter the title and description for the package template in the Title and Description fields respectively.

   3. In the Target Platform section, select either 32-bit or 64-bit based on the machine where the package needs to be installed.

   4. Click Save Template. The Package Template list is updated with the newly created package template.

6. In the Package Template Version drop-down list, select the version of the package template. By default, the version is updated as 1.

7. In the Include Associated Artifacts section:

   • Select Yes to package all the associated artifacts of the selected artifact. For example, for the Database Lookup example here, if you select Yes, the associated database connection is also added to the package template. The associated artifact of the database lookup is a database connection.

   • Select No to exclude the associated artifacts of the selected artifact. For example, for the Database Lookup example here, if you select No, the associated database connection is not added to the package template.

8. In the Include Child Artifacts section:

   • Select Yes to package all the child artifacts of the selected artifact. Here, the child artifacts of the associated artifact is also added to the package template. For example, if Database Lookup has child lookups, the child lookup can also be packaged by selecting Yes.

   • Select No to exclude the child artifacts of the selected artifact from the Package Template.

9. In the Include Security Artifacts section:

   • Select Yes to package all the security rights of the selected artifact.

   • Select No to exclude the security rights of the selected artifact from the Package Template.

   Note: You can see the Include Security Artifacts option only if you enable the security group customization of the artifact at the List Item level.

10. In the Include the automatically generated SQL Script section:

    • Select Yes to include the automatically generated SQL Script for the artifact to the package template.

    • Select No to exclude the automatically generated SQL Script for the artifact to the package template.

    Note: The Include the automatically generated SQL Script option is available only for Lookup Settings, Manage List pointing to existing table, Queue, and Workflow with Database activity.

11. Click Next.

    The Add to Package Template page appears. On the left pane, you can see the artifact Database Lookup. You can make all required changes to the configuration settings and prerequisites.

12. Click Save Template.

    The Database Lookup along with the configuration settings and prerequisites is saved to the Package Template.

    Note: When you select the Include Associated Artifacts option as Yes while adding an item (or artifact) to a Package Template, the associated artifacts are added to the package template. You can then view the associated artifacts of the item in the tree view of a Package. If you select the Include Associated Artifacts option as No, the associated artifacts are not added to the package template. Then, you cannot see the associated artifacts in the tree view of a Package. This condition holds good for both the Include Child Artifacts and Include Security Artifacts options as well. In the case, when you do not have any child artifact, selecting the Include Child Artifacts option as Yes or No does not make any difference.

See Also

Configuring a Package Template