Differences

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

--- ugx-01 [2015/01/14 12:21] – Add text Michael Scott
+++ ugx-01 [2017/12/01 16:35] (current) – external edit 127.0.0.1
@@ Line 7: / Line 7: @@
 The **Days In Cycle** value determines the length of the repeating cycle. The default is 7 for one week.
-A Master Roster starts with a status of **Design**, which means that added master shifts can be freely moved and deleted, and no live shifts are generated. After it is made **Live**, any changes are carefully marshalled and logged.
+A Master Roster starts with a status of **Planning**, which means that added master shifts can be freely moved and deleted, and no live shifts are generated. After it is made **Live**, any changes are carefully marshalled and logged.
 If the shifts generated by the Master Roster are to be filled automatically, a list of **Preferred Candidates** must be supplied and ranked in order of preference. The **Use Only Preferred Candidates** setting prevents the shift matchers from using candidates outside the preferred list for shifts generated by this Master Roster.
-Master shifts are added, like normal shifts, from the list of Shift Templates. Master shifts are assigned to a **Next Date** which is the nominal next date on which a shift will be generated. E.g. if creating a Master Roster on a Wednesday, you can place all the Master shifts in the current week even though the Monday and Tuesday ones are already in the past. The automatic shift generation process will sort it out and roll forward appropriately.
+Master shifts are added, like normal shifts, from the list of Shift Templates. Master shifts are assigned to a **Next Date** which is the nominal next date on which a shift will be generated. E.g. if creating a 7 day Master Roster on a Wednesday, you can place all the Master Shifts in the current week even though the Monday and Tuesday ones are already in the past. The automatic shift generation process will sort it out and roll forward appropriately.
 A live Master Roster may be **Paused**. No live shifts will be generated while it is in this state. This is useful if the Master Roster pattern needs to be substantially changed. Pausing and Unpausing events are both logged.
@@ Line 20: / Line 20: @@
 These changes can all be undone, by going to the **Change Log** view and right-clicking on the event you want to undo. However they cannot be undone once live shifts have been generated against the changed masters, which is a good reason for **Pausing** until you are happy with your changes, if live generation is happening continuously.
+The Live Shift generation and filling process is normally automatic, based on a defined schedule, but it can be forced using the **Generate Live Shifts** button, so that you can get immediate results.
+The **Failure Log** view details all failures encountered while generating and filling live shifts. For example you can use it to discover exactly why the expected candidate was not booked for a particular shift (on holiday, booked elsewhere, expiry of qualifications etc).
 The whole Master Roster may be **Suspended** using the button on the top panel. This works by applying a suspension to each affected Master Shift. They will all be logged and, if you need to undo, you must undo the individual log entries.
-The whole Master Roster may be **Terminated** when no longer needed. This is irreversible, but you can create a new Master Roster in Design Mode by using the **Duplicate** button. This copies the live master shifts and preferred people.
+The whole Master Roster may be **Terminated** when no longer needed. This is irreversible, but you can create a new Master Roster in Planning Mode by using the **Duplicate** button. This copies the live master shifts and preferred people.