Exercises

To ensure you gain a solid understanding of the Workmaster platform, we've designed a series of practical exercises tailored to guide you through key features and workflows. These exercises will help you build your skills step-by-step, from basic tasks to advanced functionalities, empowering you to create, design, and launch powerful apps with ease. By following this exercise series, you'll develop a hands-on understanding of the platform, enabling you to maximize your productivity and unlock the full potential of Workmaster. Get ready to dive in and take your app-building skills to the next level!

Exercise 1:

Build branding elements that evoke a strong corporate identity from three different well-known organizations whose brand is well-represented on the web. (Example, Coca-cola, IBM, Tesla)

Exercise 2:

The user will be asked to create a single app with a frame page, an initial home page from which the user can navigate to one of three different pages. The frame page should have a heading area with a menu button that lets an end user navigate to other pages via a side panel of menus. It should also have an ‘About’ icon that triggers a popup showing a message.

Exercise 3:

The user should populate the pages completed in exercise M2 with each type of widget discussed above:

Containers: use a 3 column grid container that switches to two columns in tablet view and single column in mobile view.

Fields: Build a two column form comprising each of the field types.

Page containers: build a page with page container that shifts in from the left or right two or more pages when a ‘Next’ and ‘Back’ button are pressed.

Data Lists: Use a ‘Data list’ widget to show the names, descriptions and images of all apps in a classic ‘card’ layout.

Exercise 4:

Set the simulator to start from the first page of the user’s app. Test the same page in online desktop app, send a link to the simulated app to other users.

Exercise 5:

The user will be asked to build a page container within a page a ‘Forward’ and ‘Back’ buttons. These buttons will change the contents of the page from a selected list of pages. The correct animation should be used – right-to-left when ‘Forward’ is pressed and ‘left-to-right’ when ‘Back’ is pressed. In addition, the user should pause the rule and examine the values of any condition or action’s formulae.

Exercise 6:

Create the data objects for a CRM including InventoryItem, Order, Customer, Bill, LineItem. Add the fields of these items. Link them together in a logical way. Describe the purpose of each data object and finally prepare them for testing by populating test data for each data object.

Exercise 7:

Create a ‘Join’ queries to retrieve all order item names by ordering customer and date of bill. Create another Join query – this time of all line orders by date. Combine the two into a union query and examine the results in the Data Viewer. Check that the data is consistent with expectations.

Exercise 8:

Build a dashboard to summarize the sale of items by month with drill-down to days. A chart should auto-summarize the type and count of items sold in the selected period. Tables to give details, filters and cards to give total counts and value to be added. The dashboard should be interactive with clear guidelines and a visually pleasing style for both desktop and mobile use.

Exercise 9:

Add authentication to the CRM app that was previously developed. When the user needs to pay, the app will check if the user is logged in and if not, they are asked to log in or create an account.

Exercise 10:

Attach a chatbot to the shopping app so that it can answer user’s queries about items, costs and appropriate items to buy, and contents of their shopping trolley. Add actions to add an item or remove an item from the shopping trolley. Add a command to navigate to different pages within the app.

Exercise 11:

Design a process for a ‘Supplier signup page’ in the Shopping app. This process is used by companies that wish to become suppliers of items for the shooping organization. The end user should be asked to submit a signed agreement, supply fields such as organization name, primary contact email, company logo and the category (a drop-down) of items they wish to supply. The process should go through two levels of approval (so roles or ‘Applier’, “Level 1 Approver’ and ‘Level 2 Approver’). At each stage an approver may send the application back to the user with comments captured in a field for their attention. After final approval, a field ‘approved’ should be set to ‘true’ in the data object. The process should be linked to a data object ‘Supplier Application’. Build a dashboard that shows the number or application at each task of the process, along with a drilldown to details, and a table showing the fields of each filtered application. Start and lead several processes to completion as test cases.

Exercise 12:

Execute a Zap in Zapier. Fetch data from Monday and airtable.

Exercise 13:

Build the shopping app as a mobile app for android and iOS, and then download and test it on both platforms.