.NET Proxy activity

An activity that uses a .NET proxy to call a web service method from a process.


Dot NET Proxy activity

Configure the .NET Proxy activity

To configure the .NET Proxy activity, do the procedure in this topic.

Prerequisites

Good to Know

  • In some cases, the type of the object instance returned by a web method may need to implement the IConvertible interface in order for the web method to be used with the Web Service activity.
  • 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?

  • This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
  • 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?

How to Start

  1. On the App Explorer screen, do one of these:
  2. Do one of these:
    • Add an activity:
      1. In Process Builder, in the Activity Library, open the Web Services tab.

        Open Web Services tab
      2. On the Web Services tab, drag the .NET dot NET 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.
  2. Click .NET Configuration dot NET Configuration icon.
  3. Complete the fields on the .NET Configuration screen.

    For more information, refer to Call a Web Service Method from a .NET Proxy.

  4. (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 .NET Proxy 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

.NET Proxy Configuration

Specifies the web service method to call when the activity starts.

Figure: .NET Proxy Configuration screen

Dot NET Proxy Configuration screen

Fields

Field NameDefinition

.NET Proxy Access Token
Function:
Specifies the access token that connects to your web service from a .NET proxy on the AgilePoint Server machine.
Accepted Values:
A list of access tokens configured for your environment.
Default Value:
None
Accepts Process Data Variables:
No

Create Add Token icon
Opens this Screen:
Access Token for .Net proxy
Function of this Screen:
Configure an access token to connect to a .NET proxy service.

Class Name
Function:
Specifies the name of the .NET class to call.
Accepted Values:
A class name from the list.
Default Value:
None

Method Name
Function:
Specifies the name of the method to call.
Accepted Values:
A method name from the list.
Default Value:
None
Accepts Process Data Variables:
No

Runtime URL
Function:
Specifies the URL of the endpoint of the web service or WCF service you want to connect.
Accepted Values:
A valid endpoint URL.
Default Value:
None
Accepts Process Data Variables:
Yes
Example:
  • http://localhost:60617/WebService.asmx
  • http://myserver.com/AgilePointServer/Admin?WSDL
  • http://CSC-NINE:7002/AgilePointServer/Workflow

Request Mapping
Function:
Connects the web service request to your process schema. This is mandatory only if the request passes data from the process schema to parameters in the web method.
To Open this Field:
  1. On the .NET Proxy Configuration screen, click the Request tab. You can not map the schema if the web service type is None.
Accepted Values:
Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper screen.

Use this screen to connect the request to the data model for your process.

Default Value:
None
Example:
Refer to:

Map Response to AgilePoint Schema
Function:
Specifies if the web service response connects to your process schema.
To Open this Field:
  1. On the .NET Proxy Configuration screen, click the Response tab. You can not map the schema if the web service type is None.
Accepted Values:
Click the Schema Mapping Schema Mapping icon button to open the Schema Mapper screen.

Use this screen to connect the response to the data model for your process.

Default Value:
None
Example:
Refer to:

Store the Response in Custom Attribute
Function:
Specifies the name of the process data variable that stores the response to a method call to a WCF service.
To Open this Field:
  1. On the .NET Proxy Configuration screen, click the Response tab. You can not map the schema if the web service type is None.
Accepted Values:
A process data variable.
Default Value:
None
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?