Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
ugx-01 [2015/01/14 15:45] – Failure log 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. | 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, | If the shifts generated by the Master Roster are to be filled automatically, | ||
Line 27: | Line 27: | ||
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 **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, | + | The whole Master Roster may be **Terminated** when no longer needed. This is irreversible, |