Managing Parameters with Associated Rights
In VHQ, Parameters rights restricts a user in viewing or editing the parameters based on the access level. The user is restricted or allowed to access to any parameter, on the access level defined in the Parameter Form file. These restrictions are of great help in hiding or showing the parameters for the specific users.With the current implementation, the user can not only hide or show the parameters or edit the parameters, but can also restrict the value of the parameter, even if the user has a right to view the parameter.
NOTE: If a parameter value is a password of some sort, other users will not be able to see the password, even though they have access to view or edit the parameter.
In order to meet the requirement of the user, a new attribute “MaskValue” is introduced next to “Access” attribute in VPFX XML. Masking is an act of applying a mask to the value. If the “MaskValue” attribute is set to ‘true’ (case insensitive) then the parameter value is masked with asterisks (*****), else if set to “false” the value is unmasked.The user with add permission will be able to define and add value to the defined parameter irrespective of the value being masked. The user with modify permission will be able to edit the parameter value and can also restore the parameter value to default. However, the modified value cannot be seen, since that is the expected behaviour of MaskValue. The user cannot delete the parameters.
NOTES: The user must not be able to copy the value.Masking is only applied to the parameters whose value type is String.If the MaskValue attribute is not set to true or false (Boolean value) in the form view xml file, then by default the attribute is unmasked and the user is not allowed to upload the form file. The following error as “Invalid file format” is displayed.
Multi-Merchant and Card Range Parameter ManagementMulti
MultiVHQ offers support for Multi-Merchant and editing of Card Range parameter management for all the VHQ managed devices. The multi merchant functionality allows several merchants to share a single device, making it easier for the merchants to configure, edit, download and manage the values of the application parameters. The device owner creates the merchant IDs to be accessed by the individual merchant. The merchant then logs in to the device with the credentials and perform a transaction, which gets recorded into the system.VHQ supports Multi-Merchant functionality by reusing the same set of parameters and creating multiple instances with different parameter values.With the existing functionality, VHQ manages parameters for applications at container levels, where the parameters were mapped to a single instance. However, with the introduction to Multi-Merchant functionality, VHQ supports handling of parameters for the applications multi-instance and multi-level.Multi-Level: Multiple child levels for the Parent. Hierarchal levels of parent child relationship.Multi-Instance: A set of parameters which are repeated for the same level with different values.As part of the VHQ Multi-Merchant parameter management process flow, the application developers build a parameter definition file (.vpdx) that defines all parameters of the application and their attributes and multiple form files (.vpfx) for editing application parameters.
NOTE:A hair salon could get a device that serves up to 20 different merchants, so each stylist/contractor/merchant would function as an individual by logging into the same device with the provided credentials and perform the transaction.
In most cases the multi merchant devices, download the parameters once per business day (or more often) and next-day funding options offer cash-flow opportunities that were previously unattainable. If any parameter is edited or new instances are added, the parameter download happens.
NOTE:Parameter editing and viewing is allowed only if application is configured with form file or when the form file is uploaded.
