Assignment Criteria Not Considering Translated Symbolic Strings (Doc ID 2579423.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

Assignment Criteria is not considering translated symbolic strings. Please find below the scenario:

The following objects were used as an example:

• Workflow Policy Object: Campaign Contact Owner
   >  Assignment Object: Campaign Contact

• Existing Symbolic String: SBL_TRANSACTION_STATUS_DATE-1004224814-03E
  Locale: PTB = Data de status da transação

• Assignment Attribute: Transaction Status Date

                 Assignment Criteria: Transaction Status Date

                 Display Name: Transaction Status Date

                 Display Name - String Reference: SBL_TRANSACTION_STATUS_DATE-1004224814-03E

In Siebel Tools:

1) Create a new Symbolic String:  X_TRANSACTION_STATUS_DATE-1004224814-03E

Locale: PTB: X_TRANSACTION_STATUS_DATE-1004224814-03E = SN Transaction Date

2) Go to Assignment Criteria and locate 'Transaction Status Date'

3) Change the 'Display Name - String Reference' property from SBL_TRANSACTION_STATUS_DATE-1004224814-03E to X_TRANSACTION_STATUS_DATE-1004224814-03E

'Display Name' automatically changes from 'Transaction Status Date' to 'SN Transaction Date'

Do the same for the Assignment Criteria Attribute

4) Deliver the Workspace

5) Logon to the application SCCObjMgr_ptb

6) Go to Lista de Regras de atribuicao > Criterios

7) For the existing "Campaign Contact - Northeast US", create a new Criterios de Atribuicao

7) In the Criterios field, click in the dropdown

Result: The value "Transaction Status Date" is still being displayed and not "SN Transaction Date"

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.