Date: July 14, 2026
Issues: 16
Has your company built a CAD extension to go beyond the standard automation of AutoCAD, Inventor, or SolidWorks files? Learn more about Microsoft's transition of long-term support to .NET v10, and how to test your older custom CAD extensions for compatibility at https://cpqhelp.link/dotnet.
![]() |
Features and improvements with this icon are based on customer suggestions submitted to Epicor Ideas. |
New Features and Improvements |
|||
| CPQ-6356 | The "Group By" clause added to Snap query block. |
||
![]() |
CPQ-6364 | Wildcard search added to Snap code dropdown lists. When writing Snap code, you may need to select from a list of items. A new wildcard search can help you easily find matching items from longer lists. For example, when picking a custom type from a list of many types, enter "ab*f" to filter that list to only items containing a word that starts with "ab" and ends with "f".
|
|
![]() |
CPQ-4450 | New Cancel button for the integration with Salesforce.com. When using this integration, a new Cancel button allows the user to abandon the currently-open configurator and return to the Salesforce quote without any new quote line appearing on the quote. This can prevent the buildup of un-necessary and confusing quote lines as your customers browse through other configured products before submitting their quote. |
|
![]() |
CPQ-5176 | Error emails sent to administrators are now throttled. If one error occurs multiple times within a time period, each error continues to be logged as before, but only one notification is sent to administrators in that time period. This alleviates the alert system from spamming administrators in high-volume implementations. |
|
| CPQ-5192 |
New authentication method for Salesforce.com integration: OAuth 2.0. If your company embeds Epicor CPQ within your Salesforce.com quotes, please update your authentication method to OAuth 2.0 before the salesforce-mandated October 2026 deadline. |
||
![]() |
CPQ-5575 |
New optional behavior for the Quote Header Loaded Rule. Previously, quote header rules did not save quote header field values before executing workflow actions. Now, a new option under admin > settings > settings allows each Epicor CPQ customer to choose how their quote headers behave: either follow the classic behavior (by default), or to save quote header values before executing workflow actions. Learn more unabout this "Save Quote Header Values Before Executing Workflow Actions" setting. If your company sees value in the new behavior, ensure you test the new logic across all your quote headers and workflows. This is a company-wide setting, and will apply to all quotes being submitted. |
|
| CPQ-6295 |
KB3D: new isOutput flag customizes your scene for printed use. Similar to the existing isRender flag, this new flag allows you to add logic to your scene to change scene visuals when the scene is being rendered as an output image. For example, you can add a logo or watermark, reveal or conceal a measurement grid, or make other visual effects appear only in this "printed" version that appears in output documents, while your online interactive version of the scene remains the same. |
||
| CPQ-6301 | The integration with Oracle CPQ/BMI has been updated to v2 of the Oracle CPQ API, making this integration more secure. | ||
| CPQ-6338 | Transaction logs enhanced for the integration with Epicor Kinetic. | ||
![]() |
CPQ-6347 | Comments added when committing and deploying code sets now can be saved by pressing the ENTER key, and line breaks can be added by pressing SHIFT-ENTER. | |
|
|||
| CPQ-6334 | Some translations have been updated. | ||
| CPQ-6351 | The "Set Nested" Snap block would not save correctly. This has been fixed. | ||
| CPQ-6371 | In some cases, the anonymous user could be asked to login even if "allow anonymous user" is set to true. This has been fixed. | ||
| CPQ-6335 | The icon for the Snap Assistant has been updated. | ||
| CPQ-6355 | Various small bugs in the Snap Assistant user interface have been fixed. | ||
| CPQ-6360 | An error would occur when calling a Global Function in the context of a document rule when added as a parameter array. This has been fixed. |

