Difference between revisions of "Web Services Integration"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
==About Web Service Integration== | ==About Web Service Integration== | ||
Web Services whose connections are specified using the Web Service Description Language ({{^WSDL}}), can be integrated into the platform without programming, using a few configuration steps. | |||
In addition, the interface defined by the WSDL can be simplified to match the application by: | |||
:* Ignoring fields that are not needed | |||
:* Hardcoding data for fields whose values are fixed | |||
:* Creating more application-friendly names for the remaining fields defined in the WSDL | |||
That customization is generally performed by an IT admin. The steps are covered below, under [[#Configuring a Web Service|Configuring a Web Service]] | |||
Once done, an application designer can add a step in a [[Process Model]] to start the Web Service interaction. The designer then uses the application-friendly names to: | |||
:* Map current record fields to and from WSDL input and output fields | |||
:* Specify fixed values for WSDL input fields | |||
:* Define expressions for WSDL input fields | |||
:* Define expressions that operate on WSDL output fields, before storing the resulting values in the record | |||
Those mechanisms are covered below, under [[#Working with a Web Service|Working with a Web Service]]. | |||
==Configuring a Web Service== | ==Configuring a Web Service== | ||
==Working with a Web Service== | ==Working with a Web Service== | ||
Revision as of 01:10, 12 September 2013
About Web Service Integration
Web Services whose connections are specified using the Web Service Description Language (WSDL), can be integrated into the platform without programming, using a few configuration steps.
In addition, the interface defined by the WSDL can be simplified to match the application by:
- Ignoring fields that are not needed
- Hardcoding data for fields whose values are fixed
- Creating more application-friendly names for the remaining fields defined in the WSDL
That customization is generally performed by an IT admin. The steps are covered below, under Configuring a Web Service
Once done, an application designer can add a step in a Process Model to start the Web Service interaction. The designer then uses the application-friendly names to:
- Map current record fields to and from WSDL input and output fields
- Specify fixed values for WSDL input fields
- Define expressions for WSDL input fields
- Define expressions that operate on WSDL output fields, before storing the resulting values in the record
Those mechanisms are covered below, under Working with a Web Service.