Lookup Details for Web Service

Specifies the name/value type of the lookup procedure for web service.

Video: Show Data from a Web Service on an eForm

Prerequisites

• AgilePoint NX OnDemand (public cloud), or AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v7.0 Software Update 2 or higher.

Good to Know

• Limitations

  These technical limitations apply to Web Service and WCF support in process activities and lookups:

  • Arrays of primitive data types.

    Arrays of primitive data types — for example, string, Boolean, integer, decimal — are not supported as input or output data types because this interferes with the deserialization of the array object.

    However this does work with an array of complex classes and custom classes or a list of primitive data types.

    If you have a service that returns an array of primitive data types, these workarounds are suggested:

    • Return a list objects instead of arrays — for example, List<string>, instead of string[]
    • Create a custom class that encapsulates that property — for example, a class that has a property of type string.
    • If you do not have control over the service, you can write a wrapper service that encapsulates the call to the underlying service and converts the array to a list object, or create a custom class that encapsulates that property.
  • Dictionary objects.

    Dictionary objects are not supported as input or output data type because XMLSerializer interferes with the deserialization of the dictionary object.

  • Circular references.

    Circular references are not supported in input and output objects — for example, if a class called Person contains a field of type Person that references the same class. Such a circular structure cannot be loaded in the XML Mapper.

  • Nested WSDLs.

    Web services with nested WSDLs are not supported. Consider making your service use single WSDL, or use the .Net Proxy activity.

• 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 an eForm.
   • Create an eForm in a Process.
2. Do one of these:
   • Add a Single Select Lookup control:
     1. On the eForm Builder screen, in the Toolbox, open the Advanced Controls tab.
     2. On the Advanced Controls tab, drag a Single Select Lookup form control onto your eForm.
   • Change a Single Select Lookup control:
     1. On your eForm, click the control, and click Edit .
3. On the Single Select Lookup screen, in the Configure tab, click Add Lookup .
4. On the Select Data Source Type screen, select Web Service .
5. Click Next.

Fields