Process Director v4.55 and higher logs XML import events, goal evaluations, and Active Directory syncs by default, which means that the default value for this variable is "true". This logging can be turned off by setting this variable to false.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Turn off database logging for imports, AD Syncs, etc.
    bp.Vars.fEnableDatabaseLogs = false;
}

This variable, when set to "false", will prevent the Active Directory Sync Log History from from logging most events at the "info" level (i.e., it will only log warnings and errors). This should substantially reduce the number of logs in the tblLogs table in the database, but you may still want to clear out the old logs prior to setting this variable. You can do so by adjusting the nImportLogSyncDays variable to 0, then running the global timer routines in the Troubleshooting window. Once complete, you can reset nImportLogSyncDays to the desired value. This Variable can be used in conjunction with the nMaxADSyncLogEvents variable to control the length of AD synchronization audit logs. The default value for this variable is "true".

Prior to Process Director v5.3, clearing out the old logs requires resetting the nImportLogDays Custom Variable. The nImportLogDays was deprecated in v5.3 and replaced with nImportLogSyncDays.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Prevent detailed AD Sync logging
    Vars.fKeepADSyncInfoLogs = false;
}

This variable enables you to control the number of days that Process Director should retain its logs. Logs will be archived in the /App_Data/log_archive/ folder. This custom variable is available only with users who have the Compliance edition for on-site installations, or a cloud installation.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.nArchiveLogDays = 7; // archives logs for a week
}

This Custom Variable has been deprecated in Process Director v5.3.

Process Director v4.55 and higher logs XML import events, goal evaluations, and Active Directory syncs by default, and stores the logs for 30 days. This variable enables you to change the duration from 30 days, to a number of days of your choice.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Keep logs for 45 days
    bp.Vars.nImportLogDays = 45;
}

Process Director v5.3 and higher logs goal evaluations by default, and stores the logs for 30 days. This variable enables you to change the duration from 30 days, to a number of days of your choice.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Keep Goal logs for 2 days
    bp.Vars.nImportLogGoalDays = 2;
}

Process Director v5.3 and higher logs XML imports by default, and stores the logs for 30 days. This variable enables you to change the duration from 30 days, to a number of days of your choice.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Keep XML import logs for 15 days
    bp.Vars.nImportLogImportDays = 15;
}

Process Director v5.3 and higher logs Knowledge View executions by default, and stores the logs for 30 days. This variable enables you to change the duration from 30 days, to a number of days of your choice.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Keep KV run logs for 5 days
    bp.Vars.nImportLogKVRunDays = 5;
}

Process Director v5.3 and higher logs Machine Learning object publications by default, and stores the logs for 30 days. This variable enables you to change the duration from 30 days, to a number of days of your choice.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Keep ML Pub logs for 5 days
    bp.Vars.nImportLogMLPublishDays = 5;
}

Process Director v5.3 and higher logs Stream Action runs by default, and stores the logs for 30 days. This variable enables you to change the duration from 30 days, to a number of days of your choice.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Keep SA run logs for 5 days
    bp.Vars.nImportLogSArunDays = 5;
}

Process Director v5.3 and higher logs Active Directory synchronizations by default, and stores the logs for 30 days. This variable enables you to change the duration from 30 days, to a number of days of your choice.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Keep AD Sync logs for 5 days
    bp.Vars.nImportLogSyncDays = 5;
}

This variable sets the maximum number of synchronization log events that will be displayed on the Active Directory Sync Log History page.

Example

public override void SetSystemVars (BPLogix.WorkflowDirector.SDK.bp bp)
{
    //Default is 200
    bp.Vars.nMaxADSyncLogEvents = 100;
}

This variable enables you to set the maximum number of log files. After a log file reaches the size configured by nMaxLogFileSize, it will “wrap” in a circular log file queue.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Keep a maximum of 20 wrapping log files
    bp.Vars.nMaxLogBackups = 20;
}

This variable enables you to set the maximum size of the wrapping log files. Specify this value in kilobytes.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // This will set the maximum log file size to 3 meg.
    bp.Vars.nMaxLogFileSize = 3000;
}