Description:
This step retrieves the server's CPU usage and available memory.
Inputs
- varGlobalToStoreCPU – Variable or global to CPU use
- varGlobalToStoreMemory – Variable or global to Memory use
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “getCPUMemoryUtilizationDef” example.
- Create a new process definition named “getCPUMemoryUtilizationDef” and open it in the designer.
- Drag a "getCPUMemoryUtilizationDef" step to the canvas.
- Connect the dots between the “Start” and “getCPUMemoryUtilizationDef” steps, as shown above.
- Define variables or globals to store the CPU and Memory values.
- Click the “getCPUMemoryUtilizationDef” step to configure its “Required” properties. Provide a name for the step. Click the button to configure the business object’s parameters, then click Save. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- The “Logging” configuration is necessary for documentation and to measure workflow progress and percent complete. This is done by configuring 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 new instance, and execute it. Render the process instance. Click the process step to view its properties. The step should retrieve the server's CPU and memory usage.
Definition Sample:
You may download the sample definition(s) from the provided link and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.
Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after the import. Then, save the definition to confirm the changes.