The Payment Schedule object allows you to create a variety of forward-looking, scheduled (recurring) Transactions. The Payment Method object stores the methods by which you charge your customers. The Payment Gateway Customer object connects your Salesforce customers ( Accounts and/or Contact s) with your Customer accounts in Stripe. The Payment Gateway object connects your Stripe account to Salesforce. A Stripe Line Item Record Type is used to create Invoice Items for an Invoice in Stripe Billing. Line Items store price and quantity information for items related to an Invoice. The Dispute object receives disputes and allows you to submit evidence and upload files in defense. This Metadata Type automatically installs metadata records into your org. The Company Info object houses information regarding your company or companies. Blackthorn Logsīlackthorn Log records store application errors captured in our code as well as some batch job information. For example, when a payment is made for four Invoices using the same Transaction, Allocations help to split the funds across those four Invoices. The Allocation object allows you to allocate funds to multiple Line Items on the same Invoice from a single Transaction. Note: You can always change settings related to the configurations from the Egnyte Sync Configurations tab in your production organization.These custom objects are the bread and butter of Blackthorn Payments. After specifying the triggers and test classes for custom objects, select Continue then Process to generate the Sync configurations for the selected custom objects. You need to enter the name of the apex triggers and test classes that were deployed from the sandbox environment. Select the same custom objects you specified in step 1, but this time choose No for the Auto-generate Trigger setting.Open the Egnyte Sync Configuration tab in your production organization and click New to create a new Sync Configuration record.You can check the deployment status of your changeset.Ĭreate Egnyte Sync Configurations for the custom objects in your production organization Note: If the validation does not succeed due to custom validations in your organization, you will need to manually change the generated triggers and test classes to pass your custom validations before repeating this step.Īfter validation, click Deploy to make the components available in your production organization. Select the changeset that was uploaded from the Sandbox organization and click Validate to check if there are any errors in deployment. Search for Inbound changesets in the setup section in your production organization. These steps should be performed by your production organization. Select the production organization where you want to deploy the triggers and test classes and click Upload again.ĭeploy Inbound Change Set in your production organization.After adding all the components, select the Upload option.After creating the changeset, click on Add in the Change Set Components section to add the apex trigger and test class components that were created as part of step 1.Enter a name and description and click Save. Click New to create an Outbound changeset.Search for Outbound Change Sets in the setup section of your sandbox organization.Click Continue then Process to create the triggers and test classes for the custom objects.Ĭreate an Outbound Change Set in your sandbox organization.Add the selected custom objects and set the Auto-generate Trigger option to Yes.Open the Egnyte Sync Configuration tab in your sandbox organization and click on New to create a new Sync Configuration record.You will only install the package to automatically create the required triggers and test classes. Note: You don't need to connect your Egnyte domain to the package or run through any of the post installation steps described in the Installation guide. Install the Egnyte for Salesforce package in a sandbox environment.If this is the case, the following guide can be used to deploy the custom object sync Egnyte Sync Configurations to enable the integration of custom objects.Ĭreate Egnyte Sync Configurations for custom objects in a sandbox organization Create an Outbound Change Set in your sandbox organization Upload the Outbound Change Set Deploy Inbound Change Set in your production organization Create Egnyte Sync Configurations for the custom objects in your production organizationĬreate Egnyte Sync Configurations for custom objects in a sandbox organization The Egnyte for Salesforce package can automatically create these configurations for you, however, it is not possible to directly create Apex triggers or test classes in some production organizations. Enabling the Salesforce Integration for custom objects involves creating Egnyte Sync Configurations for those custom objects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |