Description:
This step fetches the server CPU and the available memory resources.
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 definition called “getCPUMemoryUtilizationDef”
- Select the definition and click the “design” button
- Drag a "getCPUMemoryUtilizationDef" step from the toolbox
- Connect the dots between the start and “getCPUMemoryUtilizationDef” step
- Define variables/globals to store the CPU and Memory values during execution
- Click the “getCPUMemoryUtilizationDef” step to configure its “Settings” properties. Provide a name to the step. Click on the button to configure the parameters for the business object.
- The “Logging” setting configuration is necessary for documentation and also measures the workflow progress and the percent complete. This is achieved 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 process instance, and execute. Render the process instance. Click on the process step to view the properties. The step should get the server CPU and Memory resources
Definition Sample:
You may download the sample definition(s) from the link here and later import it (drag-drop) to 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 import. Then, save the definition to confirm the changes.