WovenIQ — Release R1.80

Highlights

• Per-job create vs update control: Each integration job can allow new records, updates to existing records, both (the default), or neither — for syncs to Salesforce, Lightspeed, or Adaptive.
• Order-driven product interests: Optional packaged automation marks matching Product Interest records as ordered when an Order is activated or when Order Item lines are added or updated on an activated order.
• Richer keyword search: Results columns follow a configurable Contact field set, with a Primary SA filter and a responsive toolbar on tablet and phone.
• Reassign sales associates from the profile: Users with WovenIQ - Allow Owner Change can change Primary Sales Associate (Contact owner) and Secondary Sales Associate directly on the customer profile.
• Podium default owner: New Podium contacts can be owned by the Store Concierge configured on the related Store.
• Turn off automatic AE reassignment on check-in: Set Find AE By N Consecutive Assistance to 0 or -1 to leave Primary Sales Associate unchanged when a customer is matched on queue check-in.
• Optional product hearts in follow-up emails: Product-interest image carousels can show or hide favorite heart icons per email template.

What’s new for everyone

• Keyword Search: Search results show columns from your org’s packaged Contact field set (default columns include name, email, phone, key dates, and Primary Sales Associate). Filter by Primary SA before searching, and use the updated toolbar layout on smaller screens.
• Customer profile ownership (permitted users only): Associates who have WovenIQ - Allow Owner Change see a change-owner control beside Primary Sales Associate and Secondary Sales Associate and can pick a new user from a modal.
• Follow-up emails — optional product hearts: When a follow-up email shows interested products as an image carousel, favorite heart icons can be turned on or off for that template. Hearts do not change product data; they only control whether the favorite indicator appears in the email. The packaged 90 Days Since Last Customer Visit template hides hearts for a cleaner look. Other templates keep hearts visible by default unless customized.
• Queue check-in: When Find AE By N Consecutive Assistance is 0 or -1, matching an existing customer on check-in no longer reassigns Primary Sales Associate based on consecutive store visits.
• Same day-to-day clienteling otherwise: Queues, journeys, Messaging Centre, and notifications behave as in Release 1.79 except where noted above.

What’s new for administrators and data stewards

Integration job write settings

Open Clienteling Setup → Integrations. When you create a job — or click the settings icon (Edit settings) on an existing job — use Job Settings (JSON) to control writes to the target system.

Leave Job Settings blank to use the defaults (both create and update allowed). Examples:

• Insert-only: {"allow_insert": true, "allow_update": false}
• Update-only: {"allow_insert": false, "allow_update": true}

These settings apply to jobs writing to Salesforce, Lightspeed, and Adaptive. Source and target object mappings stay fixed when you edit settings; you can still change Status and Job Settings without recreating the job.

When a write is skipped

• The run treats the row as a successful skip (not a hard failure). Job last-response / logs can show a message such as Insert disabled by job settings or Update disabled by job settings.
• Skipped updates still return the existing target identifier (Salesforce Id, Lightspeed customer Id, or Adaptive system Id and related Adaptive numbers when known). The job does not substitute a source-system external Id.
• Lightspeed customer sync: When insert is allowed but update is blocked, the middleware searches Lightspeed before creating a customer. If a match is found, the existing Lightspeed customer Id is written back to Salesforce instead of creating a duplicate.
• Related sync steps that depend on that target Id (for example orders or line items after a contact match) can still resolve against the existing target record.

The Salesforce package provides the Integrations UI. Enforcement during sync requires the matching WovenIQ middleware release.

Order activation and product interests

Two optional record-triggered automations ship inactive (Obsolete) so you can review before enabling:

To use this behaviour, activate one or both automations in Setup → Flows. Interests with Hide From Interest checked are excluded. If you prefer manual control, leave both inactive.

Find AE By N Consecutive Assistance

