Siebel Order Management Infrastructure Guide > Signals >

Creating Signal Actions

You create and modify signal actions in the Signals view. You can set the sequence for a group of actions, set input arguments for actions, and set filter values that determine when an action executes.

To create and modify signal actions

1. Navigate to Administration - Order Management > Signals.
2. In the Signals list applet, select an existing signal to modify, or create a new signal record.
3. Lock the signal by checking the Locked Flag box.

   This locks the object for your user ID.

4. If you are creating a new signal, give it a name and description, and then save the record.
5. In the Versions list applet, click the Work Space link to drill down to the Actions list applet.
6. In the Actions list applet, create a new action, or select an existing signal action.
7. Complete the fields.
   1. Set the Sequence field value to reflect the sequence number of a particular action relative to other actions for the signal.
   2. Set the Service Type field to specify whether the action is a business service method or a workflow:
      • If you specified that the signal action is a workflow, enter the workflow's name in the Service Name field and enter "RunProcess" in the Service Method field.
      • If you specified that the signal action is a business service method, enter the business service name in the Service Name field and enter the method name in the Service Method field.
   3. (Optional) Set filter fields for the action as described in the table that follows.

      Filter fields limit the execution of a signal action. The action occurs only if all filter field values specified match the current situation.

      Filter Field	Allowed Values	Description
      Application Name	Any "Application" repository object name	Used to define industry-specific or channel-specific logic.
      Mode	Any string from the ISS_MODE LOV	Must match the value of the Mode user property on the business component (such as Quote, Order, Asset or Agreement).
      Instance Type	Any string from the ISS_INSTANCE_TYPE LOV	Must match the integration component name from the integration object specified in the business component "Instance Uniform Name EAI Object:[Current Business Object]" user property, for example, "Header", "Line Item", or "Payments".
      Fields	A semi-colon-separated list of field names (example: "Account; Product; Net Price")	The business component fields for which the action is executed. The action occurs if the active field in the calling business component appears in the list.
      Condition	A Siebel logical expression that returns TRUE or FALSE.	If the condition is not empty, the action is only invoked when the condition returns TRUE.

8. (Optional) In the Parameters list applet (at the bottom), enter input arguments for the action.

   As an example, parameters for the CalculatePrice signal are listed in the following table:

   Input Argument	Example Value
   CPScope	Whole
   RowScope	Selected
   SubPSPWFName	Pricing Procedure - Default
   Variable Map - Context	Default Pricing Variable Map - Context
   Variable Map - Row Set	Default Pricing Variable Map - Row Set

9. (Optional) You can specify a CanInvoke check by completing the fields in the Properties list applet. See Modifying Signal Properties for Signal Actions.
10. Navigate back to the Signals list applet.
11. Click the Release New Version button to release the signal version.
12. If you are creating a new signal action, create a button, script or workflow to invoke the signal. See Invoking Signals from Controls and Custom Script.
13. Test the signal.

    You test the signal by triggering the appropriate event.

    NOTE:  After releasing a new version, you must start a new user session (by logging out and logging in again) to test the latest version.

14. Using Application Deployment Manager (ADM), promote the updated signal definition to the production environment. See Going Live with Siebel Business Applications for details on using ADM.