WFC813 Flash To HTML MigrationGuide

Flash-to-HTML Migration Guide
A guide to setting up HTML navigators
Kronos® Workforce Central® suite version 8.1.3

The information in this document is subject to change without notice and should not be construed as a commitment
by Kronos Incorporated. Kronos Incorporated assumes no responsibility for any errors that may appear in this
manual. This document or any part thereof may not be reproduced in any form without the written permission of
Kronos Incorporated. © 2019 Kronos Incorporated. All rights reserved.
Altitude, Altitude Dream, Altitude Pairing, Altitude PBS, CardSaver, Gatekeeper, Gatekeeper Central, Keep.Trac,
Kronos, Kronos InTouch, Kronos Touch ID, the Kronos logo, Kronos Workforce Ready, My Genies, OptiLink,
ShiftLogic, ShopTrac, Timekeeper Central, TimeLink, Unicru, Visionware, Workforce Accruals, Workforce Central,
Workforce Genie, and Workforce TeleTime are registered trademarks of Kronos Incorporated or a related company.
ACA Manager, Altitude BLISS, Altitude Insight, Altitude MPP, Altitude MPPXpress, Altitude Rostering, Altitude VBS,
CMS, Comm.Mgr, CommLink, DKC/Datalink, eDiagnostics, FasTrack, Hireport, HR and Payroll Answerforce,
HyperFind, iBid, Kronos 4500, Kronos 4500 Touch ID, Kronos 4510, Kronos Acquisition, Kronos ByDemand,
Kronos e-Central, Kronos Efficient, Kronos Enterprise Archive, Kronos Essentials, Kronos for Dining Accelerated,
Kronos for Retail Accelerated, Kronos KnowledgePass, Kronos Paragon, Kronos TechKnowledgy, KronosWorks,
KVC ByDemand, KVC OnDemand, Labor Plus, MedSched, MPPXpress, Overall Labor Effectiveness, Schedule
Assistant, Smart Scheduler, Smart View, StaffEasy, Start Quality, Start WIP, Starter Series, StartLabor, Stromberg,
Timekeeper Decisions, Timekeeper Web, VisionPlus, WebStaff, webTA, webTA Mobile, Winstar Elite, WIP Plus,
Workforce Absence Manager, Workforce Acquisition, Workforce Activities, Workforce Analytics, Workforce
Attendance, Workforce Auditor, Workforce Budgeting, Workforce Central Portal, Workforce Connect, Workforce
Device Manager, Workforce Dimensions, Workforce Employee, Workforce ESP, Workforce Forecast Manager,
Workforce HR, Workforce Innovation That Works, Workforce Institute, Workforce Integration Manager, Workforce
IntegrityScreen, Workforce Leave, Workforce Manager, Workforce Mobile, Workforce MobileTime, Workforce
Operations Planner, Workforce Payroll, Workforce Record Manager, Workforce Recruiter, Workforce Scheduler,
Workforce Scheduler with Optimization, Workforce Selection, Workforce Smart Scheduler, Workforce Sourcing
Analytics, Workforce Tablet, Workforce Tablet Analytics, Workforce Talent Acquisition, Workforce Task
Management, Workforce Tax Filing, Workforce TeleStaff, Workforce TeleTime IP, Workforce Timekeeper, Workforce
View, and Workforce Worksheet are trademarks of Kronos Incorporated or a related company.
For a complete list of Kronos trademarks, please visit the "trademarks" page at www.kronos.com. The source code
for Equinox is available for free download at www.eclipse.org. All other trademarks or registered trademarks used
herein are the property of their respective owners and are used for identification purposes only. All specifications
are subject to change.
When using and applying the information generated by Kronos products, customers should ensure that they comply
with the applicable requirements of all applicable law, including federal and state law, such as the Fair Labor
Standards Act. Nothing in this Guide shall be construed as an assurance or guaranty that Kronos products comply
with any such laws.
Published by Kronos Incorporated

900 Chelmsford St, Lowell, MA 01851 USA
Phone: 978-250-9800, Fax: 978-367-5900
Kronos Incorporated Global Support: 1-800-394-HELP (1-800-394-4357)
For links to information about international subsidiaries of Kronos Incorporated, go to

http://www.kronos.com
Document Revision History
Document Revision Release Date
A December 2018
B January 2019
C February 2019
Contents
Overview
Migration tools .............................................................................................. 6
Migration paths .............................................................................................. 7
Widgets not migrated .................................................................................... 8
Widgets remaining on Flash ................................................................... 8
Widgets whose functionality can be added to HTML widget ................ 9
Process Manager templates that use Request Manager ........................ 10
Step 1: Apply Service Release v8.1.3
Step 2: Prepare to Migrate

Task 1: Run the Navigator Configuration Report utility ............................. 16
Run the utility from the UI .................................................................... 16
Run the utility from the command line ................................................. 19
Task 2: Review the navigator reports .......................................................... 21
Summary report .................................................................................... 21
Detail report .......................................................................................... 22
Unsupported Request Types report ....................................................... 26
Step 3: Run the Migration Event

Migration event overview ............................................................................ 30
Replace Flash-dependent components .................................................. 30
Update Display Profiles ........................................................................ 32
Log on to navigator ............................................................................... 33
Migrate Flash-dependent components to HTML ........................................ 34
Task 1: Back up your Flash-dependent database .................................. 35
Task 2: Run the migration event ........................................................... 35
Task 3: Review the migration logs ....................................................... 37
Task 4: Verify Navigator Profile for SuperUser ................................... 46
Task 5: Review and test the migration .................................................. 47
Contents
Step 4: Move from Test to Production Environment
Appendix A: v8.1.3 Widget Migration Summary
Appendix B: Roll Back Flash-to-HTML Migration Changes
Appendix C: Configure v8.1.3 Online Help
Appendix D: Examples
2
Overview
Workforce Central navigators have historically required browser support for

Adobe Media Flash player to provide a web-based interactive user experience.
Over the years, open web standards such as HTML, which enable developers to
embed content directly on to web pages, have been replacing Flash and modern
browsers are now discontinuing Flash support.
With Workforce Central v8.1.3, Kronos is providing migration tools to move to a
Flash-free environment. These migration tools enable you to replace Flash-
dependent components with new HTML equivalents.
Before you migrate, however, be aware of the following important considerations:
• If you use Process Manager templates that depend on Request Manager,
do not migrate to HTML. Even if you are not sure if you have Process
Manager templates that use Request Manager, do not proceed with the
HTML migration. Because of possible user customizations, the migration
report may not identify all of these templates. Process Manager templates in
HTML Request Manager will be supported in a future release. For more
information, see “Process Manager templates that use Request Manager” on
page 10.
• The Staffing widget and Task Management widgets still require Flash player,
but all other components now have HTML equivalents. With Workforce
Central v8.1.3, Flash-dependent navigators can be assigned to people who use
the Staffing and Task Management widgets and HTML navigators can be
assigned to people who do not use these widgets. This should satisfy the
requirements for most Workforce Central v8.1.3 users to move to a Flash-free
environment.
Note: In earlier versions of Workforce Central, navigators included a combination

of Flash, HTML, and Java applet components. Although these components
continue to be supported in the current Flash navigator, best practices are to
replace Java applet and Flash components. Workforce Central v8.0.11 provided
Overview
replacements for Java applet components as described in the Navigator

Implementation Guide and v8.1.3 is providing replacements for most Flash
components as described in this document.
An important requirement for v8.1.3 users is that Flash-dependent components

