1 / 11

C/ALM Event Handling

C/ALM Event Handling. Kai. Scenario. RTC. RQM. Project Area. Project Area. Scenario. Iteration Plan Approved. Create Test Cases or Create Task to Create Test Cases or Do other smart things. Observation. Types of issued events are application specific

lei
Download Presentation

C/ALM Event Handling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. C/ALM Event Handling Kai

  2. Scenario

  3. RTC RQM ProjectArea ProjectArea Scenario Iteration Plan Approved Create Test CasesorCreate Task to Create Test Cases or Do other smart things

  4. Observation • Types of issued events are application specific • Events are issued in the context of projects • Event handling is project or even team specific • End users configure event handlers • This is really just “remote listeners”

  5. Context • Use Webhooks over Atom feeds • “Listeners” are URLs the subject POSTs the event to • The listener may be remote to interested application

  6. Subject Consumer ProjectArea ProjectArea Flow (stylized) Listener H1 (Service) POST event operates on knows registers H1

  7. Tasks (subject side) • Define resource format of events • Make issued events discoverable • Define protocol for webhook registry • POST to registered webhooks • Utilize existing process events

  8. Tasks (consumer side) • Define a way to register webhooks • [label, description, URL] • Allow end users to configure webhooks • allow to browse configured friends for available events • allow to directly enter URL • allow to configure parameters for webhook • support on project area and team area level • take Web UI perspective • Persist webhook configuration in the Foundation Storage Service • Register configured webhook with subject’s registry • Find reasonable integration in eclipse client

  9. Open Issues • Authentication • Licensing • When does the registration happen? • How do we represent cross app event handling in process templates? In what kind of process templates?

  10. Subject Consumer ProjectArea ProjectArea Potential Points of Authentication Listener H1 (Service) POST event operates on knows registers H1

  11. Interesting Points of License Enforcement • User needs licenses to register webhook, number of webhooks a user can register could be limited • The total number of webhooks on a server could be limited • The number of webhooks that can be called by the server for any given event could be limited. • …

More Related