Objective
This page explains on the topic of how to create a new event on Rapla and explains further on different scenarios.
Complexity
| Status | ||||
|---|---|---|---|---|
| Status | ||||
|
|
Page Contents
...
You have already read Introduction to Rapla
You have already installed Rapla as per Accessing Rapla
You have a valid Rapla user account
Key terms and concepts
| Info |
|---|
NoteBoth admin and non-admin user privileges are able to create events in Rapla. Only admin users may edit events created by other users. |
| Note |
|---|
Be advisedThe user needs to make sure they are not highlighting anything on the left-hand side of the menu bar. This can cause Rapla to think that you are creating any events against that resource. Hence, you might see a warning message as below. |
Explanation of
...
Standard Event Types
Sessions (Lecture, tutorials, etc.) - most popular one, used for synchronising with Paradigm
Meetings
Exams
Student bookings
Auditions
Explanation of Standard Event Attributes (Fields)
Take the most popular event type - Session as an example, please see the following common attributes:
Field Name | Description |
|---|---|
Unit Name | |
Unit Code | |
Session Type (e.g. class, tutorial, lecture) | |
Campus | |
Minimum Participants | |
Maximum Participants | |
Faculty/Department | |
Session Group ID | Do not change |
Session Seq ID | Do not change |
Workflow
How to create a single event on Rapla
You will use the left mouse (drag and drop) to mark the time period for the specific appointment you want to. The marked rows are highlighted in pale blue (As as below).
...
2. Right click a new context menu appears, then select the suitable event type, ranging from a session, generic event, meeting or student booking. In the below instance, it is an example of creating a new Event (Paradigm Session).
...
Note there are three sections:
The upper section: confirm the Event type you want to create, fill out these fields that are critical for integration between Rapla and Paradigm: Unit Codes (E.g. FIT9130), Unit Name, Campus (if applicable), Delivery mode, Department.
...
The middle section shows the detail of the appointment: you will need to fill out the start and end date, select whether it is a single event or recurring one. You can even exclude public holidays or semester breaks if applicable (Refer to below scenario 2).
...
The bottom section shows the resources you want to allocate to, add the resources from the left hand side to the right section by either double clicking or click on the resource and go to click Add button
...
3. Click on Save button.
| Expand | ||
|---|---|---|
| ||
This is one of magics that Rapla will show you next... While you follow the above steps of creating events/appointment, when you reach to the bottom section - resource allocations. Rapla tells you the available resource by |
having a green icon |
at front. The red cross icon means the resource has been taken for another event. So you should try to avoid |
allocating it again |
.  |
...
| Expand | ||
|---|---|---|
|
...
| |
|
...
|
...
|
...
|
...
|
...
|
...
|
...
 6. You have now created a repeating event with one or more exception(s). |
...
| Expand |
|---|
...
| ||
|
...
|
...
 |
4. At Resource Allocation section, you need to assign resources (e.g. staff, rooms) to each appointment individually. |
5. Currently all resources have been set to every appoint, you can change it by click on 'Every appointment'. It opens up more options to each appointment. |
6. Resources have been color coded and allocated to Appointment 1 and Appointment |
2. |
...
 |
Further Reading
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Related Pages
| Related Labels |
|---|