A contract allows you to work with items from multiple apps in a single interface. You can create, view, and edit items on the contract page, as well as configure shared business processes that handle records from different apps. This approach enables custom Low-code solutions to follow the inheritance principle used in object-oriented programming.
Apps added to a contract are called sources. You can add any number of source apps, including apps from different company workspaces. A contract and its sources are linked through fields, so both the contract and each source app must include fields of the same data type.
For example, create a Customer Documents contract and add the Contracts and Invoices apps as sources. These apps contain fields that store customer information, transaction amounts, and other data. Map these fields to the corresponding contract fields to transfer the data.
After you configure a workspace-associated business process that contains the contract, you can start process instances for items from any of the source apps.

Features of a contract
- A contract is created and used the same way as other apps. You can configure access permissions to a contract and its items.
- You can add an unlimited number of source apps to a contract. They can be included in different workspaces and solutions.
- Items of a contract are items of source apps. They will be displayed on the contract’s page. On it, you can view source app item pages, as well as search by parameters, and save custom filters for searches.
- When you create an item in a source app, the new entry is automatically displayed in the contract. You can also create an item from the contract page by selecting one of the source apps added to the contract.
- Source app forms are used in the contract. You can only customize them by going to the corresponding source app.
- You cannot create a business process associated with a contract. If you want to use a contract in a process, it is recommended to associate such processes with the workspace the contract is created in.
- You can add a button that starts a business process to the form of each source app and to the contract’s page.
- In a business process that includes a contract, the default app specified in the contract’s settings is used for the Manage Status and Create App Item activities. You can only change the status and create items within a process in this source.
- It is recommended to export contracts as part of a workspace or a solution.
- You can export contract data as an .xlsx or .csv file. It is similar to exporting app data.
Read more about working with contracts in the following articles:
- Create a contract.
- Contract settings.
- Add a source app.
- Configure contract fields.
- Business processes involving contract items.
- Contract page.
Found a typo? Select it and press Ctrl+Enter to send us feedback