Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Genesys Backend
Genesys Backend
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Genesys PGR
  • Genesys BackendGenesys Backend
  • Issues
  • #441

Closed
Open
Opened May 09, 2019 by Matija Obreza@mobrezaOwner

Recording actions

Audit logs already provide lots of helpful information about history of any record. In addition, we wish to record specific actions users perform and inform the right people about these actions.

Example: Pushing passport data to Genesys

An institute is updating passport data in batches of 50. Every upsert would fire off a record saying that "Genebank PHL001 updated 50 records of their passport data".

Example: Dataset for review

When the partner has completed the forms for publication of a Dataset on Genesys, the hit the Send for review button which triggers a service method where the Dataset is then set for Review by the Genesys team.

If that API action is successful, the system should fire off a message saying "Dataset So and so title is ready for your review". But because the owner can still reopen the Dataset for editing, any record about previous event should be removed from the system.

Vision

With such records in place, we can send email notifications to persons who need to know that something happened in Genesys. As actions happen, we scan who needs to receive notifications and make a database entry for them.

My old code at https://github.com/kenorem/iita-common/tree/master/src/org/iita/notifications might help.
Also:

  • https://github.com/kenorem/iita-common/blob/master/src/org/iita/annotation/Notification.java
  • https://github.com/kenorem/iita-common/blob/master/src/org/iita/service/impl/NotificationSubscriptionServiceImpl.java

Before you start, we should discuss.

Edited May 09, 2019 by Matija Obreza
Assignee
Assign to
2.5
Milestone
2.5
Assign milestone
Time tracking
None
Due date
None
Reference: genesys-pgr/genesys-server#441