Time Based Rule Triggers Display Incorrectly after Reloading the Rule in Experience Manager
Last updated on JUNE 01, 2018
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 11.3 and later
Information in this document applies to any platform.
On : 11.3 version, Customer Experience (Xmgr, Assembler, Workbench, Application Development)
When creating a rule that uses time based rule triggers, if we set the rule to trigger in June (06/01/2018) the next time we access that rule in XM we see the trigger is showing as July (07/01/2018)
Testing this using other months showed similar behavior (rules saved as 09/01/2018 when reloaded show as triggering 10/01/2018).
This issue is only effecting our Chrome XM users, and it not reproducible when accessing rules through Firefox.
Additionally, if we check the actual code the "correct" month is saved as the rule trigger, the issue is merely with the Display of the trigger in XM.
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