Oracle Utilities OCI Stream Responsys Notif Send
The mapping details for Oracle Utilities OCI Stream Responsys Notif Send are as shown in the table below:
OCI Target Notification Stream
"Responsys
//rest/api/v1.3/campaigns/{notifcationTemplate}/sms
//rest/api/v1.3/campaigns/{notifcationTemplate}/email "
DVM
Comments
Element Name
Parent Element
Type
Element Name
Parent Element
Type
 
 
messageId
 
Field
 
 
 
 
Not Mapped
origin
 
Field
 
 
 
 
Not Mapped
accountId
 
Field
optionalData/value (optionalData/key = INT_ACCOUNT_ID')
mergeTriggerRecordData/mergeTriggerRecords
 
 
 
notificationType
 
Field
optionalData/value (optionalData/key = INT_NOTIFTYPE')
mergeTriggerRecordData/mergeTriggerRecords
 
 
 
cisDivision
 
 
 
mergeTriggerRecordData/mergeTriggerRecords
 
 
Not Mapped
contactId
 
 
optionalData/value (optionalData/key = INT_CONTACT_ID')
mergeTriggerRecordData/mergeTriggerRecords
 
 
 
personId
 
 
optionalData/value (optionalData/key = INT_PERSON_ID')
mergeTriggerRecordData/mergeTriggerRecords
 
 
 
language
 
 
 
mergeTriggerRecordData/mergeTriggerRecords
 
 
 
firstName
 
 
optionalData/value (optionalData/key = INT_FIRST_NAME')
mergeTriggerRecordData/mergeTriggerRecords
 
 
 
lastName
 
 
optionalData/value (optionalData/key = 'INT_LAST_NAME')
mergeTriggerRecordData/mergeTriggerRecords
 
 
 
deliveryChannel
 
 
 
 
 
OUTL-BRT-NOTIFHUB_
DeliveryChannel
This lookup is used to determine if the SMS or Email campaign API needs to be invoked.
deliveryValue
 
 
fieldValues
mergeTriggerRecordData/mergeTriggerRecords
 
 
 
notificationTemplate
 
 
 
 
 
 
This value is used to populate the campaign name in the API URL.
deliveryInstance
 
 
 
 
 
 
This value is used to determine the Responsys instance to invoke. RESP1,RESP2,RESP3 correspond to three Responsys instance connections that is provided out of the box.
 
 
 
fieldValues
mergeTriggerRecordData/mergeTriggerRecords
 
 
Mapped to fieldName CUSTOMER_ID as contactination of accountId | personId.
 
 
 
fieldNames
mergeTriggerRecordData
 
 
Multiple fieldNames nodes with each mapped as following EMAIL_ADDRESS_ if the campaign type is email MOBILE_NUMBER_ if the campaign type is sms CUSTOMER_ID_
data
 
List
 
 
 
 
 
key
data
Field
optionalData/key
 
 
 
 
value
data
Field
optionalData/value
 
 
 
 
 
 
 
matchColumnName1
mergeTriggerRecordData/mergeRule
 
 
EMAIL_ADDRESS_ for Email MOBILE_NUMBER_ for SMS. These values are hardcoded in the flow.
 
 
 
matchColumnName2
mergeTriggerRecordData/mergeRule
 
 
null
 
 
 
insertOnNoMatch
mergeTriggerRecordData/mergeRule
 
 
True. Same for Email and SMS.
 
 
 
defaultPermissionStatus
mergeTriggerRecordData/mergeRule
 
OUTL-BRT-NOTIFHUB_ConfigProps
This is the same value sent for Email and SMS.
 
Property name: resp.email.permission
 
 
 
rejectRecordIfChannelEmpty
mergeTriggerRecordData/mergeRule
 
OUTL-BRT-NOTIFHUB_ConfigProps
Property name: resp.reject.channel.empty
 
 
 
optoutValue
mergeTriggerRecordData/mergeRule
 
OUTL-BRT-NOTIFHUB_ConfigProps
Metadata value to indicate optoutValue.
 
Property name: resp.optout.value.
 
 
 
optinValue
mergeTriggerRecordData/mergeRule
 
OUTL-BRT-NOTIFHUB_ConfigProps
Metadata value to indicate optinValue.
 
Property name: resp.optin.value
 
 
 
updateOnMatch
mergeTriggerRecordData/mergeRule
 
OUTL-BRT-NOTIFHUB_ConfigProps
Property name: resp.update.on.match
 
 
 
htmlValue
mergeTriggerRecordData/mergeRule
 
 
“H” Same for both Email and SMS
 
 
 
textValue
mergeTriggerRecordData/mergeRule
 
 
“T” value is passed
 
 
 
matchOperator
mergeTriggerRecordData/mergeRule
 
OUTL-BRT-NOTIFHUB_ConfigProps
Same for both SMS and Email. Property name: resp.match.operator