Base Request: Setup a print template in

Sửa đổi trên: Thu, 21 Tháng 11, 2024 tại 4:47 CH

To set up a custom print template for company request group, follow the instructions below:
Step 1: Access https://request.base.vn >> select Customize (gear icon) and click on the request group that needs editing.

Step 2: Set up the print template according to your needs in a .docx Word file
- To get the information of the custom fields in the request form into the print file, you need to set it up in the print template using the syntax: ${custom field code}, for example: ${campaign_name}.
- To get the code of the custom field, go to the Request Form tab >> Hover over the custom field you need to get the code for >> Select the lightning bolt icon >> Copy the data field code.

Note: Specifically for table-type fields
Method 1: Get each cell in the table
For table-type data fields, use the variable syntax: ${inputkey-1-1}. Where:
+ inputkey: key of the custom field in table format
+ -1-1: The coordinates of the cell (row 1 column 1)
Similarly for other rows:
+ ${inputkey-2-1} Row 2 column 1
+ ${inputkey-3-1} Row 3, column 1

Method 2: Print table data automatically across multiple lines
For the table data field that needs to print multiple lines automatically, you use the variable:
${column.inputkey.column index}. For example: ${column.bang_hang_hoa.1}
- With column index = 0 => Automatically print the corresponding serial numbers for the rows of data in the table.
For example: In a table with 15 rows of data, the order numbers will automatically be assigned from 1 to 15.
- With column index= 1,2,3,... => Automatically print the values of the corresponding columns without needing to fill in variables in each cell of the table.

You can set variables according to the request template below:
* After creating the request , there will be a table of information and the request will be printed according to the template. The request will be displayed as follows:

Note:
- These variables must be in the table; otherwise, they will have no value.
- Each table can only be printed once on a print template.
- If the table is empty, it will print a row with blank data.
- In addition, the system also has default data field codes (provided below) for users to set up in the print template.
Step 5: After completing the data, select the Print tab in the settings page >> Add print template and choose the uploaded print template file.
Step 6: Return to the created request and print the request according to the template.
When printing is successfully completed, the system outputs a Word or PDF file depending on the user's choice.

** DEFAULT DATA FIELD CODES OF THE SYSTEM
Basic information
${id} : request code (id)
${name} : request name
${company} : Company name
${creator_name} : Name of the request creator
${creator_title} : Job position of the request creator
${creator_username} : Username of the request creator
${group_name} : request group name
${group_id} : Group request ID
${status} : request status (active, done, failed)
${created_at_date} : request creation date
${created_at_datetime} : request creation date and time
${created_at_year} : Year the request was created Value of the request creation year
${created_at_month} : Value of the request creation month
${created_at_day} : Value of the request creation day

Custom field
${inputkey} : Custom field with code inputkey
${bang_abc} : Custom table field with input key code bang_abc
${bang_abc-1-2} : Value of the cell in row 1 column 2 of the custom table field with input key code bang_abc
${bang_abc-3-5} : Value of the cell in row 3 column 5 of the custom table field with input key code bang_abc The value of the cell in row 3, column 5 of the custom table field with input key code bang_abc

The block of fixed approvers according to the request group's setup
${owner_group_name_1} : Name of the first approver according to the request group's setup
${owner_group_username_1} : Username of the first approver according to the request group's setup
${owner_group_title_1} : The job position of the first approver  according to the request group's setup
${owner_group_name_2} : Name of the second approver according to the request team's setup
${owner_group_username_2} : Username of the second approver according to the request group's setup
${owner_group_title_2} : The job position of the second approver according to the request group's setup

The approver in the approval flow set up by the request
${owner_request_name_1} : The name of the first approver in the approval flow set up for the request
${owner_request_username_1} : Username of the first approver in the configured approval workflow of the request
${owner_request_title_1} : Position of the first approver in the configured approval workflow of the request
${owner_request_name_2} : The name of the second approver in the request's setup approval flow
${owner_request_username_2} : Username of the second approver in the request 's setup approval flow
${owner_request_title_2} : Job title of the second approver in the request's setup approval flow
${owners_name} : List of names of approvers in the request's setup approval flow
${owners_username} : List of usernames of approvers in the request's setup approval flow
${owners_name_username_title} : List of names, usernames, and job titles of approvers in the request's setup approval flow
${owners_name_username_title_textarea} : List of names, usernames, and job titles of approvers in the request's setup approval flow on multiple lines

