Install in Salesforce
Base package 1.78.0 — subscriber package ID 04tal000007D9sfAAC. Use your usual install process or:
Typical predecessor: 1.77.0 (04tal000007D54HAAS).
Highlights
- Safer Exclude OBM cleanup: After an excluded Contact update, clearing Exclude OBM no longer re-triggers the customer outbound message path — so transactional updates stay quiet end-to-end.
What’s new for everyone
- Same day-to-day clienteling: Queues, journeys, Messaging Centre, and the customer profile are unchanged from Release 1.77.
- Fewer accidental sync events: Internal Contact maintenance that correctly sets Exclude OBM is less likely to send a follow-on outbound sync when that flag is cleared afterward.
What’s new for administrators and data stewards
Customer outbound message — Exclude OBM entry criteria
In 1.77, more internal Contact updates set Exclude OBM so WIQ - Customer OBM skips the outbound message, then clears the flag. In some cases the clear itself could re-enter the after-save path and still send an outbound message.
1.78 tightens when that path runs so that:
| Contact save | Behaviour |
|---|---|
| Normal create/update where Exclude OBM is unchanged | Outbound message path runs as before (when the flag is not set) |
| Update with Exclude OBM = true | Outbound message is skipped; the flag is cleared afterward |
| Save that only clears Exclude OBM (true → false) | Does not re-run the outbound message |
No admin configuration change is required. Orgs already using Exclude OBM for transactional Contact updates get the safer behaviour automatically after upgrade.
Custom objects and fields referenced
- Contact → Exclude OBM — Suppresses the customer outbound message for a given save, then is cleared by the OBM handling path
No new objects or fields are introduced in 1.78.
Upgrading from 1.77 to 1.78
- Standard managed-package upgrade; no data migration or scheduler changes.
- Re-assign WIQ User and WIQ Admin after install.
- In sandbox, confirm a transactional Contact update that sets Exclude OBM does not produce an outbound sync when the flag is cleared (for example OTP or preference-maintenance style updates).
Upgrading from earlier releases
Orgs not yet on 1.77 should install 1.78 (cumulative) and also follow Release 1.77 (Notification Fallback, Normalised Phone, broader Exclude OBM usage), then Release 1.76 and earlier notes as needed.
Branding and Reports extensions
WovenIQ - Branding and WovenIQ - Reports builds pinned to 1.76 remain compatible; no extension change is required for this release unless your team publishes a new build against 1.78.
Support
If you have questions about this release or need help with configuration, contact your WovenIQ administrator or your WovenIQ support channel.