Importing and exporting content packages

To create a content package for the out-of-the-box data

After you move the content package for a line of business to your production or QA environment, you must move the content package for out-of-the-box data such as notification templates and acknowledgement templates for the line of business. To create a content package for the out-of-the-box data, perform the following steps:

1. Log in BMC Helix Innovation Suite as an administrator.
2. In Workspace, click Business Workflows.
3. Click Actions and select Create Content Package.
4. In the Create Content Package window, on the Select Definitions tab, do not select any definition, and click Next.
5. On the Add Data tab, select Email Acknowledgement Templates and Notification Templates.
6. In the Duplicates column, for Email Acknowledgement Templates and Notification Templates, select the Merge option.

1. Click Click to build an expression, on the Edit Expression page, enter the following expression:
   '450000420' = "<Name of the Line of business>"
   For example, 450000420 = "Facilities"
2. To export to-do task templates with questionnaires, export the service actions from BMC Helix Digital Workplace Catalog.
3. On the Package tab, click Create Package.
   After you create the content package, you can import it to the target system, where you want to move this data. To import the content package, see Deploying application tailoring changes.
   After importing the to-do task templates and service actions, deactivate and then activate the service actions from the BMC Helix Digital Workplace Catalog console to sync the questionnaire details with the to-do templates.

To create a content package for custom data

After you move the content package for out-of-the-box data to your production or QA environment, you must move the content package for custom data such as templates, Flowsets, documents, processes, and rules for the line of business. To create a content package for custom data, perform the following steps:

1. Log in BMC Helix Innovation Suite as an administrator. 

   Important

   If the export package contains any dynamic data that includes an attachment, the administrator must be assigned the Case Business Analyst functional role so that the dynamic data definition can be successfully imported.

2. In Workspace, click Business Workflows.
3. Click Actions and select Create Content Package.

4. In the Create Content Package window on the tabs displayed, perform the actions described in the following table:

   Tab Name	Action	Notes
   Select Definitions	Select the customized definitions you created for BMC Helix Innovation Suite, for example, documents (dynamic fields), processes, and so on.	This tab lists all the customized definitions you have created for BMC Helix Innovation Suite.
   Add Data	Select the data you want to export and click Next.	Do not remove any predefined qualifications. To add additional qualifications, add brackets to the current qualification, and use the AND operator to specify the qualifications. You can create content packages only for specific BMC Helix Innovation Suite data, if required. When exporting knowledge articles, you must select the knowledge article and the knowledge sets for which the articles have been created. To search for a particular ID, you must use the Article ID Internal field and not the Content ID field. When exporting service targets that use notification templates for milestones, you must also export those notification templates.
   	To filter the data to be exported, click Click to build a global data filter expression to enter selection criteria. For example, if you only want to export case templates defined for the Facilities line of business, enter the following expression: $450000420$ = <Domain ID of the Facilities line of business>
   	Ignore Rules—Do not select this option.	When importing data, the utility checks for duplicate records. Selecting this option bypasses all validations during data import.
   	Duplicates—Select one of these actions for duplicate data Ignore—Does not import the record if it exists in the system. Create New—Creates a new record with a different GUID even if the record exists in the system. Overwrite—Overwrites the existing record only if the fields Created Date and Owner are updated in the new record.  Merge—Update the delta part on the existing record Field exists and is populated - overwrite will replace the value and merge will append the data to the existing data.	To avoid errors, the recommended option is Merge.
   	Include configuration data in the package — Do not select this option.
   Order Data	Do not change the order displayed.	For BMC Helix Business Workflows, the order is predefined to the order in which the records need to be imported without errors.
   Approval Configuration	Select the group for which you want to export the approval configurations.	You have to export all approval flows created for a group and cannot select individual approval configurations.
   Assignment Configuration Select Definitions To Delete Options	Skip these steps when exporting data for BMC Helix Business Workflows.	These fields are not applicable for BMC Helix Business Workflowsexport. For details about these fields, see Deploying application tailoring changes.
   Package	Review the data items included and excluded and click Create Package.
   Download	To download the content package, click Download.

   After you create the content package, you can import it to the target system, where you want to move this data. 

5. To import the content package, see Deploying application tailoring changes.

To export a content use case

As an administrator, you can export an out-of-the-box content use case or a custom content use case from one environment to another. You can export one content use case at a time.

1. Log in to BMC Helix Business Workflows as an administrator.
2. Click Settings .
3. Select Content Use Cases Management > Content Use Cases.
4. Select a content use case from the list of use cases.
5. Click Export.
6. Save the file that is generated.

You can now import the content use case to your target environment.

Where to go from here