Upgrading legacy solutions to LiveCycle ES2.5

Create an xml variable:

1. In the Variables view, click Create New Variable .

2. In the Name box, type a name for the variable, following these naming rules:

   • Must be a valid XML element name that contains only valid XML characters.

   • Must not start with a digit.

   • Must be less than 100 characters long.

   • Must be unique and therefore cannot be id , create_time , update_time , creator_id , or status , which are reserved variables always in the process data model.

3. In the Type list, select xml.

4. If the variable is used to store process data, select Process Variable in the Purpose area.

   • If the variable stores input data that is provided when the process is initiated, select Input.

   • If the variable stores data that is returned to the process initiator when the process is complete, select Output.

   • If the variable stores input data that is mandatory to initiate the process, select Required.

5. To import a schema to make the xml data structure appear in XPath Builder, click Import Asset.

6. Select an XSD file or an XDP file that has an embedded schema from an application and click OK.

7. Click OK.

Reset Deployment ID properties:

1. Reset the Deployment ID property of the legacy render and submit processes that you have imported. Resetting enables you to invoke them as subprocesses. (See Breaking the link to existing run-time instances .)

2. Right-click the application that contains the render and submit process and click Deploy.

Create new render and submit processes:

1. In the Applications view, right-click the asset and click Manage Action Profiles.

2. Select the default action profile, or create an action profile to preserve the default one.

3. To create a render process, under Render Process click the Create A Render Process button .

4. Type a name for the process and click OK.

5. To create a submit process, under Submit Process click the Create A Submit Process button .

6. Type a name for the process and click OK.

7. Click OK to close the Manage Action Profiles dialog box.

Configure render and submit processes:

1. In the Applications view, right-click the new render or submit process and select Open.

2. Define the operation that was automatically added to the process:

   • For render processes, right-click the Render operation and click Define Operation.

   • For submit processes, right-click the Submit operation and click Define Operation.

3. Select the invoke operation of the legacy render or submit process and click OK.

4. On the Confirm dialog box, click Yes.

5. In the Process Properties view, configure the Input and Output properties of the invoke operation.

Configure the Workspace start point:

1. In the process diagram, select the Workspace start point.

2. In the Process Properties view, configure the properties using equivalent values from the LiveCycle ES Task Manager endpoint according to the previous table.

3. Expand the Presentation & Data property group and provide the following values:

   • Asset: Select the form or Flex application to present to users.

   • Action Profile: Select the action profile of the asset that you want to use.

   • Start Point Output: Select the xml variable for saving the submitted data.

Add an Assign Task operation:

1. Drag the Assign Task operation to the process diagram.

2. In the Process Properties view, configure the properties using equivalent values from the deprecated Assign Task operation that you are replacing according to the previous table.

3. Expand the Presentation & Data property group

4. Select Use An Application Asset, click The ellipsis button next to the Asset box, and select the form asset.

5. Make sure the action profile that you want to use is selected.

6. (Optional) To prepopulate the asset, in the Variable list select an existing xml variable that contains the data. For example, select the variable that was used as the Start Point Output property value. To create an xml variable to use as the property value, click the Create New Variable button .

7. Expand the Output property group.

8. (Optional) To save submitted task data, in the Task Result list select a Task Result variable. To create a variable to use as the property value, click the New Variable button and create a Task Result variable.

   Task Result variables were new in LiveCycle ES2. They store all data that is submitted with tasks, such as asset data and information about the task.

9. (Optional) To save submitted asset data, in the Output Data list select an xml variable to save the data. Saving the asset data separately is useful for using the data to populate the asset of a subsequent task.

Draw routes for the new Assign Task operation:

1. If the routes that lead to or away from the deprecated Assign Task operation include conditions, note the expressions of the conditions.

2. Delete the routes that lead to and away from the deprecated Assign Task operation.

3. Draw routes to and from the new Assign Task operation that you added in the previous procedure.

4. (Optional) If the deprecated Assign Task operation used route names as task submission options, add a user action for each route. For example, if the route names were Approve and Deny, add user actions named Approve and Deny:

   • Expand the User Actions property group.

   • Click the Add A User Action button .

   • In the Action Name box, type the name of the action as you want it to appear to the user.

   • From the Destination list, select next operation to execute when the user action is clicked, and then click OK.

5. (Optional) If the routes to or from the deprecated Assign Task operation included conditions, add the conditions to the routes of the new Assign Task operation:

   • Select the route and in the Process Properties view, expand the Conditions property group.

   • Click the Add Route Condition button.

   • In the Expression box on the left, type the first part of the expression. If the condition is complex, click the ellipsis button to display the XPath Builder.

   • In the Operation list, select an operation.

   • In the Expression box on the right, type the second part of the expression. If the condition is complex, click the ellipsis button to display the XPath Builder.

   • Click OK to close the Route Properties dialog box.

   • If you have more than one routing condition in the Conditions category, select the join condition to determine how the conditions are evaluated:

     • Use AND Join For Conditions means that the route is valid only if all the conditions evaluate to True .

     • Use OR Join For Conditions means that the route is valid when one or more of the conditions evaluate to True .

     The default join condition is Use OR Join For Conditions.

Delete the deprecated Assign Task operation:

Right-click the deprecated Assign Task operation and click Delete Operation.