You create a conditional activity by setting Self-Signups to Matches Role. A conditional activity will be included on a person's self-signup page only if the person's registration info contains a matching role:
In general, you should consider using conditional activities only if your group manages people in terms of roles in the real world. Otherwise in practice, you will not be able to maintain accurate Roles data inside PRESTO.
Suppose you are signing up ushers for a performance series and have 2 kinds of ushers: Ushers and Senior Ushers. Suppose as well that Senior Ushers can signup for both jobs, but Ushers should not signup as Senior Ushers. Thus you want the self-signup page of ushers to not include any Senior Usher schedule items.
To accomplish this, you could:
In this basic case, you could achieve the same effect by setting up Usher as an unconditional activity — since everyone can signup for it. That is, you could:
You use the Category Request signup style when you want people to request a job category and then have an admin assign them to a specific job in that category.
After someone signs up for a job category, you use the admin-signup page to *move* her to a specific job. When you are satisfied with (some section of) the schedule, you approve all these Ready requests.
Note that, prior to approval, a signup is shown at the job category in a person's Your Signups list and when a List All Signups is done. It is only after you have *approved* the request that the specific job is shown in these places. In other words, it is easy to keep tentative schedule assignments private until you are ready to share them.
When you do a Create Activity with the Category Request signup style, normally you leave its Location blank. Conversely when you create a specific-job activity, you give it the same Base Name and use Location to identify which job it is.
Note that there is special support for doing this. Setting a category activity's Location field to a comma-separated list will cause Create Activity to create a location-suffixed activity for each location in the list. Additionally each such specific job will have its Self-Signups property set to Not Allowed, and its Signup Style property set to Immediate.
Note that you can create all 3 items at once using Do Setup Action->Add Activity Grids.
Note that you can create more involved shift schedules "manually". For instance, you can expose specific schedule items to senior people via conditional activities.
The number of signups for a Category Request schedule item is the sum of the signup requests and approved signups anywhere within the category. On the other hand, the # of Spots for such an item is normally the sum of its specific-item spots. But if a category allows unlimited signups or has no specific-item slots, the entered value remains its # of Spots setting.
You can create sub-category request schedule items in a category (e.g. Election Official, North and Election Official, South). The specific items of a sub-category are those whose Locations start with the sub-category's Location. That is, if a sub-category's location is ABC, its specific items are those whose locations start with ABC. Sub-category counts work like category counts. For example, suppose Election Official, North&South Precinct 1&2 are your four specific items, and each has 2 spots with 1 filled. Also suppose there are 2 pending requests at Election Official, North. Then:
A judged contest is one in which an entrant's result is determined by evaluation. (Note that the Judged Contest feature can be applied to situations other than contests. For example, it could be used to tabulate employee-performance evaluations).
To create1 a judged contest (say an essay-writing contest):
A person, say Tom Jefferson, would enter the contest by clicking on the event's Author Signup link on Self-Signup Home, and then signing up for the Essay Contest activity. Judges would later score Tom Jefferson's entry by clicking on the event's Judge Essay Contest link, and then signing up for the Tom Jefferson, Essay Contest activity4.
By default, the Scorecard activity for scoring a contest entry is named person's name, contest's name (as in Tom Jefferson, Essay Contest). If you want judging to be anonymous, include a required field in Essay Contest Form whose name2 starts with E:. For example, suppose that Tom Jefferson typed "Declaration of Independence" into the E:Essay Title field, then the scorecard for his entry would be named Declaration of Independence, Essay Contest.
When you created the Essay Contest activity, PRESTO automatically created 4 elements for you. These elements influence what judges see. Thus before a contest is judged, you should look over these 4 elements and make any updates needed to fit your situation.
These elements are:
To view an entrant's scores so far, click on the entrant's Essay Contest signup on the Admin-Signup page. You can also create and view contest reports. Note that people with Observer or Agent privilege can also view contest scores and any contest reports you create.
To create a contest report (say Essay Results Summary):
To generate this report:
If you had multiple contests with the same scoring columns and wanted to view results of just one of them, the Current Event scope would not suffice. You would have to: