Development program

A development program comprises at least one or more main events, which in turn may consist of several sub-events. A continuing education program is therefore a kind of "grouping" of several events. For events that are associated with the same development program, attending each individual event is mandatory in order for the main event to be regarded as settled. Main events and sub-events can also exist without an associated development program (see also graphics below).

Create a new development program

The following procedure is recommended for setting up a development program:

• Define the name of the training program in Selection lists (List 88) under the events section.
• Create an event (if it does not already exist)
• Assignment an event to a continuing education program
• Creating further main events / sub-events within an event, which are assigned to a development program.
• Assigning employees to the development program via Employee file or directly via the tab "Participants" in the event

If someone attends the sub-event of a main event which is assigned to a development program (only the main event itself), then the other events of this main event are regarded as being settled!

Main events are in the proper sense not physical events but rather the grouping of sub-events into a "greater whole".

Working with the development program

Fig. 1: Search link on employee profile for assigning a development program

All events, which have been assigned to the same development program as the respective employees, are displayed with the help of a special search link on the left border next to the events of an employee (/Employment/Current/ID/Profile/Courses/Profile).

This search link appears only if a development program has been assigned for the employee.

Fig. 2: Search link in the event for assigning a development program

Fig. 3: Assign a participant to a sub-event

Instructions for the Administrator:

• If you are working with development programs, the development program filter must be displayed on the page for an employee's events. Otherwise this search link on the left hand side may not work properly.

In the configuration mode, you see the search link block twice!

• In the upper block only non-event administrators see all the events, which:

1. belonged to one of the development programs of the employee and the employee is not yet registered as a participant (even in a sub-event)
2. have the end date is in the past
3. have been published as advertisements (for my organization unit, if limited)
4. and are active

• In the lower block only event administrators see all the events, which belong to one of the development programs of the employee and the employee is not registered as a participant (not even in a sub-event).

The same applies to the events. Whenever an event becomes part of a development program and this setting is assigned to it, a search link of the participants’ overview appears on the left border, which shows the employees who have not yet registered for this event or one of its sub-events.

You can then do the missing registrations for both the employee and the event.

• An event administrator can also register for events that have not been advertised.
• In contrast, an event user (manager) and the employee him/herself can only register for advertised events. When registering, one can also register for sub-events.

Tips for event administrators:

If you wish to make the registrations not on the event itself but on one of its sub-events, you have the option of a multiple action "Assign people to a sub-event of this event" on the people overview "Add participants" (/Courses/ID/Participants/Assign). You can even navigate further down into the sub-events’ structure by clicking on "Number of partial events" in the table.

Logic in structured development programs

A development program is often composed of various events of which some are interchangeable events (appointments) where, e.g., it is sufficient to attend one event to complete the development program. This makes it possible to develop structured programs. There are just 2 rules to bear in mind.

• Once you select an event as being part of the development program of "Program xy", all events must be attended (e.g. date) in order to mark the main event as being successfully completed. If you want like to offer, for example, different languages for an event, however, you create a main event with sub-events in the respective different languages ​and mark the sub-events as not being part of the xy development program. Here, too, If this event is also to have sub-events, participating in one of these sub-events is enough for the main event to qualify as being settled. If there is no sub-event, the event itself must be attended as the sole remaining option.
• The maximum depth of sub-events is 4 levels.

In this way you can design development programs (mandatory event programs) that include both interchangeable components (e.g. dates) and obligatory components.

Graphic analysis

To demonstrate the complexity of the procedure visually, the following graphics are intended to aid understanding:

Fig. 4: Response for a development construct

Explanation of the adjacent figure 4

All events are assigned to the development program A (assignment of the main event 1 to the development program is optional possible, but does not change the procedure of the interaction). Main Event 1 comprises three sub-events. Sub-event 1.3 in turn has two sub-events, and is therefore at the same time also the main event of 1.3.1 and 1.3.2. All events must be attended in order for the main event to be regarded as being settled.

Fig. 5: None of the events is assigned to a development program.

Explanation of the adjacent figure 5
No event is associated with a / the development program. Sub-event 2.2 in turn is the main event of 2.2.1 and 2.2.2. If a participant attended only event 2.2.1 or 2.1, the main event 2 is deemed to be already settled.

The following example shows specifically the procedure when searching for events.

Explanation of the figure 6 below

The events A to G have all been created separately. A, B, C and D are assigned to the same development program. A is a major event which includes sub-events B, C and D. D in turn includes the sub-events E, F and G (of which D is the main event). The search for events proceeds, for an employee who is assigned this development program, according to the following procedures: Employee is not registered anywhere: In the search, A, B, C and D appear because they are assigned to the development program. Employee is already registered for sub-event G: The results of the search are only B and C, since A and D are already marked as being attended due to registration for G (since it does not belong to the development program). E, F and G are assigned to the development program as well, the employee is registered for G: The search results give B, C, E and F. Regardless of the search for events, the following procedure applies: Date 1 (E) was attended: Mouth-to-mouth (D) is deemed to be completely settled because the sub-events E, F and G are not assigned to the development program and therefore the visit to one sub-event is sufficient to highlight the main event "mouth-to-mouth" as completed, i.e. only B and C still need to be attended.

Fig. 6: Event construct with development components

Application examples:

• Identical event is offered in different languages:
  

An event is to be held in different languages, but each employee can select the language in which he wants to attend it. A breakdown in the main event, for example, with the name "security training" with the identical sub-events which are offered in German, French and English is particularly optimal here. When attending one of these sub-events, the main event is automatically marked as being settled.

⇒ Refer to figure 7

• Training program with courses building on each other in the identical language:
  

The visit of all courses is mandatory, therefore, a development program should be created with main event and sub-events.

⇒ Refer to figure 8

• Development program with offer of individual components in different languages:
  

Create a main event with sub-events (different modules of the program which are all associated with the same development program). At the same time, these sub-events have turn have sub-events in different languages, but which are then not assigned to the development program. If now a sub-event is attended in any language offered, the single module is considered to be settled, the remaining modules are still to be attended however.

⇒ Refer to figure 9

Fig. 7: Event is offered in different languages

Fig. 8: Advanced training program with sub-events whose attendance is mandatory

Fig. 9: Event with mandatory components in each of the various languages

Help with repeated development programs

• Certificates with an expiry date: After participating in an event you can issue the participants with a certificate . If you have repeat development programs the employee or the manager him/herself should decide whether a certificate needs to be renewed. Advanced searches for expiring certificates help with this.
• Reminders: Setting reminders is an effective method of attending certain development events in time. Optionally, if you define an appropriate reminder, the Umantis solution sends you an e-mail and a reminder in time before a certificate expires.
• Copying development programs: If a development program takes place again or if it should have the same set-up as an existing development program, the function "Copy event" simplifies the procedure considerably.