PhenixID Signing Workflow 2.3.0 improves the stability, compatibility, and security of your solution and is recommended for all installations.
PhenixID is proud to announce the new release of PhenixID Authentication Services (PAS) 4.7. The new release improves the stability, compatibility, and security of your solution and is recommended for all installations.
PhenixID Signing Services Workflow 2.2.0 improves the stability, compatibility and security of your solution, and is recommended for all installations.
PhenixID is proud to announce the new release of PhenixID Authentication Services (PAS) 4.5. The new release improves the stability, compatibility, and security of your solution, and is recommended for all installations.
The highlights for the 4.5 release include compliance to DIGG “Deployment profile for the Swedish eID framework”, animated QR code for BankID and WCAG 2.1 updates.
In addition, several features have received minor improvement including:
Read the full release notes for Authentication Services here:
Read full releaseThis patch release includes defect fixes and addition of minor functions for the 4.7 release, and is recommended for all 4.7 installations.
PhenixID is proud to announce the new release of PhenixID Authentication Services (PAS) 4.6 The new release improves the stability, compatibility, and security of your solution, and is recommended for all installations.
The highlights for the 4.6 release include updated HTTP API for BankID, Freja eID and SITHS, addition of Freja eID in “verify user” template and valves for BankID SIGN with QR code support.
In addition, several features have received minor improvement including:
Defect fixes recommended for all users, including
Read the full release notes for Authentication Services here:
Read full releasePhenixID Signing Workflow 2.5.0 improves the stability, compatibility and security of your solution, and is recommended for all installations.
The highlight for the 2.5.0 release includes the ability edit already created errand.
Edit errand
Prior to this release, the only thing that was possible to update on an errand was the expiration time. If the wrong person was invited as a signer, or someone was missing, a solicitor had to delete the old errand and create a new one. Signers who had already signed the document had to sign again. This release adds the possibility for the solicitor (via GUI or API) to edit an already existing errand.
Reminding signers
In the configuration its possible that a email reminder is sent prior to the errand expires. Now a solicitor can also trigger a reminder email to a signer that hasn't yet signed by clicking a button in the GUI.