If you work with a large amount of data then a dedicated database integration is the best way to push the data into BRYTER. The workflow is similar to using Excel tables but offers much more security and scalability and therefore allows you to realize the full potential of automating your workflows.
Example use cases
Store all relevant customer information
When building a customer data collection module, where your customer can enter all relevant information for a legal case including uploaded documents, all this information can be stored into a database, which could then be displayed or used in a CRM solution.
Access requirements for real estate contracts
In the area of real estate, there are a lot of rules and requirements for the landlord based on certain parameters like the size and age of the building. A database can be used to show for example maintenance intervals of specific technical devices based on the age of the building.
Every database is different, so therefore the fields used for the inputs and outputs will always vary. However, the concepts of reading and writing data from a database are similar.
[ 1 ] SESSIONID
This is the key that will trigger the query. Based on the key, the database will know exactly which data it should provide via looking up the database row that the key is on. A key could be also the customer id or any other unique identifier for example.
[ 2 ] DATATYPE and NAME
The data type is the technical format to be applied to the information from the database. It is similar to Input Nodes and the read values can be represented as text, numbers, or email addresses. The name is displaying the reference when the data will be referenced in another Node, Action, or Result. When you want to look up the data, you need to type in the name of the reference, which in this case are "criteria1", "criteria2", and "criteria3".
Implementing a database
Because each database is unique, BRYTER cannot provide an out-of-the-box solution. However, your database can be easily connected with BRYTER via an integration. If you have a use case that requires a database connection, we recommended prototyping it via an Excel integration and before working with us to build the database connection. Excel integrations can be set up within a few days and you can test your module using this first before integrating a solid database. Please contact your Customer Success Manager for further information.
Keywords: database; databse; Datenbank