Subprocess With InfoPath activity

An activity that starts a subprocess from InfoPath form services.


Subprocess With InfoPath activity

Configure the Subprocess With InfoPath activity

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

Examples

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, and open the SharePoint tab.

    Open SharePoint tab
  3. On the SharePoint tab, drag the Subprocess With InfoPath activity onto your process.

    Drag Subprocess With InfoPath activity

Procedure

  1. Complete the fields on the General Configuration screen.
  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. (Optional) Click Advanced Advanced icon > Email Notifications E-mail Notifications icon.

    For more information, refer to Email Notifications screen (Process Activities).

General Configuration

Specifies the basic settings for the Subprocess With InfoPath activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

  • Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field NameDefinition

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:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

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.

Figure: Subprocess With InfoPath Configuration screen

Subprocess With InfoPath Configuration screen

Fields

Field NameDefinition

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.

Create Add Token icon
Opens this Screen:
Access Token for SharePoint
Function of this Screen:
Configure an access token to connect to SharePoint.
Example:
Refer to:

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
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

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
Limitations:

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

InfoPath Subprocess Model

Specifies the process model for a subprocess.

Figure: InfoPath Subprocess Model screen

InfoPath Subprocess Model screen

Fields

Field NameDefinition

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.

Figure: InfoPath Subprocess Configuration screen

InfoPath Subprocess Configuration screen

Fields

Field NameDefinition

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.

Figure: Schema Mapper screen

Schema Mapper screen

Fields

Field NameDefinition

Mapping Schema
Function:
Connects the schemas to your process 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.
Example:
Refer to:

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.