Siebel Order Management Infrastructure Guide > Signals > Creating Signal Actions >

Modifying Signal Properties for Signal Actions

Signal properties are similar to user properties on repository objects. Signal properties are name/value pairs used to configure processing. In this release, the only supported use of signal properties is to provide a CanInvoke check.

To modify signal properties for a CanInvoke check

• (Optional) You can specify a CanInvoke check by completing the fields in the Properties list as follows:
  • Name. CanInvoke:[Mode]
  • Value. A Boolean expression using one of the following:
    • Business component fields. The expression can be comprised of real business fields or pseudo business fields supported by Context Service. Allowed fields include the following list:

      Field	Comment
      [$IsNewRecordPending]	Not Applicable
      [$HasActiveRow]	Not Applicable
      [$IsInQueryMode]	Not Applicable
      [$CanUpdate]	Returns Y or N
      [$GetType]	Returns instance type such as Line Item, Header, XA

    • Profile attributes. As an example, the following table shows a properties setting for the SetFieldValue signal:

      Property	Example Attributes
      CanInvoke:Any	GetProfileAttr('Block Variable Map Operations')='N' OR GetProfileAttr('Block Variable Map Operations') IS NULL

Example of Signal Properties Settings for a CanInvoke Check

An example of fields set for a CanInvoke check are listed in Table 5.

NOTE:  If CanInvoke logic exists for a specific Mode, it overwrites the CanInvoke logic defined for the mode Any. In the example above, using Quote mode, the CanInvoke logic used will be [Status] = LookupValue('ORDER_STATUS', 'Open') instead of [Account Id] is not null.