Home
Asset promotion
Asset Promotion facilitates the promotion of assets between a test, staging and a production environments.
Exporting assets
Prerequisites

EngageOne Compose
Create customized communications based on templates for optional review and approval using predefined workflows.
Tasks
Participate in predefined processes that manage the lifecycle of communications from design to delivery using predefined workflows.
Communications
A communication is created from a template and delivered to your customer at the end of the communication's life-cycle.
Templates
Templates are used as a base to create your final customer communication.
Editing and confirming data
Where data is pushed through the system, you may need to verify for the accuracy of pre-populated data, or enter missing data before the communication is edited.
Editing communications
Editing options allowing for creating and edit your customer communication using the selected template.
Selecting delivery options
Delivery options can be made up of one or more delivery channels and are configured by your EngageOne administrator.
Awaiting Delivery
Lists all documents that have been submitted for delivery but have not been delivered.
Search Archive
The Search Archive pane allows you to search documents from a selected database and view them based on communication type or month.
Design Review and Approval
Design Review and Approval provides a framework to ensure new and existing templates and active content are subject to quality control as part of a structured review and approval process.
Workflow and template management
This section describes the management of workflow and template processes.
Administration
Systems Administration and Community Administration options.
Asset promotion
Asset Promotion facilitates the promotion of assets between a test, staging and a production environments.
Copyright

Prerequisites

A maximum of 10 assets can be exported concurrently
For clustered environments:
- Up to 10 assets can be exported per node.
- The amount of export jobs is multiplied by the number of EngageOne core nodes in the cluster.
There is no limitation on how many export jobs can run at the same time in the system.
The exported files need to be accessible by the EngageOne server, in the directory where they will be imported.
The default directory is:
- Standalone EngageOne installations
  The directory can be a local server, or any network location where EngageOne has write access.
- Clustered EngageOne installations
  The directory must be a shared network location that each EngageOne node in the cluster has write access.

Note: To increase performance, use one shared location for both import and export.