DocumentationWorkfrontWorkfront Guide

SOAP module

Last update: Thu Nov 21 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User

You can use the SOAP module to connect to SOAP APIs in Adobe Workfront Fusion.

Access requirements

You must have the following access to use the functionality in this article:

Adobe Workfront plan*
Pro or higher
Adobe Workfront license*
Plan, Work
Adobe Workfront Fusion license**

Current license requirement: No Workfront Fusion license requirement.

Or

Legacy license requirement: Workfront Fusion for Work Automation and Integration

Product

Current product requirement: If you have the Select or Prime Adobe Workfront plan, your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described in this article. Workfront Fusion is included in the Ultimate Workfront plan.

Or

Legacy product requirement: Your organization must purchase Adobe Workfront Fusion as well as Adobe Workfront to use functionality described in this article.

To find out what plan, license type, or access you have, contact your Workfront administrator.

For information on Adobe Workfront Fusion licenses, see Adobe Workfront Fusion licenses.

Limitations of the SOAP module

NOTE
Redirects are disabled during WDSL loading. This is a security feature, but may mean that unverified redirects are blocked when the module is run.

The SOAP module is currently in beta and does not support:

  • Redefine elements
  • Fraction digits restrictions
  • Total digits restrictions
  • White space restrictions
  • Multiple parts in input and output messages. Only single part messages are supported
  • Custom XML Schema elements defined with the help of SOAP Encoding schemas and elements.
INFO
Example:
The following would not be recognized correctly by Workfront Fusion:
code language-none 
<complexType name="ArrayOfFloat">
   <complexContent>
      <restriction base="soapenc:Array">
         <attribute ref="soapenc:arrayType"
            wsdl:arrayType="xsd:integer[]"/>
      </restriction>
   </complexContent>
</complexType>
This example includes the soapenc:Array, soapenc:arrayType and wsdl:arrayType references, which are not yet supported in Workfront Fusion.

Workaround

If the SOAP module refuses to process the WSDL file or throws various errors in the module’s configuration, you may try using the universal HTTP > Make a request module instead:

  1. In Workfront Fusion, create a new scenario.

  2. Insert the HTTP > Make a request module in the scenario.

  3. Open the module’s configuration and fill in the following fields:

    table 0-row-2 1-row-2 2-row-2 3-row-2 layout-auto html-authored no-header
    Method POST
    Body type Raw
    Content type XML (application/xml)
    Parse response Enabled

  4. Open a new web browser window or tab.

  5. Paste the WSDL URL into the web browser’s address bar and fetch the XML file.

    The WSDL URL usually ends with ?wsdl, but not necessarily, for example http://voip.ms/api/v1/server.wsdl.

  6. If the WSDL file does not display directly in the web browser, open the downloaded file in a text editor.

  7. Search for the <service> or <wsdl:service> tag:

  8. Once located, copy the URL from the location attribute.

  9. In Workfront Fusion, paste the URL into the HTTP module’s URL field.

  10. Open the Online SOAP Client in a new web browser window/tab.

  11. Paste the WSDL URL into the WSDL URL field.

  12. Click Browse.

  13. Pick from the list of functions to the left, for example getLanguages.

  14. Copy the content of the Request XML text area.

  15. In Workfront Fusion, paste the copied content to the module’s URL field.

  16. Provide values for selected parameters by replacing the question marks with actual values:

  17. Close the module’s configuration by clicking OK.

  18. Execute the scenario or module.

recommendation-more-help
5f00cc6b-2202-40d6-bcd0-3ee0c2316b43