Training Exercise

You have now learnt how to create and configure Actionflows requiring advanced business logic and can competently use all Actionflow features. To reinforce the techniques you have learnt, complete these assignments. 

Don't worry, this is not an exam. You can use the Help to broaden your understanding and assimilate knowledge. A number of hints have been provided; use these if you are struggling as each hint gives you more information on the solution.  

.Remember to close and reopen your screen if you do not see the changes you expect.

countElements(in.Colours)

do(
	debug("This is a count of colours: " + in.Colours),
	countElements(in.Colours)
)

Assignment 1

Difficulty Level: 

Task 1

When deleting rejected companies in bulk, we need to also delete all employees associated with that company from the application. 

• On the Company Rejected Companies screen, modify the Actionflow that you created in 3.01 Bulk Delete Action Configuration on the Delete All button to also delete all employees associated with the rejected companies
  

.

Task 2

On the Company Approval Review screen, the area holding the  icon requires setup to allow companies to be dragged and dropped onto this area and then subsequently rejected.

• If you have not already completed the optional example, Example 2: Reject Company Using Drag and Drop on 3.04 Drag and Drop Configuration, configure this now

The Actionflow must:

• Set the Company's Status to Rejected
• Update the Company's UpdatedByName attribute, using the same syntax as can be seen in the existing data
• Update the Company's UpdatedTime attribute

Assignment 2

Difficulty Level: 

Task 1

When deleting rejected companies in bulk, we need to provide the user with more details, such as counts of the companies, orders and employees that will be affected by the deletion. In addition, we should give the user the ability to cancel or confirm the deletion using this information.

• Add the confirmation screen, Company Bulk Delete Confirmation, to the Actionflow on the Delete All button on the Company Rejected Companies screen
• In the Actionflow, create counts of the affected companies, orders and employees, and map these onto the screen

Task 2

A number of companies have created webpages on their company website for their employees. The website for the employees is the company website followed by "/employeeportal" .

• On the Company Management screen, expand the AdditionalDetails area on the Employees card and find the dynamic text component, Website
• This component is backed by the attribute, Website, which is currently empty
• On the Company Form screen, add an Actionflow to the Update Employee Website button that updates the Website attribute on the Employee table using a  Bulk Update action
• Every employee for the selected company should be updated
• The syntax for the employee website is CompanyWebsite/employeeportal, e.g. www.phixflow.com/employeeportal

.

.

Assignment 3

Difficulty Level: 

Task 1

We need a way to quickly create a number of companies where we have limited information about them, e.g. just their name.

• On the Company Management screen, click the Quick Add button to open the Company Quick Add screen
• On this screen, add an Actionflow to the Save button, using a  For Each action, that allows new companies to be added to the Companies table using just their name
• Users should be able to enter a list of company names, separated by a comma
• When a record for each company is created, a unique ID number should be generated
• Each company's Status should be set to "New" so that they populate the Company Approval Review screen

Task 2

Additional information about all employees has been made available. We need to make sure it is available across all applications and can be called by external systems as an API.

Set up an  API Endpoint that returns all the data from the table, EmployeesAdditionalInformation in JSON format. This table can be found in your application under  Tables in the Repository. 

On the Company Employee Extra Information screen, create a button that calls the API. The Response from URL can be seen in the  System Console.

Optional: If you wish, you can create a screen to display the results.

.

Task 3 

We need to call the API containing the additional information about employees to obtain their start dates.

On the Company Employee Extra Information screen, add an Actionflow to the Run button that displays Employees from the Employees Additional Information API you set up in Assignment 3, Task 2 above, with a start date between the two set parameters as shown in the drop down fields on the Company Employee Extra Information screen.

For this task, you can either create a new Actionflow or modify to the one you made in the task above.

Requirements:

• Your Actionflow must contain a  Loop and loop through each year parameter
• Set up a  JSON action on the API endpoint to receive the incoming parameters

Optional Task: For the purposes of this example we save the data to the table Employee Start Date Analysis but you can use the Employee ID to merge the Start Dates into the Employees table.

Testing

Ensure you test your Actionflows are working, and where relevant, test for both a positive and negative result. 

Once you have verified your Actionflows are working, the screens and data can be modified in any way you wish. For example, you may wish to add additional screens to process the Employees data and practice some of the techniques you have learnt using that data.