Step 6: Editing Swimlanes and Copy/Pasting a Module
Estimated Reading Time: 5 minutes
Introduction
Up to this point, your workflow application consists of one Task node that contains the completed Employee Informationmodule. Part of the employee information your module collects is email addresses from the employee and manager. While the Email component has some built-in validation, it only applies to the format of email addresses. If end-usersEnd-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. enter an email address that is the correct format but isn't a company email address, the validation won't catch it. In this use case, you'll add additional validation to ensure end-users enter email addresses that include the @unqork.com company domain. To do this, you'll continue working on your workflow application, configure swimlanes, and copy and past a verification module into another Task node.
Start by opening the workflow-type application you previously created in the Workflow Builder.
1.
Open your Workspace. You can find your Workspace by selecting (Search magnifying glass) and entering Creator Workshop Workspace [your name].
2.
In your Workspace, select View App on your application tile. Your application title will be [initials] + “Creator Workshop App” + [date you created the application].
3.
From the menu to the left of the Application page, select Workflows.
Under Include in Navigation, select All Tasks Until Lane Change. This lets end-users see all nodes before the workflow switches to a new swimlane.
9.
Click Save.
Add the Email Validation Task Node
Now that your swimlanes are set up, you'll add your Email ValidationTask node. As you learned, Automated swimlanes handle all background processes, such as script or service-type tasks. These tasks have no end-user interaction. Since validation occurs behind the scenes, you'll create it in the Automated swimlane.
1.
Drag and drop a Task node into the Automated swimlane.
2.
Select your new Task node to open its Settings Menu.
3.
Click Edit to open the Edit User Task menu.
4.
In the Label field, enter Email Validation.
5.
Under Module, select Create New Module. The Module Title and Module Path populate with default values.
6.
In the Module Type drop-down field, select FE Front-End.
Disconnect the Employee Information Task node from the End node by clicking on the arrow connection and pressing Delete (Return) on your keyboard.
9.
Connect the output port (right) of the Employee Information Task node to the input port (right) of the Email Validation Task node.
10.
Connect the output port (right) of the Email Validation Task node to the input port (right) of the End node.
11.
Save... your workflow.
12.
In the Save to Version History window, click Save.
Create the Email Verification Module
The Email Validationmodule you just created in your Email Validation Task node is currently blank. Instead of configuring a new module, you can copy and paste another Unqork module into it. Start by copying the Email Validationmodule definition to validate employee email addresses and ensure they include the @unqork.com company email domain. Then, paste the module definition into your new Email Validation Task module. You'll review each part of this module configuration in detail in the Step 7 use case article.
If the module works as expected, it will automatically intake your employee's email address entry, compare it to the @unqork.com company domain, and then return a valid or invalid response.
From here, try filling in the Employee Email field with and without email addresses that end with the @unqork.com domain. Once you complete the workflow process, the employeeEmailValidationHidden component in the Email Validationmodule holds the "Valid" or "Invalid" validation result of your entry.
Before you go on to the next article, remember to move your Email Validation Task node from the Employee swimlane back to the Automated swimlane. Then, Save... your workflow.
In this use case article, you configured your Authenticated swimlane to the trainingApplicant role for employee end-usersEnd-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.. You then added a Task node to your Automated lane and copy/pasted an Email Validationmodule definition your Email Validation Task node's module. This module validates the email address entered by the end-user in the Employee Email Address field. If the employee email domain is @unqork.com, the "Valid" response is held in the employeeEmailValidationHidden component in the Email Validationmodule. If the employee email domain isn't @unqork.com, the "Invalid" response is held there instead.
In the next use case article, you'll continue your workflow configuration by splitting your workflow path in two different directions using the Exclusive Gateway node. For end-users who's emails were "Valid", you'll configure a pathway that continues the employee travel request process. For "Invalid" emails, an email is sent to notify the end-user and the workflow ends.
Continue Your Learning
In the next article, you'll begin Step 7 of the Building Your First App learning module. In the first article of Step 7, you'll learn about Initializer components and how to configure them in the Module Builder.