On Customer Queue Setting, Find AE By N Consecutive Assistance controls whether queue check-in can reassign Primary Sales Associate (Contact owner) when an existing customer is matched:

Keyword Search columns and filters

• Columns: Managed by the packaged Contact field set labelled WIQ Keyword Search. Add or remove Contact fields in that field set to change result columns; Owner displays as Primary Sales Associate.
• Primary SA filter: Optional dropdown on Keyword Search limits results to customers owned by the selected associate (All shows every match).
• Responsive toolbar: Search box, Primary SA filter, and actions reflow on tablet and phone widths.

Change Primary or Secondary Sales Associate

WIQ Admin users do not receive this permission automatically. Assign WovenIQ - Allow Owner Change explicitly, or run your org’s one-off assignment script for existing admins if applicable.

Store Concierge (Podium default owner)

Requires the matching middleware release for Podium job processing.

Optional product hearts in follow-up emails

Follow-up and journey emails that render Product Interest items as an image carousel can optionally show favorite heart icons on each product card.

How to customize a template

1. Open the email template that includes the product-interest carousel (Setup → Email Templates, or your Branding / journey customization template).
2. On the product-interests component that already has the image carousel enabled, add or change showHeart.
3. Save and send a test email to confirm hearts appear or are hidden as expected.

Notes

• This only affects the email carousel display. Clienteling favorite / unfavorite behaviour on the customer profile is unchanged.
• Base package 1.80 adds the optional attribute. To pick up the packaged 90 Days Since Last Customer Visit change (hearts hidden), install or upgrade the matching WovenIQ - Branding build that includes that template update; otherwise keep using your current Branding version and set showHeart on any custom templates yourself.
• Image URLs in the carousel continue to resolve through the packaged product image helper so relative and absolute product image paths render correctly in email.

Custom objects and fields referenced

New permission set: WovenIQ - Allow Owner Change.

Integration job allow_insert / allow_update settings are stored on the job in WovenIQ middleware, not as new packaged Salesforce fields.

Upgrading from 1.79 to 1.80

• Standard managed-package upgrade plus matching middleware deploy.
• Re-assign WIQ User and WIQ Admin after install.
• Assign WovenIQ - Allow Owner Change to users who may reassign Primary or Secondary Sales Associate from the customer profile.
• Set Store Concierge on Store records used with Podium, if applicable.
• Review Find AE By N Consecutive Assistance — use 0 or -1 if you want to stop automatic Primary Sales Associate changes on check-in.
• Activate order → Product Interest automations in Setup → Flows if you want ordered products reflected automatically.
• Review follow-up / Branding email templates that use the product-interest image carousel — set showHeart if you want hearts hidden (the packaged 90 Days Since Last Customer Visit template hides them when Branding is upgraded with that change).
• Existing integration jobs with empty Job Settings keep current behaviour (create and update both allowed).
• In sandbox: verify Keyword Search columns and Primary SA filter, test owner change with the new permission set, preview a follow-up email with hearts on and off, and run an insert-only or update-only integration job to confirm skipped writes still return target system Ids.

Upgrading from earlier releases

Orgs not yet on 1.79 should install 1.80 (cumulative) and also follow Release 1.79 (required First Name / Last Name), Release 1.78 (Exclude OBM cleanup), Release 1.77 (Notification Fallback, Normalised Phone, broader Exclude OBM usage), then earlier notes as needed.

Branding and Reports extensions

WovenIQ - Branding and WovenIQ - Reports builds pinned to 1.76 remain compatible for day-to-day use. Base 1.80 alone enables the optional showHeart attribute on product-interest email carousels. A new Branding build is only required if you want the packaged 90 Days Since Last Customer Visit template update (hearts hidden by default); otherwise leave Branding as-is and adjust custom templates as needed. Reports needs no change for this release unless your team publishes a new build against 1.80.

Support

If you have questions about this release or need help with configuration, contact your WovenIQ administrator or your WovenIQ support channel.