about
WISDOMERA / WDIGITALCHANNEL

WDIGITALCHANNEL Campaign

Defines execution, agenda, customer, and integration rules of a campaign.

Execution flow

For automatic execution, the campaign must be active and working, start type must be automatic, agenda time must be eligible, and an active channel design must exist. Success analysis requires additional follow-up, department, customer-persistence, and integration conditions.

status
status select

Activation status of the campaign. Active is one of the required conditions for automatic execution; customer addition and agenda-generation checks fail for a passive campaign. Active alone is not sufficient: lifecycle must be working, start type must be automatic, the agenda must be eligible, and at least one active channel design must exist.

* Parameter relationships
Parameter: campaign_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Excludes the campaign from automatic execution checks.
1 — active
Includes the campaign in active execution checks.
campaign_config['status'] = '1' Parameter ID: 0
life cycle
life cycle select

Determines the design and execution stage of the campaign. With working lifecycle, active automatic campaigns may run when agenda and channel conditions are also eligible; planning, designing, testing, maintenance initiated, or cancelled does not satisfy the production automatic-execution condition.

* Parameter relationships
Parameter: campaign_config['life_cycle']
Condition: No other parameter option is a prerequisite.
Reason and result: “life cycle” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — planning
Keeps the campaign in the planning lifecycle and does not satisfy the automatic-execution condition.
1 — designing
Keeps the campaign in the designing lifecycle and does not satisfy the automatic-execution condition.
2 — testing
Keeps the campaign in the testing lifecycle and does not satisfy the automatic-execution condition.
3 — maintenance initiated
Keeps the campaign in the maintenance initiated lifecycle and does not satisfy the automatic-execution condition.
4 — cancelled
Keeps the campaign in the cancelled lifecycle and does not satisfy the automatic-execution condition.
5 — working
Selects the working lifecycle required by automatic campaign flows.
campaign_config['life_cycle'] = '5'
Parameter ID: 1
contact details location
contact detail location select

Determines the source from which the customer's contact information—such as their phone number—is retrieved.

If "integration" is selected, two different integration setups can be configured:

  • Data can be retrieved from another target application service or database via a defined API.
  • Data can be retrieved using a "wtransfer" integration defined within the system.

If "customer transaction" is selected, the information is drawn from the customer journey and the customer record.

In this case, when the customer is sent to the record, contact information—such as phone number and email—must also be provided.

* Parameter relationships
Parameter: campaign_config['contact_details_location']
Condition: This parameter itself has no prerequisite parameter.
Reason and result: The “contact details location” selection determines where contact information is obtained. Option '0' means “integration” and makes campaign_config['contact_details_api_id'] available so the integration API can be selected. Option '1' means “customer transaction” and disables the API field.
Options and intended use
0 — integration
selects integration behavior.
1 — customer transaction
selects customer transaction behavior.
Example:
campaign_config['contact_details_location'] = '0' Parameter ID: 2
campaign name
campaign name text

This is the descriptive name used in the campaign management screens and reports. A clear name makes it easier to distinguish between campaigns created for the same product or target audience.

