Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  • Single Event

  • With Conflict

  • With Exceptions

  • With Appointments

Key terms and concepts

 

Info

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.

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:

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 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 Classwhich will be discussed further in the Advanced section of this documentation), and how to deal with conflicts.


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.

Student Booking

Generic Meeting

Generic Event

Paradigm Session

Paradigm Session Required Fields

Field Name

Description

Unit Name

The name of the unit offers by the Institution. The same one matches the record in Paradigm.

Unit Code

The unit code offers by the Institution. The same one matches the record in Paradigm.

Session Type

Subject to each institution to define their session type (e.g. class, tutorial, lecture)

Campus

Subject to each institution to define their campus (e.g. Melbourne, Sydney)

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)

Session Group ID (Group number)

A group of sessions from which a selection is made during the enrolment (aka. 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).

 

WorkflowWorkflow

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

RAPLA

  1. 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 below).

  1. 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 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 

  1. Click on

Save button.

 

Expand
titleScenario 1: Creating events while managing resources conflicts 

This is one of magics that Rapla 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 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
titleScenario 2: Creating repeating events with exceptions 
  1. Following the same steps as above, then find Exceptions (0) button on the middle right hand side.

  2. Click on Exceptions and a new window will pop up.

  3. Add or remove the dates (e.g. public holidays, trimester breaks)

  4. Click on Close button

  5. The Exceptions button now appears in red with a number in the bracket.

  1. You have now created a repeating event with one or more exception(s).

  1. You should follow the instruction of Scenario 2 to create a recurring events first (i.e.appointment 1)

  2. After you added the exception date for the first appointment (as per the below image: Exceptions showing 1 in red)

  3. Click on New button under the Appointments section to create a 'No repeating' event (i.e. appointment 2)

  1. At Resource Allocation section, you need to assign resources (e.g. staff, rooms) to each appointment individually.

  2. 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.

  3. Resources have been color coded and allocated to

Appointment 1 and Appointment 2.