Approvals will apply to a whole row.
Hereโs how the thing can be brought to fruition:
-
Add an approval column in the โattendance entryโ sheet, with type Yes/No. The initial value of it should be โNoโ.
-
Add a virtual column in the attendance table, which is the concatenation of all the pertinent columns, that a manager needs to see to uniquely โidentifyโ each entry. Letโs call this Att_Vir.
-
Make another approval sheet for the managers, with appropriate fields like โAttendance to approveโ, โuserโ, etc. You will better know which columns to use.
-
In the โattendance to approveโ column, use a valid_if using โSelectโ expression, that shows the Att_Vir columns in the drop-down (the type would be enum-list). Proper filtering criteria have to be used, to show entries that are unapproved (based on that Approval column) and under the liability of that manager (probably when the user enters his name in the attendance sheet, then the associated managerโs name will come up using dereference).
- Actions: Here you need two actions a) one for the โattendance entryโ table
and b) For the approval table.
The attendance entry table action will mark the โApprovedโ column to YES, and probably some other columns if you want to store some details. The approval table action will use the โattendance entryโ table action as a reference, with proper expressions guiding it to which rows to act on.
- The approval table action has to be attached to the form, so that the action takes place when the form is saved, as opposed to getting to the detail view of every approval entry and pressing the action button.
Get these in place, and I will guide you on what expressions to use.
LinkedIn
Twitter
