With Kuika, you can create process automations in the web and mobile applications you develop and present them to the end user. In this learning content, we will examine the steps of creating process automation through a sample scenario.

In our sample scenario, we will use the “I Have an Idea!” web application that we developed in Kuika Academy courses. In this application, we will create a process where the ideas shared are first submitted to the team manager and then to the human resources manager for approval.

As a first step in the process, the shared idea goes to the team manager for approval. If the team manager approves the idea, it is submitted to the human resources department for approval. If the team manager does not approve the idea, the idea is rejected and the user who created the idea is notified via an e-mail.

In the second stage, if the human resources department approves the idea, the idea is saved and a notification email is sent to the user. If HR does not approve, the idea is again rejected and the user who created the idea is notified by e-mail.

Let's prepare the process automation in line with this example scenario.

1. I Have an Idea! Open the web application.
2. Open the Process Automation module.
3. Create a new Process.

First, let's start creating the parameters of the process through the Process Parameters module.

4. Open the Process Parameters panel.

Let's start with the parameters we will use in forms.

5. Under Business Object, create a String type parameter named Idea Title which is an input for the process.
6. Follow a similar process and define IdeaDescription of String type and IdeaDate of DateTimeOffSet type.
7. In addition, define ManagerDescription and HRDescription in string type and IdeaNo Business Object parameters in Guid type so that they do not carry the Input attribute.
8. Then create ManagerApproval and HRApproval parameters of Boolean type under Internal.

Let's create the buttons that will provide interactions in the process.

9. Create a new button via Buttons Panel.
10. Name it Approve and update the Label text to Approve.
11. Create another button.
12. Name it Reject and update the Label to Reject.
13. Update its color.

These buttons can be used in all Processes in the application you have developed.

Now let's continue with the process.

14. Select Lane. Expand it.
15. With Lane selected, select Role under Assignment heading in the Properties Panel.
16. Then select the Manager Role.
17. Reposition the User Task in the Canvas. This User Task will correspond to the first task in the process, manager approval.
18. After the User Task repositioning, update the User Task content.
19. Define a Step Description via the Properties panel of the User Task. While defining the description, you can also define parameters if needed.
20. At this point, you can provide a definition such as “New idea approval task opened by @processInitiator”.
21. Then, under the Step Outputs heading, it is necessary to select the outputs of the task. Within the scope of this application, it is necessary to select the ManagerApproval parameters corresponding to the manager approval and ManagerDescription parameters corresponding to the manager's description.
22. Then click on the Manage Step Interactions icon next to User Interactions.
23. Click the Add New User Interaction button on the screen that opens.
24. Define a User Interaction named ManagerApprove in the example.
25. Click Select Parameter to Map and select ManagerApproval.
26. Select button in the added table.
27. Activate the Switch in the table added to the screen.
28. Then add a new User Interaction and name it as ManagerReject.
29. Click Select Parameter to Map and select ManagerApproval.
30. Select the button in the added table.
31. Click the Update button.

With these operations, you have added User Interactions that will be automatically added to the form screens that you can create automatically for Process Automation.

32. Add and position a control tool to check the administrator approval status.
33. Add and position a system task to send an e-mail notification to the user in case of a non-approval scenario after administrator check status.
34. With the system task selected, add the Send Mail action through the Properties panel and define the parameters in the Custom option.

An important point here is the selection of the personnel who will start the process in the Receivers section.

35. In the Receivers field, select Process Parameters>Common>Process Initiator via Symbol Picker.

This will automatically define the information of the person who shares the idea that initiates the process.

36. Now add another Lane to the flow.

Through this Lane we will be managing the flow of ideas approved by the Manager on the human resources side.

37. Select the Lane you added.
38. In the Properties Panel, select Role under the Assignment heading.
39. Then create a new role called HR.
40. Add a User Task to the Lane you added and name it.
41. Then use the connection tool to connect the control tool you added for the admin control state and the User Task you just added.
42. Name the control tool's connections Yes and No.
43. Then select the control tool and make sure that No is selected in the Will Execute Otherwise parameter in the Properties panel.
44. In the “Yes” If field, add Filter and click Symbol Picker in the modal that opens.
45. Select Process Parameters>Internal>ManagerApproval.
46. Select Is Equal to and activate the Switch.

With this process, when the manager's approval is realized, the flow will be switched to the human resources Lane.

47. It is necessary to select the outputs of the task under the Step Outputs heading in the Properties panel of the User Task you added for HR approval. Within the scope of this application, there is a need to select the parameters HRApproval corresponding to human resources approval and HRDescription corresponding to human resources description.
48. Click on the Manage Step Interactions icon next to User Interactions.
49. Click the Add New User Interaction button on the screen that opens.
50. Define a User Interaction named HRApprove for the example application.
51. Click Select Parameter to Map and select HRApproval.
52. Select the button in the added table.
53. Activate the Switch in the table added to the screen.
54. Then add a new User Interaction and name it as HRReject.
55. Click Select Parameter to Map and select HRApproval.
56. Select the button in the added table.
57. Click the Update button.
58. For the User Task in the second Lane, add a control tool that allows to check the approval status
59. For the scenario where the control status is not confirmed, draw a link to the Rejection Notification system task in the first Lane.
60. For the approved scenario, add and name a new User Task.
61. Draw a link from the control tool to the newly added User Task.
62. Name the links of the control tool as Yes and No.
63. Then select the control tool and make sure that No is selected in the Will Execute Otherwise parameter in the Properties panel.
64. Then add Filter in Will Execute “Yes” If field and click Symbol Picker in the modal that opens.
65. Select Process Parameters>Internal>HRApproval.
66. Select Is Equal to and activate the Switch.
67. Select User Task next to the Control tool.

This User Task will enable HR to process the ideas into the system after the approval of human resources.

68. Under the Step Outputs heading in the Properties panel of the User Task, it is necessary to select the outputs of the task. Select IdeaNo in this field.
69. Add a system task after this task and provide its connections.
70. Name the added system task.
71. Add Send Mail action to the task.
72. In the Receivers field, select Process Parameters>Common>Process Initiator via Symbol Picker.
73. Define the other parameters as well.
74. Finally, add and name an End Event to terminate the flow.

With these operations, we have prepared a sample flow together.