Server Disk Space

Use this step to understand the disk space on the app server.

Last published at: September 10th, 2025

Server Disk Space Step

Description:

The Server Disk Space workflow step retrieves the disk-space information for the specified server drive and stores the resulting value in the selected Variable or Global.

The step supports:

  • Specifying the server drive to inspect.
  • Retrieving the disk-space value for the specified drive.
  • Storing the result in a FlowWright Variable or Global.
  • Using the stored value in subsequent workflow processing.
  • Checking server storage information before storage-intensive workflow activities.
  • Returning a True or False result for workflow routing.

 

Inputs

  • driveLetter - Specifies the server drive for which disk-space information should be retrieved.
  • varGlobalToStore - Specifies the FlowWright Variable or Global where the disk-space result is stored.
 

 

Returns

  • True – The True return path can be connected to the next workflow activity when the Server Disk Space operation completes successfully.
  • False – The False return path can be used for error handling or an alternative workflow path.
 

 

Usage:

The ClsServerDiskSpaceAvailable step can be used when a workflow needs server disk-space information as part of its processing.

A typical pattern is:

Determine Drive
      ↓
Server Disk Space
      ↓
Store Disk-Space Value
      ↓
Evaluate / Use Result
      ↓
Continue Workflow
For example, a workflow could retrieve the disk-space information for the C: drive and store it in a Variable named:
ServerDiskSpace
A subsequent workflow step can then use that Variable as appropriate for the workflow's business or operational logic.

 

 

Typical Workflow Suggestions:

Check Server Disk Space Before File Processing

Use the step before a workflow performs file-processing activities that may require significant server storage.

Example:

Start → Server Disk Space → File Processing
The disk-space value can be stored in a Variable and used by subsequent workflow logic.

 

Check Disk Space Before Document Generation

Use the step before generating documents, reports, or other files.

Example:

Start → Server Disk Space → Generate Documents
This allows the workflow to retrieve the server disk-space value before starting the document-generation operation.

 

Check Disk Space Before Large File Operations

Use the step before workflows that create, copy, convert, or otherwise process files.

Example:

Prepare Files → Server Disk Space → Process Files
A subsequent workflow step can evaluate the stored result if the process requires storage-related decision logic.

 

Store Disk-Space Information for Later Processing

The step can store the retrieved value in a Variable or Global for later use.

Example:

Server Disk Space → Store Result → Subsequent Processing
For example:
Drive Letter:
C:

Variable/Global:
ServerDiskSpace
The XML explicitly provides the varGlobalToStore property for this purpose.

 

Use Disk-Space Information in a Decision

Use a subsequent decision or evaluation step to process the stored disk-space value.

Example:

Server Disk Space
        ↓
Evaluate Stored Value
        ↓
   ┌────┴────┐
   ↓         ↓
Continue   Alternate Path
The Server Disk Space step itself does not define a disk-space threshold or comparison operation in the XML, so threshold evaluation should be performed by a subsequent workflow activity.

 

Route Processing Using the Return Paths

Use the True and False return paths to provide separate workflow paths.

Example:

                    ┌── True ──→ Continue Processing
                    │
Start → Server Disk Space
                    │
                    └── False ─→ Error Handling
The step definition provides both return paths.

 

Check Multiple Server Drives

When a workflow needs information for more than one drive, multiple Server Disk Space steps can be used.

Example:

Server Disk Space (C:)
        ↓
Server Disk Space (D:)
        ↓
Evaluate Results
Each step can store its result in a separate Variable or Global.

For example:

C: → SystemDriveSpace
D: → DataDriveSpace
 

Check Disk Space Before DMS Processing

Use the step before a workflow performs a large document-management operation such as processing or generating a large collection of files.

Example:

Start
  ↓
Server Disk Space
  ↓
DMS/File Processing
  ↓
Complete
This provides the workflow with disk-space information before the storage-intensive activity begins.

 

Prepare Storage Information for Notifications

The stored disk-space value can be supplied to a later notification or reporting step.

Example:

Server Disk Space
        ↓
Build Notification
        ↓
Send Notification
For example, a later message could incorporate the stored value into an operational status notification.

 

Record Server Storage Information

Use the step as part of an operational or administrative workflow that records server information.

Example:

Server Disk Space
        ↓
Create Operational Record
        ↓
Complete
The XML only defines retrieval and storage of the disk-space value; it does not define built-in logging or reporting behavior.

 

Use a Global for Shared Operational Information

If the workflow design requires the disk-space result to be available through a Global, specify the appropriate Global in the Variable or global to store size property.

Example:

Server Disk Space
        ↓
Global: ServerDiskSpace
        ↓
Other Workflow Activities
 

Example:

Let’s build and execute the “clsServerDiskSpaceAvailableDef” example.                 

  • Create a new definition named “clsServerDiskSpaceAvailableDef” and open it in designer mode. 
  • Drag a "clsServerDiskSpaceAvailable" step to the canvas. 
  • Connect the dots between the “Start” step and the "clsServerDiskSpaceAvailable" step, as shown above. 
  • Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
  • Click the "clsServerDiskSpaceAvailable" step to configure its "Required" properties. Provide a name for the step. Select the connection string. Enter the Tenant Name or GUID value. Click the button to enter the SQL string. Click the Save button. Note: Click the "AI Predict" button for Copilot to add new process steps that match your process description. 

 

  • The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. Configure the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

 

  • Save the process definition, create a process instance, and execute it. As configured, the process step should retrieve the server disk space from the app server.

 

Tips:

  • Use a valid drive letter that is available on the server where the workflow executes.
  • Keep the Variable or Global name meaningful, such as ServerDiskSpace, AvailableDiskSpace, or DataDriveSpace.
  • Verify the actual meaning of the returned disk-space value before using it in calculations or threshold comparisons.
  • Verify the unit of measurement before implementing numeric comparisons.
  • Test the step using each drive that will be used in the production workflow.
  • Test the workflow with an invalid or inaccessible drive to understand the resulting behavior.
  • Connect the True and False paths to appropriate downstream activities.
  • Do not assume that the True/False return paths represent a particular disk-space threshold; the XML does not define such a threshold.
  • Use separate Variables or Globals when checking multiple drives.
  • If the result is subsequently displayed to users, format the value according to the actual unit returned by the implementation.
  • Avoid hard-coding disk-space thresholds until the returned value and its unit have been verified.
  • When using this step in operational workflows, record sufficient context, such as the drive being checked.
  • Test the workflow under realistic server-storage conditions.
  • Keep server and infrastructure information out of user-facing messages unless it is required.
  • If the same disk-space information is needed by several workflow activities, store it in a clearly named Variable or Global.
  • Verify the stored value after execution before depending on it in downstream processing.

 

Definition Sample:

You may download the sample definition and later import it into your FlowWright Process Definition (XML file) or Form Definition (HTML file).

Note: Verify and complete any missing configuration after importing the sample, including:

  • Drive letter.
  • Variable or Global used to store the result.
  • Workflow Variable references.
  • Environment-specific settings.
  • Downstream True and False workflow paths.
  • Any disk-space comparison or threshold logic.

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.