Purpose: The purpose of this exercise is to create a new period that will be used when creating a new day type.
Windows:
Period
Open the Period window.
Populate the window and review the existing periods (e.g. WORK).
Create a new row and enter the following information:
Period | Name |
LUNCH | Lunch period |
Result: You have now created a new period that can be used when defining a work day. This period should be used to describe lunch hours every day.
Purpose: The purpose of this exercise is to create new work types that will be used when creating a new schedule and exceptions to that schedule.
Windows:
Day Types
From Time | To Time | Period |
08:00:00 | 11:30:00 | WORK |
11:30:00 | 12:00:00 | LUNCH |
Result: You have now created a new day type, describing the working hours and lunch time when working only half day.
Note: The total amount of working time is calculated in minutes and will be displayed in the Working Time field.
Note: Since this day type does not include working hours, no work period will be specified. Therefore the table part of the window will be left blank.
Purpose: The purpose of these exercises is to create a work time calendar that can be used in other IFS Applications components.
Windows:
Schedule
Schedule Exception
Calendar
In this exercise, you will create a schedule that will be included later in the work time calendar. This schedule will describe the working days of a person who tests race cars. The week includes two half days.
Note: This schedule has a period of seven days, restarting every Monday.
Day No. | Day Type | Description | Working Time |
1 | WEEKDAY | Weekday | 480 |
2 | HALFDAY | Half day | 240 |
3 | WEEKDAY | Weekday | 480 |
4 | WEEKDAY | Weekday | 480 |
5 | HALFDAY | Half day | 240 |
6 | WEEKEND | Weekend | 0 |
7 | WEEKEND | Weekend | 0 |
Result: You have created a schedule that describes the working time of a test week. The week consists of seven days: five working days and two non-working (weekend) days. On two of the working days, the training is only scheduled for half a day.
Note: The working time is measured in minutes.
In this exercise, you will create an exception to the schedule created previously. This exception will describe the holidays for a test driver during one year.
Date | Day Type |
2003-01-01 | HOLIDAY |
2003-12-25 | HOLIDAY |
Now you are going to create a calendar. The calendar will consist of the schedule and the schedule exception defined before.
Note: The state of the calendar is Not Generated. The calendar must be generated to function within the system.
In this exercise, you will generate the calendar that you defined above.
Note: This step might have a big impact on the overall system behavior. The effects on each component are defined in the relevant component, but the changes are of type major.
Note: Calendar changes should not be done during business hours and the changes should be done with extreme caution.
Note: All changes in other components are done using the usual business logic; therefore, use the same security mechanisms as always. For example, if a calendar change makes it necessary to move a delivery date for a customer order, the user running the update should be allowed to make that change.
Result: A background job is started, generating the calendar. This may take a while.
Note: You can find information about background jobs in the Background Jobs window.