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

Filtering Subscriptions - Sender Field #17

Open
EdCampion opened this issue Feb 17, 2017 · 0 comments
Open

Filtering Subscriptions - Sender Field #17

EdCampion opened this issue Feb 17, 2017 · 0 comments

Comments

@EdCampion
Copy link

EdCampion commented Feb 17, 2017

Hi,
I've looked at issue #7 and I'm not sure if it solves my issue, or if my case is more complex.

Given entities Transport Order, Company, User and Application.

A Transport Order is created by and "belongs to" a Producer Company. It is consumed by Consumer Companies. It maintains a m2m "consumers" relationship with companies.
Users are employees of the companies
Consumer companies only wish to be notified about updates/ deletes to Transport Orders they consume.
Applications are OAuth apps created by developers, to act on behalf of Users.

Ideal Flow

  1. Application on behalf of an employee of a consumer company registers a subscription to transport_order.change.

  2. Producer company edits an order consumed by the consumer company

  3. Consumer company's webhook is hit by the change, and not with changes to orders it does not subscribe to.

I don't think the sender_field is advanced enough to handle this, but hopefully I'm wrong?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant