Pitcher Consent 1.67 version is released!
Hey there 👋
NEW We’re pleased to announce that the following features and enhancements are now available with the new Consent 1.67 version.
Consent Topic Lines
Two new objects, Consent Topic Lines & Consent Management, have been introduced in this release to support the changes announced as part of the Consent 2.1 Frontend release in February.
This new release will enable the development of bespoke Consent subtopics to establish dynamic extra channels or groups of areas of interest inside each Consent subject.
Pitcher Consent Management Settings
The following new settings are now available to support the frontend configuration:
- Disable Account Selection: Disable the collection of consent for Business Accounts.
- Disable Consent outside engagement: Disable F2F consent submissions outside a call.
Dynamic Custom Fields Setting
Users can use the custom metadata option in the upcoming frontend form to dynamically enable and read custom fields for each Consent.
We will release more information about this option as part of the upcoming Consent 2.1 Frontend release.
Topic Email Text
A new field, Topic Email Text, has been introduced inside the Consent Topic object to customize Email notifications dynamically inside each Consent Topic.
Note: These changes are disabled by default; if you want to enable them, please contact your Pitcher representative.
BUG FIXES
A fix has been implemented inside the logic of remote consent to prevent problems updating an existing Consent when remote Consent is obtained for the same account but a different contact.
This issue does not affect customers using Person Accounts and only affects customers with standard account & contacts logic.