Call a Web Service Method from a .NET Proxy

To call a web service method from a .NET proxy, do the procedure in this topic.

Figure: .Net Proxy Configuration screen

DotNet Proxy Configuration screen

Prerequisites

Good to Know

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.
  3. On the .NET Proxy Configuration screen, click .NET Configuration dot NET Configuration icon.

Procedure

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

    To create a new access token, click Create Add Token icon. 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 process schema to the source system, complete this field as necessary:
    Field NameDefinition

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

      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:
    • To connect the response to a process data variable, complete this field as necessary:
      Field NameDefinition

      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?