Install in Salesforce
Base package 1.72.0 — subscriber package ID 04tal000007CdPlAAK. Use your usual install process or:
Typical predecessor: 1.71.0 (04tal000007CXIjAAO).
Highlights
- Cleaner Customize Email Content: The customer-profile Customize Email Content screen no longer lists stale journey notifications for contacts upgraded from pre-journey releases.
- Smarter visibility rules: Only actionable or recoverable journey email and SMS rows appear — sent and skipped notifications are removed from the list; failed sends remain visible for follow-up.
What’s new for everyone
- Less noise after journey upgrade: Store associates opening Customize Email Content on upgraded customers no longer see day-1, day-21, and similar notifications that would have been due before the customer’s Customer Journey enrollment existed.
- Only relevant upcoming work: The modal focuses on notifications tied to the current visit cycle — future send dates and past-due items that may still need attention after enrollment.
- Skipped notifications stay out of the way: If the journey batch already marked a notification as skipped (for example due to customer preference or missing contact details), that row no longer appears for customization.
- Failed sends still visible: When a journey notification failed to send, the row remains on the list so associates can review or customize content before retry.
What’s new for administrators and data stewards
Customize Email Content — journey notification visibility
The list of journey email and SMS rows on Customize Email Content is now filtered as follows:
| Condition | Shown in modal? |
|---|---|
| Send date is before the Customer Journey record was created (legacy pre-enrollment period) | No |
| Journey Notification Log → Status = Sent | No |
| Journey Notification Log → Status = Skipped | No |
| Journey Notification Log → Status = Failed | Yes (recovery) |
| Send date is in the past but after enrollment was created, and no sent/skipped log exists | Yes (recovery) |
| Send date is today or in the future | Yes |
Why this matters for upgraded orgs: After journey cutover and enrollment backfill, Customer Journey → Last Visit Date may reflect an older store visit. Without this fix, early journey notifications could appear in Customize Email Content even though they were never sent through the journey system and have no Journey Notification Log row. 1.72 uses the enrollment Created Date on Customer Journey to distinguish that legacy window from notifications that still merit associate attention.
Customer Journey fields referenced
- Customer Journey → Created Date — used to determine whether a notification’s calculated send date predates the enrollment (hidden when it does).
- Customer Journey → Last Visit Date — unchanged; still drives send-date calculation for the current visit cycle.
- Journey Notification Log → Status — Sent and Skipped suppress the row; Failed does not.
Journey groups with no visible rows
If every notification for a journey is filtered out, that journey section is omitted from Customize Email Content rather than showing an empty group.
Upgrading from 1.71 to 1.72
- Standard managed-package upgrade; no data migration, scheduler, or backfill changes.
- Re-assign WIQ User and WIQ Admin after install.
- Validate Customize Email Content on a sample of upgraded contacts in sandbox — you should see fewer legacy rows and no skipped/sent duplicates.
Upgrading from earlier releases
Orgs not yet on 1.71 should upgrade through the latest patch and follow Release 1.71, Release 1.70, and (for journey cutover from 1.67) Release 1.68.
Support
If you have questions about this release or need help with configuration, contact your WovenIQ administrator or your WovenIQ support channel.