This chapter contains the following topics:
Section 6.1, "Understanding JD Edwards EnterpriseOne Workflow Process Versions"
Section 6.2, "Validating a JD Edwards EnterpriseOne Workflow Process Version"
Section 6.3, "Attaching a JD Edwards EnterpriseOne Workflow Process Version to an Application"
After you use JD Edwards EnterpriseOne Workflow Modeler to create the tasks within the process and you add transition conditions and distribution lists, you must validate the workflow process version. When validating a version, the system verifies that the version contains start and end points. It also verifies that all tasks that need event rules contain event rules, and that transitions exist among all the tasks.
You must make a version of a JD Edwards EnterpriseOne workflow process active in the system before you can attach it to an application. Additionally, only one version of a workflow process can be active at a time. This active version is the one that will be used if a process is started. However, once a process is started it will continue running with the version it started with, regardless of the status of that version.
You must validate a workflow process version before you can activate it in the system. You cannot activate a process that contains errors.
Note:
Once a JD Edwards EnterpriseOne workflow process is made active in the system, or, if there are running instances of that workflow, you cannot modify it.Access Object Management Workbench (OMW).
Find the JD Edwards EnterpriseOne workflow process version that you want to validate in Object Management Workbench.
Move the workflow process version to a project folder.
Click the workflow process version and then click the Design button in the center column.
On the Workflow Design form, click the Design Tools tab and then click Validate Workflow.
If the version contains no errors, the message Workflow is VALID appears. You can now attach the workflow process version to an application.
If the version contains errors, a dialog box appears with a list of errors. Click Start Workflow Modeler to open the version in JD Edwards EnterpriseOne Workflow Modeler and correct the errors.
This section provides an overview of activating and attaching a JD Edwards EnterpriseOne workflow process version and describes how to:
Attach the Start Process system function to an application.
Attach the Pending Approval form to an application.
Only one version of a JD Edwards EnterpriseOne workflow process can be active at a time. This active version is the one that will be used if a workflow process is started. However, once a process is started it will continue running with the version it started with, regardless of the status of that version.
Note:
Once a JD Edwards EnterpriseOne workflow process is made active in the system, you cannot modify it. See Working with Existing JD Edwards EnterpriseOne Workflow Processes for information on how to modify existing JD Edwards EnterpriseOne Workflow processes.You cannot activate a process if it contains errors. Therefore, you must validate the workflow process before you activate it.
Access OMW.
Find the JD Edwards EnterpriseOne Workflow process version in Object Management Workbench.
Move the workflow process version to a project folder.
Click the workflow process version, and then click the Design button in the center column.
On the Workflow Design form, click the Design Tools tab and then click Change Workflow Status to toggle between inactive and active.
After you create, validate, and activate a JD Edwards EnterpriseOne workflow process, you attach it to an event within an application using Event Rules in Form Design Aid (FDA). You only need to define the system function Start Process in an application to attach a JD Edwards EnterpriseOne workflow process. The Start Process system function invokes the tasks within the process.
You can also attach workflow processes in Event Rules within Report Design Aid (RDA), Table Design Aid (TDA), or through named event rules (NER).
The following tasks explain how to attach the process called CREDLIMIT to an application and how to call a pending approval message that appears within the application when a user makes a change to a customer's credit limit. The example used is specific to the Credit Limit Revisions process; the way in which you attach your processes varies.
Understand how to attach event rules to applications.
See "Event Rules Fundamentals" in the JD Edwards EnterpriseOne Tools Event Rules Guide.
Access OMW.
Find and check out the application to which you want to attach the JD Edwards EnterpriseOne workflow process.
Click the Design button in the center column.
On the Interactive Application Design form, click the Design Tools tab.
Click Start Form Design Aid.
Find the form to which you want to attach the Start Process system function.
Open the event rules for the form, position the cursor where you want to start the workflow process, and click the System Function button.
On System Functions, click the Function Selection tab, double-click the Workflow folder, and then select Start Process.
Click the Parameter Mapping tab and double-click Choose Process.
On the Process Search and Select form, find the process that you want to attach to the application and click OK.
The JD Edwards EnterpriseOne Workflow engine dynamically selects the active version of the process attached in Event Rules.
On the System Functions form, select the Key Data Structure data item, and double-click the Define Mapping object.
On the Data Structure Mapping form, map the Key Data Structure to the corresponding object in the Available Objects list.
Repeat steps 10 and 11 to map the Additional Data Structure, and then click OK.
You can attach a form interconnection event rule that calls a message form. For example, you might want the system to call a form that notifies a user that the requested changes will be made after others approve them.
To attach a form interconnection:
On Event Rules, click the Form Interconnect button.
On the Work With Applications form, find and select the application that you want to use.
On Work With Forms, select the form that you want to use.
On Form Interconnections, map the appropriate parameters, if applicable.
In the Credit Limit Revisions example, the form that is called when a user makes a change to a customer's credit limit is for informational purposes only; you do not need to pass any values to this form.