Web Service UDR Type Structure

When you save a Web Service (WS) profile, several User Defined Record (UDR) types are automatically created and mapped according to the specifications in the WSDL file.

Accessing UDR Types

To view the Web Service UDR types:

Open the APL Code editor.
Right-click on the text pad and select UDR Assistance.
Scroll down the UDR types list to the WS folder.

UDR Assistance button

UDR Types and Creation Context

The following table summarizes the key UDR types, when or why they are created, and where they are stored within the folder structure:

UDR Type	When/Why It Is Created	Where It Is Stored / Folder Structure

UDR Type	When/Why It Is Created	Where It Is Stored / Folder Structure
`Abstract[port type name]WSCycle`	For every WS profile	`WS.[Directory Name].[WSProfile Name].cycles.[WSCycleUDR Names]`
`WSCycleUDR`	For every WSDL operation	`WS.[Directory Name].[WSProfile Name].cycles.[WSCycleUDR Names]`
`UDR type (complex type)`	When complex types are defined in the XML Schema	`WS.[Directory Name].[WSProfile Name].[alias].[complexTypeUDRs]` Alias = Target Namespace (tns) from XML Schema. If the tns has no name alias, the UDR is saved in the `[WSProfile Name]` folder
`AbstractWSCycle`	Always present in the WS folder (default)	WS folder (default location)
`ws.QName`	Always present in the WS folder (default, only one per WS folder)	WS folder (default location)
`XML Element`	Always present in the WS folder (default)	WS folder (default location)

The UDR folder structure

Note!
When concatenating WSDL files, the aliases in the files may be identical. If this occurs, the structure is changed to avoid a name conflict. If the names include invalid characters, they are replaced with underscore characters.

Example structure:

WS.[Directory Name].[WSProfile Name].[WSDL Filename].[alias]

If the WSDL filename includes invalid name characters, these are replaced with underscore characters in the WSDL Filename.

Note!
If the WSDL file that you use to configure the WS profile includes a variable named "Thread", it is automatically changed to "thread". You must then rename the variable to “thread” in the APL code in the Analysis or Aggregation agent in your workflow. This prevents compilation issues when you try to compile your workflow.

The section has the following subsections: