step-four

Step # Four

In this step, the flow must be reduced to all users in the Human Resources Department after manager approval. We connected the Manager object's "Confirm" action arrow to the Position Group object placed in the flow in the previous step.

The Position Group object added to the flow needs to be selected from the Human Resources Department in the system. This requires the selection of which contacts will be included in the group object from the "Group Contents" field in the properties of the group object. In the Group content section,

• The Group Type field selects which type of user to assign to the group. In this field, the "Position Groups" option is selected because the assignment of bulk users in the business unit, not individual users or positions, will be made.

• In the Content Type field, the choice of which data to fill in the group content should be made. Since we want to add the people in that department to the group with the definition of department, we select "User Group by Department" from this field.

• After these selections, a structure will appear at the bottom of the screen that lists all the titles and departments defined in the system. Select "Human Resources Department" from the department list and press the OK button.

People in the group object will see the form that the initiator of the flow filled out and enter a record that the person will be on leave on that date. Therefore, from the Docs field of the group object, the form document filled out by the initiator of the flow is selected.

The action that the group object takes in the flow is to send the flow to the next step by pressing the "Confirm" button after 1 of the users in the group has taken action. The events for a position group object added to the flow screen are "Approve" and "Reject" by default. In our scenario, because the group object will not have a Reject action, we remove the Reject event from the object, which comes by default.

There is another action to be taken with the events of the group object. Depending on the scenario, it should be enough for 1 person from the group to press the "Confirm" action button for the flow to proceed. For example; Let's say there are 5 people in the Human Resources Department. When the flow falls into the position group, an action request will be sent to these 5 people. In order for the flow to proceed, all 5 people in the group must press the "Confirm" button by default.

To change this status to Let the flow proceed with the approval of 1 person in the group, the event definition that is intended to work this way must select "Number" in the Condition section and "1" in the Condition Value section.

When a user from the HR department advances the flow with the "Confirm" action button, an information mail will be sent to the initiator of the flow as the next step. Therefore, an Informational object is placed in the flow after the position group object, and the "Confirm" action arrow of the position group is connected to this Informational object.