Call a Web Service Method from a .NET Proxy

Prerequisites

• A valid web service — for example a live, valid WSDL file.
• AgilePoint NX OnPremises or AgilePoint NX PrivateCloud.
• On your AgilePoint Server machine, enter the .NET proxy assemblies in the file (AgilePoint Server instance installation folder) C:\Program Files\AgilePoint\AgilePointServerInstance \ConfigurationSettings\DotnetProxyAssemblies\DotnetProxyAssemblyList.xml
• The .NET proxy .dll or .exe assembly files must be in the GAC on the AgilePoint Server machine.

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?

• Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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 Application Explorer screen, do one of these:
   • Open a Process.
   • Create a Process.
2. Do one of these:
   • Add an activity:
     1. In the Process Builder, in the Activity Library, open the Web Services tab.
     2. On the Web Services tab, drag the .NET activity onto your process.
   • Change an activity:
     1. In your process, double-click your activity.
3. On the .NET Proxy Configuration screen, click .NET Configuration .

Procedure

1. On the .NET Configuration screen, in the .NET Proxy Access Token field, select access token.

   To create a new access token, click Add Token . For more information, refer to Access Token for .Net Proxy.

2. In the Class Name list, select the name of the .NET class to call.
3. In the Method Name list, select the name of the method to call.
4. In the Runtime URL field, enter the URL of the endpoint of the web service to connect.
5. To connect the request data from your schema to the source system, complete this field as necessary:

   Field Name

   Definition

   Request Mapping

   Function: Connects the web service request to your schema. This is mandatory only if the request passes data from the process schema to parameters in the web method. To Open this Field: 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 button to open the Schema Mapper. Use this screen to connect the request to the data model for your process. Default Value: None Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?

6. To connect response data from the web service call to your process, do one of these.
   • To connect the response to your process schema, complete this field as necessary:

     Field Name

     Definition

     Map Response to AgilePoint Schema

     Function: Specifies if the web service response connects to your schema. To Open this Field: 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 button to open the Schema Mapper. Use this screen to connect the response to the data model for your process. Default Value: None Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?

   • To connect the response to a process data variable, complete this field as necessary:

     Field Name

     Definition

     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: 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, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?