* Parameter relationships
Parameter: campaign_config['campaign_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['campaign_name'] = 'Information on Vitamin B12 deficiency' Parameter ID: 3
campaign short name
campaign short name text

Short name that may be used in compact areas and integration output. When the full name is long, a short but distinctive value keeps lists and external-system mappings readable.

* Parameter relationships
Parameter: campaign_config['campaign_short_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign short name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['campaign_short_name'] = 'VitaminB12Deficiency' Parameter ID: 4
save customer
save customer select

Determines whether customer and journey records should be permanently created.

Selecting "Yes" allows customer addition, automated scheduling, and success analysis workflows to generate records.

Selecting "No" means that the success analysis eligibility condition—specifically within the scheduler—will not be met. This option can be used when you wish to proceed with one-off channel action triggers without creating records; for instance, it is useful when sending tens of thousands of mobile notifications where maintaining a record of each is unnecessary.

* Parameter relationships
Parameter: campaign_config['save_customer']
Condition: No other parameter option is a prerequisite.
Reason and result: “save customer” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and use cases
0 — no
Disables the associated behavior.
1 — yes
Enables the associated behavior.
Example:
campaign_config['save_customer'] = '1' Parameter ID: 5
product code
product code text

Business code associating the campaign with its product. When populated, external systems and reporting processes can separate campaign results by product; the inspected main campaign-execution condition does not use this field as a direct gate.

It is used in installations carried out by WisdomEra products.

* Parameter relationships
Parameter: campaign_config['product_code']
Condition: No other parameter option is a prerequisite.
Reason and result: “product code” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['product_code'] = '123'
Parameter ID: 6
external campaign id
external campaign id text

Identifier of the campaign in an external system. The value is used for matching with external integrations; an empty or incorrect value may prevent external records from being associated with the correct campaign.

For instance, when customers who fill out lead forms on a website are stored in a separate lead system, they are recorded in that external system with an associated campaign ID. This ID value is then used to facilitate matching with the Wdigitalchannel platform.

* Parameter relationships
Parameter: campaign_config['external_campaign_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “external campaign id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['external_campaign_id'] = 'CRM-CAMP-4821'
Parameter ID: 7
genel bilgi
genel bilgi text

General description of the campaign purpose, audience, and operational scope. The field is stored in configuration but does not directly participate in the automatic eligibility decision; detailed content helps campaign operators interpret the rules consistently.

* Parameter relationships
Parameter: campaign_config['information']
Condition: No other parameter option is a prerequisite.
Reason and result: “genel bilgi” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['information'] = 'Sending surveys to discharged patients within 24 hours.'
Parameter ID: 8
start type
start type select

Determines whether the campaign starts manually or automatically. With automatic, customer and channel flow may start when status is active, lifecycle is working, the agenda is eligible, and the channel list is populated; manual does not satisfy this automatic condition.

* Parameter relationships
Parameter: campaign_config['start_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “start type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — manuel
Keeps the campaign in manual-start mode.
1 — auto
Enables automatic customer and channel flow when the agenda is eligible.
Example: 1 — otomatik / auto
Example:
campaign_config['start_type'] = '1'
Parameter ID: 9
minimum time (days) for customer re-acceptance
minimum time (days) for customer re-acceptance float

Minimum number of days that must pass after the previous start date before the same customer can be accepted into the campaign again. A new acceptance is rejected before the period expires; when empty, this day-based waiting check is not applied.

* Parameter relationships
Parameter: campaign_config['minimum_time_days_for_customer_re_acceptance']
Condition: No other parameter option is a prerequisite.
Reason and result: “minimum time (days) for customer re-acceptance” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: When it is not requested that they be included in the same campaign again within 30 days
campaign_config['minimum_time_days_for_customer_re_acceptance'] = ''
Parameter ID: 10
automatically deactivate the customer after x days
automatically deactivate the customer after x days select

This setting determines whether an active customer journey should be automatically deactivated after a specified number of days. If "Yes" is selected and the duration defined in the "automatically deactivate after (days)" field has elapsed—calculated by adding this duration to the start date—the journey is added to the deactivation list once the current date surpasses this threshold.

For example, consider a scenario where a customer journey is created when a customer is added to a campaign, but the servers are subsequently shut down. When the servers are brought back online 30 days later, the system would normally proceed to execute the channel-related action for that customer. However, if this parameter is set to "Yes" and a specific number of days is defined for automatic deactivation, the system will take this into account; if the specified time has passed, it will deactivate the journey and refrain from executing the action. This configuration must be designed specifically for the campaign in question.

* Parameter relationships
Parameter: campaign_config['auto_deactivate_customer']
Condition: This parameter itself has no prerequisite parameter.
Reason and result: The “automatically deactivate the customer after X days” selection determines whether a day value is needed. Option '1' means “yes” and enables campaign_config['auto_deactivate_day'] . Option '0' means “no” , so the day field is not evaluated.
Options and usage purposes
0 — no
Disables the related behavior.
1 — yes
Enables the related behavior.
Example:
campaign_config['automatically_deactivate_the_customer_after_x_days'] = '1'
Parameter ID: 11
after how many days will it automatically deactivate?
after how many days will it automatically deactivate? float

This is the number of days to be added to the trip start date for the purpose of automatic deactivation. This field is only effective when the 'automatically deactivate customer after x days' parameter is set to 'yes'; if left blank, the deactivation check will not be triggered.

* Parameter relationships
Parameter: campaign_config['auto_deactivate_day']
Condition: campaign_config['auto_deactivate_customer'] = '1' ; option '1' means “yes” .
Reason and result: When automatic deactivation is enabled, this field determines after how many days the customer becomes passive. If the controller is “no” ( '0' ), this field is hidden and not evaluated.
Example:
campaign_config['after_how_many_days_will_it_automatically_deactivate'] = '15'
Parameter ID: 12
campaign type
campaign type select

Determines whether the campaign is digital marketing, survey, or digital advertising. This selection controls which campaigns enter child flows such as survey-link generation and integration-based success analysis; the success scheduler accepts digital marketing and digital advertising types.

* Parameter relationships
Parameter: campaign_config['campaign_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — digital marketing
This model is employed when a business has access to customer contact details—such as phone numbers for SMS, email addresses, or identifiers for mobile push notifications—and wishes to reach out to those customers to provide information or share specific links. For instance, this approach is used in an algorithm designed to send informational messages to patients who have visited a hospital within the last month and were diagnosed with a B12 deficiency.
1 — survey
Selects the survey behavior. This is used when a survey link is sent to customers with a request for them to complete it. Once the survey type is selected, the survey questions for the campaign are also designed.
2 — digital advertising
It selects digital advertising behavior. This is a campaign model to be used in cases where contact channel information—such as SMS or email—is not available, and the customer has reached out via a website or a lead form.
Example:
campaign_config['campaign_type'] = '1'
Parameter ID: 13
customer success followup time (day)
customer success followup time (day) integer

This is the number of days following the date of the final channel interaction during which success is monitored. In success analysis, this duration is added to the date of the initial channel interaction (for example, the first SMS sent when a journey begins) to determine the end time and the timeframe for the query.

For instance, in the case of hospital visits, if a patient presents to the internal medicine department within 30 days, this is considered an indication that the target algorithm has succeeded.

* Parameter relationships
Parameter: campaign_config['customer_success_followup_time_day']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer success followup time (day)” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['customer_success_followup_time_day'] = '30'
Parameter ID: 14
select departrment
select departrment list_parameter

This is a list containing one or more departments to be included in the performance analysis. The scheduler which executes success analyze requires this list to be non-empty for the performance analysis to proceed.

When using the HospitalPatient database map provided by WisdomEra, these department ID values ​​are fixed, as they are mapped to the corresponding entities within the hospital system.

* Parameter relationships
Parameter: campaign_config['department_list']
Condition: No other parameter option is a prerequisite.
Reason and result: “select departrment” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['department_list'] = [{'department': '1'}]
Parameter ID: 15
department
department select

A clinical specialty or healthcare service area standardized by WisdomEra. Selected values define the scope of the achievement query.

For example, in cases where a patient has previously visited the emergency department with chest pain but no cardiac issue was detected, one could plan to send a message to this patient group three months later, stating: "If you continue to experience chest pain, please do not ignore it." This message serves as a reminder for the patient. Let us assume that if the patient visits the cardiology department following this message, the outcome is considered a success. In this scenario, by selecting "cardiology" from the department list, the success can be tracked through the hospital system. Success monitoring will continue for the duration specified in the campaign settings.

* Parameter relationships
Parameter: campaign_config['department_list'][0]['department']
Condition: The related campaign_config['department_list'] list item must exist.
Reason and result: “department” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and intended use
0 — emergency medicine
Includes the emergency medicine department in the scope of achievement tracking.
1 — oral and maxillofacial surgery
Includes the oral and maxillofacial surgery department in the scope of achievement tracking.
2 — dentistry
Includes the dentistry department in the scope of achievement tracking.
3 — oral and maxillofacial radiology
Includes the oral and maxillofacial radiology department in the scope of achievement tracking.
4 — pain medicine
Includes the pain medicine department in the scope of achievement tracking.
5 — family medicine
Includes the family medicine department in the scope of achievement tracking.
6 — anesthesiology and resuscitation
Includes the anesthesiology and resuscitation department in the scope of achievement tracking.
7 — general intensive care
Includes the general intensive care department in the scope of achievement tracking.
8 — nutrition and dietetics
Includes the nutrition and dietetics department in the scope of achievement tracking.
9 — neurosurgery
Includes the neurosurgery department in the scope of achievement tracking.
10 — neurosurgical intensive care
Includes the neurosurgical intensive care department in the scope of achievement tracking.
11 — surgical oncology
Includes the surgical oncology department in the scope of achievement tracking.
12 — surgical intensive care
Includes the surgical intensive care department in the scope of achievement tracking.
13 — pediatric emergency medicine
Includes the pediatric emergency medicine department in the scope of achievement tracking.
14 — child nutritional diseases
Includes the child nutritional diseases department in the scope of achievement tracking.
15 — pediatric neurosurgery
Includes the pediatric neurosurgery department in the scope of achievement tracking.
16 — pediatric kidney transplant
Includes the pediatric kidney transplant department in the scope of achievement tracking.
17 — pediatric surgery
Includes the pediatric surgery department in the scope of achievement tracking.
18 — pediatric endocrinology
Includes the pediatric endocrinology department in the scope of achievement tracking.
19 — pediatric infectious diseases
Includes the pediatric infectious diseases department in the scope of achievement tracking.
20 — pediatric gastroenterology
Includes the pediatric gastroenterology department in the scope of achievement tracking.
21 — child development
Includes the child development department in the scope of achievement tracking.
22 — pediatric chest diseases
Includes the pediatric chest diseases department in the scope of achievement tracking.
23 — pediatric hematology
Includes the pediatric hematology department in the scope of achievement tracking.
24 — pediatric allergy and immunology
Includes the pediatric allergy and immunology department in the scope of achievement tracking.
25 — pediatric cardiovascular surgery
Includes the pediatric cardiovascular surgery department in the scope of achievement tracking.
26 — pediatric liver transplantation
Includes the pediatric liver transplantation department in the scope of achievement tracking.
27 — pediatric cardiology
Includes the pediatric cardiology department in the scope of achievement tracking.
28 — pediatrics
Includes the pediatrics department in the scope of achievement tracking.
29 — pediatric urology
Includes the pediatric urology department in the scope of achievement tracking.
30 — pediatric nephrology
Includes the pediatric nephrology department in the scope of achievement tracking.
31 — pediatric neurology
Includes the pediatric neurology department in the scope of achievement tracking.
32 — pediatric oncology
Includes the pediatric oncology department in the scope of achievement tracking.
33 — pediatric orthopedics
Includes the pediatric orthopedics department in the scope of achievement tracking.
34 — pediatric psychiatry
Includes the pediatric psychiatry department in the scope of achievement tracking.
35 — pediatric rheumatology
Includes the pediatric rheumatology department in the scope of achievement tracking.
36 — dermatology
Includes the dermatology department in the scope of achievement tracking.
37 — speech and language therapy
Includes the speech and language therapy department in the scope of achievement tracking.
38 — diabetology
Includes the diabetology department in the scope of achievement tracking.
39 — diabetic foot
Includes the diabetic foot department in the scope of achievement tracking.
40 — hand surgery
Includes the hand surgery department in the scope of achievement tracking.
41 — cardiac electrophysiology
Includes the cardiac electrophysiology department in the scope of achievement tracking.
42 — endodontics
Includes the endodontics department in the scope of achievement tracking.
43 — endocrine surgery
Includes the endocrine surgery department in the scope of achievement tracking.
44 — endocrinology
Includes the endocrinology department in the scope of achievement tracking.
45 — infectious diseases intensive care
Includes the infectious diseases intensive care department in the scope of achievement tracking.
46 — infectious diseases
Includes the infectious diseases department in the scope of achievement tracking.
47 — occupational therapist
Includes the occupational therapist department in the scope of achievement tracking.
48 — home care
Includes the home care department in the scope of achievement tracking.
49 — physical therapy and rehabilitation
Includes the physical therapy and rehabilitation department in the scope of achievement tracking.
50 — gastroenterology
Includes the gastroenterology department in the scope of achievement tracking.
51 — gastrointestinal surgery
Includes the gastrointestinal surgery department in the scope of achievement tracking.
52 — general surgery
Includes the general surgery department in the scope of achievement tracking.
53 — medical genetics
Includes the medical genetics department in the scope of achievement tracking.
54 — geriatrics
Includes the geriatrics department in the scope of achievement tracking.
55 — interventional radiology
Includes the interventional radiology department in the scope of achievement tracking.
56 — thoracic surgery
Includes the thoracic surgery department in the scope of achievement tracking.
57 — respiratory intensive care
Includes the respiratory intensive care department in the scope of achievement tracking.
58 — pulmonology
Includes the pulmonology department in the scope of achievement tracking.
59 — ophthalmology
Includes the ophthalmology department in the scope of achievement tracking.
60 — hematology
Includes the hematology department in the scope of achievement tracking.
61 — internal medicine intensive care
Includes the internal medicine intensive care department in the scope of achievement tracking.
62 — internal medicine
Includes the internal medicine department in the scope of achievement tracking.
63 — immunology and allergic diseases
Includes the immunology and allergic diseases department in the scope of achievement tracking.
64 — stroke medicine
Includes the stroke medicine department in the scope of achievement tracking.
65 — stroke intensive care
Includes the stroke intensive care department in the scope of achievement tracking.
66 — obstetrics and gynecology
Includes the obstetrics and gynecology department in the scope of achievement tracking.
67 — cardiovascular surgery
Includes the cardiovascular surgery department in the scope of achievement tracking.
68 — cardiology
Includes the cardiology department in the scope of achievement tracking.
69 — otolaryngology
Includes the otolaryngology department in the scope of achievement tracking.
70 — coronary care unit
Includes the coronary care unit department in the scope of achievement tracking.
71 — cardiovascular surgical intensive care
Includes the cardiovascular surgical intensive care department in the scope of achievement tracking.
72 — medical oncology
Includes the medical oncology department in the scope of achievement tracking.
73 — breast surgery
Includes the breast surgery department in the scope of achievement tracking.
74 — nephrology
Includes the nephrology department in the scope of achievement tracking.
75 — nephrology intensive care
Includes the nephrology intensive care department in the scope of achievement tracking.
76 — neonatology
Includes the neonatology department in the scope of achievement tracking.
77 — neurology
Includes the neurology department in the scope of achievement tracking.
78 — neurological intensive care
Includes the neurological intensive care department in the scope of achievement tracking.
79 — neuroradiology
Includes the neuroradiology department in the scope of achievement tracking.
80 — nuclear medicine
Includes the nuclear medicine department in the scope of achievement tracking.
81 — obesity surgery
Includes the obesity surgery department in the scope of achievement tracking.
82 — audiology
Includes the audiology department in the scope of achievement tracking.
83 — spine health and scoliosis
Includes the spine health and scoliosis department in the scope of achievement tracking.
84 — transplantation
Includes the transplantation department in the scope of achievement tracking.
85 — orthodontics
Includes the orthodontics department in the scope of achievement tracking.
86 — orthopedics and traumatology
Includes the orthopedics and traumatology department in the scope of achievement tracking.
87 — orthopedic intensive care
Includes the orthopedic intensive care department in the scope of achievement tracking.
88 — palliative care clinic
Includes the palliative care clinic department in the scope of achievement tracking.
89 — palliative intensive care
Includes the palliative intensive care department in the scope of achievement tracking.
90 — movement disorders
Includes the movement disorders department in the scope of achievement tracking.
91 — pathology
Includes the pathology department in the scope of achievement tracking.
92 — pediatric dentistry
Includes the pediatric dentistry department in the scope of achievement tracking.
93 — perinatology
Includes the perinatology department in the scope of achievement tracking.
94 — periodontics
Includes the periodontics department in the scope of achievement tracking.
95 — plastic surgery
Includes the plastic surgery department in the scope of achievement tracking.
96 — prosthetic dental treatment
Includes the prosthetic dental treatment department in the scope of achievement tracking.
97 — psychiatry
Includes the psychiatry department in the scope of achievement tracking.
98 — psychology
Includes the psychology department in the scope of achievement tracking.
99 — radiation oncology
Includes the radiation oncology department in the scope of achievement tracking.
100 — radiology
Includes the radiology department in the scope of achievement tracking.
101 — restorative dental treatment
Includes the restorative dental treatment department in the scope of achievement tracking.
102 — rheumatology
Includes the rheumatology department in the scope of achievement tracking.
103 — sports medicine
Includes the sports medicine department in the scope of achievement tracking.
104 — medical pharmacology
Includes the medical pharmacology department in the scope of achievement tracking.
105 — medical microbiology
Includes the medical microbiology department in the scope of achievement tracking.
106 — reproductive medicine and IVF
Includes the reproductive medicine and IVF department in the scope of achievement tracking.
107 — urology
Includes the urology department in the scope of achievement tracking.
108 — sleep medicine
Includes the sleep medicine department in the scope of achievement tracking.
109 — wound unit
Includes the wound unit department in the scope of achievement tracking.
110 — neonatal intensive care
Includes the neonatal intensive care department in the scope of achievement tracking.
111 — pediatric sleep medicine
Includes the pediatric sleep medicine department in the scope of achievement tracking.
112 — pediatric intensive care
Includes the pediatric intensive care department in the scope of achievement tracking.
113 — pediatric metabolic diseases
Includes the pediatric metabolic diseases department in the scope of achievement tracking.
Example:
campaign_config['department_list'][0]['department'] = '68'
Parameter ID: 16
customer source
customer resource select

Classifies whether a customer registration originated from within WisdomEra or from a website. The source value is used for reporting and distinguishing data flows.

* Parameter relationships
Parameter: campaign_config['customer_source']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer source” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and intended use
0 — wisdomera
Indicates that the data was submitted via the 'wanalyzer' platform, which is part of the internal WisdomEra system.
1 — website
Indicates that the customer was registered via a website or an environment containing a lead form.
Example:
campaign_config['customer_source'] = '0'
Parameter ID: 17
advertisement type
ad type select

The "digital advertisement" concept refers to an interaction model where the customer engages via a website—external to your own database—or through a separate screen containing a lead form. In this scenario, the interaction with the customer can be captured as a lead form, or it may result in the direct scheduling of an appointment.

* Parameter relationships
Parameter: campaign_config['advertisement_type']
Condition: campaign_config['campaign_type'] = '2' ; option '2' means “digital advertising” .
Reason and result: Advertisement type is meaningful only for digital advertising campaigns. When this condition holds, the field is shown and the user may select '0' — “lead form” or '1' — “appointment” . For other campaign types, the field is hidden and is not populated by the user.
Options and use cases
0 — lead form
Select this option if the customer interaction occurs via a lead form (a form filled out by a customer who wishes to get in touch).
1 — appointment
Select "appointment" as the advertisement type if an appointment is being scheduled via a website or mobile application.
Example:
campaign_config['advertisement_type'] = '0'
Parameter ID: 18
agenda type
agenda type select

This is an agenda model that determines the days and times during which a campaign is active. It defines the timeframes in which channel-based actions—such as SMS, email, or mobile notifications—can be triggered for customers enrolled in the campaign.

* Parameter relationships
Parameter: campaign_config['agenda_type']
Condition: campaign_config['campaign_type'] must be '0' — “digital marketing” or '1' — “survey” .
Reason and result: Digital-marketing and survey campaigns use an agenda to determine the days and times when channel operations may run. For these two campaign types, agenda type and the day/time fields belonging to the selected agenda model are shown. With '2' — “digital advertising” , agenda type and its dependent fields are hidden.
Options and use cases
0 — all days and all times
1 — specific days and times
2 — all days and specific times
3 — select days and time ranges separately
4 — all days with separately selected time ranges
Example:
campaign_config['agenda_type'] = '0'
Parameter ID: 19
selected calendar hours for all days
selected agenda hours on all days checkbox

The timeframes during which channel-based actions (SMS, email, etc.) for the campaign are permitted are specified here.

* Parameter relationships
Parameter: campaign_config['selected_calendar_hours_for_all_days']
Condition: campaign_config['agenda_type'] must be '2' — “all days and specific times” .
Reason and result: These two agenda models use individual hour selections, so this field becomes available. Other agenda types use different time/range fields, and this parameter is not evaluated.
Options and intended uses
0 — 1
1 — 2
2 — 3
3 — 4
4 — 5
5 — 6
6 — 7
7 — 8
8 — 9
9 — 10
10 — 11
11 — 12
12 — 13
13 — 14
14 — 15
15 — 16
16 — 17
17 — 18
18 — 19
19 — 20
20 — 21
21 — 22
22 — 23
23 — 24
Represents the 24th hour, i.e., 00:00.
Example: If we want it to operate at 8:00 and 20:00, we specify it as follows:
campaign_config['selected_calendar_hours_for_all_days'] = ['7', '19']
Parameter ID: 20
selected agenda days
selected agenda days checkbox

This section specifies the appropriate day(s) for executing campaign channel actions (such as SMS, email, etc.).

* Parameter relationships
Parameter: campaign_config['selected_agenda_days']
Condition: campaign_config['agenda_type'] must be '3' — “select days and time ranges separately” .
Reason and result: These models require specific days to be selected. Agenda types that use all days do not evaluate this field.
Options and usage
0 — Monday
1 — Tuesday
2 — Wednesday
3 — Thursday
4 — Friday
5 — Saturday
6 — Sunday
Example: To enable operation on Tuesdays and Thursdays, make the following selection:
campaign_config['selected_agenda_days'] = ['1', '3']
Parameter ID: 21
all agenda days start hour
all agenda days start hour select

Specifies the time after which the campaign's channel actions (SMS, email, etc.) can be triggered.

For example, if SMS triggers in a campaign should occur between 11:00 and 17:00, an SMS for a newly arriving customer is triggered immediately if the current time falls within this window. For SMS triggers that require a second step or occur outside the permitted time window, an agenda entry is scheduled according to this window. The channel action is triggered when the scheduled time arrives.

* Parameter relationships
Parameter: campaign_config['all_agenda_days_start_hour']
Condition: campaign_config['agenda_type'] = '4' ; option '4' means “all days with separately selected time ranges” .
Reason and result: This model uses one common time range across all days, so its start hour comes from this field. For other agenda types, the field is hidden and not evaluated.
Options and usage
0 — 1
1 — 2
2 — 3
3 — 4
4 — 5
5 — 6
6 — 7
7 — 8
8 — 9
9 — 10
10 — 11
11 — 12
12 — 13
13 — 14
14 — 15
15 — 16
16 — 17
17 — 18
18 — 19
19 — 20
20 — 21
21 — 22
22 — 23
23 — 24
24 represents 00:00 (midnight).
Example:
campaign_config['all_agenda_days_start_hour'] = '10'
Parameter ID: 22
all agenda days end hour
all agenda days end hour select

Specifies the time before which the campaign's channel-based actions (SMS, email, etc.) can be triggered.

For example, if SMS triggers in a campaign should occur between 11:00 and 17:00, an SMS for a newly arriving customer is triggered immediately if the current time falls within this window. For SMS triggers that require a second step or occur outside the permitted time window, an agenda entry is scheduled according to this window. The channel action is triggered when the scheduled time arrives.

* Parameter relationships
Parameter: campaign_config['all_agenda_days_end_hour']
Condition: campaign_config['agenda_type'] = '4' ; option '4' means “all days with separately selected time ranges” .
Reason and result: This model uses one common time range across all days, so its end hour comes from this field. For other agenda types, the field is hidden and not evaluated.
Options and usage
0 — 1
1 — 2
2 — 3
3 — 4
4 — 5
5 — 6
6 — 7
7 — 8
8 — 9
9 — 10
10 — 11
11 — 12
12 — 13
13 — 14
14 — 15
15 — 16
16 — 17
17 — 18
18 — 19
19 — 20
20 — 21
21 — 22
22 — 23
23 — 24
24 represents 00:00 (midnight).
Example:
campaign_config['all_agenda_days_end_hour'] = '17'
Parameter ID: 22
selected agenda days start hour
selected agenda days start hour select

Specifies the time after which the campaign's channel action (SMS, email, etc.) can be triggered.

* Parameter relationships
Parameter: campaign_config['selected_agenda_days_start_hour']
Condition: campaign_config['agenda_type'] = '3' ; option '3' means “select days and time ranges separately” .
Reason and result: Determines the start of the time range applied to selected days. Other agenda types use different time fields, so this field is hidden and not evaluated.
Options and usage purposes
0 — 1
1 — 2
2 — 3
3 — 4
4 — 5
5 — 6
6 — 7
7 — 8
8 — 9
9 — 10
10 — 11
11 — 12
12 — 13
13 — 14
14 — 15
15 — 16
16 — 17
17 — 18
18 — 19
19 — 20
20 — 21
21 — 22
22 — 23
23 — 24
24 hour  means 00:00
Example:
campaign_config['selected_agenda_days_start_hour'] = '9'
Parameter ID: 24
selected agenda days end hour
selected agenda days end hour select

Specifies the time before which the campaign's channel action (SMS, email, etc.) can be triggered.

* Parameter relationships
Parameter: campaign_config['selected_agenda_days_end_hour']
Condition: campaign_config['agenda_type'] = '3' ; option '3' means “select days and time ranges separately” .
Reason and result: Determines the end of the time range applied to selected days. Other agenda types use different time fields, so this field is hidden and not evaluated.
Options and usage purposes
0 — 1
1 — 2
2 — 3
3 — 4
4 — 5
5 — 6
6 — 7
7 — 8
8 — 9
9 — 10
10 — 11
11 — 12
12 — 13
13 — 14
14 — 15
15 — 16
16 — 17
17 — 18
18 — 19
19 — 20
20 — 21
21 — 22
22 — 23
23 — 24
24 hour means 00:00.
Example:
campaign_config['selected_agenda_days_end_hour'] = '17'
Parameter ID: 25
agenda days selection
agenda days selection list_parameter

It is used to trigger a channel operation at specific times by specifying various days and hours together.

* Parameter relationships
Parameter: campaign_config['agenda_day_list']
Condition: campaign_config['agenda_type'] = '1'; the option '1' means “1 — specific days and times”.
Reason and result: It is used when it is necessary to specify different days and times together—for example, Mondays between 9:00 and 11:00, or Wednesdays at 13:00 and 17:00.
Example:
campaign_config['agenda_day_list'] = [{'selected_agenda_day': '', 'agenda_hour_type': '', 'selected_agenda_hours': [], 'day_start_hour': '', 'day_end_hour': ''}]
Parameter ID: 26
...selected agenda day
selected agenda day select

The specific day on which it is appropriate to carry out the campaign's channel-based actions (such as SMS, email, etc.) is indicated here.

* Parameter relationships
Parameter: campaign_config['agenda_day_list'][0]['selected_agenda_day']
Condition: The related campaign_config['agenda_day_list'] list item must exist.
Reason and result: “selected agenda day” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — monday
1 — tuesday
2 — wednesday
3 — thursday
4 — friday
5 — saturday
6 — sunday
Example:
campaign_config['agenda_day_list'][0]['selected_agenda_day'] = '0'
Parameter ID: 27
...agenda hour type
agenda hour type select

Determines how the hours within a selected day are to be taken into account.

* Parameter relationships
Parameter: campaign_config['agenda_day_list'][0]['agenda_hour_type']
Condition: The related campaign_config['agenda_day_list'] list item must exist.
Reason and result: “agenda hour type” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — all hours
Selects the all hours behavior.
1 — selected hours
Selects the selected hours behavior.
2 — hour range
Selects the hour range behavior.
Example:
campaign_config['agenda_day_list'][0]['agenda_hour_type'] = '2'
Parameter ID: 28
...selected agenda hours
selected agenda hours checkbox

The timeframes during which channel-based actions (SMS, email, etc.) for the campaign are permitted are specified here.

* Parameter relationships
Parameter: campaign_config['agenda_day_list'][0]['selected_agenda_hours']
Condition: The related campaign_config['agenda_day_list'] list item must exist.
Reason and result: “selected agenda hours” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — 1
1 — 2
2 — 3
3 — 4
4 — 5
5 — 6
6 — 7
7 — 8
8 — 9
9 — 10
10 — 11
11 — 12
12 — 13
13 — 14
14 — 15
15 — 16
16 — 17
17 — 18
18 — 19
19 — 20
20 — 21
21 — 22
22 — 23
23 — 24
24 means 00:00
Example: 9, 10, 11
Example:
campaign_config['agenda_day_list'][0]['selected_agenda_hours'] = []
Parameter ID: 29
...day start hour
day start hour select

Start boundary of the hour range in an agenda-day item. When hour type is hour range, both boundaries are compared inclusively; the stored value is converted to its actual hour by adding one in code.

* Parameter relationships
Parameter: campaign_config['agenda_day_list'][0]['day_start_hour']
Condition: The related campaign_config['agenda_day_list'] list item must exist.
Reason and result: “day start hour” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — 1
1 — 2
2 — 3
3 — 4
4 — 5
5 — 6
6 — 7
7 — 8
8 — 9
9 — 10
10 — 11
11 — 12
12 — 13
13 — 14
14 — 15
15 — 16
16 — 17
17 — 18
18 — 19
19 — 20
20 — 21
21 — 22
22 — 23
23 — 24
24 means 00:00
Example:
campaign_config['agenda_day_list'][0]['day_start_hour'] = '9'
Parameter ID: 30
...day end hour
day end hour select

Specifies the time before which the campaign's channel action (SMS, email, etc.) can be triggered.

* Parameter relationships
Parameter: campaign_config['agenda_day_list'][0]['day_end_hour']
Condition: The related campaign_config['agenda_day_list'] list item must exist.
Reason and result: “day end hour” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — 1
1 — 2
2 — 3
3 — 4
4 — 5
5 — 6
6 — 7
7 — 8
8 — 9
9 — 10
10 — 11
11 — 12
12 — 13
13 — 14
14 — 15
15 — 16
16 — 17
17 — 18
18 — 19
19 — 20
20 — 21
21 — 22
22 — 23
23 — 24
24 means 00:00
Example:
campaign_config['agenda_day_list'][0]['day_end_hour'] = '17'
Parameter ID: 31
wanalyzer project client id
wanalyzer project client id text

This is the ID value that associates the campaign with a Wanalyzer project. It is not mandatory.

* Parameter relationships
Parameter: campaign_config['wanalyzer_project_client_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “wanalyzer project client id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['wanalyzer_project_client_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 32
algorithm id
algorithm id text

This is an algorithm identifier stored for the purpose of associating it with a campaign. It is not a mandatory field and is not taken into account during programmatic processes.

* Parameter relationships
Parameter: campaign_config['algorithm_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “algorithm id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['algorithm_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 33
create date
create date datetime

Creation time information of the campaign record.

* Parameter relationships
Parameter: campaign_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['create_date'] = '2026-10-25T09:30:00'
Parameter ID: 34
update date
update date datetime

Update time information of the campaign record.

* Parameter relationships
Parameter: campaign_config['update_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “update date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T10:15:00
Example:
campaign_config['update_date'] = ''
Parameter ID: 35
wtransfer select api
wtransfer select api text

Wtransfer can be used for database integrations—such as retrieving customer contact information (phone numbers, email addresses, etc.)—or for connecting to a customer database during success analysis processes.

If no specific configuration is provided and the contact detail location parameter is set to 'integration,' the system retrieves contact information via its internal Wtransfer component. In most cases, this is done without needing to explicitly define a Wtransfer API.

If a configuration is provided, it indicates that contact information will be retrieved via an external, remote Wtransfer instance rather than the one internal to the system. This is an architecture that is rarely used.

* Parameter relationships
Parameter: campaign_config['wtransfer_select_api']
Condition: No other parameter option is a prerequisite.
Reason and result: “wtransfer select api” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['wtransfer_select_api'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 36
powerbi api campaign record id
powerbi api campaign record id text

With this API, the desired information from campaign settings can be saved as a list of campaigns into a Power BI reporting database.

Wdigitalchannel database content—including campaigns, details of initiated customer journeys, success analyses, and operational data related to these journeys—can be exported to a target Power BI MSSQL database upon request. This serves as an additional feature for users who wish to leverage this Power BI reporting structure.

Users can configure an API for Power BI, ensuring that data updates triggered by specific events are automatically propagated to the corresponding Power BI database.

The User/API management screen provides template API models that can be utilized for the Power BI framework.

* Parameter relationships
Parameter: campaign_config['powerbi_api_campaign_record_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “powerbi api campaign record id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['powerbi_api_campaign_record_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 37
survey link create type
survey link create type select

Determines whether the survey link is generated by Wdigitalchannel or by an external user application programming interface (API). If Wdigitalchannel is selected, an internal survey link is prepared; if the other survey link option is chosen, the API code registered in parameter number 39, 'other survey link API,' is executed.

* Parameter relationships
Parameter: campaign_config['survey_link_create_type']
Condition: This parameter itself has no prerequisite parameter.
Reason and result: Determines the survey-link source. With '0' — “WDC survey link” , Wdigitalchannel generates the link. With '1' — “other survey link” , campaign_config['other_survey_link_api'] becomes available so an external API can be selected.
Options and usage purposes
0 — wdc survey link
The `wdigitalchannel` platform manages survey link behavior. Survey links are processed through a survey registration service integrated into the `wdigitalchannel` application. Within this framework, campaign-specific survey questions can be designed directly via the `wdigitalchannel` interface. In the campaign configuration screen, the system automatically generates HTML code for the survey; this code is then configured with the appropriate URL and deployed on a server. When a customer clicks the link provided in a message, it opens this HTML-based survey application.
1 — other survey link
The system selects the behavior associated with the "other survey" link. The survey registration screen and the actual registrations are handled within a separate survey system. Records generated in that survey system are then transmitted to the Wdigitalchannel platform via an API. Once the survey system notifies Wdigitalchannel that a submission has been successfully completed, no further channel-related actions are triggered—even if a failure were to occur, no re-triggering takes place. Consequently, success outcomes and reports can also be generated within the Wdigitalchannel environment.
Example:
campaign_config['survey_link_create_type'] = '0'
Parameter ID: 38
other survey link api
other survey link api text

Wdigitalchannel uses a user API ID to generate external survey links.

The survey registration screen and the actual survey records are managed within a separate survey system. Data from this system is then transmitted to Wdigitalchannel via an API. When the survey system notifies Wdigitalchannel that a survey has been successfully completed, no further "channel" (trigger/re-engagement) actions are initiated—ensuring that such actions are only triggered in the event of a failure. Consequently, success outcomes and reports can also be generated within the Wdigitalchannel platform.

* Parameter relationships
Parameter: campaign_config['other_survey_link_api']
Condition: campaign_config['survey_link_create_type'] = '1' ; option '1' means “other survey link” .
Reason and result: When an external system will generate the survey link, this field selects the API to execute. With “WDC survey link” ( '0' ), the field is hidden and not evaluated.
Example:
campaign_config['other_survey_link_api'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 39
success analyze with integration
success analysis with integration select

Once channel actions—such as sending an SMS—have been executed for a customer enrolled in a campaign, a background scheduler within the `wdigitalchannel` system determines whether the targeted success criteria have been met, based on data from an integrated system.

For instance, a patient visiting a specific hospital department can be defined as a "success." Suppose there is a 15-day interval between the first and second scheduled SMS messages. If the patient visits the targeted hospital department on the 10th day following the first SMS, the system will not trigger the second SMS on the 15th day.

Success analysis process:

A "channel action journey" is initiated for customers enrolled in a campaign.

This journey follows the sequence of channel steps defined in the campaign’s channel design—for example, an initial SMS followed by a second SMS.

When an SMS channel action is triggered for a customer, and the "success analysis" parameter is enabled, a background scheduler performs an evaluation (typically once a day). Because this analysis can run concurrently for all customers, a fixed cycle duration cannot be specified; it depends on factors such as system resources and customer volume.

Once the success criterion is met, the customer’s journey is set to an inactive state.

Consequently, when the 15th day arrives—the scheduled time for the next action—the second SMS is not triggered.

* Parameter relationships
Parameter: campaign_config['success_analyze_with_integration']
Condition: This parameter has no prerequisites in terms of other parameters.
Cause and effect: It controls the visibility of the success analysis API field. In the current form configuration, selecting '0' (“no”) enables the campaign_config['success_analyze_api_id'] field, while selecting '1' (“yes”) disables this API field.
Options and intended uses
0 — no
1 — yes
Example:
campaign_config['success_analyze_with_integration'] = '1'
Parametre ID: 40
username
username text

It is the username that creates the campaign registration.

* Parameter relationships
Parameter: campaign_config['username']
Condition: No other parameter option is a prerequisite.
Reason and result: “username” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: campaign.operator
Example:
campaign_config['username'] = ''
Parameter ID: 41
survey validity period hours
survey validity period hours integer

Determines the number of hours for which the generated survey link remains valid.

For example, if a survey link is generated and sent via SMS with a validity period of 24 hours, the customer will be unable to access the survey if they attempt to open it after those 24 hours have passed.

* Parameter relationships
Parameter: campaign_config['survey_validity_period_hours']
Condition: campaign_config['campaign_type'] = '1'; the option '1' signifies "survey."
Cause and effect: The "survey validity period (hours)" parameter is populated and evaluated directly within its own registration context; it is not toggled on or off based on the selection of any other parameter.
Example:
campaign_config['survey_validity_period_hours'] = '24'
Parameter ID: 42
powerbi api channel operastion record id
powerbi api channel operastion record id text

With this API, specific operational details—such as those related to channel-based triggers like SMS sent during a customer journey—can be saved into a Power BI reporting database as a list of campaigns.

Data from the Wdigitalchannel database—including campaigns, details of initiated customer journeys, success analyses, and operations related to these journeys—can be exported to a target Power BI MSSQL database upon request. This serves as an additional feature for users who wish to utilize this Power BI reporting structure.

Users can configure an API for Power BI; subsequently, data updates triggered by specific events will be automatically reflected in the corresponding Power BI database.

The User/API management screen provides template API models that can be used for Power BI integration.

* Parameter relationships
Parameter: campaign_config['powerbi_api_channel_operation_record_id']']
Condition: No other parameter option is a prerequisite.
Reason and result: “powerbi api channel operastion record id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['powerbi_api_channel_operation_record_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 43
powerbi api journey record id
powerbi api journey record id text

Through this API, details regarding the channel journey process—including information derived from success analysis outputs—can be saved to a Power BI reporting database.

The contents of the 'Wdigitalchannel' database—such as campaigns, initiated customer journey details, success analyses, and operations related to customer journeys—can be exported to a target Power BI MSSQL database upon request. This serves as an additional feature for users who wish to utilize this Power BI reporting structure.

Users can configure an API, and subsequently, data updates triggered by specific events will be automatically propagated to the corresponding Power BI database.

The User/API management screen provides template API models that can be used for Power BI integration.

* Parameter relationships
Parameter: campaign_config['powerbi_api_journey_record_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “powerbi api journey record id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
campaign_config['powerbi_api_journey_record_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 44
success analyze completed journeys
success analyze completed journeys select

In standard success analysis, the analysis of a customer journey begins after the first channel interaction is triggered. This process continues for the number of days specified by the "customer success tracking duration (days)" parameter in the campaign settings. Once this period concludes, no further success analysis is performed for that specific journey.

However, if updates occur in the integration databases, or if there is a need to refresh success analyses—for instance, by modifying the aforementioned duration parameter for a campaign—the "success analysis for completed journeys" parameter can be set to "yes."

This allows for updates to be applied to historical records as well. Once the success analysis for these past records has been updated, this parameter can be set back to "no."

* Parameter relationships
Parameter: campaign_config['success_analyze_completed_journeys']
Condition: Populated if campaign_config['success_analyze_with_integration'] = '1'; '1' signifies 'yes'.
Reason and result: “success analyze completed journeys” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — no
1 — yes
Example:
campaign_config['success_analyze_completed_journeys'] = '1'
Parameter ID: 45
contact details api id
contact details api id text

This is the ID value of the API registration used to retrieve contact details specifically for a campaign. There are two architectural workflows for retrieving contact information via integration:

- Utilizing the `HospitalPatient` database map within the internal `Wtransfer` system. If this parameter is left empty, the system defaults to using the `Wtransfer` instance configured internally. It must be ensured that `HospitalPatient` is also used on the `Wanalyzer` side, as the entire system requires consistent ID values ​​across all its components.

- Connecting an API created by the user. This API can, for instance, retrieve contact information directly from an MSSQL table. In this scenario, the custom-created API is used, and no data queries are performed through `Wtransfer`.

* Parameter relationships
Parameter: campaign_config['contact_details_api_id']
Condition: campaign_config['contact_details_location'] = '0' ; option '0' means “integration” .
Reason and result: When contact details come from an integration, this field selects the user API record to use. With “customer transaction” ( '1' ), the field is hidden and not evaluated.
Example:
campaign_config['contact_details_api_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 46
success analyze api id
success analyze api id text

Success analysis can be performed automatically via Wtransfer using the 'HospitalPatient' database map. Alternatively, success outcomes can be queried by configuring an additional environment—specifically MSSQL—within the API user settings. These outcomes will then be recorded in the customer journey.

* Parameter relationships
Parameter: campaign_config['success_analyze_api_id']
Condition: campaign_config['success_analyze_with_integration'] = '0' ; in the current option definition, '0' means “no” .
Reason and result: The current form-visibility logic enables selection of the success-analysis API for this value. With “yes” ( '1' ), the field is hidden. This mapping is stated explicitly because it appears counterintuitive relative to the option label.
Example:
campaign_config['success_analyze_api_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 47
powerbi api journey success record id
powerbi api journey success record id text

Identifier field designated for the Power BI journey-success record. Parameter 48 is not wired in inspected campaign new, edit, get, CampaignConfig, or execution code; therefore it must not be presented as saved or executed and must not be treated as operational until implementation is completed.

* Parameter relationships
Parameter: campaign_config['powerbi_api_journey_success_record_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “powerbi api journey success record id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: powerbi-journey-success-api-id
Example:
campaign_config['powerbi_api_journey_success_record_id'] = ''
Parameter ID: 48
about
WISDOMERA / WDIGITALCHANNEL

Campaign / Customer

It tracks the customer's persistent unique record within the campaign and the time of their re-entry.

Customer flow

A new customer is stored as active. When the same customer arrives again, the campaign waiting period is added to the last process start; after expiry, the record is updated and a new journey is created.

The unique customer ID (CustomerId) for a customer record is transmitted via the service. This allows the customer ID to be recorded uniquely for the campaign.

A unique customer record is created. For each customer, new channel-based interaction journeys can be initiated under a campaign.
status
status select

A campaign represents the active status of a customer registration. When a new customer is accepted, the record is created with an "active" status; similarly, when an existing customer is re-accepted, the resulting record also carries an "active" status. The value taken into account for customer triggers is the status parameter associated with the journey data.

* Parameter relationships
Parameter: customer_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
It can be set to inactive to represent general information about a customer. This does not affect the journey processes that trigger channel actions. The status parameter of the journey layer is taken into account when triggering channel actions.
1 — active
Active value used for newly accepted and re-accepted customer records.
Example:
customer_config['status'] = '1'
Parameter ID: 0
campaign id
campaign id text

This is the ID value for the Wdigitalchannel campaign to which a customer record belongs. The relevant campaign client ID value is automatically added within the customer registration service.

* Parameter relationships
Parameter: customer_config['campaign_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
customer_config['campaign_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 1
customer id
customer id text

This is a unique ID value that distinguishes a customer from other customers within a campaign. When a customer record is submitted, the CustomerId value is assigned to this parameter.

* Parameter relationships
Parameter: customer_config['customer_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
customer_config['customer_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 2
last customer process start date
last customer process start date datetime

The start time of the customer's most recently accepted journey action within a campaign serves as the reference point. The date on which a previously added customer becomes eligible for re-acceptance is calculated by adding a specified number of days to this timestamp.

For instance, suppose the campaign settings define the 'minimum time (in days) for customer re-acceptance' (`campaign_config['minimum_time_days_for_customer_re_acceptance']`) as 30. In this scenario, a customer becomes eligible for re-acceptance into the campaign once 30 days have elapsed since the 'start date of the customer's last action' recorded in their profile. This algorithm accounts for the possibility that the same customer might be re-identified by audience segmentation systems, such as WisdomEra Wanalyzer. If a customer were to be included in the same target audience again—for example, only 10 days later—this temporal algorithm, implemented within Wdigitalchannel, prevents the redundant re-initiation of customer journey actions.

* Parameter relationships
Parameter: customer_config['last_customer_process_start_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “last customer process start date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
customer_config['last_customer_process_start_date'] = '2026-10-25T09:30:00'
Parameter ID: 3
create date
create date datetime

A "campaign" refers to the point in time when a customer record is first created. The system automatically logs this during the customer registration process. It is used for informational purposes and is not utilized in any channel-based transaction-triggering algorithms.

* Parameter relationships
Parameter: customer_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
customer_config['create_date'] = '2026-10-01T08:15:00'
Parameter ID: 4
update date
update date datetime

This refers to the point in time when an existing customer's registration is renewed, following their fulfillment of the re-acceptance criteria. The system records this automatically during the customer registration process. It is used for informational purposes only and is not utilized in any channel-based transaction-triggering algorithms.

* Parameter relationships
Parameter: customer_config['update_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “update date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
customer_config['update_date'] = '2026-10-25T09:30:00'
Parameter ID: 5
passived date
passived date datetime

This field is defined to store the timestamp when a customer record is set to an inactive status. In the system, transaction controls for active channels are processed via the customer journey layer. This layer is designed to include a "date of deactivation" parameter, which can be utilized whenever such information is required.

* Parameter relationships
Parameter: customer_config['passived_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “passived date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
customer_config['passived_date'] = '2026-11-10T12:00:00'
Parameter ID: 6
about
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Customer / Journey

It tracks a customer’s progression across channels, their schedule, achievements, clicks, and the context of communications within a single campaign journey. This data initiates the channel-based journey process. Multiple such journeys can be initiated for a single customer.

It is referred to as a "journey" because, throughout the process, various channel-based actions can be triggered at specified time intervals. For instance, a campaign design might be configured to send an SMS, followed by a second SMS 15 days later—thereby setting the channel-based journey in motion.

Journey flow

When a customer record is submitted to a campaign, the customer profile is updated—either by re-registering them (if the re-registration date criteria are met) or by creating a new entry if they are a new customer. Simultaneously, a new "journey" record is generated.

The status of this new record begins as "active," with its success status set to "in progress."

If the campaign is configured for automatic mode, the system immediately triggers the designated channel action, provided the current time aligns with the schedule defined for that channel. If the current time does not fall within the scheduled window, the task is queued in the background according to the campaign’s hourly schedule; it is then triggered automatically once the scheduled time arrives.

The journey data contains several key parameter groups.

Contact details—such as phone numbers and email addresses—to be used for customer interactions are stored within this layer.

Permissions related to communication are also recorded as part of the journey data. The channel-triggering permission rules defined for the campaign (within the channel design layer) are evaluated based on these parameters. For instance, consider a campaign with two distinct channel designs: the first might involve sending an SMS to individuals who have provided SMS consent, while the second might involve sending a mobile notification without requiring specific consent. The system identifies the first applicable option and executes the corresponding channel action, using the permission settings stored within the journey data.

Furthermore, the journey data is updated to track the success of the process. For example, if the campaign settings define an appointment with the Internal Medicine department as a "success," the system will update the journey data to reflect the specific appointment ID, the department visited, and the physician consulted once that success criterion is met. Thus, these success outcomes can be viewed and examined on the report screens. It is possible to see what kind of success was achieved in each campaign.

Customer journey data can also be exported to a desired Power BI MSSQL environment via an API integration.
status
status select

Indicates whether a journey record will participate in the processing cycle. A new journey is created in an "active" state. If no suitable channel can be found, the customer is deceased, contact information is missing, or the channel flow terminates the journey, it is set to an "inactive" state, and the date of this transition is recorded.

* Parameter relationships
Parameter: journey_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Removes the journey from active channel processing.
1 — active
Includes the journey in active processing.
Example:
journey_config['status'] = '0'
Parameter ID: 0
customer id
customer id text

This is the ID of the customer to whom the journey belongs. It is the same value as the customer ID at the customer layer. It is recorded for relational data purposes.

* Parameter relationships
Parameter: journey_config['customer_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
journey_config['customer_id'] = '123'
Parameter ID: 1
passived date
passived date datetime

This is the time value recorded when the journey is set to a passive state.

* Parameter relationships
Parameter: journey_config['passived_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “passived date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
journey_config['passived_date'] = '2026-10-25T09:30:00'
Parameter ID: 2
success status
success status select

Tracks the overall success result of the journey. The record starts as `continue`; after success analysis evaluates the campaign’s primary and secondary success rules, it changes the result to `success` or `unsuccess`. This field is separate from channel step status: campaign success is analyzed independently even if channel delivery has completed.

* Parameter relationships
Parameter: journey_config['success_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “success status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — continue
The first trip is initiated as a continuation.
1 — success
This value is selected when success is achieved following the triggering of a channel action. For example, receiving an application from a targeted department within 30 days could be considered a success.
2 — unsuccess
This value is selected when success is not achieved within the targeted timeframe.
Example:
journey_config['success_status'] = '0'
Parameter ID: 3
success channel type
success channel type select

The communication channel associated with a success is recorded.

For instance, consider a journey consisting of three channel steps: SMS, mobile notification, and email. If a success occurs following a mobile notification, that mobile notification is recorded as the successful channel step. Consequently, reports on the specific channel steps that lead to success enable the effective management of targeted customer interactions.

* Parameter relationships
Parameter: journey_config['success_channel_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “success channel type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — sms
1 — push notification
2 — ivr
3 — mail
4 — phone call
Example:
journey_config['success_channel_type'] = '0'
Parameter ID: 4
channel step status
channel step status select

This is the progress status of the journey within the campaign channel stages.

* Parameter relationships
Parameter: journey_config['channel_step_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “channel step status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — continue
When a journey is first recorded, it is saved with the type `in progress`.
1 — complete
Once the channel steps are completed, they are marked as finished.
2 — not complete
Example:
journey_config['channel_step_status'] = '0'
Parameter ID: 5
selected campaign channel setting id
selected campaign channel setting id text

This is the ID value of the campaign channel configuration record selected for a journey. Channel design settings are saved within campaigns; in some cases, multiple channel designs may be stored, as the channel design process incorporates decision-making logic based on various algorithms. For instance, the system might be configured to select a specific channel design based on a customer's nationality or their consent status for receiving SMS messages. Therefore, when a channel operation is initiated for a journey, the system first determines which channel design is appropriate for the specific customer, and the ID of that chosen channel design is stored here.

* Parameter relationships
Parameter: journey_config['selected_campaign_channel_setting_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “selected campaign channel setting id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
journey_config['selected_campaign_channel_setting_id'] = 'bd513e04-d868-45d5-82d3-78ed0d2a7bef'
Parameter ID: 6
start date
start date datetime

This refers to the date at the time a customer record is created. It is maintained for general informational purposes.

* Parameter relationships
Parameter: journey_config['start_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “start date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
journey_config['start_date'] = '2026-10-25T09:30:00'
Parameter ID: 7
firstname
firstname text

This is the customer's name. It is not mandatory.

* Parameter relationships
Parameter: journey_config['firstname']
Condition: No other parameter option is a prerequisite.
Reason and result: “firstname” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
journey_config['firstname'] = 'john'
Parameter ID: 8
lastname
lastname text

This is the customer's surname. It is not mandatory.

* Parameter relationships
Parameter: journey_config['lastname']
Condition: No other parameter option is a prerequisite.
Reason and result: “lastname” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
journey_config['lastname'] = 'xyz'
Parameter ID: 9
institution name
institution name text

This is the name of the organization with which the customer is associated. It can be used for informational and reporting purposes.

* Parameter relationships
Parameter: journey_config['institution_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “institution name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
journey_config['institution_name'] = 'Abc hospital'
Parameter ID: 10
institution code
institution code text

This is the code for the institution with which the customer is affiliated. An institution code is a short identifier assigned to an organization, consisting of English characters with no spaces. For example, for "Istanbul Abc Hospital," a code such as "IstAbc" or "ABC" could be used. This is particularly helpful when dealing with multiple institutions, as it makes management reports much easier to interpret.

This code must be provided when creating a customer record, as it is used throughout all reporting processes.

* Parameter relationships
Parameter: journey_config['institution_code']
Condition: No other parameter option is a prerequisite.
Reason and result: “institution code” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 11-example
Example:
journey_config['institution_code'] = ''
Parameter ID: 11
institution department name
institution department name text

This refers to the customer's department within their organization.

It is not mandatory. Providing department information allows for the generation of department-specific reports.

For instance, in survey campaigns, if the department is specified while recording the customer journey, the resulting journey and success reports can be broken down by department—for example, showing a 35% survey completion rate for Department A and a 15% completion rate for Department B. Similarly, in digital marketing-oriented application campaigns, when an application is received from a targeted department, that department name is captured as a parameter within the customer journey. This enables the generation of reports on successful applications categorized by department.

* Parameter relationships
Parameter: journey_config['institution_department_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “institution department name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example:
journey_config['institution_department_name'] = 'Internal Medicine'
Parameter ID: 12
nation language
Nationality language select

Language code used when sending content to the customer.

When sending data via the customer registration service, it is submitted using the variable name 'NationLanguage'.

customer_rows = [{'NationLanguage': 'TR', 'CustomerId': '123'}]

* Parameter relationships
Parameter: journey_config['nation_language']
Condition: No other parameter selection is required.
Behavior: “Nationality language” kendi kayıt bağlamında doğrudan doldurulur ve değerlendirilir; başka bir parametrenin seçimine göre açılıp kapanmaz.
Options and languages
0 — TR
Turkish
1 — AZ
Azerbaijani
2 — EN
English
3 — FA
Persian
4 — DE
German
5 — CA
Catalan
6 — PT
Portuguese
7 — ES
Spanish
8 — SQ
Albanian
9 — NL
Dutch
10 — TKL
Definition requires verification
11 — AR
Arabic
12 — BN
Bengali
13 — BE
Belarusian
14 — FR
French
15 — BS
Bosnian
16 — MS
Malay
17 — BG
Bulgarian
18 — DZ
Dzongkha
19 — CS
Czech
20 — ZH
Chinese
21 — DA
Danish
22 — ID
Indonesian
23 — TI
Tigrinya
24 — HY
Armenian
25 — ET
Estonian
26 — AM
Amharic
27 — FO
Faroese
28 — FI
Finnish
29 — KL
Greenlandic
30 — KO
Korean
31 — KA
Georgian
32 — HR
Croatian
33 — HI
Hindi
34 — HE
Hebrew
35 — SV
Swedish
36 — IT
Italian
37 — IS
Icelandic
38 — JA
Japanese
39 — KM
Khmer
40 — KK
Kazakh
41 — EL
Greek
42 — KY
Kyrgyz
43 — LO
Lao
44 — LV
Latvian
45 — LT
Lithuanian
46 — LB
Luxembourgish
47 — HU
Hungarian
48 — MG
Malagasy
49 — MK
Macedonian
50 — DV
Dhivehi
51 — MT
Maltese
52 — MN
Mongolian
53 — RO
Romanian
54 — NE
Nepali
55 — NO
Norwegian
56 — UZ
Uzbek
57 — UR
Urdu
58 — PL
Polish
59 — RW
Kinyarwanda
60 — RU
Russian
61 — SR
Serbian
62 — SK
Slovak
63 — SL
Krio (Sierra Leone Creole)
64 — SI
Sinhala
65 — SW
Swahili
66 — TH
Thai
67 — TO
Tongan
68 — TVL
Definition requires verification
69 — TK
Turkmen
70 — UK
Ukrainian
71 — BI
Bislama
72 — VI
Vietnamese
73 — TG
Tajik
74 — SO
Somali
75 — MY
Burmese
76 —
Unspecified
77 — NIU
Niuean
78 — SM
Samoan
Example:
journey_config['nation_language'] = '0'
Parameter ID: 13
country phone code + gsm
country phone code + gsm text

The combined contact value containing the country calling code and GSM number. Customer-acceptance code writes the source `PhoneNumber` field here; phone-based channels can use it when they require the full number, while the separate parts are also stored in parameters 15 and 16.

* Parameter relationships
Parameter: journey_config['country_phone_code_gsm']
Condition: No other parameter option is a prerequisite.
Reason and result: “country phone code + gsm” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 14-example
Example:
journey_config['country_phone_code_gsm'] = ''
Parameter ID: 14
country phone code
country phone code text

The country calling code of the phone number, received from source `PhoneCountryCode`. It enables construction of the correct international address with the GSM number; by itself it is not the complete number to contact.

* Parameter relationships
Parameter: journey_config['country_phone_code']
Condition: No other parameter option is a prerequisite.
Reason and result: “country phone code” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 15-example
Example:
journey_config['country_phone_code'] = ''
Parameter ID: 15
gsm number
gsm number text

The GSM number stored separately from the country code, received from source `PhoneGsm`. It is used in contact-information checks when SMS, IVR, or phone call is selected; the journey may be made passive if required phone information is unavailable.

* Parameter relationships
Parameter: journey_config['gsm_number']
Condition: No other parameter option is a prerequisite.
Reason and result: “gsm number” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 16-example
Example:
journey_config['gsm_number'] = ''
Parameter ID: 16
email
email text

The customer’s email address, received from source `Mail`. It supplies the delivery address when the email channel is selected; if a valid contact value is unavailable, channel processing cannot be performed and the journey may be ended.

* Parameter relationships
Parameter: journey_config['email']
Condition: No other parameter option is a prerequisite.
Reason and result: “email” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 17-example
Example:
journey_config['email'] = ''
Parameter ID: 17
mobile notification id
mobile notification id text

The customer’s device- or subscription-based push-notification identifier. It identifies the target for the mobile-notification channel; when it is absent from direct customer data, channel processing may attempt to complete it from the wtransfer-based contact-detail source.

* Parameter relationships
Parameter: journey_config['mobile_notification_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “mobile notification id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 18-example
Example:
journey_config['mobile_notification_id'] = ''
Parameter ID: 18
mobile notification group id
mobile notification group id text

The identifier of the mobile-notification group associated with the customer. It is used when the push-notification provider requires group-based targeting and is carried into the journey from source `PushNotificationGroup`.

* Parameter relationships
Parameter: journey_config['mobile_notification_group_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “mobile notification group id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 19-example
Example:
journey_config['mobile_notification_group_id'] = ''
Parameter ID: 19
api variables
api variables textarea

The JSON text of the customer object received in the customer-acceptance API request. The code stores the object with `json.dumps` and converts it back with `json.loads` when reading the configuration; invalid JSON therefore causes parsing to fail, while original extra variables are preserved for channel-message and integration context.

* Parameter relationships
Parameter: journey_config['api_variables']
Condition: No other parameter option is a prerequisite.
Reason and result: “api variables” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: {"CustomerId":"CUSTOMER-10428"}
Example:
journey_config['api_variables'] = ''
Parameter ID: 20
visit id
visit id text

The customer’s application or visit identifier in the source system. It is used in success analysis and reporting to associate the campaign journey with the related healthcare-service record.

* Parameter relationships
Parameter: journey_config['visit_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “visit id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 21-example
Example:
journey_config['visit_id'] = ''
Parameter ID: 21
survey link
survey link text

The survey address generated for the journey or received from an external system. The survey operation writes it here after creating the link; because a channel message can deliver this value to the customer, an empty link prevents survey redirection.

* Parameter relationships
Parameter: journey_config['survey_link']
Condition: No other parameter option is a prerequisite.
Reason and result: “survey link” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 22-example
Example:
journey_config['survey_link'] = ''
Parameter ID: 22
survey system id
survey system id text

The identifier of the survey record in the relevant survey system. Stored together with the survey link, it allows response and operation records to be associated with the correct survey.

* Parameter relationships
Parameter: journey_config['survey_system_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “survey system id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 23-example
Example:
journey_config['survey_system_id'] = ''
Parameter ID: 23
agenda time
agenda time list_parameter

A repeating list that stores one or more agenda times calculated for the journey. Each list row contains parameter 25, agenda date; therefore, if the selected campaign agenda rule produces multiple eligible delivery times, all of them are stored under the same journey.

* Parameter relationships
Parameter: journey_config['agenda_time']
Condition: No other parameter option is a prerequisite.
Reason and result: “agenda time” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
journey_config['agenda_time'] = []
Parameter ID: 24
agenda date
agenda date datetime

A single scheduled date and time in the agenda-time list. Agenda-calculation code produces the eligible time according to campaign day and hour rules and adds it to the list; channel operations use this schedule so processing can occur only when the time is due.

* Parameter relationships
Parameter: journey_config['agenda_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “agenda date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['agenda_date'] = ''
Parameter ID: 25
create date
create date datetime

The Coordinated Universal Time at which the journey record was first created. It is written with the current time during new acceptance and provides the technical record-creation time; although written in the same operation as parameter 7, start date, it is a separate audit field.

* Parameter relationships
Parameter: journey_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['create_date'] = ''
Parameter ID: 26
update date
update date datetime

Defined to store the time at which journey data was last updated. The inspected configuration code reads the field but does not automatically write it during initial customer acceptance; integrations that update the record must send this field separately.

* Parameter relationships
Parameter: journey_config['update_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “update date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['update_date'] = ''
Parameter ID: 27
campaign client id
campaign client id text

The client identifier of the campaign record that owns the journey. When a new journey is created, the campaign identifier in request scope is written here; channel settings and success analysis find the correct campaign configuration through this association.

* Parameter relationships
Parameter: journey_config['campaign_client_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign client id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 28-example
Example:
journey_config['campaign_client_id'] = ''
Parameter ID: 28
primary click status
primary click status select

A summary of whether at least one click related to the primary target was detected. `yes` summarizes the presence of events in the primary-click list; because detail identifier and date are stored in parameters 45–47, this field alone is not the event history.

* Parameter relationships
Parameter: journey_config['primary_click_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary click status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — no
Interprets the field as “no”; business rules are evaluated according to this selected state.
1 — yes
Interprets the field as “yes”; business rules are evaluated according to this selected state.
Example: 0 — no
Example:
journey_config['primary_click_status'] = '0'
Parameter ID: 29
primary success status
primary success status select

Specifies whether the campaign’s primary success condition was met. Success analysis evaluates relevant integration results; if the condition occurs, it produces `yes` together with date and total-income fields, otherwise it remains `no`.

* Parameter relationships
Parameter: journey_config['primary_success_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary success status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — no
Interprets the field as “no”; business rules are evaluated according to this selected state.
1 — yes
Interprets the field as “yes”; business rules are evaluated according to this selected state.
Example: 0 — no
Example:
journey_config['primary_success_status'] = '0'
Parameter ID: 30
primary success date
primary success date datetime

The date on which primary success occurred or the date used by analysis. It is reported with the summary success status; when multiple details exist, detail dates remain in the list while this field carries the top-level date.

* Parameter relationships
Parameter: journey_config['primary_success_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary success date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['primary_success_date'] = ''
Parameter ID: 31
primary success total income
primary success total income float

The numeric total of revenues associated with primary success. Revenue values in success details may be totaled in the result context for reporting; when there is no success, the field may remain empty or zero, and currency is not defined separately in this layer.

* Parameter relationships
Parameter: journey_config['primary_success_total_income']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary success total income” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 1250.50
Example:
journey_config['primary_success_total_income'] = ''
Parameter ID: 32
secondary click status
secondary click status select

A summary of whether at least one click related to the secondary target was detected. Detailed events are stored in the repeating list at parameters 48–50; this field provides a quick yes/no distinction for reports and filters.

* Parameter relationships
Parameter: journey_config['secondary_click_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary click status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — no
Interprets the field as “no”; business rules are evaluated according to this selected state.
1 — yes
Interprets the field as “yes”; business rules are evaluated according to this selected state.
Example: 0 — no
Example:
journey_config['secondary_click_status'] = '0'
Parameter ID: 33
secondary success status
secondary success status select

Specifies whether the campaign’s secondary success condition was met. Success analysis evaluates secondary-rule results separately; therefore, it can be yes or no independently of primary success.

* Parameter relationships
Parameter: journey_config['secondary_success_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary success status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — no
Interprets the field as “no”; business rules are evaluated according to this selected state.
1 — yes
Interprets the field as “yes”; business rules are evaluated according to this selected state.
Example: 0 — no
Example:
journey_config['secondary_success_status'] = '0'
Parameter ID: 34
secondary success date
secondary success date datetime

The date on which secondary success occurred or the date used by analysis. When there are multiple secondary-success details, list dates are preserved while this field provides the top-level reporting date.

* Parameter relationships
Parameter: journey_config['secondary_success_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary success date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['secondary_success_date'] = ''
Parameter ID: 35
secondary success total income
secondary success total income float

The numeric total of revenues associated with secondary success. It is reported together with secondary-success details; when no revenue is found it may be empty or zero, and this field does not store currency information.

* Parameter relationships
Parameter: journey_config['secondary_success_total_income']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary success total income” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 1250.50
Example:
journey_config['secondary_success_total_income'] = ''
Parameter ID: 36
primary success detail
primary success detail list_parameter

A repeating list that stores all matches found by primary-success analysis. Because each row contains an identifier, date, and revenue, multiple success records in one journey are preserved without loss; top-level parameters 30–32 provide their summary.

* Parameter relationships
Parameter: journey_config['primary_success_detail']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary success detail” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
journey_config['primary_success_detail'] = []
Parameter ID: 37
primary success detail id
primary success detail id text

The source or integration-record identifier of a primary-success detail. It distinguishes the list row to prevent the same success event from being added again and to keep the report traceable to its source record.

* Parameter relationships
Parameter: journey_config['primary_success_detail_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary success detail id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 38-example
Example:
journey_config['primary_success_detail_id'] = ''
Parameter ID: 38
primary success detail date
primary success detail date datetime

The event date in a primary-success detail. When multiple successes exist, each event time is stored separately, preserving chronological detail beyond the single top-level date.

* Parameter relationships
Parameter: journey_config['primary_success_detail_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary success detail date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['primary_success_detail_date'] = ''
Parameter ID: 39
primary success detail total income
primary success detail total income float

The revenue value of one event in a primary-success detail. Because top-level total revenue is associated with these details, the contribution of each source record can be examined separately.

* Parameter relationships
Parameter: journey_config['primary_success_detail_total_income']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary success detail total income” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 1250.50
Example:
journey_config['primary_success_detail_total_income'] = ''
Parameter ID: 40
secondary success detail
secondary success detail list_parameter

A repeating list that stores all matches found by secondary-success analysis. Each row contains identifier, date, and revenue parameters 42–44; top-level secondary-success fields provide a summary while the list preserves source events.

* Parameter relationships
Parameter: journey_config['secondary_success_detail']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary success detail” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
journey_config['secondary_success_detail'] = []
Parameter ID: 41
secondary success detail id
secondary success detail id text

The source or integration-record identifier of a secondary-success detail. It is used to trace the success event uniquely within the list and distinguish duplicate results.

* Parameter relationships
Parameter: journey_config['secondary_success_detail_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary success detail id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 42-example
Example:
journey_config['secondary_success_detail_id'] = ''
Parameter ID: 42
secondary success detail date
secondary success detail date datetime

The event date in a secondary-success detail. Because the time of each match is stored separately, the chronology of secondary successes can be reconstructed in reporting.

* Parameter relationships
Parameter: journey_config['secondary_success_detail_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary success detail date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['secondary_success_detail_date'] = ''
Parameter ID: 43
secondary success detail total income
secondary success detail total income float

The revenue value of one event in a secondary-success detail. It allows inspection of which source events make up the total-revenue summary in parameter 36.

* Parameter relationships
Parameter: journey_config['secondary_success_detail_total_income']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary success detail total income” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 1250.50
Example:
journey_config['secondary_success_detail_total_income'] = ''
Parameter ID: 44
primary click
primary click list_parameter

A repeating list that stores click events for the primary target. Each row contains a click identifier and date; parameter 29 only summarizes whether an event exists.

* Parameter relationships
Parameter: journey_config['primary_click']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary click” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
journey_config['primary_click'] = []
Parameter ID: 45
primary click id
primary click id text

The source identifier of a primary-click event. It makes the same event traceable and distinguishes repeated clicks from one another.

* Parameter relationships
Parameter: journey_config['primary_click_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary click id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 46-example
Example:
journey_config['primary_click_id'] = ''
Parameter ID: 46
primary click date
primary click date datetime

The date on which a primary-click event occurred. When there are multiple clicks, each time is preserved separately in its list row.

* Parameter relationships
Parameter: journey_config['primary_click_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “primary click date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['primary_click_date'] = ''
Parameter ID: 47
secondary click
secondary click list_parameter

A repeating list that stores click events for the secondary target. Each row contains identifier and date parameters 49 and 50; parameter 33 is the yes/no summary of the list.

* Parameter relationships
Parameter: journey_config['secondary_click']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary click” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
journey_config['secondary_click'] = []
Parameter ID: 48
secondary click id
secondary click id text

The source identifier of a secondary-click event. It allows the event to be traced to its source and multiple clicks to be recorded separately.

* Parameter relationships
Parameter: journey_config['secondary_click_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary click id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 49-example
Example:
journey_config['secondary_click_id'] = ''
Parameter ID: 49
secondary click date
secondary click date datetime

The date on which a secondary-click event occurred. It preserves the chronological order of interactions with the secondary target.

* Parameter relationships
Parameter: journey_config['secondary_click_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “secondary click date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:30:00
Example:
journey_config['secondary_click_date'] = ''
Parameter ID: 50
doctor id
doctor id text

The source-system identifier of the doctor associated with the visit or success record. It is received from the `DoctorId` field in customer-acceptance input and used for doctor-based reporting and matching.

* Parameter relationships
Parameter: journey_config['doctor_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “doctor id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 51-example
Example:
journey_config['doctor_id'] = ''
Parameter ID: 51
doctor name
doctor name text

The display name of the doctor associated with the visit or success record. It comes from source `DoctorName`; it complements the identifier with human-readable context but does not replace the doctor identifier for matching.

* Parameter relationships
Parameter: journey_config['doctor_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “doctor name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 52-example
Example:
journey_config['doctor_name'] = ''
Parameter ID: 52
visit type
visit type select

Classifies the operation type of the source visit. Customer-acceptance code stores incoming `VisitType` as the option value; success analysis and reports can distinguish emergency examination, surgery, control, and other types with this classification.

* Parameter relationships
Parameter: journey_config['visit_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “visit type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — emergency examination
Stores the record with the “emergency examination” classification and uses this value in matching and reporting.
1 — operation
Stores the record with the “operation” classification and uses this value in matching and reporting.
2 — check up
Stores the record with the “check up” classification and uses this value in matching and reporting.
3 — pediatric intensive care
Stores the record with the “pediatric intensive care” classification and uses this value in matching and reporting.
4 — test
Stores the record with the “test” classification and uses this value in matching and reporting.
5 — other
Stores the record with the “other” classification and uses this value in matching and reporting.
6 — donor
Stores the record with the “donor” classification and uses this value in matching and reporting.
7 — endoscopy colonoscopy
Stores the record with the “endoscopy colonoscopy” classification and uses this value in matching and reporting.
8 — injection
Stores the record with the “injection” classification and uses this value in matching and reporting.
9 — home care
Stores the record with the “home care” classification and uses this value in matching and reporting.
10 — physical therapy session
Stores the record with the “physical therapy session” classification and uses this value in matching and reporting.
11 — general examination
Stores the record with the “general examination” classification and uses this value in matching and reporting.
12 — general intensive care
Stores the record with the “general intensive care” classification and uses this value in matching and reporting.
13 — interventional procedures
Stores the record with the “interventional procedures” classification and uses this value in matching and reporting.
14 — physician preliminary interview
Stores the record with the “physician preliminary interview” classification and uses this value in matching and reporting.
15 — second opinion
Stores the record with the “second opinion” classification and uses this value in matching and reporting.
16 — prescriptions
Stores the record with the “prescriptions” classification and uses this value in matching and reporting.
17 — workplace medicine
Stores the record with the “workplace medicine” classification and uses this value in matching and reporting.
18 — test tube baby
Stores the record with the “test tube baby” classification and uses this value in matching and reporting.
19 — bone marrow
Stores the record with the “bone marrow” classification and uses this value in matching and reporting.
20 — chemotherapy
Stores the record with the “chemotherapy” classification and uses this value in matching and reporting.
21 — stem cell donor
Stores the record with the “stem cell donor” classification and uses this value in matching and reporting.
22 — council
Stores the record with the “council” classification and uses this value in matching and reporting.
23 — control inspection
Stores the record with the “control inspection” classification and uses this value in matching and reporting.
24 — laboratory
Stores the record with the “laboratory” classification and uses this value in matching and reporting.
25 — medical treatment
Stores the record with the “medical treatment” classification and uses this value in matching and reporting.
26 — intervention
Stores the record with the “intervention” classification and uses this value in matching and reporting.
27 — oncology
Stores the record with the “oncology” classification and uses this value in matching and reporting.
28 — Online examination
Stores the record with the “Online examination” classification and uses this value in matching and reporting.
29 — transplantation
Stores the record with the “transplantation” classification and uses this value in matching and reporting.
30 — orthodontics
Stores the record with the “orthodontics” classification and uses this value in matching and reporting.
31 — dressing
Stores the record with the “dressing” classification and uses this value in matching and reporting.
32 — before going to bed
Stores the record with the “before going to bed” classification and uses this value in matching and reporting.
33 — radiological
Stores the record with the “radiological” classification and uses this value in matching and reporting.
34 — radiotherapy
Stores the record with the “radiotherapy” classification and uses this value in matching and reporting.
35 — prescriptions
Stores the record with the “prescriptions” classification and uses this value in matching and reporting.
36 — hair transplantation
Stores the record with the “hair transplantation” classification and uses this value in matching and reporting.
37 — scanning
Stores the record with the “scanning” classification and uses this value in matching and reporting.
38 — examination record
Stores the record with the “examination record” classification and uses this value in matching and reporting.
39 — newborn examination
Stores the record with the “newborn examination” classification and uses this value in matching and reporting.
40 — neonatal intensive care
Stores the record with the “neonatal intensive care” classification and uses this value in matching and reporting.
41 — intensive care
Stores the record with the “intensive care” classification and uses this value in matching and reporting.
Example: 0 — emergency examination
Example:
journey_config['visit_type'] = '0'
Parameter ID: 53
hospitalization type
hospitalization type select

Specifies whether the hospitalization-related service is classified as surgery, medical treatment, or intensive care. Source `HospitalizationType` is carried into the journey and is meaningful only when a hospitalization context exists.

* Parameter relationships
Parameter: journey_config['hospitalization_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “hospitalization type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — surgery
Stores the record with the “surgery” classification and uses this value in matching and reporting.
1 — medical treatment
Stores the record with the “medical treatment” classification and uses this value in matching and reporting.
2 — intensive care
Stores the record with the “intensive care” classification and uses this value in matching and reporting.
Example: 0 — surgery
Example:
journey_config['hospitalization_type'] = '0'
Parameter ID: 54
arrive type
arrive type select

Specifies whether the visit occurs as outpatient, inpatient, or day case. Because source `ArriveType` is stored as an option, reports and success rules can distinguish the service-delivery mode.

* Parameter relationships
Parameter: journey_config['arrive_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “arrive type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — standing
Stores the record with the “standing” classification and uses this value in matching and reporting.
1 — lying
Stores the record with the “lying” classification and uses this value in matching and reporting.
2 — daily
Stores the record with the “daily” classification and uses this value in matching and reporting.
Example: 0 — standing
Example:
journey_config['arrive_type'] = '0'
Parameter ID: 55
db map id
db map id text

The client identifier of the database map that produced the customer data. Source `DbMapId` preserves data lineage and makes it possible to trace which mapping supplied the success or contact-detail integration.

* Parameter relationships
Parameter: journey_config['db_map_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “db map id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 56-example
Example:
journey_config['db_map_id'] = ''
Parameter ID: 56
db server id
db server id text

The client identifier of the database server that produced the customer data. Together with `DbMapId` it defines the source connection; using a map that belongs to another server can cause queries against the wrong source.

* Parameter relationships
Parameter: journey_config['db_server_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “db server id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 57-example
Example:
journey_config['db_server_id'] = ''
Parameter ID: 57
legal data processing permission
legal data processing permission select

The permission status for processing the customer’s personal data. When the source has no value, the configuration defaults to `missing`; rejected or awaiting-approval values must not be treated as approved in channel and integration decisions that require permission.

* Parameter relationships
Parameter: journey_config['legal_data_processing_permission']
Condition: No other parameter option is a prerequisite.
Reason and result: “legal data processing permission” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 — approved
Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 — awaiting approval
Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 — missing
Interprets the field as “missing”; business rules are evaluated according to this selected state.
Example: 0 — rejected
Example:
journey_config['legal_data_processing_permission'] = '0'
Parameter ID: 58
legal communication permission
legal communication permission select

The permission status for general communication with the customer. It may be used together with channel-specific permissions when evaluating channel eligibility; values other than `approved` do not represent explicit approval.

* Parameter relationships
Parameter: journey_config['legal_communication_permission']
Condition: No other parameter option is a prerequisite.
Reason and result: “legal communication permission” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 — approved
Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 — awaiting approval
Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 — missing
Interprets the field as “missing”; business rules are evaluated according to this selected state.
Example: 0 — rejected
Example:
journey_config['legal_communication_permission'] = '0'
Parameter ID: 59
sms permission
sms permission select

The permission to send SMS messages to the customer. If the SMS channel is to be selected, an approved value permits communication; rejected, awaiting approval, or missing values must not be interpreted as approved SMS permission.

* Parameter relationships
Parameter: journey_config['sms_permission']
Condition: No other parameter option is a prerequisite.
Reason and result: “sms permission” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 — approved
Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 — awaiting approval
Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 — missing
Interprets the field as “missing”; business rules are evaluated according to this selected state.
Example: 0 — rejected
Example:
journey_config['sms_permission'] = '0'
Parameter ID: 60
email permission
email permission select

The permission to send email to the customer. It is used when evaluating eligibility of the email channel; only `approved` expresses explicit permission, and other states are not approval for delivery.

* Parameter relationships
Parameter: journey_config['email_permission']
Condition: No other parameter option is a prerequisite.
Reason and result: “email permission” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 — approved
Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 — awaiting approval
Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 — missing
Interprets the field as “missing”; business rules are evaluated according to this selected state.
Example: 0 — rejected
Example:
journey_config['email_permission'] = '0'
Parameter ID: 61
phone call permission
phone call permission select

The permission to call the customer by phone. It carries the approval state for the phone-call channel; rejected, pending, or missing permission must not produce the same behavior as approved call permission.

* Parameter relationships
Parameter: journey_config['phone_call_permission']
Condition: No other parameter option is a prerequisite.
Reason and result: “phone call permission” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; business rules are evaluated according to this selected state.
1 — approved
Interprets the field as “approved”; business rules are evaluated according to this selected state.
2 — awaiting approval
Interprets the field as “awaiting approval”; business rules are evaluated according to this selected state.
3 — missing
Interprets the field as “missing”; business rules are evaluated according to this selected state.
Example: 0 — rejected
Example:
journey_config['phone_call_permission'] = '0'
Parameter ID: 62
nation code
nation code select

The option that represents the customer’s country by code. Source `NationCode` is normally written here and is machine-readable for country-based matching. However, in the two inspected customer-acceptance paths, `NationName` is also mistakenly written to parameter 63 instead of 64, so the name can overwrite the code; until this is fixed, verify that the value in this field is actually a country code.

* Parameter relationships
Parameter: journey_config['nation_code']
Condition: No other parameter option is a prerequisite.
Reason and result: “nation code” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — US
Stores the record with the “US” classification and uses this value in matching and reporting.
1 — AF
Stores the record with the “AF” classification and uses this value in matching and reporting.
2 — DE
Stores the record with the “DE” classification and uses this value in matching and reporting.
3 — AS
Stores the record with the “AS” classification and uses this value in matching and reporting.
4 — AD
Stores the record with the “AD” classification and uses this value in matching and reporting.
5 — AO
Stores the record with the “AO” classification and uses this value in matching and reporting.
6 — AI
Stores the record with the “AI” classification and uses this value in matching and reporting.
7 — AR
Stores the record with the “AR” classification and uses this value in matching and reporting.
8 — AL
Stores the record with the “AL” classification and uses this value in matching and reporting.
9 — AW
Stores the record with the “AW” classification and uses this value in matching and reporting.
10 — AU
Stores the record with the “AU” classification and uses this value in matching and reporting.
11 — AT
Stores the record with the “AT” classification and uses this value in matching and reporting.
12 — AZ
Stores the record with the “AZ” classification and uses this value in matching and reporting.
13 — BS
Stores the record with the “BS” classification and uses this value in matching and reporting.
14 — BH
Stores the record with the “BH” classification and uses this value in matching and reporting.
15 — BD
Stores the record with the “BD” classification and uses this value in matching and reporting.
16 — BB
Stores the record with the “BB” classification and uses this value in matching and reporting.
17 — AG
Stores the record with the “AG” classification and uses this value in matching and reporting.
18 — BY
Stores the record with the “BY” classification and uses this value in matching and reporting.
19 — BE
Stores the record with the “BE” classification and uses this value in matching and reporting.
20 — BZ
Stores the record with the “BZ” classification and uses this value in matching and reporting.
21 — BJ
Stores the record with the “BJ” classification and uses this value in matching and reporting.
22 — BM
Stores the record with the “BM” classification and uses this value in matching and reporting.
23 — AE
Stores the record with the “AE” classification and uses this value in matching and reporting.
24 — BO
Stores the record with the “BO” classification and uses this value in matching and reporting.
25 — BA
Stores the record with the “BA” classification and uses this value in matching and reporting.
26 — BW
Stores the record with the “BW” classification and uses this value in matching and reporting.
27 — BR
Stores the record with the “BR” classification and uses this value in matching and reporting.
28 — VG
Stores the record with the “VG” classification and uses this value in matching and reporting.
29 — BN
Stores the record with the “BN” classification and uses this value in matching and reporting.
30 — BG
Stores the record with the “BG” classification and uses this value in matching and reporting.
31 — BF
Stores the record with the “BF” classification and uses this value in matching and reporting.
32 — BI
Stores the record with the “BI” classification and uses this value in matching and reporting.
33 — BT
Stores the record with the “BT” classification and uses this value in matching and reporting.
34 — CV
Stores the record with the “CV” classification and uses this value in matching and reporting.
35 — KY
Stores the record with the “KY” classification and uses this value in matching and reporting.
36 — GI
Stores the record with the “GI” classification and uses this value in matching and reporting.
37 — CK
Stores the record with the “CK” classification and uses this value in matching and reporting.
38 — TD
Stores the record with the “TD” classification and uses this value in matching and reporting.
39 — CZ
Stores the record with the “CZ” classification and uses this value in matching and reporting.
40 — CN
Stores the record with the “CN” classification and uses this value in matching and reporting.
41 — DK
Stores the record with the “DK” classification and uses this value in matching and reporting.
42 — DJ
Stores the record with the “DJ” classification and uses this value in matching and reporting.
43 — TL
Stores the record with the “TL” classification and uses this value in matching and reporting.
44 — DO
Stores the record with the “DO” classification and uses this value in matching and reporting.
45 — DM
Stores the record with the “DM” classification and uses this value in matching and reporting.
46 — EC
Stores the record with the “EC” classification and uses this value in matching and reporting.
47 — GQ
Stores the record with the “GQ” classification and uses this value in matching and reporting.
48 — SV
Stores the record with the “SV” classification and uses this value in matching and reporting.
49 — ID
Stores the record with the “ID” classification and uses this value in matching and reporting.
50 — ER
Stores the record with the “ER” classification and uses this value in matching and reporting.
51 — AM
Stores the record with the “AM” classification and uses this value in matching and reporting.
52 — EE
Stores the record with the “EE” classification and uses this value in matching and reporting.
53 — ET
Stores the record with the “ET” classification and uses this value in matching and reporting.
54 — FO
Stores the record with the “FO” classification and uses this value in matching and reporting.
55 — MA
Stores the record with the “MA” classification and uses this value in matching and reporting.
56 — FJ
Stores the record with the “FJ” classification and uses this value in matching and reporting.
57 — CI
Stores the record with the “CI” classification and uses this value in matching and reporting.
58 — PH
Stores the record with the “PH” classification and uses this value in matching and reporting.
59 — PS
Stores the record with the “PS” classification and uses this value in matching and reporting.
60 — FI
Stores the record with the “FI” classification and uses this value in matching and reporting.
61 — FR
Stores the record with the “FR” classification and uses this value in matching and reporting.
62 — GF
Stores the record with the “GF” classification and uses this value in matching and reporting.
63 — PF
Stores the record with the “PF” classification and uses this value in matching and reporting.
64 — GA
Stores the record with the “GA” classification and uses this value in matching and reporting.
65 — GM
Stores the record with the “GM” classification and uses this value in matching and reporting.
66 — GH
Stores the record with the “GH” classification and uses this value in matching and reporting.
67 — GN
Stores the record with the “GN” classification and uses this value in matching and reporting.
68 — GD
Stores the record with the “GD” classification and uses this value in matching and reporting.
69 — GL
Stores the record with the “GL” classification and uses this value in matching and reporting.
70 — GP
Stores the record with the “GP” classification and uses this value in matching and reporting.
71 — GU
Stores the record with the “GU” classification and uses this value in matching and reporting.
72 — GT
Stores the record with the “GT” classification and uses this value in matching and reporting.
73 — GY
Stores the record with the “GY” classification and uses this value in matching and reporting.
74 — ZA
Stores the record with the “ZA” classification and uses this value in matching and reporting.
75 — KR
Stores the record with the “KR” classification and uses this value in matching and reporting.
76 — GE
Stores the record with the “GE” classification and uses this value in matching and reporting.
77 — HT
Stores the record with the “HT” classification and uses this value in matching and reporting.
78 — HR
Stores the record with the “HR” classification and uses this value in matching and reporting.
79 — IN
Stores the record with the “IN” classification and uses this value in matching and reporting.
80 — NLD
Stores the record with the “NLD” classification and uses this value in matching and reporting.
81 — AN
Stores the record with the “AN” classification and uses this value in matching and reporting.
82 — HN
Stores the record with the “HN” classification and uses this value in matching and reporting.
83 — HK
Stores the record with the “HK” classification and uses this value in matching and reporting.
84 — IQ
Stores the record with the “IQ” classification and uses this value in matching and reporting.
85 — IE
Stores the record with the “IE” classification and uses this value in matching and reporting.
86 — ES
Stores the record with the “ES” classification and uses this value in matching and reporting.
87 — IL
Stores the record with the “IL” classification and uses this value in matching and reporting.
88 — SE
Stores the record with the “SE” classification and uses this value in matching and reporting.
89 — CH
Stores the record with the “CH” classification and uses this value in matching and reporting.
90 — IT
Stores the record with the “IT” classification and uses this value in matching and reporting.
91 — IS
Stores the record with the “IS” classification and uses this value in matching and reporting.
92 — JM
Stores the record with the “JM” classification and uses this value in matching and reporting.
93 — JP
Stores the record with the “JP” classification and uses this value in matching and reporting.
94 — KH
Stores the record with the “KH” classification and uses this value in matching and reporting.
95 — CM
Stores the record with the “CM” classification and uses this value in matching and reporting.
96 — CA
Stores the record with the “CA” classification and uses this value in matching and reporting.
97 — QA
Stores the record with the “QA” classification and uses this value in matching and reporting.
98 — KZ
Stores the record with the “KZ” classification and uses this value in matching and reporting.
99 — KE
Stores the record with the “KE” classification and uses this value in matching and reporting.
100 — CY
Stores the record with the “CY” classification and uses this value in matching and reporting.
101 — KG
Stores the record with the “KG” classification and uses this value in matching and reporting.
102 — CO
Stores the record with the “CO” classification and uses this value in matching and reporting.
103 — CD
Stores the record with the “CD” classification and uses this value in matching and reporting.
104 — CG
Stores the record with the “CG” classification and uses this value in matching and reporting.
105 — CR
Stores the record with the “CR” classification and uses this value in matching and reporting.
106 — KW
Stores the record with the “KW” classification and uses this value in matching and reporting.
107 — LA
Stores the record with the “LA” classification and uses this value in matching and reporting.
108 — LV
Stores the record with the “LV” classification and uses this value in matching and reporting.
109 — LS
Stores the record with the “LS” classification and uses this value in matching and reporting.
110 — LR
Stores the record with the “LR” classification and uses this value in matching and reporting.
111 — LY
Stores the record with the “LY” classification and uses this value in matching and reporting.
112 — LI
Stores the record with the “LI” classification and uses this value in matching and reporting.
113 — LT
Stores the record with the “LT” classification and uses this value in matching and reporting.
114 — LB
Stores the record with the “LB” classification and uses this value in matching and reporting.
115 — LU
Stores the record with the “LU” classification and uses this value in matching and reporting.
116 — HU
Stores the record with the “HU” classification and uses this value in matching and reporting.
117 — MG
Stores the record with the “MG” classification and uses this value in matching and reporting.
118 — MO
Stores the record with the “MO” classification and uses this value in matching and reporting.
119 — MK
Stores the record with the “MK” classification and uses this value in matching and reporting.
120 — MW
Stores the record with the “MW” classification and uses this value in matching and reporting.
121 — MV
Stores the record with the “MV” classification and uses this value in matching and reporting.
122 — MY
Stores the record with the “MY” classification and uses this value in matching and reporting.
123 — ML
Stores the record with the “ML” classification and uses this value in matching and reporting.
124 — MT
Stores the record with the “MT” classification and uses this value in matching and reporting.
125 — MU
Stores the record with the “MU” classification and uses this value in matching and reporting.
126 — MH
Stores the record with the “MH” classification and uses this value in matching and reporting.
127 — MQ
Stores the record with the “MQ” classification and uses this value in matching and reporting.
128 — MX
Stores the record with the “MX” classification and uses this value in matching and reporting.
129 — FM
Stores the record with the “FM” classification and uses this value in matching and reporting.
130 — EG
Stores the record with the “EG” classification and uses this value in matching and reporting.
131 — MN
Stores the record with the “MN” classification and uses this value in matching and reporting.
132 — MD
Stores the record with the “MD” classification and uses this value in matching and reporting.
133 — MC
Stores the record with the “MC” classification and uses this value in matching and reporting.
134 — MS
Stores the record with the “MS” classification and uses this value in matching and reporting.
135 — MR
Stores the record with the “MR” classification and uses this value in matching and reporting.
136 — MZ
Stores the record with the “MZ” classification and uses this value in matching and reporting.
137 —
Stores the record with the “” classification and uses this value in matching and reporting.
138 — NP
Stores the record with the “NP” classification and uses this value in matching and reporting.
139 — NE
Stores the record with the “NE” classification and uses this value in matching and reporting.
140 — NG
Stores the record with the “NG” classification and uses this value in matching and reporting.
141 — NI
Stores the record with the “NI” classification and uses this value in matching and reporting.
142 — NO
Stores the record with the “NO” classification and uses this value in matching and reporting.
143 — UZ
Stores the record with the “UZ” classification and uses this value in matching and reporting.
144 — PK
Stores the record with the “PK” classification and uses this value in matching and reporting.
145 — PW
Stores the record with the “PW” classification and uses this value in matching and reporting.
146 — PA
Stores the record with the “PA” classification and uses this value in matching and reporting.
147 — PG
Stores the record with the “PG” classification and uses this value in matching and reporting.
148 — PY
Stores the record with the “PY” classification and uses this value in matching and reporting.
149 — PE
Stores the record with the “PE” classification and uses this value in matching and reporting.
150 — PL
Stores the record with the “PL” classification and uses this value in matching and reporting.
151 — PT
Stores the record with the “PT” classification and uses this value in matching and reporting.
152 — PR
Stores the record with the “PR” classification and uses this value in matching and reporting.
153 — RE
Stores the record with the “RE” classification and uses this value in matching and reporting.
154 — RO
Stores the record with the “RO” classification and uses this value in matching and reporting.
155 — RW
Stores the record with the “RW” classification and uses this value in matching and reporting.
156 — RU
Stores the record with the “RU” classification and uses this value in matching and reporting.
157 — MP
Stores the record with the “MP” classification and uses this value in matching and reporting.
158 — SN
Stores the record with the “SN” classification and uses this value in matching and reporting.
159 — SC
Stores the record with the “SC” classification and uses this value in matching and reporting.
160 — CS
Stores the record with the “CS” classification and uses this value in matching and reporting.
161 — SG
Stores the record with the “SG” classification and uses this value in matching and reporting.
162 — SK
Stores the record with the “SK” classification and uses this value in matching and reporting.
163 — SI
Stores the record with the “SI” classification and uses this value in matching and reporting.
164 — LK
Stores the record with the “LK” classification and uses this value in matching and reporting.
165 — KN
Stores the record with the “KN” classification and uses this value in matching and reporting.
166 — LC
Stores the record with the “LC” classification and uses this value in matching and reporting.
167 — VC
Stores the record with the “VC” classification and uses this value in matching and reporting.
168 — SR
Stores the record with the “SR” classification and uses this value in matching and reporting.
169 — SY
Stores the record with the “SY” classification and uses this value in matching and reporting.
170 — SA
Stores the record with the “SA” classification and uses this value in matching and reporting.
171 — SZ
Stores the record with the “SZ” classification and uses this value in matching and reporting.
172 — CL
Stores the record with the “CL” classification and uses this value in matching and reporting.
173 — TZ
Stores the record with the “TZ” classification and uses this value in matching and reporting.
174 — TH
Stores the record with the “TH” classification and uses this value in matching and reporting.
175 — TW
Stores the record with the “TW” classification and uses this value in matching and reporting.
176 — TG
Stores the record with the “TG” classification and uses this value in matching and reporting.
177 — TO
Stores the record with the “TO” classification and uses this value in matching and reporting.
178 — TT
Stores the record with the “TT” classification and uses this value in matching and reporting.
179 — TN
Stores the record with the “TN” classification and uses this value in matching and reporting.
180 — TC
Stores the record with the “TC” classification and uses this value in matching and reporting.
181 — TR
Stores the record with the “TR” classification and uses this value in matching and reporting.
182 — TM
Stores the record with the “TM” classification and uses this value in matching and reporting.
183 — UG
Stores the record with the “UG” classification and uses this value in matching and reporting.
184 — UA
Stores the record with the “UA” classification and uses this value in matching and reporting.
185 — OM
Stores the record with the “OM” classification and uses this value in matching and reporting.
186 — UY
Stores the record with the “UY” classification and uses this value in matching and reporting.
187 — JO
Stores the record with the “JO” classification and uses this value in matching and reporting.
188 — VU
Stores the record with the “VU” classification and uses this value in matching and reporting.
189 — VE
Stores the record with the “VE” classification and uses this value in matching and reporting.
190 — VN
Stores the record with the “VN” classification and uses this value in matching and reporting.
191 — VI
Stores the record with the “VI” classification and uses this value in matching and reporting.
192 — WF
Stores the record with the “WF” classification and uses this value in matching and reporting.
193 — YE
Stores the record with the “YE” classification and uses this value in matching and reporting.
194 — NC
Stores the record with the “NC” classification and uses this value in matching and reporting.
195 — NZ
Stores the record with the “NZ” classification and uses this value in matching and reporting.
196 — GR
Stores the record with the “GR” classification and uses this value in matching and reporting.
197 — ZM
Stores the record with the “ZM” classification and uses this value in matching and reporting.
198 — ZW
Stores the record with the “ZW” classification and uses this value in matching and reporting.
199 — IR
Stores the record with the “IR” classification and uses this value in matching and reporting.
200 — XK
Stores the record with the “XK” classification and uses this value in matching and reporting.
201 — UK
Stores the record with the “UK” classification and uses this value in matching and reporting.
202 — TJ
Stores the record with the “TJ” classification and uses this value in matching and reporting.
203 — SO
Stores the record with the “SO” classification and uses this value in matching and reporting.
204 — DZ
Stores the record with the “DZ” classification and uses this value in matching and reporting.
205 — AX
Stores the record with the “AX” classification and uses this value in matching and reporting.
206 — AQ
Stores the record with the “AQ” classification and uses this value in matching and reporting.
207 — EH
Stores the record with the “EH” classification and uses this value in matching and reporting.
208 — UM
Stores the record with the “UM” classification and uses this value in matching and reporting.
209 — BV
Stores the record with the “BV” classification and uses this value in matching and reporting.
210 — CX
Stores the record with the “CX” classification and uses this value in matching and reporting.
211 — CC
Stores the record with the “CC” classification and uses this value in matching and reporting.
212 — TF
Stores the record with the “TF” classification and uses this value in matching and reporting.
213 — GW
Stores the record with the “GW” classification and uses this value in matching and reporting.
214 — GG
Stores the record with the “GG” classification and uses this value in matching and reporting.
215 — GS
Stores the record with the “GS” classification and uses this value in matching and reporting.
216 — HM
Stores the record with the “HM” classification and uses this value in matching and reporting.
217 — VA
Stores the record with the “VA” classification and uses this value in matching and reporting.
218 — IM
Stores the record with the “IM” classification and uses this value in matching and reporting.
219 — IO
Stores the record with the “IO” classification and uses this value in matching and reporting.
220 — JE
Stores the record with the “JE” classification and uses this value in matching and reporting.
221 — KI
Stores the record with the “KI” classification and uses this value in matching and reporting.
222 — KM
Stores the record with the “KM” classification and uses this value in matching and reporting.
223 — KP
Stores the record with the “KP” classification and uses this value in matching and reporting.
224 — YT
Stores the record with the “YT” classification and uses this value in matching and reporting.
225 — MM
Stores the record with the “MM” classification and uses this value in matching and reporting.
226 — NR
Stores the record with the “NR” classification and uses this value in matching and reporting.
227 — NU
Stores the record with the “NU” classification and uses this value in matching and reporting.
228 — NF
Stores the record with the “NF” classification and uses this value in matching and reporting.
229 — CF
Stores the record with the “CF” classification and uses this value in matching and reporting.
230 — PN
Stores the record with the “PN” classification and uses this value in matching and reporting.
231 — BL
Stores the record with the “BL” classification and uses this value in matching and reporting.
232 — MF
Stores the record with the “MF” classification and uses this value in matching and reporting.
233 — PM
Stores the record with the “PM” classification and uses this value in matching and reporting.
234 — WS
Stores the record with the “WS” classification and uses this value in matching and reporting.
235 — SM
Stores the record with the “SM” classification and uses this value in matching and reporting.
236 — SH
Stores the record with the “SH” classification and uses this value in matching and reporting.
237 — ST
Stores the record with the “ST” classification and uses this value in matching and reporting.
238 — RS
Stores the record with the “RS” classification and uses this value in matching and reporting.
239 — SL
Stores the record with the “SL” classification and uses this value in matching and reporting.
240 — SB
Stores the record with the “SB” classification and uses this value in matching and reporting.
241 — SJ
Stores the record with the “SJ” classification and uses this value in matching and reporting.
242 — TK
Stores the record with the “TK” classification and uses this value in matching and reporting.
243 — TV
Stores the record with the “TV” classification and uses this value in matching and reporting.
244 — KK
Stores the record with the “KK” classification and uses this value in matching and reporting.
245 — ME
Stores the record with the “ME” classification and uses this value in matching and reporting.
246 — CU
Stores the record with the “CU” classification and uses this value in matching and reporting.
Example: 0 — US
Example:
journey_config['nation_code'] = '0'
Parameter ID: 63
nation name
nation name select

The option defined to store the display name of the customer’s country. Although the WDM schema contains parameter 64 and country-name options, the inspected customer-acceptance code mistakenly writes `NationName` to parameter 63; therefore, this field may not be populated automatically in the current flow and may remain empty unless written manually or by another integration.

* Parameter relationships
Parameter: journey_config['nation_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “nation name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — western sahara
Stores the record with the “western sahara” classification and uses this value in matching and reporting.
1 — united states outlying minor islands
Stores the record with the “united states outlying minor islands” classification and uses this value in matching and reporting.
2 — aland islands
Stores the record with the “aland islands” classification and uses this value in matching and reporting.
3 — antarctica
Stores the record with the “antarctica” classification and uses this value in matching and reporting.
4 — somalia
Stores the record with the “somalia” classification and uses this value in matching and reporting.
5 — algeria
Stores the record with the “algeria” classification and uses this value in matching and reporting.
6 — tajikistan
Stores the record with the “tajikistan” classification and uses this value in matching and reporting.
7 — sudan
Stores the record with the “sudan” classification and uses this value in matching and reporting.
8 — seychelles
Stores the record with the “seychelles” classification and uses this value in matching and reporting.
9 — bouvet island
Stores the record with the “bouvet island” classification and uses this value in matching and reporting.
10 — christmas island
Stores the record with the “christmas island” classification and uses this value in matching and reporting.
11 — mexico
Stores the record with the “mexico” classification and uses this value in matching and reporting.
12 — martinique
Stores the record with the “martinique” classification and uses this value in matching and reporting.
13 — marshall islands
Stores the record with the “marshall islands” classification and uses this value in matching and reporting.
14 — mauritius island
Stores the record with the “mauritius island” classification and uses this value in matching and reporting.
15 — moldova
Stores the record with the “moldova” classification and uses this value in matching and reporting.
16 — mongolia
Stores the record with the “mongolia” classification and uses this value in matching and reporting.
17 — egypt
Stores the record with the “egypt” classification and uses this value in matching and reporting.
18 — micronesia
Stores the record with the “micronesia” classification and uses this value in matching and reporting.
19 — montserrat
Stores the record with the “montserrat” classification and uses this value in matching and reporting.
20 — monaco
Stores the record with the “monaco” classification and uses this value in matching and reporting.
21 — serbia montenegro
Stores the record with the “serbia montenegro” classification and uses this value in matching and reporting.
22 — united united arab emirates
Stores the record with the “united united arab emirates” classification and uses this value in matching and reporting.
23 — bolivia
Stores the record with the “bolivia” classification and uses this value in matching and reporting.
24 — bosnia and herzegovina
Stores the record with the “bosnia and herzegovina” classification and uses this value in matching and reporting.
25 — botswana
Stores the record with the “botswana” classification and uses this value in matching and reporting.
26 — belgium
Stores the record with the “belgium” classification and uses this value in matching and reporting.
27 — belize
Stores the record with the “belize” classification and uses this value in matching and reporting.
28 — benin
Stores the record with the “benin” classification and uses this value in matching and reporting.
29 — bermuda
Stores the record with the “bermuda” classification and uses this value in matching and reporting.
30 — rwanda
Stores the record with the “rwanda” classification and uses this value in matching and reporting.
31 — brazil
Stores the record with the “brazil” classification and uses this value in matching and reporting.
32 — british virgin islands
Stores the record with the “british virgin islands” classification and uses this value in matching and reporting.
33 — russia
Stores the record with the “russia” classification and uses this value in matching and reporting.
34 — american samoa
Stores the record with the “american samoa” classification and uses this value in matching and reporting.
35 — argentina
Stores the record with the “argentina” classification and uses this value in matching and reporting.
36 — cocos (keeling) islands
Stores the record with the “cocos (keeling) islands” classification and uses this value in matching and reporting.
37 — lebanon
Stores the record with the “lebanon” classification and uses this value in matching and reporting.
38 — luxembourg
Stores the record with the “luxembourg” classification and uses this value in matching and reporting.
39 — hungary
Stores the record with the “hungary” classification and uses this value in matching and reporting.
40 — madagascar
Stores the record with the “madagascar” classification and uses this value in matching and reporting.
41 — macau
Stores the record with the “macau” classification and uses this value in matching and reporting.
42 — macedonia
Stores the record with the “macedonia” classification and uses this value in matching and reporting.
43 — malawi
Stores the record with the “malawi” classification and uses this value in matching and reporting.
44 — maldives
Stores the record with the “maldives” classification and uses this value in matching and reporting.
45 — malaysia
Stores the record with the “malaysia” classification and uses this value in matching and reporting.
46 — mali
Stores the record with the “mali” classification and uses this value in matching and reporting.
47 — malta
Stores the record with the “malta” classification and uses this value in matching and reporting.
48 — singapore
Stores the record with the “singapore” classification and uses this value in matching and reporting.
49 — philippines
Stores the record with the “philippines” classification and uses this value in matching and reporting.
50 — ivory coast
Stores the record with the “ivory coast” classification and uses this value in matching and reporting.
51 — faroe islands
Stores the record with the “faroe islands” classification and uses this value in matching and reporting.
52 — ethiopia
Stores the record with the “ethiopia” classification and uses this value in matching and reporting.
53 — fiji
Stores the record with the “fiji” classification and uses this value in matching and reporting.
54 — morocco
Stores the record with the “morocco” classification and uses this value in matching and reporting.
55 — eritrea
Stores the record with the “eritrea” classification and uses this value in matching and reporting.
56 — indonesia
Stores the record with the “indonesia” classification and uses this value in matching and reporting.
57 — estonia
Stores the record with the “estonia” classification and uses this value in matching and reporting.
58 — armenia
Stores the record with the “armenia” classification and uses this value in matching and reporting.
59 — senegal
Stores the record with the “senegal” classification and uses this value in matching and reporting.
60 — new caledonia
Stores the record with the “new caledonia” classification and uses this value in matching and reporting.
61 — wallis and futuna islands
Stores the record with the “wallis and futuna islands” classification and uses this value in matching and reporting.
62 — tanzania
Stores the record with the “tanzania” classification and uses this value in matching and reporting.
63 — yemen
Stores the record with the “yemen” classification and uses this value in matching and reporting.
64 — vanuatu
Stores the record with the “vanuatu” classification and uses this value in matching and reporting.
65 — vietnam
Stores the record with the “vietnam” classification and uses this value in matching and reporting.
66 — chile
Stores the record with the “chile” classification and uses this value in matching and reporting.
67 — oman
Stores the record with the “oman” classification and uses this value in matching and reporting.
68 — ukraine
Stores the record with the “ukraine” classification and uses this value in matching and reporting.
69 — jordan
Stores the record with the “jordan” classification and uses this value in matching and reporting.
70 — uruguay
Stores the record with the “uruguay” classification and uses this value in matching and reporting.
71 — liberia
Stores the record with the “liberia” classification and uses this value in matching and reporting.
72 — lesotho
Stores the record with the “lesotho” classification and uses this value in matching and reporting.
73 — ireland
Stores the record with the “ireland” classification and uses this value in matching and reporting.
74 — libya
Stores the record with the “libya” classification and uses this value in matching and reporting.
75 — kuwait
Stores the record with the “kuwait” classification and uses this value in matching and reporting.
76 — latvia
Stores the record with the “latvia” classification and uses this value in matching and reporting.
77 — laos
Stores the record with the “laos” classification and uses this value in matching and reporting.
78 — netherlands
Stores the record with the “netherlands” classification and uses this value in matching and reporting.
79 — netherlands antilles
Stores the record with the “netherlands antilles” classification and uses this value in matching and reporting.
80 — croatia
Stores the record with the “croatia” classification and uses this value in matching and reporting.
81 — india
Stores the record with the “india” classification and uses this value in matching and reporting.
82 — iraq
Stores the record with the “iraq” classification and uses this value in matching and reporting.
83 — lithuania
Stores the record with the “lithuania” classification and uses this value in matching and reporting.
84 — honduras
Stores the record with the “honduras” classification and uses this value in matching and reporting.
85 — hong kong
Stores the record with the “hong kong” classification and uses this value in matching and reporting.
86 — tokelau
Stores the record with the “tokelau” classification and uses this value in matching and reporting.
87 — virgin islands (u.s.)
Stores the record with the “virgin islands (u.s.)” classification and uses this value in matching and reporting.
88 — iran
Stores the record with the “iran” classification and uses this value in matching and reporting.
89 — holy see (vatican city state)
Stores the record with the “holy see (vatican city state)” classification and uses this value in matching and reporting.
90 — germany
Stores the record with the “germany” classification and uses this value in matching and reporting.
91 — swaziland
Stores the record with the “swaziland” classification and uses this value in matching and reporting.
92 — anguilla
Stores the record with the “anguilla” classification and uses this value in matching and reporting.
93 — serbia
Stores the record with the “serbia” classification and uses this value in matching and reporting.
94 — cuba
Stores the record with the “cuba” classification and uses this value in matching and reporting.
95 — south sudan
Stores the record with the “south sudan” classification and uses this value in matching and reporting.
96 — batumi-georgia
Stores the record with the “batumi-georgia” classification and uses this value in matching and reporting.
97 — heard island and mcdonald islands
Stores the record with the “heard island and mcdonald islands” classification and uses this value in matching and reporting.
98 — santa helena
Stores the record with the “santa helena” classification and uses this value in matching and reporting.
99 — san marino
Stores the record with the “san marino” classification and uses this value in matching and reporting.
100 — congo (brazzaville)
Stores the record with the “congo (brazzaville)” classification and uses this value in matching and reporting.
101 — costa rica
Stores the record with the “costa rica” classification and uses this value in matching and reporting.
102 — saint martin (french side)
Stores the record with the “saint martin (french side)” classification and uses this value in matching and reporting.
103 — saint barthelemy
Stores the record with the “saint barthelemy” classification and uses this value in matching and reporting.
104 — samoa
Stores the record with the “samoa” classification and uses this value in matching and reporting.
105 — saint pierre and miquelon
Stores the record with the “saint pierre and miquelon” classification and uses this value in matching and reporting.
106 — kazakhstan
Stores the record with the “kazakhstan” classification and uses this value in matching and reporting.
107 — kenya
Stores the record with the “kenya” classification and uses this value in matching and reporting.
108 — canada
Stores the record with the “canada” classification and uses this value in matching and reporting.
109 — qatar
Stores the record with the “qatar” classification and uses this value in matching and reporting.
110 — colombia
Stores the record with the “colombia” classification and uses this value in matching and reporting.
111 — republic of the congo
Stores the record with the “republic of the congo” classification and uses this value in matching and reporting.
112 — cyprus
Stores the record with the “cyprus” classification and uses this value in matching and reporting.
113 — kyrgyzstan
Stores the record with the “kyrgyzstan” classification and uses this value in matching and reporting.
114 — chad
Stores the record with the “chad” classification and uses this value in matching and reporting.
115 — cook islands
Stores the record with the “cook islands” classification and uses this value in matching and reporting.
116 — burundi
Stores the record with the “burundi” classification and uses this value in matching and reporting.
117 — burkina faso
Stores the record with the “burkina faso” classification and uses this value in matching and reporting.
118 — bulgaria
Stores the record with the “bulgaria” classification and uses this value in matching and reporting.
119 — brunei
Stores the record with the “brunei” classification and uses this value in matching and reporting.
120 — gibraltar
Stores the record with the “gibraltar” classification and uses this value in matching and reporting.
121 — keymen islands
Stores the record with the “keymen islands” classification and uses this value in matching and reporting.
122 — cape verde
Stores the record with the “cape verde” classification and uses this value in matching and reporting.
123 — bhutan
Stores the record with the “bhutan” classification and uses this value in matching and reporting.
124 — sao tome and principe
Stores the record with the “sao tome and principe” classification and uses this value in matching and reporting.
125 — tuvalu
Stores the record with the “tuvalu” classification and uses this value in matching and reporting.
126 — zimbabwe
Stores the record with the “zimbabwe” classification and uses this value in matching and reporting.
127 — guernsey
Stores the record with the “guernsey” classification and uses this value in matching and reporting.
128 — saudi arabia
Stores the record with the “saudi arabia” classification and uses this value in matching and reporting.
129 — self-governing state of palestine
Stores the record with the “self-governing state of palestine” classification and uses this value in matching and reporting.
130 — finland
Stores the record with the “finland” classification and uses this value in matching and reporting.
131 — france
Stores the record with the “france” classification and uses this value in matching and reporting.
132 — french guiana
Stores the record with the “french guiana” classification and uses this value in matching and reporting.
133 — french polynesia
Stores the record with the “french polynesia” classification and uses this value in matching and reporting.
134 — gabon
Stores the record with the “gabon” classification and uses this value in matching and reporting.
135 — wales (uk)
Stores the record with the “wales (uk)” classification and uses this value in matching and reporting.
136 — gambia
Stores the record with the “gambia” classification and uses this value in matching and reporting.
137 — ghana
Stores the record with the “ghana” classification and uses this value in matching and reporting.
138 — guinea
Stores the record with the “guinea” classification and uses this value in matching and reporting.
139 — syria
Stores the record with the “syria” classification and uses this value in matching and reporting.
140 — suriname
Stores the record with the “suriname” classification and uses this value in matching and reporting.
141 — saint vincent
Stores the record with the “saint vincent” classification and uses this value in matching and reporting.
142 — saint lucia
Stores the record with the “saint lucia” classification and uses this value in matching and reporting.
143 — saint kitts and nevis
Stores the record with the “saint kitts and nevis” classification and uses this value in matching and reporting.
144 — sri lanka
Stores the record with the “sri lanka” classification and uses this value in matching and reporting.
145 — greece
Stores the record with the “greece” classification and uses this value in matching and reporting.
146 — guinea-bissau
Stores the record with the “guinea-bissau” classification and uses this value in matching and reporting.
147 — taiwan
Stores the record with the “taiwan” classification and uses this value in matching and reporting.
148 — sierra leone
Stores the record with the “sierra leone” classification and uses this value in matching and reporting.
149 — togo
Stores the record with the “togo” classification and uses this value in matching and reporting.
150 — tongo
Stores the record with the “tongo” classification and uses this value in matching and reporting.
151 — thailand
Stores the record with the “thailand” classification and uses this value in matching and reporting.
152 — afghanistan
Stores the record with the “afghanistan” classification and uses this value in matching and reporting.
153 — saipan
Stores the record with the “saipan” classification and uses this value in matching and reporting.
154 — turkey
Stores the record with the “turkey” classification and uses this value in matching and reporting.
155 — trinidad and tobago tobago
Stores the record with the “trinidad and tobago tobago” classification and uses this value in matching and reporting.
156 — angola
Stores the record with the “angola” classification and uses this value in matching and reporting.
157 — turks and caicos islands
Stores the record with the “turks and caicos islands” classification and uses this value in matching and reporting.
158 — turkmenistan
Stores the record with the “turkmenistan” classification and uses this value in matching and reporting.
159 — uganda
Stores the record with the “uganda” classification and uses this value in matching and reporting.
160 — new zealand
Stores the record with the “new zealand” classification and uses this value in matching and reporting.
161 — venezuella
Stores the record with the “venezuella” classification and uses this value in matching and reporting.
162 — french southern territories
Stores the record with the “french southern territories” classification and uses this value in matching and reporting.
163 — tunisia
Stores the record with the “tunisia” classification and uses this value in matching and reporting.
164 — cameroon
Stores the record with the “cameroon” classification and uses this value in matching and reporting.
165 — cambodia
Stores the record with the “cambodia” classification and uses this value in matching and reporting.
166 — slovak republic
Stores the record with the “slovak republic” classification and uses this value in matching and reporting.
167 — slovenia
Stores the record with the “slovenia” classification and uses this value in matching and reporting.
168 — jersey
Stores the record with the “jersey” classification and uses this value in matching and reporting.
169 — british indian ocean territory
Stores the record with the “british indian ocean territory” classification and uses this value in matching and reporting.
170 — israel
Stores the record with the “israel” classification and uses this value in matching and reporting.
171 — spain
Stores the record with the “spain” classification and uses this value in matching and reporting.
172 — switzerland
Stores the record with the “switzerland” classification and uses this value in matching and reporting.
173 — sweden
Stores the record with the “sweden” classification and uses this value in matching and reporting.
174 — iceland
Stores the record with the “iceland” classification and uses this value in matching and reporting.
175 — italy
Stores the record with the “italy” classification and uses this value in matching and reporting.
176 — japan
Stores the record with the “japan” classification and uses this value in matching and reporting.
177 — jameika
Stores the record with the “jameika” classification and uses this value in matching and reporting.
178 — australia
Stores the record with the “australia” classification and uses this value in matching and reporting.
179 — aruba
Stores the record with the “aruba” classification and uses this value in matching and reporting.
180 — azerbaijan
Stores the record with the “azerbaijan” classification and uses this value in matching and reporting.
181 — austria
Stores the record with the “austria” classification and uses this value in matching and reporting.
182 — bahrain
Stores the record with the “bahrain” classification and uses this value in matching and reporting.
183 — bahamas
Stores the record with the “bahamas” classification and uses this value in matching and reporting.
184 — barbados
Stores the record with the “barbados” classification and uses this value in matching and reporting.
185 — bangladesh
Stores the record with the “bangladesh” classification and uses this value in matching and reporting.
186 — belarus (belarus)
Stores the record with the “belarus (belarus)” classification and uses this value in matching and reporting.
187 — barbuda/antigua
Stores the record with the “barbuda/antigua” classification and uses this value in matching and reporting.
188 — liechtenstein
Stores the record with the “liechtenstein” classification and uses this value in matching and reporting.
189 — svalbard
Stores the record with the “svalbard” classification and uses this value in matching and reporting.
190 — zambia
Stores the record with the “zambia” classification and uses this value in matching and reporting.
191 — panama
Stores the record with the “panama” classification and uses this value in matching and reporting.
192 — palau
Stores the record with the “palau” classification and uses this value in matching and reporting.
193 — paraguay
Stores the record with the “paraguay” classification and uses this value in matching and reporting.
194 — papua new guinea
Stores the record with the “papua new guinea” classification and uses this value in matching and reporting.
195 — poland
Stores the record with the “poland” classification and uses this value in matching and reporting.
196 — peru
Stores the record with the “peru” classification and uses this value in matching and reporting.
197 — puerto rico
Stores the record with the “puerto rico” classification and uses this value in matching and reporting.
198 — portugal
Stores the record with the “portugal” classification and uses this value in matching and reporting.
199 — romania
Stores the record with the “romania” classification and uses this value in matching and reporting.
200 — reunion island
Stores the record with the “reunion island” classification and uses this value in matching and reporting.
201 — central africa republic of
Stores the record with the “central africa republic of” classification and uses this value in matching and reporting.
202 — pitcairn
Stores the record with the “pitcairn” classification and uses this value in matching and reporting.
203 — myanmar
Stores the record with the “myanmar” classification and uses this value in matching and reporting.
204 — nauru
Stores the record with the “nauru” classification and uses this value in matching and reporting.
205 — niu
Stores the record with the “niu” classification and uses this value in matching and reporting.
206 — norfolk island
Stores the record with the “norfolk island” classification and uses this value in matching and reporting.
207 — kiribati
Stores the record with the “kiribati” classification and uses this value in matching and reporting.
208 — comoros
Stores the record with the “comoros” classification and uses this value in matching and reporting.
209 — democratic people's republic of korea
Stores the record with the “democratic people's republic of korea” classification and uses this value in matching and reporting.
210 — mayotte
Stores the record with the “mayotte” classification and uses this value in matching and reporting.
211 — south georgia and the south sandwich islands
Stores the record with the “south georgia and the south sandwich islands” classification and uses this value in matching and reporting.
212 — equatorial guinea
Stores the record with the “equatorial guinea” classification and uses this value in matching and reporting.
213 — el salvador
Stores the record with the “el salvador” classification and uses this value in matching and reporting.
214 — dominica
Stores the record with the “dominica” classification and uses this value in matching and reporting.
215 — ecuador
Stores the record with the “ecuador” classification and uses this value in matching and reporting.
216 — east timor
Stores the record with the “east timor” classification and uses this value in matching and reporting.
217 — dominican republic
Stores the record with the “dominican republic” classification and uses this value in matching and reporting.
218 — denmark
Stores the record with the “denmark” classification and uses this value in matching and reporting.
219 — djibouti
Stores the record with the “djibouti” classification and uses this value in matching and reporting.
220 — czech republic
Stores the record with the “czech republic” classification and uses this value in matching and reporting.
221 — china
Stores the record with the “china” classification and uses this value in matching and reporting.
222 — united states of america
Stores the record with the “united states of america” classification and uses this value in matching and reporting.
223 — andorra
Stores the record with the “andorra” classification and uses this value in matching and reporting.
224 — albania
Stores the record with the “albania” classification and uses this value in matching and reporting.
225 — nicaragua
Stores the record with the “nicaragua” classification and uses this value in matching and reporting.
226 — norway
Stores the record with the “norway” classification and uses this value in matching and reporting.
227 — niger
Stores the record with the “niger” classification and uses this value in matching and reporting.
228 — nigeria
Stores the record with the “nigeria” classification and uses this value in matching and reporting.
229 — namibia
Stores the record with the “namibia” classification and uses this value in matching and reporting.
230 — nepal
Stores the record with the “nepal” classification and uses this value in matching and reporting.
231 — mauritania
Stores the record with the “mauritania” classification and uses this value in matching and reporting.
232 — mozambique
Stores the record with the “mozambique” classification and uses this value in matching and reporting.
233 — united kingdom
Stores the record with the “united kingdom” classification and uses this value in matching and reporting.
234 — kosovo
Stores the record with the “kosovo” classification and uses this value in matching and reporting.
235 — uzbekistan
Stores the record with the “uzbekistan” classification and uses this value in matching and reporting.
236 — pakistan
Stores the record with the “pakistan” classification and uses this value in matching and reporting.
237 — south korea
Stores the record with the “south korea” classification and uses this value in matching and reporting.
238 — south africa
Stores the record with the “south africa” classification and uses this value in matching and reporting.
239 — guyana
Stores the record with the “guyana” classification and uses this value in matching and reporting.
240 — guatemala
Stores the record with the “guatemala” classification and uses this value in matching and reporting.
241 — guam
Stores the record with the “guam” classification and uses this value in matching and reporting.
242 — guadelup
Stores the record with the “guadelup” classification and uses this value in matching and reporting.
243 — greenland
Stores the record with the “greenland” classification and uses this value in matching and reporting.
244 — grenada
Stores the record with the “grenada” classification and uses this value in matching and reporting.
245 — haiti
Stores the record with the “haiti” classification and uses this value in matching and reporting.
246 — georgia
Stores the record with the “georgia” classification and uses this value in matching and reporting.
247 — solomon islands
Stores the record with the “solomon islands” classification and uses this value in matching and reporting.
248 — isle of man
Stores the record with the “isle of man” classification and uses this value in matching and reporting.
249 — montenegro
Stores the record with the “montenegro” classification and uses this value in matching and reporting.
250 — turkish republic of northern cyprus
Stores the record with the “turkish republic of northern cyprus” classification and uses this value in matching and reporting.
Example: 0 — western sahara
Example:
journey_config['nation_name'] = '0'
Parameter ID: 64
About WDC Campaign / Customer / Journey / Operation
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Customer / Journey / Operation

Tracks one channel delivery, its provider response, and subsequent delivery checks in a single operation record.

Operation flow

If send-API code returns success, the operation is created as active with delivery and customer-success statuses waiting. When the provider returns a delivery identifier, the timer queries the record again; date, counter, duration, response, and status are updated on each check. When follow-up time expires, an indeterminate result is changed to unsuccessful and checking ends.

Code compatibility: Current WDM options must be treated as authoritative. Status mappings for parameter 30 in CampaignConfig are legacy, the channel reader for parameter 38 mistakenly reads parameter 4, and parameter 41 callback status is not used by the standard backend flow.
status
status select

The activity state of the operation record. After a successful provider call, the record is created as active; activity is a record-lifecycle field separate from delivery result and delivery-check result. Although the inspected delivery-check query does not directly filter this field, passive indicates that the operation is out of use.

* Parameter relationships
Parameter: operation_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Classifies the field as “passive”; processes and reports use the selected value.
1 — active
Classifies the field as “active”; processes and reports use the selected value.
Example: 0 — passive
Example:
operation_config['status'] = '0'
Parameter ID: 0
campaign name
campaign name text

The display name of the campaign associated with the operation. Channel processing copies the name from campaign configuration when creating the operation, preserving the context in which the operation was produced even if the campaign record later changes.

* Parameter relationships
Parameter: operation_config['campaign_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: campaign name-example
Example:
operation_config['campaign_name'] = ''
Parameter ID: 1
customer id
customer id text

The source identifier of the customer to whom the message was sent. It is copied from the journey into the operation record and associates delivery, success analysis, and report output with the same customer.

* Parameter relationships
Parameter: operation_config['customer_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: customer id-example
Example:
operation_config['customer_id'] = ''
Parameter ID: 2
provider send api id
provider send api id text

The client identifier of the user API record that sends the message to the provider. It is received from the send-API setting in the channel step; because the code loads API configuration and executes provider code with this identifier, an incorrect or missing identifier prevents delivery.

* Parameter relationships
Parameter: operation_config['provider_send_api_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “provider send api id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: provider send api id-example
Example:
operation_config['provider_send_api_id'] = ''
Parameter ID: 3
campaign type
campaign type select

The business type of the campaign that produced the operation. Digital marketing, survey, or digital advertising is copied into the operation; reporting and type-specific processing use this classification.

* Parameter relationships
Parameter: operation_config['campaign_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — digital marketing
Classifies the field as “digital marketing”; processes and reports use the selected value.
1 — survey
Classifies the field as “survey”; processes and reports use the selected value.
2 — digital advertising
Classifies the field as “digital advertising”; processes and reports use the selected value.
Example: 0 — digital marketing
Example:
operation_config['campaign_type'] = '0'
Parameter ID: 4
customer source
customer source select

Specifies whether the customer came from Wisdomera or the website source. Because it is copied from campaign settings at operation time, operation reports can distinguish acquisition source without rereading the campaign record.

* Parameter relationships
Parameter: operation_config['customer_source']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer source” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — wisdomera
Classifies the field as “wisdomera”; processes and reports use the selected value.
1 — website
Classifies the field as “website”; processes and reports use the selected value.
Example: 0 — wisdomera
Example:
operation_config['customer_source'] = '0'
Parameter ID: 5
advertisement type
advertisement type select

Classifies whether a digital-advertising customer came from a lead form or an appointment source. It is meaningful only in the relevant advertising flow, and the campaign-configuration value is copied into the operation.

* Parameter relationships
Parameter: operation_config['advertisement_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “advertisement type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — lead form
Classifies the field as “lead form”; processes and reports use the selected value.
1 — appointment
Classifies the field as “appointment”; processes and reports use the selected value.
Example: 0 — lead form
Example:
operation_config['advertisement_type'] = '0'
Parameter ID: 6
delivery status
delivery status select

Tracks the result of provider delivery. A new operation is created as `wait`; success analysis or subsequent processing can update it to success, unsuccess, or skip. It is different from parameter 30, which is used for the delivery-check service.

* Parameter relationships
Parameter: operation_config['delivery_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — wait
Sets delivery result to “wait”; delivery checking selects only records that are waiting and have a delivery identifier.
1 — success
Sets delivery result to “success”; delivery checking selects only records that are waiting and have a delivery identifier.
2 — unsuccess
Sets delivery result to “unsuccess”; delivery checking selects only records that are waiting and have a delivery identifier.
3 — skip
Sets delivery result to “skip”; delivery checking selects only records that are waiting and have a delivery identifier.
Example: 0 — wait
Example:
operation_config['delivery_status'] = '0'
Parameter ID: 7
customer success status
customer success status select

The customer’s campaign-success result associated with the operation. A new operation starts as `wait`; customer-success analysis later changes it to success or unsuccess. This field represents achievement of the business objective, not technical message delivery.

* Parameter relationships
Parameter: operation_config['customer_success_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer success status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — wait
Classifies the field as “wait”; processes and reports use the selected value.
1 — success
Classifies the field as “success”; processes and reports use the selected value.
2 — unsuccess
Classifies the field as “unsuccess”; processes and reports use the selected value.
Example: 0 — wait
Example:
operation_config['customer_success_status'] = '0'
Parameter ID: 8
last customer process start date
last customer process start date datetime

The customer-process start time copied from the journey create date when the operation is created. This allows the communication operation to be compared with the time the customer entered the campaign; despite the word “last,” the inspected creation code uses the journey `create_date` value.

* Parameter relationships
Parameter: operation_config['last_customer_process_start_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “last customer process start date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
operation_config['last_customer_process_start_date'] = ''
Parameter ID: 9
create date
create date datetime

The Coordinated Universal Time at which the operation record is created after provider delivery is considered successful. It indicates technical record creation and is written at the same time as operation date.

* Parameter relationships
Parameter: operation_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
operation_config['create_date'] = ''
Parameter ID: 10
update date
update date datetime

Defined to store the last update time of the operation record. The inspected creation and delivery-check code does not write this field automatically; therefore, parameter 29 must be used for check time and this field must not be assumed to populate itself.

* Parameter relationships
Parameter: operation_config['update_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “update date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
operation_config['update_date'] = ''
Parameter ID: 11
webservice response
webservice response textarea

The raw response returned by the delivery provider for the initial API call. If the response is a dictionary it is converted to JSON text; otherwise it is stored as received. It supports error investigation and provider traceability, but its display must be controlled because it may contain sensitive data.

* Parameter relationships
Parameter: operation_config['webservice_response']
Condition: No other parameter option is a prerequisite.
Reason and result: “webservice response” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: {"status":"accepted"}
Example:
operation_config['webservice_response'] = ''
Parameter ID: 12
webservice time (seconds)
webservice time (seconds) integer

The whole-second difference between the start and end of the initial provider-delivery call. Because the code calculates the duration and converts it to an integer, calls shorter than one second may appear as `0`; the value is not the time required for delivery to reach the customer.

* Parameter relationships
Parameter: operation_config['webservice_time_seconds']
Condition: No other parameter option is a prerequisite.
Reason and result: “webservice time (seconds)” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 3
Example:
operation_config['webservice_time_seconds'] = ''
Parameter ID: 13
operation date
operation date datetime

The Coordinated Universal Time at which the channel operation was created and delivery occurred. Delivery follow-up duration is calculated from the hour difference between the current time and this date; an incorrect date causes checking to end too early or too late.

* Parameter relationships
Parameter: operation_config['operation_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “operation date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
operation_config['operation_date'] = ''
Parameter ID: 14
sent message
sent message textarea

The final message content prepared during channel selection and sent to the provider. The operation record copies it from the eligible channel message in the journey, allowing the actual delivered text to be audited even if the template later changes.

* Parameter relationships
Parameter: operation_config['sent_message']
Condition: No other parameter option is a prerequisite.
Reason and result: “sent message” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: sent message-example
Example:
operation_config['sent_message'] = ''
Parameter ID: 15
campaign client id
campaign client id text

The client identifier of the campaign record associated with the operation. Channel processing writes it from campaign configuration; Power BI transfer, delivery-check summary, and reporting use it to group operations under the campaign.

* Parameter relationships
Parameter: operation_config['campaign_client_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign client id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: campaign client id-example
Example:
operation_config['campaign_client_id'] = ''
Parameter ID: 16
campaign wdmr id
campaign wdmr id text

The Wisdom data model record identifier of the campaign record. Unlike the client identifier, it points to the record in the storage layer and is copied from campaign configuration when the operation is created.

* Parameter relationships
Parameter: operation_config['campaign_wdmr_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign wdmr id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: campaign wdmr id-example
Example:
operation_config['campaign_wdmr_id'] = ''
Parameter ID: 17
institution name
institution name text

A copy, at operation time, of the institution name associated with the customer. It provides human-readable context for institution-based providers, reporting, or distribution analysis.

* Parameter relationships
Parameter: operation_config['institution_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “institution name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: institution name-example
Example:
operation_config['institution_name'] = ''
Parameter ID: 18
institution code
institution code text

The source code of the institution associated with the customer. Channel processing copies it from the journey; this code can be used instead of the display name for technical institution-based matching.

* Parameter relationships
Parameter: operation_config['institution_code']
Condition: No other parameter option is a prerequisite.
Reason and result: “institution code” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: institution code-example
Example:
operation_config['institution_code'] = ''
Parameter ID: 19
utm source
utm source text

The UTM source value defined to identify the digital traffic source. The inspected standard channel-operation creation code does not write this field; it can be used in reporting only if another integration or update flow supplies it.

* Parameter relationships
Parameter: operation_config['utm_source']
Condition: No other parameter option is a prerequisite.
Reason and result: “utm source” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: utm source-example
Example:
operation_config['utm_source'] = ''
Parameter ID: 20
integrated system id
integrated system id text

The identifier of the external or integrated-system record associated with the operation. Because no automatic write was found in the inspected standard delivery and delivery-check flow, population of this field depends on the relevant integration.

* Parameter relationships
Parameter: operation_config['integrated_system_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “integrated system id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: integrated system id-example
Example:
operation_config['integrated_system_id'] = ''
Parameter ID: 21
survey link
survey link text

A copy, at operation time, of the survey link generated in the journey. Because a survey-campaign message can contain this link, the operation record preserves which address was used in the delivery context.

* Parameter relationships
Parameter: operation_config['survey_link']
Condition: No other parameter option is a prerequisite.
Reason and result: “survey link” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: survey link-example
Example:
operation_config['survey_link'] = ''
Parameter ID: 22
survey system id
survey system id text

A copy, at operation time, of the survey-system identifier in the journey. It helps associate the delivered link and subsequent survey operations with the correct survey record.

* Parameter relationships
Parameter: operation_config['survey_system_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “survey system id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: survey system id-example
Example:
operation_config['survey_system_id'] = ''
Parameter ID: 23
phone number
phone number text

A copy, at operation time, of the customer number used for a phone-based channel. The code writes the GSM value from the journey here, making it possible to trace which target received SMS, IVR, or phone-call operations.

* Parameter relationships
Parameter: operation_config['phone_number']
Condition: No other parameter option is a prerequisite.
Reason and result: “phone number” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: phone number-example
Example:
operation_config['phone_number'] = ''
Parameter ID: 24
mail
mail text

A copy, at operation time, of the customer email address used for the email channel. It is transferred from the journey and associates the delivery result with the target address.

* Parameter relationships
Parameter: operation_config['mail']
Condition: No other parameter option is a prerequisite.
Reason and result: “mail” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: mail-example
Example:
operation_config['mail'] = ''
Parameter ID: 25
mobile notification id
mobile notification id text

The device or subscription identifier targeted by push-notification delivery. It is copied from the journey into the operation and identifies the mobile target for which the provider response was produced.

* Parameter relationships
Parameter: operation_config['mobile_notification_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “mobile notification id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: mobile notification id-example
Example:
operation_config['mobile_notification_id'] = ''
Parameter ID: 26
mobile notification group id
mobile notification group id text

The group identifier associated with the push-notification target. It is copied from the journey into the operation to preserve targeting context for group-based mobile delivery.

* Parameter relationships
Parameter: operation_config['mobile_notification_group_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “mobile notification group id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: mobile notification group id-example
Example:
operation_config['mobile_notification_group_id'] = ''
Parameter ID: 27
delivery check id
delivery check id text

The message identifier returned by the initial delivery provider and used in later delivery queries. The timer checks only operations whose delivery status is wait and whose field is populated; without this identifier, the operation does not enter the automatic delivery-check query.

* Parameter relationships
Parameter: operation_config['delivery_check_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery check id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: delivery check id-example
Example:
operation_config['delivery_check_id'] = ''
Parameter ID: 28
delivery last check date
delivery last check date datetime

The Coordinated Universal Time at which the delivery-check service last ran. It is refreshed with the current time on every result write, making the latest query time visible together with the check count.

* Parameter relationships
Parameter: operation_config['delivery_last_check_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery last check date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
operation_config['delivery_last_check_date'] = ''
Parameter ID: 29
delivery check status
delivery check status select

The current result of the delivery-check service; the value returned by provider check code is written directly as a WDM option. In the current schema it represents unsuccessful, success, authentication error, delivery identifier not found, checking continues, or no service response. Because legacy `CampaignConfig` mappings use different meanings, WDM values must be treated as authoritative when reading this field.

* Parameter relationships
Parameter: operation_config['delivery_check_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery check status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — unsuccess
Records the latest delivery-check result as “unsuccess”.
1 — success
Records the latest delivery-check result as “success”.
2 — incorrect username or password
Records the latest delivery-check result as “incorrect username or password”.
3 — delivery id not found
Records the latest delivery-check result as “delivery id not found”.
4 — delivery check continue
Records the latest delivery-check result as “delivery check continue”.
5 — no response from service
Records the latest delivery-check result as “no response from service”.
Example: 0 — unsuccess
Example:
operation_config['delivery_check_status'] = '0'
Parameter ID: 30
undelivered reason
undelivered reason select

Classifies why the message could not be delivered. The field is updated when provider check code returns a failure reason; the detailed provider explanation is stored separately in parameter 32.

* Parameter relationships
Parameter: operation_config['undelivered_reason']
Condition: No other parameter option is a prerequisite.
Reason and result: “undelivered reason” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — faulty
Classifies the field as “faulty”; processes and reports use the selected value.
1 — timeout or mms rejected
Classifies the field as “timeout or mms rejected”; processes and reports use the selected value.
2 — timeout
Classifies the field as “timeout”; processes and reports use the selected value.
3 — mms rejected
Classifies the field as “mms rejected”; processes and reports use the selected value.
4 — blacklisted
Classifies the field as “blacklisted”; processes and reports use the selected value.
5 — mms rejected or no mms approval code
Classifies the field as “mms rejected or no mms approval code”; processes and reports use the selected value.
Example: 0 — faulty
Example:
operation_config['undelivered_reason'] = '0'
Parameter ID: 31
undelivered reason information
undelivered reason information textarea

The detailed text for the non-delivery reason returned by the provider or check code. It complements the category in parameter 31 with a technical message; display permission must be restricted because it may contain raw error information or personal data.

* Parameter relationships
Parameter: operation_config['undelivered_reason_information']
Condition: No other parameter option is a prerequisite.
Reason and result: “undelivered reason information” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: undelivered reason information-example
Example:
operation_config['undelivered_reason_information'] = ''
Parameter ID: 32
delivery check count
delivery check count integer

Shows how many times the delivery-check service has run for the operation. It is written as `1` on the first check and incremented after each subsequent result; the counter advances only when a check result is produced and the record is updated.

* Parameter relationships
Parameter: operation_config['delivery_check_count']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery check count” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 3
Example:
operation_config['delivery_check_count'] = ''
Parameter ID: 33
delivery check follow-up time (hour)
delivery check follow-up time (hour) integer

The maximum follow-up duration returned by provider check code. The code treats the value as hours and sets parameter 37, time-ended status, to `yes` when whole hours elapsed since operation date exceed this limit; zero or empty does not enable expiration calculation.

* Parameter relationships
Parameter: operation_config['delivery_check_follow_up_time_hour']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery check follow-up time (hour)” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 3
Example:
operation_config['delivery_check_follow_up_time_hour'] = ''
Parameter ID: 34
delivery check webservice time (seconds)
delivery check webservice time (seconds) integer

The duration, in seconds, of one delivery-check webservice call. The difference between its start and end times is recorded; this field is separate from parameter 13, the initial delivery duration.

* Parameter relationships
Parameter: operation_config['delivery_check_webservice_time_seconds']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery check webservice time (seconds)” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 3
Example:
operation_config['delivery_check_webservice_time_seconds'] = ''
Parameter ID: 35
delivery check webservice response
delivery check webservice response textarea

The raw response returned by the delivery-check provider for the latest query. When check code returns a value, the record is updated and the latest response is preserved for technical investigation; this field is separate from parameter 12, the initial-delivery response.

* Parameter relationships
Parameter: operation_config['delivery_check_webservice_response']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery check webservice response” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: delivery check webservice response-example
Example:
operation_config['delivery_check_webservice_response'] = ''
Parameter ID: 36
delivery check time end status
delivery check time end status select

Specifies whether the configured follow-up period for the message has expired. It is set to `yes` when elapsed hours exceed the follow-up duration; if the check result is neither success nor unsuccess at that point, the code changes parameter 30 to unsuccessful to end indefinite checking.

* Parameter relationships
Parameter: operation_config['delivery_check_time_end_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery check time end status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — no
Indicates that follow-up time has not yet expired.
1 — yes
Indicates that follow-up time has expired and continuing indeterminate checks will end.
Example: 0 — no
Example:
operation_config['delivery_check_time_end_status'] = '0'
Parameter ID: 37
channel type
channel type select

Specifies whether the operation was produced through SMS, push notification, IVR, email, or phone call. The type from the channel step is copied into the operation and determines how target contact fields and provider behavior are interpreted. The `CampaignConfig` reader mistakenly reads parameter 4, campaign type, instead of this field; the direct WDM value is the reliable source.

* Parameter relationships
Parameter: operation_config['channel_type']
Condition: No other parameter option is a prerequisite.
Reason and result: “channel type” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — sms
Classifies the field as “sms”; processes and reports use the selected value.
1 — push notification
Classifies the field as “push notification”; processes and reports use the selected value.
2 — ivr
Classifies the field as “ivr”; processes and reports use the selected value.
3 — mail
Classifies the field as “mail”; processes and reports use the selected value.
4 — phone call
Classifies the field as “phone call”; processes and reports use the selected value.
Example: 0 — sms
Example:
operation_config['channel_type'] = '0'
Parameter ID: 38
provider delivery check api id
provider delivery check api id text

The client identifier of the user API record that queries delivery result with the message identifier. It is copied from the channel step into the operation; check code runs only when both the identifier and API code exist, and no automatic check result can be produced if either is missing.

* Parameter relationships
Parameter: operation_config['provider_delivery_check_api_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “provider delivery check api id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: provider delivery check api id-example
Example:
operation_config['provider_delivery_check_api_id'] = ''
Parameter ID: 39
channel design id
channel design id text

The client identifier of the campaign channel-design record that produced the operation. It is copied from the selected eligible channel setting and makes the source of message, provider, and step configuration traceable.

* Parameter relationships
Parameter: operation_config['channel_design_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “channel design id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: channel design id-example
Example:
operation_config['channel_design_id'] = ''
Parameter ID: 40
delivery callback status
delivery callback status select

A field present in the WDM schema to classify the business result of phone or call-center feedback. However, an inspected backend comment marks the field as “no longer present,” the operation configuration reader does not read parameter 41, and standard creation and checking flows do not write it; therefore, it must not be assumed to update automatically.

* Parameter relationships
Parameter: operation_config['delivery_callback_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “delivery callback status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — information provided
Classifies the field as “information provided”; processes and reports use the selected value.
1 — check-up given
Classifies the field as “check-up given”; processes and reports use the selected value.
2 — check-up sale made
Classifies the field as “check-up sale made”; processes and reports use the selected value.
3 — complaint, request, suggestion
Classifies the field as “complaint, request, suggestion”; processes and reports use the selected value.
4 — appointment given
Classifies the field as “appointment given”; processes and reports use the selected value.
5 — unreachable
Classifies the field as “unreachable”; processes and reports use the selected value.
6 — unanswered
Classifies the field as “unanswered”; processes and reports use the selected value.
7 — incorrect number
Classifies the field as “incorrect number”; processes and reports use the selected value.
8 — will be called later
Classifies the field as “will be called later”; processes and reports use the selected value.
Example: 0 — information provided
Example:
operation_config['delivery_callback_status'] = '0'
Parameter ID: 41
About WDC Campaign / Survey Settings
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Survey Settings

Defines predefined and manual questions, answers, and ordering for a campaign survey generated by WDC.

Survey-generation flow

The first active settings record is selected. Predefined questions are prepared with fixed five-point satisfaction answers, while active manual questions are prepared with their type and active answers. Order JSON arranges questions; when general opinion is enabled, a fixed textarea question is appended last.

Code finding: WDM values and backend mapping for question type disagree for values 5 and 6. In addition, create date is rewritten on every save while update date is not written.
status
status select

The availability state of the survey-settings record. When a WDC survey link is created, settings under the campaign are inspected in sequence; questions are prepared from the first active record and the loop then stops, while a passive record contributes nothing to the survey payload.

* Parameter relationships
Parameter: survey_settings_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Excludes this setting from survey generation.
1 — active
Makes this setting eligible for survey generation; the first active record is selected.
Example: 0 — passive
Example:
survey_settings_config['status'] = '0'
Parameter ID: 0
question list
question list checkbox

The multiple selection of questions to include from the predefined question catalog. Each selected option uses its value as the question identifier and its translated text as the question label, and the backend adds the same five answers, identified 1–5 from “very dissatisfied” to “very satisfied,” to every predefined question; therefore, predefined questions are produced as select questions.

* Parameter relationships
Parameter: survey_settings_config['question_list']
Condition: No other parameter option is a prerequisite.
Reason and result: “question list” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — how likely are you to recommend our service to others?
Adds the predefined “how likely are you to recommend our service to others?” question to the survey with the fixed five-point satisfaction answers.
1 — how would you rate the service you received overall?
Adds the predefined “how would you rate the service you received overall?” question to the survey with the fixed five-point satisfaction answers.
2 — how satisfied were you with the doctor's service?
Adds the predefined “how satisfied were you with the doctor's service?” question to the survey with the fixed five-point satisfaction answers.
3 — how would you rate the reception and registration process?
Adds the predefined “how would you rate the reception and registration process?” question to the survey with the fixed five-point satisfaction answers.
4 — how satisfied were you with the nursing services?
Adds the predefined “how satisfied were you with the nursing services?” question to the survey with the fixed five-point satisfaction answers.
5 — how would you rate the beautician's service?
Adds the predefined “how would you rate the beautician's service?” question to the survey with the fixed five-point satisfaction answers.
6 — were you satisfied with the podologist's service?
Adds the predefined “were you satisfied with the podologist's service?” question to the survey with the fixed five-point satisfaction answers.
7 — how would you rate the cleaning services?
Adds the predefined “how would you rate the cleaning services?” question to the survey with the fixed five-point satisfaction answers.
8 — how satisfied were you with the food services?
Adds the predefined “how satisfied were you with the food services?” question to the survey with the fixed five-point satisfaction answers.
9 — how would you rate the admission and discharge process?
Adds the predefined “how would you rate the admission and discharge process?” question to the survey with the fixed five-point satisfaction answers.
10 — were you satisfied with the parking services?
Adds the predefined “were you satisfied with the parking services?” question to the survey with the fixed five-point satisfaction answers.
11 — how would you rate the valet parking service?
Adds the predefined “how would you rate the valet parking service?” question to the survey with the fixed five-point satisfaction answers.
12 — how satisfied were you with the sleep technician's service?
Adds the predefined “how satisfied were you with the sleep technician's service?” question to the survey with the fixed five-point satisfaction answers.
13 — how would you rate the service provided by the embryologist?
Adds the predefined “how would you rate the service provided by the embryologist?” question to the survey with the fixed five-point satisfaction answers.
14 — how satisfied were you with the physiotherapist's service?
Adds the predefined “how satisfied were you with the physiotherapist's service?” question to the survey with the fixed five-point satisfaction answers.
15 — how would you rate the facilities of the breastfeeding room?
Adds the predefined “how would you rate the facilities of the breastfeeding room?” question to the survey with the fixed five-point satisfaction answers.
16 — were you satisfied with the service provided by the eye technician?
Adds the predefined “were you satisfied with the service provided by the eye technician?” question to the survey with the fixed five-point satisfaction answers.
17 — how would you rate the blood sampling process?
Adds the predefined “how would you rate the blood sampling process?” question to the survey with the fixed five-point satisfaction answers.
18 — how would you rate the cafeteria services?
Adds the predefined “how would you rate the cafeteria services?” question to the survey with the fixed five-point satisfaction answers.
19 — how would you rate the anesthesia process?
Adds the predefined “how would you rate the anesthesia process?” question to the survey with the fixed five-point satisfaction answers.
20 — were you satisfied with the service provided by the dental technician?
Adds the predefined “were you satisfied with the service provided by the dental technician?” question to the survey with the fixed five-point satisfaction answers.
21 — how would you rate the in-clinic coordination and guidance?
Adds the predefined “how would you rate the in-clinic coordination and guidance?” question to the survey with the fixed five-point satisfaction answers.
22 — what was your experience with the mobile application?
Adds the predefined “what was your experience with the mobile application?” question to the survey with the fixed five-point satisfaction answers.
23 — how satisfied were you with the service of the radiotherapy team?
Adds the predefined “how satisfied were you with the service of the radiotherapy team?” question to the survey with the fixed five-point satisfaction answers.
24 — how would you rate the process of sharing results and discussing results?
Adds the predefined “how would you rate the process of sharing results and discussing results?” question to the survey with the fixed five-point satisfaction answers.
25 — to what extent were you satisfied with the resolution process of your complaints?
Adds the predefined “to what extent were you satisfied with the resolution process of your complaints?” question to the survey with the fixed five-point satisfaction answers.
26 — how would you rate your experience using the website?
Adds the predefined “how would you rate your experience using the website?” question to the survey with the fixed five-point satisfaction answers.
27 — how did you find the process of submitting your complaints and receiving feedback?
Adds the predefined “how did you find the process of submitting your complaints and receiving feedback?” question to the survey with the fixed five-point satisfaction answers.
28 — how would you rate the in-hospital guidance and transfer process?
Adds the predefined “how would you rate the in-hospital guidance and transfer process?” question to the survey with the fixed five-point satisfaction answers.
29 — were you satisfied with the video clinic (remote consultation) service?
Adds the predefined “were you satisfied with the video clinic (remote consultation) service?” question to the survey with the fixed five-point satisfaction answers.
30 — how would you rate the content and scope of the check-up?
Adds the predefined “how would you rate the content and scope of the check-up?” question to the survey with the fixed five-point satisfaction answers.
31 — what was your experience communicating with the call center?
Adds the predefined “what was your experience communicating with the call center?” question to the survey with the fixed five-point satisfaction answers.
32 — how would you rate the appointment and service scheduling?
Adds the predefined “how would you rate the appointment and service scheduling?” question to the survey with the fixed five-point satisfaction answers.
33 — to what extent were you satisfied with the service of the radiology technician?
Adds the predefined “to what extent were you satisfied with the service of the radiology technician?” question to the survey with the fixed five-point satisfaction answers.
Example: 0 — how likely are you to recommend our service to others?
Example:
survey_settings_config['question_list'] = [{'question_type': 'template', 'id': '', 'order': 0}]
Parameter ID: 1
create date
create date datetime

The Coordinated Universal Time at which the settings record is saved. The record service rewrites this field with the current time for both creation and update requests; therefore, in the current implementation it behaves like the latest save time rather than an immutable original creation time.

* Parameter relationships
Parameter: survey_settings_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
survey_settings_config['create_date'] = ''
Parameter ID: 2
update date
update date datetime

Defined to store the last update time of the settings record. The line that would write this field is commented out in record code, and the field is not used by the read or survey-generation flow; therefore, it must not be assumed to populate automatically in the current standard flow.

* Parameter relationships
Parameter: survey_settings_config['update_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “update date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
survey_settings_config['update_date'] = ''
Parameter ID: 3
manuel question list
manuel question list list_parameter

A repeating list that stores questions defined outside the predefined catalog. Each row contains status, identifier, type, multilingual label, and an answer list when required; only active rows enter the payload during survey creation, and if an identifier conflicts with another predefined or manual question, the later entry can replace the earlier one in the question map.

* Parameter relationships
Parameter: survey_settings_config['question_list']
Condition: No other parameter option is a prerequisite.
Reason and result: “manuel question list” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
survey_settings_config['question_list'] = [{'question_type': 'manuel', 'status': '1', 'id': '', 'order': 0, 'type': '', 'label': {'tr': '', 'en': ''}, 'answer_list': [{'status': '1', 'id': '', 'label': {'tr': '', 'en': ''}}]}]
Parameter ID: 4
question status
question status select

Determines whether a manual-question row is included in the survey. An `active` row is processed; for other values the code skips the row directly, so the question and its answers do not appear in the generated survey even if they and order information remain in the settings record.

* Parameter relationships
Parameter: survey_settings_config['question_list'][0]['status']
Condition: The related survey_settings_config['question_list'] list item must exist.
Reason and result: “question status” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — passive
Keeps the row in settings but excludes it from the generated survey.
1 — active
Includes the row in the generated survey.
Example: 0 — passive
Example:
survey_settings_config['question_list'][0]['status'] = '0'
Parameter ID: 5
question id
question id text

The identifier of the manual question within the survey. Instead of retaining an incoming identifier, the record service regenerates it as `m_0`, `m_1`, and so on from the manual-question counter; survey-preparation code creates a fallback identifier with the same pattern if the field is empty. Because the order list also uses this identifier as its key, changing it affects ordering.

* Parameter relationships
Parameter: survey_settings_config['question_list'][0]['id']
Condition: The related survey_settings_config['question_list'] list item must exist.
Reason and result: “question id” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: question id-example
Example:
survey_settings_config['question_list'][0]['id'] = ''
Parameter ID: 6
question type
question type select

Determines the answer component of a manual question. Current WDM options provide select, int, float, text, textarea, date, and datetime from values 0–6; however, backend mapping interprets value 5 as checkbox, value 6 as date, and schema-absent value 7 as datetime. Therefore, with the current code, choosing WDM `date` produces a checkbox, choosing `datetime` produces a date field, and there is no selectable value that produces a true datetime field.

* Parameter relationships
Parameter: survey_settings_config['question_list'][0]['type']
Condition: The related survey_settings_config['question_list'] list item must exist.
Reason and result: “question type” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — select
The WDM option is “select”; for values 5 and 6, the backend offset produces the behavior described above.
1 — int
The WDM option is “int”; for values 5 and 6, the backend offset produces the behavior described above.
2 — float
The WDM option is “float”; for values 5 and 6, the backend offset produces the behavior described above.
3 — text
The WDM option is “text”; for values 5 and 6, the backend offset produces the behavior described above.
4 — textarea
The WDM option is “textarea”; for values 5 and 6, the backend offset produces the behavior described above.
5 — date
The WDM option is “date”; for values 5 and 6, the backend offset produces the behavior described above.
6 — datetime
The WDM option is “datetime”; for values 5 and 6, the backend offset produces the behavior described above.
Example: 0 — select
Example:
survey_settings_config['question_list'][0]['type'] = '0'
Parameter ID: 7
question label
question label text

The multilingual text of the manual question shown to the user. The record service writes the current interface-language value to the main `val` field and all translations to the `lang` object; because survey-generation code reads the label from `lang`, the question text can be missing in a language whose translation is absent.

* Parameter relationships
Parameter: survey_settings_config['question_list'][0]['label']
Condition: The related survey_settings_config['question_list'] list item must exist.
Reason and result: “question label” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: question label-example
Example:
survey_settings_config['question_list'][0]['label'] = {'tr': '', 'en': ''}
Parameter ID: 8
answer list
answer list list_parameter

A repeating list that stores possible answers for a select-type manual question. The backend processes this list only when the question type resolves to `select`; even if the list contains data for int, float, text, textarea, date, or datetime types, answer options are not added to the payload.

* Parameter relationships
Parameter: survey_settings_config['question_list'][0]['answer_list']
Condition: The related survey_settings_config['question_list'] list item must exist.
Reason and result: “answer list” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: [{ ... }]
Example:
survey_settings_config['question_list'][0]['answer_list'] = [{'status': '1', 'id': '', 'label': {'tr': '', 'en': ''}}]
Parameter ID: 9
answer status
answer status select

Determines availability of a manual answer option in the survey. Only `active` answers are added to the select question’s `answers` array; a passive answer may remain in the record but is not shown to the user as an option.

* Parameter relationships
Parameter: survey_settings_config['question_list'][0]['answer_list'][0]['status']
Condition: The related survey_settings_config['question_list'] list item must exist.
Reason and result: “answer status” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — passive
Keeps the row in settings but excludes it from the generated survey.
1 — active
Includes the row in the generated survey.
Example: 0 — passive
Example:
survey_settings_config['question_list'][0]['answer_list'][0]['status'] = '0'
Parameter ID: 10
answer id
answer id text

The identifier of the manual answer within its question. The record service renumbers answers as `0`, `1`, `2`, and so on according to their zero-based list index; therefore, reordering answers can also change their identifiers and they must not be treated as persistent external business identifiers.

* Parameter relationships
Parameter: survey_settings_config['question_list'][0]['answer_list'][0]['id']
Condition: The related survey_settings_config['question_list'] list item must exist.
Reason and result: “answer id” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: answer id-example
Example:
survey_settings_config['question_list'][0]['answer_list'][0]['id'] = ''
Parameter ID: 11
answer label
answer label text

The multilingual text of a manual answer option shown to the user. The main value is saved from the active interface language and translations are saved in the `lang` object; because the survey payload uses the `lang` object, a value should be supplied for every target language.

* Parameter relationships
Parameter: survey_settings_config['question_list'][0]['answer_list'][0]['label']
Condition: The related survey_settings_config['question_list'] list item must exist.
Reason and result: “answer label” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: answer label-example
Example:
survey_settings_config['question_list'][0]['answer_list'][0]['label'] = {'tr': '', 'en': ''}
Parameter ID: 12
add general opinion text
add general opinion text select

Determines whether a free-text general-opinion question is appended to the survey. When `yes` is selected, the backend appends a fixed Turkish and English question with identifier `35` and type `textarea` to the end of the payload; because it is added after ordering rather than through the order list, it always appears last.

* Parameter relationships
Parameter: survey_settings_config['add_general_opinion']
Condition: No other parameter option is a prerequisite.
Reason and result: “add general opinion text” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — no
Does not add a general-opinion question.
1 — yes
Appends the fixed general-opinion textarea question to the end of the survey.
Example: 0 — no
Example:
survey_settings_config['add_general_opinion'] = '0'
Parameter ID: 13
order list
order list text

A JSON object that maps predefined and manual question identifiers to their display order, for example `{"0":"1","m_0":"2"}`. The record service builds this object from each question’s `order` value, survey-generation code converts values to integers, sorts ascending, and includes only identifiers present in the question map. If JSON is invalid, the order list is treated as empty and questions are used in their insertion order.

* Parameter relationships
Parameter: survey_settings_config['order_list']
Condition: No other parameter option is a prerequisite.
Reason and result: “order list” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: {"0":"1","m_0":"2"}
Example:
survey_settings_config['order_list'] = {}
Parameter ID: 14
About WDC Campaign / Lead Form
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Lead Form

Tracks resolution of a digital-advertising lead through phone or customer identifier and its conversion into a customer journey.

Lead-tracking flow

When a direct customer identifier exists, customer, journey, and operation creation starts. With only a phone number, the campaign’s phone-lookup API code runs; if no identifier is found the record waits, and if one is found or follow-up time expires the record completes.

Code findings: The method call in daily rechecking does not match the current signature. In addition, the multiple-phone-match loop passes the old customer identifier to the central method instead of the newly found identifier. These two paths must be fixed before automatic follow-up is used in production.
status
status select

The activity state of the lead-tracking record. A tracking record created through the phone flow is written as active; the timer is intended to reevaluate only records whose status is `active` and customer status is `wait`. If passive is selected, the record does not satisfy this processing condition.

* Parameter relationships
Parameter: lead_form_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Excludes the record from the active tracking condition.
1 — active
Makes the record eligible for the active tracking condition.
Example: 0 — passive
Example:
lead_form_config['status'] = '0'
Parameter ID: 0
campaign name
campaign name text

Defined to store the display name of the campaign associated with the lead. The inspected lead tracking create/update method does not write this field, and the timer does not read the campaign name from it; therefore, it must not be assumed to populate automatically in the standard phone-tracking flow.

* Parameter relationships
Parameter: lead_form_config['campaign_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: campaign name-example
Example:
lead_form_config['campaign_name'] = ''
Parameter ID: 1
customer status
customer status select

Specifies whether a source customer identifier has been found from the phone number and whether follow-up should continue. `wait` is written when no identifier is found; `completed` is written when one or more identifiers are found, processing completes with a direct customer identifier, or the final check of the maximum follow-up period is reached. A completed record must not be checked again.

* Parameter relationships
Parameter: lead_form_config['customer_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — wait
Indicates that the customer was not found and daily follow-up should continue.
1 — completed
Indicates that the customer was found or the final check occurred and follow-up should end.
Example: 0 — wait
Example:
lead_form_config['customer_status'] = '0'
Parameter ID: 2
campaign client id
campaign client id text

The client identifier of the campaign that owns the lead. The tracking record is stored under the campaign with this identifier, and the timer query selects only records with the same campaign identifier; an incorrect value can cause the lead to be processed with another campaign’s settings or not found.

* Parameter relationships
Parameter: lead_form_config['campaign_client_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign client id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: campaign client id-example
Example:
lead_form_config['campaign_client_id'] = ''
Parameter ID: 3
operation date
operation date datetime

The date and time at which the lead event occurred. If the API request supplies an operation date it is used; otherwise, current Coordinated Universal Time is written. The correct date is important because reacceptance eligibility and the end of the maximum customer-success follow-up period are calculated from this time context.

* Parameter relationships
Parameter: lead_form_config['operation_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “operation date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
lead_form_config['operation_date'] = ''
Parameter ID: 4
last check date
last check date datetime

The Coordinated Universal Time at which phone-to-customer matching was last attempted. It is refreshed with the current time whenever the tracking record is written; the timer is intended to add one day to this date and check the record again after the current time passes that threshold. The current timer call does not match the current method signature, so automatic retry requires a code fix.

* Parameter relationships
Parameter: lead_form_config['last_check_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “last check date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
lead_form_config['last_check_date'] = ''
Parameter ID: 5
institution code
institution code text

The source code of the institution associated with the lead. It is carried from the request to the tracking record, then to the institution code of the customer journey and the created channel operation; therefore, the same context is preserved for institution-based reporting and success matching.

* Parameter relationships
Parameter: lead_form_config['institution_code']
Condition: No other parameter option is a prerequisite.
Reason and result: “institution code” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: institution code-example
Example:
lead_form_config['institution_code'] = ''
Parameter ID: 6
website link
website link text

The direct link of the web page from which the lead originated. According to the code comment it is stored as a URL and preserved during tracking; however, the line that would write it into the customer journey operation is commented out, so it is not transferred to the operation layer in the standard flow.

* Parameter relationships
Parameter: lead_form_config['website_link']
Condition: No other parameter option is a prerequisite.
Reason and result: “website link” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: website link-example
Example:
lead_form_config['website_link'] = ''
Parameter ID: 7
utm source
utm source text

The UTM source value that identifies the acquisition source of the lead, such as Google, Facebook, or Instagram. It is preserved in the tracking record and copied to the operation’s UTM source field when a customer identifier is resolved and a channel operation is created, allowing digital-advertising success to be distinguished by source.

* Parameter relationships
Parameter: lead_form_config['utm_source']
Condition: No other parameter option is a prerequisite.
Reason and result: “utm source” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: utm source-example
Example:
lead_form_config['utm_source'] = ''
Parameter ID: 8
phone number
phone number text

The phone number used to search for the customer in the source system. When the request does not contain a customer identifier, this field becomes the required alternative; the campaign’s customer-list-by-phone API code can use it to return one or more customer identifiers. The tracking-record client identifier is also based on a combination of campaign identifier and phone number.

* Parameter relationships
Parameter: lead_form_config['phone_number']
Condition: No other parameter option is a prerequisite.
Reason and result: “phone number” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: +905321234567
Example:
lead_form_config['phone_number'] = ''
Parameter ID: 9
integrated system customer id
integrated system customer id text

The customer or record identifier of the lead in an external or integrated system. It is received from the request query, stored in the tracking record, and transferred to the channel operation’s integrated-system identifier when the customer identifier is resolved; it is different from parameter 14, the platform customer identifier.

* Parameter relationships
Parameter: lead_form_config['integrated_system_customer_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “integrated system customer id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: integrated system customer id-example
Example:
lead_form_config['integrated_system_customer_id'] = ''
Parameter ID: 10
create date
create date datetime

Defined to store the time at which the lead-tracking record was first created. The inspected `f_updateProjectLeadFormLogWdmr` method does not write this field or use it for follow-up scheduling; because it may remain empty in the standard flow, it must not be used instead of operation date or last check date.

* Parameter relationships
Parameter: lead_form_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
lead_form_config['create_date'] = ''
Parameter ID: 11
update date
update date datetime

Defined to store the last data-update time of the lead-tracking record. The inspected record and timer code does not write this field; because actual check updates are tracked through parameter 5, last check date, this field must not be assumed to populate automatically.

* Parameter relationships
Parameter: lead_form_config['update_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “update date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
lead_form_config['update_date'] = ''
Parameter ID: 12
country phone code
country phone code text

The country calling code of the phone number. It is received from the lead request and preserved when the tracking record is rewritten; customer lookup API code can use it to normalize the number by country or query the correct source, but it is not a complete phone number by itself.

* Parameter relationships
Parameter: lead_form_config['country_phone_code']
Condition: No other parameter option is a prerequisite.
Reason and result: “country phone code” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: country phone code-example
Example:
lead_form_config['country_phone_code'] = ''
Parameter ID: 13
customer id
customer id text

The platform customer identifier found by phone matching or supplied directly in the API request. When a direct value exists, customer, journey, and operation creation starts immediately; if no value is found in the phone flow, the record remains waiting. The inspected multiple-phone-result loop passes the old `customer_id` variable to the central method instead of the found `new_customer_id`, so this path must be verified to carry the correct identifier and the code must be fixed.

* Parameter relationships
Parameter: lead_form_config['customer_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “customer id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: customer id-example
Example:
lead_form_config['customer_id'] = ''
Parameter ID: 14
About WDC Campaign / Channel Design
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Channel Design

Defines the permission, institution, and nationality conditions under which a journey proceeds through ordered channel steps.

Selection and step flow

Only active designs are evaluated. When all required permissions, institution filter, and nationality filter are eligible together, the channel step corresponding to the number of previous operations is selected. Next-step time is calculated by adding an hour or day period to the previous operation date.

Code findings: Excluded institution/nationality lists are lost during save, HTML message type cannot be selected because of a value mismatch, and WhatsApp/language fields are not processed in the current step save/read flow. Timestamps are also mistakenly written to top-level fields 26/27 instead of 23/24.
status
status select

The availability state of the channel design. Eligible-channel selection evaluates only active designs; a passive design is not selected for a journey even when permissions, institution, nationality, and channel steps are configured.

* Parameter relationships
Parameter: channel_design_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Excludes the design from eligible-channel selection.
1 — active
Makes the design available to eligible-channel selection.
Example: 0 — passive
Example:
channel_design_config['status'] = '0'
Parameter ID: 0
channel permission type
channel permission type select

Determines whether customer permissions are checked for channel eligibility. When checking is disabled, the permission condition is accepted directly and dependent permission fields are removed during save; when enabled, every permission selected in parameter 2 must match its own list of accepted states.

* Parameter relationships
Parameter: channel_design_config['channel_permission_type']
Condition: This parameter itself has no prerequisite parameter.
Reason and result: Determines whether permission filters are used. With '0' — “don't check permissions” , channel_design_config['required_permissions'] and detailed permission fields are removed from the form/record. With '1' — “check permissions” , those fields become available.
Options and usage purposes
0 — dont check permissions
Interprets the field as “dont check permissions”; the related filter or step operates according to this value.
1 — check permissions
Interprets the field as “check permissions”; the related filter or step operates according to this value.
Example: 0 — dont check permissions
Example:
channel_design_config['channel_permission_type'] = '0'
Parameter ID: 1
required permissions
required permissions checkbox

The permission categories that must be satisfied together before the channel can be used. The algorithm checks selected permissions in sequence and rejects the design when any permission is not present in its corresponding accepted-state list in parameters 3–7; therefore, the logic is “all selected,” not “any selected.”

* Parameter relationships
Parameter: channel_design_config['required_permissions']
Condition: channel_design_config['channel_permission_type'] = '1' ; option '1' means “check permissions” .
Reason and result: Determines the permission categories to check: '0' “legal data processing” , '1' “legal contact” , '2' “SMS” , '3' “mail” , and '4' “phone call” . Detailed accept/reject fields are enabled and persisted only for categories selected here.
Options and usage purposes
0 — legal data processing
Makes the “legal data processing” category required; the channel is rejected if its accepted-state list does not match.
1 — legal contact
Makes the “legal contact” category required; the channel is rejected if its accepted-state list does not match.
2 — sms
Makes the “sms” category required; the channel is rejected if its accepted-state list does not match.
3 — mail
Makes the “mail” category required; the channel is rejected if its accepted-state list does not match.
4 — phone call
Makes the “phone call” category required; the channel is rejected if its accepted-state list does not match.
Example: 0 — legal data processing
Example:
channel_design_config['required_permissions'] = []
Parameter ID: 2
legal data processing permission
legal data processing permission checkbox

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “legal data processing permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

* Parameter relationships
Parameter: channel_design_config['legal_data_processing_permission']
Condition: channel_design_config['channel_permission_type'] = '1' ( “check permissions” ) and option '0' — “legal data processing” must be present in channel_design_config['required_permissions'] .
Reason and result: When both conditions hold, this field selects which accepted/rejected states of the legal data processing permission are eligible for the channel. If either condition fails, the field is removed from the form and record.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; the related filter or step operates according to this value.
1 — approved
Interprets the field as “approved”; the related filter or step operates according to this value.
2 — awaiting approval
Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 — missing
Interprets the field as “missing”; the related filter or step operates according to this value.
Example: 0 — rejected
Example:
channel_design_config['legal_data_processing_permission'] = []
Parameter ID: 3
legal communication permission
legal communication permission checkbox

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “legal communication permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

* Parameter relationships
Parameter: channel_design_config['legal_communication_permission']
Condition: channel_design_config['channel_permission_type'] = '1' ( “check permissions” ) and option '1' — “legal contact” must be present in channel_design_config['required_permissions'] .
Reason and result: When both conditions hold, this field selects which accepted/rejected states of the legal contact permission are eligible for the channel. If either condition fails, the field is removed from the form and record.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; the related filter or step operates according to this value.
1 — approved
Interprets the field as “approved”; the related filter or step operates according to this value.
2 — awaiting approval
Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 — missing
Interprets the field as “missing”; the related filter or step operates according to this value.
Example: 0 — rejected
Example:
channel_design_config['legal_communication_permission'] = []
Parameter ID: 4
sms permission
sms permission checkbox

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “sms permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

* Parameter relationships
Parameter: channel_design_config['sms_permission']
Condition: channel_design_config['channel_permission_type'] = '1' ( “check permissions” ) and option '2' — “SMS” must be present in channel_design_config['required_permissions'] .
Reason and result: When both conditions hold, this field selects which accepted/rejected states of the SMS permission are eligible for the channel. If either condition fails, the field is removed from the form and record.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; the related filter or step operates according to this value.
1 — approved
Interprets the field as “approved”; the related filter or step operates according to this value.
2 — awaiting approval
Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 — missing
Interprets the field as “missing”; the related filter or step operates according to this value.
Example: 0 — rejected
Example:
channel_design_config['sms_permission'] = []
Parameter ID: 5
email permission
email permission checkbox

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “email permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

* Parameter relationships
Parameter: channel_design_config['email_permission']
Condition: channel_design_config['channel_permission_type'] = '1' ( “check permissions” ) and option '3' — “mail” must be present in channel_design_config['required_permissions'] .
Reason and result: When both conditions hold, this field selects which accepted/rejected states of the mail permission are eligible for the channel. If either condition fails, the field is removed from the form and record.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; the related filter or step operates according to this value.
1 — approved
Interprets the field as “approved”; the related filter or step operates according to this value.
2 — awaiting approval
Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 — missing
Interprets the field as “missing”; the related filter or step operates according to this value.
Example: 0 — rejected
Example:
channel_design_config['email_permission'] = []
Parameter ID: 6
phone call permission
phone call permission checkbox

The multiple list of customer states accepted by the channel for this permission category. The field is stored only when channel permission checking is enabled and the category is selected in required permissions, parameter 2. If the customer’s “phone call permission” value is not in this list, the channel is rejected; selecting multiple values creates alternative accepted states within this category.

* Parameter relationships
Parameter: channel_design_config['phone_call_permission']
Condition: channel_design_config['channel_permission_type'] = '1' ( “check permissions” ) and option '4' — “phone call” must be present in channel_design_config['required_permissions'] .
Reason and result: When both conditions hold, this field selects which accepted/rejected states of the phone call permission are eligible for the channel. If either condition fails, the field is removed from the form and record.
Options and usage purposes
0 — rejected
Interprets the field as “rejected”; the related filter or step operates according to this value.
1 — approved
Interprets the field as “approved”; the related filter or step operates according to this value.
2 — awaiting approval
Interprets the field as “awaiting approval”; the related filter or step operates according to this value.
3 — missing
Interprets the field as “missing”; the related filter or step operates according to this value.
Example: 0 — rejected
Example:
channel_design_config['phone_call_permission'] = []
Parameter ID: 7
channel institution type
channel institution type select

Determines the scope of the institution filter. No code comparison is made for all institutions; for only selected institutions the customer institution code must be in the list, while in exclude mode it must not be in the list. However, the record service persists parameter 9 only for value 1, so exclude mode loses its selections in the current form save and can effectively accept all institutions with an empty exclusion list.

* Parameter relationships
Parameter: channel_design_config['channel_institution_type']
Condition: This parameter itself has no prerequisite parameter.
Reason and result: Determines how the institution filter works: '0' “all institutions” , '1' “only selected institutions” , and '2' “except selected institutions” . In the current form logic, channel_design_config['institution_selection'] is enabled and persisted only for option '1' .
Options and usage purposes
0 — all institutions
Interprets the field as “all institutions”; the related filter or step operates according to this value.
1 — only selected institutions
Interprets the field as “only selected institutions”; the related filter or step operates according to this value.
2 — except selected institutions
Interprets the field as “except selected institutions”; the related filter or step operates according to this value.
Example: 0 — all institutions
Example:
channel_design_config['channel_institution_type'] = '0'
Parameter ID: 8
institution code list
institution code list textarea

The comma-separated institution codes used by the institution filter. The reader splits text on commas, trims whitespace, and performs exact matching against customer `institution_code`; source codes rather than names must be entered. The current record endpoint attempts to persist this field in checkbox form and only for “only selected institutions,” so textarea schema behavior and exclude mode must be verified together.

* Parameter relationships
Parameter: channel_design_config['institution_selection']
Condition: channel_design_config['channel_institution_type'] = '1' ; option '1' means “only selected institutions” .
Reason and result: This field lists institution codes where the channel may apply. With “all institutions” ( '0' ) or “except selected institutions” ( '2' ), the current form hides and does not persist this field.
Example: institution code list-example
Example:
channel_design_config['institution_selection'] = ''
Parameter ID: 9
channel nationality type
channel nationality type select

Determines the scope of the nationality filter. No match is required for all nations; in only-selected mode the journey’s normalized country name must be in the list, while in exclude mode it must not be in the list. The record service persists parameter 11 only for value 1, so exclude mode loses its selections in the current form flow.

* Parameter relationships
Parameter: channel_design_config['channel_nationality_type']
Condition: This parameter itself has no prerequisite parameter.
Reason and result: Determines how the nationality filter works: '0' “all nationalities” , '1' “only selected nationalities” , and '2' “except selected nationalities” . In the current form logic, channel_design_config['nationality_selection'] is enabled and persisted only for option '1' .
Options and usage purposes
0 — all nations
Interprets the field as “all nations”; the related filter or step operates according to this value.
1 — only selected nations
Interprets the field as “only selected nations”; the related filter or step operates according to this value.
2 — except selected nations
Interprets the field as “except selected nations”; the related filter or step operates according to this value.
Example: 0 — all nations
Example:
channel_design_config['channel_nationality_type'] = '0'
Parameter ID: 10
nationality selection
nationality selection checkbox

The multiple selection of country names used by the nationality filter. The backend converts each WDM option value into an underscore-normalized English country name and compares it with journey `nation_name`. Because journey creation currently has a country-name field bug that can leave this value empty, an only-selected nationality filter can unexpectedly reject the channel.

* Parameter relationships
Parameter: channel_design_config['nationality_selection']
Condition: channel_design_config['channel_nationality_type'] = '1' ; option '1' means “only selected nationalities” .
Reason and result: This field selects the nationalities to which the channel may apply. With “all nationalities” ( '0' ) or “except selected nationalities” ( '2' ), the current form hides and does not persist this field.
Options and usage purposes
0 — western sahara
Adds “western sahara” to the nationality-filter list.
1 — united states outlying minor islands
Adds “united states outlying minor islands” to the nationality-filter list.
2 — aland islands
Adds “aland islands” to the nationality-filter list.
3 — antarctica
Adds “antarctica” to the nationality-filter list.
4 — somalia
Adds “somalia” to the nationality-filter list.
5 — algeria
Adds “algeria” to the nationality-filter list.
6 — tajikistan
Adds “tajikistan” to the nationality-filter list.
7 — sudan
Adds “sudan” to the nationality-filter list.
8 — seychelles
Adds “seychelles” to the nationality-filter list.
9 — bouvet island
Adds “bouvet island” to the nationality-filter list.
10 — christmas island
Adds “christmas island” to the nationality-filter list.
11 — mexico
Adds “mexico” to the nationality-filter list.
12 — martinique
Adds “martinique” to the nationality-filter list.
13 — marshall islands
Adds “marshall islands” to the nationality-filter list.
14 — mauritius island
Adds “mauritius island” to the nationality-filter list.
15 — moldova
Adds “moldova” to the nationality-filter list.
16 — mongolia
Adds “mongolia” to the nationality-filter list.
17 — egypt
Adds “egypt” to the nationality-filter list.
18 — micronesia
Adds “micronesia” to the nationality-filter list.
19 — montserrat
Adds “montserrat” to the nationality-filter list.
20 — monaco
Adds “monaco” to the nationality-filter list.
21 — serbia montenegro
Adds “serbia montenegro” to the nationality-filter list.
22 — united united arab emirates
Adds “united united arab emirates” to the nationality-filter list.
23 — bolivia
Adds “bolivia” to the nationality-filter list.
24 — bosnia and herzegovina
Adds “bosnia and herzegovina” to the nationality-filter list.
25 — botswana
Adds “botswana” to the nationality-filter list.
26 — belgium
Adds “belgium” to the nationality-filter list.
27 — belize
Adds “belize” to the nationality-filter list.
28 — benin
Adds “benin” to the nationality-filter list.
29 — bermuda
Adds “bermuda” to the nationality-filter list.
30 — rwanda
Adds “rwanda” to the nationality-filter list.
31 — brazil
Adds “brazil” to the nationality-filter list.
32 — british virgin islands
Adds “british virgin islands” to the nationality-filter list.
33 — russia
Adds “russia” to the nationality-filter list.
34 — american samoa
Adds “american samoa” to the nationality-filter list.
35 — argentina
Adds “argentina” to the nationality-filter list.
36 — cocos (keeling) islands
Adds “cocos (keeling) islands” to the nationality-filter list.
37 — lebanon
Adds “lebanon” to the nationality-filter list.
38 — luxembourg
Adds “luxembourg” to the nationality-filter list.
39 — hungary
Adds “hungary” to the nationality-filter list.
40 — madagascar
Adds “madagascar” to the nationality-filter list.
41 — macau
Adds “macau” to the nationality-filter list.
42 — macedonia
Adds “macedonia” to the nationality-filter list.
43 — malawi
Adds “malawi” to the nationality-filter list.
44 — maldives
Adds “maldives” to the nationality-filter list.
45 — malaysia
Adds “malaysia” to the nationality-filter list.
46 — mali
Adds “mali” to the nationality-filter list.
47 — malta
Adds “malta” to the nationality-filter list.
48 — singapore
Adds “singapore” to the nationality-filter list.
49 — philippines
Adds “philippines” to the nationality-filter list.
50 — ivory coast
Adds “ivory coast” to the nationality-filter list.
51 — faroe islands
Adds “faroe islands” to the nationality-filter list.
52 — ethiopia
Adds “ethiopia” to the nationality-filter list.
53 — fiji
Adds “fiji” to the nationality-filter list.
54 — morocco
Adds “morocco” to the nationality-filter list.
55 — eritrea
Adds “eritrea” to the nationality-filter list.
56 — indonesia
Adds “indonesia” to the nationality-filter list.
57 — estonia
Adds “estonia” to the nationality-filter list.
58 — armenia
Adds “armenia” to the nationality-filter list.
59 — senegal
Adds “senegal” to the nationality-filter list.
60 — new caledonia
Adds “new caledonia” to the nationality-filter list.
61 — wallis and futuna islands
Adds “wallis and futuna islands” to the nationality-filter list.
62 — tanzania
Adds “tanzania” to the nationality-filter list.
63 — yemen
Adds “yemen” to the nationality-filter list.
64 — vanuatu
Adds “vanuatu” to the nationality-filter list.
65 — vietnam
Adds “vietnam” to the nationality-filter list.
66 — chile
Adds “chile” to the nationality-filter list.
67 — oman
Adds “oman” to the nationality-filter list.
68 — ukraine
Adds “ukraine” to the nationality-filter list.
69 — jordan
Adds “jordan” to the nationality-filter list.
70 — uruguay
Adds “uruguay” to the nationality-filter list.
71 — liberia
Adds “liberia” to the nationality-filter list.
72 — lesotho
Adds “lesotho” to the nationality-filter list.
73 — ireland
Adds “ireland” to the nationality-filter list.
74 — libya
Adds “libya” to the nationality-filter list.
75 — kuwait
Adds “kuwait” to the nationality-filter list.
76 — latvia
Adds “latvia” to the nationality-filter list.
77 — laos
Adds “laos” to the nationality-filter list.
78 — netherlands
Adds “netherlands” to the nationality-filter list.
79 — netherlands antilles
Adds “netherlands antilles” to the nationality-filter list.
80 — croatia
Adds “croatia” to the nationality-filter list.
81 — india
Adds “india” to the nationality-filter list.
82 — iraq
Adds “iraq” to the nationality-filter list.
83 — lithuania
Adds “lithuania” to the nationality-filter list.
84 — honduras
Adds “honduras” to the nationality-filter list.
85 — hong kong
Adds “hong kong” to the nationality-filter list.
86 — tokelau
Adds “tokelau” to the nationality-filter list.
87 — virgin islands (u.s.)
Adds “virgin islands (u.s.)” to the nationality-filter list.
88 — iran
Adds “iran” to the nationality-filter list.
89 — holy see (vatican city state)
Adds “holy see (vatican city state)” to the nationality-filter list.
90 — germany
Adds “germany” to the nationality-filter list.
91 — swaziland
Adds “swaziland” to the nationality-filter list.
92 — anguilla
Adds “anguilla” to the nationality-filter list.
93 — serbia
Adds “serbia” to the nationality-filter list.
94 — cuba
Adds “cuba” to the nationality-filter list.
95 — south sudan
Adds “south sudan” to the nationality-filter list.
96 — batumi-georgia
Adds “batumi-georgia” to the nationality-filter list.
97 — heard island and mcdonald islands
Adds “heard island and mcdonald islands” to the nationality-filter list.
98 — santa helena
Adds “santa helena” to the nationality-filter list.
99 — san marino
Adds “san marino” to the nationality-filter list.
100 — congo (brazzaville)
Adds “congo (brazzaville)” to the nationality-filter list.
101 — costa rica
Adds “costa rica” to the nationality-filter list.
102 — saint martin (french side)
Adds “saint martin (french side)” to the nationality-filter list.
103 — saint barthelemy
Adds “saint barthelemy” to the nationality-filter list.
104 — samoa
Adds “samoa” to the nationality-filter list.
105 — saint pierre and miquelon
Adds “saint pierre and miquelon” to the nationality-filter list.
106 — kazakhstan
Adds “kazakhstan” to the nationality-filter list.
107 — kenya
Adds “kenya” to the nationality-filter list.
108 — canada
Adds “canada” to the nationality-filter list.
109 — qatar
Adds “qatar” to the nationality-filter list.
110 — colombia
Adds “colombia” to the nationality-filter list.
111 — republic of the congo
Adds “republic of the congo” to the nationality-filter list.
112 — cyprus
Adds “cyprus” to the nationality-filter list.
113 — kyrgyzstan
Adds “kyrgyzstan” to the nationality-filter list.
114 — chad
Adds “chad” to the nationality-filter list.
115 — cook islands
Adds “cook islands” to the nationality-filter list.
116 — burundi
Adds “burundi” to the nationality-filter list.
117 — burkina faso
Adds “burkina faso” to the nationality-filter list.
118 — bulgaria
Adds “bulgaria” to the nationality-filter list.
119 — brunei
Adds “brunei” to the nationality-filter list.
120 — gibraltar
Adds “gibraltar” to the nationality-filter list.
121 — keymen islands
Adds “keymen islands” to the nationality-filter list.
122 — cape verde
Adds “cape verde” to the nationality-filter list.
123 — bhutan
Adds “bhutan” to the nationality-filter list.
124 — sao tome and principe
Adds “sao tome and principe” to the nationality-filter list.
125 — tuvalu
Adds “tuvalu” to the nationality-filter list.
126 — zimbabwe
Adds “zimbabwe” to the nationality-filter list.
127 — guernsey
Adds “guernsey” to the nationality-filter list.
128 — saudi arabia
Adds “saudi arabia” to the nationality-filter list.
129 — self-governing state of palestine
Adds “self-governing state of palestine” to the nationality-filter list.
130 — finland
Adds “finland” to the nationality-filter list.
131 — france
Adds “france” to the nationality-filter list.
132 — french guiana
Adds “french guiana” to the nationality-filter list.
133 — french polynesia
Adds “french polynesia” to the nationality-filter list.
134 — gabon
Adds “gabon” to the nationality-filter list.
135 — wales (uk)
Adds “wales (uk)” to the nationality-filter list.
136 — gambia
Adds “gambia” to the nationality-filter list.
137 — ghana
Adds “ghana” to the nationality-filter list.
138 — guinea
Adds “guinea” to the nationality-filter list.
139 — syria
Adds “syria” to the nationality-filter list.
140 — suriname
Adds “suriname” to the nationality-filter list.
141 — saint vincent
Adds “saint vincent” to the nationality-filter list.
142 — saint lucia
Adds “saint lucia” to the nationality-filter list.
143 — saint kitts and nevis
Adds “saint kitts and nevis” to the nationality-filter list.
144 — sri lanka
Adds “sri lanka” to the nationality-filter list.
145 — greece
Adds “greece” to the nationality-filter list.
146 — guinea-bissau
Adds “guinea-bissau” to the nationality-filter list.
147 — taiwan
Adds “taiwan” to the nationality-filter list.
148 — sierra leone
Adds “sierra leone” to the nationality-filter list.
149 — togo
Adds “togo” to the nationality-filter list.
150 — tongo
Adds “tongo” to the nationality-filter list.
151 — thailand
Adds “thailand” to the nationality-filter list.
152 — afghanistan
Adds “afghanistan” to the nationality-filter list.
153 — saipan
Adds “saipan” to the nationality-filter list.
154 — turkey
Adds “turkey” to the nationality-filter list.
155 — trinidad and tobago tobago
Adds “trinidad and tobago tobago” to the nationality-filter list.
156 — angola
Adds “angola” to the nationality-filter list.
157 — turks and caicos islands
Adds “turks and caicos islands” to the nationality-filter list.
158 — turkmenistan
Adds “turkmenistan” to the nationality-filter list.
159 — uganda
Adds “uganda” to the nationality-filter list.
160 — new zealand
Adds “new zealand” to the nationality-filter list.
161 — venezuella
Adds “venezuella” to the nationality-filter list.
162 — french southern territories
Adds “french southern territories” to the nationality-filter list.
163 — tunisia
Adds “tunisia” to the nationality-filter list.
164 — cameroon
Adds “cameroon” to the nationality-filter list.
165 — cambodia
Adds “cambodia” to the nationality-filter list.
166 — slovak republic
Adds “slovak republic” to the nationality-filter list.
167 — slovenia
Adds “slovenia” to the nationality-filter list.
168 — jersey
Adds “jersey” to the nationality-filter list.
169 — british indian ocean territory
Adds “british indian ocean territory” to the nationality-filter list.
170 — israel
Adds “israel” to the nationality-filter list.
171 — spain
Adds “spain” to the nationality-filter list.
172 — switzerland
Adds “switzerland” to the nationality-filter list.
173 — sweden
Adds “sweden” to the nationality-filter list.
174 — iceland
Adds “iceland” to the nationality-filter list.
175 — italy
Adds “italy” to the nationality-filter list.
176 — japan
Adds “japan” to the nationality-filter list.
177 — jameika
Adds “jameika” to the nationality-filter list.
178 — australia
Adds “australia” to the nationality-filter list.
179 — aruba
Adds “aruba” to the nationality-filter list.
180 — azerbaijan
Adds “azerbaijan” to the nationality-filter list.
181 — austria
Adds “austria” to the nationality-filter list.
182 — bahrain
Adds “bahrain” to the nationality-filter list.
183 — bahamas
Adds “bahamas” to the nationality-filter list.
184 — barbados
Adds “barbados” to the nationality-filter list.
185 — bangladesh
Adds “bangladesh” to the nationality-filter list.
186 — belarus (belarus)
Adds “belarus (belarus)” to the nationality-filter list.
187 — barbuda/antigua
Adds “barbuda/antigua” to the nationality-filter list.
188 — liechtenstein
Adds “liechtenstein” to the nationality-filter list.
189 — svalbard
Adds “svalbard” to the nationality-filter list.
190 — zambia
Adds “zambia” to the nationality-filter list.
191 — panama
Adds “panama” to the nationality-filter list.
192 — palau
Adds “palau” to the nationality-filter list.
193 — paraguay
Adds “paraguay” to the nationality-filter list.
194 — papua new guinea
Adds “papua new guinea” to the nationality-filter list.
195 — poland
Adds “poland” to the nationality-filter list.
196 — peru
Adds “peru” to the nationality-filter list.
197 — puerto rico
Adds “puerto rico” to the nationality-filter list.
198 — portugal
Adds “portugal” to the nationality-filter list.
199 — romania
Adds “romania” to the nationality-filter list.
200 — reunion island
Adds “reunion island” to the nationality-filter list.
201 — central africa republic of
Adds “central africa republic of” to the nationality-filter list.
202 — pitcairn
Adds “pitcairn” to the nationality-filter list.
203 — myanmar
Adds “myanmar” to the nationality-filter list.
204 — nauru
Adds “nauru” to the nationality-filter list.
205 — niu
Adds “niu” to the nationality-filter list.
206 — norfolk island
Adds “norfolk island” to the nationality-filter list.
207 — kiribati
Adds “kiribati” to the nationality-filter list.
208 — comoros
Adds “comoros” to the nationality-filter list.
209 — democratic people's republic of korea
Adds “democratic people's republic of korea” to the nationality-filter list.
210 — mayotte
Adds “mayotte” to the nationality-filter list.
211 — south georgia and the south sandwich islands
Adds “south georgia and the south sandwich islands” to the nationality-filter list.
212 — equatorial guinea
Adds “equatorial guinea” to the nationality-filter list.
213 — el salvador
Adds “el salvador” to the nationality-filter list.
214 — dominica
Adds “dominica” to the nationality-filter list.
215 — ecuador
Adds “ecuador” to the nationality-filter list.
216 — east timor
Adds “east timor” to the nationality-filter list.
217 — dominican republic
Adds “dominican republic” to the nationality-filter list.
218 — denmark
Adds “denmark” to the nationality-filter list.
219 — djibouti
Adds “djibouti” to the nationality-filter list.
220 — czech republic
Adds “czech republic” to the nationality-filter list.
221 — china
Adds “china” to the nationality-filter list.
222 — united states of america
Adds “united states of america” to the nationality-filter list.
223 — andorra
Adds “andorra” to the nationality-filter list.
224 — albania
Adds “albania” to the nationality-filter list.
225 — nicaragua
Adds “nicaragua” to the nationality-filter list.
226 — norway
Adds “norway” to the nationality-filter list.
227 — niger
Adds “niger” to the nationality-filter list.
228 — nigeria
Adds “nigeria” to the nationality-filter list.
229 — namibia
Adds “namibia” to the nationality-filter list.
230 — nepal
Adds “nepal” to the nationality-filter list.
231 — mauritania
Adds “mauritania” to the nationality-filter list.
232 — mozambique
Adds “mozambique” to the nationality-filter list.
233 — united kingdom
Adds “united kingdom” to the nationality-filter list.
234 — kosovo
Adds “kosovo” to the nationality-filter list.
235 — uzbekistan
Adds “uzbekistan” to the nationality-filter list.
236 — pakistan
Adds “pakistan” to the nationality-filter list.
237 — south korea
Adds “south korea” to the nationality-filter list.
238 — south africa
Adds “south africa” to the nationality-filter list.
239 — guyana
Adds “guyana” to the nationality-filter list.
240 — guatemala
Adds “guatemala” to the nationality-filter list.
241 — guam
Adds “guam” to the nationality-filter list.
242 — guadelup
Adds “guadelup” to the nationality-filter list.
243 — greenland
Adds “greenland” to the nationality-filter list.
244 — grenada
Adds “grenada” to the nationality-filter list.
245 — haiti
Adds “haiti” to the nationality-filter list.
246 — georgia
Adds “georgia” to the nationality-filter list.
247 — solomon islands
Adds “solomon islands” to the nationality-filter list.
248 — isle of man
Adds “isle of man” to the nationality-filter list.
249 — montenegro
Adds “montenegro” to the nationality-filter list.
250 — turkish republic of northern cyprus
Adds “turkish republic of northern cyprus” to the nationality-filter list.
Example: 0 — western sahara
Example:
channel_design_config['nationality_selection'] = []
Parameter ID: 11
channel step
channel step list_parameter

A repeating list that stores the ordered delivery steps of the channel design. The eligible step index is calculated as the number of operations already created in the journey; when all steps have been used, the design is no longer eligible. Each row carries channel type, waiting duration, message, and provider API settings together.

* Parameter relationships
Parameter: channel_design_config['channel_step_list']
Condition: No other parameter option is a prerequisite.
Reason and result: “channel step” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
channel_design_config['channel_step_list'] = [{'channel_type': '', 'channel_time_type': '', 'channel_time_period': '', 'message_header': '', 'message_content_type': '', 'html_message': '', 'plain_text': '', 'provider_send_api_id': '', 'provider_delivery_check_api_id': '', 'create_date': '', 'update_date': '', 'name': '', 'whatsapp_sender_id': '', 'whatsapp_template_id': '', 'message_language': ''}]
Parameter ID: 12
channel type
channel type select

Determines whether the step uses SMS, push notification, IVR, email, or phone call. The selection determines target contact information, context passed to provider code, and channel type written to the operation; the journey may be made passive if required contact information is unavailable.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['channel_type']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “channel type” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — sms
Interprets the field as “sms”; the related filter or step operates according to this value.
1 — push notification
Interprets the field as “push notification”; the related filter or step operates according to this value.
2 — ivr
Interprets the field as “ivr”; the related filter or step operates according to this value.
3 — mail
Interprets the field as “mail”; the related filter or step operates according to this value.
4 — phone call
Interprets the field as “phone call”; the related filter or step operates according to this value.
Example: 0 — sms
Example:
channel_design_config['channel_step_list'][0]['channel_type'] = '0'
Parameter ID: 13
next channel step transition time type
next channel step transition time type select

Specifies whether transition time after the previous step is measured in hours or days. Agenda calculation adds parameter 16 to the previous operation date using the selected unit; an incorrect unit schedules the next channel earlier or later than intended.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['channel_time_type']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “next channel step transition time type” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — hour
Interprets the field as “hour”; the related filter or step operates according to this value.
1 — day
Interprets the field as “day”; the related filter or step operates according to this value.
Example: 0 — hour
Example:
channel_design_config['channel_step_list'][0]['channel_time_type'] = '0'
Parameter ID: 15
next channel step transition time period
next channel step transition time period integer

The integer duration to wait before moving to the next channel step. It is added to the previous operation date as hours or days according to parameter 15; if empty or not convertible to an integer, no usable transition period is available for calculation.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['channel_time_period']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “next channel step transition time period” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: 24
Example:
channel_design_config['channel_step_list'][0]['channel_time_period'] = ''
Parameter ID: 16
message header (email subject)
message header (email subject) text

The message header defined primarily for use as the subject line of an email channel. It is read into channel-step configuration and provides context usable by provider API code; for other channel types its meaning depends on provider implementation.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['message_header']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “message header (email subject)” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: message header (email subject)-example
Example:
channel_design_config['channel_step_list'][0]['message_header'] = ''
Parameter ID: 17
message content type
message content type select

Selects whether the step message is plain text or HTML. The record service removes the unused content field according to the selection. The reader stores HTML selection as `html`, while channel selection expects `html_message`, so HTML content is not assigned as the eligible message in the current code; the plain-text path works.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['message_content_type']
Condition: This parameter is populated when the related channel_design_config['channel_step_list'] item exists.
Reason and result: Determines the message-body format. Option '0' — “plain text” enables channel_design_config['channel_step_list'][0]['plain_text'] and clears the HTML field. Option '1' — “HTML” enables channel_design_config['channel_step_list'][0]['html_message'] and clears the plain-text field.
Options and usage purposes
0 — plain text
Interprets the field as “plain text”; the related filter or step operates according to this value.
1 — html
Interprets the field as “html”; the related filter or step operates according to this value.
Example: 0 — plain text
Example:
channel_design_config['channel_step_list'][0]['message_content_type'] = '0'
Parameter ID: 18
html message
html message html_editor

The rich content intended for delivery when HTML message is selected. The record service removes this field unless content type is HTML; however, it is not used as the final message during channel selection until the current `html` versus `html_message` value mismatch is fixed.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['html_message']
Condition: channel_design_config['channel_step_list'][0]['message_content_type'] = '1' ; option '1' means “HTML” .
Reason and result: When the message will be sent as HTML, its content comes from this field. With “plain text” ( '0' ), the HTML field is removed from the channel step and is not evaluated.
Example: html message-example
Example:
channel_design_config['channel_step_list'][0]['html_message'] = ''
Parameter ID: 19
plain text
plain text textarea

The message delivered when plain-text content type is selected. The record service keeps the field only when content type is 0; for plain text, channel selection copies this value into the journey’s eligible-channel message and the operation record stores the content actually sent.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['plain_text']
Condition: channel_design_config['channel_step_list'][0]['message_content_type'] = '0' ; option '0' means “plain text” .
Reason and result: When the message will be sent as plain text, its content comes from this field. With “HTML” ( '1' ), the plain-text field is removed from the channel step and is not evaluated.
Example: plain text-example
Example:
channel_design_config['channel_step_list'][0]['plain_text'] = ''
Parameter ID: 20
provider send api id
provider send api id text

The client identifier of the user API record that sends the message to the external provider. The API record is loaded while reading channel design; channel processing executes its code and expects `channel_success_status`, provider response, and delivery-check identifier, so a valid identifier and code are required for delivery.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['provider_send_api_id']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “provider send api id” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: provider send api id-example
Example:
channel_design_config['channel_step_list'][0]['provider_send_api_id'] = ''
Parameter ID: 21
provider delivery check api id
provider delivery check api id text

The client identifier of the user API record that queries message status after delivery. It is copied into the operation record; when present together with a delivery-check identifier, the timer executes API code to update delivery status, failure reason, follow-up duration, and service response.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['provider_delivery_check_api_id']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “provider delivery check api id” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: provider delivery check api id-example
Example:
channel_design_config['channel_step_list'][0]['provider_delivery_check_api_id'] = ''
Parameter ID: 22
create date
create date datetime

Defined in WDM to store the initial creation time of the channel design, and the configuration reader reads this field. However, the current record endpoint mistakenly writes the timestamp to top-level parameter 26, so this field may remain empty in the standard save path.

* Parameter relationships
Parameter: channel_design_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
channel_design_config['create_date'] = ''
Parameter ID: 23
update date
update date datetime

Defined in WDM to store the latest update time of the channel design, and the configuration reader reads this field. The current record endpoint mistakenly writes the timestamp to top-level parameter 27, so a current value may not be produced here.

* Parameter relationships
Parameter: channel_design_config['update_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “update date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
channel_design_config['update_date'] = ''
Parameter ID: 24
name
name text

The name that distinguishes the channel design for users. The record endpoint writes a form field named `description` into this parameter; because configuration selection does not read the name, it does not change algorithmic eligibility and is used for management screens and human readability.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['name']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “name” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: name-example
Example:
channel_design_config['channel_step_list'][0]['name'] = ''
Parameter ID: 25
whatsapp sender id
whatsapp sender id text

Defined under a channel step to store the sender identifier used by a WhatsApp provider. WhatsApp is absent from current channel-type options and save/read code does not process step parameter 26; additionally, the record endpoint mistakenly writes a timestamp to top-level parameter 26. Therefore, it is not functional in the current standard flow.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['whatsapp_sender_id']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “whatsapp sender id” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: whatsapp sender id-example
Example:
channel_design_config['channel_step_list'][0]['whatsapp_sender_id'] = ''
Parameter ID: 26
whatsapp template id
whatsapp template id text

Defined under a channel step to store the message-template identifier used by a WhatsApp provider. Because current step save/read code does not carry this field and top-level parameter 27 is mistakenly used for a timestamp, it is not used in standard channel delivery.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['whatsapp_template_id']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “whatsapp template id” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Example: whatsapp template id-example
Example:
channel_design_config['channel_step_list'][0]['whatsapp_template_id'] = ''
Parameter ID: 27
message language
message language select

The language code of the message in the channel step. WDM provides 79 language options; however, the current step-save method does not persist parameter 28 and the configuration reader does not read it. Therefore, it does not automatically affect template or message selection and must not be assumed to persist in the standard flow.

* Parameter relationships
Parameter: channel_design_config['channel_step_list'][0]['message_language']
Condition: The related channel_design_config['channel_step_list'] list item must exist.
Reason and result: “message language” is a child field of that parent-list item; it is populated only when the item is created and evaluated while processing the same item. It has no other parameter-option dependency.
Options and usage purposes
0 — TR
Interprets the field as “TR”; the related filter or step operates according to this value.
1 — AZ
Interprets the field as “AZ”; the related filter or step operates according to this value.
2 — EN
Interprets the field as “EN”; the related filter or step operates according to this value.
3 — FA
Interprets the field as “FA”; the related filter or step operates according to this value.
4 — DE
Interprets the field as “DE”; the related filter or step operates according to this value.
5 — CA
Interprets the field as “CA”; the related filter or step operates according to this value.
6 — PT
Interprets the field as “PT”; the related filter or step operates according to this value.
7 — ES
Interprets the field as “ES”; the related filter or step operates according to this value.
8 — SQ
Interprets the field as “SQ”; the related filter or step operates according to this value.
9 — NL
Interprets the field as “NL”; the related filter or step operates according to this value.
10 — TKL
Interprets the field as “TKL”; the related filter or step operates according to this value.
11 — AR
Interprets the field as “AR”; the related filter or step operates according to this value.
12 — BN
Interprets the field as “BN”; the related filter or step operates according to this value.
13 — BE
Interprets the field as “BE”; the related filter or step operates according to this value.
14 — FR
Interprets the field as “FR”; the related filter or step operates according to this value.
15 — BS
Interprets the field as “BS”; the related filter or step operates according to this value.
16 — MS
Interprets the field as “MS”; the related filter or step operates according to this value.
17 — BG
Interprets the field as “BG”; the related filter or step operates according to this value.
18 — DZ
Interprets the field as “DZ”; the related filter or step operates according to this value.
19 — CS
Interprets the field as “CS”; the related filter or step operates according to this value.
20 — ZH
Interprets the field as “ZH”; the related filter or step operates according to this value.
21 — DA
Interprets the field as “DA”; the related filter or step operates according to this value.
22 — ID
Interprets the field as “ID”; the related filter or step operates according to this value.
23 — TI
Interprets the field as “TI”; the related filter or step operates according to this value.
24 — HY
Interprets the field as “HY”; the related filter or step operates according to this value.
25 — ET
Interprets the field as “ET”; the related filter or step operates according to this value.
26 — AM
Interprets the field as “AM”; the related filter or step operates according to this value.
27 — FO
Interprets the field as “FO”; the related filter or step operates according to this value.
28 — FI
Interprets the field as “FI”; the related filter or step operates according to this value.
29 — KL
Interprets the field as “KL”; the related filter or step operates according to this value.
30 — KO
Interprets the field as “KO”; the related filter or step operates according to this value.
31 — KA
Interprets the field as “KA”; the related filter or step operates according to this value.
32 — HR
Interprets the field as “HR”; the related filter or step operates according to this value.
33 — HI
Interprets the field as “HI”; the related filter or step operates according to this value.
34 — HE
Interprets the field as “HE”; the related filter or step operates according to this value.
35 — SV
Interprets the field as “SV”; the related filter or step operates according to this value.
36 — IT
Interprets the field as “IT”; the related filter or step operates according to this value.
37 — IS
Interprets the field as “IS”; the related filter or step operates according to this value.
38 — JA
Interprets the field as “JA”; the related filter or step operates according to this value.
39 — KM
Interprets the field as “KM”; the related filter or step operates according to this value.
40 — KK
Interprets the field as “KK”; the related filter or step operates according to this value.
41 — EL
Interprets the field as “EL”; the related filter or step operates according to this value.
42 — KY
Interprets the field as “KY”; the related filter or step operates according to this value.
43 — LO
Interprets the field as “LO”; the related filter or step operates according to this value.
44 — LV
Interprets the field as “LV”; the related filter or step operates according to this value.
45 — LT
Interprets the field as “LT”; the related filter or step operates according to this value.
46 — LB
Interprets the field as “LB”; the related filter or step operates according to this value.
47 — HU
Interprets the field as “HU”; the related filter or step operates according to this value.
48 — MG
Interprets the field as “MG”; the related filter or step operates according to this value.
49 — MK
Interprets the field as “MK”; the related filter or step operates according to this value.
50 — DV
Interprets the field as “DV”; the related filter or step operates according to this value.
51 — MT
Interprets the field as “MT”; the related filter or step operates according to this value.
52 — MN
Interprets the field as “MN”; the related filter or step operates according to this value.
53 — RO
Interprets the field as “RO”; the related filter or step operates according to this value.
54 — NE
Interprets the field as “NE”; the related filter or step operates according to this value.
55 — NO
Interprets the field as “NO”; the related filter or step operates according to this value.
56 — UZ
Interprets the field as “UZ”; the related filter or step operates according to this value.
57 — UR
Interprets the field as “UR”; the related filter or step operates according to this value.
58 — PL
Interprets the field as “PL”; the related filter or step operates according to this value.
59 — RW
Interprets the field as “RW”; the related filter or step operates according to this value.
60 — RU
Interprets the field as “RU”; the related filter or step operates according to this value.
61 — SR
Interprets the field as “SR”; the related filter or step operates according to this value.
62 — SK
Interprets the field as “SK”; the related filter or step operates according to this value.
63 — SL
Interprets the field as “SL”; the related filter or step operates according to this value.
64 — SI
Interprets the field as “SI”; the related filter or step operates according to this value.
65 — SW
Interprets the field as “SW”; the related filter or step operates according to this value.
66 — TH
Interprets the field as “TH”; the related filter or step operates according to this value.
67 — TO
Interprets the field as “TO”; the related filter or step operates according to this value.
68 — TVL
Interprets the field as “TVL”; the related filter or step operates according to this value.
69 — TK
Interprets the field as “TK”; the related filter or step operates according to this value.
70 — UK
Interprets the field as “UK”; the related filter or step operates according to this value.
71 — BI
Interprets the field as “BI”; the related filter or step operates according to this value.
72 — VI
Interprets the field as “VI”; the related filter or step operates according to this value.
73 — TG
Interprets the field as “TG”; the related filter or step operates according to this value.
74 — SO
Interprets the field as “SO”; the related filter or step operates according to this value.
75 — MY
Interprets the field as “MY”; the related filter or step operates according to this value.
76 —
Interprets the field as “”; the related filter or step operates according to this value.
77 — NIU
Interprets the field as “NIU”; the related filter or step operates according to this value.
78 — SM
Interprets the field as “SM”; the related filter or step operates according to this value.
Example: 0 — TR
Example:
channel_design_config['channel_step_list'][0]['message_language'] = '0'
Parameter ID: 28
About WDC Campaign / Agenda
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Agenda

Packages campaign journeys for channel operation at a specific date and time and tracks their states.

Agenda flow

Journeys are added to a main document by campaign and hour. Large lists are split into additional parts and merged again before processing. Only active journeys run; successfully processed rows become completed, while rows requiring another schedule become replanned.

Code finding: Additional part documents are created with `_part_N` identifiers, but their status is not set to “additional document.” No operation writing “continue” or “complete” for the main agenda was found in the inspected code.
status
status select

The processing lifecycle state of the agenda document. A new document is written as `wait` when it contains journeys and as `cancel` when its list is empty; when an agenda from the last 48 hours or earlier still contains active journeys and is regenerated, the old document is set to `replanned`. No automatic write of `continue`, `complete`, or `additional document` was found in the inspected code.

* Parameter relationships
Parameter: agenda_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — cancel
Indicates an empty or cancelled agenda.
1 — wait
Indicates an agenda waiting to be processed.
2 — continue
Represents an agenda in progress in the schema; inspected code does not write it automatically.
3 — complete
Represents a completed agenda in the schema; inspected code does not write it automatically.
4 — replanned
Indicates an old document whose active journeys were moved to a new agenda.
5 — additional document
Represents an additional part in the schema; current partition code does not write this state automatically.
Example: 0 — cancel
Example:
agenda_config['status'] = '0'
Parameter ID: 0
campaign name
campaign name text

The display name of the campaign associated with the agenda. It is copied from campaign configuration when a new main agenda document is created; additional part documents copy the main document data, so they carry the same name and make the date-based agenda readable in reports.

* Parameter relationships
Parameter: agenda_config['campaign_name']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign name” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: campaign name-example
Example:
agenda_config['campaign_name'] = ''
Parameter ID: 1
campaign client id
campaign client id text

The client identifier of the campaign that owns the agenda. The main agenda client identifier is produced by combining this value with agenda date; querying, partitioning, merging, and replanning operations group agendas by campaign through this field.

* Parameter relationships
Parameter: agenda_config['campaign_client_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “campaign client id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: campaign client id-example
Example:
agenda_config['campaign_client_id'] = ''
Parameter ID: 2
agenda date
agenda date datetime

The agenda date representing the hour boundary at which channel operations are scheduled. It is used with campaign identifier in the main client identifier, and main/additional part documents for the same date are merged through this value. When processing time arrives, only active journeys run after campaign day and hour eligibility is also verified.

* Parameter relationships
Parameter: agenda_config['agenda_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “agenda date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T10:00:00
Example:
agenda_config['agenda_date'] = ''
Parameter ID: 3
additional part count
additional part count integer

Specifies how many `_part_N` documents exist in addition to the main agenda. When journey count exceeds configured document capacity, the first batch remains in the main document, remaining batches are stored as `_part_1`, `_part_2`, and so on, and the counter is updated to the new part count. During reading, that many parts are fetched and appended to the main journey list.

* Parameter relationships
Parameter: agenda_config['additional_part_count']
Condition: No other parameter option is a prerequisite.
Reason and result: “additional part count” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2
Example:
agenda_config['additional_part_count'] = ''
Parameter ID: 4
journey list
journey list list_parameter

A repeating list that stores journeys to process for the same campaign and agenda hour. A new journey identifier is added with active status only when it is not already present, while identifiers marked for removal are deleted. Large lists are split into main and additional documents according to the storage limit and merged back into one logical list before processing.

* Parameter relationships
Parameter: agenda_config['journey_list']
Condition: No other parameter option is a prerequisite.
Reason and result: “journey list” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
agenda_config['journey_list'] = []
Parameter ID: 5
journey id
journey id text

The client identifier of the customer journey referenced by the agenda row. Channel processing fetches journey records in bulk with these identifiers; the same identifier is not added twice to one agenda and is carried into a new agenda document during replanning.

* Parameter relationships
Parameter: agenda_config['journey_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “journey id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: journey id-example
Example:
agenda_config['journey_id'] = ''
Parameter ID: 6
journey status
journey status select

The processing state of one journey within this agenda. A newly added row starts as `active`; after channel processing it is set to `operation completed` on success or `replanned` when unsuccessful and requiring another agenda. Only active rows are executed or replanned from old agendas; no code path automatically writing `cancel` was found in the inspected file.

* Parameter relationships
Parameter: agenda_config['journey_status']
Condition: No other parameter option is a prerequisite.
Reason and result: “journey status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — cancel
Excludes the row from processing; no automatic write path was found.
1 — active
Makes the row eligible for channel processing and replanning.
2 — operation completed
Indicates that the channel operation completed successfully.
3 — replanned
Indicates that an unsuccessful operation was moved to a new agenda.
Example: 0 — cancel
Example:
agenda_config['journey_status'] = '0'
Parameter ID: 7
create date
create date datetime

The Coordinated Universal Time at which the main agenda document was first created. It is written with the current time when a document for a new date is prepared; it is preserved when an existing agenda is updated, and additional parts carry the same creation time because they are produced from copied main data.

* Parameter relationships
Parameter: agenda_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T10:00:00
Example:
agenda_config['create_date'] = ''
Parameter ID: 8
update date
update date datetime

The last update time written when an existing agenda’s journey list changes or an old agenda is marked as replanned. It may be absent initially on a new document; it is refreshed with current Coordinated Universal Time when additions, removals, or replanning occur on an existing document.

* Parameter relationships
Parameter: agenda_config['update_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “update date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T10:00:00
Example:
agenda_config['update_date'] = ''
Parameter ID: 9
About WDC Campaign / Customer / Journey / Operation / Survey
WISDOMERA / WDIGITALCHANNEL

WDC Campaign / Customer / Journey / Operation / Survey

Stores predefined and manual answers of a completed WDC survey under the latest channel operation.

Answer-recording flow

The timer retrieves completed surveys, finds the latest operation of the journey, and creates an active answer record. Predefined question identifiers 0–33 map to fields 1–34; general opinion is written to 35 and manual answers under list 37.

Code findings: Survey generation uses answer identifiers 1–5 while result WDM options are 0–4, and recording performs no conversion. In addition, parameter 36 create date and parameter 41 answer date are not written automatically.
status
status select

The activity state of the survey-answer record. The timer creates a record only for surveys whose survey-service result is `complete` and writes the state as active; an expired but incomplete survey is removed from the queue, but no passive answer record is created in this layer.

* Parameter relationships
Parameter: operation_survey_config['status']
Condition: No other parameter option is a prerequisite.
Reason and result: “status” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — passive
Represents a passive record in the schema; the automatic creation path does not write this value.
1 — active
Stores the completed survey answer as an active reporting record.
Example: 0 — passive
Example:
operation_survey_config['status'] = '0'
Parameter ID: 0
how likely are you to recommend our service to others?
how likely are you to recommend our service to others? select

The selected answer value for the predefined question “how likely are you to recommend our service to others?”. Survey-service question identifier 0 is mapped to WDM field 1 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_likely_are_you_to_recommend_our_service_to_others']
Condition: No other parameter option is a prerequisite.
Reason and result: “how likely are you to recommend our service to others?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_likely_are_you_to_recommend_our_service_to_others'] = '0'
Parameter ID: 1
how would you rate the service you received overall?
how would you rate the service you received overall? select

The selected answer value for the predefined question “how would you rate the service you received overall?”. Survey-service question identifier 1 is mapped to WDM field 2 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_service_you_received_overall']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the service you received overall?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_service_you_received_overall'] = '0'
Parameter ID: 2
how satisfied were you with the doctor's service?
how satisfied were you with the doctor's service? select

The selected answer value for the predefined question “how satisfied were you with the doctor's service?”. Survey-service question identifier 2 is mapped to WDM field 3 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_satisfied_were_you_with_the_doctor_s_service']
Condition: No other parameter option is a prerequisite.
Reason and result: “how satisfied were you with the doctor's service?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_satisfied_were_you_with_the_doctor_s_service'] = '0'
Parameter ID: 3
how would you rate the reception and registration process?
how would you rate the reception and registration process? select

The selected answer value for the predefined question “how would you rate the reception and registration process?”. Survey-service question identifier 3 is mapped to WDM field 4 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_reception_and_registration_process']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the reception and registration process?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_reception_and_registration_process'] = '0'
Parameter ID: 4
how satisfied were you with the nursing services?
how satisfied were you with the nursing services? select

The selected answer value for the predefined question “how satisfied were you with the nursing services?”. Survey-service question identifier 4 is mapped to WDM field 5 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_satisfied_were_you_with_the_nursing_services']
Condition: No other parameter option is a prerequisite.
Reason and result: “how satisfied were you with the nursing services?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_satisfied_were_you_with_the_nursing_services'] = '0'
Parameter ID: 5
how would you rate the beautician's service?
how would you rate the beautician's service? select

The selected answer value for the predefined question “how would you rate the beautician's service?”. Survey-service question identifier 5 is mapped to WDM field 6 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_beautician_s_service']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the beautician's service?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_beautician_s_service'] = '0'
Parameter ID: 6
were you satisfied with the podologist's service?
were you satisfied with the podologist's service? select

The selected answer value for the predefined question “were you satisfied with the podologist's service?”. Survey-service question identifier 6 is mapped to WDM field 7 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['were_you_satisfied_with_the_podologist_s_service']
Condition: No other parameter option is a prerequisite.
Reason and result: “were you satisfied with the podologist's service?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['were_you_satisfied_with_the_podologist_s_service'] = '0'
Parameter ID: 7
how would you rate the cleaning services?
how would you rate the cleaning services? select

The selected answer value for the predefined question “how would you rate the cleaning services?”. Survey-service question identifier 7 is mapped to WDM field 8 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_cleaning_services']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the cleaning services?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_cleaning_services'] = '0'
Parameter ID: 8
how satisfied were you with the food services?
how satisfied were you with the food services? select

The selected answer value for the predefined question “how satisfied were you with the food services?”. Survey-service question identifier 8 is mapped to WDM field 9 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_satisfied_were_you_with_the_food_services']
Condition: No other parameter option is a prerequisite.
Reason and result: “how satisfied were you with the food services?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_satisfied_were_you_with_the_food_services'] = '0'
Parameter ID: 9
how would you rate the admission and discharge process?
how would you rate the admission and discharge process? select

The selected answer value for the predefined question “how would you rate the admission and discharge process?”. Survey-service question identifier 9 is mapped to WDM field 10 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_admission_and_discharge_process']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the admission and discharge process?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_admission_and_discharge_process'] = '0'
Parameter ID: 10
were you satisfied with the parking services?
were you satisfied with the parking services? select

The selected answer value for the predefined question “were you satisfied with the parking services?”. Survey-service question identifier 10 is mapped to WDM field 11 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['were_you_satisfied_with_the_parking_services']
Condition: No other parameter option is a prerequisite.
Reason and result: “were you satisfied with the parking services?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['were_you_satisfied_with_the_parking_services'] = '0'
Parameter ID: 11
how would you rate the valet parking service?
how would you rate the valet parking service? select

The selected answer value for the predefined question “how would you rate the valet parking service?”. Survey-service question identifier 11 is mapped to WDM field 12 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_valet_parking_service']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the valet parking service?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_valet_parking_service'] = '0'
Parameter ID: 12
how satisfied were you with the sleep technician's service?
how satisfied were you with the sleep technician's service? select

The selected answer value for the predefined question “how satisfied were you with the sleep technician's service?”. Survey-service question identifier 12 is mapped to WDM field 13 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_satisfied_were_you_with_the_sleep_technician_s_service']
Condition: No other parameter option is a prerequisite.
Reason and result: “how satisfied were you with the sleep technician's service?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_satisfied_were_you_with_the_sleep_technician_s_service'] = '0'
Parameter ID: 13
how would you rate the service provided by the embryologist?
how would you rate the service provided by the embryologist? select

The selected answer value for the predefined question “how would you rate the service provided by the embryologist?”. Survey-service question identifier 13 is mapped to WDM field 14 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_service_provided_by_the_embryologist']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the service provided by the embryologist?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_service_provided_by_the_embryologist'] = '0'
Parameter ID: 14
how satisfied were you with the physiotherapist's service?
how satisfied were you with the physiotherapist's service? select

The selected answer value for the predefined question “how satisfied were you with the physiotherapist's service?”. Survey-service question identifier 14 is mapped to WDM field 15 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_satisfied_were_you_with_the_physiotherapist_s_service']
Condition: No other parameter option is a prerequisite.
Reason and result: “how satisfied were you with the physiotherapist's service?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_satisfied_were_you_with_the_physiotherapist_s_service'] = '0'
Parameter ID: 15
how would you rate the facilities of the breastfeeding room?
how would you rate the facilities of the breastfeeding room? select

The selected answer value for the predefined question “how would you rate the facilities of the breastfeeding room?”. Survey-service question identifier 15 is mapped to WDM field 16 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_facilities_of_the_breastfeeding_room']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the facilities of the breastfeeding room?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_facilities_of_the_breastfeeding_room'] = '0'
Parameter ID: 16
were you satisfied with the service provided by the eye technician?
were you satisfied with the service provided by the eye technician? select

The selected answer value for the predefined question “were you satisfied with the service provided by the eye technician?”. Survey-service question identifier 16 is mapped to WDM field 17 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['were_you_satisfied_with_the_service_provided_by_the_eye_technician']
Condition: No other parameter option is a prerequisite.
Reason and result: “were you satisfied with the service provided by the eye technician?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['were_you_satisfied_with_the_service_provided_by_the_eye_technician'] = '0'
Parameter ID: 17
how would you rate the blood sampling process?
how would you rate the blood sampling process? select

The selected answer value for the predefined question “how would you rate the blood sampling process?”. Survey-service question identifier 17 is mapped to WDM field 18 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_blood_sampling_process']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the blood sampling process?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_blood_sampling_process'] = '0'
Parameter ID: 18
how would you rate the cafeteria services?
how would you rate the cafeteria services? select

The selected answer value for the predefined question “how would you rate the cafeteria services?”. Survey-service question identifier 18 is mapped to WDM field 19 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_cafeteria_services']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the cafeteria services?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_cafeteria_services'] = '0'
Parameter ID: 19
how would you rate the anesthesia process?
how would you rate the anesthesia process? select

The selected answer value for the predefined question “how would you rate the anesthesia process?”. Survey-service question identifier 19 is mapped to WDM field 20 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_anesthesia_process']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the anesthesia process?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_anesthesia_process'] = '0'
Parameter ID: 20
were you satisfied with the service provided by the dental technician?
were you satisfied with the service provided by the dental technician? select

The selected answer value for the predefined question “were you satisfied with the service provided by the dental technician?”. Survey-service question identifier 20 is mapped to WDM field 21 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['were_you_satisfied_with_the_service_provided_by_the_dental_technician']
Condition: No other parameter option is a prerequisite.
Reason and result: “were you satisfied with the service provided by the dental technician?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['were_you_satisfied_with_the_service_provided_by_the_dental_technician'] = '0'
Parameter ID: 21
how would you rate the in-clinic coordination and guidance?
how would you rate the in-clinic coordination and guidance? select

The selected answer value for the predefined question “how would you rate the in-clinic coordination and guidance?”. Survey-service question identifier 21 is mapped to WDM field 22 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_in_clinic_coordination_and_guidance']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the in-clinic coordination and guidance?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_in_clinic_coordination_and_guidance'] = '0'
Parameter ID: 22
what was your experience with the mobile application?
what was your experience with the mobile application? select

The selected answer value for the predefined question “what was your experience with the mobile application?”. Survey-service question identifier 22 is mapped to WDM field 23 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['what_was_your_experience_with_the_mobile_application']
Condition: No other parameter option is a prerequisite.
Reason and result: “what was your experience with the mobile application?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['what_was_your_experience_with_the_mobile_application'] = '0'
Parameter ID: 23
how satisfied were you with the service of the radiotherapy team?
how satisfied were you with the service of the radiotherapy team? select

The selected answer value for the predefined question “how satisfied were you with the service of the radiotherapy team?”. Survey-service question identifier 23 is mapped to WDM field 24 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_satisfied_were_you_with_the_service_of_the_radiotherapy_team']
Condition: No other parameter option is a prerequisite.
Reason and result: “how satisfied were you with the service of the radiotherapy team?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_satisfied_were_you_with_the_service_of_the_radiotherapy_team'] = '0'
Parameter ID: 24
how would you rate the process of sharing results and discussing results?
how would you rate the process of sharing results and discussing results? select

The selected answer value for the predefined question “how would you rate the process of sharing results and discussing results?”. Survey-service question identifier 24 is mapped to WDM field 25 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_process_of_sharing_results_and_discussing_results']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the process of sharing results and discussing results?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_process_of_sharing_results_and_discussing_results'] = '0'
Parameter ID: 25
to what extent were you satisfied with the resolution process of your complaints?
to what extent were you satisfied with the resolution process of your complaints? select

The selected answer value for the predefined question “to what extent were you satisfied with the resolution process of your complaints?”. Survey-service question identifier 25 is mapped to WDM field 26 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['to_what_extent_were_you_satisfied_with_the_resolution_process_of_your_complaints']
Condition: No other parameter option is a prerequisite.
Reason and result: “to what extent were you satisfied with the resolution process of your complaints?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['to_what_extent_were_you_satisfied_with_the_resolution_process_of_your_complaints'] = '0'
Parameter ID: 26
how would you rate your experience using the website?
how would you rate your experience using the website? select

The selected answer value for the predefined question “how would you rate your experience using the website?”. Survey-service question identifier 26 is mapped to WDM field 27 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_your_experience_using_the_website']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate your experience using the website?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_your_experience_using_the_website'] = '0'
Parameter ID: 27
how did you find the process of submitting your complaints and receiving feedback?
how did you find the process of submitting your complaints and receiving feedback? select

The selected answer value for the predefined question “how did you find the process of submitting your complaints and receiving feedback?”. Survey-service question identifier 27 is mapped to WDM field 28 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_did_you_find_the_process_of_submitting_your_complaints_and_receiving_feedback']
Condition: No other parameter option is a prerequisite.
Reason and result: “how did you find the process of submitting your complaints and receiving feedback?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_did_you_find_the_process_of_submitting_your_complaints_and_receiving_feedback'] = '0'
Parameter ID: 28
how would you rate the in-hospital guidance and transfer process?
how would you rate the in-hospital guidance and transfer process? select

The selected answer value for the predefined question “how would you rate the in-hospital guidance and transfer process?”. Survey-service question identifier 28 is mapped to WDM field 29 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_in_hospital_guidance_and_transfer_process']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the in-hospital guidance and transfer process?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_in_hospital_guidance_and_transfer_process'] = '0'
Parameter ID: 29
were you satisfied with the video clinic (remote consultation) service?
were you satisfied with the video clinic (remote consultation) service? select

The selected answer value for the predefined question “were you satisfied with the video clinic (remote consultation) service?”. Survey-service question identifier 29 is mapped to WDM field 30 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['were_you_satisfied_with_the_video_clinic_remote_consultation_service']
Condition: No other parameter option is a prerequisite.
Reason and result: “were you satisfied with the video clinic (remote consultation) service?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['were_you_satisfied_with_the_video_clinic_remote_consultation_service'] = '0'
Parameter ID: 30
how would you rate the content and scope of the check-up?
how would you rate the content and scope of the check-up? select

The selected answer value for the predefined question “how would you rate the content and scope of the check-up?”. Survey-service question identifier 30 is mapped to WDM field 31 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_content_and_scope_of_the_check_up']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the content and scope of the check-up?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_content_and_scope_of_the_check_up'] = '0'
Parameter ID: 31
what was your experience communicating with the call center?
what was your experience communicating with the call center? select

The selected answer value for the predefined question “what was your experience communicating with the call center?”. Survey-service question identifier 31 is mapped to WDM field 32 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['what_was_your_experience_communicating_with_the_call_center']
Condition: No other parameter option is a prerequisite.
Reason and result: “what was your experience communicating with the call center?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['what_was_your_experience_communicating_with_the_call_center'] = '0'
Parameter ID: 32
how would you rate the appointment and service scheduling?
how would you rate the appointment and service scheduling? select

The selected answer value for the predefined question “how would you rate the appointment and service scheduling?”. Survey-service question identifier 32 is mapped to WDM field 33 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['how_would_you_rate_the_appointment_and_service_scheduling']
Condition: No other parameter option is a prerequisite.
Reason and result: “how would you rate the appointment and service scheduling?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['how_would_you_rate_the_appointment_and_service_scheduling'] = '0'
Parameter ID: 33
to what extent were you satisfied with the service of the radiology technician?
to what extent were you satisfied with the service of the radiology technician? select

The selected answer value for the predefined question “to what extent were you satisfied with the service of the radiology technician?”. Survey-service question identifier 33 is mapped to WDM field 34 during recording, and the campaign report counts this value as a select answer. Important compatibility note: survey-generation code produces predefined answer identifiers 1–5, while this WDM field defines options 0–4; because recording code writes the received value without conversion, value 5 may fall outside the schema and the scale may be offset by one.

* Parameter relationships
Parameter: operation_survey_config['to_what_extent_were_you_satisfied_with_the_service_of_the_radiology_technician']
Condition: No other parameter option is a prerequisite.
Reason and result: “to what extent were you satisfied with the service of the radiology technician?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Options and usage purposes
0 — 😞 i am definitely not satisfied
Classifies the answer as “😞 i am definitely not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
1 — 😕 i am not satisfied
Classifies the answer as “😕 i am not satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
2 — 😐 i am undecided
Classifies the answer as “😐 i am undecided”; however, value mapping must be verified because the service returns identifiers 1–5.
3 — 🙂 i am satisfied
Classifies the answer as “🙂 i am satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
4 — 😍 i am very satisfied
Classifies the answer as “😍 i am very satisfied”; however, value mapping must be verified because the service returns identifiers 1–5.
Example: 0 — 😞 i am definitely not satisfied
Example:
operation_survey_config['to_what_extent_were_you_satisfied_with_the_service_of_the_radiology_technician'] = '0'
Parameter ID: 34
could you write your general thoughts?
could you write your general thoughts? textarea

The answer to the free-text question created when general opinion is enabled in survey settings. Result code writes an answer whose question identifier is `note` or `35` into this field; campaign reporting collects a nonempty value as text answer number 35.

* Parameter relationships
Parameter: operation_survey_config['could_you_write_your_general_thoughts']
Condition: No other parameter option is a prerequisite.
Reason and result: “could you write your general thoughts?” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: Hizmetten genel olarak memnun kaldım.
Example:
operation_survey_config['could_you_write_your_general_thoughts'] = ''
Parameter ID: 35
create date
create date datetime

Defined to store the creation time of the survey-answer record, and campaign reporting first attempts to use this field for period grouping. However, the inspected timer does not write parameter 36 when creating an answer record; when it is empty, reporting falls back to the journey date.

* Parameter relationships
Parameter: operation_survey_config['create_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “create date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
operation_survey_config['create_date'] = ''
Parameter ID: 36
manuel answer list
manuel answer list list_parameter

A repeating list that stores answers to manual questions outside the 34 predefined fields. Each answer is stored with its question identifier; parameter 39, answer identifier, is used when the manual question is select type, while parameter 40, answer text, is used for other types. This preserves different manual answer types together for reporting.

* Parameter relationships
Parameter: operation_survey_config['manuel_answer_list']
Condition: No other parameter option is a prerequisite.
Reason and result: “manuel answer list” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: [{ ... }]
Example:
operation_survey_config['manuel_answer_list'] = []
Parameter ID: 37
question id
question id text

The identifier that specifies which manual question owns the answer. Because manual questions are generated as `m_0`, `m_1`, and so on in survey settings, result code writes the same `q_id` from the service response here; reporting groups questions by this identifier.

* Parameter relationships
Parameter: operation_survey_config['question_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “question id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: question id-example
Example:
operation_survey_config['question_id'] = ''
Parameter ID: 38
answer id
answer id text

The identifier of the answer option selected by the user for a select-type manual question. It is written when result input `type` is `select`; campaign reporting reads this field first and classifies a nonempty answer as select.

* Parameter relationships
Parameter: operation_survey_config['answer_id']
Condition: No other parameter option is a prerequisite.
Reason and result: “answer id” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: answer id-example
Example:
operation_survey_config['answer_id'] = ''
Parameter ID: 39
answer text
answer text textarea

The answer text supplied by the user for manual question types other than select. Result code writes incoming `answer` into this textarea without distinguishing int, float, text, textarea, date, or datetime; reporting uses it as a text answer when parameter 39 is empty.

* Parameter relationships
Parameter: operation_survey_config['answer_text']
Condition: No other parameter option is a prerequisite.
Reason and result: “answer text” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: answer text-example
Example:
operation_survey_config['answer_text'] = ''
Parameter ID: 40
answer date
answer date datetime

Defined to store the answer date of an individual manual response. The inspected survey-result recording code does not write this field, and campaign reporting does not read manual answer time from it; it must not be assumed to populate automatically in the current standard flow.

* Parameter relationships
Parameter: operation_survey_config['answer_date']
Condition: No other parameter option is a prerequisite.
Reason and result: “answer date” is populated and evaluated directly in its record context; it is not enabled or disabled by another parameter selection.
Example: 2026-10-25T09:45:55
Example:
operation_survey_config['answer_date'] = ''
Parameter ID: 41