and v8.1.3 HTML components cannot be included in the same navigator, which
means that:
• HTML navigators can only contain HTML workspaces, widgets, and widget
parts. They cannot contain Flash or Java applet content.
• Flash-dependent navigators cannot include any of the new v8.1.3 HTML
components. They can only contain workspaces, widgets, and widget parts
that were created before v8.1.3.
Included in Flash
Component Type Navigators Included in HTML Navigators
Flash-dependent Yes No
Pre-v8.1.3 HTML Yes Yes
v8.1.3 HTML No Yes
Java applet Yes No, but will be replaced with an HTML
placeholder
Because of this requirement, both HTML and Flash navigators are available
within the Workforce Central v8.1.3 environment until the Flash-removal process
is completed. If a navigator contains any components that do not have an HTML
equivalent (such as the Staffing or Task Management widgets), the navigator
continues to depend on Flash and cannot be migrated to HTML.
This means that people in your organization will be assigned either a Flash-
dependent navigator or an HTML navigator, depending on the widgets that they
use, for example:
• People who do not use the Staffing widget or Task Management widgets can
use HTML navigators.
• People who use the Staffing widget or Task Management widgets, must
continue to use Flash-dependent navigators.
4
Flash and HTML components must be managed separately. If you change an
HTML component, the change is not reflected in the Flash component and if you
change a Flash component, the change is not reflected in the HTML component.
Important: If anyone in your organization uses Process Manager requests that

depend on Request Manager do not proceed with the migration.
This document describes how to migrate your Flash navigator components to new
HTML components.
• Step 1: “Apply Service Release v8.1.3” on page 13
• Step 2: “Prepare to Migrate” on page 15
• Step 3: “Run the Migration Event” on page 29
• Step 4: “Move from Test to Production Environment” on page 49
Notes:
• Steps 1, 2, and 3 are typically done in a test environment. When you are
totally satisfied with the results of the migration within your test environment,
you can update your production environment.
• Step 2 does not require service release v8.1.3, but a best practice is to apply
the service release and fully test it before migrating your Flash-dependent
content.
• Best practices are to back up your database at three points in the migration
process:
- Before you apply service release v8.1.3
- Before you run the migration event
- Before you move from the test to production environment
• If you use non-English languages, you must apply the v8.1.3 Language Pack
release before you migrate to the HTML Navigator.
5
Overview
Migration tools
The following tools are included with service release v8.1.3 to help you migrate to
a Flash-free experience:
• The Navigator Configuration Report utility is used before running the
migration event so you can analyze the components that will and will not be
migrated. You can run this utility before or after applying service release
v8.1.3. The reports generated by the utility can be used to identify widgets
that will not be migrated but whose functionality can be incorporated in
HTML widgets.
Note:
• The Navigator Configuration Report utility also identifies Java applets.
See the Navigator Implementation Guide for information about removing
Java applets.
• Because of possible user customizations, the Navigator Configuration
Report utility may not identify all of the non-migratable Process Manager
templates used in HTML Request Manager. See “Process Manager
templates that use Request Manager” on page 10 for more information.
• A migration event called Migrate Navigators from Flash to HTML is

delivered by the service release v8.1.3 installer. After you apply the service
release, you can run it from Event Manager. A rollback event called Roll
Back Navigators from HTML to Flash is also delivered in case you need to
return to a Flash environment.
6
Migration paths
Migration paths
The HTML migration event supports Workforce Central environments that are
currently using the following navigator configurations:
• Workforce Central v6.3.x navigator
• Workforce Central v8.1.x
Java applets are not supported in HTML navigators. Before migrating to a Flash-
free environment, Workforce Central instances running classic configurations that
use Java applets must be migrated to navigator configurations by using the
Navigator Configuration utility as described in the Navigator Implementation
Guide. If you do not remove Java applet components, the HTML migration event
replaces the Java applet component with a placeholder.
7
Overview
Widgets not migrated

Although most Flash-dependent navigator components can be migrated to HTML,
some cannot as described in the following sections:
• “Widgets remaining on Flash” on page 8
• “Widgets whose functionality can be added to HTML widget” on page 9
Widgets remaining on Flash

Navigators that contain the following components cannot be migrated to HTML.
They must remain on Flash.
Content Status
Classic Java applets The migration event replaces Java applets with a placeholder and
migrates the placeholder to HTML. You must replace Java
applets with HTML content before running the migration event.
Staffing widget Navigators that include this widget must remain on Flash.
Task Management Navigators that include Task Management widgets (Project
widgets Planning, Project List, and Project Monitoring widgets) must
remain on Flash.
Process templates that If you are using Process Manager templates that are dependent on
have a Request Request Manager, do not proceed with the HTML Migration.
Manager dependency
8
Widgets whose functionality can be added to HTML widget

The following widgets will not be migrated to HTML in v8.1.3, but the
functionality of these widgets is available elsewhere in the suite. You should
reconfigure HTML widgets to include the functionality of these Flash widgets
before running the migration event:
Flash widget Migration Recommendations
Call List widget Use the Staffing Assistant in the Schedule Planner instead of the
Call List widget.
Accruals Use the Accruals add-on in the timecard instead of the Accruals
widget.
Flash Timecard Use the HTML timecard instead of the Flash timecard.
(Employee Timecard)
Metrics widget Use the Metrics add-on in Schedule Planner instead of the
metrics widget.
Flash Scheduling Use the HTML Schedule Planner instead of the Flash Scheduling
widget widget.
Weather widget Use the Single Link widget pointing to a preferred weather site
instead of using the Weather widget.
Time-Off widget Use the functionality available in HTML Request Manager
instead of using the Time-Off widget.
9
Overview
Process Manager templates that use Request Manager

All legacy request types based on Process Manager templates that are dependent
on Request Manager or Request Transition are not yet supported in the HTML
Request Manager. Do not migrate to HTML if you use any of these templates.
This includes the templates listed in the following table.
Important background information:

The system allows you to create Process Manager templates without a category,
so if you used Request Manager or Request Transitions in a process template
without identifying the category, the Navigator Configuration Report utility will
not flag these templates as non-migratable.
Other templates that you have customized may also not be flagged. Because of
this, the following list is for guidance purposes only. Ultimately, you need to
know which templates you use in Process Manager.
10
Name Template
Request Manager Time Off Request RM_TimeOffRequest.template.xml
Request Manager Time Off Request RM_TimeOffRequest_4500.template.xml
(Kronos 4500)
Request Manager Cancel Time Off RM_CancelTimeOffRequest.template.xml
Request
Request Manager Overtime Request RM_OvertimeRequest.template.xml
Request Manager Shift Swap RM_ShiftSwap.template.xml
Request Manager Sign Up for Open RM_OpenShiftSignUp.template.xml
Shifts
Request Manager Request Open Shifts RM_RequestOpenShifts.template
Request Manager New Hire Decision/ RM_NewHireDecisionandAnnouncement.te
Announcement mplate.xml
Request Manager Employee Awards RM_EmployeeAward.template.xml
Request Manager Disciplinary Action RM_DisciplinaryAction.template.xml
Request Manager Termination RM_TerminationAnnouncement.template.
Announcement xml
Request Manager Training Registration RM_TrainingRegistration.template.xml
Request Manager Request to Cover RM_RequestToCover.template.xml
Request Manager Request to Cover RM_RequestToCoverShift.template
Shift
Request Manager Delegate RM_Admin_Delegation.template
Authority—Administration
Request Manager Delegate RM_Mgr_Delegation.template
Authority—Manager
11
Overview
12
Step 1: Apply Service Release v8.1.3
Because service release v8.1.3 includes a number of new features and issue fixes,
you should back up your database, apply service release v8.1.3, and then test it
before you migrate the Flash-dependent components to HTML.
See the Applying 8.1.x Service Releases document for more information.
Note: If you use non-English languages, you must also apply the v8.1.3 Language
Pack release before you migrate to the HTML Navigator.
Apply Service Release v8.1.3
14 Kronos Incorporated
Step 2: Prepare to Migrate
Before you run the migration event, you can run the Navigator Configuration
Report utility to identify and analyze the components that will be migrated when
you run the HTML migration event.
Note: You can run this utility one or more times, either before or after you apply
service release v8.1.3.
“Task 1: Run the Navigator Configuration Report utility” on page 16

“Task 2: Review the navigator reports” on page 21
Prepare to Migrate
Task 1: Run the Navigator Configuration Report utility
Note: The JRE 1.8 plug-in must be installed on the machine that is executing the
report.
You can run the Navigator Configuration Report utility from the UI or from the
command line.
Run the utility from the UI

