LogoLogo
HomeNewsletterSupportKnowledge Base
Rapla Knowledge Base
Rapla Knowledge Base
  • Rapla
  • 📘Terminology
  • 🌟Get Started
    • Install the App
    • Navigate the Interface
      • Section 1: Side Menus
        • Select a Side Menu
        • Conflicts Menu
      • Section 2: Top Menu Bar
        • Switch Account View
        • Apply Filters
        • Edit Preferences
      • Section 3: Main Calendar View
        • Calendar Types
        • Customise the Calendar Space
    • Add New Users
    • Add New Resources
      • Facility
      • Staff
      • Equipment
    • Create Time Periods
  • 🗓️Create Events
    • Choose an Event Type
      • Paradigm Session
      • Generic Meeting
      • Generic Event
      • Student Booking
    • Repeat Events
    • Use Multiple Appointments
      • Delete Appointments
      • Convert to Single Events
    • Add Exception Dates
    • Allocate Resources
  • 🕚Example Events
    • Session Group and Class
    • Scenarios
      • ▫️Scenario 1
      • ▫️Scenario 2
      • ▫️Scenario 3
      • ▫️Scenario 4
      • ▫️Scenario 5
  • 🛑Resolve Conflicts
    • Identify Conflicts
    • Disable Conflict Checking
  • 🔀Synchronise with Paradigm
    • Prepare Scheduled Unit Records
    • Prepare Rapla Events
    • Trigger Import
    • Troubleshoot Import Errors
    • Validate Imported Data
    • Change Event
      • Impact: NONE Change (1)
      • Impact: NONE Change (2)
      • Impact: NONE Change (3)
      • Impact: NONE Change (4)
      • Impact: NONE Change (5)
      • Impact: LOW Change (1)
      • Impact: LOW Change (2)
      • Impact: LOW Change (3)
      • Impact: LOW Change (4)
      • Impact: LOW Change (5)
      • Impact: LOW Change (6)
      • Impact: LOW Change (7)
      • Impact: HIGH Change (1)
  • ⚙️Advanced Configuration
    • Publish HTML Calendar Views
    • Manage User Accounts
      • Change a User Permission Level
      • Archive Inactive User Accounts
    • Add New Resource or Event Type
    • Colour Code Resources
    • Change Events Name Format
    • Change Data Schema
      • Make Fields Visible
      • Hide Fields
      • Add New Fields
      • Change Field Options
  • ❓Support
    • Online Helpdesk
    • Silverband Slack workspace
    • Phone Numbers
Powered by GitBook
On this page
  • Overview
  • Data Entry Notes
  • Workflow
  • Section 1: Event Type Fields
  • Section 2: Appointments
  • Section 3: Allocations
  1. Create Events
  2. Choose an Event Type

Paradigm Session

This page will discuss the requirements when creating a Paradigm Session event type and the instructions on how to add in Rapla.

PreviousChoose an Event TypeNextGeneric Meeting

Last updated 2 years ago

Overview

Paradigm Session is one of the types of events you can add to be managed in Rapla. By default, you have four event types: Paradigm Session, Generic Meeting, Generic Event, and Student Booking. if you want to customise this section and if you want to add more event types as your business requirements change. Alternatively, refer to the section.

This knowledge article will guide you with the basics of creating sessions or events in Rapla, and the possible functionalities you can use which could be relevant to your business or institution (Exceptions, Appointments, – which will be discussed ), and how to deal with conflicts.

Data Entry Notes

Before you add sessions, make sure that the following are true to your current Paradigm records:

  • Scheduled Units - all sessions you will plan to add in Rapla must have the Scheduled Units record equivalent created in Paradigm. The following fields: Unit Code, Campus, and Delivery Mode, are important to match your records in Paradigm when doing the .

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

WARNING:

Doing a resync to your sessions can have implications on your previously imported data. Learn more about the level of impact your changes can do when you do a resync of your sessions to Paradigm in this article: .

We would highly recommend that you only import your sessions once everything is finalised.

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.

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.

  1. Select the Date and the Time Period where you want your event to fall from the Top Menu Bar. The Main Calendar View will change accordingly.

  2. Use the left mouse (drag and drop) to mark the time duration, against the Day column for the specific appointment you want to. The marked rows are highlighted in pale blue (as below).

3. Right-click on the highlighted rows (selected time), a new context menu appears, then select the Paradigm Session event type.

4. A New Event window will appear. Note that there are three sections involved to successfully create a Paradigm Session event type:

Section 1: Event Type Fields

Fill out these fields which are critical for the integration between Rapla and Paradigm: Unit Codes (E.g. FIT9130), Unit Name, Campus (if applicable), Delivery mode, Department. Refer to the table below for the description of each field.

Field Name
Description

Unit Code

The unit code offers by your Institution. The same one that matches the Scheduled Units UNIT CODE record in Paradigm.

Unit Name

The name of the unit offers by your Institution. The same one that matches Scheduled Units UNIT 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: Make sure that there is a matching recorded scheduled unit in Paradigm with the same delivery mode as set in Rapla.

If a unit has one or more delivery modes, create a new scheduled unit for each delivery mode in Paradigm before you attempt to sync the sessions.

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

Session Group and Session Class

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

Section 2: Appointments

Section 3: Allocations

Allocate your resources here needed for the event. Add the resources from the left-hand side to the right section by either double-clicking or clicking on the resource and clicking the Add button. Resources with a red x mark on them will create conflict if you will select them. Refer to the workflow link below for the details on allocating resources.

5. After filling out all the necessary information for your event, click the Save button to add your Paradigm session in Rapla.

MUST be the same Unit Code coded in Paradigm.

These two fields are applicable if you offer options for your sessions for the students to choose from upon enrolment, e.g. morning or afternoon lecture sessions, etc. Refer to when using these fields

Fill out the start and end date, and select whether it is a single event or a recurring one. For recurring events, you can exclude public holidays or semester breaks if applicable by . You can also add two or more appointments with the same event details as necessary and required. Refer to the workflows below.

🗓️
Raise a ticket
Advanced Configuration
Groups and Class
here
sync
Change Event
adding exceptions
Repeat Events
Use Multiple Appointments
Add Exception Dates
Convert to Single Events
Allocate Resources
Example Events