If permitted, element fields or parameter can be displayed in the same manner as in the form Value insert. But, if printable form is unavailable, request printable display
from any value
Example: {=Variable:Datetime > date, printable} // converting to printable format
(variable, additional result and etc.).
In addition to 'printable' you can use the modifier (text) to convert into text the fields with content not intended for print. Example of such field is Phone in CRM entity. Record format: {{Phone (text)}}.
Example of modifying the Phone field to print a comment in Contact details
Use the action Add comment in the Contact workflow in CRM.
Select Phone field using Insert Value form for printing in comment.
Check the result. Run the workflow for contact and see the Array entry in comment:
This occurred due to the field is not intended for print. Modify it by adding (text):
The result is the number in comment is printed correctly:
Converting data types
In addition to the above, you can convert not only into the print form, but also changing the data type:
{=Variable:string>date} // преобразование строки в дату
Find all the options for such conversion in data type conversion table.
friendly
User data type can be converted into friendly format. In this case, prints only user first and last name, without ID and login.
Example: {=Document:CREATED_BY} > User_1
{=Document:CREATED_BY > printable} > John Smith [1]
{=Document:CREATED_BY > friendly} > John Smith
Important! Variables and PHP code actions can be used for data type conversion, including print form query for values without printable form (for module version earlier than 15.6.0).
Note: using Value insert form is optional for inserting the same value into different template actions. It's sufficient to copy the text, inserted via the this form and use it.
Data type conversion table
Start/end
bool (Yes/No)
date
datetime (Date/Time)
double (Number)
int (Integer)
file (File)
select (List)
string (String)
text (Text)
user (User)
bool (Yes/No)
---
x
x
1 or 0
1 or 0
х
х
Y or N
Y or N
x
date
x
---
as per format
timeslamp
timeslamp
x
x
as per format
as per format
x
datetime (Date/Time)
x
as per format
---
timeslamp
timeslamp
x
x
as per format
по формату
x
double (Number)
0==N
!0==Y
from timeslamp
from timeslamp
---
(int)
x
x
(string)
(string)
user_<ID>
int (Integer)
0==N
!0==Y
from timeslamp
from timeslamp
(float)
---
x
x
(string)
(string)
user_<ID>
file
x
x
x
x
x
---
x
x
x
x
select (List)
Y or N
x
x
(float)
(int)
x
---
(string)
(string)
user_<ID>
group_<CODE>
<ID>
string
Y or N
strtotime
strtotime
(float)
(int)
x
x
---
(string)
user_<ID>
group_<CODE>
<ID>
text (Текст)
Y or N
strtotime
strtotime
(float)
(int)
x
x
(string)
---
user_<ID>
group_<CODE>
<ID>
user
x
x
x
ID
ID
x
x
(string)
(string)
---
Note: all expressions in text are automatically converted into string, if no additional IDs present.
Note: converting List into String or Text sources list values. When converting List into List - corresponding list keys. To get list key values, use converting: for example: {=Variable:Select > select}.
Examples of specific issue resolution (for Bitrix24 On-premise)
For example, additional field was created for a document; however it's not showing in the Insert Value form. In this case, go to iblock settings in admin site section (Content > Information Blocks > Information block types > [required_iblock], Property tab), and uncheck Include property in filter on element list page: option in this field parameters.
This property will be unavailable in workflows if this option is enabled.