1. From the Workforce Central installation kit, navigate to Flash-to-HTML
Migration Tools and select the Navigator Configuration Report Utility that
is appropriate for your operating system (Windows, AIX, or Linux).
2. Extract the zip file to any folder.
Note: Delete existing content before extracting the zip file. Back up the folder
if necessary.
3. Double-click navreport.bat (Windows) or navreport (Linux/AIX). Refer to

the README.txt file on the service pack installation kit for details on
interactive and non-interactive modes of running the tool.
The Navigator Configuration Report Utility opens.
16
4. Enter the following information:

Host Name: Enter a URL that contains the fully qualified domain name for
the application server name and instance, for example:
http://MyServer.int.mycompany.com/wfc
User Name and Password: Enter a super-access user name and password.
CSV file name: Enter the location and name of the report or use the ... button
to open the Report location box:
a. Save In: Navigate to the appropriate location.
b. File Name: Enter the name of the report with a .csv extension.
c. Files of Type: Select CSV files.
d. Click Save.
17
Prepare to Migrate
Server certificate file name: If you are using SSL, enter the name of the
server certificate. Use the ... button to navigate to the appropriate location.
Note: You need to export a copy of the certificate to the local file system
before you complete the Server certificate file name field. The process
varies with each browser, but using Chrome as an example, do the following:
1. Open Workforce Central in a Chrome browser.
2. Right-click the lock next to the URL and select Certificate (Valid).
3. Select the Details tab.
4. Click Copy to File...
5. In the Welcome to the Certificate Export Wizard page, click Next.
6. Select DER encoded binary X.509 (.CER) and click Next.
7. In the File to Export window, enter a name for the copied certificate and
click Next and then click Finish in the next window.
8. Use the path and name of the copied file in the Server certificate file
name field.
5. Click Generate Report. A message displays while the report is being

generated.
After the report is created, the Navigator Configuration Report Utility box
closes automatically.
18
Run the utility from the command line

To run the utility from a command line:
1. Open a command window and navigate to the directory of the utility.
2. Enter the following:
NavReport.jar HostName UserName Password CSVFileName
ServerCertificateFileName
where
– HostName – Fully qualified domain name of the application server and
instance
– UserName – Super-access user name
– Password – Super-access password
– CSVFileName – Location and name of the report with a .csv
extension.
Note: If you are not using SSL and do not enter a name, the report is
called NavigatorReport.csv and is created in the current directory. If you
are using SSL, you must enter a CSV file name here. This is because the
utility assumes that the fourth parameter is the CSV file name and the
fifth parameter is the server certificate file name.
– ServerCertificateFileName – Name and location of the server
certificate (for SSL implementations)
19
Prepare to Migrate
Note: You need to export a copy of the certificate to the local file system
before you complete the Server certificate file name field. The process
varies with each browser, but using Chrome as an example, do the following:
1. Open Workforce Central in a Chrome browser.
2. Right-click the lock next to the URL and select Certificate (Valid).
3. Select the Details tab.
4. Click Copy to File...
5. In the Welcome to the Certificate Export Wizard page, click Next.
6. Select DER encoded binary X.509 (.CER) and click Next.
7. In the File to Export window, enter a name for the copied certificate and
click Next and then click Finish in the next window.
8. Use the path and name of the copied file in the Server certificate file
name field.
3. Press Enter to run the utility.
20
Task 2: Review the navigator reports

The Navigator Configuration Report utility generates the following reports:
• “Summary report” on page 21
• “Detail report” on page 22
• “Unsupported Request Types report” on page 26
Summary report
The HTMLMigrationOverview.csv report is a summary report that lists each
navigator and navigator template in your environment and indicates if it is ready
for migration. If the navigator or navigator template is not ready for migration, the
Details column identifies the widget preventing the migration.
21
Prepare to Migrate
You should review the content of all these navigators in the detail report. Even if a
navigator is listed as ready for migration, it might contain some Java applet
content. The migration event will drop the Java applet content and add a
placeholder. And although navigators that are not ready for migration might
contain widgets that do not have an HTML replacement, they might contain
functionality that is available within other HTML widgets.
In either of these cases, you may want to reconfigure the content before running
the migration event.
Detail report
The detail report, which is named from your entry in Task 1, contains detailed
information about every navigator component in your system. You should use this
report to review the navigators listed in the summary report that are not ready for
migration.
• If the navigator contains the Staffing widget or Task Management widgets
(Project Planning, Project List, and Project Monitoring widgets), the
navigator continues to depend on Flash. All widgets used in the navigator
must be Flash widgets. You cannot change this.
• If the navigator contains widgets whose functionality is available within other
HTML widgets, you should consider reconfiguring these widgets before
running the migration event.
For example, the Accruals widget does not have an HTML replacement
because the Accruals add-on in the timecard provides the same functionality.
You may be able to delete the Accruals widget and configure the timecard to
accommodate your requirements. Then, if you rerun the Navigator
Configuration Report utility, the navigator will be identified as ready for
migration.
See “Widgets not migrated” on page 8 for more information.
Note: Mobile components are not migrated and are marked as “Not Applicable”
in the detail report.
22
The detail report contains the following columns:
Navigator
• Navigator Name – Lists all navigators and navigator templates used in your
environment. Names that start with 00 are templates.
• Default Workspace – Identifies the default workspace used by each
navigator or navigator template.
Workspace
• Workspace Name – Lists all workspaces and workspace templates used
within each navigator. Names that start with 00 are templates.
• Workspace Label – Identifies the label used by each workspace.
Widget
• Widget Name – Lists all widgets and widget templates used within each
workspace. Names that start with 00 are templates.
• Widget Label – Identifies the label used by each widget.
• Widget Type – Identifies the type of each widget.
• Applet(s) – Identifies whether or not the widget is a Java applet: Yes if the
widget is a Java applet and No if it is not.
• Flash – Identifies whether or not the widget is dependent on the Flash plug-
in: Yes if the widget requires Flash and No if it does not require Flash.
• HTML – A number of HTML widgets that did not rely on Flash were
delivered in earlier releases. These widgets will continue to work in Flash-free
navigators. This column identifies these widgets: Yes if the widget is a pre-
existing HTML widget and No if it is not.
• HTML Migration Notes – Indicates how the migration event will handle the
widget:
– Currently HTML – This designation includes HTML components
introduced before v8.1.3.
– Ready for HTML migration – The migration event will replace this
Flash-dependent widget with the equivalent HTML widget.
23
Prepare to Migrate
– Not ready for HTML migration – The migration event will not replace
this widget. It will continue to require Flash. Note that some widgets will
be identified as not ready for migration but you can include their
functionality in other widgets as described in “Widgets not migrated” on
page 8.
– Not Applicable – Typically, this designates Mobile navigators and related
items.
– Not Supported – Typically, this designates Java applet content, which is
not supported. The migration event will replace this widget with a
placeholder.
Note: Single Link, Quick Links, and Wizard widgets that include links that
are Java applets are marked as Ready for HTML migration. You should
review the “Link” section for details about these links.
• Notes – Indicates whether the widget is available in the Primary View or the
Secondary View, or is a Page.
Widget Part
• Widget Part Name – Lists all widgets parts and widget part templates used
within each widget. Names that start with 00 are templates.
• Widget Part Type – Identifies the type of each widget part.
• Applet – Identifies whether or not the widget part is a Java applet: Yes if the
widget part is a Java applet and No if it is not.
• Flash – Identifies whether or not the widget part is dependent on the Flash
plug-in: Yes if the widget part requires Flash and No if it does not.
• HTML – A number of HTML widget parts that did not rely on Flash were
delivered in earlier releases. These widget parts will continue to work in
Flash-free navigators. This column identifies these widget parts: Yes if the
widget part is a pre-existing HTML widget part and No if it is not.
widget part:
24
Flash-dependent widget part with the equivalent HTML widget.
this widget part. It will continue to require Flash.
items.
not supported. The migration event will replace this widget part with a
placeholder.
Link
This area lists the links used within Single Link, Quick Links, and Wizard
widgets.
Note: If there is a Staffing widget in a wizard, the migration event drops it from
the wizard and continues to migrate to HTML.
• Link Name – Lists any links used in the workspace.

