# 18 Other vtenext Settings # 18 Other vtenext Settings You can define further settings within vtenext: - **Template email** - **Webforms** - **Webform with GDPR fields** - **Customer Portal** - **How to enable the Customer portal** - **Customer Portal interface** - **GDPR module settings** - **Account Details** - **Server SoftPhone Settings** - **Requirements and configurations** - **LDAP** - **Currencies** - **Taxes Calculation** - **Proxy Server** # 18.1 Template email As for the newsletter module, the admin user will be able to access to the email template editor. An email template can be used for messages or for newsletter and can be saved in a public or private folder. Within the template the variables can be added. # 18.2 Webforms Through the vtenext Webforms tool, you can create a web form to be inserted within your site, for example the classic "contact us" form. The data entered in the webform will be automatically sent to the CRM in the Leads modules. To create a new webform, from Settings > Webforms, click on the button [](https://usermanual.vtenext.com/uploads/images/gallery/2020-05-May/create_button.png) [![18.2 [1].png](https://usermanual.vtenext.com/uploads/images/gallery/2022-06/scaled-1680-/4tp18-2-1.png)](https://usermanual.vtenext.com/uploads/images/gallery/2022-06/4tp18-2-1.png) - Assigned to --> vtenext user that will manage the lead - Return URL --> By clicking on the confirm of the webform, the user will be redirected to the address here indicated Once you have created the form by selecting all the desired fields and determining which ones are mandatory, you can click on VIEW FORM at the top right to access a window that reveals the HTML code to copy and paste onto the desired website page (or landing page). This HTML code is not formatted and will need to be managed with CSS files by your webmaster. **ATTENTION:** Any changes made to the web form fields in the CRM require that the HTML code be re-uploaded to the site. **HOW TO RECEIVE NOTIFICATIONS UPON RECEIVING NEW LEADS.** During the form creation process, it is necessary to choose the LEAD SOURCE field and determine the desired default source (e.g., WebSite). This field should be set as hidden. This way, you can create a filter in the lead module that filters leads coming from the WebSite source and set up the notification bell on that filter. At this point, every time someone fills out the form on the site, a new lead will be automatically created and the CRM will notify you with a notification. # 18.2.1 Webform with GDPR fields GDPR fields have been enabled inside the webforms from version 18.12 onwards. For example, you can request Marketing Consent, Third-Party Consent, Profiling Consent, etc., and save the choice made with IP and date-time in the lead data sheet. **Here are the configuration details:** The GDPR fields are grouped in blocks of three (view, date-time, IP). It is therefore necessary to set the information view fields as mandatory, to display the field in the webform as a picklist (YES/NO) and then force the user to make a choice. The date and IP fields must be hidden fields (so set the hidden flag to yes in the webform configuration). The following must be entered as default value in the date field: **“$(general : (\_\_VteMeta\_\_) date\_Y\_m\_d) $(general : (\_\_VteMeta\_\_) time”** The following must be entered as default value in the IP field **“$(general : (\_\_VteMeta\_\_) clientip”.** By doing so, the setting of the consent + date-time and IP of the request is obtained in the GDPR block. [![18.2.1 [1].PNG](https://usermanual.vtenext.com/uploads/images/gallery/2022-06/scaled-1680-/RBt18-2-1-1.PNG)](https://usermanual.vtenext.com/uploads/images/gallery/2022-06/RBt18-2-1-1.PNG)
**Assigned to** | Lead Recipient |
**Return Url** | When the webform confirmation button is pressed, the user will be redirected to the address indicated here (for example, the thank you page) |
**Owner** | You can select the CRM user to whom all records created from the portal will be directly assigned; |
**Notifications** | It offers the possibility to select email templates, which can be customized through creation or modification using the dedicated EMAIL TEMPLATE section in SETTINGS, for exchanging information with the portal user. The options are: - Template used for the portal registration email; - Template used for the successful password change email; - Template used for the password recovery email; - Template used to notify the customer about the creation of a ticket; - Template used to notify the customer about the ticket response; |
**Home** | It allows configuring buttons for quick actions on the portal home page. By clicking on ADD BUTTON on the right, you can enable a window from which to set: - Button Title - Button Description - Button color - Icon representing the button's function - Action that allows choosing to link a module or trigger the creation of a record in a specific module [](https://usermanual.vtenext.com/uploads/images/gallery/2023-08/image-1692883982340.png) *Button Creation Screen* [](https://usermanual.vtenext.com/uploads/images/gallery/2023-08/image-1692884400981.png) *Button List Viewing Screen* **The order of the buttons can be changed through drag-and-drop.** |
**Conditionals** | It is possible to set up conditional fields for the Customer Portal, so that they work exactly like in the vte interface. When they are activated, the conditions will function properly on the portal as well. There are three ways to configure them: - **Import from another portal profile** - **Import from roles and groups** - **Create a new rule directly on the portal (Add button)** [](https://usermanual.vtenext.com/uploads/images/gallery/2024-10/bOaimage.png) [](https://usermanual.vtenext.com/uploads/images/gallery/2024-10/1rXimage.png) By clicking on **Import from another portal profile**, a popup will open, allowing you to select other existing profiles. Once you've selected the desired profile, you can click **Import** at the bottom right of the window to complete the process. [](https://usermanual.vtenext.com/uploads/images/gallery/2024-10/A5Zimage.png) By clicking on **Import from roles and groups**, a popup will open, allowing you to select predefined rules for the CRM directly in the Conditional Fields section. For more details on this topic, refer to *Chapter 17.4 Conditional Fields*. [](https://usermanual.vtenext.com/uploads/images/gallery/2024-10/kV4image.png) By clicking on **Add**, you can create a new rule for the portal's conditional fields, exclusive to the portal itself (it will not reflect in the CRM). The configuration follows the standard process explained in Chapter 17.4. In the example shown in the image below, you can see a rule where the company's profile becomes entirely read-only when the Status field takes the value Blocked. [](https://usermanual.vtenext.com/uploads/images/gallery/2024-10/cz5image.png) |
**Global Privileges** | It offers the possibility to configure all privileges for each individual user profile, determining what they can or cannot do or see through the customer portal. You can apply these settings to all modules of vtenext. |
**Currency Name** | The name of the currency you want to manage, for example "USA, Dollars (USD)" |
**Conversion Rate** | The conversion rate must always be linked to the base currency of vtenext |
**Status** | Active/Inactive |
**Name** | **Description** | **Parameters** | **Response** |
**create** | Create a record of the specified module | elementType (String)element (Encoded) | Return all fields and values of the created record |
Ex:**Url**: VTE\_URL/restapi/v1/vtews/create**Parameters**: {"elementType":"Accounts", "element":"{\\"accountname\\":\\"account1\\", \\"assigned\_user\_id\\":\\"19x1\\"}"} | |||
**update** | Update the specified record | id (String)columns (Encoded) | Return all fields and values of the updated record |
Ex:**Url**: VTE\_URL/restapi/v1/vtews/update**Parameters**: {"id":"3x310", "columns":"{\\"accountname\\":\\"test fede postman\\"}"} | |||
**revise** | Update the specified record. It’s different only for parameters, the result is the same | element (Encoded) | Return all fields and updated values |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/revise**Parameters**: {"element":"{\\"id\\":\\"3x27\\",\\"employees\\":\\"5\\",\\"industry\\":\\"Banking\\"}"} | |||
**retrieve** | Illustrate the fields of the specified record and their relative values | id (String) | Return all fields and values of the specified record |
Ex:**Url**: VTE\_URL/restapi/v1/vtews/retrieve**Parameters**: {"id":"3x310"} | |||
**retrieveinventory** | Illustrate the fields of the specified inventory record, their relative values and the product block’s information | id (String) | Return all fields and values of the specified record and product’s block information |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/retrieveinventory**Parameters**: {"id":"16x104"} | |||
**delete** | Delete the specified record | id (String) | Return the request status (successful or not) |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/delete**Parameters**: {"id":"3x306"} | |||
**query** | Execute a query and return the result’s rows | query (String) | Return all rows of the executed query |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/query**Parameters**: {"query":"SELECT \* FROM Accounts WHERE accountname like '%vte%';"} | |||
**listtypes** | Describe each one module which contains uitype of the specified format | fieldTypeList (Encoded) | Return module information of the specified fieldtypes |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/listtypes**Parameters**:{"fieldTypeList":"\[\\"integer\\",\\"file\\"\]"} | |||
**describe** | Describe the specified module and their relative fields | elementType (String) | Return all module information and its fields properties(no hidden fields) |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/describe**Parameters**: {"elementType":"Accounts"} | |||
**describeall** | The describeall method is different from describe one because it shows hidden fields too | ElementType (Encoded) | Return all module information and its fields properties(hidden fields too) |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/describeall**Parameters**: {"elementType":"Accounts"} | |||
**getlabels** | Return all labels and translated ones of the specified module,language | username (String)language (String)module (String) | Return labels and translated ones of the specified module, language |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/getlabels**Parameters**: {"username":"admin", "language":"it\_it", "module":"Accounts"} | |||
**getlangs** | Return all languages installed into the CRM | Return all CRM languages | |
**loginpwd** | Return user webservice access key if username and password are valid | username (String)password (String) | Return user webservice access key |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/loginpwd**Parameters**: {"username":"admin","password":"123456789"} | |||
**getmenulist** | Return all modules information (visibility, tabid, name, sequence, ...) | Return modules information and properties | |
**oldoquery** | Return records that contain the searched value into specified module’s fields | module (String)search\_fields (Encoded)search\_value (String) | Return some record basic information where searched value is contained into the specified module’s fields |
Ex:**Url**: VTE\_URL//restapi/v1/vtews/oldoquery**Parameters**: {"module":"Accounts", "search\_fields":"\[\\"accountname\\", \\"website\\"\]", "search\_value":"vtenext"} |