Importing performance via webservice issue when it triggers a completion requirement (SYSDATE used)

(Doc ID 2014655.1)

Last updated on JUNE 13, 2017

Applies to:

Oracle iLearning - Version 6.0 and later
Information in this document applies to any platform.


On : 6.0 version, Learner Administration

If performance is imported via webservice against an object where a completion requirement is set, the object successfully gets updated with a completion date as defined in the xml.
Objects that get marked complete as a result of this process do not get the same completion date on their performance record, they get a completion date of the SYSDATE instead.


A performance webservice is called to set RCO ID 123 to completed with a completion date of 01-JAN-2015.
RCO ID 123 has a completion requirement set on it to mark RCO ID 345 as complete

When performance is imported against RCO ID 123 via web service, the completion date on that object gets set to 01-JAN-2015.
RCO ID 345 also gets marked complete as a result, but has a completion date of 05-FEB-2015, the day the import was done vs the same completion date as RCO ID 123, which should be 01-JAN-2015. This causes the completion dates on these completion requirements to be incorrect.

The same does not occur if you manually update performance on an object in the Admin UI, it will use the same completion date for the completion requirement objects.

Expect the completion dates on these completion requirements to be correct.
Expect the import Performance web service should pass the completed date of the parent object completion (15-Dec-2014) into ILA_CONTENT.SET_PERFORMANCE_STATUS


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms