Issues With The OOTB Solution For Recipient Groups (Doc ID 1665897.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Communications, Media and Energy CRM - Version 8.1.1.10 [23021] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.10 [23021] version, Comms Server & Email Response

ACTUAL BEHAVIOR
---------------
Whilst configuring a custom Recipient Group for sending emails the customer identified the following issue:

1. This process relies on using the LIC field of the List Of Values to represent the name of the Business Object or Business Component used for the recipient group. As per bookshelf:

http://docs.oracle.com/cd/E14004_01/books/eMail/eMail_ConfigUI6.html#wp1005994

Optionally, complete the following steps to create a new List of Values item of the COMM_RECIP_SRC type, if one does not already exist that specifies the business object that serves as the recipient source for the recipient group you require:

- Locate a record of the COMM_RECIP_SRC type for which the Parent LIC (Language-Independent Code) field contains no value.
- Copy the record.
- Set the Display Value and the Language-Independent Code fields for the new record to the business object name that represents the recipient source (for example, Campaign, Account, and so on).

The issue here is that the LIC field is only 50 characters long and a Business Object Names can be up to 75 characters long.

2. There are a number of examples in the COMM_RECIP_SRC list of values which have the same LIC but different Display Values (such as Contact, Comm Contact, etc), but if you try to create a new entry in this LOV which has the same LIC as another entry, but with a different Display Value then the following error appears:

- Found another LOV record with the same language independent code but different display value 'Account Contacts'.(SBL-SVC-52159)

This is a result of the compliance checks introduced in version 8.x to the list of values. As described in Doc ID: 843895.1, this can be overcome by disabling these compliance checks via a user property on the BC. However, there appears to be no provision should we want to keep these compliance checks (clearly useful in a multi-lingual environment).


EXPECTED BEHAVIOR
-----------------------
The Language-Independent Code field on the LOV table should be able to accept the same amount of characters as the Business Object field defined in Siebel Tools.

You should be able to modify the name of the Recipient group without having to set the compliance check BC user property As described in Doc ID: 843895.1

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms