- 27 Feb 2024
- 4 Minutes to read
- Updated on 27 Feb 2024
- 4 Minutes to read
Custom Settings are used in Blackthorn apps for multiple use cases, such as turning Apex-based features on and off, custom handling around scheduled processes, tracking the status of your onboarding in the setup wizard, and many more.
Blackthorn Pay - Reattempt Settings
Out-of-the-box, Blackthorn Payments automatically creates and enables a Reattempt Schedule for your failed Transactions.
- Navigate to Custom Settings.
Lightning/Classic: Setup > In Quick Find, Search and Click: "Custom Settings."
- Click Manage on Blackthorn Pay - Reattempt Settings.
Allow on Non-Auto Processif you want to reattempt failed Transactions that don't have
If you don't want to reattempt Transactions unless they have the auto-process field checked, then skip this step.
Enter a number (of days) for each
If you enter "1" in each field, each attempt will occur that number of days after the previous attempt. By default, we have entered a "1" from the first to fourth reattempt (reattempting each day for four days).
To disable the Reattempt Logic, uncheck the Enabled field.
- Click Save.
Blackthorn Pay - Trigger Settings
There are many Apex-based validation rules, enabled by default. These Custom Settings serve to disable them.
To stop the trigger that summed the total Transactions related to an Account and populated the
Historical Account Value field from causing failures, a new Custom Setting was created. The failure occurred during Check and Money Order scans for Check 21 and Mobile Payments users when more than 50,000 Transactions were related to a single Account. The new
Disable Trans Rollup To Account custom setting in Blackthorn Pay – Trigger Settings will disable the trigger.
- Navigate to Custom Settings.
Lightning/Classic: Setup | In Quick Find, Search and Click: "Custom Settings."
- Click Manage next to Blackthorn Pay - Trigger Settings.
Example: Disable Transaction Account/Contact Lookup Setting
When you don't wish to define a Contact/Account on a Transaction, you can disable the related lookups from the Payment Method being populated on the Transaction using a Custom Setting.
To disable this, navigate to setup >Custom Settings >Blackthorn Pay - Trigger Settings > “Disable Transaction Related Lookups“. set to TRUE. This will turn off transaction account/contact based lookup settings.
This Custom Setting is set to TRUE in new orgs by default. Users will still see
TransactionRollupToParentService in the Apex Jobs list, but the logic will not fire. To ensure that Transaction rollups are being executed in your org be sure to uncheck this setting.
Blackthorn Pay - Transaction Parents
This Custom Setting correlates to the custom lookup field (Transaction parent) created on the Transaction object.
Add a New Transaction Parent
Adding additional Transaction parents happen in the Setup Wizard under the "Relationships" step.
We do not advise manipulating these records manually.
The most common Transaction parent is Opportunity, but it can be any object or multiple objects. When the object is selected, it creates a Custom Setting record here.
You can go back to the Setup Wizard at any time to add additional objects (Transaction parents).
Blackthorn Pay - Transaction Validations
This Custom Setting includes items that allow user to fine tune Transaction validation rules.
- TR Validate Status Transition - Blocks invalid manual updates of Transaction Status or Payment Status.
- TR Prevent Delete of Record with IDs - Blocks the deletion of Transactions if a Transaction ID is present.
- TR Currency Validation - Blocks Transactions from being saved if the Currency on Transaction and Currency on the associated Authorize.net Payment Gateway do not match.
Blackthorn Pay – Features
Authorize.net: Track and Reconcile Payments
Customers can now track and reconcile payments processed through Authorize.net via the new “Blackthorn Pay – Features” custom setting. The custom setting will be created during package upgrades and new installations and can only be accessed via the LMO.
Solution Id field will be populated with Blackthorn’s partner ID when Payments is installed/upgraded in production. A test value will be used in an Authorize.net sandbox. If a sandbox is created from production, the production value will be updated to the test value.
Solution Id is populated, it will be included any time Blackthorn sends data to Authorize.net. If the
Solution Id is not available, the data will be sent without the Transaction source information.
High-Volume Batch Processing
The introduction of high-volume batch processing resolves the issue of scalability with our batch processes. Previously, batch processes were limited to one record at a time to ensure that Payments was compliant with Salesforce's limits.
The new protected custom setting is located under the Blackthorn Pay – Features custom setting.
- Field Label: Auto-Change Batch Size
- API Name: Auto_Charge_Batch_Size__c
- Data Type: Number(3,0)
- Description: Controls the batch size of the scheduled job. The default setting is 1. Currently, the maximum supported value is 75.
If you have received an error with your Custom Settings or have a question, please view our Troubleshooting page.. If you still have Custom Setting questions, please contact Blackthorn Support. We're happy to help!