Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend communications table to correlate sent messages and responses #50

Open
ryankortbeek opened this issue Feb 3, 2022 · 1 comment
Labels
enhancement New feature or request low priority Nice to have functionality

Comments

@ryankortbeek
Copy link
Member

Brief Feature Description

Correlate sent messages and satellite responses by adding an additional column to the communications table in the database. The comm.py module will also need to be modified to add the reference to the sent message id when creating the communication record for the response.

Additional Details

  1. Extend communications table to have a sent_message_id field (or some name like that) of type int (and nullable=True) which references the id of the communications record that the response is a response to
  2. In the comm.py module when creating a communication record for the response, include the message_id of the communication that was sent to the satellite

Priority

Low

@ryankortbeek ryankortbeek added enhancement New feature or request low priority Nice to have functionality labels Feb 3, 2022
@jmmabanta
Copy link
Contributor

More Additional Details:

  • It should work similar to the 'admin creator' user account relation where a sent message can be associated with multiple responses.
  • If a sent message has at least one associated response, hide the 'Queue' button and prevent it from being Queued/Dequeued again.
    • This is to prevent a command from being sent multiple times without it being logged properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request low priority Nice to have functionality
Projects
None yet
Development

No branches or pull requests

2 participants