My Oracle Support Banner

Recommendation Rule Displays Message Based on Input Default Value Instead of Current Value in Search Flow (Doc ID 2440947.1)

Last updated on SEPTEMBER 05, 2018

Applies to:

Oracle BigMachines CPQ Cloud Service - Version 18 B and later
Information in this document applies to any platform.

Symptoms

It is noticed that with a search flow, an attribute which is the action attribute in a recommendation rule A and also an input in an AJAX rule B, will have the recommendation message from A showing based on the default value for the input in A, instead of current value.

Steps to Reproduce:
1. Create a search flow
2. In the search flow, create 3 attributes(single select menu is easiest)
3. Create a recommendation rule that uses attribute 1 as input, attribute 2 is the action
4. Create an AJAX rule(constraint or hiding rule) that has attribute 2 as input, attribute 3 as action
5. Put attributes in layout, deploy

Expected Behavior:
When updating attribute 2, the recommendation rule should always use the current value of attribute 1 to decide if the rule should run. Only on update would the value of attribute 1 as an input change.

Actual Behavior:
After attribute 2 is changed, the input to the recommendation rule is treated as the default value for attribute 1. This page state stays until update is clicked again.

This issue can be reproduced in 18B and 18C.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


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