Operation Properties

To view or edit an operation's properties, double-click its Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.

The General tab contains the following properties:

Property	Description
Provider / Interface	[Read-only] Specifies the name of the service provider and its interface that own the operation. Click the Properties tools next to these fields to display the properties of these objects.
Name/Code/Comment	Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.
Stereotype	Extends the semantics of the object. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file.
Implementation	Specifies a link between the operation and an OOM operation or a PDM web service operation. Use the tools to the right of the box to select an implementation object, view the properties of the currently selected object, or remove it.
Keywords	Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas.

The following tabs are also available:

Input/Output - Contains the following properties:

Property	Description
Type	Specifies the type of the operation and how messages will be handled: `Undefined` – [default: no message] `One Way` – [input message only] The activity calls the web service and no response is expected. `Request-Response` – [input and then output messages] The activity calls the web service and a response is expected. Fault messages can also be sent as output in case of error. `Solicit-Response` – [output and then input messages] The web service solicits the activity and a response is expected. Fault messages can also be sent as input in case of error. `Notification` - [output message only] The web service solicits the activity and no response is expected.
Input / Output message	Specify names and message formats for the input and output messages. Select a format from the list or use the tools to the right of the list to create a format or view the properties of the currently selected format.

Property

Description

Type

Specifies the type of the operation and how messages will be handled:

Undefined – [default: no message]
One Way – [input message only] The activity calls the web service and no response is expected.
Request-Response – [input and then output messages] The activity calls the web service and a response is expected. Fault messages can also be sent as output in case of error.
Solicit-Response – [output and then input messages] The web service solicits the activity and a response is expected. Fault messages can also be sent as input in case of error.
Notification - [output message only] The web service solicits the activity and no response is expected.

Input / Output message

Specify names and message formats for the input and output messages. Select a format from the list or use the tools to the right of the list to create a format or view the properties of the currently selected format.

Faults - [Request-Response and Solicit-Response operations] Lists the fault links between the operation and a message format. You can add or create a fault using the Add Objects and Create an Object tools.