1. Developing SOA Applications with Oracle SOA Suite
  2. Using the Human Workflow Service Component
  3. Designing Task Forms for Human Tasks
  4. Creating an ADF Task Flow Based on a Human Task
  5. What You May Need to Know About Having Multiple ADF Task Flows That Contain the Same Element with Different Meta-attributes

What You May Need to Know About Having Multiple ADF Task Flows That Contain the Same Element with Different Meta-attributes

You must create separate ADF task flows if both contain the same element, but with different meta-attributes specified (for example, editable and noneditable).

For example, assume you perform the following tasks.

  1. Create two task form applications for a SOA composite application:

    • Task form application one (for example, named EnterBankDetails.task) has one editable payload (for example, named BankDetails) and one noneditable payload (for example, named Employee).

    • Task form application two (for example, named ValidatePersonalInformation.task) has one editable payload (for example, also Employee).

    While creating the task form, the wizard provides you with the option to define the ADF table for payload Employee.

  2. Complete the wizard, then deploy the process.

  3. Invoke the process.

  4. Log in to Oracle BPM Worklist.

    There is a Validate Personal Information task (for ValidatePersonalInformation.task).

  5. Select the task.

    Employee details are available for modification, as expected.

  6. Add a new record, then approve the task.

  7. Select the Enter Bank Details task (for EnterBankDetails.task). In the task form, the Insert New and Delete buttons are still present for Employee data, even though it is a noneditable payload.

  8. Click Delete, then select Approve. The payload gets deleted.

Ensure that you create two separate ADF task flow applications because both contain the Employee element, but with different meta-attributes specified (editable and noneditable).