Jump to: navigation, search

ETL Section

PDF This Page



     


AdhDaysBack

Default Value: DaysBack option value
Valid Values: Any positive integer
Changes Take Effect: Next ETL cycle
Dependencies: AdhEnable must be set to true
Introduced: 8.5.100.10

Specifies a value that overrides the DaysBack option value for the Adherence data.

If not specified, WFM uses the DaysBack option value.

>> Back to Top

AdhEnable

Default Value: true
Valid Values: true, false
Changes Take Effect: Next ETL cycle
Introduced: 8.5.100.10

Specifies whether ETL is enabled or disabled for the Adherence data.

>> Back to Top

DayChunk

Default Value: 7
Valid Values: Any integer between 1 and 31
Changes Take Effect: Immediately
Dependencies: Should be less than (DaysBack+ DaysAhead)

Specifies the number of days that will be processed at a time.

The tracked day range is defined by the values set in the DaysBack and DaysAhead parameters and is processed in the specified chunks of data. So, this parameter determines the size of transaction.

Larger transactions require more memory and other resources, but can be processed faster.

>> Back to Top

DaysAhead

Default Value: 14
Valid Values: Any integer between 1 and 365
Changes Take Effect: Immediately
Dependencies: None

Specifies the number of days (from current date) in the future to track Fact data.

>> Back to Top

DaysBack

Default Value: 14
Valid Values: Any integer between 0 and 365
Changes Take Effect: Immediately
Dependencies: None

Specifies the number of days (from the current date) in the past to track Fact data.

>> Back to Top

ETLTimeout

Default Value: 180
Valid Values: Any integer between -2880 and 2880
Changes Take Effect: Immediately
Dependencies: None
Introduced: 8.5.200.05

Specifies the timeout interval (in minutes) between each execution of the Extract, Transform, and Load (ETL) process.

If you set this option to a negative value the first ETL cycle starts immediately after server is started. If you set this option to 0 the ETL process is disabled.

>> Back to Top

MaxPurgeChunk

Default Value: 100000
Valid Values: Any positive integer
Changes Take Effect: At the start of the Purge cycle after the next ETL cycle
Introduced: 8.5.218.29

Specifies the maximum number of records to be purged in one transaction.

>> Back to Top

PerfDaysAhead

Default Value: DaysAhead option value
Valid Values: Any positive integer
Changes Take Effect: Next ETL cycle
Dependencies: PerfEnable must be set to true
Introduced: 8.5.100.10

Specifies a value that overrides the DaysAhead option value for the Performance statistics data.

If not specified, WFM uses the DaysAhead option value.

>> Back to Top

PerfDaysBack

Default Value: DaysBack option value
Valid Values: Any positive integer
Changes Take Effect: Next ETL cycle
Dependencies: PerfEnable must be set to true
Introduced: 8.5.100.10

Specifies a value that overrides the DaysBack option value for the Performance statistics data.

If not specified, WFM uses the DaysBack option value.

>> Back to Top

PerfEnable

Default Value: true
Valid Values: true, false
Changes Take Effect: Next ETL cycle
Introduced: 8.5.100.10

Specifies whether ETL is enabled or disabled for the Performance statistics data.

>> Back to Top

PurgeDate

Default Value: empty
Valid Values: Any date (In the same format as the host settings. For example, 10/21/2021.)
Changes Take Effect: After the next ETL cycle
Dependencies: Overrides the PurgeDaysBack option
Introduced: 8.5.218.29

Specifies the exact date to purge data that is older than the specified date.

Tip
The PurgeDaysBack option is the main purge option that enables a rolling data purge. This option is an optional override that can be used in special cases, when required.
>> Back to Top

PurgeDaysBack

Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: After the next ETL cycle
Dependencies: The PurgeDate option overrides this option.
Introduced: 8.5.218.29

Specifies the number of days from the current date to calculate a cut-back purge date. Data that is older than the calculated purge date is purged after each ETL cycle, up to the maximum number of records specified in the MaxPurgeChunk option.

If this option value is not specified or is set to 0, and the PurgeDate option value is also not specified, WFM does not purge any data.

Tip
This option is the main purge option that enables a rolling data purge. The PurgeDate option is an optional override that can be used in special cases, when required.
>> Back to Top

SchDaysAhead

Default Value: DaysAhead option value.
Valid Values: Any positive integer
Changes Take Effect: Next ETL cycle
Dependencies: SchEnable must be set to true
Introduced: 8.5.100.10

Specifies a value that overrides the DaysAhead option value for the Schedule data.

If not specified, WFM uses the DaysAhead option value.

>> Back to Top

SchDaysBack

Default Value: DaysBack option value
Valid Values: Any positive integer
Changes Take Effect: Next ETL cycle
Dependencies: SchEnable must be set to true
Introduced: 8.5.100.10

Specifies a value that overrides the DaysBack option value for the Schedule data.

If not specified, WFM uses the DaysBack option value.

>> Back to Top

SchEnable

Default Value: true
Valid Values: true, false
Changes Take Effect: Next ETL cycle
Introduced: 8.5.100.10

Specifies whether ETL is enabled or disabled for the Schedule data.

>> Back to Top
This page was last edited on July 13, 2017, at 17:51.
Comments or questions about this documentation? Contact us for support!