Step Two

When the user who initiated the flow fills out and submits the form, the flow is prompted to fall to the person in the "Proxy User" field selected on the form.

In order to use the value of a field on the form on the flow side, we must first access this field in the form on the flow screen. In such cases, the Variable object from the flow objects is used. The variable object is added to the flow screen and added to the properties of the Variable Screen;

• From the Source Document field, the Document object to which the form is connected to whichever form is desired to be accessed on the flow side,

• From the Source Object field, whichever of the objects on the selected form wants to keep its data in this variable, the form object must be selected.

We've kept the contact information in the variable object in the flow so that we can drop the flow side approval to the person selected in the Combobox object on the form. Now we need to assign this contact information to a confirmation position in the flow. For this operation, a Assignment object is placed after the "Send" action lever of the object that starts the flow, and a Position object is placed in the stream after the Assignment object.

With the assignment object, the contact information held in the Variable object will be assigned to the Position object. Accordingly, in the properties of the Assignment object;

• In the Target Object field, select which object in the stream to assign a value to. For our example, the object to select is the Position object that follows the assignment

• In the Resource Type field, the assignment type will be selected. According to the example, the **"User from Variable Value" option is selected in this field because the value held in the Variable object in the flow will be assigned to the Position object

info

In the value field of the ComboBox object on the form, "User from Variable Value" is selected because the User ID information is kept. If the user's Position ID was kept in this field, the "Position from Variable Value" option would be selected.

• In the Select Item field, the Variable object is selected whichever variable object in the stream will be used in the value assignment.

When the flow passes through the assignment object, the Position object will now be the user selected for proxy through the form. This proxy user will view the form filled out by the initiator of the flow, approve the transaction if appropriate during the permission dates, and if not, reject it and send the flow back to the initiator of the flow.

First, in order for the proxy user to see the completed form, the Document object to which the corresponding form is linked must be selected from the Document field in the object properties. The proxy user must not be able to make any edits to the form filled out by the initiator of the flow. That's why we don't give editing authority for this position when attaching documents.

According to the scenario, the proxy user should have "Confirm" and "Reject" action buttons. The events of a Position object positioned from the Toolbox to the flow screen by drag/drop are "Confirm" and "Reject" by default. If it had to have a different action depending on the scenario, this change would have been made from the "Events" field in the properties of the position object. We are not making any changes to this area because the events that come by default are in line with our scenario.

For all action descriptions attached to the position object, the object must be subtracted from the arrow for the corresponding action to indicate where the flow should be headed if the corresponding action occurs.

According to the scenario; If the proxy user approves the process by pressing the "Confirm" action button, the flow must be sent to the administrator of the initiator of the flow as the next step. Because the user who initiates the flow can be any user defined in the system, no fixed value can be assigned to the user administrator position. The Assignment object will also be used in this step to find the manager of whoever started the flow and assign them to the Manager position.

That is, after the position object "Proxy User" there must be an Assignment object that makes a manager assignment. The "Confirm" action arrow of the "Proxy User" position is also linked to this Assignment object.

Again, according to the scenario, if the "Proxy User" object rejects the process by pressing the "Deny" action button, the flow will be sent back to the user who started the flow. Therefore, the "Deny" action arrow extracted from the "Proxy User" object is bound to the Flow Initiator object.