Return to main navigation Page
When a Configuration isn't working, the cause can reside in many different areas.
General Configuration Troubleshooting
Check Rules using the Debugger.
Click a Favorite to locate the Debugger Import ID within the URL.
Are all condition and input attributes active and present on the Flow? Check the advanced function on the Recommended Items action. Any attributes needed here must be on the Flow.
The attributes can be hidden, but not inactive.
Configurator Recommending Incorrect Number of Parts
Rule Isn't Firing
Is the Rule active? Look at the Overall Status on the Rule List page.
The Rule can be inactive for 2 reasons:
Change to Attribute's Auto Update field not Reflected
If you have changed the Auto Update field on the attribute itself, it will not reflect the change. If your attribute is mapped to a Configuration Flow layout, you have to change the Auto Update value in the Configuration Flow as well.
The change will not take affect until the value is changed in both locations: the Attribute and the Configuration Flow.
Attribute Change not Reflected in the Configuration Flow
Attribute Value is Different than Expected
Either alter Conditions so only one rule fires, or combine Rules.
In general, simultaneously firing multiple Recommendation Rules causes confusion.
Multiple Updates Required to Change a Value
Review the order in which Rules fire and Attributes are set.
Flow is Different than Expected
Set Type is Different than Expected
If the set type on the attribute is set to None, then the user's input will override the rule's value. The Rule appears in the Pipeline Viewer, but does not change the Configurator value.
Places to check the Set Type on the admin side include the:
Recommendation Message Unexpectedly Appears for Text Field Containing Delimiters
If a Recommendation Rule associated with an Attribute has a Text data type and the Attribute's recommended value BML script returns as a String, the system will display the tokens that are split along the following delimiter sequence in the System Recommended message when the following character sequence is used: |^|
Using another character sequence will resolve the issue.