Low-code designer / Contract


Contracts implement the principles of object-oriented programming on our low-code platform. You can create a Contract and add several apps from different workspaces into it. These apps will become the contract’s sources. You will be able to work with their app items right on a contract’s page. In other words, contracts allow you to work with apps from different solutions and workspaces in a single interface.

Consider the following example. You can create a contract and name it Employee documentation, then add the Resumes and Employment agreements from different workspaces as its sources. App items of both apps will be displayed in one list on the contract’s page. When you click an app item, you will see the view form set up for the corresponding source app. You can view all the item’s data, edit fields, add buttons to the form, etc. Changes you make will be saved in the original app item, and you will be able to see them in the source app.

If you use a contract in a business process associated with a workspace, you will be able to run process instances with app items from different source apps.


Important features that contracts have:

  • A contract is created and used the same way as other apps. You can configure access permissions to a contract and its items.
  • Items of a contract are items of source apps linked to it. They will be displayed on the contract’s page. New entries are created in the contract as new app items are added to its source apps.
  • On a contract’s page, you can view all items of its source apps. You can also search by parameters and save custom search filers.
  • You can add an unlimited number of source apps to a contract. They can be included in different workspaces and solutions.
  • A contract doesn’t have its own view form. Its view forms are the view forms of its source apps, so you can only configure forms in source apps.
  • 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. In a business process, you can only change app item statuses or create new app items in the source app specified as default.
  • It is recommended to export Contracts as part of a workspace or a solution.

Read more about working with contracts in the following articles:

Found a typo? Highlight the text, press ctrl + enter and notify us