• Applet – Identifies whether or not the link is a Java applet: Yes if the link is a
Java applet and No if it is not.
link:
Flash-dependent link with the equivalent HTML widget.
this link. It will continue to require Flash.
items.
not supported. The migration event will replace this widget with a
placeholder.
25
Prepare to Migrate
Unsupported Request Types report

The Unsupported Request Types report identifies request sub-types that were
created using process templates. Process templates that are uncategorized,
however, will not be identified and they may not be supported by the HTML
Request Manager.
Before you run the report, manually review all process templates that are not
categorized and assign a category where required. For example, all process
templates used by Request Manager require that the Request Manager category
be set.
Important:
All legacy request types based explicitly on Process Manager templates that
depend on Request Manager are not yet supported. Because of possible user
customizations, however, the migration report may not identify all of these
templates. This means that:
• If you use Process Manager templates that depend on Request Manager, do
not run the migration report and do not migrate to HTML.
• If you are not sure if you have Process Manager templates that use Request
Manager, do not run the migration report and do not proceed with the HTML
migration.
These Process Manager templates will be supported in HTML Request Manager
in a future release.
If no unsupported request types are identified, the report includes a row that states,
“No Unsupported Types Found.”
The Unsupported Request Types report contains the following columns:
• Request Sub Type – Name of the request sub-type
• Request Type – Name of the request type
• Template Categories – Indicates if Request Manager or Request
Transitions are used.
26
• Comments — Depending on the template category identified, the following

comments are generated:
– Request Manager template category:
Not Supported by HTML Request Manager.
– Request Transitions template category:
Review if there are Request subtypes using request transitions that
includes this template. If so, it is not supported by HTML Request
Manager
For example
The following request sub-types are supported by the HTML Request Manager
widget. Any request type not on this list is not supported.
• Global Time-Off
• Work Time
• Self Schedule
• Scheduling Request To Cover
• Change Availability Request
• Scheduling Shift Swap
• Global Open Shift
27
Prepare to Migrate
28
Step 3: Run the Migration Event
The service release installer delivers a migration event that you can run from
Event Manager. When you run this event:
• All Flash-dependent components that have HTML equivalents are cloned and
renamed. User preferences within widgets are also migrated to the applicable
HTML widget.
• New Navigator Profiles that contain only HTML content are created and
users’ Display Profiles are mapped to the new HTML Navigator Profiles.
Details are provided in the following sections:
• “Migration event overview” on page 30
• “Migrate Flash-dependent components to HTML” on page 34
Run the Migration Event
Migration event overview

The Migrate Navigators from Flash to HTML event, which can be scheduled or
run immediately from Event Manager, automatically clones Flash-dependent
components, creates HTML Navigator Profiles, and updates users’ Display Profiles.
Important: The migration event must be run with no one logged in or using the
system. Because of this, consider running it during a maintenance window.
Replace Flash-dependent components

The migration event automatically clones most Flash-dependent workspaces,
widgets, and widget parts to the HTML replacements and makes the following
name changes:
• Cloned widgets, widget parts, and Navigator Profiles are renamed with an
HTML suffix. The original components retain their original name. For
example, the cloned Calendar widget is named CalendarHTML and the
Flash-dependent widget name remains Calendar.
• For workspaces and navigators, the original Flash-dependent component is
renamed with an FLX suffix. New cloned workspaces and navigators use the
original name. For example, the original Manage My Department workspace
is renamed Manage My DepartmentFLX and the cloned HTML workspace
is named Manage My Department.
Flash Component HTML Component

WidgetName WidgetNameHTML
WidgetPartName WidgetPartNameHTML
NavigatorProfileName NavigatorProfileNameHTML
WorkspaceNameFLX WorkspaceName
NavigatorNameFLX NavigatorName
Note: Navigator, workspace, widget, and widget part names as well as Navigator
Profile names cannot exceed 50 characters. Due to this limitation, the migration
event truncates the original name to 47 characters to accommodate the FLX suffix
or 46 characters to accommodate the HTML suffix.
The following details how various widgets are migrated:
Migrate to
Widget Name Replacement HTML
Widget Type (example) Name navigator?
Java applet Placeholder widget Yes
Flash widgets that have HTML equivalents
Single Link Single Link Single LinkHTML Yes
Quick Link Quick Link Quick LinkHTML Yes
Alerts Alerts AlertsHTML Yes
Wizard Approve Time Approve TimeHTML Yes
Calendar Calendar CalendarHTML Yes
Request Manager Requests RequestsHTML Yes
Timestamp Punch PunchHTML Yes
Exceptions Exceptions ExceptionsHTML Yes
Manage Navigators Manage Navigators Manage NavigatorsHTML Yes
Flash widgets that have no HTML equivalents
Call List* Call List No replacement No
Task Management: Task Management No replacement No
• Project Planning
• Project List
• Project
Monitoring
Staffing Staffing No replacement No
Accruals* Accruals No replacement No
Employee Timecard Employee Timecard No replacement No
(Flash)*
Metrics* Metrics No replacement No
Scheduling (Flash)* Scheduling No replacement No
31
Migrate to
Widget Name Replacement HTML
Widget Type (example) Name navigator?
Time-Off widget* Time-Off widget No replacement No
Weather* Weather No replacement No
Pre-8.1.3 HTML widgets
HTML widgets NA Uses pre-8.1.3 HTML Yes
created before v8.1.3 widget
*Although these widgets do not have HTML replacements, their functionality is available within
other HTML widgets. See “Widgets not migrated” on page 8 for more information.
Important
The Flash-dependent Exceptions widget is a special case. The HTML exceptions
widget requires the HTML timecard. This means that, in addition to replacing the
Flash-dependent Exceptions widget with the HTML widget, the migration utility
also does the following:
• Adds the HTML Timecard widget if there is no Timecard widget in the
workspace.
• Migrates a Flash Timecard (if already installed) to the HTML equivalent.
• Adds the HTML Timecard to any wizards that use the Exceptions widget
without a timecard.
Update Display Profiles

Navigators are defined in a Navigator Profile, which is then assigned to users in
their Display Profile.
The migration event creates an HTML version of all Navigator Profiles and
appends the name with “HTML.” For example, if the Navigator Profile is named
DeptMgr, the migration event creates a new Navigator Profile called
DeptMgrHTML.
• If the Navigator Profile contains an HTML navigator, the migration event

assigns the HTML Navigator Profile (for example, DeptMgrHTML) to the
Display Profile.
• If the Navigator Profile contains a Flash-dependent navigator, the migration
event does not change the Display Profile (for example, the Navigator Profile
remains at DeptMgr).
• If a Display Profile does not have a Navigator Profile assigned, the user will
log on using the navigator template based on his or her license. See the
Navigator Administrator’s Guide for more information.
Note: To access both Flash and HTML navigators, the Navigator Profile must
include access to a Flash Navigator Profile and an HTML Navigator Profile. The
migration event does this automatically for the SuperUser account. You can also
manually configure multi-navigator access for additional super-access
administrators. See the Navigator Administrator’s Guide for more information.
Log on to navigator
Most users, regardless of whether they are using an HTML navigator or a Flash-
dependent navigator, continue to use the same URL to log on to the system:
http://server/wfc/logon
If the user’s Display Profile points to an HTML navigator, the HTML
environment opens. If the user’s Display Profile points to a Flash navigator, the
Flash environment opens.
Note:
Because certain administrators need to manage both Flash-dependent and HTML
navigators, administrators with super-access can access two different URLs:
• http://server/wfc/navigator/logon – To access Flash-dependent navigators
• http://server/wfc/htmlnavigator/logon – To access HTML navigators
33
Migrate Flash-dependent components to HTML

Complete the following:
• “Task 1: Back up your Flash-dependent database” on page 35
• “Task 2: Run the migration event” on page 35
• “Task 3: Review the migration logs” on page 37
• “Task 4: Verify Navigator Profile for SuperUser” on page 46
• “Task 5: Review and test the migration” on page 47
Task 1: Back up your Flash-dependent database

