Member-only story
Tracking careers in
Using a time stamp in a table to identify a time related position
The creation of the logic shown in this blog is the result of a double exercise. I am building a serie of related docs that once launches the 2WS without shared permissions on both sides (stage 4) we can use together. In this scenario the HR team creates a doc with employees of your team you have access to. You can add information and this new information is shared with the HR team. You don’t have access to the main HR doc that contains all information about all teams, you only access the doc relevant for your team. We are not there yet.
The other and more direct motivation was that I got asked to develop a permission logic. Team leaders and managers have to sign off on proposals, budgets, you name it.
The signing off is not the issue. We have buttons to handle that and on top they can relate to a specific user, thus only become active for a specific user. Here is the thing, You don’t want to set manually who is responsible for what once an employee asks for permission. You want to use a filter to bring in the relevant person (team leader or manager).
This is very well possible when we apply a BOM logic that gives as back the most recent value when we use today or any other date related value. In this context we…