Invoke Form - Template Path
- Last UpdatedJul 01, 2024
- 3 minute read
Standard Template
If you are using the template in general, then you can use the generic template which is placed in the physical path across the workflow.
The standard template is available in [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\WorkflowElements\Default\en-US\Templates\FormEmailTemplate\ folder.
The standard template 'InvokeFormEmail.html' is shown in the figure below:
The text enclosed within @@ are taken from Locales folder [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Locales\en-US and you can customize these text. These are marked in the figure below.
To customize text within '@@', follow the steps given below:
-
Go to the following path [AVEVA Work Tasks Installed Path]\AVEVA\Work Tasks\Locales\en-US
-
Open the required file and customize the required text.
Customizing Template
If you want to specify the template for different activities then you can create different templates for different activities. You can store the created templates wherever engine is running. Example: You can create a manger template for manager, Employee template for employee, leave application template for all employees and salary template etc.
Note: In an Enterprise Server scenario, if there are two servers running, then the template path will be considered for which engine has got the request.
To create a new template, there are two ways:
First Option:
Create a HTML file and place it in any place wherever the engine is running. Enter the entire path in the Template Path property.
Note: Make sure that, while creating a template, you should use the marked text in the template in order to get the Work Items from AVEVA Work Tasks.
Second Option:
Take a copy of 'InvokeFormEmail.html' and place it in any physical path and customize the text however you want.
The following table depicts the Placeholder which you can customize in your template:
|
Placeholder |
Description |
Example |
|---|---|---|
|
<%#ActorName%> |
Name of the user to whom the email has to be sent, using the template. |
Sam |
|
<%#Submitedby%> |
Name of the user who submitted the workflow |
John |
|
<%#Body%> |
The content specified in the Body property will be reflected. |
Please fill a form below to process your tax declaration. |
|
<%#TaskName%> |
Activity name |
Leave Application Form |
|
<%#Description%> |
Activity description |
Detailed leave information of the employee |
|
<%#SubmitedDate%> |
Date when workflow was submitted |
12/10/2008 |
|
<%#SubmitedTime%> |
Time when workflow was submitted |
04:00:24 |
|
<%#LocalUrl%> |
Enterprise Console local URL to send form link as an email. |
http://localhost:8000/enterpriseconsole/BPMUITemplates/Default/Email/ |
|
<%#IntranetUrl%> |
Enterprise Console Intranet URL to send form link as an email. |
http://machinename:8000/enterpriseconsole/BPMUITemplates/Default/Email/ |
|
<%#InternetUrl%> |
Enterprise Console Internet URL to send form link as an email. |
http://www.skelta.com/enterpriseconsole/BPMUITemplates/Default/Email/ |
|
<%#ApplicationPath%> |
Enterprise Console path will be considered from SKAddInProviderSettings table for the respective repository. If you are not getting the mail from SMTP exchange server , you need to do some manual entry in the SKAddInProviderSettings table. In the Settings column of the SKAddInProviderSettings table, change the entry 'http://[ApplicationPath]/BPMUITemplates/Default/Email/' to your local machine name/IP address with port. Example: Change ApplicationPath to EnterpriseConsole url In the Application column of the SKAddInProviderSettings table, change the entry 'Default' to repository name. Example: Change Application to EmployeeRepo |
http://skeltanb24:8000/enterpriseconsole/BPMUITemplates/Default/Email/ |
|
<%#QueryString%> |
The query string which contains the Work Item information in encrypted format. |
mcuri=uSR0tBXvLACdY2J-e1EPXjPewxFYxLx6G5Rg2zPgzpr8EYiyP63v6QSY0jdq26OnLOrwfy8iDwUhUUCdeEsOzKWgI4D7MF_9Y-LWRlb05T0pfbBP12oTqK0hRvyZsnCBxDeX190sSTkyt2mGY3nCDzCkVPrLMu82msEhQdm_g8HeO5SY_fWhiWgGDKjPai0O |
|
<%#DocViewQueryString%> |
Document View page details |
Emaildocview.aspx?mailviewuri=nLOVXOa2m4x43xcG4kWt0Zi7gsePioiAfQsnck92w-Fr-uMXWj5scuZy-xVNkzCQhOKoFPTpRGuRQobt4kbSlJD4TXQXi6e9mDkPXOrR5UGBQiGOq88IvRJqleRkwK5PXKgWPIbdLChdMYl1Xl5IIebMMjeVsHi4KXFuiw9Maa1vp2805TjpiBAbODvy1dO6NX8oBEaoiKu1XiHUKX1Lwpd2nkCb26C_jEpvKDBKAwHvqpHWZViDFoDlKmUa8YvgHfrm3Xf-xAWy02z5IJ4WvPUe6kgQoFwLDleRfF-W6hw! |
|
<%#ExecutionViewQueryString%> |
Process Execution page details |
EmaiExecutionView.aspx?mailviewuri=nLOVXOa2m4x43xcG4kWt0Zi7gsePioiAfQsnck92w-Fr-uMXWj5scuZy-xVNkzCQhOKoFPTpRGuRQobt4kbSlJD4TXQXi6e9mDkPXOrR5UGBQiGOq88IvRJqleRkwK5PXKgWPIbdLChdMYl1Xl5IIebMMjeVsHi4KXFuiw9Maa1vp2805TjpiBAbODvy1dO6ROMtM-aBMo5QlRzS6Ad9MrGhjuLxkHy4ebMtncEUuH3zXPnGUpSzT-qRBduN4iOWF53PJF1MHI_nIyLmNBJloxMz5RqzgDfKM8BLur3QOwtc3lUZBT0M-JKH-EYpbAfgDHUq9uhDWhBbBhMsxYN09M30_NyJmL20HiBVbDQrxwHQrZrxBLpQRlJKSymutzHM |
|
For configuring workflow variables |
Using Variables in Invoke Form Activity |
|
|
For configuring workflow contents |
Using Contents in Invoke Form Activity |
|
|
For configuring workflow Xml variables |
Using XML Variables in Invoke Form Activity |