Auto-Lookup > WCF > Name/Value

Access Token

Function:

Specifies the access token that connects to your data source.

Accepted Values:

A list of access tokens configured for your environment.

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.

Add New

Opens this Screen:

Access Token for WCF Service

Function of this Screen:

Configure an access token to connect to a WCF service.

Lookup Name

Function:

Specifies the name you want to give to your lookup procedure.

Accepted Values:

One line of text that can have spaces.

Default Value:

None

Accepts Process Data Variables:

No

Example:

Refer to:

• (Example) How Do I Configure a Pop-Up Select Control to Bind the Lookup Values to a Data Grid?
• (Example) Configure an Auto-Lookup Form Control with Microsoft Excel

Lookup Type

Function:

Specifies the type of lookup procedure to do.

Accepted Values:

• Name/Value - The lookup gets data for specified name/value pairs.
• Multiple Columns - The lookup gets data for more than one column.

Default Value:

Name/Value

Example:

Refer to:

• (Example) How Do I Configure a Pop-Up Select Control to Bind the Lookup Values to a Data Grid?
• (Example) Configure an Auto-Lookup Form Control with Microsoft Excel

Service Operation

Function:

Specifies the name of the method to call.

Accepted Values:

A valid web method name from the specified WCF service.

Default Value:

None

Example:

GetSalesInfo

Also refer to:

• The videos on this page

Endpoint 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.

However, once a web service is connected, the endpoint URL shows if it is defined in the WSDL file.

Accepts Process Data Variables:

No

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?

Generate Message Contracts

Function:

Specifies if the method you call supplies a message contract or not.

A message contract gives the structure of a SOAP message.

Accepted Values:

• Selected - The method gives message contracts.
• Deselected - The method does not give message contracts.

Default Value:

Deselected

Request Mapping

Function:

Connects the WCF service request to your process schema. This is mandatory only if the request passes data from the process schema to parameters in the service operation.

To Open this Field:

1. On the Configure Lookup screen, in the Request tab, select the name of the method from the Service Operation list.

Accepted Values:

To open the Schema Mapper, click the Ellipses (...) button.

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

Default Value:

None

Example:

Refer to:

• (Example) Schema Mapper

Service Operation

Function:

Specifies the name of the method to call.

Accepted Values:

A valid web method name from the specified WCF service.

Default Value:

None

Example:

GetSalesInfo

Also refer to:

• The videos on this page

Endpoint 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.

However, once a web service is connected, the endpoint URL shows if it is defined in the WSDL file.

Accepts Process Data Variables:

No

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?

Map Response to AgilePoint Schema

Function:

Specifies if the WCF service response connects to your process schema.

Accepted Values:

To open the Schema Mapper, click the Ellipses (...) button.

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

Default Value:

None

Example:

Refer to:

• (Example) Schema Mapper

Store the Response In This Variable

Function:

Specifies the name of the process data variable that stores the response to a method call to a WCF service.

Accepted Values:

A process data variable.

Default Value:

None

Accepts Process Data Variables:

Yes

Service Operation

Function:

Specifies the name of the method to call.

Accepted Values:

A valid web method name from the specified WCF service.

Default Value:

None

Example:

GetSalesInfo

Also refer to:

• The videos on this page

Endpoint 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.

However, once a web service is connected, the endpoint URL shows if it is defined in the WSDL file.

Accepts Process Data Variables:

No

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?

No Items Retrieved

Function:

Specifies the error message to show if the lookup does not return any data.

Accepted Values:

One line of text that can have spaces.

Default Value:

None

Lookup Failed

Function:

Specifies the message to show if the data fails to load.

Accepted Values:

More than one line of text.

Default Value:

Failed to load data.