Install in Salesforce
Base package 1.74.0 — subscriber package ID 04tal000007ChA1AAK. Use your usual install process or:
Typical predecessor: 1.72.0 (04tal000007CdPlAAK).
Highlights
- Email templates that work across packages: Shared email building blocks (product interest lists, tags, associate contact email, and branded header/footer) can now receive their required inputs when templates live in the Branding extension or other org-level (unmanaged) email content.
- Branding 1.11 companion release: Email header and footer branding pieces are updated to the same packaging rules so branded journey and follow-up emails render correctly with 1.74.
- No change to day-to-day clienteling screens: Store associates continue to use queues, journeys, messaging, and the customer profile as in 1.72.
What’s new for everyone
- More reliable branded emails: Journey and follow-up emails that show product interests, favourites, tags, or store branding are less likely to fail or render incompletely when the email template comes from the Branding package or a subscriber customization.
- Same associate experience: Check-in, Customize Email Content, Messaging Centre, and customer profile behaviour are unchanged from Release 1.72.
- Same journey timing: Scheduled email and SMS send rules are unchanged; this release focuses on how email HTML assembly resolves packaged content.
What’s new for administrators and data stewards
Packaging compatibility for branded and custom email templates
Managed (base) and unlocked (Branding) email content must pass values such as Contact, Store, and related identifiers into shared Visualforce email building blocks. In 1.74 / Branding 1.11, those inputs are exposed for use from templates outside the managed package so subscriber and Branding templates can call them safely.
What this affects operationally
| Area | What to expect |
|---|---|
| Journey / follow-up email templates that embed product interests or tags | Should resolve contact-scoped content when sent from Branding or org-custom templates |
| Branded email header (logo / cover) and email footer (store social links, unsubscribe context) | Should accept Store and related-to context from Branding templates |
| Task / associate contact email merge blocks used in templates | Should accept contact context from outside the managed package |
After base 1.74, install WovenIQ - Branding 1.11 (04tal000007ChBdAAK) when you use packaged email templates.
Custom objects and fields referenced (unchanged)
No new objects or fields are introduced. Templates continue to rely on existing data such as:
- Contact — customer context for interest and tag merge content
- Product Interest — listed or carousel product preferences in email body
- Store — logo, cover image, and social links used by branded header/footer
- Customer Queue / Customer Journey — existing journey send and merge context (unchanged from prior releases)
Upgrading from 1.72 to 1.74
- Standard managed-package upgrade for WovenIQ 1.74, then install WovenIQ - Branding 1.11.
- No data migration, scheduler changes, or journey reconfiguration.
- Re-assign WIQ User and WIQ Admin after the base install.
- In sandbox, send a sample journey or follow-up email that includes product interests and store branding and confirm the HTML preview and delivered message look complete.
Upgrading from earlier releases
- Orgs not yet on 1.72 should upgrade through the latest patch and follow Release 1.72, Release 1.71, Release 1.70, and (for journey cutover from 1.67) Release 1.68.
- Pair Branding 1.11 with base 1.74 (or later). Older Branding builds that depended on pre-1.74 packaging rules should be replaced after the base upgrade.
Reports extension
WovenIQ - Reports builds pinned to 1.74 remain compatible; no Reports change is required for this release unless your team publishes a new Reports build against 1.74.
Support
If you have questions about this release or need help with configuration, contact your WovenIQ administrator or your WovenIQ support channel.