Pre-populating Partstat Information On Attendee For New Event Cloned By Lightning (Doc ID 2270627.1)

Last updated on MAY 05, 2021

Applies to:

Symptoms

Consider a Calendar Server setup comprising Oracle Communications Calendar Server 8.0.0.1.0

One would notice that the partstat information gets effectively cloned/pre-populated by organizer using Lightning.

Sample Scenario:

Consider following accounts hosted on a single system.

1) Organizer, 'test_org' using Lightning

2) Attendee, 'test_attendee' using Oracle Communications Convergence


Preparation

As 'test_org' user: Create an event and invite 'test_attendee'
As 'test_attendee' user: Accept the event invite sent by 'test_org'
As 'test_org' user: Make sure, there exists a sync state, i.e see partstat accepted (wait a sync cycle or enforce)

Derive new event

As 'test_org' user:

Clone the event to set another date (select Event; hit 'ctrl+c' for copy; select another day; hit 'ctrl+v' for paste)
Notice that the time of the event is not changed.
Notice the 'partstat=accepted' reported for attendee.

3) check outcome
as Attendee: refresh view -> new instance should be visible
observe cloned event already has 'partstat=accepted'

Below is the sample organizer's copy of the cloned event ( on 2017-04-05 while src is on 2017-04-04).

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.