Process Administration Custom Variables

You have the option to alter who may use some Process Director functions by restricting their use to Process Administrators. The custom variables in this section define which actions can be restricted to process administrators.

fDisableAsyncWorkflow

This boolean variable, when set to true, will disable any asynchronous process steps in a process definition. The default value is false. This setting is primarily for use in development systems.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
bp.Vars.fDisableAsyncWorkflow = true; // Disable async processes
}

fInternalDSPadminOnly

This boolean variable sets whether only Process Administrators are allowed to configure internal Datasources. The default value is true.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
bp.Vars.fInternalDSPadminOnly = true; // Only P-Admins can config
}

fInternalUserDSPadminOnly

This boolean variable sets whether only Ptocess Administrators are allowed ro configure internal user Datasources. The default value is true.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
bp.Vars.fInternalUserDSPadminOnly = true; // Only P-Admins can config
}

fNewSkipPendingLogic

For Process Director v5.36 and higher, the logic for evaluating the Activity Result system variable was changed to skip activity instances that were marked as not needed. This can cause an issue for customers that used the system variable that on conditions to control looping when using the legacy Branch Activity Type, instead of the Looping conditions on a Parent Activity Type. Setting this variable to "false" disables the new logic. The default value for this variable is "true".

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
// Use the old Activity Result logic for Branch activities
bp.Vars.fNewSkipPendingLogic = false;
}

fReportViewsPadminOnly

This boolean variable sets whether only Process Administrators are allowed to configure views in reports. The default value is true.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
bp.Vars.fReportViewsPadminOnly = true; // Only P-Admins can config
}

fScriptsPadminOnly

This boolean variable sets whether only System Administrators are allowed to configure scripts in Forms, Process Timelines, and Knowledge Views. The default value is false.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
bp.Vars.fScriptsPadminOnly = false; // Anyone can config
}

nAsyncSubProcessWaitSecs

This variable enables you to control the number of seconds that Process Director should wait for an asynchronous subprocess to complete. On some systems, when starting a subprocess using the "Run Asynchronously" and the "Wait for subprocess to complete" options, the system can mark the calling task as complete before the called subprocess completes. This may be especially true if the subprocess contains complex rendering operations. This variable adds a 5-second wait time as a default, to help ensure the subprocess has time to complete.

Example

public override void PreSetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    // Wait 5 seconds before marking the
    // calling task as complete
    bp.Vars.nAsyncSubProcessWaitSecs = 5;
}

Documentation Feedback and Questions

If you notice some way that this document can be improved, we're happy to hear your suggestions. Similarly, if you can't find an answer you're looking for, ask it via feedback. Simply click on the button below to provide us with your feedback or ask a question. Please remember, though, that not every issue can be addressed through documentation. So, if you have a specific technical issue with Process Director, please open a support ticket.

Send Feedback to BP Logix

Related Topics

Process Administration Custom Variables

Example

Example

Example

Example

Example

Example

Example

Documentation Feedback and Questions