18 Results for Category CloudCraze
A seamless checkout process is an important aspect of B2B Commerce. We want the process to be as quick and painless as possible. Any delays will make users think twice about finalizing the order. One way to enhance the process is to preload address books for users at the time of site launch. Most users do not want to retype their Bill To and Ship To addresses at checkout, if that information has already been provided and stored in the system. A simple preloaded address book is a quick win and provides a great user experience in the first step of the checkout process. Below are steps to mass preload address books using existing data in your system.
It's not uncommon for particular CloudCraze API calls to fail within a test because they aren't executed as a community portal user. One example of this, that we recently encountered, is with regard to the `ccrz.ccApiWishList.create()` method. In order to address scenarios like these we'd need to simulate a CloudCraze Community Portal User. There are a number of challenges that make creating a portal user difficult.
Many times, there is a need to create custom fields on objects for storing project specific custom data. We can create custom fields on any Salesforce B2B Commerce Cloud (previously CloudCraze) custom objects. However, below steps need to be followed in order to expose those fields on CC model and to be used on UI level when pages are rendered on storefront.
Communication with customers is an imperative aspect of B2BCommerce. Many organizations have specific customer service teams set aside to handle any issues raised by users of a B2B commerce system. Customer service has several communication channels , among them a live chat feature has been gaining popularity. This is not a chat bot. Those have a place as well, but this post concerns itself with the value added proposition of supporting ones customers via an actual human being. Read this blog for a step by step guide on how to implement Live Agent chat.
Dealing with the exporting and importing of data when refreshing sandboxes is an issue that most SFDC orgs wrestle with. In Salesforce B2BCommerce, this entails base migration of three objects relating to configuration of the application, as well as secondary (but still required objects) for Page Labels, Page Sections, Products, Price Lists, and Specs (just to name a few).
While there are a few third-party products out there that offer varying degrees of solutions to this dilemma - I've developed a proof of concept that leverages the Metadata API and Static Resources to allow a configurable solution that can be implemented not only from a typical production-to-sandbox scenario, but from sandbox-to-sandbox or sandbox-to-production.