This morning we had a partner meeting and Chris asked me to share our solution in here. I hope it’s an inspiration.
2 questions to follow up on:
- @Chr1sG If you see something that could be set up more easily I’d love to hear about it.
- In this video I’ll show you one of many possible use cases why it can be a great advantage to trigger an automation based on one of the possible linked entities.
In this video you can see what I’m talking about further on.
A brief explanation to start with. We have set up a scheduling system where we work with 2 different ways of scheduling → Planning & deadline.
Planning: A task should be done within a certain period of time. Sometime in this week, next week, this month or next month.
Deadline: A task must be done at a fixed deadline.
In the database Planning period we have the 4 entities, as described above at planning.
- Those different planning options have (amongst others) a startdate, enddate, duration, month, quarter and year.
- Every single week / month the startdate and enddate is updated. This will update the duration (via formula).
- And when duration is updated, month, quarter and year is also updated.
When some sort of planning information is manually being updated, we automatically set all the other information logically known.
For example. When the quarter is Q3 - 2023, we know the year should be 2023. But we don’t know which specific month or deadline it should be. But when we update the deadline, we know the month, quarter, year etc.
The only issue is that we have more databases than just tasks that needs to behave exactly the same as tasks (talking about planning). We also have development tasks, content, personal development, etc.
In order to behave the same they should all have the same automations as we have inside the Task database.
But what would happen if it would be possible to have the automation trigger When entity linked to beingd triggered not by one fixed option, but by on of the mentioned options? Like it is possible when an entity is updated.
When I do a quick calculation for this specific use case it would save us probably 16 automations.
4 automations in 5 database can be to converted to 1 automation in 4 database.
Maybe you know an even better solution for what we have build here. But I’m convinced it’s extremely usefull to have the possibility to have more options when linked to an entity.
Let me know what you think of it.