Atomic framework does not support Coveo JSUI-specific events.
Previously, Coveo's JSUI library provided the flexibility to customize the search behavior based on business requirements by using event handlers like buildingQuery, deferredQuerySuccess, doneBuildingQuery, and duringQuery. Now Coveo has an updated Atomic framework, which is easier and more flexible to build the search interface, but at the same time, it's not providing the same features as JSUI to handle the events to customize the search behavior. Any suggestions or workarounds to achieve how we are using the deferredQuerySuccess to modify the field values before the search initialization.Default Tab feature not available in Coveo Atomic Framework.
Default tab feature is not available in Coveo atomic framework. While going through the Coveo documentation, I came across an article which talks about the custom component available through the CDN link. With the help of CDN, we can use custom tab components. By using this Tab component CDN, we have the following limitations. 1- We can't customize the tab component to meet the additional business requirements, as it's already built and hosted. 2- Lot's of additional conditioning features was available in JSUI framework Tab components, which are not supported in this Atomic custom Tab Component. Any suggestions or workaround to resolve the above use cases.Not able to assign a separate field to atomic-result-link component
Hi Team, In the Coveo JSUI framework, we have the capability to customize the default behavior of result links by assigning specific data fields using the attribute data-field="@uri" to the class CoveoResultLink. This allows us to map the desired input to the specified field, thus enabling customization of result links according to our requirements. But how can we use the same in atomic-result-link. Do you have any suggestions or workarounds to address the use cases mentioned above?Challenges of Implementing Folding Structure within the Coveo Atomic Framework
When ever we are using Coveo atomic folding structure, following are the few challenges we faced 1. We've encountered an issue with the "show more" and "show less" buttons where clicking on "show more" causes the "show less" button to appear above the folding structure, which is not a good behavior for end user. 2. Another issue we've observed is with the displaying of the number of child results. when we are updating the component to display only to two child results. But, for some parent results we are seeing three items as an child. Any assistance on identifying solutions or resolutions to address this default behavior observed within the Coveo Atomic framework.
