Subprocess With InfoPath activity

An activity that starts a subprocess from InfoPath form services.



Configure the Subprocess With InfoPath activity

To configure the Subprocess With InfoPath activity, do the procedure in this topic.

Good to Know

  • In most text fields, you can use process data variables as an alternative to literal data values.
  • You can configure whether this activity waits for other activities before it runs.

    For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?

  • Documentation for Integrations with Third-Party, External, or Open Source Technologies

    The highest priority for AgilePoint NX Product Documentation is accuracy. Whenever feasible, AgilePoint provides input details, business rules, or example values for third-party integrations. These can include any technology that is not native to AgilePoint NX, such as Salesforce, Active Directory, or REST. However this information is subject to change without notice to AgilePoint. Because we can not guarantee the accuracy of this information, the details provided for third-party product input values, as well as examples for third-party product integrations, are limited in the AgilePoint documentation. It is the responsibility of third-party vendors to provide documentation related to these aspects of their software and services.

    For examples of use case implementations or configuration field input values for third-party products, AgilePoint recommends these resources:

    • AgilePoint Community Forums - An AgilePoint-moderated, crowd-sourcing user forum where you can ask questions about specific techniques, the solutions to use cases, workarounds, or other topics that may not be covered in the Product Documentation.
    • Professional Services - If you can not find the information you need for your specific business problem, mentoring is available through AgilePoint Professional Services.
    • Personalized Training - AgilePoint can provide personalized training for your organization. To request personalized training, contact AgilePoint Sales.
    • Third-Party Vendor Documentation - Whenever feasible, AgilePoint provides links to third-party vendor documentation.

      This does not include technology standards or protocols, such as JavaScript, REST, or FTP. Resources for these technical standards are publicly available on the Internet.

How to Start

  1. On the Application Explorer screen, do one of these:
  2. Do one of these:
    • Add an activity:
      1. In the Process Builder, go to the Activity Library, and open the SharePoint SharePoint icon tab.
      2. On the SharePoint SharePoint icon tab, drag the SubProcess With infoPath SubProcess With infoPath icon activity onto your process.
    • Change an activity:
      1. In your process, double-click your activity.

Procedure

  1. Complete the fields on the General Configuration screen.

    For more information, refer to Configure General Options for a System Activity.

  2. Click Configuration Properties Configuration Properties icon.
  3. Configure Subprocess With InfoPath Configuration screen.
  4. Click Subprocess Template Subprocess Template icon.
  5. On the InfoPath Subprocess Model screen , in the InfoPath Subprocess Model field, select the process from InfoPath form services from the list.
  6. Click Subprocess Configuration Subprocess Configuration icon.
  7. On the Subprocess Configuration screen, do this procedure.
    1. To specify the format for the name of the subprocess, do one of these:
      • To use the name of the process model to create the process instance name, in the Subprocess Instance Name Format field, select Name .
      • Select Custom to specify a different format.

        In the Custom field, enter the name of the process, or drag a process data variable from the Process Data screen.

    2. (Optional) To add a GUID to the custom subprocess name, select If the subprocess name already exists, append the name with @${GUID}.
    3. To specify the participant who starts the subprocess, do one of these:
      • To let the process initiator start the subprocess, in the Subprocess Initiator Name, select Process Initiator.
      • To let a different participant start the subprocess, select Custom.

        In the Custom field, drag a participant from the Process Data screen.

  8. Click Schema Mapping Schema Mapping icon.
  9. On the Schema Mapper screen, drag the variables from the parent process model schema to child process model schema as necessary to connect them.
  10. For more information, refer to Configure a Subprocess With InfoPath.
  11. (Optional) Click Advanced Advanced icon > E-mail Notifications E-mail Notifications icon.

    For more information, refer to Configure E-mail Notifications for Any Activity.

General Configuration

Specifies the common information for a system activity.

Screen



Fields

Field Name Definition

Display Name

Function:
Specifies the activity name that shows in your process.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data Variables:
No
Example:
Refer to:

Description

Function:
Specifies an optional text description for your activity.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data Variables:
No

Subprocess With InfoPath Configuration

Configures the activity to specify the InfoPath form that triggers the child process.

Screen



Fields

Field Name Definition

SharePoint

