Install in Salesforce
Base package 1.70.0 — subscriber package ID 04tal000007CWzNAAW. Use your usual install process or:
Typical predecessor: 1.69.0 (04tal000007CVwrAAG).
Highlights
- Journey enrollment backfill alignment: One-time enrollment backfill and visit context now use the customer queue Created Date for Last Visit Date, matching how journey notification timing is calculated in production.
- Preference ownership control: New Customer Profile Setting lets administrators route new Product Interest records to the contact owner (primary SA) instead of the creating user.
- Notification Preferences UI: Cleaner layout and background styling on the Notification Preferences tab for store associates.
- Customer Journey reporting: Reports 1.7 adds journey reports and a custom report type for enrollments and notification send history.
- Packaging reliability: Permission sets aligned for managed-package rules so Customer Journey access continues through Contact sharing.
What’s new for everyone
- Clearer notification preferences: Store associates see an improved Notification Preferences screen when toggling customer-in-queue bell notifications per store.
- Consistent journey visit dates: Customer Journey enrollments created or refreshed from queue history use the same visit date basis as scheduled journey emails and SMS.
- Optional primary-SA preferences: When enabled by your administrator, new customer preferences on the profile are attributed to the contact’s primary store associate (owner) rather than whoever entered them.
What’s new for administrators and data stewards
Customer Profile Setting
- Customer Profile Setting → Assign Preferences To Primary SA — When checked, new Product Interest rows on a Contact default Store Associate to the contact owner (primary SA). Default is off; enable when your org wants preference ownership centralized on the primary associate.
Customer Journey enrollment and backfill
- Last Visit Date on Customer Journey is set from the linked Customer Queue → Created Date (not check-in date) when enrollment context is applied or when the one-time enrollment backfill runs.
- Re-run enrollment backfill only after validating a sample in sandbox if you previously backfilled on 1.68 / 1.69 and need rows refreshed — most orgs upgrading from 1.69 do not need a second backfill.
Permission sets (WIQ User)
- Customer Journey, Journey Email Customization, and Journey Notification Log remain accessible through Contact (master-detail sharing). They are not granted as standalone object permissions in WIQ User because Customer Journey is a child of Contact.
- After upgrading to 1.70, re-assign WIQ User and WIQ Admin so all other journey, messaging, and tab permissions apply.
WovenIQ - Reports extension (1.7)
Install WovenIQ - Reports@1.7.0-1 (04tal000007CWsvAAG) after base 1.70:
- Report type: Customer Journeys with Notification Logs
- Reports: Customer Journeys with Notification Logs; Journeys with Stores; Journeys with Notifications
WovenIQ - Branding
If you use journey email templates, upgrade Branding to the latest build compiled against 1.70 so queue date merge fields stay aligned with Created Date on Customer Queue.
Upgrading from 1.69 to 1.70
- Standard managed-package upgrade; no scheduler or journey reconfiguration required.
- Review Assign Preferences To Primary SA before enabling in production.
- Install Reports 1.7 when journey reporting is needed.
Support
If you have questions about this release or need help with configuration, contact your WovenIQ administrator or your WovenIQ support channel.