---

Create Events for Requirements

Report Description:

This report will automatically schedule events based on specific types of requirements. For example, if you add a requirement of “drug testing” you may want Quest to randomly select people with that requirement to come in for testing. This report will randomly pick the person and schedule an event for them to appear.

Running the Report:

This report should configured and set up as a scheduled job. It should NOT be run manually.

The Report:

This does not produce a report, instead it creates events based on the report settings.

Where the data comes from:

You indicate which type of event you want added. You decide the event time. You indicate which calendar the event should be added to.

Report Settings:

# — Required settings —
class=equest.app.reports.CreateEventsForRequirements

# default event type to create
# eventType=<EVENT TYPE>
eventType=DR

# default event time for the events
# eventTime=<valid time format>
eventTime=7:00 am

# default court for the events
# court=<COURT CODE>
court=DR

# base probability on the requirement, but then determine each person to schedule individually
scheduleByPerson=n

# Minimum number of < 100% entries to include # We default to 1 if not specified.
# minPicked=1

# Maximum number of < 100% entries to include # We default to 2 if not specified.
# maxPicked=2

# skip scheduling on weekends
# skipWeekend=<Y/N>
skipWeekend=Y

# skip scheduling on holidays
# skipHoliday=<Y/N>
skipHoliday=Y

# Requirements to process
# requirement.<TYPE>=<probability>
# requirement.<TYPE>/<CODE>=<probability>
# requirement.<TYPE>/<CODE>/<PHASE>=<probability>
# requirement.<TYPE>/<CODE>/<PHASE>/<ATTRIBUTE>=<probability>
# requirement.<TYPE>/<CODE>//<ATTRIBUTE>=<probability>
# where:
# <TYPE> = requirement type
# <CODE> = requirement code
# <PHASE> = requirement phase
# <ATTRIBUTE> = requirement attribute
# <probability> = chance of being scheduled each day (1 – 100)

requirement.CC=100
requirement.CC/DR5=100
requirement.CC/HDAD//DR=100
requirement.CC/DTC/1=100
requirement.CC/DTC/2/BLUE=50
requirement.CC/DTC/2/GREE=75
requirement.CC/DTC/2/YELL=25
requirement.CC/DTC/2/RED=0

# For any of the above requirement entries, you can override the default event type, time and/or court. # NOTE: The portion before the ‘.’ below must match the portion after the ‘requirement.’ in the above definitions, for example:

<TYPE>/<CODE>/<PHASE>/<ATTRIBUTE>.eventType=<EVENT TYPE>
<TYPE>/<CODE>/<PHASE>/<ATTRIBUTE>.eventTime=<valid time format>
<TYPE>/<CODE>/<PHASE>/<ATTRIBUTE>.court=<COURT CODE>

CC/DTC/2/BLUE.eventType=BDR
CC/DTC/2/BLUE.eventTime=8:00 am
CC/DTC/2/GREE.eventTime=9:00 am
CC/DTC/2/YELLl.eventTime=10:00 am
CC/DTC/2/RED.eventTime=11:00 am

# To automatically, based upon probability, schedule additional events for a requirement being selected # NOTE: The portion before the ‘.’ below must match the portion after the ‘requirement.’ in the above definitions, for example:
# requirement.<TYPE>/<CODE>/<PHASE>/<ATTRIBUTE>.more.n=<probability># requirement.<TYPE>/<CODE>/<PHASE>.more.n.eventType=<EVENT TYPE>
# requirement.<TYPE>/<CODE>/<PHASE>.more.n.eventTime=<valid time format> # requirement.<TYPE>/<CODE>/<PHASE>.more.n.court=<COURT CODE>

# To automatically include other requirements based upon another requirement being selected
# NOTE: The portion before the ‘.’ below must match the portion after the ‘requirement.’ in the above definitions, for example:
# requirement.<TYPE>/<CODE>/<PHASE>/<ATTRIBUTE>.auto.n=<TYPE>/<CODE>/<PHASE>/<ATTRIBUTE>

# — Optional Report settings — #report.notify.userID.1=xxxxxx prompt.parm.1=startDate prompt.parm.1.type=date prompt.parm.1.label=Event date prompt.parm.1.required=false prompt.parm.1.default=+1