Related Topics
System Custom Variables
This section covers various System items and settings.
fDebugInsertLockData
This variable when set to "true", will let the system automatically execute a SQL command when a database timeout occurs on an UPDATE command. The default value for this variable is "false".
When set to true, the default SQL that is executed will insert records into a table named TEMP_LOCK_LIST and this table needs to exist prior to setting the variable to "true". You can create this table in the process Director installation by running this SQL command:
CREATE TABLE TEMP_LOCK_LIST (SPID int, BLOCKED int, BATCH nvarchar(max))
Once this table exists, this variable will insert records in to the table when locks are found. You can use the table to pull out any lock conditions via SQL query.
Example
public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
bp.Vars.fDebugInsertLockData = true;
}
fEnableCSRF1Protection/fEnableCSRF2Protection
These variables when set to "false", will alter certain aspects of CSRF protection. Occasionally errors may occur on the system in rare circumstances that can be addressed by changing these variable settings.
Example
public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
Vars.fEnableCSRF1Protection = false;
Vars.fEnableCSRF2Protection = false;
}
nTimelineUnwindLoopCount
This variable enables you to change the number of times the system will allow a process instance activity check to start processing from the top again. The default is 10 times.
Example
public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
// Allow 15 restarts
bp.Vars.nTimelineUnwindLoopCount = 15;
}
Document Feedback
If you notice some way that this document can be improved, we're happy to hear your suggestions. Click on the button below to provide us with your feedback. Please remember, though, that not every issue can be addressed through documentation. So, if you have a specific technical issue, please open a support ticket.