Approvers in the actual approval order of the request 

${approval_final_date} : Date of complete request approval
${approval_final_datetime} : Date and time of complete request approval
${approval_action} : request approval action
${approval_name_1} : The name of the first approver in the actual approval order of the request
${approval_username_1} : Username of the first approver in the actual approval order of the request
${approval_title_1} : Position of the first approver in the actual approval order of the request
${owner_request_action_1}: The actual approval status of the first person in the approval order (approved, rejected, in process)
${approval_datetime_1} : Date and time of approval by the first approver in the actual approval order of the request
${approval_note_1} : Approval note of the first approver in the actual approval order of the request
${approval_note_textarea_1} : Approval note of the first approver in the actual approval order of the request over multiple lines
${approvals_name} : List of approvers' names in the actual approval order of the request
${approvals_name_datetime} : List of approvers' names and approval dates in the actual approval order of the request
${approvals_name_username_title_datetime} : List of approvers' names, usernames, job titles, and approval dates in the actual approval order of the request
${approvals_name_username_title_datetime_note} : List of approver names, usernames, job titles, approval dates and times, and approval notes in the actual approval order of the request
${approvals_name_username_title_datetime_note_textarea} : List of approvers' names, usernames, job positions, approval dates and times, and notes upon approval in the actual approval order of the request on multiple lines

Approvers in the actual approval order of each block of approvers
${block_approvals_block key_name} : List of names
${block_approvals_block key_username} : List of usernames
${block_approvals_block key_title} : List of job titles
${block_approvals_block key_date}: Approval date list
${block_approvals_block key_datetime}: Approval date and time list
${block_approvals_block key_note}: Approval note list
${block_approvals_block key_name_username_title_datetime} : List of approver names, usernames, job titles, and approval dates and times in the actual approval order of the request
${key_name_username_title_datetime_note} : List of approver names, usernames, job positions, approval notes, and approval dates and times in the actual approval order of the request . ${block_approvals_block key_name_username_title_datetime_note_textarea} : List of approver names, usernames, job titles, approval notes, and approval dates and times in the actual approval order of the request . Each set of information for one person is one line.

 
Final approver:
${approval_final_name} : approver's name

${approval_final_username}: username of the approver 

${approval_final_title}: the approver's position 

${approval_final_date}: the approval date of the approver 

${approval_final_datetime}: the time (hour + day) of the approver

${approval_final_note}: the content of the approver's comments without line breaks
${approval_final_note_textarea} : content of the approver's comments kept on a new line

Reject the request
${rejection_name} : Name of the person rejecting the request
${rejection_username} : Username of the person rejecting the request
${rejection_title} : Job position of the person rejecting the request
${rejection_date} : Rejection date Date of request rejection
${rejection_datetime} : Date and time of request rejection
${rejection_note} : Note when rejecting the request
${rejection_note_textarea} : Note when rejecting a request over multiple lines
${rejection_name_username_title_datetime} : Name, username, job title, and the date and time of the rejection by the person rejecting the request
${rejection_name_username_title_datetime_note} : Name, username, job position, date and time, and notes when the request was rejected by the person rejecting the request

* Special notes
01. Variables with a list will be able to list each value in order (for example, ${approval_note_1}, ${owner_request_title_2}). Ordered list-type variables will be extracted to the required number of variables with actual values. If a variable is filled in the template file but does not have an actual value, it will be displayed as empty (supporting up to order 20).

02. Custom fields of type int, float will have a dot separator.
03. Custom file type fields will display the file name.
04. Custom field variables of the textarea type will display with line breaks.
05. Based on the variable naming rules, customers can suggest additional variables that accurately represent the extracted values or how they are displayed. For example, ${owners_name_username_title_textarea}: A list of names, usernames, and job positions of the approvers in the approval flow set up for the request , displayed on multiple lines.

Câu trả lời này có giúp ích cho bạn không? Yes No