MakeUserActiveInactive Step
Description:
This step marks a selected user as “active or inactive”.
Inputs
- workflowUserID – id of the user
- markActive – make the user active or inactive
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “makeUserActiveInactiveDef” example.
- Create a new process definition called “makeUserActiveInactiveDef” and open it in Designer mode.
- Drag a " getWorkflowUserID, makeUserActiveInactive” step to the canvas.
- Connect the dots between the “Start” step and other steps, as shown above.
- Define a variable or a global to store the UserID and UserName.
- Click the “getWorkflowUserID” step to configure its “Required” properties. Provide a name for the step, the username to fetch, and the variable or global to store the user ID after execution. Click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description.
- Click the “makeUserActiveInactive” step to configure its “Required” properties. Provide a name for the step. Specify the variable or global that contains the user ID from the previous steps. Select “Yes” to mark the user inactive. Click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description.
- Alternatively, you may copy and paste the workflow User ID from the User Management page.
- The “Logging” configuration is necessary for documentation and also measures workflow progress and 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 instance, and execute it. Render the process instance to check the step properties. The step configures the user as “active” or “inactive” based on the configuration.
Definition Sample:
You may download the sample definition(s) from the link here and later import them (drag-and-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 the import. Then, save the definition to confirm the changes.