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

add: Conditionals in Table Change Alerts #203

Closed
emoss08 opened this issue Jan 7, 2024 · 3 comments
Closed

add: Conditionals in Table Change Alerts #203

emoss08 opened this issue Jan 7, 2024 · 3 comments
Assignees
Labels
backend Change to backend application client Change to client application enhancement New feature or request included in next release Enhancement will be deployed in the next release

Comments

@emoss08
Copy link
Owner

emoss08 commented Jan 7, 2024

Is your feature request related to a problem? Please describe.
The need for this feature arises from the requirement to have more control and flexibility in triggering alerts based on specific conditions and criteria within a database system.

Describe the solution you'd like
The proposed solution aims to enhance the alerting functionality within our system by introducing conditional logic and data joins to tailor alerts to specific use cases. This feature would empower users to set up alerts that trigger only when certain conditions are met, and also incorporate data from related tables when necessary.

  1. Conditional Logic for Alerts:

    • When adding a table change alert, users should have the option to define conditional logic that dictates when the alert should trigger.
    • Conditions can be based on specific columns or fields in the database, such as customer information, actions (e.g., insert), and any other relevant criteria.
    • For example, if an alert is set to trigger on a database insert action, users can specify additional conditions like "only trigger for a specific customer" or "only trigger when a certain frequency is met."
  2. Data Joins for Enhanced Information:

    • To add further depth and relevance to alerts, the feature should allow users to perform data joins with related tables.
    • For instance, if a customer requests equipment positions for a tractor, users can configure the alert to join data from tables like "order," "movement," and "equipment positions" to provide comprehensive information.
    • This feature would enable users to create more context-rich alerts that deliver valuable insights to external customers.

By implementing these enhancements, our system will provide a powerful and customizable alerting mechanism, improving user satisfaction and meeting the diverse needs of our customers.

@emoss08 emoss08 added enhancement New feature or request client Change to client application backend Change to backend application labels Jan 7, 2024
@emoss08 emoss08 self-assigned this Jan 7, 2024
@emoss08
Copy link
Owner Author

emoss08 commented Jan 8, 2024

Passed first wave of test. Still have not worked on getting it to work with joins ,but it does work with simple conditions such as where a field equals a specific value.

@emoss08
Copy link
Owner Author

emoss08 commented Jan 14, 2024

Going to start working on the client side implementation for this.

emoss08 added a commit that referenced this issue Jan 26, 2024
@emoss08 emoss08 added the included in next release Enhancement will be deployed in the next release label Jan 26, 2024
Copy link

repo-ranger bot commented Jan 26, 2024

Congratulations! This issue has been included in the next release! Closing in 15 seconds . . .

@repo-ranger repo-ranger bot closed this as completed Jan 26, 2024
repo-ranger bot pushed a commit that referenced this issue Jan 26, 2024
* chore: bump deps

* change: minor layout fixes

* feat: table change alert #203

* change: dark theme

* change: admin pages to adjust to layout

* change: borders on fields to new class

* change: data-table style

* change: data table pagination to no longer show

if there are no pages or records in the table do not show the pagination

* change: remove footer and adjust layout styles

* change: layout skeleton style

* change: logo to unpic instead of react lazy load

* change: tailwind convention

* chore: bump deps

* remove: coverage from tests

* chore: cleanup unused code

* add: signal to create org google api

* Update Feature Flags.md

* fix: broken tests

* Update factories.py

* add: table and topic apis for table changes

* Update managers.py

* Update urls.py

* add: business units to excluded topics

* change: org and business unit name in create system user

* change: map view option buttons

* change: background of worker list

* chore: change to new tailwind conventions

* add: database choices for table change alerts

* Update organization.ts

* Update index.ts

* Update OrganizationRequestService.ts

* add: alert to reset password page

* change: style to match new dark app style

* Delete resizable.tsx

* add: hook to get table change alert requirements

* add: cards to location pages

* change: sheet header style

* Update team-switcher.tsx

* change: input focus color to orange

* Update theme-switcher.tsx

* remove: unused assets

* remove: loading text from button

* Create logo.webp

* Update App.css

* change: auth pages

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Change to backend application client Change to client application enhancement New feature or request included in next release Enhancement will be deployed in the next release
Projects
None yet
Development

No branches or pull requests

1 participant