SSPL Does Not Work Properly If System Attribute _transaction_id Is Used In the Filter Condition
(Doc ID 2748037.1)
Last updated on MARCH 14, 2024
Applies to:
Oracle BigMachines CPQ Cloud Service - Version 21 A Patch 2 and laterInformation in this document applies to any platform.
Symptoms
SSPL does not work properly if system attribute "_transaction_id" is used in the filter condition.
Steps to reproduce:
- Create an SSPL attribute and add the following filter: {Data table's column name:"|_transaction_id|"}
- Add it to the layout.
- Ensure the data table has lines that will return true for the above filter
- From a quote that qualifies for the filter click add to transaction
- Try setting a value for the SSPL attribute. No rows will be available
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 |