Client Custom Fields as Placeholders In Task & Projects
T
Tanya Bartholomew
Being able to add Client Custom Fields as dynamic placeholders from a drop-down list in Tasks would be a game-changer for things like:
- Naming conventions
- Less customising of project templates at a client level, so staff know if a task needs to be completed within a project - e.g. when completing month-end. Does the client have payroll? The Client Custom Field would be Yes/No. If "Yes", they complete the subtasks. If "No", they tick the task and move on to the next task
- Adding client-specific URL links to open specific web pages or reports directly from the task, e.g. Xero Payroll Report
Log In
T
Tanya Bartholomew
Some examples of how placeholders can be used, so you don't have to customise each client's templates.
These are just 2 of many, many ways placeholders can be used in work templates to save on admin (I use this feature so often in my old WFMS) - One master template for tasks that have common requirements.
Then, client-specific details can be added at the client level within a project.
The Custom Client Fields are already being stored. These now need to be utilised within the system rather than just read-only data on the client's file.
Kasey Cunningham Amanda Aparicio
Photo Viewer
View photos in a modal
K
Kasey Cunningham
Amanda Aparicio - Do you know if we plan on adding this in the future?