Internal Errigal Collaboration Wiki

User Tools

Site Tools

Trace:
Writing /app/www/public/data/meta/onboarding/ticketer/ticket_creation_activity_checks.meta failed
onboarding:ticketer:ticket_creation_activity_checks

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
onboarding:ticketer:ticket_creation_activity_checks [2017/02/21 15:11] – adowlingonboarding:ticketer:ticket_creation_activity_checks [2021/06/25 10:09] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== Ticket Creation Activity Checks ======
 + --- //[[anna.dowling@errigal.com|Anna Dowling]] //
 +
 +==== What is a ticket creation Activity Check? ====
 +
 +Ticket creation activity checks were originally created as a means of automatically checking for tickets that are generated (via email parsing groovlets) from dig ticket emails received from call centers.
 +
 +An example use case would be to check the 'New York' visibility for a minimum amount of 10 tickets created in the last 24 hours. If there is a "lastAlertEmailSent" date associated with the object, we have sent an email alert on this. Once we get back to a stage where we are reaching the minimum count required once again, we clear out this date (Enables this to re-send another email if the minimum threshold is not reached once again).
 +
 +==== How does it work? ====
 +Based on the actual amount of tickets created in a certain period, if a ticket count threshold is breached, send an email to specified users to notify them that a minimum count has not been met, highlighting a potential issue with ticket creation for a specific visibility.
 +
 +As previously mentioned this is assigned on a visibility level. To configure a ticket creation check on a specific market you can navigate to the controller page located in **/Ticketer/ticketCreationActivityCheck/list** .
 +From here you can add a new TicketCreationActivityCheck. The form looks as follows:
 +
 +{{:onboarding:ticketer:screen_shot_2017-02-21_at_16.40.48.png|}}
 +
 +Fields to fill out are as follows:
 +  * **Visibility** - The market to monitor.
 +  * **Minimum Ticket Count Threshold** - The minimum number of tickets to be created before an email is sent.
 +  * **Timeframe In Hours** - the timeframe in which the mimiumum tickets created can be hit.
 +  * **Last Alert Email Sent** - Populated the last email notification which has been sent to the various interested parties.
 +  * **Active** - Flag to determine whether the check is active or not.
 +  * **Ignore Weekends** - Flag to determine whether to run this check on the weekends as these are often quieter periods for a network.
 +
 +The job itself is run from the quartz page in the Ticketer under the name TicketCreationActivityCheckJob. It runs on an hourly basis as demonstrated below:
 +
 +{{:onboarding:ticketer:screen_shot_2017-02-21_at_16.49.12.png|}}
 +
 +==== Self Assessment ====
 +
 +  - Review the TicketCreationActivityCheck parameters.
 +  - Based on the knowledge provided above, how would you verify from a TicketCreationActivityCheck email that it is just a quiet time for that network and that there is not actually a problem that is preventing ticketing?
 +  - If necessary, ask a member of support to forward a warning email received in the past for TicketCreationActivityCheck on a particular market.
 +
 +
 +
  

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki