Overview
Now that you have created users, added new resources, and time periods in Rapla, its now time for you to create sessions or events. Creating events in Rapla can be relatively straightforward if you are already familiar with the interface and you have already experimented with the look and feel of the environment. This knowledge article will guide you with the basics of creating sessions or events in Rapla, the possible functionalities you can use which could be relevant to your business or institution (Exceptions, Appointments, Groups and Class – which will be discussed further in the Advanced section of this documentation), and how to deal with conflicts.
| Note |
|---|
BE ADVISED Paradigm vs Rapla Data EntrySCHEDULED UNITS: It does not matter if you make the Rapla Paradigm Session Event first or the Scheduled Units in Paradigm. The only thing that matters is that the Scheduled Units have been created in Paradigm BEFORE you attempt to sync the data from Rapla to Paradigm (see https://silverband.atlassian.net/wiki/spaces/DPG/pages/1516044289 on how to synchronise data to Paradigm). TIME PERIODS: The naming conventions of academic periods in Rapla may be different to Paradigm as that information is not part of the data sync. However, having them the same would be significantly better for your end users to avoid confusion. Just note of the coding of your time periods in Rapla – the Start and End Dates of your coded sessions in Rapla should be THE SAME or WITHIN the Start and End Dates of the Time Period coded in Paradigm. |
Event Types
NOTE: The event types mentioned below are the default event types we’ve configured for your Rapla application. These are highly customisable. Please feel free to raise a ticket or contact our Support Team if you have any questions or clarifications on the event types mentioned below.
Event Type | Description |
|---|---|
Student Booking | To be used for student booking. This event type will ask you for the Student name, Student Number, etc.information when you create the booking. |
Generic Meeting | To be used when scheduling all types of meeting. This event type will ask you to enter the Meeting Name or Reservation Name. |
Generic Event | Sessions or Events that doesn’t fall to any of the three types (Student Booking, Meeting, Paradigm Session) This Event Name and Key Staff Member are the possible fields, and will also allow you to select an Event Type |
Paradigm Session | This is the event type which is being used to synchronise sessions to Paradigm. The fields and data of this event type is crucial for the sync to be successful (see table below). |
Paradigm Session Required Fields
| Anchor | ||||
|---|---|---|---|---|
|
Field Name | Description | |||
|---|---|---|---|---|
Unit | NameCode | The | name of the unit code offers by your Institution. The same one that matches the Scheduled Units UNIT | NAME CODE record in Paradigm. MUST be the same Unit Code coded in Paradigm.  |
Unit Name | The name of the unit code offers by your Institution. The same one that matches the Scheduled Units UNIT CODE NAME record in Paradigm. This field should not necessarily be the same as the unit name you’ve coded in Paradigm. You can customise the unit name in Rapla if need be to help in your data entry. e.g. ‘Entertainment Since 1945’ in Paradigm and ‘Entertainment Since 1945 Group 1’ in Rapla to emphasise grouping. | |||
Session Type | (Subject to each institution) to define your session type (e.g. class, tutorial, lecture) | |||
Campus | Your Business or Institution’s Name or a specific location of one of your branches if you have multiple campuses. (Subject to each institution) to define your campus (e.g. Melbourne, Sydney). Should match the Provider record in Paradigm where the scheduled unit/s to be imported are/is under. | |||
Delivery Mode | On campus/Online/Weekends/Intensive/Others NOTE
| synchronise
| ||
Minimum Participants | The minimum number of participants for running the session (e.g. 5) | |||
Maximum Participants | The maximum number of participants for running the session | |||
Faculty/Department | (Subject to each institution) to define their faculty/department (e.g. Faculty of Art, etc.) | |||
Refer to the Advanced section: Session Group and Session Class for more details on the two fields below: | ||||
Session Group ID (Group number) | A group of sessions from which a selection is made during the enrolment (it is an enrolment choice). | |||
Session Seq ID (Class number) | A set of students who attend the same session together under one scheduled unit (Lecture). | |||
Workflow
NOTE
Both admin and non-admin user privileges are able to create events in Rapla. Only admin users can edit events created by other users.
| Note |
|---|
BE ADVISED The 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. |
How to create a single event on Rapla
| Anchor | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
In the below instance, it is an example of creating a new Event (Paradigm Session). Note that there are three sections involved to successfully create a Paradigm Session event type:
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
Scenario 1: Creating Events while Managing Resources Conflicts
While you follow the above steps of creating events/appointments, when you reach to the bottom section - Resource Allocations section. Rapla tells you the available resources by having green icons in front of them and the green texts under the Selectable on column that says “Every appointment”. The red cross icon means that that resource has been taken already in another event. So you should try to avoid allocating it again. Example 1  Example 2  You can still override the conflict and successfully create the event, however, you will be prompted by an error message (as shown in the sample warning message below),  and the Conflicts Configuration Folder on the left side menus will remind you of the number of conflicts you’ve created.  |
| Expand | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
Scenario 2: Creating Repeating Events with Exceptions
NOTE: The Exceptions button will only appear if you make a session into a repeating event by clicking on Weekly, Daily, Monthly, or Yearly from the options.
|
| Expand | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||
Scenario 3: Creating Repeating Events Along with a One-Off Event
 After clicking the New button, a copy of the same event will be added below, coded with another colour to avoid confusion. This will serve as your Appointment 2. 
 You can change it by clicking the 'Every appointment' button. It opens up more options to each appointment (as shown in the screenshot below). Select the appropriate Appointment number you want each of the Resources to be allocated to (the resources have been colour coded Appointment 1 as yellow and Appointment 2 as purple). 
 |