Generating Process Version 1
In this table example, a Designer process named ProcessName has four steps.
Step Type | Step Label (Name) |
Message Start Event (receive) | CatchDocument |
Service Task | InvokeService |
User Task | DoSomething |
Message End Event (publish) | ThrowDocument |
The process uses two logical servers (Integration Server Names), both listed in the following table:
the default logical server | Default |
a second logical server | LogicalServer2 |
The first time the process is built (version 1), the package is generated. Its name is the same as the ProcessProjectName. Then a new process version is created (version 2), and the process is regenerated (built again).
Within the generated package, Designer creates a folder named ProcessName, which contains folders for each process version (ProcessName_1 and ProcessName_2), as well as the default logical server folder (Default) and the subscription trigger (subscriptionTrigger) used for all versions of the process. Designer creates the ProcessName_1 folder the first time the process is built. It contains the Integration Server Name folder (Default), which contains the following:
The table below lists the content of the Integration Server Name folder:
A flow service for the Message Start Event step. | CatchDocument |
A flow service for the Service Task step. | InvokeService |
A flow service for the User Task step. | DoSomething |
A transition trigger for version 1 of the process on this logical server (Default). | transitionTrigger |
The process also uses a second logical server called LogicalServer2, so Designer creates a folder for it under the ProcessName_1 folder. The Message End Event step (ThrowDocument) runs on LogicalServer2, and Designer generates the information listed in the following table in the LogicalServer2 folder:
A flow service for the Message End Event step. | ThrowDocument |
A transition trigger for version 1 of the process on this logical server (LogicalServer2). | transitionTrigger |