Summary of Notifications That Siebel Open UI Supports
The following table describes the notification types that Siebel Open UI supports. For more information, see New Notification User Interfaces.
Notification | Type | Description |
---|---|---|
NotifyBeginNotifys |
SWE_PROP_BC_NOTI_BEGIN |
Notifies the client business component that the request that Siebel Open UI sent to the Siebel Server resulted in at least one notification from a business component. |
NotifyStateChanged |
SWE_PROP_BC_NOTI _STATE_CHANGED |
Specifies a top-level notification for more than one state change that occurs in the business component level. Siebel Open UI uses the following properties to identify the change and to get the data associated with the change:
Siebel Open UI can provide summary or detailed state information. For more information, see NotifyStateChanged Notification Type. |
NotifyGeneric |
SWE_PROP_BC_NOTI_GENERIC |
Identifies the predefined and custom notifications that the Siebel application must send. Siebel Open UI addresses most predefined generic notifications to a particular applet. You can use NotifyGeneric to get the exact type for a generic notification. Siebel Open UI provides actual information of the changes as an encoded argument set. |
NotifyNewSelection |
SWE_PROP_NOTI_SELECTED |
Notifies the client business component that a change occurred in the selection status. Siebel Open UI calls NotifyNewSelection two times for each selection status change:
You cannot use NotifyNewSelection with a multi-select. You can use the following syntax in the property set that Siebel Open UI sends:
where:
|
NotifyNewActiveRow |
SWE_PROP_BC_NOTI_ NEW_ACTIVE_ROW |
Notifies the client business component that a change occurred on an active row of the corresponding business component on the Siebel Server. Siebel Open UI usually uses NotifyNewSelection with NotifyNewActiveRow. You can use the following syntax:
where:
|
NotifyDeleteRecord |
SWE_PROP_BC_NOTI _DELETE_RECORD |
Notifies the business component in the client that Siebel Open UI deleted a record from the current set of records on the Siebel Server. Siebel Open UI might use this notification two times for a single record deletion. You can use the following syntax in the property set that Siebel Open UI sends:
where:
For an example usage of this notification, see Customizing the Presentation Model to Handle Notifications. |
NotifyDeleteRecordSet |
SWE_PROP_BC_NOTI _DELETE_WORKSET |
Notifies the business component in the client that Siebel Open UI is deleting a record from the current set of records in the client. Does not correspond to a method invoke. Siebel Open UI sends a separate notification for each record that it deletes. You can use the following syntax in the property set that Siebel Open UI sends:
where:
For more information, see Using Notifications with Operations That Call Methods. |
NotifyInsertWorkSet |
SWE_PROP_BC_NOT I_INSERT_WORKSET |
Notifies the business component in the client that Siebel Open UI is inserting a new record in the current set of records in the client. You can use the following syntax in the property set that Siebel Open UI sends:
where:
For more information, see Using Notifications with Operations That Call Methods. |
NotifyNewData |
SWE_PROP_BC _NOTI_NEW_DATA |
Notifies the business component in the client that Siebel Open UI is modifying the current set of records. Siebel Open UI sends this notification only if it modifies a record. It does not send this notification if it only modifies a field value. |
NotifyNewPrimary |
SWE_PROP_BC_ NOTI_NEW_PRIMARY |
Sets the primary record in a multi-value group. The RepopulateField notification calls NotifyNewPrimary. |
NotifyNewRecord |
SWE_PROP_BC_ NOTI_NEW_RECORD |
Notifies the client business component that Siebel Open UI is creating a new record in the current set of records on the Siebel Server. You can use the following syntax in the property set that Siebel Open UI sends:
where:
For a similar usage of this notification, see Customizing the Presentation Model to Handle Notifications. |
NotifyNewRecordData |
SWE_PROP_BC_NOTI_ NEW_RECORD_DATA |
Sets the do populate flag. |
NotifyNewDataWorkSet |
SWE_PROP_BC _NOTI_NEW _RECORD_DATA_WS |
Updates a record in the current set of records. |
NotifyNewFieldData |
SWE_PROP_BC_NOTI_ NEW_FIELD_DATA |
Notifies the client business component that Siebel Open UI modified a field value on the Siebel Server, and that Siebel Open UI communicated this modification to the client through the NotifyNewDataWorkset notification. You can use the following syntax in the property set that Siebel Open UI sends:
where:
|
NotifyNewDataWorkset |
SWE_PROP_BC_NOTI_ NEW_DATA_WS |
Notifies the client business component of a field value that Siebel Open UI modified for a field that resides on the Siebel Server. You can use the following syntax in the property set that Siebel Open UI sends:
where:
You can use the following syntax in the child property set:
where:
|
NotifyNewFieldList |
SWE_PROP_BC_ NOTI_NEW_FIELD_LIST |
Refreshes the entire view internally. |
NotifyNewRecordDataWS |
SWE_PROP_BC_NOTI_ NEW_RECORD_DATA_WS |
Updates the values in the record set. Siebel Open UI updates the dirty flag during previous notifications. |
NotifyChangeSelection |
SWE_PROP_BC_ NOTI_CHANGE_SELECTION |
Sets the update conditionals flag and the row counter. |
NotifyEndNotifys |
SWE_PROP _BC_NOTI_END |
Notifies the client business component that Siebel Open UI is ending the notification, and that no more server notifications exist for the current transaction. |
NotifyBeginQuery |
SWE_PROP_BC _NOTI_BEGIN_QUERY |
Notifies the client business component that Siebel Open UI started a query on the business component on the Siebel Server. |
NotifyNewQuerySpec |
SWE_PROP_BC_ NOTI_NEW_QUERYSPEC |
Siebel Open UI uses the NotifyNewQuerySpec notification if the user refines a query. If the business component search specification is empty, then NotifyNewQuerySpec clears all field search specifications. |
NotifyNewFieldQuerySpec |
SWE_PROP_BC_NOTI_ NEW_FIELD_QUERYSPEC |
Notifies the client business component that Siebel Open UI is doing one of the following to query the fields of the current business component on the Siebel Server:
This situation can occur through a predefined or custom configuration, or in reply to a query that the user performs. You can use the following syntax in the property set that Siebel Open UI sends:
where:
|
NotifyEndQuery |
SWE_PROP_BC_ NOTI_END_QUERY |
Notifies the client business component that Siebel Open UI is ending a query on the business component on the Siebel Server. This situation can occur if the ExecuteQuery method or the UndoQuery method runs. |
NotifyExecute |
SWE_PROP_BC _NOTI_EXECUTE |
Notifies the client business component that Siebel Open UI is running a business component on the Siebel Server. You can use the following syntax in the property set that Siebel Open UI sends:
where:
|
NotifyScrollAmount |
SWE_PROP_BC_ NOTI_SCROLL_AMOUNT |
Sets the scroll folder and the amount for a mobile swipe operation. |
NotifyPageRefresh |
SWE_NOTIFY_PAGE_REFRESH |
Updates the urltogo with the URL that Siebel Open UI uses to refresh a view. Siebel Open UI gets this URL from a subsequent executeurltoGo notification. |