Merge

Merges multiple files that are on the Novunex platform into one single PDF file. If the files are not yet PDF files, they are converted to PDF files before they are merged. Apart from PDF files, also Microsoft Word files in the docx format and Microsoft Excel Files in the xlsx format are supported.

This Activity can have an arbitrary amount of Outcomes, but all Outcomes must have the same name. The script of each Outcome is evaluated once the Activity has completed. Each Outcome with a script evaluating to true is followed. If more than one Outcome script evaluates to true, the Instance is paralleled. If no Outcome script evaluates to true, the Instance is ended by entering the closed-state.

Activity config

General

• Name - Name of the Activity.
• Version - Version of this Activity used in the Process. If a new version of this Activity is available and you want to use it, you have to manually update the version here. When a new Activity is added to the Process, automatically the latest version is placed.
• Timeout in second - Once this time is elapsed, the Activity is closed and the Instance changes into the faulted-state. The default Timeout is two minutes. The timeout can be shortened and extended by entering a custom duration. If the Activity is left after a timeout, the first Outcome is followed. If multiple Outcomes have the same name as the first Outcome, all of them are followed. However, a continuation after a timeout does not effect the Outcome Scripts, meaning only Outcomes with Outcome Scripts evaluating to true are followed.
• Hide in process graph - Controls if the Activity is hidden (Yes) or shown (No) in the Process Graph on the Execution Screen.
• Continue on error - If this is set to Yes, the execution of the Instance continues even if the Activity failed. If set to No, the Instance fails when the Activity fails by entering the faulted-state. In the case of a continuation after an error, the first Outcome is followed. If multiple Outcomes have the same name as the first Outcome, all of them are followed. However, a continuation after an error does not effect the Outcome Scripts, meaning only Outcomes with Outcome Scripts evaluating to true are followed.

Merge Process

Merge Activity specific configurations

GENERAL

General interaction configuration, shared with most other Activities

• Disable activity - Disables (Yes) or enables (No) the Activity. When disabled, the Activity is not executed and passed like a Connection by following the first Outcome. If multiple Outcomes have the same name as the first Outcome, all of them are followed. Disabling the Activity does not effect the Outcome Scripts, i.e., still only Outcomes with Outcome Scripts evaluating to true are followed.
• Retry on error - If set to Yes, an automatic retry is executed up to ten times. If set to No, no retries are done. Retries are issued when the Activity failed so that the Instance would enter the faulted-state if the retry is disabled.
• Additional text for task list - Description of this Activity shown to the Users in their task list. You can enter this text directly or use Process Context Expressions to compile it.

SETTINGS

Configure what files will be merged

• Name - Name of the merged file entered directly or determined by a Process Context Expression
• URLs - List of all files that should be merged. The files are merged in the order of this list. The files must already exist on the Novunex platform. Each file is identified by its URL. A new URL is added by clicking Add and an URL can be deleted by clicking on . The URL can be entered as a fixed value string or it can be determined by a Process Context Expression. The URL of an Attribute of type File is accessed via .Url. For example, if the Variable is called MyEntity and the Attribute is called MyFile, then the URL can be accessed with the Process Context Expression #[MyEntity.MyFile.Url].
• Variable - The link to the resulting file is stored in this Variable. Here, an Attribute of type File of an existing Variable can be specified like MyVariable.FileAttribute. The Attribute is optional, if it is a Context Variable. If the Variable does not exist, a new Context Variable is automatically created.