guide introduction
status
status select

Determines the project’s overall activation state. When active is selected, the project becomes available to user operations and automatic-run eligibility checks; when passive is selected, automatic data preparation does not start even if the schedule is valid. An automatic run additionally requires the life cycle to be “working” and automatic data update to be “yes”.

* Parameter relationships
Parameter: project_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Excludes the project from automatic-run eligibility checks.
1 — active
Makes the project runnable when the other automatic-run conditions are also satisfied.
Example: 1 —active
project_config['status'] = '1'
Parameter ID: 0
name
name text

Provides the human-readable name used to distinguish the project in lists, the record screen, and process tracking. A descriptive and unique name prevents projects that use the same data source from being confused; an ambiguous name makes operations and error tracking harder.

* Parameter relationships
Parameter: project_config['name']
Condition: No other parameter option is a prerequisite.
Reason and result: “name” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example: Hospital Patient Risk Analysis
project_config['name'] = 'Hospital Patient Risk Analysis'
Parameter ID: 1
data preparation mode
data preparation mode select

Determines the source and preparation flow used to build the dataset. Manuel mode expects data to be uploaded or edited by the user. Wtransfer uses the selected database map and main rule. Wisdombase uses platform layer data; MSSQL executes the connections and queries in the SQL list. Changing this selection also changes which dependent parameters are required.

* Parameter relationships
Parameter: project_config['data_preparation_mode']
Condition: No other parameter option is a prerequisite.
Reason and result: This controller has no prerequisite. '0' — “manual” enables file/user flows; '1' — “Wtransfer” enables map and layer fields; '2' — “Wisdombase” uses a layer source; and '3' — “MSSQL” enables the SQL connection list. Only child fields for the selected source are shown and evaluated.
Options and usage purposes
0 — manuel
Used for file upload and user-controlled data preparation.
1 — wtransfer
Prepares data from related layers through a database map.
2 — wisdombase
Uses Wisdombase layer records as the data source.
3 — mssql
Prepares data with the defined Microsoft SQL Server connections and queries.
Example: 1 — wtransfer
project_config['data_preparation_mode'] = '1'
Parameter ID: 2
product code
product code text

This is the text stored as the "product code" within a project record. The project screen displays this value in a read-only format; the WisdomEra product management code compares this value against the codes in the product list to identify the corresponding pre-configured product project. It is a specific product code assigned to products created by WisdomEra. It is used in scenarios where matching is required during product installations or when it is necessary to verify the existence of a product. For instance, if a product is installed with the product code "123," another instance of the same product can be installed using that same code. This mechanism establishes the relationship between WisdomEra’s pre-configured products and the products actually installed.

* Parameter relationships
Parameter: project_config['product_code']
Condition: No other parameter option is a prerequisite.
Reason and result: “product code” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example: 123
project_config['product_code'] = '123'
Parameter ID: 3
life cycle
life cycle select

Identifies the project’s design and operational stage. Automatic data preparation can become eligible only when “testing” or “working” is selected; no automatic process starts for planning, designing, maintenance initiated, or cancelled. This prevents the scheduler from running projects that are not ready or have been taken out of service.

* Parameter relationships
Parameter: project_config['life_cycle']
Condition: No other parameter option is a prerequisite.
Reason and result: “life cycle” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — planning
Marks the planning stage and prevents automatic runs.
1 — designing
Marks ongoing design and prevents automatic runs.
2 — testing
Makes an active project with automatic update enabled eligible for test runs.
3 — maintenance initiated
Prevents automatic runs during maintenance.
4 — cancelled
Keeps the project out of service and prevents automatic runs.
5 — working
Makes an active project with automatic update enabled eligible for production runs.
Example: working
project_config['life_cycle'] = '5'
Parameter ID: 4
about
about textarea

A free-text field for the project purpose, data source, target users, and operational notes. Sufficient context lets a future maintainer understand why the project exists and which assumptions it uses; leaving it empty does not technically stop execution but makes maintenance and auditing harder.

* Parameter relationships
Parameter: project_config['about']
Condition: No other parameter option is a prerequisite.
Reason and result: “about” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
project_config['about'] = 'It calculates the risk of readmission for inpatients on a daily basis.'
Parameter ID: 5
scope type
scope type select

Selection that classifies the project’s business context and is displayed by label in the project list. The code does not use this field to change the data-preparation query.

