Enables user interaction via BankID.
Allows users to sign documents using BankID.
See extended documentation for detailed installation instructions, how to get the certificates, and pricing information.
All certificates required for testing and production are available here (except the client certificate for production) if they are not already installed.
The component will use BankID's test server when the system setting BankIdUseTestId is enabled.
Requires the user to have a BankID for the specified personal number.
Must contain exactly 12 digits and no other characters.
SoftadminApi.User has support for storing personal numbers via the procedure SoftadminApi.User_UpdatePersonalNumber. The PersonalNumber column of SoftadminApi.User can then be used to retrieve the personal number.
Formatted text to sign, shown in the user's BankID app.
FormattedTextToSign can not be combined with TextToSign.
Additional data that will be signed but which is not shown to the user.
It might be tempting to include the entire document to sign (e.g. a PDF file) here, but it will require additional disk space. The data will be included in the signature (stored in SoftadminApi.BankIdSignature), which means that disk usage will increase proportionally to the size of the data.
The name of the file.
The result of the signing.
Allows you to validate the parameters supplied by the user before any other SQL is run in the component. This call is only made if the component has visible parameters, the SQL is a stored procedure, and Validate parameters is checked.
Use this call to restrict which entries a user is allowed to view and edit, and to log which entries a user views.
Access to a menu item is normally controlled through functions and roles alone but some entities need more fine grained control. For example, a user may have access to the View Member menu item for normal members but not for members with a protected identity.
The menu items a user visits are always logged (in ADMINLogMenuItem) but for sensitive data you may need to log exactly what entries are viewed. Do the logging in this call as the common ways of viewing data (grid and InfoSQL) are not allowed to modify the database.
If you bind a scalar function instead of a stored procedure to this call then its name must end with '_GrantAccess'.