Before you run the migration event, back up your database. Although there is a
rollback event, these backups can be helpful, if you need to restore the original
Flash Navigator configuration.
Task 2: Run the migration event
Important: The migration event must be run with no users in the system. Because
of this, consider running it during a maintenance window.
1. Log on to Workforce Central as an administrator.

2. Open Event Manager (located in Setup > Common Setup). Scroll to the
Migrate Navigators from Flash to HTML.
35
3. To verify the conditions of the event, click Edit.
You can run the event immediately or schedule it for a time in the future.
– To run the event immediately, select the event and click Run.
– To schedule the event for a later time, select Once from the Schedule
Type drop-down list, enter the applicable date as the start date and the
starting time and click Run.
4. Select Yes in the Are you sure you want to run? warning box.
5. Click Refresh to view the progress.
Note: To run the event a second time, you must run the rollback event first as
described in “Roll Back Flash-to-HTML Migration Changes” on page 55.
Task 3: Review the migration logs

When the event is completed, two logs are created in Kronos/wfc/logs:
• MigrationSummary_yyymmddhm.log
• MigrationDetails_yyymmddhm.log
where yyymmddhm is the date and time that the log was created.
MigrationSummary.log
The MigrationSummary.log file identifies the navigators, workspaces, widgets

and Navigator Profiles that were migrated and those that were not. It also
identifies the Display Profiles that now include HTML navigators instead of Flash
navigators.
Note: All navigators, including the ones that are not fully qualified for HTML are
migrated, but without the Flash content. And Display Profile/template changes are
made only if the underlying navigator is fully qualified for HTML.
Navigators
The log lists the navigators migrated and those that were not migrated. Note that
the migration event appends Flash navigators with the FLX suffix and then clones
the HTML navigators. For example:
--------------------------------------------------------------------------
Migrated Navigator count: 10
--------------------------------------------------------------------------
"00Employee TemplateFLX" migrated to "00Employee Template"
"PartnerFLX" migrated to "Partner"
"00Manager TemplateFLX" migrated to "00Manager Template"
"00SuperUser NavigatorFLX" migrated to "00SuperUser Navigator"
"Manager NavigatorFLX" migrated to "Manager Navigator"
"Inquiry NavigatorFLX" migrated to "Inquiry Navigator"
"Timekeeper NavigatorFLX" migrated to "Timekeeper Navigator"
"Timekeeper Cannot Aprv TCFLX" migrated to "Timekeeper Cannot Aprv TC"
"Employee NavigatorFLX" migrated to "Employee Navigator"
"Default Grant-Project Manager NavigatorFLX" migrated to "Default Grant-
Project Manager Navigator"
37
--------------------------------------------------------------------------
Navigators with unsupported Flash content and not fully qualified for HTML: 6
--------------------------------------------------------------------------
"Manager Navigator"
"Employee Navigator"
"Inquiry Navigator"
"Timekeeper Navigator"
"Timekeeper Cannot Aprv TC"
Workspaces
The log lists the workspaces migrated and those that are not migrated. Note that
the migration event appends Flash workspaces with the FLX suffix and then
clones the HTML navigators. For example:
--------------------------------------------------------------------------
Migrated Workspaces count: 14
--------------------------------------------------------------------------
"Go To LinksFLX" migrated to "Go To Links"
"00My InformationFLX" migrated to "00My Information"
"00GoToLinksFLX" migrated to "00GoToLinks"
"Default Production Order Monitor WorkspaceFLX" migrated to "Default
Production Order Monitor Workspace"
"00Manage My DepartmentFLX" migrated to "00Manage My Department"
"Default Grant-Project Monitor WorkspaceFLX" migrated to "Default Grant-
Project Monitor Workspace"
"ManagerFLX" migrated to "Manager"
"Default SupportFLX" migrated to "Default Support"
"00AdministrationFLX" migrated to "00Administration"
"TimekeeperFLX" migrated to "Timekeeper"
"Inquiry OnlyFLX" migrated to "Inquiry Only"
"AdministrationFLX" migrated to "Administration"
"Timekeeper Cannot Aprv TCFLX" migrated to "Timekeeper Cannot Aprv TC"
"My InformationFLX" migrated to "My Information"
--------------------------------------------------------------------------
Workspaces with unsupported Flash content and not fully qualified for HTML: 1
--------------------------------------------------------------------------
"My Information"
Widgets
The log lists the widgets migrated and those that are not migrated. Note that the
migration event appends the name of the HTML widgets with “HTML” and does
not change the name of Flash widgets. For example:
--------------------------------------------------------------------------
Migrated Widgets count: 22
--------------------------------------------------------------------------
"00Setup" migrated to "00SetupHTML"
"Default Hours of Operation" migrated to "Default Hours of OperationHTML"
"Default Special Events" migrated to "Default Special EventsHTML"
"Default Volume Forecast" migrated to "Default Volume ForecastHTML"
"Default Labor Forecast" migrated to "Default Labor ForecastHTML"
"Default Generate Schedule" migrated to "Default Generate ScheduleHTML"
"Default Create Schedule" migrated to "Default Create ScheduleHTML"
"Quick Leave Editor" migrated to "Quick Leave EditorHTML"
"Change My Password" migrated to "Change My PasswordHTML"
"Change Password" migrated to "Change PasswordHTML"
"Exceptions" migrated to "ExceptionsHTML"
"Group Edit Results" migrated to "Group Edit ResultsHTML"
"Inbox" migrated to "InboxHTML"
"My Calendar" migrated to "My CalendarHTML"
"My Inbox" migrated to "My InboxHTML"
"My Reports" migrated to "My ReportsHTML"
"My Timestamp" migrated to "My TimestampHTML"
"Quick Links" migrated to "Quick LinksHTML"
"Reports" migrated to "ReportsHTML"
"Requests" migrated to "RequestsHTML"
"Rule Analysis" migrated to "Rule AnalysisHTML"
"Security Audit Export" migrated to "Security Audit ExportHTML"
--------------------------------------------------------------------------
Non-Migrated Widgets count: 6
--------------------------------------------------------------------------
"Default ESS Accruals"
"My Leave"
"Default Metrics"
"Default Fill Open Shift"
"Default Staff Management"
"Default Schedule"
39
Navigator Profiles
This section lists the new HTML Navigator Profiles. Note that the migration event
appends the name of the HTML Navigator Profiles with “HTML.”
--------------------------------------------------------------------------
Migrated Navigator Profiles count: 9
--------------------------------------------------------------------------
"Partner" migrated to "PartnerHTML"
"Manager" migrated to "ManagerHTML"
"Employee" migrated to "EmployeeHTML"
"System Administrator" migrated to "System AdministratorHTML"
"Inquiry Only" migrated to "Inquiry OnlyHTML"
"Employee Kronos Template" migrated to "Employee Kronos TemplateHTML"
"Timekeeper" migrated to "TimekeeperHTML"
"Default Grant-Project Manager Navigator Profile" migrated to "Default
Grant-Project Manager Navigator ProfilHTML"
"Default Production Order Manager Navigator Profile" migrated to "Default
Production Order Manager Navigator ProHTML"
--------------------------------------------------------------------------
Navigator Profiles with unsupported Flash content and not fully qualified
for HTML: 5
--------------------------------------------------------------------------
"Manager"
"Employee"
"System Administrator"
"Inquiry Only"
"Timekeeper"
Display Profiles
The log lists the Display Profiles that now only include HTML navigators. Note
that Display Profiles are not renamed. For example:
--------------------------------------------------------------------------
Migrated Display Profiles count: 2
--------------------------------------------------------------------------
"Super Access" - 1 user migrated to HTML
"Partner" - 1 user migrated to HTML
MigrationDetails.log
The MigrationDetails.log file displays the chronological progress of all the

