Changelog
- Craft 4.0 support
- Methods
flipbox\craft\salesforce\fields\Objects::pullFromSalesforceandflipbox\craft\salesforce\fields\Objects::pushToSalesforceare now publicly accessible.
- When syncing an object via the field type, checks were added to ensure a Case Safe Object Id is used.
- Error thrown when attempting to create a new element from a sync request.
- Disabled attachment/document downloads by default.
- Attachment download capabilities
- Document download capabilities
- Webhook processing capabilities (to trigger actions from external sources).
- Admin interactions with the Salesforce API can specific which connection to use
- Connections can be managed via the admin
- Criteria template variables to create criteria used to access date
craft.salesforce.criteria.query,craft.salesforce.criteria.object,craft.salesforce.criteria.search \flipbox\craft\salesforce\records\SOQL::fetch()to execute the SOQL query API call.
- Widget would not create a new element if one was not found.
- Sync jobs can accept an objectId rather than trying to resolve one.
- Checking if field is associated to element prior to syncing as it causes unexpected errors.
- Supporting new dependencies
- Namespacing
- Element Populate transformer can accept a key
- Log viewer in admin panel for debugging purposes
- Docs link
- Connection management via CP
- TransformerHelper inherits the Flux TransformerHelper which assist in resolving a transformer from Yii config
- Moved redundant integration classes into separate package.
- Issue where objects were not getting associated on new element creation
- Patron OAuth2 icon
- Corrected widget class name
- Major refactoring
- 'sobject', 'SObject', 'sObject' references are not 'object' and 'Object'
- Salesforce package dependency
- Altered/Removed transformers
- SObject field entries will return more than the limit, even if it exceeds the max
- A SObject ID is validated prior to performing an association
- Updated dependencies
- Logging will now occur in a separate force.log file
- View Url property to the SObject field which supports direct linking to Salesforce Object
- List Url property to the SObject field which supports direct linking to Salesforce Object List
- The default connection and cache strategy can be set via settings
- The following plugins settings: instanceUrl, sObjectViewUrlString, sObjectListUrlString,
- SObject fields was returning the first entry for new elements
- SObject field Push Object to Salesforce action only appears on existing entries
- CP notifications were not being displayed after field actions occurred
- Instance where an environment
- Sync actions and transformations
- Class type casing issues
- Issue where a correct cache instance would throw an exception
- SObject field type supports min and max values
Initial release.