Using an InfoPath Sub Process

Instructional Goals

• Demonstrate how to call a sub process from a parent process using the InfoPath SubProcess AgileShape.

Example Parent Process: Execute a Software Change Request

Example Sub Process: QA Test the Change Request

Problem Statement

Fulfill a change request (CR) for a software product.

Business Requirements

• The process is initiated when someone submits a CR.
• Engineering implements the CR.
• Once the CR is implemented in the code, the Quality Assurance (QA) department tests it. The QA department has the following unique requirements:
  • QA for this product requires complex preparation, where test cases must be written and real-world system configurations and data must be set up prior to testing to ensure proper implementation of fixes and enhancements. This requirement carries a unique set of needs for resources and logistics.
  • The QA department is managed separately from Engineering, and follows its own internal processes. They want to maintain autonomous control over their processes.
  • There is an initiative in the company to improve the QA process in order to improve efficiency and product quality. Therefore, the QA review process is likely to change more frequently than the overall Change Request process.

  To meet the QA department's requirements, the company uses a sub process to define and manage the QA review process.

• The form technology is InfoPath

Navigation

1. In AgilePoint Envision, open a process template.
2. Navigate to the SharePoint stencil.
3. On the SharePoint stencil, drag the InfoPath SubProcess AgileShape, and drop it on the process template.
4. To view the entire list of properties, in the Design Tasks pane, click Show Properties.

Instructions

1. Set up the following properties for InfoPath SubProcess AgileShape:

   Field	Configuration
   FormLibUrl	Definition: Specifies the URL for the InfoPath form located in a SharePoint form library or folder. Allowed Values: A valid URL to a SharePoint form library. Note the following: The InfoPath form must be located in a SharePoint form library or folder. The value must be an absolute URL. Default Value: None Custom Attributes: No Example: http://demo3:8000/InfoPathChangeRequest/Forms/AllItems.aspx
   NamingFormat	Definition: Specifies the format to name the sub process. Allowed Values: A valid format. Default Value: yyyy-MM-dd hh-mm-ss-ffffff - The DateTime format that is used to name the sub process. Custom Attributes: Yes
   Prefix	Definition: Specifies the prefix that is associated with the sub process name. Allowed Values: A text string. Default Value: Prefix- Custom Attributes: No Example: CR- This prefix could be used to indicate a change request for a software development process.
   SubProcess	Definition: Specifies the name of the InfoPath process to be initiated as a sub process. Allowed Values: The name of the existing process to be initiated as a sub process. You can use the Ellipses button to select the InfoPath process name. Default Value: None Custom Attributes: No
   Wait For Complete	Definition: Determines whether the parent process waits for the sub process to complete before moving forward. Allowed Values: False - The AgileShape exits immediately once the sub process is initiated. True - The AgileShape waits for sub process to complete. Default Value: True Custom Attributes: No
   XMLMappings	Opens the Following Window: XML Schema Mappings Window Purpose of this Window: Maps schema nodes from a parent process to a sub-process.
   XsnFileUrl	Definition: The URL of the InfoPath form template file to be associated with the sub process. Allowed Values: A valid URL of the InfoPath form template file. Default Value: /forms/template.xsn Custom Attributes: Yes Example: /forms/QAReview.xsn

Downloads

NTLoginTest.zip.