HTML migration activity, including:
• Name of the widgets, workspaces, navigators, and Navigator Profiles that
were cloned
• Status of the cloning operation
• Success
• Success with a warning message
• Failure with an error message
• If operation is successful, details of the cloned widget/workspace/navigator is
listed.
• If the operation fails, the reason for the failure is noted, but the cloning
continues.
When updating the Display Profiles/templates, the following information is
logged:
• Name of the Display Profile/template that has been updated, along with the
details
• Name of the Display Profile/template that has been reviewed for an update,
but was not updated, along with the details
The following is an abbreviated example of the MigrationDetails.log.
41
Preliminaries
2018-Nov-01 12:18:56 INFO ###########################################################
2018-Nov-01 12:18:56 INFO Migration Details Log
2018-Nov-01 12:18:56 INFO Host Name: server22.com
2018-Nov-01 12:18:56 INFO Database Name: DB_40284
2018-Nov-01 12:18:56 INFO Database URL: jdbc:sqlserver://ksr-
usconeng163:1433;databaseName=DB_40284;
2018-Nov-01 12:18:56 INFO Start: 2018-Nov-01 12:18:56
2018-Nov-01 12:18:56 INFO############################################################
2018-Nov-01 12:18:56 INFO Reading configuration data...
2018-Nov-01 12:18:56 INFO Reading configuration data complete
2018-Nov-01 12:18:56 INFO Identifying applet content...
2018-Nov-01 12:18:56 INFO Applet identification complete
Migrating widgets
2018-Nov-01 12:18:56 INFO Migrating widgets...
2018-Nov-01 12:18:56 INFO Flash widget identified: Default Schedule - this widget
will not be migrated to HTML
2018-Nov-01 12:18:56 INFO Flash widget identified: Default Staff Management - this
widget will not be migrated to HTML
2018-Nov-01 12:18:56 INFO Widget: 00Requests migrated to 00RequestsHTML
2018-Nov-01 12:18:56 INFO Widget: 00Punch Issues migrated to 00Punch IssuesHTML
2018-Nov-01 12:18:56 INFO Widget: My Calendar migrated to My CalendarHTML
2018-Nov-01 12:18:56 INFO Widget: My Inbox migrated to My InboxHTML
2018-Nov-01 12:18:56 INFO Widget: My Reports migrated to My ReportsHTML
2018-Nov-01 12:18:57 INFO Widget: My Timestamp migrated to My TimestampHTML
2018-Nov-01 12:18:57 INFO Widget: Quick Links migrated to Quick LinksHTML
2018-Nov-01 12:18:57 INFO Widget: Reports migrated to ReportsHTML
2018-Nov-01 12:18:57 INFO Widget: Requests migrated to RequestsHTML
2018-Nov-01 12:18:57 INFO Widget: Rule Analysis migrated to Rule AnalysisHTML
2018-Nov-01 12:18:57 INFO Widget: Setup migrated to SetupHTML
2018-Nov-01 12:18:57 INFO Widget: Timecard Approval migrated to Timecard ApprovalHTML
2018-Nov-01 12:18:57 INFO Widget: Punch Issues migrated to Punch IssuesHTML
2018-Nov-01 12:18:57 INFO Widget: Timecard Signoff migrated to Timecard SignoffHTML
2018-Nov-01 12:18:57 INFO Widget: 00My Calendar migrated to 00My CalendarHTML
2018-Nov-01 12:18:57 INFO Widget: 00My Inbox migrated to 00My InboxHTML
2018-Nov-01 12:18:57 INFO Widget: Worked Shift migrated to Worked ShiftHTML
2018-Nov-01 12:18:57 INFO Widget: Pay Code Edit migrated to Pay Code EditHTML
2018-Nov-01 12:18:57 INFO Widget: Daily Totals migrated to Daily TotalsHTML
2018-Nov-01 12:18:57 INFO Widget: Schedule Editor migrated to Schedule EditorHTML
2018-Nov-01 12:18:57 INFO Widget: Schedule Shift migrated to Schedule ShiftHTML
2018-Nov-01 12:18:57 INFO Migrating widgets complete
Migrating widget property data

2018-Nov-01 12:18:57 INFO Reading widget property data...
2018-Nov-01 12:18:57 INFO Reading widget property data complete
2018-Nov-01 12:18:57 INFO Migrating widget property data...
2018-Nov-01 12:18:57 INFO Applet content: &SIGNOFF_ISSUES will be replaced by
placeholder link
2018-Nov-01 12:18:57 INFO Applet content: &Pay_Period_Close will be replaced by
placeholder link
2018-Nov-01 12:18:57 INFO Applet content: &Pay_Period_Close will be replaced by
placeholder link
2018-Nov-01 12:18:57 INFO Applet content: &WFS_Schedule_Editor will be replaced by
placeholder link
2018-Nov-01 12:19:00 INFO Migrating widget property data complete
Migrating workspaces
2018-Nov-01 12:19:00 INFO Migrating workspaces...
2018-Nov-01 12:19:00 INFO Workspace with Flash content identified: My Information -
users with navigators containing this workspace will not be migrated
2018-Nov-01 12:19:00 INFO Workspace: Go To Links was renamed to Go To LinksFLX
2018-Nov-01 12:19:00 INFO Workspace: 00GoToLinks was renamed to 00GoToLinksFLX
2018-Nov-01 12:19:00 INFO Workspace: Default Production Order Monitor Workspace was
renamed to Default Production Order Monitor WorkspaceFLX
2018-Nov-01 12:19:00 INFO Workspace: Timekeeper was renamed to TimekeeperFLX
2018-Nov-01 12:19:00 INFO Workspace: Inquiry Only was renamed to Inquiry OnlyFLX
2018-Nov-01 12:19:00 INFO Workspace: Administration was renamed to AdministrationFLX
2018-Nov-01 12:19:00 INFO Workspace: My Information was renamed to My InformationFLX
2018-Nov-01 12:19:00 INFO Workspace: Go To LinksFLX migrated to Go To Links
2018-Nov-01 12:19:00 INFO Workspace: 00My InformationFLX migrated to 00My Information
2018-Nov-01 12:19:00 INFO Workspace: 00GoToLinksFLX migrated to 00GoToLinks
2018-Nov-01 12:19:00 INFO Workspace: ManagerFLX migrated to Manager
2018-Nov-01 12:19:00 INFO Workspace: Default SupportFLX migrated to Default Support
2018-Nov-01 12:19:00 INFO Workspace: 00AdministrationFLX migrated to 00Administration
2018-Nov-01 12:19:00 INFO Workspace: TimekeeperFLX migrated to Timekeeper
2018-Nov-01 12:19:00 INFO Workspace: Inquiry OnlyFLX migrated to Inquiry Only
2018-Nov-01 12:19:00 INFO Workspace: AdministrationFLX migrated to Administration
2018-Nov-01 12:19:00 INFO Workspace: My InformationFLX migrated to My Information
2018-Nov-01 12:19:00 INFO Linking migrated workspaces to migrated widgets...
2018-Nov-01 12:19:01 INFO Linking migrated workspaces to migrated widgets complete
2018-Nov-01 12:19:01 INFO Migrating workspaces complete
43
Migrating navigators
2018-Nov-01 12:19:01 INFO Migrating navigators...
2018-Nov-01 12:19:01 INFO Navigator with Flash content identified: Manager Navigator
- users assigned this navigator will not be migrated
2018-Nov-01 12:19:01 INFO Navigator with Flash content identified: Employee Navigator
- users assigned this navigator will not be migrated
2018-Nov-01 12:19:01 INFO Navigator with Flash content identified: System
Administrator Navigator - users assigned this navigator will not be migrated
2018-Nov-01 12:19:01 INFO Navigator: Partner was renamed to PartnerFLX
2018-Nov-01 12:19:01 INFO Navigator: 00Manager Template was renamed to 00Manager
TemplateFLX
2018-Nov-01 12:19:01 INFO Navigator: 00Employee TemplateFLX migrated to 00Employee
Template
2018-Nov-01 12:19:01 INFO Navigator: 00Manager and Employee TemplateFLX migrated to
00Manager and Employee Template
2018-Nov-01 12:19:01 INFO Navigator: 00Manager and Employee Template is a new
template for: Manager and Employee
2018-Nov-01 12:19:01 INFO Navigator: 00System Administrator TemplateFLX migrated to
00System Administrator Template
2018-Nov-01 12:19:01 INFO Navigator: 00System Administrator Template is a new
template for: System Administrator
2018-Nov-01 12:19:01 INFO Navigator: PartnerFLX migrated to Partner
2018-Nov-01 12:19:01 INFO Linking migrated navigators to migrated workspaces...
2018-Nov-01 12:19:01 INFO Linking migrated navigators to migrated workspaces complete
2018-Nov-01 12:19:01 INFO Migrating navigators complete
Migrating Navigator Profiles