* Parameter relationships
Parameter: project_config['scope_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “scope type” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — satisfaction survey
Classifies survey and satisfaction work.
1 — digital marketing
Classifies marketing and audience projects.
2 — billing algorithm
Classifies billing control and calculation projects.
3 — research
Classifies research and exploration projects.
4 — report
Classifies projects intended to produce reports.
5 — clinical decision support
Classifies clinical assessment and decision-support projects.
Example: 5 — clinical decision support
project_config['scope_type'] = '5'
Parameter ID: 6
scope
scope text

Specifies the concrete subject within the selected scope type.

For example, if the scope type is clinical decision support, the scope may be “readmission risk”. A clear scope distinguishes projects of the same type; this field does not directly change data-preparation behavior.

* Parameter relationships
Parameter: project_config['scope']
Condition: No other parameter option is a prerequisite.
Reason and result: “scope” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
project_config['scope'] = 'readmission risk'
Parameter ID: 7
sql
sql list_parameter

A list containing one or more connection and query records to execute in MSSQL data-preparation mode. Each item contains an SQL name, server address, username, password, port, and query.

* Parameter relationships
Parameter: project_config['sql_list']
Condition: project_config['data_preparation_mode'] must be '3' — “MSSQL” .
Reason and result: MSSQL connections and queries are defined in this list.
Example:
project_config['sql_list'] = [{'sql_name': 'X hospital', 'sql_database_ip': '100.100.100.100', 'sql_database_username': 'wisdomera', 'sql_database_password': '*****', 'sql_database_port': '', 'sql_query': 'SELECT PatientId FROM [dbo].[PatientSchema].[PatientTable] P WHERE P.Gender = 1'}]
Parameter ID: 9
sql name
sql name text

The human-readable name of a connection and query item in the SQL list. A descriptive name makes selection and troubleshooting easier when several databases or queries are present; the name does not change query results.

* Parameter relationships
Parameter: project_config['sql_list'][0]['sql_name']
Condition: project_config['data_preparation_mode'] must be '3' — “MSSQL” .
Reason and result: The SQL name is populated as part of the related SQL-list item.
Example:
project_config['sql_list'][0]['sql_name'] = 'X hospital'
Parameter ID: 9
sql database ip
sql database ip text

Specifies the network address or resolvable host name of the MSSQL server. With the correct address, the application attempts to connect to the target server.

* Parameter relationships
Parameter: project_config['sql_list'][0]['sql_database_ip']
Condition: project_config['data_preparation_mode'] must be '3' — “MSSQL” .
Reason and result: The database IP is populated as part of the related SQL-list item.
Example:
project_config['sql_list'][0]['sql_database_ip'] = '10.20.30.40'
Parameter ID: 10
sql database username
sql database username text

The database account used to authenticate the MSSQL connection. Data can be prepared when the account has the required read permissions on queried objects.

* Parameter relationships
Parameter: project_config['sql_list'][0]['sql_database_username']
Condition: project_config['data_preparation_mode'] must be '3' — “MSSQL” .
Reason and result: The database username is populated as part of the related SQL-list item.
Example:
project_config['sql_list'][0]['sql_database_username'] = 'wisdomera'
Parameter ID: 11
sql database password
sql database password text

The connection password of the MSSQL account, entered through a password field in the interface.

* Parameter relationships
Parameter: project_config['sql_list'][0]['sql_database_password']
Condition: project_config['data_preparation_mode'] must be '3' — “MSSQL” .
Reason and result: The database password is populated as part of the related SQL-list item.
Example:
project_config['sql_list'][0]['sql_database_password'] = '*****'
Parameter ID: 12
sql database port
sql database port text

Specifies the network port on which the MSSQL service listens. When it matches the server configuration, the connection reaches the correct endpoint.

* Parameter relationships
Parameter: project_config['sql_list'][0]['sql_database_port']
Condition: project_config['data_preparation_mode'] must be '3' — “MSSQL” .
Reason and result: The database port is populated as part of the related SQL-list item.
Example:
project_config['sql_list'][0]['sql_database_port'] = '1433'
Parameter ID: 13
sql query
sql query text

This is a query executed during MSSQL data preparation that generates the rows for a dataset. When a query is created for the first time—and before any design for the columns to be retrieved has been defined—the columns are generated automatically. If a column with the same name already exists in the project, the data is simply added to that existing column. Only read-only queries should be used for this process, and both the query cost and the number of rows returned must be tested beforehand.

* Parameter relationships
Parameter: project_config['sql_list'][0]['sql_query']
Condition: project_config['data_preparation_mode'] must be '3' — “MSSQL” .
Reason and result: The SQL query is populated as part of the related SQL-list item.
Example:
project_config['sql_list'][0]['sql_query'] = 'SELECT PatientId FROM [dbo].[PatientSchema].[PatientTable] P WHERE P.Gender = 1'
Parameter ID: 14
wtransfer map json
wtransfer map json This stores the database maps to be used in 'wtransfer' mode, along with the servers selected for each map, in JSON format. The interface generates this value via the map and server selection window. During data preparation, the system iterates through the maps and servers listed.

Multiple database maps can be defined within a single project. In such cases, the same queries are executed across all selected database maps. This is typically used for multi-center integration models.

For instance, separate database maps can be created for two Hospital Information Management Systems (HIMS) located on different servers and featuring different table structures—as their integration architectures and SQL configurations differ. However, the parameters associated with the layers in these two database maps may correspond to the same target query content.

Consider a scenario where you intend to retrieve a 'gender' value from both locations: in HIMS-1, 'male' might be represented as '1', while in HIMS-2, it might be represented as '0'. Furthermore, table and column names may also vary. Within the WisdomEra 'wtransfer' application, you can create distinct database maps for each system and incorporate both into a unified data-querying project while utilizing the same query model.

* Parameter relationships
Parameter: project_config['wtransfer_map_json']
Condition: project_config['data_preparation_mode'] must be '1' — “Wtransfer” .
Reason and result: Stores the map and server selections used to retrieve data.
Example:
project_config['wtransfer_map_json'] = '{"list":[[{"map_cl_id":"…","servers":[{"server_cl_id":"…"}]}]]}'
Parameter ID: 15
main layer name
main layer name text

Identifies the main layer that serves as the starting point of the target population in the Wtransfer data model. The system evaluates the main rule in this layer’s context to find base records before preparing related column data. If the value does not match an actual layer name in the map, rule and data queries cannot be generated from the correct root.

For instance, if the primary layer in a hospital database concerns patients, it is structured so that each individual row represents a single patient. If the primary layer concerns encounters (or visits), then each individual row is structured to represent a single encounter.

* Parameter relationships
Parameter: project_config['main_layer_name']
Condition: project_config['data_preparation_mode'] must be '1' — “Wtransfer” .
Reason and result: Identifies the main layer in the selected Wtransfer map; a map selection must also exist.
Example:
project_config['main_layer_name'] = 'Patient'
Parameter ID: 16
data preparation row limit
data preparation row limit integer

Limits the total number of rows that may be added to the dataset in one data-preparation run. When a value greater than zero is entered, the Wtransfer and MSSQL flows reduce query batches according to the remaining allowance and stop fetching new rows at the limit; an empty or inactive value applies no limit. A small value during testing reduces query time and resource consumption.

* Parameter relationships
Parameter: project_config['data_preparation_row_limit']
Condition: project_config['data_preparation_mode'] must be '1' — “Wtransfer” , '2' — “Wisdombase” , '3' — “MSSQL” .
Reason and result: Row limit is used by system-driven preparation modes and hidden in manual mode.
Example:
project_config['data_preparation_row_limit'] = '100'
Parameter ID: 17
process application
in which application is the transaction This is an application identifier that determines which "Wanalyzer" application node within a WisdomEra platform installation is responsible for handling an automated process. WisdomTimer will only prepare the project configuration and proceed with automated process controls if this value matches the configured identifier of the running application exactly. If the field is empty or points to a different application ID, the timer code being evaluated will not execute the project on that specific application node. When a new project is defined in the system, the number of projects already assigned to each application is calculated using this value; the project is then assigned to the Wanalyzer application node with the fewest existing assignments. This ensures load balancing for project execution.

For example, if a WisdomEra installation shows high CPU or RAM usage on an existing server node, a second server node with a Wanalyzer application can be added. This new Wanalyzer instance will then begin sharing the workload and taking on project tasks. New Wanalyzer nodes can be added via the "wamserver" application interface.

* Parameter relationships
Parameter: project_config['process_application']
Condition: No other parameter option is a prerequisite.
Reason and result: “process application” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example: An ID value in the format bd513e04-d868-45d5-82d3-78ed0d2a7bef is used for an application, indicating that the processes for a given project are handled by that specific application. This ID is generated automatically during the registration of a new project and cannot be created manually.
project_config['process_application'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 18
auto data update
automatic data update select

Enables or disables the scheduler for automatic data preparation within the project.

If "Yes" is selected, the automatic process may begin, provided the project is active, its lifecycle is in a testing or running phase, and the time filters are met.

If "No" is selected, the automatic process will not start, even if all other conditions are met. Manual data preparation tasks can still be initiated by the user, regardless of this setting.

* Parameter relationships
Parameter: project_config['auto_data_update']
Condition: project_config['data_preparation_mode'] must be '1' — “Wtransfer” , '2' — “Wisdombase” , '3' — “MSSQL” .
Reason and result: '0' — “no” disables scheduling. '1' — “yes” enables time-cycle, day/hour, and update-mode fields.
Options and use cases
0 — No
Disables scheduler-triggered data preparation.
1 — Yes
Enables scheduler-triggered data preparation, subject to other eligibility conditions.
Example:
project_config['auto_data_update'] = '1'
Parameter ID: 20
time cycle type
time cycle type select

Determines the timing logic that makes automatic data update eligible. Instantaneous is eligible at every scheduler evaluation; minute, hour, and day cycles wait until the time-cycle value has elapsed since the latest process start; specified times during the day is eligible only in selected hours and at most once within the same hour. Month, weekday, and day-of-month filters are applied before every cycle type.

* Parameter relationships
Parameter: project_config['time_cycle_type']
Condition: project_config['auto_data_update'] must be '1' — “yes” .
Reason and result: '0' means “instantaneous” ; '1' “every minute” ; '2' “every hour” ; '3' “every day” ; and '4' “at specified times during the day” . Values '1'–'3' enable project_config['time_cycle_value'] .
Options and usage purposes
0 — instantaneous
Becomes eligible at every scheduler check when date filters match.
1 — every minute
Becomes eligible after the specified number of minutes since the latest process.
2 — every hour
Becomes eligible after the specified number of hours since the latest process.
3 — every day
Becomes eligible after the specified number of days since the latest process.
4 — at specified times during the day
Becomes eligible in selected hours without repeating within the same hour.
Example:
project_config['time_cycle_type'] = '1'
Parameter ID: 21
time cycle value
time cycle value float

Specifies the numeric interval for minute-, hour-, or day-based cycles. For example, with an hourly cycle and value 6, the project becomes eligible again at least six hours after the latest process start.

* Parameter relationships
Parameter: project_config['time_cycle_value']
Condition: project_config['time_cycle_type'] must be '1' — “every minute” , '2' — “every hour” , '3' — “every day” .
Reason and result: Defines the minutes, hours, or days between cycles; automatic data updating must also be “yes”.
Example:
project_config['time_cycle_value'] = 6'
Parameter ID: 22
defined hours
defined hours checkbox

Stores the time options for the cycle based on the hours specified for the day. Selecting 24 corresponds to 00:00 (midnight).

* Parameter relationships
Parameter: project_config['defined_hours']
Condition: project_config['auto_data_update'] must be '1' — “yes” .
Reason and result: Defines the defined hours within automatic-update scheduling; it is not evaluated when automatic updating is disabled.
Options and usage purposes
0 — 1
Adds this hour to the automatic-run window.
1 — 2
Adds this hour to the automatic-run window.
2 — 3
Adds this hour to the automatic-run window.
3 — 4
Adds this hour to the automatic-run window.
4 — 5
Adds this hour to the automatic-run window.
5 — 6
Adds this hour to the automatic-run window.
6 — 7
Adds this hour to the automatic-run window.
7 — 8
Adds this hour to the automatic-run window.
8 — 9
Adds this hour to the automatic-run window.
9 — 10
Adds this hour to the automatic-run window.
10 — 11
Adds this hour to the automatic-run window.
11 — 12
Adds this hour to the automatic-run window.
12 — 13
Adds this hour to the automatic-run window.
13 — 14
Adds this hour to the automatic-run window.
14 — 15
Adds this hour to the automatic-run window.
15 — 16
Adds this hour to the automatic-run window.
16 — 17
Adds this hour to the automatic-run window.
17 — 18
Adds this hour to the automatic-run window.
18 — 19
Adds this hour to the automatic-run window.
19 — 20
Adds this hour to the automatic-run window.
20 — 21
Adds this hour to the automatic-run window.
21 — 22
Adds this hour to the automatic-run window.
22 — 23
Adds this hour to the automatic-run window.
23 — 24
Adds this hour to the automatic-run window.
Example: It means it will operate at 8:00 and 19:00.
project_config['defined_hours'] = ['8', '19']
Parameter ID: 23
selected days
selected days checkbox

Filters the weekdays on which automatic update may run. When the list contains values, the time cycle is evaluated only if the current weekday is selected; when empty, every weekday is accepted. For example, selecting Monday through Friday prevents automatic runs on weekends even when timing and all other conditions match.

* Parameter relationships
Parameter: project_config['selected_days']
Condition: project_config['auto_data_update'] must be '1' — “yes” .
Reason and result: Defines the selected days within automatic-update scheduling; it is not evaluated when automatic updating is disabled.
Options and usage purposes
0 — monday
Adds this weekday to the automatic-run calendar.
1 — tuesday
Adds this weekday to the automatic-run calendar.
2 — wednesday
Adds this weekday to the automatic-run calendar.
3 — thursday
Adds this weekday to the automatic-run calendar.
4 — friday
Adds this weekday to the automatic-run calendar.
5 — saturday
Adds this weekday to the automatic-run calendar.
6 — sunday
Adds this weekday to the automatic-run calendar.
Example: If work is requested for Thursday and Friday, the 3rd and 4th options are selected.
project_config['selected_days'] = ['3', '4']
Parameter ID: 24
selected months
selected months checkbox

Filters the months in which automatic update may run. When the list contains values, other timing conditions are evaluated only if the current month is selected; when empty, every month of the year is accepted. Selecting only relevant months for a seasonal project prevents automatic data preparation outside the season.

For example, the seasonal allergic rhinitis algorithm can be selected for months such as March, April, and May—periods when allergy symptoms tend to intensify.

* Parameter relationships
Parameter: project_config['selected_months']
Condition: project_config['auto_data_update'] must be '1' — “yes” .
Reason and result: Defines the selected months within automatic-update scheduling; it is not evaluated when automatic updating is disabled.
Options and usage purposes
0 — January
Adds this month to the automatic-run calendar.
1 — February
Adds this month to the automatic-run calendar.
2 — March
Adds this month to the automatic-run calendar.
3 — April
Adds this month to the automatic-run calendar.
4 — May
Adds this month to the automatic-run calendar.
5 — June
Adds this month to the automatic-run calendar.
6 — July
Adds this month to the automatic-run calendar.
7 — August
Adds this month to the automatic-run calendar.
8 — September
Adds this month to the automatic-run calendar.
9 — October
Adds this month to the automatic-run calendar.
10 — November
Adds this month to the automatic-run calendar.
11 — December
Adds this month to the automatic-run calendar.
Example: When it is required to operate during the months of January, February, and March, the options 0, 1, and 2 are selected.
project_config['selected_months'] = ['0', '1', '2']
Parameter ID: 25
day of month
day of month checkbox

Filters the calendar days, from 1 through 31, on which automatic update may run. When the list contains values, the time cycle is evaluated only if the current day of the month is selected; when empty, every day of the month is accepted. A selected day such as 29, 30, or 31 cannot trigger a run in a month where that date does not exist.

* Parameter relationships
Parameter: project_config['day_of_month']
Condition: project_config['auto_data_update'] must be '1' — “yes” .
Reason and result: Defines the days of month within automatic-update scheduling; it is not evaluated when automatic updating is disabled.
Options and usage purposes
0 — 1
Adds this date to the automatic-run calendar.
1 — 2
Adds this date to the automatic-run calendar.
2 — 3
Adds this date to the automatic-run calendar.
3 — 4
Adds this date to the automatic-run calendar.
4 — 5
Adds this date to the automatic-run calendar.
5 — 6
Adds this date to the automatic-run calendar.
6 — 7
Adds this date to the automatic-run calendar.
7 — 8
Adds this date to the automatic-run calendar.
8 — 9
Adds this date to the automatic-run calendar.
9 — 10
Adds this date to the automatic-run calendar.
10 — 11
Adds this date to the automatic-run calendar.
11 — 12
Adds this date to the automatic-run calendar.
12 — 13
Adds this date to the automatic-run calendar.
13 — 14
Adds this date to the automatic-run calendar.
14 — 15
Adds this date to the automatic-run calendar.
15 — 16
Adds this date to the automatic-run calendar.
16 — 17
Adds this date to the automatic-run calendar.
17 — 18
Adds this date to the automatic-run calendar.
18 — 19
Adds this date to the automatic-run calendar.
19 — 20
Adds this date to the automatic-run calendar.
20 — 21
Adds this date to the automatic-run calendar.
21 — 22
Adds this date to the automatic-run calendar.
22 — 23
Adds this date to the automatic-run calendar.
23 — 24
Adds this date to the automatic-run calendar.
24 — 25
Adds this date to the automatic-run calendar.
25 — 26
Adds this date to the automatic-run calendar.
26 — 27
Adds this date to the automatic-run calendar.
27 — 28
Adds this date to the automatic-run calendar.
28 — 29
Adds this date to the automatic-run calendar.
29 — 30
Adds this date to the automatic-run calendar.
30 — 31
Adds this date to the automatic-run calendar.
Example: To set it to operate on the 1st and 15th days, select options 0 and 14.
project_config['day_of_month'] = ['0', '14']
Parameter ID: 26
auto data update mode
auto data update mode select

Determines how automatic data-preparation results are applied to the existing dataset. Delete all and add performs a full refresh; add new rows only preserves existing records; update and add modifies matches and inserts new records; update only changes existing matches. Evaluate it with business requirement.

* Parameter relationships
Parameter: project_config['auto_data_update_mode']
Condition: project_config['auto_data_update'] must be '1' — “yes” .
Reason and result: Defines the update mode within automatic-update scheduling; it is not evaluated when automatic updating is disabled.
Options and usage purposes
0 — delete all dataset and add new rows
Removes existing dataset rows and writes the result from scratch.
1 — do not delete or update dataset and add new rows
Preserves existing rows and only adds new rows.
2 — update dataset and add new rows
Updates matching rows and inserts rows that do not exist.
3 — update dataset
Updates only existing matching rows.
Example: To delete all data and prepare the data anew, select option 0.
project_config['auto_data_update_mode'] = '0'
Parameter ID: 27
algorithm columns auto work status
algorithm columns automatic working status select

Determines whether the calculations for algorithm-based columns should be triggered automatically once data preparation is complete.

If "Yes" is selected, the algorithm columns are triggered during the final stages of data preparation, allowing any defined automated analyses to be evaluated subsequently.

If "No" is selected, the dataset is prepared, but any existing algorithm columns must be executed manually.

* Parameter relationships
Parameter: project_config['algorithm_columns_auto_work_status']
Condition: project_config['auto_data_update'] must be '1' — “yes” .
Reason and result: Defines the algorithm-column execution status within automatic-update scheduling; it is not evaluated when automatic updating is disabled.
Options and use cases
0 — No
Does not automatically execute algorithm columns upon completion of data preparation.
1 — Yes
Automatically triggers algorithm columns upon completion of data preparation.
Example:
project_config['algorithm_columns_auto_work_status'] = '1'
Parameter ID: 28
main rule json
main rule json Wtransfer stores the rule tree—which filters target records within the main layer—in JSON format. During data preparation, this rule, along with the name of the main layer, is sent to the Wtransfer query; rows that satisfy the main rule are then retrieved as the target population. Individual rows from the main layer that conform to the established rule are pulled into the dataset.

For instance, if you request data where the main layer is "patient" and the age is over 65, each row will represent a unique patient. Conversely, if you request data where the main layer is "encounter" (or "application/visit") and the age is over 65, the system will retrieve all encounters for patients over 65—meaning that if a single patient has multiple encounters, each one will be included as a separate row.

* Parameter relationships
Parameter: project_config['main_rule_json']
Condition: project_config['data_preparation_mode'] must be '1' — “Wtransfer” .
Reason and result: This is the main filter rule applied to Wtransfer data.
Example: Age ≥ 65 and active patient
project_config['main_rule_json'] = '{"query_list":[],"compile_str_date":[],"compile_str_text":[],"compile_str_array":[]}'
Parameter ID: 29
copied project client id
copied project client id text

When a project is copied from another project, it stores the client ID of the source project. This information allows for tracking which project the copy was created from and is displayed in the interface as a read-only source reference. It is generated automatically when the copy service is executed; it cannot be defined manually via the interface.

* Parameter relationships
Parameter: project_config['copied_project_client_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “copied project client id” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
project_config['copied_project_client_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 30
about
status
status select

This is the status value in the column record. The active mode is used.

* Parameter relationships
Parameter: column_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Represents passive in the layer options; current column-save code overwrites it with 1.
1 — active
The current status value written for every column by column-save code.
Example:
column_config['status'] = '1'
Parameter ID: 0
wanalyzer project id
wanalyzer project id text

The client identifier of the Wanalyzer project to which the column belongs.

* Parameter relationships
Parameter: column_config['wanalyzer_project_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “wanalyzer project id” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
column_config['wanalyzer_project_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 1
name
name textarea

The name displayed in dataset headers and design screens. A descriptive and unique name makes the correct column easy to select in rules and mappings.

* Parameter relationships
Parameter: column_config['name']
Condition: No other parameter option is a prerequisite.
Reason and result: “name” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
column_config['name'] = 'Creatinine Result mg/dl'
Parameter ID: 2
note
note textarea

Explains the column’s meaning, unit, source, and calculation assumptions. A sufficient note helps users interpret the generated value correctly; an empty or outdated note does not stop technical execution but may cause the analytical result to be misunderstood.

* Parameter relationships
Parameter: column_config['note']
Condition: No other parameter option is a prerequisite.
Reason and result: “note” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
column_config['note'] = 'The most recent creatinine value from the last 30 days, in mg/dL.'
Parameter ID: 3
order
order integer

It is an integer that represents the index value in a list of columns, starting from zero.

* Parameter relationships
Parameter: column_config['order']
Condition: No other parameter option is a prerequisite.
Reason and result: “order” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
column_config['order'] = 0
Parameter ID: 4
data source
data source select

Determines whether the column value is generated from the database or manually.

If "manual" is selected, the value is generated via user input, rules and functions, machine learning, natural language processing, or an algorithmic API flow.

If "database" is selected, the field data is retrieved via a layer rule in Wtransfer.

* Parameter relationships
Parameter: column_config['data_source']
Condition: No other parameter option is a prerequisite.
Reason and result: This controller has no prerequisite. '0' — “manual” enables column_config['manuel_data_creation_type'] and generation settings. '1' — “database” enables text/numeric usage, root-column, and layer-rule fields.
Options and usage purposes
0 — manuel
Defines the column as entered or produced inside project.
1 — database
Defines the column as prepared from Wtransfer layer data.
Example:
column_config['data_source'] = '1'
Parameter ID: 5
parameter type
parameter type select

Determines the data type of column values and how they are edited in the interface. With the correct type, rule comparisons, numeric operations, options, and date evaluations work appropriately.

* Parameter relationships
Parameter: column_config['parameter_type']
Condition: No other parameter option is a prerequisite.
Reason and result: Determines the column format: '0' “text” , '1' “select/categorical” , '2' “float” , '3' “integer” , '4' “textarea” , and '5' “datetime” . Option '1' enables options and value/label usage; algorithm-API generation forces this type to '1' .
Options and usage purposes
0 — text
Used for short text values.
1 — select
Used for categorical values selected from defined options.
2 — float
Used for numeric values that may contain decimals.
3 — integer
Used for whole-number values.
4 — textarea
Used for long, multiline text.
5 — datetime
Used for values containing date and time.
Example:
column_config['parameter_type'] = '2'
Parameter ID: 6
value or label usage
value or label usage select

For database columns with predefined options, this setting determines whether the option's ID (identifier) ​​or its label (display text) is written to the dataset.

Selecting "value" preserves the underlying code used for integration, while selecting "label" provides a human-readable term.

If the algorithms require a code, choose "value"; if the report is intended for end-user viewing, choose "label."

For instance, in API integrations, it is often necessary to send an ID rather than a label; in such cases, the "value"—the ID—should be used. Consider a "gender" column: data can be written to a cell in two ways—either as the term "Male" or as the ID associated with that label (e.g., 1). If "label" is selected, the cell will display "Male."

* Parameter relationships
Parameter: column_config['value_or_label_usage']
Condition: column_config['data_source'] must be '1' — “database” .
Reason and result: Parameter type must also be “select/categorical”; this chooses the technical value or displayed label.
Options and usage purposes
0 — value
Uses the option’s technical value.
1 — label
Uses the option’s displayed label.
Example:
column_config['value_or_label_usage'] = '0'
Parameter ID: 7
text or numeric usage
numeric or text-based handling select

Determines whether values ​​should be treated as a numerical summary or as a selection of text-based records when multiple database entries are retrieved. If "numeric" is selected, operations such as average, median, maximum, minimum, or sum are applied; if "text" is selected, the system uses an approach based on the oldest, most recent, or all available records.

This setting defines how data should be handled, regardless of whether the underlying database data is numerical or textual. For example, if a laboratory value—which is numerical in nature—is retrieved in a text format, it is presented as a list within the target cell, without any calculations like averages being performed. If "numeric" is selected, a specific calculation model must then be chosen. The numeric mode is typically used in cases where a single cell contains multiple data entries.

For example:

- If a single row contains multiple blood sugar values ​​and you intend to calculate their average and record the result in the cell, you can use the numeric mode.

- If you prefer to have all blood sugar values ​​listed in the cell—along with their corresponding dates—you should select the text format.

* Parameter relationships
Parameter: column_config['text_or_numeric_usage']
Condition: column_config['data_source'] must be '1' — “database” .
Reason and result: Determines whether the column is processed with text rules or numeric aggregation.
Options and intended use
0 — text
Processes records using text-based selection rules.
1 — numeric
Processes records using numerical aggregation rules.
Example: 1 — numeric
column_config['text_or_numeric_usage'] = '1'
Parameter ID: 8
numeric usage type
numeric usage type select

Determines which value will be written into a single cell within a numerical, multi-record column.

For example, mean produces the arithmetic average of valid values and maximum produces the largest value.

* Parameter relationships
Parameter: column_config['numeric_usage_type']
Condition: column_config['text_or_numeric_usage'] must be '1' — “numeric” .
Reason and result: Selects mean, median, maximum, minimum, or sum for numeric values.
Options and usage purposes
0 — mean
Calculates the arithmetic mean of valid values.
1 — median
Calculates the median of ordered values.
2 — maximum
Takes the largest value.
3 — minimum
Takes the smallest value.
4 — sum
Sums the valid values.
Example:
column_config['numeric_usage_type'] = '0'
Parameter ID: 9
text usage type
text usage type select

Determines which historical record is used for textual data with multiple records. Oldest or most recent produces one record. Without date information, ordering may remain dependent on the source order.

* Parameter relationships
Parameter: column_config['text_usage_type']
Condition: column_config['text_or_numeric_usage'] must be '0' — “text” .
Reason and result: Data source must also be “database”; this determines how text data is selected.
Options and usage purposes
0 — get the oldest historical record
Uses the first record by date.
1 — get the most recent historical record
Uses the latest record by date.
2 — get all records
Passes all eligible records to list handling.
Example:
column_config['text_usage_type'] = '0'
Parameter ID: 10
same values usage type
same values usage type select

This determines how to handle repeated identical values ​​within multiple records. If frequency or time-based analysis is to be performed, these repetitions must be preserved.

For instance, in a project where the primary entity is the patient, one might plan to list all diabetes diagnoses associated with a patient in a single column.

There are two possible approaches here:

  • If the specific dates are not significant, there is no need for the same diagnosis code to appear multiple times in a cell. In this case, the option to "retrieve unique values ​​(excluding dates)" is used.
  • If, however, it is necessary to retain the dates alongside the diagnosis codes—even when the same diagnosis occurs multiple times—the option to "retrieve repeated values ​​(including dates)" should be selected.

For example, when extracting a diagnosis value from an ICD column based on a date range found in another column, the "retrieve repeated values ​​(including dates)" option is specified. This model is used, for instance, when answering a question such as: "Did the patient receive an 'X' diagnosis within 15 days of their initial visit?"

* Parameter relationships
Parameter: column_config['same_values_usage_type']
Condition: column_config['text_or_numeric_usage'] must be '0' — “text” .
Reason and result: Data source must also be “database” and text usage type must be “2”; this controls deduplication or retention with dates.
Options and intended use
0 — get unique values ​​without a date
Removes duplicates and does not include dates.
1 — get duplicate values ​​with their dates
Retains duplicates along with their respective dates.
Example:
column_config['same_values_usage_type'] = '0'
Parameter ID: 12
manuel data creation type
manuel data creation type select

Determines which engine produces the value of a manually sourced column. Depending on the selection, direct entry, rules and functions, machine-learning mappings, a natural-language processing phrase definition, or algorithm application programming interface settings are used.

* Parameter relationships
Parameter: column_config['manuel_data_creation_type']
Condition: column_config['data_source'] must be '0' — “manual” .
Reason and result: '0' means “manual” ; '1' “rule and function” ; '2' “machine-learning model” ; '3' “NLP model” ; and '4' “algorithm API” . Each option enables only its own settings.
Options and usage purposes
0 — manuel
Manages the value through user entry.
1 — rule and function
Produces the value with conditional functions.
2 — machine learning model
Produces a prediction with the selected model and input mappings.
3 — nlp model
Produces a result from the selected text column and phrase model.
4 — algorithm api
Produces a result with the selected application programming interface and variable mappings.
Example:
column_config['manuel_data_creation_type'] = '0'
Parameter ID: 13
root based column status
root based column status select

Specifies whether a database column should be generated based on the related sub-records of another database column.

For example, consider a column defined to capture a patient's first internal medicine encounter in the system. It may be necessary to retrieve the list of associated diagnosis codes into a separate column. In this case, the "first internal medicine encounter" column is selected as the root column for the column containing the associated diagnosis codes.

* Parameter relationships
Parameter: column_config['root_based_column_status']
Condition: column_config['data_source'] must be '1' — “database” .
Reason and result: '0' — “no” disables the root relationship; '1' — “yes” enables column_config['root_based_column_index'] .
Options and use cases
0 — no
Disables the relevant behavior.
1 — yes
Enables the relevant behavior.
Example:
column_config['root_based_column_status'] = '1'
Parameter ID: 14
root based column index
root based column index integer

When the root-related column condition is met, this represents the index—that is, the zero-based sequence value—of the parent column. The code uses this relationship to organize the processing order of database columns and to determine the identifier for the relationship field.

It is assigned automatically when a selection is made from the list of columns on the screen.

* Parameter relationships
Parameter: column_config['root_based_column_index']
Condition: column_config['root_based_column_status'] must be '1' — “yes” .
Reason and result: Selects the root database column used by the relationship.
Example:
column_config['root_based_column_index'] = 0
Parameter ID: 15
layer rule json
layer rule json textarea

This is a rule object that defines the Wtransfer layer, parameter, and filter conditions for a database column.

It can be created via the rule editor on the screen.

* Parameter relationships
Parameter: column_config['layer_rule_json']
Condition: column_config['data_source'] must be '1' — “database” .
Reason and result: Defines the rule used to obtain the column from layer data.
Example:
column_config['layer_rule_json'] = {'query_list': [], 'compile_str_array': [], 'compile_str_date': [], 'compile_str_text': []}
Parameter ID: 16
Kolonla ilişkili görseli metin tabanlı görsel verisi olarak saklar. Görsel tanımlanırsa kolonun sunum veya sınıflandırma bağlamında görsel karşılığı kullanılabilir; büyük görseller kayıt boyutunu artıracağı için yalnızca gerekli ve uygun boyutlu içerik kullanılmalıdır.
image image

This is a field in a column record that contains an image in base64 format. It represents the column itself. In WAI algorithms, it can be used as an image displayed next to the column whenever the column is shown on screen. It is not frequently used in routine data analytics.

* Parameter relationships
Parameter: column_config['image']
Condition: No other parameter option is a prerequisite.
Reason and result: “Kolonla ilişkili görseli metin tabanlı görsel verisi olarak saklar. Görsel tanımlanırsa kolonun sunum veya sınıflandırma bağlamında görsel karşılığı kullanılabilir; büyük görseller kayıt boyutunu artıracağı için yalnızca gerekli ve uygun boyutlu içerik kullanılmalıdır.” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
column_config['image'] = ''
Parameter ID: 17
function
function list_parameter

Holds one or more conditional function definitions for a manual column generated via rules and functions. Each item contains both the function code and the rule under which that code should execute.

A function area may contain a list of function codes and function rules. The process continues until it reaches the final rule that yields a positive result. For instance, suppose five functions are defined; even if the second function returns a positive result, the process will continue until it reaches the last rule that produces a positive outcome.

For example, if 'yes' is entered into the function code field—with no function rule defined and this being the only function row present—the value 'yes' will be written directly into the cell. Since there is no rule, the row is considered valid, and the function code is executed; furthermore, as no specific function logic has been defined, the result 'yes' is simply written into the cell.

* Parameter relationships
Parameter: column_config['function']
Condition: column_config['manuel_data_creation_type'] must be '1' — “rule and function” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example: If the rule within `function_rule` evaluates to true, it proceeds to execute the `function_code` field.
column_config['function'] = [{'function_code': '', 'function_rule': {'query_list': [], 'compile_str_array': [], 'compile_str_date': [], 'compile_str_text': []}}]
Parameter ID: 18
function code
function code textarea

The code or defined function expression that generates a column value when the corresponding rule in the function list is satisfied. References such as col1 and col2 ensure that dependent manual columns are calculated first; invalid column references or unsupported expressions may cause errors.

Fonksiyon kodu yazım kuralları:

* Parameter relationships
Parameter: column_config['function'][0]['function_code']
Condition: The related column_config['function'] list item must exist.
Reason and result: “function code” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example:
column_config['function'][0]['function_code'] = ''
Parameter ID: 19
function - Cell and data operations
1. Cell and data operations 5 functions function
* Parameter relationships
Parameter: column_config['function']
Condition: No other parameter option is a prerequisite.
Reason and result: “function - Cell and data operations” is populated directly in its record context and is not enabled or disabled by another parameter selection.
function - Statistical and numerical operations
2. Statistical and numerical operations 9 functions function
* Parameter relationships
Parameter: column_config['function']
Condition: No other parameter option is a prerequisite.
Reason and result: “function - Statistical and numerical operations” is populated directly in its record context and is not enabled or disabled by another parameter selection.
function - Historical data selection
3. Historical data selection 11 functions function
* Parameter relationships
Parameter: column_config['function']
Condition: No other parameter option is a prerequisite.
Reason and result: “function - Historical data selection” is populated directly in its record context and is not enabled or disabled by another parameter selection.
function - Date and time operations
4. Date and time operations 15 functions function
* Parameter relationships
Parameter: column_config['function']
Condition: No other parameter option is a prerequisite.
Reason and result: “function - Date and time operations” is populated directly in its record context and is not enabled or disabled by another parameter selection.
function - Text processing and regular expressions
5. Text processing and regular expressions 2 functions function
* Parameter relationships
Parameter: column_config['function']
Condition: No other parameter option is a prerequisite.
Reason and result: “function - Text processing and regular expressions” is populated directly in its record context and is not enabled or disabled by another parameter selection.
function - AI integration
6. AI integration 1 functions function
* Parameter relationships
Parameter: column_config['function']
Condition: No other parameter option is a prerequisite.
Reason and result: “function - AI integration” is populated directly in its record context and is not enabled or disabled by another parameter selection.
function - Row-based code script
7. Row-based code script 1 function function
* Parameter relationships
Parameter: column_config['function']
Condition: No other parameter option is a prerequisite.
Reason and result: “function - Row-based code script” is populated directly in its record context and is not enabled or disabled by another parameter selection.
function rule
function rule textarea

The JSON rule that determines on which rows in the dataset a function code runs. A correct rule applies the function to matching rows; an incorrect or empty condition may produce values on unintended rows or produce no value. The rule editor creates the query list and compilation arrays together.

The process continues until it reaches the final rule that yields a positive result. For instance, suppose five functions are defined; even if the second function returns a positive result, the process will continue until it reaches the last rule that produces a positive outcome.

* Parameter relationships
Parameter: column_config['function'][0]['function_rule']
Condition: The related column_config['function'] list item must exist.
Reason and result: “function rule” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example: Execute when age ≥ 65.
column_config['function'][0]['function_rule'] = {'query_list': [], 'compile_str_array': [], 'compile_str_date': [], 'compile_str_text': []}
Parameter ID: 20
api id
api id text

The client identifier of the record selected from the user application programming interface layer for the algorithm API method.

For instance, if, after the data has been prepared within a project, a specific piece of information from a row needs to be transferred to another API, the API definition is assigned to the corresponding column. This API definition is not configured manually; rather, when a user selects an API from the list provided on the screen, its ID value is automatically written to this variable. Consequently, it functions as a system-managed parameter.

* Parameter relationships
Parameter: column_config['api_id']
Condition: column_config['manuel_data_creation_type'] must be '4' — “algorithm API” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example:
column_config['api_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 21
algorithm message
algorithm message text

In algorithm-triggering columns, column data corresponding to rows that meet the algorithm's criteria can be sent to a target API system. Furthermore, message information defined as a parameter for the column can also be transmitted via the API.

* Parameter relationships
Parameter: column_config['algorithm_message']
Condition: column_config['manuel_data_creation_type'] must be '4' — “algorithm API” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example:
column_config['algorithm_message'] = 'The patient presents with frequent abdominal pain. You may want to evaluate for rare underlying conditions.'
Parameter ID: 22
algorithm rule
algorithm rule textarea

The JSON rule object that determines which dataset rows run the algorithm application programming interface column. A row is prepared for the API operation when it satisfies the rule.

* Parameter relationships
Parameter: column_config['algorithm_rule']
Condition: column_config['manuel_data_creation_type'] must be '4' — “algorithm API” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example:
column_config['algorithm_rule'] = {'query_list': [], 'compile_str_array': [], 'compile_str_date': [], 'compile_str_text': []}
Parameter ID: 23
algorithm operation id
algorithm operation id textarea

In the column record, this is an ID value in text format that serves as an algorithm operation identifier. A value to be sent to the API—whenever the rule in the algorithm column returns a positive result—can be defined here. This value can then be used by the receiving system, for instance, as an algorithm ID or as a tag for grouping purposes.

For example, a value of 1000 could be assigned to a physician decision-support algorithm, while a value of 2000 could be assigned to a nurse decision-support algorithm, facilitating such categorization.

* Parameter relationships
Parameter: column_config['algorithm_operation_id']
Condition: column_config['manuel_data_creation_type'] must be '4' — “algorithm API” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example:
column_config['algorithm_operation_id'] = '1000'
Parameter ID: 24
wai input
wai input select

WAI is an abbreviation for "WisdomEra Artificial Intelligence." It is an architecture used in the development of frontend interfaces that rely on data queries or machine learning model queries in the backend. When a column is designated as a "WAI input" and the corresponding project is linked to a WAI interface, that column will be displayed on the screen. It is recommended to manage the WAI process in conjunction with the provided WAI documentation sections.

For example, if a "gender" column is selected as a WAI input, it will appear on the screen as a selectable parameter for the user.

* Parameter relationships
Parameter: column_config['wai_input']
Condition: column_config['manuel_data_creation_type'] must be '4' — “algorithm API” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Options and usage purposes
0 — no
Disables the related behavior.
1 — yes
Enables the related behavior.
Example:
column_config['wai_input'] = '1'
Parameter ID: 25
wai output
wai output select

WAI stands for "WisdomEra Artificial Intelligence." It is an architecture used in the development of frontend interfaces that rely on data queries or machine learning model inferences. When a column is designated as a WAI output—and provided the relevant project is linked to a WAI-enabled interface—that column will appear on the screen, displaying the corresponding result. It is recommended that the WAI management process be utilized in conjunction with the provided WAI documentation.

For instance, if a "cardiac risk score" column is selected as a WAI output, this scoring parameter will be displayed to the user on the interface where the WAI project is configured. Consequently, after entering various input values, the user will be able to view the resulting output directly within that column on the screen.

Options and usage purposes

* Parameter relationships
Parameter: column_config['wai_output']
Condition: column_config['manuel_data_creation_type'] must be '4' — “algorithm API” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
0 — no
Disables the related behavior.
1 — yes
Enables the related behavior.
Example:
column_config['wai_output'] = '1'
Parameter ID: 26
option
option list_parameter

Contains the allowed values of a categorical column together with each value, label, and optional rule. The technical value is used for data mapping, the label for display, and an option rule can produce the value according to row conditions. Repeating the same technical value creates ambiguous mapping.

For manual-type columns, options can be generated using rules. These rules operate based on the row data in the dataset and write the result into the cell.

* Parameter relationships
Parameter: column_config['options']
Condition: No other parameter option is a prerequisite.
Reason and result: “option” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example:
column_config['options'] = [{'label': 'male', 'value': '1', 'rule': {'query_list': [], 'compile_str_array': [], 'compile_str_date': [], 'compile_str_text': []}}]
Parameter ID: 27
option id
option id text

The option’s identifier value used in datasets and integrations.

* Parameter relationships
Parameter: column_config['options'][0]['value']
Condition: The related column_config['options'] list item must exist.
Reason and result: “option id” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example:
column_config['options'][0]['value'] = '1'
Parameter ID: 28
option label
option label text

The human-readable name displayed to users for the option.

* Parameter relationships
Parameter: column_config['options'][0]['label']
Condition: The related column_config['options'] list item must exist.
Reason and result: “option label” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example:
column_config['options'][0]['label'] = 'male'
Parameter ID: 29
option rule
option rule text

The JSON rule that determines under which row condition an option is assigned in a manual categorical column. When the condition matches, the option can become the column value; if several option rules overlap on the same row, the design may become ambiguous. Test rules together for priority and mutual exclusivity.

* Parameter relationships
Parameter: column_config['options'][0]['rule']
Condition: The related column_config['options'] list item must exist.
Reason and result: “option rule” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example:
column_config['options'][0]['rule'] = {'query_list': [], 'compile_str_array': [], 'compile_str_date': [], 'compile_str_text': []}
Parameter ID: 30
nlp phrase id
nlp phrase id text

The system supports expression tagging based on natural language processing (NLP). These expression tags can be assigned to a specific column, allowing for the extraction of data from the text contained within that column based on the generated tags. Furthermore, thousands of pre-developed NLP expression tags—created by WisdomEra—can be assigned to a column. The ID values ​​associated with these tags are not created manually; instead, users select them from a list of available NLP expression tags via the interface.

For instance, this structure can be used to extract age-related expressions from patient examination notes and record them in a designated column. Suppose column 2 contains clinical examination summaries (epikrisis notes), which may include various expressions. By applying an NLP expression model designed for age, the value "50" can be extracted and mapped to column 3.

Patient aged 50

Age: 50

For a 50-year-old patient...

* Parameter relationships
Parameter: column_config['nlp_phrase_id']
Condition: column_config['manuel_data_creation_type'] must be '3' — “NLP model” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example:
column_config['nlp_phrase_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 31
nlp analyse column index
nlp analyse column index text

This refers to the index of the source text column from which the natural language processing model will read data. It is assigned by selecting it from the list of columns displayed on the screen; it is not specified manually.

For instance, this structure can be used when one wishes to extract a patient's age from clinical examination notes and record it in a separate column. Suppose that clinical summary (epicrisis) information is contained in column 2. If the patient's age is to be read from column 2 and written to column 3, this value will be populated in column 3. During this process, the reference to column 2 is recorded as '1' within the system. However, this is handled automatically by the system; the user does not enter this value manually.

* Parameter relationships
Parameter: column_config['nlp_analyse_column_index']
Condition: column_config['manuel_data_creation_type'] must be '3' — “NLP model” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example: The second column appearing on the screen actually has an index of 1 when starting from zero.
column_config['nlp_analyse_column_index'] = 1
Parameter ID: 32
machine learning model id
machine learning model id text

For machine learning models generated within projects for which a user has authorization—much like with NLP expression models—it is possible to produce a predicted value in a target column by utilizing source columns. This value is not created manually by the user; rather, it is populated once a model is selected from the list of machine learning models registered in the system.

For instance, consider a project that predicts the need for surgery, using parameters such as gender and disease stage as inputs.

Subsequently, this model can be employed in a new project to generate predictions. The new project must contain the necessary input data, such as age and gender. Once the machine learning model is selected, the columns from which the model’s input values ​​are to be drawn must also be mapped accordingly.

* Parameter relationships
Parameter: column_config['machine_learning_model_id']
Condition: column_config['manuel_data_creation_type'] must be '2' — “machine-learning model” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example:
column_config['machine_learning_model_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 33
machine learning column match
machine learning column match list_parameter

The list that maps model training variables to current project columns. Each item contains the variable name, selected column index, and categorical option conversion when needed; when every required input is mapped, the model receives the data layout it expects. Missing or incorrect mappings damage prediction quality or execution.

* Parameter relationships
Parameter: column_config['machine_learning_column_match']
Condition: column_config['manuel_data_creation_type'] must be '2' — “machine-learning model” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example: age → column index 2, gender → column index 5
column_config['machine_learning_column_match'] = [{'machine_learning_variable_name': 'age', 'machine_learning_selected_column_index': 2, 'machine_learning_options': []}, {'machine_learning_variable_name': 'gender', 'machine_learning_selected_column_index': 5, 'machine_learning_options': []}]
Parameter ID: 34
machine learning variable name
machine learning variable name text

The name of an input variable used during model training. When it exactly matches the model schema, the selected project column is bound to the correct input.

* Parameter relationships
Parameter: column_config['machine_learning_column_match'][0]['machine_learning_variable_name']
Condition: The related column_config['machine_learning_column_match'] list item must exist.
Reason and result: “machine learning variable name” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example:
column_config['machine_learning_column_match'][0]['machine_learning_variable_name'] = 'age'
Parameter ID: 35
machine learning selected column index
machine learning selected column index integer

This is the index of the project column that will provide data for a machine learning variable.

For example, if age data is to be retrieved from the third column, the column index would be 2. The user does not enter this value manually; it is assigned automatically when a selection is made from the list of columns displayed on the screen.

* Parameter relationships
Parameter: column_config['machine_learning_column_match'][0]['machine_learning_selected_column_index']
Condition: The related column_config['machine_learning_column_match'] list item must exist.
Reason and result: “machine learning selected column index” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example:
column_config['machine_learning_column_match'][0]['machine_learning_selected_column_index'] = 2
Parameter ID: 36
machine learning match options
machine learning match options textarea

When assigning a machine learning model, if the model inputs include categorical variables, the options for these categorical variables must also be mapped. This is a JSON list that maps the training group values ​​found in the categorical model inputs to the current options available in the project column.

For example, a value of '0' (representing 'female') used during training is linked to the 'female' option in the project. This value is generated automatically when a user makes a selection on the screen; the user is not expected to enter the JSON object manually.

* Parameter relationships
Parameter: column_config['machine_learning_column_match'][0]['machine_learning_options']
Condition: The related column_config['machine_learning_column_match'] list item must exist.
Reason and result: “machine learning match options” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example:
column_config['machine_learning_column_match'][0]['machine_learning_options'] = [{"group_val":0,"matched_option":{"value":"female"}}]
Parameter ID: 37
nlp layer type
nlp layer type select

NLP determines whether an expression identifier should be sought within the user-specific expression layer or the global expression layer. If "user" is selected, the system queries the user's own NLP entries; if "global" is selected, it queries the system-wide entries.

For instance, if a user trains and saves a model themselves via the NLP expression management module, this constitutes a user-specific expression model. Conversely, expression models provided globally by WisdomEra can be selected and used by any user, but they cannot be edited.

* Parameter relationships
Parameter: column_config['nlp_layer_type']
Condition: column_config['manuel_data_creation_type'] must be '3' — “NLP model” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Options and usage purposes
0 — user
Loads the phrase from the user-specific natural-language processing layer.
1 — global
Loads the phrase from the global natural-language processing layer.
Example:
column_config['nlp_layer_type'] = '0'
Parameter ID: 38
api variable
api variable list_parameter

This is a list that maps the variable names to be used in an algorithm's API request to the project's column indices. For each row, the value from the specified column is added to the API data under the defined API variable name. In the context of Wdigitalchannel customer campaign integration, this list is also used to prepare customer rows. When sending data from a row to an API other than Wdigitalchannel, manual API mapping is not strictly required, as the code section can be easily managed by the user who designs the API. However, since the Wdigitalchannel API structure is fixed, this list must be populated when using it. In particular, 'CustomerId' is mandatory, as the Wdigitalchannel application requires a value for 'CustomerId'.

* Parameter relationships
Parameter: column_config['api_variable']
Condition: column_config['manuel_data_creation_type'] must be '4' — “algorithm API” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Example: In this example, for any row where the algorithm produces a positive API output, the data from the column at index 0 (i.e., the first column) will be sent to the target API as the 'CustomerId'. column_config['api_variable'] = [{'key': 'CustomerId', 'col': '0'}].
Parameter ID: 39
api variable name
API variable name text

This is the key name of the field to be sent to the target algorithm API. It corresponds to the 'key' value in the API variable list. It is filled in manually by the user.

The system stores this value in the 'key' field within column_config['api_variable'][0]['key'] = '' .

* Parameter relationships
Parameter: column_config['api_variable'][0]['key']
Condition: The related column_config['api_variable'] list item must exist.
Reason and result: “api variable name” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example: column_config['api_variable'][0]['key'] = 'CustomerId'
Parameter ID: 40
api match column index
API-mapped column index text

This is the column index value of the row to be sent to the target algorithm API. It corresponds to the 'col' value in the API variable list. Assignments are made by selecting from a list of available columns.

The system stores this value within the 'key' section of the configuration, specifically as: column_config['api_variable'][0]['col'] = '' .

* Parameter relationships
Parameter: column_config['api_variable'][0]['col']
Condition: The related column_config['api_variable'] list item must exist.
Reason and result: “api match column index” is a child field of this list; it is populated only when the item exists and evaluated in that item context.
Example: column_config['api_variable'][0]['col'] = 3
Parameter ID: 41
nlp phrase name
NLP expression name text

Refers to the name of the NLP expression model when it is assigned to a column. It is not entered manually; it is assigned automatically upon selection from the list of NLP expression models.

* Parameter relationships
Parameter: column_config['nlp_phrase_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “nlp phrase name” is populated directly in its record context and is not enabled or disabled by another parameter selection.
Example: Get age value
column_config['nlp_phrase_name'] = ''
Parameter ID: 42
wdigitalchannel api
wdigitalchannel api select

Determines whether the algorithm API result should be used for transferring customer data to a Wdigitalchannel campaign, rather than being returned as a standard column result. If set to "yes," customer rows are prepared based on mapped API variables and sent to the Wdigitalchannel service along with the campaign ID.

* Parameter relationships
Parameter: column_config['wdigitalchannel_api']
Condition: column_config['manuel_data_creation_type'] must be '4' — “algorithm API” .
Reason and result: Populated only in the selected manual-column generation method and unused by other methods.
Options and usage
0 — no
Disables this behavior.
Parameter ID: 43
1 — yes
Enables this behavior.
Example: column_config['wdigitalchannel_api'] = '1'
wdigitalchannel campaign name
wdigitalchannel campaign name text

This is the name of the selected Wdigitalchannel campaign as displayed to the user. It is the campaign name that appears on the screen.

* Parameter relationships
Parameter: column_config['wdigitalchannel_campaign_name']
Condition: column_config['wdigitalchannel_api'] must be '1' — “yes” .
Reason and result: Manual data creation type must also be “algorithm API”; this stores the Wdigitalchannel campaign selection and is cleared when “no” is selected.
Example: column_config['wdigitalchannel_campaign_name'] = 'Vitamin B12 deficiency patient information'
Parameter ID: 44
wdigitalchannel campaign id
wdigitalchannel campaign ID text

The ID value of the selected Wdigitalchannel campaign. This is chosen by the user from the list of available Wdigitalchannel campaigns.

* Parameter relationships
Parameter: column_config['wdigitalchannel_campaign_id']
Condition: column_config['wdigitalchannel_api'] must be '1' — “yes” .
Reason and result: Manual data creation type must also be “algorithm API”; this stores the Wdigitalchannel campaign selection and is cleared when “no” is selected.
Example: column_config['wdigitalchannel_campaign_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 45
about
status
status select

Identifies the process lifecycle state. Continue allows data-preparation, manual-column, and algorithm flows to resume from saved progress; cancel causes execution to stop at control points; complete indicates normal completion. The active-process service treats continue records as running work.

* Parameter relationships
Parameter: process_config['status']
Condition: The related system record must exist.
Reason and result: “status” is not enabled by another user option; it is produced or updated by the system while processing.
Options and usage purposes
0 — cancel
Prevents the process from continuing at its control points.
1 — continue
Keeps the process active or resumable.
2 — complete
Indicates that the process completed normally.
Example: 1 — continue
wanalyzer project id
Wanalyzer project ID text

The project identification ID that links a process record to the relevant Wanalyzer project.

* Parameter relationships
Parameter: process_config['wanalyzer_project_id']
Condition: The related system record must exist.
Reason and result: “wanalyzer project id” is not enabled by another user option; it is produced or updated by the system while processing.
Example: bd513e04-d868-45d5-82d3-78ed0d2a7bef
process type
process type select

Classifies which Wanalyzer job the record tracks. Scheduler and resume code route data preparation, algorithm triggering, and manual data preprocessing to different worker flows; operations such as column recording, Excel upload, and project copying also create process records under their own types for tracking.

* Parameter relationships
Parameter: process_config['process_type']
Condition: The related system record must exist.
Reason and result: “process type” is not enabled by another user option; it is produced or updated by the system while processing.
Options and usage purposes
0 — data preparation
Tracks a Wtransfer or MSSQL data-preparation run.
1 — algorithm trigger
Tracks algorithm-column execution over dataset parts.
2 — manuel data preprocessing
Tracks manual-column calculation over dataset parts.
3 — column record
Process type used to track column recording or copying results.
4 — upload excel data
Tracks Excel upload and dataset-part creation results.
Example: data preparation
data update mode
data update mode select

Determines how the prepared data is applied to the existing dataset throughout the process. Options include: "delete and add" for a full refresh; "add only" to preserve existing data; "update and add" (upsert) to modify matching records while adding new ones; and "update only" to modify existing, matching records.

* Parameter relationships
Parameter: process_config['data_update_mode']
Condition: The related system record must exist.
Reason and result: “data update mode” is not enabled by another user option; it is produced or updated by the system while processing.
Options and use cases
0 — delete dataset and add new rows
Removes the existing dataset and adds the new results.
1 — add new rows without deleting or updating the dataset
Adds new rows without modifying the existing data.
2 — update dataset and add new rows
Updates matching records and adds new records.
3 — update dataset
Updates only the existing, matching records.
4 — calculate total count
Used when the calculation of the total number of data entries is triggered.
Example: 2 — update dataset and add new rows
start date
start date datetime

Timestamp recorded when the process is first created. Interval-based automatic scheduling adds the configured duration to this date from the latest process to calculate the next eligible time.

* Parameter relationships
Parameter: process_config['start_date']
Condition: The related system record must exist.
Reason and result: “start date” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 2026-10-25T09:30:00
end date
end date datetime

Records the time at which a process completes. Start and end together support examination of duration and normal completion.

* Parameter relationships
Parameter: process_config['end_date']
Condition: The related system record must exist.
Reason and result: “end date” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 2026-10-25T09:42:10
stop date
termination date datetime

Indicates the time of the cancellation or termination action.

* Parameter relationships
Parameter: process_config['stop_date']
Condition: The related system record must exist.
Reason and result: “stop date” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 2026-10-25T09:36:00
offset
last processed row number text

A progress value that stores the position of the row processed within the data source. In MSSQL and Wtransfer data querying processes, the offset value is updated after each successfully processed segment; if the ongoing process utilizes the same source, it can resume the next query from this position. Resetting this value to an earlier point may result in the same source rows being processed again.

* Parameter relationships
Parameter: process_config['offset']
Condition: The related system record must exist.
Reason and result: “offset” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 25000
location offset
location (current stage) text

This is a field maintained within the process record to track progress through the various stages (locations) defined in a Wtransfer data preparation map. The data preparation process in Wtransfer may be designed to ingest data from two distinct locations. Once the process begins at the first location and all associated queries are completed, it proceeds to the second location. This value is updated throughout the process, ensuring that if the system restarts, it can resume from the specific stage (location) where it was interrupted.

* Parameter relationships
Parameter: process_config['location_offset']
Condition: The related system record must exist.
Reason and result: “location offset” is not enabled by another user option; it is produced or updated by the system while processing.
Example: bd513e04-d868-45d5-82d3-78ed0d2a7bef
location server offset
current server location text

Stores the server location currently being processed within the Wtransfer workflow. When multiple servers are handled in a mapping operation, this value tracks which server stage the process is currently at.

For example, suppose there are 5 separate hospital servers defined in a database mapping configuration. If the system restarts while processing the second server, this value ensures that the process does not have to start over from the beginning; instead, it resumes queries from the second server.

* Parameter relationships
Parameter: process_config['location_server_offset']
Condition: The related system record must exist.
Reason and result: “location server offset” is not enabled by another user option; it is produced or updated by the system while processing.
Example: bd513e04-d868-45d5-82d3-78ed0d2a7bef
new row count
number of new rows integer

This is a cumulative counter of the new rows added throughout the data preparation process. For MSSQL data preparation, it records the total number of rows added. For Excel uploads, it records the number of rows in the loaded data frame.

* Parameter relationships
Parameter: process_config['new_row_count']
Condition: The related system record must exist.
Reason and result: “new row count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 100
dataset total count
total number of datasets integer

Indicates the number of dataset segments in a project. Algorithmic and manual column operations iterate through these dataset segments—from 1 up to this total—and verify completion once the current segment number reaches this value. The Excel download feature also uses this same counter to traverse all segments.

As the volume of data in a project grows, multiple datasets are generated, allowing for the storage of very large datasets within the system.

* Parameter relationships
Parameter: process_config['dataset_total_count']
Condition: The related system record must exist.
Reason and result: “dataset total count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 24
algorithm api trigger
trigger algorithm API select

The process of triggering algorithm columns can be initiated either following project data preparation or manually via the interface. When the algorithm-triggering step is reached, the rules associated with the algorithm columns are executed for each row, first determining whether the algorithm result is "true" or "false." Subsequently, if an API is defined for an algorithm column, that API can also be triggered. When configured within the project's automatic settings to "trigger algorithm columns," any API defined for an algorithm column will be triggered automatically.

In the case of manual triggering via the interface, the process can be executed to simply determine whether the algorithm result is "true" or "false"; alternatively, it can be configured to trigger a call to a defined API for rows where the result is "true."

If the process is initiated with an API trigger, it is recorded as "yes"; if the algorithm is triggered without an API call, it is recorded as "no."

* Parameter relationships
Parameter: process_config['algorithm_api_trigger']
Condition: The related system record must exist.
Reason and result: “algorithm api trigger” is not enabled by another user option; it is produced or updated by the system while processing.
Options and usage purposes
0 — no
Records the selection as "no" in the process log.
1 — yes
Records the selection as "yes" in the process log.
Example: 1 — yes
offset dataset no
dataset number (resume point) integer

Indicates the dataset segment where an algorithmic or manual column process was interrupted. When a process with an "in-progress" status is restarted, the code uses this value as the starting segment.

Upon restart, the application resumes from the specified dataset number.

* Parameter relationships
Parameter: process_config['offset_dataset_no']
Condition: The related system record must exist.
Reason and result: “offset dataset no” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 8
log
log textarea

Stores descriptions, error messages, or progress updates related to the process. Error logs, in particular, appear here when issues arise during operations.

* Parameter relationships
Parameter: process_config['log']
Condition: The related system record must exist.
Reason and result: “log” is not enabled by another user option; it is produced or updated by the system while processing.
Example: SQL query error.
positive algorithm count
number of positive algorithms integer

A counter for the number of rows that yielded a positive result during algorithm evaluation.

* Parameter relationships
Parameter: process_config['positive_algorithm_count']
Condition: The related system record must exist.
Reason and result: “positive algorithm count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 320
negative algorithm count
number of negative algorithms integer

A counter for the number of rows that yield a negative result during algorithm evaluation. Records for which the algorithm column rule evaluates to 'false' are added to this count.

* Parameter relationships
Parameter: process_config['negative_algorithm_count']
Condition: The related system record must exist.
Reason and result: “negative algorithm count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 1180
success api count
number of successful API calls integer

A counter for calls to the Algorithm API or Wdigitalchannel API that are recorded as successful. It is incremented whenever the service response is successful. Since only a positive algorithm result can generate a corresponding entry for an API call, this should be evaluated in conjunction with the positive counter.

* Parameter relationships
Parameter: process_config['success_api_count']
Condition: The related system record must exist.
Reason and result: “success api count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 300
unsuccess api count
number of failed API calls integer

This is a counter for calls to the Algorithm API or Wdigitalchannel API that have been recorded as errors. A service error code, a failed response, or an 'error' status returned by the executed API code can increment this counter. Error conditions are also logged within the individual cells. By examining the details of dataset cells where the algorithm is marked as successful but the API call is marked as failed, the root cause of the error can be identified.

* Parameter relationships
Parameter: process_config['unsuccess_api_count']
Condition: The related system record must exist.
Reason and result: “unsuccess api count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 20
column total count
total number of columns integer

The total number of columns in the project is stored here. When the number of columns changes, the latest process record is updated.

* Parameter relationships
Parameter: process_config['column_total_count']
Condition: The related system record must exist.
Reason and result: “column total count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 42
last information date
last update timestamp datetime

Indicates the last time the process updated its progress record. The active process service reads this timestamp to report the most recent update time for the record. Workflows update this timestamp as they process individual items. A timestamp that remains unchanged for an extended period serves as an operational indicator that the process might be stuck; however, this alone is not sufficient grounds for a cancellation decision.

* Parameter relationships
Parameter: process_config['last_information_date']
Condition: The related system record must exist.
Reason and result: “last information date” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 2026-10-25T09:40:15
triggered algorithm column id list
triggered algorithm column IDs textarea

Stores the IDs of algorithm columns triggered during the algorithm process as a comma-separated string. This record is used to track which algorithm columns have been processed within the scope of a given operation. The use of commas within the IDs themselves will disrupt the parsing of the list.

* Parameter relationships
Parameter: process_config['triggered_algorithm_column_id_list']
Condition: The related system record must exist.
Reason and result: “triggered algorithm column id list” is not enabled by another user option; it is produced or updated by the system while processing.
Example: column_id_1, column_id_2
last data preparation date
last data preparation date datetime

Indicates the timestamp for the most recent data preparation for the project.

* Parameter relationships
Parameter: process_config['last_data_preparation_date']
Condition: The related system record must exist.
Reason and result: “last data preparation date” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 2026-10-24T23:00:00
do last operations
perform final operations select

This selection determines whether final steps should be executed after data preparation is complete. It is set to "yes" when subsequent actions—such as triggering an algorithm or performing statistical analysis—are required once the data is prepared.

This parameter applies to manual triggers initiated via the interface. For projects that run automatically, the project's own settings take precedence. If the configuration specifies triggering statistics, they will be generated; if the algorithm is set to run automatically, it will be executed accordingly.

* Parameter relationships
Parameter: process_config['do_last_operations']
Condition: The related system record must exist.
Reason and result: “do last operations” is not enabled by another user option; it is produced or updated by the system while processing.
Options and usage
0 — no
Records the "no" selection in the process log.
1 — yes
Records the "yes" selection in the process log.
Example: 1 — yes
total data count
total data count integer

Wtransfer includes a mode for calculating the total number of data entries during data queries. When a trigger is executed using this mode, the total data count is recorded in this parameter.

* Parameter relationships
Parameter: process_config['total_data_count']
Condition: The related system record must exist.
Reason and result: “total data count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 50000
about
status
status select

Stores the status selection for a dataset component. By default, it is used in "active" mode within the system.

* Parameter relationships
Parameter: dataset_config['status']
Condition: The related system record must exist.
Reason and result: “status” is not enabled by another user option; it is produced or updated by the system while processing.
Options and intended use
0 — inactive
A value defined as inactive within the layer; the relevant read service will exclude records based on this value.
1 — active
The current status value, written directly by the code responsible for creating and updating the dataset.
Example: 1 — active
wanalyzer project id
wanalyzer project ID text

This is the project ID value that determines which project a dataset belongs to. It cannot be edited manually; it is assigned automatically by the system.

* Parameter relationships
Parameter: dataset_config['wanalyzer_project_id']
Condition: The related system record must exist.
Reason and result: “wanalyzer project id” is not enabled by another user option; it is produced or updated by the system while processing.
Example: bd513e04-d868-45d5-82d3-78ed0d2a7bef
row count
number of rows integer

It is the number of rows of the data in the data set.

* Parameter relationships
Parameter: dataset_config['row_count']
Condition: The related system record must exist.
Reason and result: “row count” is not enabled by another user option; it is produced or updated by the system while processing.
Example: 1000
dataset json
dataset json textarea

Stores the actual content of the dataset component as JSON text. The top-level `rows` array contains cell objects for each row, ordered by column; the `row_info` array, at the corresponding indices, contains tracking information such as the row number, source record ID, client ID, map, and server ID.

* Parameter relationships
Parameter: dataset_config['dataset_json']
Condition: The related system record must exist.
Reason and result: “dataset json” is not enabled by another user option; it is produced or updated by the system while processing.
Example: {"rows":[[{"manuel":{"list":[{"val":"42"}]}}]],"row_info":[{"no":1,"cl_id":"patient_1"}],"updated_at":"2026-10-25T09:30:00"}