Skip Headers

Oracle Common Application Calendar Implementation Guide
Release 12.1
Part Number E13405-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Implementing the HTML Calendar

This chapter covers the following topics:

Creating or Changing a Calendar Administrator

The Calendar Administrator, typically the system administrator or workflow administrator, has the privilege to grant approval or rejection to new group and public calendar requests. When new group or public calendar requests are generated, the Calendar Administrator receives workflow notifications for approval. Therefore, the user who becomes the Calendar Administrator must exist in Oracle Human Resource Management System (HRMS) as an employee resource.

Use the following procedures to create a Calendar Administrator:

  1. Assigning Appropriate Responsibilities:

After identifying an employee resource to become a Calendar Administrator, implementors or system administrators must assign appropriate responsibilities to the employee. In order to receive notifications and create calendar general users, the Calendar Administrator must have the following responsibilities:

After creating the Calendar Administrator, implementors must set the "JTF HTML Calendar: Administrator" profile option to the person who will be the Calendar Administrator. This grants the profile option to the Calendar Administrator, so that she or he can grant approval for new group and public calendar requests.

Additionally, if the standalone HTML Calendar module is used as default application and responsibility after signing on, then the following profile options also need to be assigned to the Calendar Administrator:

Changing a Calendar Administrator

HTML Calendar allows only one Calendar Administrator in the system to be responsible for any new group or public calendar requests; therefore, in the case of the absence of the Calendar Administrator, the Calendar Administrator or whoever has the JTF_CALENDAR_ADMIN role can perform the update by changing the name in the Calendar Administration window.

The JTF_CALENDAR_ADMIN role can be assigned through the System Administrator Console by the system administrator. A user without this role attempting to access the Calendar Administration window will see an error message saying that "You don't have sufficient privileges to view this page."

Once you update the Calendar Administrator, the JTF_CALENDAR_ADMIN role is automatically assigned to the new Calendar Administrator, and is revoked from the old Calendar Administrator. Therefore, the new Calendar Administrator can get access to the Calendar Administration window while the old Calendar Administrator cannot. All the new group calendar requests should be sent to the new Calendar Administrator through workflow notifications.

Assign JTF_CALENDAR_ADMIN Role to a User

To grant the JTF_CALENDAR_ADMIN role to a user, log in to the System Administrator Console as a system administrator. Select Users tab > Registration subtab > User Maintenance. Query up the user name and then click the Roles button to access the User-Role Mapping window. Select the JTF_CALENDAR_ADMIN role from the Available Roles block to move the role to the Assigned Roles block. Click the Update button to complete the change. The user will have access to the Calendar Administration window.

Implementing Calendar Events

In addition to scheduled appointments and tasks, HTML Calendar provides the ability to allow users to view calendar events, such as campaigns, on their calendar views.

In order to use this functionality, the integrated applications have to perform the following tasks:

  1. Identify resource groups to which they would like to publish events and add CALENDAR_ITEMS usage to the groups.

  2. Make sure that business objects (known as events in calendar) that are published are valid JTF_OBJECTS with all the following metadata defined:

  3. Populate the JTF_CAL_ITEMS_B table using the JTF_CAL_ITEMS_PUB API.

In order to view the calendar events in the personal calendars, calendar users must also meet the following conditions:

This feature will work only when integrated applications implement the functionality and follow the required steps.

Oracle Marketing is one of the applications that is currently implementing this functionality. Please refer to Oracle Marketing Implementation Guide for more details.

Subscribing to Business Events for Appointments

The Calendar module, leveraging the Oracle Workflow Business Event System, publishes business events for appointments such as creating, updating, and deleting an appointment, adding and removing an invitee, as well as responding to an invitation when the following conditions occur from APIs, application user interfaces (UIs) in HTML or the Oracle Applications Framework based modules:

Applications that contain data directly affected by these events can subscribe to them and synchronize or modify their data accordingly.

For example, if an appointment is created with invitees, this action is published or "raised" as a business event. This event can be, for example, captured to send relevant workflow notifications. If an appointment is created, updated, or deleted, this action is raised as a business event.

The Oracle Workflow Business Event System

The Oracle Workflow Business Event System is an application service that leverages the Oracle Advanced Queuing (AQ) infrastructure to communicate business events between systems. The Business Event System consists of the Event Manager, which allows you to register subscriptions to significant events, and workflow process event activities, which allow you to model business events within workflow processes.

The Event Manager contains a registry of business events, systems, named communication agents within those systems, and subscriptions indicating that an event is significant to a particular system. Events can be raised locally or received from an external system or the local system through AQ. When a local event occurs, the subscribing code is executed in the same transaction as the code that raised the event, unless the subscriptions are deferred.

See Oracle Workflow Developer's Guide for detailed information about Oracle workflow business event system, and subscriptions.

Appointment Business Events

When an appointment is created, updated or deleted, an invitee is added or removed, as well as an invitation is responded from APIs, or application user interfaces (UIs), the Calendar module will publish the following events:

Appointment Business Events
Event Name Display Name Description
oracle.apps.jtf.cac.calendar.createAppointment Appointment created. This event is published when an appointment is created.
oracle.apps.jtf.cac.calendar.updateAppointment Appointment updated. This event is published when an appointment is updated.
oracle.apps.jtf.cac.calendar.deleteAppointment Appointment deleted. This event is published when an appointment is deleted.
oracle.apps.jtf.cac.calendar.addInvitee Invitee added. This event is published when an invitee is added.
oracle.apps.jtf.cac.calendar.respondInvitation Invitee responded. This event is published when an invitee is responded.
oracle.apps.jtf.cac.calendar.removeInvitee Invitee removed. This event is published when an invitee is removed.

For each appointment business event, the owner name is Calendar, the owner tag is JTF and the default status is Enabled.

Event name represents the name of a business event that is an occurrence in an application or program that might be significant to other objects in a system or to external agents. Event name must be unique and is case-sensitive; therefore, subscribers must use Event Name for subscription purposes.

Event Attributes for Appointment and Invitee Events

The following table contains published attributes for the parameters used to create, update, and delete appointments.

Event Attributes to Create, Update, and Delete Appointments
Parameter Name Source Table Name Create Appointment Update Appointment Delete Appointment
TASK_ID JTF_TASKS_B Yes Yes Yes

The following table contains published attributes for the parameters used to add, and remove invitees, as well as respond invitation events. Yes indicates that an attribute is published and No indicates that it is not.

Event Attributes for Invitee Events
Parameter Name Source Table Name Add Invitees Respond Invitation Remove Invitees
TASK_ID JTF_TASKS_B Yes Yes Yes
ASSIGNMENT_STATUS_ID JTF_TASK_ASSIGNMENTS No Yes No
RESOURCE_ID JTF_TASK_ASSIGNMENTS Yes Yes Yes
RESOURCE_TYPE JTF_TASK_ASSIGNMENTS Yes Yes Yes

Appointment Events Subscription Guidelines

All event subscriptions must follow the guidelines mentioned in the workflow development standards. For example, any subscription cannot commit inside the rule function. This can cause unexpected behavior in the workflow or appointment APIs.

In addition, the following subscription guidelines are also used in publishing appointment business events:

Running Concurrent Program

The Rebuilding Intermedia Index for Task Names concurrent program rebuilds the intermedia index so that a user can use the Quick Find to search for new and updated appointments and tasks. Therefore, the concurrent program has to be compiled periodically in order for appointment search to work properly. For more information on running this concurrent program, see the Running the Task Manager Concurrent Program documentation in the Task Manager section.