Install in Salesforce
Base package 1.76.0 — subscriber package ID 04tal000007CqlBAAS. Use your usual install process or:
Typical predecessor: 1.74.0 (04tal000007ChA1AAK).
Highlights
- Smarter message notifications: When message bells are routed to primary and secondary store associates, inactive users are no longer notified—and when no active associate remains, no bell is sent at all.
- Clearer preference ownership guidance: Help text for Assign Preferences To Primary SA now states that the setting applies to upcoming preferences only.
- Cleaner journey data entry (1.76): Customer Journey and Journey Email Customization layouts now surface and require the Unique Id so records stay consistent, with Unique Id also shown in the Customer Journey highlights panel.
What’s new for everyone
- Fewer failed or wasted message alerts: If your org routes new-message notifications to the customer’s primary and secondary store associates, associates whose Salesforce user is inactive no longer receive those bells, and no empty notification is raised when every associate is inactive.
- More consistent journey records: When associates or administrators work with Customer Journey and Journey Email Customization records, the Unique Id is now visible and required, and the Journey Notification link is required on customization records.
- Same day-to-day clienteling: Queues, journeys, Messaging Centre, Customize Email Content, and the customer profile continue to work as in Release 1.74.
What’s new for administrators and data stewards
Message notifications — skip inactive associates
When Email Notification Setting → Message Notification To SA is checked, new-message bells go to the customer’s primary and secondary store associates instead of the store public group. Recipients are now resolved as follows:
| Recipient | Notified when… |
|---|---|
| Contact owner (primary SA) | Owner is set and the user’s Salesforce account is active |
| Contact → Secondary Associate | Secondary associate is set and that user’s Salesforce account is active |
| Inactive primary or secondary SA | Not notified |
| Both associates inactive or unset | No message bell is sent. Store-group routing is unchanged when Message Notification To SA is off. |
- Inactive owners and secondary associates are filtered out of the resolved recipient list.
- The message-received notification is sent only when at least one active recipient remains, preventing an empty or failed notification when all associates are inactive.
Why this matters: Inactive users can no longer be targeted for messaging bells, reducing failed notification delivery and avoiding alerts to users who have left the brand or been deactivated.
Customer Profile Setting — help text clarification
Customer Profile Setting → Assign Preferences To Primary SA now explains that the setting applies only to upcoming preferences assigned to the Primary SA (Contact owner). Behaviour is unchanged from 1.71: when enabled, new Product Interest rows default Store Associate to the contact owner.
Customer Journey and Journey Email Customization layouts (1.76)
- Customer Journey — the Unique Id field is now on the page layout as required and is included in the record highlights panel so it is visible at a glance.
- Journey Email Customization — Journey Notification and Unique Id are now required on the layout to keep customization records correctly linked to their journey and notification.
Custom objects and fields referenced
- Contact — Owner (primary SA) and Secondary Associate for message-bell recipients; owner for preference attribution when the setting below is on
- Product Interest — Store Associate ownership for new preferences (unchanged behaviour)
- Customer Journey — Unique Id surfaced and required on the layout and highlights panel
- Journey Email Customization — Journey Notification and Unique Id required on the layout
- Email Notification Setting → Message Notification To SA — Controls SA versus store-group routing for new-message bells
- Customer Profile Setting → Assign Preferences To Primary SA — Routes upcoming preferences to the primary SA
No new objects or fields are introduced in 1.76.
Upgrading from 1.74 to 1.76
- Use the standard managed-package upgrade; no data migration, scheduler, or backfill changes are required.
- Re-assign WIQ User and WIQ Admin after install.
- In sandbox, if Message Notification To SA is enabled, test an inbound message for a contact whose primary or secondary associate is inactive. Confirm that user does not receive the bell and that no notification is sent when every associate is inactive.
- Confirm Unique Id is populated on existing Customer Journey and Journey Email Customization records before rollout, since these fields are now required on the layouts.
Upgrading from earlier releases
Orgs not yet on 1.74 should upgrade through the latest patch and follow Release 1.74, Release 1.72, Release 1.71, Release 1.70, and (for journey cutover from 1.67) Release 1.68.
Branding and Reports extensions
WovenIQ - Branding and WovenIQ - Reports builds pinned to 1.74 remain compatible. No extension change is required unless your team publishes a new build against 1.76.
Support
If you have questions about this release or need help with configuration, contact your WovenIQ administrator or your WovenIQ support channel.