› Workflow › Business processes › Design a basic process › Add an activity › Activity types › Other activities › Document creation activity › Configure a Document creation activity

Configure a Document creation activity

Use the following procedure to configure a Document creation activity.

  1. Add an activity to the map.

    By default, the Configuration tab is open in the properties panel of the activity.

  2. Change the default Name of the activity to something meaningful.
  3. On the Type list, select Other > Document creation.
  4. Do one of the following to specify a document template.

    Select an existing template

    1. Select Load document template from store.

    2. On the Document template name list, select a document template.

    Specify the template for creating the document

    1. Clear Load document template from store.

    2. Do one of the following for the Document template name:

      • To provide a dynamic value, select the appropriate variable. The variable used for the template document must have a predefined value, which can be a location within the same computer. For example, (C:\Templates\Mytemplate.dotx); on a different computer within the same domain (\\192.68.0.108\Templates\MySite.dotx); or a URL.

        At runtime, if you try to provide a location other than the one specified at design time, the job is suspended.

      • To provide a static value, click , and specify the path to the template, such as C:\Templates\Mytemplate.

  5. Set the Format to be Document or HTML.
    Document
    1. To specify a location to save the document, do one of the following for Document save location.

      • To provide a dynamic location, select a document variable.

      • To specify a static location, click and enter the path, such as D:\Documents.

        The Designer running in on-premise multi-tenant or Azure environments does not support the static location to save the document.

    2. Specify a static or dynamic value in the Name box.

      You can use only a String variable or an XML Expression of any return type.

      At runtime, once the job is complete, the new Word document is automatically saved at the specified location or repository. If you save it in the repository, an instance ID is populated in the mapped document variable. You can use the instance ID in other capture activities.

    3. If a document with the same name already exists, the job is suspended at runtime. To avoid the job from being suspended, select Overwrite existing document.
    HTML
    1. Select a String variable or an XML expression of any return type as Output.
    2. At runtime, once the job is complete, the new HTML page is automatically saved to this variable.

    3. Map the variables from the process map to the corresponding placeholders in a template using a static or dynamic value. You can also map the document set properties to the document fields.

  6. Enter a static value or select a dynamic value for the placeholders. At runtime, the placeholders in the document are replaced with the values and the document is generated.

    TotalAgility supports String, Date and Dynamic Complex variables for placeholders.

  7. Save the process map.