Redesigned order management, a batch lookup for workflows, and store actions in the Audit Log
A redesigned admin Order History with inline status changes, a workflow node that reads many traders at once, and store actions in the Audit Log.
01 ·A redesigned admin Order History
The Order History page a broker's team works in, under Settings and the store, was redesigned. The columns were cleaned up: Redemption ID reads as Order ID, Name of Product reads as Product, and the product type, voucher code, and voucher expiry columns are hidden by default and can be switched back on under the Fields tab. Each order's status now shows as a colored pill, and clicking its arrow opens a dropdown of every status the broker set up in store settings, grouped by category, with the order's current status already selected, so a status change happens right on the row.
Clicking any order opens a details modal that matches the one a trader sees on their own purchase history: the product with its image, quantity, order number, and price, the order status timeline, the product details, and the customer's name, phone number, email, and address. The admin view leaves out the trader's refund button and adds the buyer's email to the customer details.
Managing a redemption from the same row it sits on, with the buyer's contact details one click away, cuts the steps a broker's support team takes to move an order along and reach the trader who placed it.
02 ·A workflow node that looks up many traders at once
Data Workflows gained a Get Users node that reads several traders in a single step. You hand it a list of traders, identified by whichever unique identifier your community keys on, and it returns each one's email, username, and the fields you asked for, with a short note on any row it could not match. It is the batch counterpart to looking a single trader up, so a workflow can pull a group's data and act on all of them together.
Reading a whole list of traders in one workflow step lets a broker drive downstream actions, such as syncing a segment into a CRM or BI tool, off a single lookup rather than one call per trader.
03 ·Store management in the Audit Log
The admin activity log, now named the Audit Log, records every action a broker's team takes across store management and order history. That covers the store itself (name, description, banners, widget settings), categories, products and their pricing and discounts, vouchers, redemption options, the information collected at checkout, access and permissions, custom order statuses, and each change to an order's status. Every entry reads one of three ways: the action taken, a field set for the first time, or a field changed from its old value to the new one, and an Email column was added so each action ties back to the admin who made it.
A running record of who changed a price, a permission, or an order status gives a broker running the store with more than one admin a way to trace a change back to its source when a trader queries it.
The wheel section of the Spin the Wheel widget now takes its background and padding from the widget's global section styling, so it can be styled together with the other sections on the page.
2 JulClearer error responses when a user-field history entry cannot be created over the API.
2 JulThe store toggle in the navigation bar settings can now be switched on whenever the store itself is enabled.
2 JulA workflow router's nested branches now keep their run history.
2 JulThe mini-game custom widget setting now lists more than twenty games.
2 JulThe rewards store now runs on a single shared store module, mounting once the active community is known for a steadier start.
2 Jul