2018-Nov-01 12:19:01 INFO Migrating navigator profiles...
2018-Nov-01 12:19:01 INFO Navigator profile with Flash content identified: Manager -
users assigned this navigator profile will not be migrated
2018-Nov-01 12:19:01 INFO Navigator profile with Flash content identified: Employee -
users assigned this navigator profile will not be migrated
2018-Nov-01 12:19:01 INFO Navigator profile with Flash content identified: System
Administrator - users assigned this navigator profile will not be migrated
2018-Nov-01 12:19:01 INFO Navigator Profile: Partner migrated to PartnerHTML
2018-Nov-01 12:19:01 INFO Navigator Profile: Manager migrated to ManagerHTML
2018-Nov-01 12:19:01 INFO Navigator Profile: Employee migrated to EmployeeHTML
2018-Nov-01 12:19:01 INFO Linking migrated navigator profiles to migrated
navigators...
2018-Nov-01 12:19:01 INFO Linking migrated navigator profiles to migrated navigators
complete
2018-Nov-01 12:19:01 INFO Migrating navigator profiles complete
Updating Display Profiles

2018-Nov-01 12:19:01 INFO Updating display profiles...
2018-Nov-01 12:19:01 INFO Display Profile with Flash content identified: Manager -
users assigned this display profile will not be migrated
2018-Nov-01 12:19:01 INFO Display Profile with Flash content identified: Employee -
users assigned this display profile will not be migrated
2018-Nov-01 12:19:01 INFO Display Profile: Super Access originally referenced:
Partner
2018-Nov-01 12:19:01 INFO Display Profile: Manager originally referenced: Manager
2018-Nov-01 12:19:01 INFO Display Profile: Employee originally referenced: Employee
2018-Nov-01 12:19:01 INFO Display Profile: Timekeeper originally referenced:
Timekeeper
2018-Nov-01 12:19:01 INFO Display Profile: Timekeeper cannot Approve TC originally
referenced: Timekeeper cannot Aprv TC
2018-Nov-01 12:19:01 INFO Display Profile: Super Access was updated to reference:
PartnerHTML
2018-Nov-01 12:19:01 INFO Display Profile: Partner was updated to reference:
PartnerHTML
2018-Nov-01 12:19:01 INFO Updating display profiles complete
Finish the migration

2018-Nov-01 12:19:01 INFO Flash navigator: PartnerFLX was added to SuperUser's
navigator profile: PartnerHTML
2018-Nov-01 12:19:01 INFO Migrating generic data access profiles...
2018-Nov-01 12:19:01 INFO Migrating generic data access profiles complete
2018-Nov-01 12:19:01 INFO Running post-processor...
2018-Nov-01 12:19:01 INFO Widget: 00TimecardsPageHTML was added
2018-Nov-01 12:19:01 INFO Widget: TimecardsPageHTML was added
2018-Nov-01 12:19:01 INFO Post-processor run complete
2018-Nov-01 12:19:02 INFO############################################################
2018-Nov-01 12:19:02 INFO End: 2018-Nov-01 12:19:02
2018-Nov-01 12:19:02 INFO Duration (H:M:S.ms): 0:0:5.583
2018-Nov-01 12:19:02 INFO############################################################
45
Task 4: Verify Navigator Profile for SuperUser

During the Migration process, the Navigator Profile used by the HTML Super-
Access Display Profile is assigned two navigators, one for Flash-dependent
navigators and one for HTML navigators. With the assignment of two Navigator
Profiles, the SuperUser (or any user that uses this Navigator Profile) can log on to
each type of navigator by entering one of the following URLs:
See “Examples” on page 63 for more information.
Note: Users logging on with Single Sign-On (SSO) are directed to the navigator
defined in their Display Profile. Users who can access both Flash and HTML
navigators are directed to the HTML navigator. To access the Flash navigator after
logged in via SSO, the user must immediately open a new tab or browser window
and enter in the Flash URL. When the Flash navigator opens, close the HTML
navigator and start working in the Flash navigator.
To verify the assignment:

1. Log on to the system as SuperUser.
2. From Setup, navigate to Display Preferences and open Navigator Profiles.
3. Select the SuperUser Navigator Profile and click Edit.
4. In the Navigator Profiles Editor, verify that both the HTML navigator and the
Flash navigator is listed in the Selected box.
5. Click Save & Return.
If necessary, you can manually provide access to Flash and HTML navigators for
additional super-access accounts by following these steps. For more detailed
information, refer to the Navigator Administrator’s Guide for v8.1.3.
Task 5: Review and test the migration

While still in the test environment, log on as different users and thoroughly test
the migration.
If you are not satisfied with migration, run the rollback event (as described in
“Roll Back Flash-to-HTML Migration Changes” on page 55), make the necessary
changes to your navigator configuration, and run the migration event again.
If you are satisfied with the migration, you are ready to move to the production
environment as described in “Move from Test to Production Environment” on
page 49.
47
Step 4: Move from Test to Production Environment
After thoroughly testing the migration in your test environment, you can update
your production environment. Note that it is important to run the migration event
on the production system before using Setup Data Manager.
1. Back up the production database.
2. Run the migration event.
Note: You need to run the migration event in the production environment
before running SDM because the event creates metadata that is not exportable
via SDM.
3. Copy the configuration from the test environment to the production

environment using Setup Data Manager. Make sure that you select all of the
HTML navigator configurations.
Move from Test to Production Environment
Appendix A
v8.1.3 Widget Migration Summary
HTML
Pre- Not
Widget Type Flash v8.1.3 v8.1.3 Migrated Comments
Accruals X X Use the Accruals add-on in the
timecard instead of the
Accruals widget.
Activities X X
Alerts X X
Audit X X
Calendar X X
Call List X X Use the Staffing Assistant in the
Schedule Planner instead of the
Call List widget.
Employee Punch X X
Employee Self X X
Scheduling
Employee X X Use the HTML timecard
Timecard instead of the Flash timecard.
Exceptions X X Requires an HTML timecard as
well.
Genie X X
Grant and Project X X
Tracking
Leaderboard X
Manage Navigators X X
Appendix A v8.1.3 Widget Migration Summary
HTML
Pre- Not
Metrics X X Use the Metrics add-on in
Schedule Planner instead of the
metrics widget.
People Editor X X
Project List X X Requires Flash. Part of Task
Management.
Project Monitoring X X Requires Flash. Part of Task
Management.
Project Planning X X Requires Flash. Part of Task
Management.
Quick Links X X The Quick Links container
migrates to HTML but applet or
Flash-dependent links within
the container do not migrate.
See the Links section in the
Navigator Configuration Report
utility detail report.
Request Manager X X
Schedule (legacy) X X Use the HTML Schedule
Planner instead of the Flash
Scheduling widget.
Schedule X X Use functionality available in
the Schedule Planner widget
Schedule Planner X X
Search X X
Single Link X X The Single Link container
migrates to HTML but an
applet or Flash-dependent link
within the container does not
migrate. See the Links section
in the Navigator Configuration
Report utility detail report.
HTML
Pre- Not
Staffing X X Requires Flash
Timecard X X
Time-Off Request X X Use the functionality available
in HTML Request Manager
instead of using the Time-Off
widget.
Timestamp X X
Totals X X
Weather X X Use the Single Link widget
pointing a weather site instead
of using the Weather widget.
Wizard X X • If there is a Staffing widget
in a wizard, the migration
event drops it from the
wizard and continues to
migrate to HTML.
• Applet or Flash-dependent
links within the wizard do
not migrate. See the Links
section in the Navigator
Configuration Report utility
detail report.
Workload Planner X X
53
Appendix A v8.1.3 Widget Migration Summary
Appendix B
Roll Back Flash-to-HTML Migration Changes
If you want to remain on service release v8.1.3 but need to roll back to Flash-
dependent components, you can do so from the rollback event in Event Manager
called Roll Back Navigators from HTML to Flash. The event does the
following:
• Deletes all HTML components delivered by the migration event
• Returns all components to their original names
• Changes all Display Profiles to point to Flash-dependent navigators
Important:
Be aware of the following:
• Although it can be done, running the rollback event in a production
environment is not recommended. The rollback event is a mechanism built to
allow for rollbacks in test environments, as you test and finalize your HTML
components. For production rollbacks and downgrades, Kronos recommends
that you use the data backups created before migration/upgrade.
• If your original Flash-dependent navigator configuration changed since you
migrated to HTML, you should not rely on the rollback event. Use the backup
you made in “Task 1: Back up your Flash-dependent database” on page 35.
Appendix B Roll Back Flash-to-HTML Migration Changes
To run the rollback event, do the following:

