Skip to main content

Object Data Dictionary v1.9

Version 1.9 adds the Send Thnks Apex Action, a new way to send Thnks directly from a Salesforce Flow (see below), alongside reliability fixes for the Thnks Request/Approval workflows introduced in v1.8. No fields were added, removed, or changed on either object in this release.

Thnks Object Data Dictionary

Below is a table with the default labels, API names and definitions for all fields that come with the AppExchange listing within the Thnks object. Object Label: Thnks Object API Name: thnksdev1__Gift__c
Send Thnks Apex Action in Flows (new in v1.9): Sends made through the Apex action do still result in a record on this object, created asynchronously through the same organic sync that captures web, mobile, and extension activity, rather than written directly by the Apex action itself. Once created, it uses the same fields and Contact/Lead/Opportunity matching logic as any other send path. The Apex action’s own inputs (Gift Id, Sender Email, Recipient Email, etc.) are configured in Flow Builder and are separate from this object’s fields, see the note under the Thnks Request Object table below.

Thnks Request Object Data Dictionary

New in v1.8, the Thnks Request object enables workflow automation and approval processes for Thnks sending. Object Label: Thnks Request Object API Name: Thnks__Request__c
Send Thnks Apex Action in Flows (new in v1.9): The Send Thnks Apex Action does not use the Thnks Request object at all, it does not create, read, or update any records here. Its inputs (Gift Id, Sender Email, Recipient Email, Recipient First/Last Name, Recipient Message, Include Carbon Neutral Cost, UTM Campaign Id, Source Record Id) are configured directly in Flow Builder as action parameters, not Salesforce fields, so none of them appear in this table even though some share a name with a field above (e.g. Gift Id, Include Carbon Neutral Cost). See the Install Guide for the full Apex Action input reference.

Field Usage Notes

Status Field Values:
  • Pending: Request created but not yet processed
  • Approved: Request approved and ready for sending
  • Rejected: Request rejected by approver
  • Sent: Thnks successfully sent and Thnks record created
Auto-Approved Field:
  • When checked, requests bypass manual approval process
  • Controlled by “Default New Requests to Auto-Approve” setting in Manage Thnks Settings
  • Can be manually unchecked on individual records if approval is needed
Gift ID Fields:
  • Multiple gift ID fields support different gift catalog structures
  • Root Gift Id provides categorization
  • Third Party fields enable vendor-specific gift fulfillment