FAQ: Packaged Content

Which package formats do Workday support?: Version
Release Date
Widely Used
Works Cross-Domain

AICC HACP
Feb. 1998
Yes
Yes

SCORM 1.2
Oct. 2001
Yes
No

SCORM 2004 (V2-V4)
Jul. 2004 - Mar. 2009
Yes
No

Version	Release Date	Widely Used	Works Cross-Domain
AICC HACP	Feb. 1998	Yes	Yes
SCORM 1.2	Oct. 2001	Yes	No
SCORM 2004 (V2-V4)	Jul. 2004 - Mar. 2009	Yes	No

What is the maximum file size limit for packaged content?: 4 GB.
Why am I receiving the error message: Processing failed for this media item?: If the item is a Lynda.com AICC package, the packaged content could be nested outside of the root folder. Manually unzip the package and nest the actual SCORM or AICC file in the zipped folder.

How reliable are packaged content completions and updates in Workday?: See: Packaged Content Reliability in Workday Learning.

How can I troubleshoot SCORM-related errors?: See: Packaged Content.

How can I report on SCORM content scores?: You can select the
Provide Course Grade
check box on a SCORM lesson and create a custom report against learning enrollments for score and grade. If replay is allowed on a SCORM lesson, learners can replay the lesson to improve their score. If replaying of a SCORM lesson isn’t allowed, learners must create a new enrollment, and you can report on the latest enrollments to check the most recent score.

Why am I receiving the error message when I resume my SCORM 2004 (2nd and 3rd Editions): You failed this packaged content lesson?: This is expected behavior of SCORM 2004 (2nd and 3rd Editions). Rules have been corrected for SCORM 2004 (4th Edition). You have 2 options to fix this issue:
Republish your package as SCORM 2004 (4th Edition) if you've access to the authoring tool.
Alter the manifest file to override the default rollup rules. See: Packaged Content Tracking Troubleshooting.

How are completion statuses for Packaged Content, Lessons, and Courses determined?: Packaged Content: Completion status for packaged content is dependent on the logic built into the package by its author. Workday is reliant on receiving completion status information from the package.
Lessons: Completion status for lessons is dependent on the packaged content completion status. Lesson status is set to Not Started
before content is launched. When packaged content is launched, and before it’s complete, status sets to In Progress
in most cases. We mark both package and corresponding lesson as Completed
when the package sends completion status to Workday.

Courses: Completion status for learning courses is based on the logic for the course set by a learning administrator in Workday. Courses in Workday require all lessons that are required learning content to be complete.

What impact does the Enable Completion Without Exit functionality have on completion status?: Completion status for packaged content is determined by the logic built into the package by its author. You can configure the package to send completion status at any point during user consumption or upon user exit. Regardless of when the package sends the completion status to Workday, lesson completion status updates when the learner exits the course as a current default with interaction reporting enabled.
Enable Completion Without Exit
functionality updates this process so that lesson completion status is immediately marked in Workday as soon as completion status for packaged content is received.
For highest reliability, Workday recommends that the tracking logic in your packaged content send completion status as early as makes logical sense. See: Completion Without Exit Tracking Logic.

How does the Enhanced Tracking Completion logic work?: Enhanced Tracking Completion (ETC) is designed to recover the tracking details of learners that might have completed a course, but aren’t marked as Completed
or Passed
because the information was lost due to network issues or flaws in the SCORM standard. ETC is enabled for all Workday tenants by default. See: Enhanced Tracking Completion Recovery Logic.

How does the Align Workday and Packaged Content functionality work?: When a learner launches a piece of packaged content, that course opens in a separate pop-up window. Workday generates a separate session for the packaged content in order to track the learner's progress and course completion, which is independent from the underlying Workday session. The packaged content session refreshes by specific activity within the packaged content, such as progress, tracking, or bookmarking updates. In the case of SCORM content, this includes any updates in a RecordResults.jsp request, or in the case of AICC, a ProcessAiccRequest.jsp request. When you enable this functionality, the length of the packaged content session aligns to the length of the Workday session. Both remain active until:
Learners exit the course and the pop-up window closes.
Or, an inactivity threshold of 4 hours is reached. If no activity requests are received within a 4 hour period, the packaged content session expires and no further updates will be processed between the packaged content and Workday.
Or, a maximum extension time of 18 hours is reached for SCORM or AICC courses hosted inside Workday. For AICC courses hosted outside of Workday, the maximum extension time is 4 hours. If the package continues to send activity requests, the packaged content session is extended for up to 18 hours or 4 hours, respectively. After 18 hours or 4 hours, respectively, the packaged content session expires and no further updates are processed between the packaged content and Workday.
If 1 of these criteria is met, the packaged content session expires and users see the message, “A fatal error has occurred, communication with the server has been lost.” From that moment the Workday session resumes to the default session timeout you've configured.
It’s important to note that session inactivity isn't solely determined by user interactions within the packaged content. In Workday, session expiration is also influenced by automated system actions wherein the package content itself can autonomously send requests and therefore reflate the session to a maximum of 18 hours. This means that the session may not expire even if the user isn't actively engaging with the packaged content. Such non-user interactions are dependent on how the package itself is created. Examples include checks to see if the state has changed, or if the scores have changed. This feature is supported by web browsers and mobile web browsers only. User settings (e.g. extensions, storage/cookie settings) can modify the behavior of the mobile web browser to a certain extent. Also, by default, when the Mobile web browser is in the background (receiving a phone call, locking the phone, switching to a different application etc), the operating system suspends most of the Workday application activity and only specifically allowed applications are given extended time to perform additional functions, resulting in the Workday session to timeout.