1. Log on to Workforce Central as an administrator.
2. Open Event Manager (located in Setup > Common Setup). Scroll to Roll
Back Navigators from HTML to Flash.
3. To verify the conditions of the event, click Edit.
4. Click Run to open the event and then click Yes in the Are you sure you want
to run? warning box.
5. Click Refresh to view the progress.
Note: To remove service release v8.1.3 altogether and return to v8.1, roll back the
migration event and then remove the service release as described in the Applying
8.1.x Service Releases document.
57
Appendix B Roll Back Flash-to-HTML Migration Changes
Appendix C
Configure v8.1.3 Online Help
Starting with service release v8.1.3, updated online help is included in a zip file on
the service release installation kit.
You can unzip the v8.1.3 help folder to a web server within your environment or
unzip it within the Workforce Central environment, and link to it within
navigators.
Note: If you configure the help before running the migration event, the v8.1.3 help
can be used in both Flash-dependent and HTML navigators. If you configure the
help after running the migration event, you should configure it for in an HTML
navigator.
To incorporate the updated help, complete the following steps:

1. From the Workforce Central installation kit, navigate to Flash-to-HTML
Migration Tools and select Help file.
2. Extract the help system zip file to new folder within the \\Kronos folder.
For example, the v8.1.3 help could be:
\\Kronos\help\help813
3. Log on to the system as SuperUser.
4. In the Administration workspace, open Setup and expand it to full screen.
5. Navigate to Display Preferences > Display Profile Building Blocks and
open Custom URLs.
6. On the Custom URLs page, add a new row and enter the following
information:
– Display Label — Enter the name of the URL
Appendix C Configure v8.1.3 Online Help
– URL — Enter:
http://ServerName/wfcstatic/help/ServicePackHelpName/en/
wwhelp.htm
For example:
http://MyMachine/wfcstatic/help/Help813/en/wwhelp.htm
– Select the Display on the top Navigation Bar check box.
7. Click Save.
8. Go back to Setup and select Display Preferences > Display Profile Building
Blocks and open Custom URL Profiles.
a. Select a profile and click Edit.
b. On the Edit Custom URL Profile page, select the URL that you just
created from the Available URLs box and move it to the Selected URLs
box.
c. Click Save & Return.
9. Sign out and sign back in again.
10. Open Manage Navigators.
a. Select the Widgets tab.
b. Click New and enter the following information on the Add Widgets page:
Widget Type — Select Single Link.
Name, Label and Description — Enter information to identify the help
system.
Primary View — Expand My Links and select the help system.
(Optional) Secondary View — Expand My Links and select the help
system.
c. Click Save.
11. In Manage Navigators, select the Workspaces tab and then select a
workspace.
a. In the Widgets area, select the service pack help from the Available box
and move it to the Selected box.
b. If you want the widget to be visible, add it to the Selected box in the
Visible Widgets area.
12. Sign out and sign back in again. The new help system is now visible.
Note: The original v8.1.0 help, which was delivered as a Single Link widget when
you installed v8.1, will still be on the system and you can continue to use it or
remove it from navigators. If you roll back the service release, the v8.1.3 help
Single Link widget will remain, but so will the original v8.1.0 help so you can
decide which one to use.
61
Appendix C Configure v8.1.3 Online Help
Appendix D
Examples
During the Migration process, the Navigator Profile used by the HTML Super-
Access Display Profile is assigned two navigators, one for Flash-dependent
navigators and one for HTML navigators. With the assignment of two Navigator
Profiles, the SuperUser (or any user that uses this Navigator Profile) can log on to
each type of navigator by entering one of the following URLs:
Example 1: SuperUser logs on to the Flash-dependent navigator and

opens Manage Navigators
Only Flash-dependent widgets are listed on the Widgets tab. Note that the Default
Staff Management widget is also listed.
Only Flash-dependent navigators are listed on the Navigators tab:
64
Example 2: SuperUser logs on to the HTML navigator and opens
Manage Navigators
Only HTML widgets are listed on the Widgets tab. Note that the Default Staff
Management widget is not listed
Only HTML navigators are listed on the Navigators tab:
65
66

WFC813 Flash To HTML MigrationGuide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

WFC813 Flash To HTML MigrationGuide

Hochgeladen von

Copyright:

Verfügbare Formate

Flash-to-HTML Migration Guide

A guide to setting up HTML navigators

Kronos® Workforce Central® suite version 8.1.3

Published by Kronos Incorporated

For links to information about international subsidiaries of Kronos Incorporated, go to

Document Revision Release Date

Step 1: Apply Service Release v8.1.3

Step 2: Prepare to Migrate

Step 3: Run the Migration Event

Step 4: Move from Test to Production Environment

Appendix A: v8.1.3 Widget Migration Summary

Appendix B: Roll Back Flash-to-HTML Migration Changes

Appendix C: Configure v8.1.3 Online Help

Workforce Central navigators have historically required browser support for

Note: In earlier versions of Workforce Central, navigators included a combination

replacements for Java applet components as described in the Navigator

An important requirement for v8.1.3 users is that Flash-dependent components

Important: If anyone in your organization uses Process Manager requests that

• A migration event called Migrate Navigators from Flash to HTML is

Widgets not migrated

Widgets remaining on Flash

Widgets whose functionality can be added to HTML widget

Process Manager templates that use Request Manager

Important background information:

“Task 1: Run the Navigator Configuration Report utility” on page 16

Task 1: Run the Navigator Configuration Report utility

Run the utility from the UI

3. Double-click navreport.bat (Windows) or navreport (Linux/AIX). Refer to

4. Enter the following information:

5. Click Generate Report. A message displays while the report is being

Run the utility from the command line

3. Press Enter to run the utility.

Task 2: Review the navigator reports

The detail report contains the following columns:

• Link Name – Lists any links used in the workspace.

Unsupported Request Types report

• Comments — Depending on the template category identified, the following

Migration event overview

Replace Flash-dependent components

Flash Component HTML Component

The following details how various widgets are migrated:

Update Display Profiles

• If the Navigator Profile contains an HTML navigator, the migration event

Migrate Flash-dependent components to HTML

Task 1: Back up your Flash-dependent database

Task 2: Run the migration event

1. Log on to Workforce Central as an administrator.

3. To verify the conditions of the event, click Edit.

Task 3: Review the migration logs

The MigrationSummary.log file identifies the navigators, workspaces, widgets

The MigrationDetails.log file displays the chronological progress of all the

Migrating widget property data

Migrating Navigator Profiles

Updating Display Profiles

Finish the migration

Task 4: Verify Navigator Profile for SuperUser

To verify the assignment:

Task 5: Review and test the migration

3. Copy the configuration from the test environment to the production

To run the rollback event, do the following:

3. To verify the conditions of the event, click Edit.

To incorporate the updated help, complete the following steps:

Example 1: SuperUser logs on to the Flash-dependent navigator and