Tutorial: Submitting Multiple Primary Items

This topic shows how to submit multiple primary items based on a single transition action. You will create a workflow and configure it so users can create two items, each one in a separate project, when a third item is submitted. In this example, the three items are linked together, but no parent/child or principal/subtask relationship is established, and the items move independently through their workflows.

Prerequisites:

The following must be set up before you perform this procedure:

  • Application workflow named Software Issues
    • Submit Defect Regular transition that leads from the Submit state to the New state
    • Submit Enhancement Regular transition that leads from the Submit state to the New state
  • Application workflow named Product Development
    • Defect Post Post transition that leads from the Any state back to itself
    • Enhancement Post Post transition that leads from the Any state back to itself
Consider the following information when you use actions to submit multiple primary items.
  • The example in this topic uses Post transitions to submit multiple items. You can also use Copy or Subtask transitions.
  • The example is defined within a single application. You can use Subtask or Post transitions to set up multiple submittals across applications as needed. Make sure users have submit privileges into the projects specified in the Subtask or Post transitions.
  • When you implement multiple submittals in your system, consider how you want data to be mapped. By default, some field values automatically map to the new items, depending on the type of transition you use to submit new items, and whether you are submitting items into the same primary table or to a different primary table. You can specify your own mapping or use the default mapping. You can also define default field values for the Copy, Post, or Subtask transitions.

    For details, refer to Mapping Fields for Post, Publish, Copy, or Subtask Transitions.

To submit multiple primary items:

  1. Configure the transitions in the Software Issues workflow:
    1. Click the Submit Defect transition.
    2. In the transition Property Editor, on the Options tab, select the Quick Transition check box.
    3. Click the Submit Enhancement transition.
    4. In the transition Property Editor, on the Options tab, select the Quick Transition check box.
    5. Save the process app.
  2. Configure the transitions in the Product Development workflow:
    1. Click the Defect Post transition.
    2. In the transition Property Editor, on the Options tab, select the Quick Transition and Hide transition button on state form check boxes.
    3. On the Post Options tab, in the Use submit transition list, select Software Issues : Submit Defect.
    4. Still on the Post Options tab, In the Item Link Type list, select 2-Way, no triggers.
    5. Click the Post Enhancement transition.
    6. In the transition Property Editor, on the Options tab, select the Quick Transition and Hide transition button on state form check boxes.
    7. On the Post Options tab, in the Use submit transition list, select Software Issues : Submit Enhancement.
    8. Still on the Post Options tab, in the Item Link Type list, select 2-Way, no triggers.
  3. Create actions to allow multiple submittals:
    1. In the Product Development workflow, right-click the Submit transition, and then select Show Actions.
    2. In the transition Property Editor, on the Actions tab, click New. The Action Wizard opens.
    3. Select Transition, and then click Next.
    4. Select This Item, and then click Next.
    5. Select Unconditionally, and then click Next.
    6. Select Product Development:Defect Post([Any])->([Any]) and then click Finish.
    7. In the transition Property Editor, on the Actions tab, click New again.
    8. In the Action Wizard, repeat steps c, d, and e.
    9. Select Product Development:Enhancement Post([Any])->([Any]) and then click Finish.
  4. Deploy the process app.
  5. In SBM Application Administrator, add two subprojects to the Software Issues project.
    1. On the Projects tab, select Software Issues Project.
    2. Click Add.
    3. In the Add Project dialog box, type Defects in the Project Name box.
    4. Repeat steps b and c, except type Enhancements in the Project Name box.
  6. Still in Application Administrator, edit the Post transitions in the Product Development project.
    1. On the Projects tab, select Product Development Project.
    2. Click Edit.
    3. In the Edit Project dialog box, click the Transitions tab.
    4. Select the Defect Post transition, and then click Edit.
    5. In the Edit Transition dialog box, select the Override check box above the Post Item Project box.
    6. Select Defects under Software Issues Project, and then click OK.
    7. Repeat steps d, e, and f, except select the Enhancement Post transition, and select Enhancements under Software Issues Project.
  7. Test the process app:
    1. In the SBM User Workspace, submit an issue into the Product Development project. The Attachments and Change History sections indicate that when you submitted issue 000225, issues 000226 and 000227 were automatically submitted. Issue 000226 was submitted into the Defects project, and issue 000227 was submitted into the Enhancements project.

    image

Related Topics

Using the Action Wizard