Variables in task templates: Difference between revisions

From Planfix
Jump to: navigation, search
No edit summary
No edit summary
 
(32 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{#seo:
|title=Variables in task templates
|titlemode=append
|keywords=planfix, variables, templates, tasks
|description=Variables in task templates
}}
You can use '''variables''' in the names and descriptions of [[tasks]]. A variable takes the form of a field from a task or other object, contained in double curly brackets.  
You can use '''variables''' in the names and descriptions of [[tasks]]. A variable takes the form of a field from a task or other object, contained in double curly brackets.  


Example: the variable that stores the current date:
Example: the variable that stores the current date:
   
   
<pre>{{System.Today}}</pre>


'''{{System.Today}}'''
Variables are added to [[objects]] and [[task templates]] when creating or editing templates. When you create a task using a template, each variable's value at the time the task is created will be used in place of the variable.
 
==Adding variables==
In the interface for creating a template, there is a special icon. Click on it to display a list of available variables:
Variables are added to task templates when creating or editing templates. When you create a task using a template, each variable's value at the time the task is created will be used in place of the variable.
 
==Adding variables to task templates==
In the interface for creating a template, there's a link above the task name that leads to a list of available variables:
 
https://pic.planfix.ru/pf/kp/SkG6vn.png


https://s.pfx.so/pf/qu/dm8MCr.jpg
===Among the variables available are===
===Among the variables available are===
*about 30 system variables that let you display time, date, day of the week, month, and year, in various formats;
*about 30 system variables that let you display time, date, day of the week, month, and year, in various formats;
*all variables having to do with the tasks, including variables for each custom field;
*all variables having to do with the tasks, including variables for each [[Custom fields | custom field]];
*variables for each field of any directory that is used in task fields;
*variables for each field of any [[Directories | directory]] that is used in [[Directory entry | task fields]];
*all variables having to do with the project each task is created in, including custom project fields;
*all variables having to do with the [[Projects | project]] each task is created in, including [[custom project fields]];
*all variables having to do with task counterparties, including any data from client cards;
*all variables having to do with task [[Counterparty | counterparties]], including any data from client cards;
*all variables having to do with the parent task of the current task, including data from its counterparty or directories used in it.
*all variables having to do with the parent task of the current task, including data from its counterparty or directories used in it.
   
   
When you create a task using a template, each variable's value at the time the task is created will be used in place of the variable.
==Examples of using variables==
Variables can be used for:
*'''numbering incoming requests''':


When you create a task using a template, each variable's value at the time the task is created will be used in place of the variable.
https://s.pfx.so/pf/HK/I3Nenv.jpg


==Examples of using variables==
Variables can be used to number incoming requests:
<screenshot>
And for getting requests with numbers in their name, regardless of how they were created:
And for getting requests with numbers in their name, regardless of how they were created:
https://s.pfx.so/pf/59/sAJe4n.jpg
*'''For distinguishing between typical tasks in various projects'''
Using a custom '''Project code''' field:
https://s.pfx.so/pf/O1/DWbTe3.jpg
Getting tasks with project code in names:
https://s.pfx.so/pf/1s/lRGIxp.jpg
   
   
<screenshot>
*'''For naming [[Recurring tasks|recurring tasks]]:'''
 
For distinguishing between typical tasks in various projects:
https://s.pfx.so/pf/Wv/VKrOwc.jpg
Using a custom project reference name field:
 
Get intuitive names for recurring tasks:
<screenshot>
 
https://s.pfx.so/pf/gM/W7SPUG.jpg
Getting tasks with project reference names:
 
==Please note==
<screenshot>
*Variables are replaced with specific values one time when a task is created from a template.
*If a task made based on a template is created as a [[Draft]], the variables in the task will be replaced with values when the task is switched to working [[Task statuses | status]].
For naming periodic tasks:
*You can [[Formatting_dates|format dates]] in variables.
*Variables in tasks are available only in paid and premium accounts.
<screenshot>
 
== Additional information ==
for setting intuitive names for periodic tasks:
*[[Variables in Text|Using variables in text]]
<screenshot>
Please note:
Variables are replaced with specific values one time when a task is created from a template.
If a task made based on a template is created as a Draft, the variables in the task will be replaced with values when the task is switched to working status.
Variables in tasks are available only in paid and premium accounts.




Line 64: Line 66:
*[[Task templates]]
*[[Task templates]]
*[[Tasks]]
*[[Tasks]]
*[[Feature Description]]

Latest revision as of 13:11, 11 December 2024

You can use variables in the names and descriptions of tasks. A variable takes the form of a field from a task or other object, contained in double curly brackets.

Example: the variable that stores the current date:

{{System.Today}}

Variables are added to objects and task templates when creating or editing templates. When you create a task using a template, each variable's value at the time the task is created will be used in place of the variable.

Adding variables

In the interface for creating a template, there is a special icon. Click on it to display a list of available variables:

dm8MCr.jpg

Among the variables available are

  • about 30 system variables that let you display time, date, day of the week, month, and year, in various formats;
  • all variables having to do with the tasks, including variables for each custom field;
  • variables for each field of any directory that is used in task fields;
  • all variables having to do with the project each task is created in, including custom project fields;
  • all variables having to do with task counterparties, including any data from client cards;
  • all variables having to do with the parent task of the current task, including data from its counterparty or directories used in it.

When you create a task using a template, each variable's value at the time the task is created will be used in place of the variable.

Examples of using variables

Variables can be used for:

  • numbering incoming requests:

I3Nenv.jpg

And for getting requests with numbers in their name, regardless of how they were created:

sAJe4n.jpg

  • For distinguishing between typical tasks in various projects

Using a custom Project code field:

DWbTe3.jpg

Getting tasks with project code in names:

lRGIxp.jpg

VKrOwc.jpg

Get intuitive names for recurring tasks:

W7SPUG.jpg

Please note

  • Variables are replaced with specific values one time when a task is created from a template.
  • If a task made based on a template is created as a Draft, the variables in the task will be replaced with values when the task is switched to working status.
  • You can format dates in variables.
  • Variables in tasks are available only in paid and premium accounts.

Additional information


Go To