Release 21.3.0

1. Updated Ratings/Reviews purchase feed order export job to sort orders by creation date, ensuring that orders are exported in chronological order.
2. Updated Ratings/Reviews purchase feed order export job to save the date/time of the latest order exported as the new “Order Feed Job Last Execution Date Time” in yotpoJobsConfiguration custom object so that orders are not skipped if there are more than 1000 (SFCC limit) orders to be exported, the next run of the job will pick up where it left off rather than jumping ahead to the current date/time. If the new “Order Feed Job Last Execution Date Time” value would be the same as the previous value, it will report an error and shift the new value ahead by one minute to prevent an endless loop.
3. Fixed typos in order export job debug logs,

Release 21.2.1

1. Exposed a hashed customer token within the customer identification DIV for use by the Yotpo widget.
2. Updated the backfill customer and order jobs to be significantly more performant for large volumes of data. This primarily impacts new Yotpo customers who have previously existed on the SFCC platform and have accumulated large amounts of data that needs to be exported to Yotpo for backfilling the customer and orders lists. These also send data to Yotpo’s high performance batch backfill endpoint. The following points detail the current configuration following this change:
   1. Backfill jobs with name prefixed “Backfill”. These are meant to be run once and only viable for customers who have historical data on the SFCC platform. The other jobs are used for the real-time sending of Order and Customer data.
   2. Backfill jobs are controlled by the settings within the yotpoJobsConfiguration custom object - the loyalty_XXX_LastId serves as a pointer to that last object sent to Yotpo. As the job is running, that pointer is moved forward until it walks all the objects (either orders or customer). Once it's done walking, it sets the loyalty_XXX_ExportComplete boolean to true.
   3. To begin exports, merchant should set the loyalty_XXX_LastId to something that alphabetically comes “before” the records in the system. Typically a simple 0 (zero) should work since it falls alphabetically “before” most common order or customer numbers. The loyalty_XXX_ExportComplete should be unchecked.
   4. Use the BM Jobs screen to run the Job.
   5. If needed, a merchant may adjust the loyalty_XXX_LastId backward to resend objects to Yotpo (due to interruption or otherwise).
3. Exposed a new API endpoint for Yotpo to call when a customer redeems a free product loyalty reward, allowing customer to add the free item to a cart that is empty.
4. Miscellaneous minor improvements.

Release 21.1.1

The new release is primarily new code meant to be run as a job that periodically informs Yotpo's systems about simplistic cartridge version information.

Release 21.1.0

YTPOS-16 and YTPOS-18 Modify the location in code where a prefix is a…

…dded to the productID so the check for null productID is accurate. Change name of attribute sent to Yotpo from imageURL to image. Check for existence of pdict.yotpoConversionTrackingData before attempting to find it's properties.

Release 20.1.0

release-20.1.0

Add integration tests for all controllers that return JSON

Release 19.1.0

release-19.1.0

CBU Release 19.1.0