I greatly appreciate the Access authorization to form fields in WEBCON BPS – it’s a much-needed and well-designed solution that all most meets our needs.
Like many other organizations, we handle sensitive data that should not be stored in plain text in the SQL database. To address this, we've developed a simple SDK-based customization of a form field that displays the field value on the form, but stores it in an encrypted format in the database.
Unfortunately – and to our disappointment – field-level access authorization is not supported for SDK-customized fields. This significantly limits the use of both features together, which would otherwise be a perfect solution: secure on the interface level, and secure at the data storage level.
I strongly believe that many clients would welcome a solution where field access requires authorization, and the value is encrypted in the database. This combination would provide a much higher level of data protection, especially for systems handling confidential or regulated information.
Or allow to use Access authorization to form fields in while SDK customization is used.