Deleting errands

All errands are saved in the SWF database for future reference, althought the actula document can be deleted after a configured lifetime. Organizations might have policiys to delete information about digital errands after a specific time.  It could also be that errands that arent successul (maybe someone refused to sign) chould be removed right away to avide clutter. Added in 2.3 there are 3 different ways to delete an errand

• Scheduled jobs – configure the lifetime of errands for a specific state
• Delete signing errand via GUI
• Delete siging errand via API

Anonymizing signer

Siging errands in SWF database include information about the people set to sign, information that could include AD usernaname,  e-mail address or social security number (“personnummer”). General Data Protection Regulation (GDPR) adopted by European Union in 2016 regulates the use and ownership of personal data. It includes the right for any person to be forgotten and have their information removed from any data storage.

To help the administrator to comply with GDRP, SWF 2.3.0 includes the possibility to anomynize a user. The administrator can execue a job to anonymize a user based on either UUID, personnummer, username or email address. At anonymization, errans including the user that has asked to be forgotten are updated and all information about this user are replaced with “anonymized”, however still present in the errand database. For example, a errand including users john.doe and jane.doe, where john.doe is anonymized will still be present but when opened it says that the signers are “jone.doe” and “anonymized”.

IMPROVED FUNCTIONS

In addition, several features have received minor improvement including:

• Added additional Java arguments for Hazelcast in the startup scripts to get the best performance results
• Set notifyUser parameter via API
• Minor GUI improvements

BUG FIXES

IGA-434 Can’t change language
IGA-438 Empty defaultLanguage config value cause crash