Last updated on MAY 30, 2017
Applies to:Oracle Communications Calendar Server - Version 8.0.0 and later
Information in this document applies to any platform.
Consider a Calendar Server setup comprising Oracle Communications Calendar Server 220.127.116.11.0
One would notice that the partstat information gets effectively cloned/pre-populated by organizer using Lightning.
Consider following accounts hosted on a single system.
1) Organizer, 'test_org' using Lightning
2) Attendee, 'test_attendee' using Oracle Communications Convergence
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).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms