How to Map Actions in the Web Service Access Designer and Generate the Action Set › Add Web Service Operations and Map Actions in the Web Service Access Designer

Add Web Service Operations and Map Actions in the Web Service Access Designer

Add any number of Action Sets to a single site project in the Web Service Access Designer. Map the Actions to access the business logic in the WSDL file.

Follow these steps:

1. Right-click an Action in the Web Service Access Navigator and click Open.

   The Action displays in an editor in the Editor view.

2. Expand the Web Services node to the required operation in the Web Service Access Navigator.

   Note: The Web Services must be already imported.

3. Right-click the Web Service operation and click Add to Action Steps.

   Note: You can also drag-and-drop Web Service operations.

   The operation is added to the Action Steps in the Editor view.

4. Click the operation in the Editor view.

   The parameters' information displays in the mapping tabs. You can navigate to input or output mapping using the Input Mapping and Output Mapping tabs. By default, the Input Mapping tab is active.

   Parameter

   Indicates the name of the parameter. You cannot change the name of the parameter.

   Data Type

   Indicates the data type of the parameter. You cannot change the data type of the parameter.

   Mapping Style

   Specifies the mapping style of the parameter. Select any one of the following mapping styles:

   None—Identifies that no mapping is required for this parameter. You can choose not to assign a mapping for a parameter. This results in the parameter not being used on the user interface.

   Field—Identifies that a request to a Web Service or response from a Web Service is a text field.

   Literal—Identifies that a request to a Web Service or response from a Web Service is a value.

   Not Set—Indicates that no mapping is required for this parameter.

   Table—Identifies that a request to a Web Service or response from a Web Service is a two-dimensional array. Use this mapping style to map fields to columns. Specify a collection parameter as a Table and define the table through a separate dialog box before you map the child parameters to columns.

   Column—When a collection parameter is defined as a Table, map the child parameters to columns. Map one parameter to one column. Columns are identified by indices (0-based).

   Row—Selects a single row of data from a collection that can be mapped to individual fields in the HTML page. The fields in the HTML page must contain a unique ‘id’ attribute to be mapped.

   Mapping

   Defines any data specific to the parameter.

   • If you select Field as the Mapping Style, use this column to map a field to text, textarea, or td.
   • If you select Row or Column as the Mapping Style, use this column to add any numeric data. Non-numeric values are not saved.
   • If you select Table as the Mapping Style, a <…> button shows in the Mapping field, which opens a dialog box prompting for inputs like Table Name, Max Rows, Max Columns, Starting Row, Fixed Size, and Unbound.

   Note: You may see a red X symbol in the Web Service Access Navigator, the action name, or the parameter name in the Editor view. This means that all the parameters showing the red X symbol must be resolved.

5. Navigate to the Output Mapping tab to map the output fields after you finish mapping the HTML controls on a web page as inputs to the Web Services. Map the input parameters and the output parameters.
6. Save the site project.

The mapping information will eventually allow the Web Service Access Designer to generate the required XML and XSL files for data access in the site directory.

If you delete an HTML control or rename the ID/name of an HTML control in Adobe Dreamweaver that is mapped in the Web Service Access Designer perspective, an error is displayed in the Problems view.