Schemas
Last updated
Was this helpful?
Last updated
Was this helpful?
A schema is the collection which contains everything about your use-case. The schema will contain information about the selected database, module, user groups and the configuration of the structure of the write-back table. Whenever you create a new schema you have to choose one of our modules first. Depending on the selected module the setup of your schema will be different.
To create a schema:
Go to the Schemas section in the Management Console
Click Create New Schema
Follow the steps in the guided wizard:
Choose a module
Select a database connection
Define whether you're using a new or existing table
Add the fields to your schema
When adding fields to your schema form, you can choose from the following input types:
Single Line Text – For short entries like names or codes
Paragraph Text – For longer free-text comments
Number – For numerical values
Boolean (Yes/No) – For binary selections
Dropdown Select – For predefined options
Date/Datetime – For selecting dates or timestamps
Each module has its own purpose. Here's how to choose the right one for your use case:
For a data correction schema it is possible to connect to a database table that already exists in your database. The only requirement is that the table has ONE primary key. (Compound keys are not allowed)
To create a schema from an existing table follow these steps:
Create new schema
Select Data correction
module
Select Use existing schema
Select the connection which connects to the database where the table is located
A list of all tables will be presented, Select your table. (when the list is to large, just use Ctrl+F to actiate the search function in your browser)
The new schema wizard will show with all detected columns matched to the field types that WriteBackExtreme uses.
For best compatibility make sure the ID column of the table is a UUID column for example CHAR(36). An example statement for a table could look like:
create or replace MY_TABLE( ID CHAR(36) NOT NULL, COLUMN_1 VARCHAR(16777216), constraint MY_TABLE_ID primary key (ID) );