Improvements and New features of system Tee-pee

 

[CHANGES] Terminating the membership of the member in the organization of a person without automatically revoking his consents

According to the requirements of the GDPR, the logic of withdrawing the consent of persons was modified as follows:

 

  • If the person who has granted consent is terminated by using the "Terminate membership in the organization" action (via the person's profile or via individual/collective actions in the list of people in the unit), the granting of consents will not be revoked. (Consents remain granted).
  • If a person who has granted consent is terminated by using the "Terminate Unit" action, for the unit in which he has primary membership, the membership in the organization will be terminated, but the granting of consents will not be revoked. (Consents remain granted).
  • If a person's mandatory consent is revoked directly from his profile (GDPR tab), membership in the organization will be terminated and only the given consent is revoked, other consents remain granted.
  • If the person who has given consent is terminated in the organisation by using the "Terminate membership in the organization" action (via the person's profile or via individual/bulk actions in the list of people in the unit), the granting of consent will be preserved. (Consents remain granted).
  • In case a person with terminated membership in the organisation wants to revoked consents, it must be done on requests and the consents will be revoked by admin as this person can not log in anymore to the system.

Read more in Units/People in the Unit, Profile/GDPR and User Management/Terminating, restoring and deleting a person.

 

[IMPROVEMENT] Frequency of email notifications

In the Notifications tab in the Person's profile, was added the option to set the frequency of sending notifications for each type of notification separately.

  • Available notification frequencies: Never (predefined option), Every time, Daily, and Weekly.
  • For frequency of notification: "Every time", the logic for sending notifications is preserved (as previously).
  • The Daily notifications are sent at 3 AM the next day.
  • The Weekly notifications are summarising the actions that have happened from Monday to Sunday. The weekly notifications are sent at 3 AM on Monday (summarising the previous week).
  • For notification type: The registration link has expired, Type of frequency "Always" is not available.
  • Administrators with permissions to administer Notifications can edit the body of the email for frequency type: Every time.
  • Each email text in Daily and Weekly notification (summary) has a preset format (only selected parameters can be edited by the administrator). These records will form a list depending on the number of concrete notification actions.
  • Administration/Notifications: If the notification has set "Turn-on automatically for a user with a role" to ON - the notification is by default set to Daily.

Read more in Administration - Settings/Notifications and Profile/Notifications.

 

[IMPROVEMENT] Added new parameters for Notification administration

New parameters have been added (and selected existing parameters have been modified) for each notification type as follows:

  • For Notification type: New unit and frequency type: Every time:
    • New parameter #ORG_UNIT_LINK# (Link to unit profile).
    • New parameter #ORG_UNIT_ID# (Unit ID).
    • Other parameters were preserved.

 

  • For Notification type: New unit and frequency type: Daily and Weekly:
    • New parameter #LIST# includes a list of individual notification records (parameters) and text in the following preset format:
      • There has been a new *ORG_UNIT_NAME* (*ORG_UNIT_LINK*) created by *CREATED_BY_NAME* of *ORG_UNIT_TYPE* type under the *PARENT_ORG_UNIT_NAME* parent unit.
      • The original parameter that can be used in the body of the email: # FIRST_NAME # (Recipient's first name).
      • The parameters in the legend are only informational and cannot be used in the body of the email.

 

  • For Notification type: Unit function assignment and frequency type: Every time:
    • New parameter #ORG_UNIT_LINK# (Link to unit profile).
    • New parameter #ORG_UNIT_ID# (Unit ID).
    • New parameter #MEMBER_ID# (Member ID).
    • New parameter #PERSON_ID# (Person ID).
    • New parameter #PERSON_LINK# (Link to person profile).
    • Other parameters were preserved.

 

 

  • For Notification type: Unit function assignment and frequency type Daily and Weekly:
    • New parameter #LIST# includes a list of individual notification records (parameters) and text in following the preset format:
      • There has been a new function *ORG_UNIT_FUNCTION* assigned to *ASSIGNED_TO* (*MEMBER_ID*) by *CREATED_BY_NAME* in *ORG_UNIT_NAME* (*ORG_UNIT_ID*) valid from *VALID_FROM*. Visit person's profile: *PERSON_LINK*.
      • The original parameter that can be used in the body of the email: # FIRST_NAME # (Recipient's first name).
      • The parameters in the legend are only informational and cannot be used in the body of the email.

 

 

  • For Notification type: User Revoked consent and frequency type: Every time:
    • New parameter #ORG_UNIT_LINK# (Link to unit profile).
    • New parameter #ORG_UNIT_ID# (Unit ID).
    • New parameter #ORG_UNIT_NAME# (Primary unit of the person who revoked consents).
    • New parameter #MEMBER_ID# (Member ID).
    • New parameter #PERSON_ID# (Person ID).
    • New parameter #PERSON_LINK# (Link to person profile).
    • New parameter #CONSENT_REVOKED_BY# (Name and surname of the person who revoked the consent).
    • Other parameters were preserved.

 

  • For Notification type: User Revoked consent and frequency type: Daily and Weekly:
    • New parameter #LIST# includes a list of individual notification records (parameters) and text in following the preset format:
      • Member of your unit (*ORG_UNIT_LINK*) *PERSON_NAME* (*MEMBER_ID*) has withdrawn the following consent relating to the processing of personal data: *CONSENT_NAME*. The consent was revoked by *CONSENT_REVOKED_BY*. Visit person's profile: *PERSON_LINK*.
      • The original parameter that can be used in the body of the email: # FIRST_NAME # (Recipient's first name).
      • The parameters in the legend are only informational and cannot be used in the body of the email.

 

  • For Notification type: User registration link expired and frequency type: Daily and Weekly:
    • New parameter #LIST# includes a list of individual notification records (parameters) and text in following the preset format:
      • *USER_NAME* (*MEMBER_ID*) has not filled in the registration form and the registration link has expired. The registration concerned the unit *ORG_UNIT_NAME* (*ORG_UNIT_LINK*). Visit person's profile: *PERSON_LINK*.
      • The original parameter that can be used in the body of the email: # FIRST_NAME # (Recipient's first name).
      • The parameters in the legend are only informational and cannot be used in the body of the email.

Read more in Administration - Settings/Notifications.

 

Tasks

  • Specific modifications of data in the database according to customer requirements.

 

Bugs

  • Fix to other minor bugs.