What is an Integration Rule?
| This topic relates to the first generation of Integration Rules. Contact your FinancialForce representative for information about the suitability and availability of the next generation of integration rules (ClickLink). |
You can use integration rules to expose data fields or map fields between objects in your organization
A deployment of the Salesforce/FinancialForce applications with a defined set of licensed users. Your organization (org) includes all of your data and applications, and is separate from all other orgs..
There are two types of integration rule:
- Type 1: Designed to expose custom fields. They only have target objects defined. See Integration Rules - Type 1 for more information.
- Type 2: Designed to map fields between different objects. They have both source and target objects defined. See Integration Rules - Type 2 for more information.
The following table summarizes the types of integration rule that you can create:
| Type | Function | Source Object | Target Object | Description |
|---|---|---|---|---|
| 1 | Expose custom fields on target object | None | Sales Invoice (Master/Detail) | Make your own custom fields available on the sales invoice page and expose them to the FinancialForce API and desktop apps. Make any sales invoice fields available for printing. |
| Sales Credit Note (Master/Detail) | Make your own custom fields available on the sales credit note page and expose them to the FinancialForce API and desktop apps |
|||
| Payable Invoice (Master/Detail) | Make your own custom fields available on the payable invoice page and expose them to the FinancialForce API. | |||
| Payable Credit Note (Master/Detail) | Make your own custom fields available on the payable credit note page and expose them to the FinancialForce API. | |||
| Journal (Master/Detail) | Make your own custom fields available on the journal page and expose them to the FinancialForce API and desktop apps |
|||
| Budget and Balance | Expose your custom fields, such as extra periods, to the FinancialForce API and desktop apps |
|||
| 2a | Map fields between source and target objects | Opportunity (Master) Opportunity Product (Detail) |
Sales Invoice (Master/Detail) | Customize the standard behavior for the creation of a sales invoice from the information stored on an opportunity. |
| Sales Credit Note (Master/Detail) | Customize the standard behavior for creation of sales credit notes by converting sales invoices which were created using the information stored on opportunities. | |||
| 2b | Map fields between source and target objects | Any object or pair of master-detail objects | Sales Invoice (Master/Detail) | Map the fields and create a custom button on any object so that it can be used to create sales invoices. |
| Sales Credit Note (Master/Detail) | Map the fields and create a custom button on any object so that it can be used to create sales credit notes. | |||
| 2c | Map fields between source and target objects | Any pair of master-detail objects | Sales Invoice (Master-Detail) |
Set up automated generation of sales invoices using the Run Integration Rule page. |
|
Any single object |
Cash Entry (Master/Detail) |
Set up automated generation of cash entries using the Run Integration Rule page. |
The Integration Rule object is an organization-level object
Custom object that exists across all companies in an organization (org)..