Function:
Specifies the access token that connects to your SharePoint site.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None
Accepts Process Data Variables:
No
Example:
Refer to:
Limitations:
  • OAuth 2.0 authentication is not supported for this activity.

Add Token Add Token icon

Opens this Screen:
Access Token for SharePoint
Function of this Screen:
Configure an access token to connect to SharePoint.

Site

Function:
Specifies the URL for your SharePoint site.
Accepted Values:
A valid SharePoint site URL
Default Value:
None
Accepts Process Data Variables:
Yes
Example:

Form Library

Function:
Specifies the SharePoint library with the InfoPath form.
Accepted Values:
A valid SharePoint form library.
Default Value:
None
Accepts Process Data Variables:
Yes

Xsn File Url

Function:
Specifies an InfoPath form template file.
Accepted Values:
A valid InfoPath form template file.
Default Value:
None
Accepts Process Data Variables:
Yes
Example:
template.xsn

InfoPath Naming Format

Function:
Specifies the naming convention for the records in the specified InfoPath form library.
Accepted Values:
  • One line of text that can have spaces.
  • A process data variable.

    You can use Process Data screen to specify a process data variable.

Default Value:
yyyy-MM-dd hh-mm-ss-ffffff
Accepts Process Data Variables:
Yes

InfoPath Prefix

Function:
Specifies the prefix for the the naming convention for the records in the specified InfoPath form library.
Accepted Values:
  • One line of text that can have spaces.
  • A process data variable.

    You can use Process Data screen to specify a process data variable.

Default Value:
Prefix-
Accepts Process Data Variables:
Yes

InfoPath Subprocess Model

Specifies the process model for a subprocess.

Screen



Fields

Field Name Definition

InfoPath Subprocess Model

Function:
Specifies the name of the process from InfoPath form services.
Accepted Values:
A valid process name.
Default Value:
None

Zoom In (+) Zoom Out (-)

Function:
Allows you to increase / reduce the size of your process to view more detail or less detail about the process.

InfoPath Subprocess Configuration

Specifies the format for the name of the subprocess. For example, the format can contain the name of the subprocess, the session ID, and the name of the Subprocess activity in the parent process. You can use the name to manage your processes in Manage Center.

Screen



Fields

Field Name Definition

InfoPath Subprocess Model

Function:
Specifies the name of the process that starts as a subprocess when the process goes to this activity.
Accepted Values:
Read only.

Subprocess Instance Name Format

Function:
Specifies the process instance name for the subprocess instance.
Accepted Values:
  • Name - Specifies the default format for the process instance name to use for the subprocess. AgilePoint NX uses this format to create the name.
  • Custom - Specifies a custom format for the process instance name.
Default Value:
${ProcessName}-${Session}@${ActivityName}
Accepts Process Data Variables:
Yes

If the subprocess name already exists, append the name with @${GUID}

Function:
Adds a GUID to a custom subprocess name when the name already exists in the AgilePoint system.
Accepted Values:
  • Selected - Specifies that a GUID is added to the custom subprocess name.
  • Deselected - Specifies that a GUID is not added to the custom subprocess name.
Default Value:
Selected
Accepts Process Data Variables:
Yes

Subprocess Initiator Name

Function:
Specifies the participant to use as the process initiator for the subprocess.
Accepted Values:
Default Value:
Process Initiator
Accepts Process Data Variables:
Yes

Schema Mapper

Maps SharePoint fields, form fields, web methods, or other input sources to an XML schema.

Screen



Fields

Field Name Definition

Mapping Schema

Function:
Connects the schemas to your schema.

The source and the destination schemas show in a tree view in the left and right panes.

Accepted Values:
Read only - However, the drag and drop operations are supported to map the schemas.

Drag a data node from the source schema pane to the destination schema pane:

  • Green line - The data type of source and destination nodes matches.
  • Blue line - The data type of source and destination nodes doesn't match. The data conversion is required to map the schemas.
  • Red line - Specifies that the custom data conversion is required.
Example:
Refer to:

AutoMap

Function:
Maps all fields in the data source and the process schema that have the same name.

Reset

Function:
Deletes all connections that have been made in the schema mapper for this activity.

Delete

Function:
Deletes the selected custom data conversion from the list.