Overview of WisdomEra documentation
WISDOMERA / DOCUMENTATION CENTER

WisdomEra application guides

Explore application-layer parameters, options, and operational relationships in one place, from data integration and preparation to statistics, machine learning, digital-channel operations, and server monitoring.

What does this documentation center provide?

Instead of merely listing field names, each guide explains why and how a process is affected when a parameter changes. Option tables, example values, layer relationships, and operational cautions verified in the code are presented together.

Language parity: The Turkish and English versions of the application guides carry the same scope. The buttons below open the page for the current language.
Application guides and their scope
WISDOMERA / APPLICATION GUIDES

Documentation directory

Select the application you need to access its layers, parameters, options, and verified runtime behavior.

Data integration

Wtransfer

Explains how to configure database maps, server connections, layers, and layer parameters. It covers SQL, column mapping, option mapping, the end-to-end transfer flow, and operational test tools.

  • DB Map and server connections
  • Layer and column configuration
  • SQL, mapping, and transfer flow
Open guide →
Data preparation

Wanalyzer

Explains Wanalyzer project settings, data sources, and scheduling; data-generation and transformation rules for project columns; data-preparation processes; and prepared dataset records.

  • Project and automatic-update settings
  • Column, function, and algorithm configuration
  • Process tracking and dataset records
Open guide →
Analytics and modeling

Wistats

Explains statistical-analysis and machine-learning definitions that operate on shared Wanalyzer datasets. The guide covers analysis and model processes, tests, metrics, result records, input combinations, and automatic-execution relationships.

  • Descriptive and comparative statistics
  • Machine-learning model definitions
  • Process, result, and performance metrics
Open guide →
Customer communication

Wdigitalchannel

Explains the digital-communication process from the campaign lifecycle through customer journeys and channel operations. Surveys, lead forms, agenda scheduling, channel design, permission checks, and delivery tracking are covered together.

  • Campaign, customer, and journey management
  • Channel operation and delivery tracking
  • Survey, lead form, agenda, and channel design
Open guide →
Infrastructure monitoring

Wamserver

Explains how to define server CPU, RAM, and disk monitoring together with MSSQL connection checks. It covers storing reports as charts or summary values, log generation, alert thresholds, and alert-email processes.

  • CPU, RAM, disk, and MSSQL checks
  • Chart and summary report records
  • Alert thresholds, records, and email status
Open guide →
Operational relationship between applications
WISDOMERA / PRODUCT RELATIONSHIPS

In which order should you use the guides?

Each application has an independent responsibility, but they complement one another across data, analysis, communication, and monitoring flows.

Wtransfer Obtains data from source systems and maps it to target layers.
Wanalyzer Prepares data for analysis and manages columns and datasets.
Wistats Runs analysis and modeling on the prepared dataset.
Wdigitalchannel Operates customer journeys and channels with analytical outputs.
Wamserver Monitors infrastructure resources, connections, and alerts.
Practical use: Read the main layer of the application you are working with first, then continue to the related process and result child layers. If a field depends on an identifier or dataset in another application, verify both sides of the relationship in the relevant guides.

Approach used in the guides

  • Technical layer and parameter identifiers are preserved in their data-model form.
  • The guides explain not only option names but also their effects on the process.
  • Example values demonstrate usage; production values must be verified against project configuration.
  • Behavior that cannot be verified in code is not presented as a guaranteed feature; current limitations are identified where applicable.