APPS.CSM_MAIL_RECIPIENTS_PKG dependencies on WF_NOTIFICATION

Line 63: from wf_notification_attributes wna

59: , wna.name
60: , wna.text_value
61: , wna.number_value
62: , wna.date_value
63: from wf_notification_attributes wna
64: where wna.notification_id = b_notification_id
65: and wna.name = b_flag_name;
66:
67: r_notification_attributes c_notification_attributes%rowtype;

Line 78: -- The properties mentioned are stored in wf_notification_attributes.

74:
75: -- Important. "Deleted" means on the mobile side. The notification
76: -- will *not* be deleted on the central database side.
77:
78: -- The properties mentioned are stored in wf_notification_attributes.
79: -- For every update of the record a check must be done if the
80: -- attribute is allready present or that it must be inserted.
81: -- For example in the situation where both the notification is read and
82: -- deleted, it is impossible to detect if this is done in one or two

Line 99: wf_notification.AddAttr

95: then
96: -- This records exists allready. We're done.
97: null;
98: else
99: wf_notification.AddAttr
100: ( p_record.notification_id
101: , 'READ_FLAG'
102: );
103:

Line 104: wf_notification.SetAttrText

100: ( p_record.notification_id
101: , 'READ_FLAG'
102: );
103:
104: wf_notification.SetAttrText
105: ( p_record.notification_id
106: , 'READ_FLAG'
107: , p_record.read_flag
108: );

Line 126: wf_notification.AddAttr

122: then
123: -- This records exists allready. We're done.
124: null;
125: else
126: wf_notification.AddAttr
127: ( p_record.notification_id
128: , 'DELETE_FLAG'
129: );
130:

Line 131: wf_notification.SetAttrText

127: ( p_record.notification_id
128: , 'DELETE_FLAG'
129: );
130:
131: wf_notification.SetAttrText
132: ( p_record.notification_id
133: , 'DELETE_FLAG'
134: , p_record.delete_flag
135: );