Unexpected Behaviour With Field Trigger Groovy (Doc ID 2181409.1)

Last updated on SEPTEMBER 12, 2016

Applies to:

Oracle Fusion Sales Cloud Service - Version 11.1.10.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.10.0.0 version, Accounts, Contacts, Households

ACTUAL BEHAVIOR
---------------
Unexpected behaviour with Field Trigger Groovy

There is a behavior with the groovy script, which I don't understand. Could you please explain? When I change the Associated Account a field trigger is triggered. It changes the field AccountExternalId_c but doesn't change the field Company_c. Here the script to make it easier:

if(Organization != null) {
  if(WebSite_c != Organization?.WebSite_c) {
  setAttribute('WebSite_c', Organization?.WebSite_c)
  }
  if(Company_c != Organization?.OrganizationName) {
  setAttribute('Company_c', Organization?.OrganizationName)
  }
  if(AccountExternalId_c != Organization?.ExternalId_c) {
  setAttribute('AccountExternalId_c', Organization?.ExternalId_c)
  }
}


EXPECTED BEHAVIOR
-----------------------
Both fields should reflect the updated value

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure the trigger on a field and change the field.
2. Only ExternalId is getting updated but the name is not.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot see the updated value.

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