Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

Input and Output for Create Map

Input and Output for Create Map

The input for the create map operation looks like the following example. You must provide a Plan Id for the running process instances to migrate. For your process request message that passes data to this operation, you can look up the Plan Id on the Active Process Detail page or obtain it programmatically in various ways, such as a using a database query or the appropriate Admin API call.
The following example show sample data. Note that the
toPlanId
is optional. If deleted, the default behavior is to map to the online version of the same process definition.
<migration:createMapRequest xmlns:migration="http://docs.active-endpoints/wsdl/migration/2011/04/migration.xsd"> <migration:fromPlanId>144</migration:fromPlanId> <!--Optional. If not used, defaults to the online plan of the pid:--> <migration:toPlanId>145</migration:toPlanId> </migration:createMapRequest>
The following example shows just the beginning of the migration map created for the response:
<createMapResponse xmlns="http://docs.active-endpoints/wsdl/migration/2011/04/migration.xsd"> <migrationMap><![CDATA[ <processMigration xmlns="http://schemas.activevos.com/processMigration/2010/05/processMigrationMapper.xsd"> <migrationInfo> <locationInfo> <locationId>1</locationId> <locationPath>/process</locationPath> <idsToRoot /> </locationInfo> <mapForVariable>false</mapForVariable> <migrationMapper> <oldLocationInfo> <locationId>1</locationId> <locationPath>/process</locationPath> <idsToRoot /> </oldLocationInfo> <activityStrategy> <stateMapType>0</stateMapType> <defaultLocationInfo> <locationId>1</locationId> <locationPath>/process</locationPath> <idsToRoot /> </defaultLocationInfo> </activityStrategy> </migrationMapper> </migrationInfo> ... </createMapResponse>

0 COMMENTS

We’d like to hear from you!