System Administrators Guide

Workforce Central ®
System Administrator’s
Guide
An administrator’s guide to the Workforce Central system.
Kronos Workforce Central Suite

Version 6
Document Part Number: 4703953-001

Document Revision: A
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. All rights reserved. Copyright 2007.
Altitude, Altitude Dream, Cambridge Clock, CardSaver, Datakeeper, Datakeeper Central, eForce, Gatekeeper,
Gatekeeper Central, Imagekeeper, Jobkeeper Central, Keep.Trac, Kronos, Kronos Touch ID, the Kronos logo, My
Genies, PeoplePlanner, PeoplePlanner & Design, Schedule Manager & Design, ShiftLogic, ShopTrac, ShopTrac
Pro, StarComm, StarPort, StarSaver, StarTimer, TeleTime, Timekeeper, Timekeeper Central, TimeMaker, Unicru,
Visionware, Workforce Accruals, Workforce Central, Workforce Decisions, Workforce Express, Workforce Genie,
and Workforce TeleTime are registered trademarks of Kronos Incorporated or a related company. Altitude MPP,
Altitude MPPXpress, Altitude Pairing, Altitude PBS, Comm.Mgr, CommLink, DKC/Datalink, eDiagnostics, Experts at
Improving the Performance of People and Business, FasTrack, Hireport, HR and Payroll Answerforce, HyperFind,
Kronos 4500 Touch ID, Kronos 4500, Kronos 4510, Kronos Acquisition, Kronos e-Central, Kronos KnowledgePass,
Kronos TechKnowledgy, KronosWorks, KVC OnDemand, Labor Plus, Momentum Essentials, Momentum Online,
Momentum, MPPXpress, Overall Labor Effectiveness, Schedule Assistant, Smart Scheduler, Smart View, Start
Quality, Start WIP, Starter Series, StartLabor, Timekeeper Decisions, Timekeeper Web, VisionPlus, Winstar Elite,
WIP Plus, Workforce Acquisition, Workforce Activities, Workforce Analytics, Workforce Attendance, Workforce
Central Portal, Workforce Connect, Workforce Employee, Workforce HR, Workforce Leave, Workforce Manager,
Workforce MobileTime, Workforce Operations Planner, Workforce Payroll, Workforce Record Manager, Workforce
Recruiter, Workforce Scheduler with Optimization, Workforce Scheduler, Workforce Smart Scheduler, Workforce Tax
Filing, Workforce Timekeeper, and Workforce View are trademarks of Kronos Incorporated or a related company.
Mozilla.org is a registered trademark of the Mozilla Foundation. All other trademarks or registered trademarks used
herein are the property of their respective owners and are used for identification purposes only.
When using and applying the information generated by Kronos products, customers should ensure that they comply
with the applicable requirements of 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

297 Billerica Road, Chelmsford, Massachusetts 01824-4119 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 Product Version Release Date
A Workforce Central 6.0 June 2007

Contents
About This Guide

Organization of this guide ........................................................................... 12
Abbreviations and Terminology .................................................................. 14
Workforce Central suite documentation ...................................................... 16
Workforce Central documentation ........................................................ 16
Workforce Timekeeper documentation ................................................. 17
Workforce Record Manager documentation ......................................... 18
Developers Toolkit documentation ....................................................... 18
Other documentation ............................................................................. 19
Chapter 1: Introduction
Workforce Central infrastructure ................................................................ 22
System configuration overview ................................................................... 23
Logging on to Workforce Central ................................................................ 24
Logging on with Single Sign-on ........................................................... 24
Enabling Active X controls and plugins ............................................... 25
Offline mode ......................................................................................... 25
Managing an instance remotely ........................................................... 26
Configure a visual theme ............................................................................ 27
Working with passwords ............................................................................. 28
Change user passwords ......................................................................... 28
Use the single sign-on feature ............................................................... 28
Set users’ browsers to remember passwords ........................................ 28
Change the SuperUser Password .......................................................... 29
Changing the Relogon session timeout ....................................................... 31
Changing the JBoss Session timeout setting ......................................... 32
Changing the Workforce Central session timeout grace period ............ 32
Working with property files ........................................................................ 34
Modifying properties ............................................................................ 34
Contents
Configuring a multi-instance environment .................................................36

Configuring Group Edits for a multi-instance environment ..................37
Configuring e-mail for a multi-instance environment ...........................37
Configuring Event Manager for a multi-instance environment ............37
Working with Workflow Notifications ........................................................39
Notification types ..................................................................................39
Available notification ............................................................................40
Setting up a Workflow Notification ......................................................41
Configuring Process Manager and Process Designer ..................................44
Upgrading from an earlier version of Process Manager ........................45
Configuring the Server ..........................................................................46
Setting up Delegate Authority ......................................................................50
Setting up the environment ....................................................................50
Setting up the delegate ...........................................................................50
Creating and assigning a Delegate Data Access Profile ........................51
Chapter 2: System Information

Working with System Information ..............................................................54
All Servers information ................................................................................55
Applications information .............................................................................57
Background Processors information ............................................................58
Totals Calculation - Excluded Employees ............................................58
Historical Edits with Retroactive Pay Calculation - Excluded
Employees ...................................................................................59
Database information ...................................................................................60
Database ................................................................................................60
Database Report Status ..........................................................................61
Database Report Display .......................................................................62
Working with database reports ..............................................................63
Creating Database Report Definition files ............................................63
Guidelines for creating Database Report Definition files .....................65
Licenses information ....................................................................................67
Meters information .......................................................................................68
Primary Labor Account Update information ...............................................69
Primary Labor Account Update .............................................................69
4 Kronos Incorporated
Contents
Resubmit All People for Account Update ............................................ 69

Threads information ................................................................................... 71
User information .......................................................................................... 73
Chapter 3: Log Report

Log reports ................................................................................................... 76
Log files ....................................................................................................... 79
System log file ...................................................................................... 79
Component log files .............................................................................. 79
Log file report .............................................................................................. 81
Filtering and running log reports ................................................................. 82
Archiving system log reports ....................................................................... 83
Chapter 4: Log File Gathering

Listing the log files to be gathered .............................................................. 86
Gathering log information ........................................................................... 88
Opening gathered log files ........................................................................... 89
Chapter 5: System Settings

Overview .................................................................................................... 93
Working with System Settings .................................................................... 94
Before editing a configuration setting ................................................... 94
Editing a configuration setting .............................................................. 95
Using system settings ............................................................................ 95
Understanding properties validation ..................................................... 97
Audit Settings .............................................................................................. 98
Business Automation settings ...................................................................... 99
Background Processor settings .................................................................. 102
Clock Synchronize settings ....................................................................... 105
Data Source settings .................................................................................. 107
Adding Data Source Names ................................................................ 108
Database settings ....................................................................................... 109
Switching databases ............................................................................ 110
Display settings ......................................................................................... 116
E-mail settings ........................................................................................... 117
Workforce Central System Administrator’s Guide 5

Contents
Event Manager settings ..............................................................................120

Working with Event Manager .............................................................122
Scheduling Event Manager tasks .........................................................125
Global Values settings ...............................................................................126
Group Edits settings ...................................................................................136
Clearing the Group Edit Results in Genies ..........................................138
Java Plug-in settings ...................................................................................139
Locale settings ............................................................................................140
Log file settings ..........................................................................................145
Logging Context settings ...........................................................................148
Messaging settings .....................................................................................149
Printers settings ..........................................................................................150
Enabling a server-based printer ...........................................................151
Record Retention - Affected Databases settings ........................................152
Record Retention - Database Setup settings ..............................................153
Record Retention - Options & Tuning settings ..........................................154
Reports settings ..........................................................................................157
Security settings .........................................................................................160
Understanding authentication ..............................................................163
Changing the logoff timer ...................................................................165
Service settings ..........................................................................................167
SQL Coverage settings ...............................................................................169
Enabling SQL tracing ..........................................................................170
Startup settings ...........................................................................................171
Transformation settings ..............................................................................172
Web & App Server settings .......................................................................173
System Settings for Workload Generator ..................................................175
Configurable terms ..............................................................................175
Additional system settings ...................................................................177
Chapter 6: Create a Custom Theme

Create a new theme folder for the custom theme .......................................180
Select colors for the theme ..................................................................180
Prepare the logo file .............................................................................184
Specify custom property values in theme.css ......................................185
Contents
Change colors in the image files to match the custom theme ............. 189
Test the custom theme ........................................................................ 194
Deploy the custom theme ................................................................... 195
Extend the custom theme to the portal ................................................ 196
Chapter 7: Reports
Overview .................................................................................................. 198
Terminology ........................................................................................ 199
Setting up reports for totalization ....................................................... 200
Enabling a report to export to Microsoft Excel .................................. 200
Installing fonts for Workforce Activities reports ................................ 201
Managing reporting environments ............................................................ 202
Basic reporting .................................................................................... 202
Advanced Reporting ........................................................................... 205
Customizing reports ................................................................................... 211
Customizing RDL reports ................................................................... 211
Customizing RPT reports .................................................................... 221
Customizing reports that use stored procedures ................................. 240
Chapter 8: Workforce Central Portal Configuration

Overview of the Workforce Central Portal ................................................ 244
Purpose of the Workforce Central Portal ............................................ 244
Workforce Central Portal page configuration options ........................ 245
Kronos Web Parts and sample pages provided by the
Workforce Central Portal .......................................................... 245
Adding Kronos Web Parts to a new or existing SharePoint portal page ... 249
Adding Kronos navigation Web Parts to a portal page ....................... 250
Adding and connecting Kronos Web Parts to a portal page ............... 252
Customizing a Workforce Central Portal sample page .............................. 255
Using the Kronos Web Part page template to create a portal page ........... 256
Customizing preconfigured Workforce Central Portal Web Parts ............ 257
Using SharePoint to change the title and appearance of a Web Part .. 257
Using SharePoint to change Kronos-specific settings for Web Parts . 258
Changing labels in Kronos Web Parts ................................................ 260
Additional configuration of health care Web Parts ............................. 262

Contents
Configuring the Productivity Monitor KPIs (retail) ............................264

Configuring the Web Part charts for compatibility with Office Web
Components ..............................................................................270
Advanced configuration of Kronos Web Parts ....................................273
Creating custom Workforce Central Web Parts .........................................274
How Web Parts work ...........................................................................274
Examples of Web Parts to create .........................................................275
Basic strategy for creating a Web Part ................................................276
Procedures for creating a Web Part based on a Genie .........................277
Visual theme for the Workforce Central Portal and Kronos Web Parts ....287
Customizing and creating Web Part Help topics .......................................288
Customizing Kronos Web Part Help topics .........................................288
Creating and linking a Help topic to a custom Web Part ....................290
Troubleshooting .........................................................................................292
General ................................................................................................292
SharePoint ............................................................................................295
Workforce Genies .......................................................................................298
HyperFind query ........................................................................................301
Workforce Genie profile ............................................................................302
People .........................................................................................................303
Logon profiles ............................................................................................304
Managing processes with Process Administrator ......................................306
Viewing the status of all processes ......................................................306
Aborting a process ...............................................................................308
Deleting a process ................................................................................308
Restarting a process .............................................................................309
Viewing process reports ......................................................................310
Managing tasks in a process using Process Administrator ........................311
Viewing and changing the status of tasks in a process ........................311
Changing the status of tasks in a process ............................................313
Viewing the properties of a task ..........................................................315
Viewing task statistics for a process ....................................................315
Monitoring resources using Process Administrator ...................................317
Troubleshooting Process Manager .............................................................318
Enhancing Process Manager performance .................................................319
Contents
Clustering ............................................................................................ 319

Process pooling ................................................................................... 321
Workforce Central language packs ............................................................ 324
Character set support ................................................................................. 325
Workforce Central instances and regionalization ...................................... 326
How Workforce Central displays regionalized data and text .................... 327
Browser applications ........................................................................... 327
Currency support ....................................................................................... 332
Using and modifying predefined names .................................................... 333
Using site-defined text strings in a multilanguage environment ............... 340
Windows registry keys .............................................................................. 342
UNIX registry keys .................................................................................... 343
Configuring Workforce Central to enable single sign-on .......................... 346
Configuring SiteMinder ............................................................................. 347
Diagnostic Tools user interface ................................................................. 350
Diagnostic Tools logon screen ............................................................ 350
Launching a specific application ........................................................ 350
Diagnostics Tools and usage ..................................................................... 351
Running the SMTP Mail Server Diagnostic Tool ............................... 351
Running the SMTP Mail to Launcher Diagnostic Tool ...................... 351
Running the Shift-Builder Diagnostic Tool ........................................ 352
Index

Contents
About This Guide
This preface contains the following sections:

• “Organization of this guide” on page 12
• “Abbreviations and Terminology” on page 14
• “Workforce Central suite documentation” on page 16
About This Guide
Organization of this guide

The chapters in this guide provide the following information:
• Chapter 1, “Introduction,” on page 21 contains an overview of the Kronos®
Workforce Central® system architecture and describes the tasks that you use to
administer the system.
• Chapter 2, “System Information,” on page 53 explains the System
Information component of the Workforce Central system and describes the
tasks that you use to work with System Information.
• Chapter 3, “Log Report,” on page 75 explains the Log Report section of the
System Configuration component and describes the tasks that you use to work
with log reports.
• Chapter 4, “Log File Gathering,” on page 85 describes the Log Gathering
tool, which enables you to gather all the log files in your Workforce Central
system into one ZIP file.
• Chapter 5, “System Settings,” on page 91 explains the System Settings
section of the System Configuration component and describes the tasks that
you use to work with System Settings.
• Chapter 6, “Create a Custom Theme,” on page 179 describes how to create a
custom theme to change the appearance of colors and fonts in Workforce
Central application pages to any set of colors preferred for the site.
• Chapter 7, “Reports,” on page 197 contains information about working with
reports in the Workforce Central system.
• Chapter 8, “Workforce Central Portal Configuration,” on page 243 describes
how to configure the Workforce Central Portal.
• Appendix A, “Predefined Data,” on page 297 describes predefined data that
the Workforce Central system provides to simplify your administration tasks.
• Appendix B, “System Administration of Process Manager,” on page 305
explains the processes that you implement with Process Designer and
Workforce Central across the organization.
• Appendix C, “Regional Settings,” on page 323 discusses values that need to
be set for different countries and languages.
Organization of this guide
• Appendix D, “Registry Keys,” on page 341 describes the registry keys that
were set up when your Workforce Central system was installed.
• Appendix E, “Single Sign-On,” on page 345 provides information about using
single sign-on, which allows users to log on to Workforce Central
automatically, without having to re-enter a username or password after they
have logged onto their browser.
• Appendix F, “Diagnostic Tools,” on page 349 contains an overview of the
diagnostic tools and describes how to use the different tools.

About This Guide
Abbreviations and Terminology

This guide uses the following abbreviations and terms:
Abbreviation/Terms Meaning
ADSI Microsoft Active Directory Service Interface
API Application Programming Interface
BGP Background Processor. A platform on which a Background
Totalizer application runs.
daemon A process that runs in the background and performs a specified
operation at predefined times or in response to certain events.
DCM Data Collection Manager. A set of functions that deals with data
from data collection devices. In a multiserver environment,
DCM can run on a dedicated server.
DNS Domain Naming Service
DSN Data Source Name
GUI Graphical User Interface
HTTP HyperText Transfer Protocol. A communication protocol
between a client and a server.
HTTPS HyperText Transfer Protocol Secure. A communication protocol
with encryption security, using a Secure Sockets Layer.
IE Microsoft Internet Explorer
IP Internet Protocol address
ISO International Standards Organization
JDBC Java Database Connectivity
JRE Java Runtime Environment
JSP Java Server Page
JVM Java Virtual Machine
LDAP Lightweight Directory Access Protocol
ODBC Open Database Connectivity
PDF Portable Document Format
RSA A public-key cryptosystem developed by RSA, Inc.
Abbreviations and Terminology
Abbreviation/Terms Meaning
SMTP Simple Mail Transfer Protocol
SSL Secure Sockets Layer

About This Guide
Workforce Central suite documentation

The following documentation is available in PDF and HTML format on the
Workforce Central documentation CD to help you install, use, and maintain the
database and associated software.
Workforce Central documentation

• Guide to Planning a Workforce Central Installation provides an overview of
the Workforce Central architecture, outlines the system requirements,
explains how to prepare to install the server and client components for
Workforce Timekeeper and other products in the suite, and includes the
corresponding licensing and upgrade requirements.
• The Workforce Central documentation CD includes several installation and
upgrade guides that describe how to install or upgrade Workforce Timekeeper
and other Workforce Central suite products based on the product
combinations and versions in use at your site.
• Workforce Central System Administrator’s Guide provides an overview of the
system architecture, explains system administration tasks, describes how to
work with logs and reports, and provides instructions for creating a custom
theme for the browser interface.
• Workforce Central Process Manager/Messaging Database Tables Reference
Guide supplements the Workforce Timekeeper Database Tables Reference
Guide with information about the database tables that are used specifically by
Process Manager and the Kronos Messaging System.
• Workforce Central Process Manager Programmer’s Guide describes how to
use Process Manager to configure, implement, and maintain automated
business processes across an organization.
• Workforce Central Database Administrator’s Guide explains how to maintain
the Oracle and SQL Server databases for Workforce Timekeeper. This guide
includes procedures for backing up databases, restoring and recovering
databases, adjusting performance, and using maintenance utilities.
• Workforce Central Import User’s Guide provides information about setting up

and running XML and table imports for labor management systems. It
describes the Transaction Assistant, which you use to correct failed XML
import data.
Workforce Timekeeper documentation

• Getting Started with Workforce Timekeeper—A Manager’s Guide for Power
Users summarizes the most common manager tasks, which include using
Workforce Genies, Timecards, Reports, and the People Editor.
• Getting Started with Workforce Timekeeper—A Guide for Managers
summarizes key product features for people who access employee time and
attendance information. The book also explains the various Workforce
Timekeeper components and the most common tasks that managers are likely
to perform with each component.
• Getting Started with Workforce Timekeeper—An Employee Guide for Power
Users explains some of the most common employee tasks, which include
using the Timecard and Time Stamp components, as well as viewing personal
schedules and reports.
• Getting Started with Workforce Timekeeper—A Guide for Employees explains
some of the most common employee tasks in Workforce Employee - HTML
Client, which includes using the Timecard, Time Stamp, and Quick Time
Stamp components, as well as viewing personal reports.
• Workforce Timekeeper Database Tables Reference Guide contains details
about the Workforce Central database tables.
• Workforce Timekeeper Database Views Reference Guide provides information
and details about Views and how they are used as virtual tables in Workforce
Central.
• Workforce Central System Administrator’s Guide—Timekeeping describes the
administrator’s activities, such as system configuration and setup, and
working with log reports, predefined data, and diagnostic tools.
• Workforce Timekeeper Table Format Import Programmer’s Guide provides
instructions and table data for Workforce Timekeeper Import tables.

About This Guide
• Workforce Central Process Manager Programmer’s Guide—Timekeeping and

Scheduling provides information on how to configure the Workforce
Timekeeper and Workforce Scheduler process templates.
Workforce Record Manager documentation

• Workforce Record Manager Installation Guide includes installation and
configuration instructions for Workforce Record Manager, the Setup Data
Manager, and the non-production databases and application servers that make
up the Workforce Record Manager environment.
• Workforce Record Manager User’s Guide provides instructions and guidelines
for customers and service personnel who use Workforce Record Manager and
the Setup Data Manager to copy data from one Workforce Central database to
another. It describes how to create, run, and schedule Workforce Record
Manager jobs and how to administer the Workforce Record Manager
environment.
Developers Toolkit documentation

Workforce Central includes an Application Program Interface (API) that you can
use to access certain Workforce Central features from application programs. The
separate Developers Toolkit documentation CD contains the information that you
need to use the API.
• The Workforce Central Developers Toolkit Programmer’s Guide includes
annotated sample programs that show how to use the API, provides
information that specifically addresses XML import and export issues, and
includes descriptions of all of the tags, actions, and properties used by import
transactions.
• The Workforce Central Developers Toolkit Reference Guides provide detailed
information about each element of the API for each product in the Workforce
Central suite.
Other documentation
• The Guide to Translating and Customizing Workforce Central that is available
on the separate Translation and Customization Toolkit CD, provides
instructions for editing the browser-based graphical user interface and the
associated browser-based Help files for Workforce Central.
• Online Help for the Workforce Central suite is installed automatically with the
product.
• Release notes that are available on the Workforce Central suite product CD
provide additional information about the Workforce Central suite, including a
list of new features, resolved issues, and late-breaking changes.

About This Guide
Chapter 1
Introduction
This chapter introduces the Workforce Central system architecture and discusses
its implementation in single-instance and multi-instance environments.
This chapter contains the following sections:
• “Workforce Central infrastructure” on page 22
• “System configuration overview” on page 23
• “Logging on to Workforce Central” on page 24
• “Configure a visual theme” on page 27
• “Working with passwords” on page 28
• “Changing the Relogon session timeout” on page 31
• “Working with property files” on page 34
• “Configuring a multi-instance environment” on page 36
• “Working with Workflow Notifications” on page 39
• “Configuring Process Manager and Process Designer” on page 44
• “Setting up Delegate Authority” on page 50
Chapter 1 Introduction
Workforce Central infrastructure

Workforce Central applications require the following infrastructure:
• Operating system — All Workforce Central applications run on Windows;
most can also run on UNIX.
• Application server — Workforce Timekeeper requires a J2EE-compatible
application server: JBoss (delivered by the Workforce Timekeeper installation
program).
• Web server — All Workforce Central applications can use Microsoft IIS web
server software. Most applications can use Apache (delivered by the
Workforce Timekeeper installation program), IBM HTTP Web Server, or
Oracle HTTP Server.
• Database — All Workforce Central applications support an SQL Server
database; most also support an Oracle database.
Earlier versions of Workforce Timekeeper used the term application server to
describe the entire Workforce Timekeeper application, which included third-party
application server software and web server software, all installed on one machine.
Although Workforce Timekeeper v6.0 continues to support this configuration, it
also now supports the following configurations:
• Workforce Timekeeper and application server software can reside on one
machine and web server software can reside on a different machine.
• Multiple instances of one or more Workforce Central applications can be
installed on the same machine. Each instance can be independent and does not
share code, runtime information, or temporary files.
This means that, in Workforce Timekeeper v6.0, the following important
distinctions are made:
• The term application server is only used in reference to the third-party
application server software, such as JBoss, not the Workforce Timekeeper
application.
• The term instance is used to refer to a single copy of a running Workforce
Central application. For example, one, two, or more instances of Workforce
Timekeeper can be installed on a machine supported by one application
server.
System configuration overview
System configuration overview

Use the System Configuration component to manage and configure the system.
As system administrator, you can configure various aspects of a Workforce
Central instance, diagnose and correct problems, and establish database and
networking parameters.
The System Configuration component in Setup contains the following
components that deal with administering the system (these are accessible only
with administrative rights):
• System Information — Displays a set of tabs representing different
characteristics of the system. Clicking each tab displays that area’s
parameters. This component is used primarily for viewing the current state of
the system, although actions are possible from several areas.
• Log Report — Displays a workspace that can be edited, enabling you to
determine the information to be detailed in the log, and an action menu. This
component allows you to create a customized log report.
• System Settings — Displays a set of tabs representing different
characteristics of the system and a workspace that can be edited. Clicking
each tab displays properties for that area, and an action menu. This
component allows you to change the values for system properties and to save
the changes in a custom property file.
When the system starts in offline mode, the system configuration components are
the only part of the system that are accessible. For information about offline
mode, see “Offline mode” on page 25.
Because you can access the system through a web browser, you do not need direct
access to the system console and property files to administer the system. Instead,
you can administer the system from a remote location through System
Configuration.

Logging on to Workforce Central

Users normally access the system through the web logon page specified for the
instance:
http://web_server/instance/logon
where web_server is the name of the machine where the web server software
is installed and instance is the name of the instance, which is wfc by default.
Note that this URL is case-sensitive.
Users of Workforce Employee - HTML Client access the Workforce Timekeeper
system through:
http://web_server/instance/applications/wtk/html/ess/
logon.jsp
Users of Workforce Employee - HTML Client using Quick Time Stamp access the
system through:
http://web_server/instance/applications/wtk/html/ess/
quick-ts.jsp
For more details about HTML Client logons, see the Workforce Central
installation documentation.
Note: If you specify HTTPS (HyperText Transport Protocol Secure) for your
communication protocol on the Web & App Server tab, you must use https://
rather than http:// for the logon URLs. For more information, see “Web &
App Server settings” on page 173.
Logging on with Single Sign-on

If you have single sign-on enabled using SiteMinder, you can access Workforce
Central using the following URL:
http://web_server/instance/logonWithUID
For more information about single sign-on, see “Configuring Workforce Central
to enable single sign-on” on page 346.
Logging on to Workforce Central
Enabling Active X controls and plugins

The Download ActiveX controls and plugins is triggered every time you log on.
The first time you log on after installing, you need to set the Download Active X
control to enabled.
1. In your Internet Explorer Security Internet Options, select Custom Level.
2. In the Security Settings dialog box, set ActiveX controls and plug-ins to
settings in keeping with security policies at your site. At minimum, set the
Run Active X controls and plug-ins to Prompt. This will prompt the user for a
given server the first time, and provide a choice to add the server to a list and
avoid future prompts.
3. When you finish, click OK.
Note: Optionally, you can add your server(s) name(s) as a trusted server to
launch Active X controls.
Offline mode
As system administrator, you may need access to the administration functions of
the system, even if the database is offline.
When the system starts in offline mode, you can access the system via a special
offline logon URL for system administrators. You can also use this offline logon
URL if you have single sign-on enabled using Netegrity SiteMinder. To access the
system in offline mode, enter the following URL in your browser:
http://web_server/instance/offlineLogon
where web_server is the name of the machine where the web server software
is installed and instance is the name of the instance, which is wfc by default.
Note that this URL is case-sensitive.
When the system starts in offline mode, the system configuration components are
the only part of the system that are accessible.
Note: If you specify HTTPS (HyperText Transport Protocol Secure) for your
communication protocol on the Web & App Server tab, you must use https://

rather than http:// for the logon URLs. For more information, see “Web &
App Server settings” on page 173.
If the database is offline, the Database tab in System Configuration > System
Information indicates that the database is offline and that no information is
currently available.
Specify the offline mode user name and password using the following settings on
the Security settings tab:
• site.security.authentication.offline.username
• site.security.authentication.offline.password keys
The system encrypts the value of this password.
Managing an instance remotely

You can perform the following tasks remotely using any Web browser:
• Access log reports
• Change system configuration settings
• Restart a server
Configure a visual theme
Configure a visual theme

You can create a custom theme by changing visual properties, including colors
and fonts, and by changing logos and graphics. The properties are defined in a
style sheet, theme.css, and the graphics are stored in a theme folder, along
with the style sheet. All Workforce Central products that are installed with a
Workforce Central application server instance use theme.css and the graphics
in a theme folder.
For detailed information and procedures about creating a custom theme, see
“Create a Custom Theme” on page 179.

Working with passwords

Passwords maintain system security. Within the Workforce Central system, you
can perform the following tasks to manage passwords:
“Change user passwords” on page 28
“Use the single sign-on feature” on page 28
“Set users’ browsers to remember passwords” on page 28
“Change the SuperUser Password” on page 29
Change user passwords

Users can change their password by clicking the Change Password link and
entering the new password in the dialog box.
Use the single sign-on feature

You can set authentication so that a user who logs on to the browser can
automatically log on to Workforce Central without having to re-enter a username
or password. This process is called single sign-on.
For information about configuring your system to use single sign-on, see
“Configuring Workforce Central to enable single sign-on” on page 346
Set users’ browsers to remember passwords

You can set your users’ browsers to remember passwords so that they can log on
more quickly. You can also disable the Password Save.
Caution: Use discretion if you decide to use this capability.
Use the following methods to enable or disable Password Save:

• Setting Password Save With a Deployment Tool — Using this method, you
can simultaneously enable or disable this capability for all the browsers that
use your site. Users cannot change this setting.
Working with passwords
• Setting Password Save From User Desktops — If the browsers are already
on your users' desktops, you need to change this setting at each browser. You
cannot prevent users from altering the setting.
Change the SuperUser Password

The Super User system user account, SuperUser, is the highest-priority system
user account that the Workforce Central system administrator uses. A limited
number of users should know of and use this account.
Note: For an SQL Server 2000 database, SuperUser name is case-sensitive in

offline mode only. Online mode is case-insensitive, for example:
Online mode: SuperUser
Offline mode: superuser
Online mode
To change the SuperUser password in online mode:

1. Log on to Workforce Central at:
http://web_server/instance/logon
where web_server is the name of the machine where the web server
software is installed and instance is the name of the instance, which is
wfc by default. Note that this URL is case-sensitive.
2. Enter the default logon with the user name, SuperUser, and default
password, kronites.
3. Click the Change Password link, enter the user name, the old password, and
the new password.
Make subsequent logins as SuperUser, using the new password.
Offline mode
To change the superuser password in offline mode:

1. Log on to the offline page at:

http://web_server/instance/offlineLogon
where web_server is the name of the machine where the web server
software is installed and instance is the name of the instance, which is
wfc by default. Note that this URL is case-sensitive.
2. Enter the default logon with the user name, superuser, and default
password, kronites.
3. In the Setup workspace, select System Configuration > System Settings.
4. Click the Security tab.
5. Change the site.security.authentication.offline. password value.
6. Click Save.
Make subsequent logins as superuser, using the new password.
Client security
You can set your users’ browsers to remember passwords so that they can log on
more quickly. You can also disable the Password Save. Use the following methods
to enable or disable Password Save:
• Setting Password Save With a Deployment Tool — Using this method, you
can simultaneously enable or disable this capability for all the browsers that
use your site. Users cannot change this setting.
– For Microsoft Internet Explorer browsers, turn on or off the
AutoComplete function using the Microsoft Internet Explorer
Administration Kit Customization Wizard; then deploy the browsers to
your users’ desktops.
• Setting Password Save From User Desktops — If the browsers are already
on your users' desktops, you need to change this setting at each browser. You
cannot prevent users from altering the setting.
– For Microsoft Internet Explorer browsers, turn on or off AutoComplete
through the browser’s Tools > Internet Options > Content tab.
Changing the Relogon session timeout

After a set amount of inactivity, the system times out and prompts the user for the
password. Upon entry of a valid password, the system logs the user back into the
application.
Note: Inactivity is defined as any action that results in direct communication to

the server, such as saving, refreshing, or searching. Changing data on a page
without saving it is not considered activity and will not reset the Workforce
Central timer.
Session timeouts for user inactivity are governed by the application server session
timeout parameter and the Session Timeout grace period. The Session Timeout
grace period represents the number of minutes prior to the application server
session timeout that the Relogon dialog box will appear. The Relogon dialog box
informs the user that the session is about to time out, and prompts for relogin in
order to prevent a time-out. If the user does not respond to the relogin request in
time, the application server session times out, the application closes, and the user
must relogin through the logon screen.
Example 1:
Application server Session Timeout = 30
Session Timeout Grace Period = 1
The Relogon dialog window appears after 29 minutes of inactivity; the application
server session closes after 30 minutes.
Example 2:
Application server session Timeout = 60
Session Timeout Grace Period = 10
The Relogon dialog window appears after 50 minutes of inactivity; the application
server session closes after 60 minutes.

Changing the JBoss Session timeout setting
Note: You should copy the web.xml file (WFC.rootdir/Kronos/jboss/

server/instance/deploy/jbossweb-tomcat50.sar) to a backup
directory before you change the relogon session timeout.
To change the session timeout for the Relogon screen:
1. Stop the application by using the Stop Workforce Central icon.

2. Open the web.xml file in a text editor (WFC.rootdir/kronos/jboss/
server/instance/deploy/jbossweb-tomcat50.sar).
3. Find the following line, where xxx is the number of minutes until session
timeout:
<session-config><session-timeout>xxx</session-
timeout></session-config>
4. Enter a new value for the session timeout.
The default value is 30 minutes. Do not change this value to a zero (0) or a
negative integer.
Note: Changing the parameter will affect all clients that attach to the web/
application server.
5. Delete the comment characters (
comment line, just after the formula for the KPI.
<xsl:variable
name="actualToForecastSalesGreenIfAbove">105
</xsl:variable>
<xsl:variable
name="actualToForecastSalesRedIfBelow">100
</xsl:variable>
The value that is produced by a KPI formula can be:
• Between the two boundaries
• Greater than the "...IfAbove" boundary
• Lower than the "...IfBelow" boundary
To change the threshold boundaries, edit the boundary values. When the outcome
is between these boundary values, the indicator icon in the output is yellow. When
the outcome is above or below the boundary values, the indicator icon is green or
red, depending on how you configure the KPI output.
Changing the icons that indicate KPI status
1. In the KPITable.xsl file, find where the output HTML <table> is

defined.
2. Find the row within this table where the KPI whose icons you want to edit are
defined. The row will reference the label of the KPI.
3. Find the <td> cell that contains the XML that applies the icon to this KPI.
The table cell will look something like this:
<td>
<xsl:choose>
<xsl:when test="$newKpiVariable >
$newKpiNameGreenIfAbove">
<img src="/wpresources/greenlight.gif" alt="Green"/>

</xsl:when>
<xsl:when test="$newKpiVariable <
$newKpiNameRedIfBelow">
<img src="/wpresources/redlight.gif" alt="Red"/>
</td>
</tr>
4. Edit the src attribute for the <img> tags to match the path to the image you
want to use.
Changing the formula that determines a KPI
Find the 

comment line. The formula for each KPI is defined under this heading. The name
of the KPI is included in a comment line before the formula. If you change the
label for a KPI, it is good practice to change the name in the comment line to
match the new label.

<xsl:variable name="actualToForecastSales"
select="100 * ($actualSales div $forecastSales)"/>
Notice that the KPI is defined as a variable: actualToForecastSales. The
formula for the KPI is defined as the value for the "select" attribute. This formula
refers to variables that are defined in the first part of the KPITable.xsl file
(actualSales and forecastSales).
Each piece of data that is returned by the default XML response file is stored as a
variable within the XSL file, under the  comment line. You can add variables, as necessary, within the
context of the new formula.
To change the math in the formula, use the XSL conventions for arithmetic
operations. Refer to www.w3schools.com.

Adding a custom KPI
1. To define the formula for calculating the KPI:

a. In the KPITable.xsl file, copy an existing formula, including the
label for the formula, and paste it at the end of the section labeled  (just
before the HTML <table> tag). For example:

<xsl:variable name="actualToForecastSales"
select="100 *($actualSales div $forecastSales)"/>
b. Change the name in the comment line and the "name" attribute in the
<xsl:variable> tag to reflect the name of the KPI you want to
create.

<xsl:variable name="newKpiVariable" select=
"100 * ($actualSales div $forecastSales)"/>
c. Edit the "select" attribute in the <xsl:variable> tag to use the
formula for the new KPI.
Each piece of data that is returned by the default XML response file is
stored as a variable within the XSL file, under the  comment line. You can add variables,
as necessary, within the context of the new formula.
To change the math involved in the formula, use the XSL conventions for
arithmetic operations. Refer to www.w3schools.com.
The following example shows new variables in a new formula:

<xsl:variable name="newKpiName" select=
"$actualHours - $scheduledHours"/>

2. Create a set of threshold boundaries for the new KPI.

a. Copy an existing set of boundaries and paste it beneath the line of text that
contains the formula that you just defined.
b. Change the name attributes in the <xsl:variable> tag to reflect the
name of the new KPI, and edit the threshold values to reflect the
boundaries for the new KPI.
<xsl:variable name="newKpiNameGreenIfAbove">
nnn
</xsl:variable>
where nnn is a numeric value that represents a percentage.
<xsl:variable name="newKpiNameRedIfBelow">
nnn
</xsl:variable>
where nnn is a numeric value that represents a percentage.
3. Add a new row to the output table and include the new KPI.
a. In the KPITable.xsl file, find where the HTML <table> is defined.
b. Add a new row to the HTML table by copying all the text in a <tr>
element, including the opening <tr> and closing </tr> tags for that
row, and pasting it on the line after the last </tr> tag, before the closing
</table> tag.
c. Edit the contents of that row to include a label for the new KPI:
<tr>
<td>New KPI Name</td>
Include a reference to the variable that stores the new KPI:
<td>
<xsl:value-of select="format-
number($newKpiVariable, '#.0')"/>
</td>
Include the threshold boundaries for the new KPI:
<td>
<xsl:choose>
<xsl:when test="$newKpiVariable >

$newKpiNameGreenIfAbove">
<img src="/wpresources/greenlight.gif"
alt="Green"/>
</xsl:when>
<xsl:when test="$newKpiVariable <
$newKpiNameRedIfBelow">
<img src="/wpresources/redlight.gif" alt="Red"/>
</td>
</tr>
Removing a KPI
In the HTML Table element of the KPITable.xsl file, delete all the text in the
<tr> element for the KPI that you want to remove, including the opening <tr>
and closing </tr> tags for that row.

Configuring the Web Part charts for compatibility with Office Web
Components
Charts in the SharePoint portal are built by Microsoft’s Office Web Components
(OWC) software. Therefore, the XSLT configuration files must match the format
that the OWC expects. The XSL transform files transform the XML data that is
returned by Workforce Central into viewable output (in this case, chart format).
Note the following information about Kronos Web Part charts:
• Two default XSL transform files are used for Productivity Monitor charts: one
for each chart in the retail portal sample page. One uses SalesChart.xsl
and the other uses LaborChart.xsl.
• Two default XSL transform files are used for health care charts: one for each
chart in the health care portal sample page. One uses
HoursSummaryBarChart.xsl and the other uses
HoursSummaryPieChart.xsl.
To create an OWC-compatible XSL file, Kronos recommends that you start with a
chart template in Microsoft FrontPage. Follow these steps to customize a chart
using this method.
1. Create a chart template in Microsoft FrontPage, using the Microsoft Chart
Wizard.
a. Open a new HTML web page.
b. In Microsoft FrontPage, choose Insert > Web Component.
c. In the Insert Web Component dialog box, select Spreadsheets and charts
as the component type and choose Office Chart as the control. Click
Finish.
d. In the Commands and Options dialog box, indicate that the chart data will
come from Data typed in to a data sheet.

e. In the Data Sheet tab, set up the headings for the chart that you want to
add. Include temporary placeholder data for now. For example:
f. Once you have set up the chart, it appears on the screen. Right-click on
the chart and click Toolbar to show the Chart Toolbar.
g. From the Chart Toolbar, you can select options to add a legend to the
chart and to further customize the Commands and Options for the chart
(for example, to define borders, colors, and fills).
2. Copy the markup of the FrontPage chart template into the appropriate file:
SalesChart.xsl or LaborChart.xsl.
a. While the chart is on the screen in Microsoft FrontPage, click the Code
button in the bottom left-hand corner of the screen to show the code view
of the chart.
b. Locate the following line in the code view:
<x:ChartSpace>
Copy from the beginning of this line down to and including the line:
</x:ChartSpace>
c. Paste the copied text into the SalesChart.xsl or
LaborChart.xsl file, replacing the existing text between the <xml>
tags in that file.
d. In the XSL file, use Find and Replace to replace all occurrences of <
with a less than symbol (<).
e. In the XSL file, use Find and Replace to replace all occurrences of >
with a greater than symbol (>).

3. Link the XSL file to data in the XML response file returned by Workforce
Central.
a. In the SalesChart.xsl or LaborChart.xsl file, look for the first
list of placeholder values that you added to the chart wizard.
b. Replace the list of placeholder values with XSL code that extracts the
appropriate data from the XML response file.
For example, if you want the first set of data in the chart to represent the
Actual Labor Volume for each day of the week, enter the following XSL
code to extract the data from the XML response file:
{ <xsl:for-each select="//LaborData[@Date]">
<xsl:value-of select="./@Actual" /> ,
</xsl:for-each>}
This says that for each <LaborData> element in the XML response file
that has a "Date" attribute, return the value of the "Actual" attribute,
followed by a comma. The result is a list that looks like this: {242.5,
194.25, 178.75, 175.5, 189.25, 220}.
Note: You must understand the structure of the XML response file in order to
write XSL to extract data from it. This example assumes that you are using the
standard Kronos Productivity Monitor Web Parts and the XML request file
that is built into the product. If you have customized your XML request file
for use with the Kronos XML API XSLT Chart Web Part, your XSL may be
different. For more information about the relationship between Workforce
Central XML API requests and responses, refer to the Workforce Central
Developers Toolkit Programmer’s Guide.
c. Save the XSL file and make sure that the chart Web Part refers to the
appropriate configuration file.
The next time you view the portal, the chart that you customized will show the
new data, as interpreted by the OWC software.

Advanced configuration of Kronos Web Parts

System administrators perform advanced configuration procedures.
Advanced configuration of Kronos Web Parts requires knowledge about API
request files and XSL transform files.
To make anything other than minor changes to the default files, or to use your own
configuration files, you need a working knowledge of:
• Workforce Central XML APIs
• XML
• XSL
Note: Creating and advanced editing of these files is beyond the scope of this
guide.

Creating custom Workforce Central Web Parts

This section provides:
• Instructions for creating custom Web Parts using the default configuration
files supplied with the pre-configured Kronos Web Parts
• Information about how the Web Parts work
• Basic strategy for creating new Web Parts.
Advanced editing of configuration files requires a working knowledge of:
• Workforce Central XML APIs
• XML
• XSL
How Web Parts work

A Web Part is associated with two file types:
• API request file (.xml file) — Requests information from the Workforce
Central database. For example, a request file can request data from a specified
Genie, based on a specific HyperFind query and a reporting time period. API
request files can make use of any exposed Workforce Central API.
• XSL transform file (.xslt file) — Extracts the data from the associated API
request file and formats the data for viewing.
Note: The Kronos XML API XSLT Chart and Kronos XML API XSLT Table
Web Parts are the only Kronos Web Parts that have XSLT files you can use as a
starting point to create an XSLT file for custom Web Parts. All of the other Kronos
Web Parts consist of a .dwp file which contains the code that creates the Web
Part. The .dwp files cannot be edited.
Any changes that you make to an XML API request file must be reflected in the
XSL transform file, which extracts data from the XML response and formats it for
viewing. You can request data from any part of the Workforce Central suite, as

long as that data is supported by a Workforce Central API. For a complete list of
Workforce Central APIs and information about the relationship between Workforce
Central XML API requests and responses, refer to the Workforce Central Developers
Toolkit Programmer’s Guide.
Note: The WFCGenie API allows you to retrieve data from Workforce Timekeeper
Detail and Rollup Genie types only.
Examples of Web Parts to create

The following are examples of Web Parts that system administrators can create to
retrieve information from the Workforce Central database:
Exceptions — Show whether employees at a business location have the following
exceptions during a specified time period. This information needs to be presented in
table format.
• Unexcused absences
• Missed punches
• Unscheduled time worked
Non-productive Time — Show non-productive time that was taken by employees at
a business location and during a specified time period. This information will be
presented in pie chart format.
Reg and OT Hours Summary — Show pay code hours or currency totals for home
employees at a specific location, during the current pay period.

Basic strategy for creating a Web Part

System administrators perform these tasks.
The high-level strategy for creating a Web Part includes the following tasks:
1. If the Web Part needs to extract data from a Genie, find or create a Genie that
includes the information you need.
2. Find or create a HyperFind query that finds employees who meet the criteria
required for the Web Part.
3. Through function access profiles, grant the appropriate employees access to
view and use the Genie and HyperFind query.
4. Create an API request file that references the Genie and HyperFind query.
5. Create an XSL transform file to format the data.
6. Use SharePoint to drag one of the following Kronos Web Parts onto the portal
page:
– Kronos XML API XSLT Chart — Use this to display the custom Web
Part in chart format.
– Kronos XML API XSLT Table — Use this to display the custom Web
Part in table format.
7. Use SharePoint to configure the Web Part to reference the XML request and
the XSL transform files that you created for it.

Procedures for creating a Web Part based on a Genie

The following instructions are based on creating this Web Part:
Reg and OT Hours Summary — Show pay code hours totals for regular and
overtime hours for home employees at a business location, during the current pay
period. This information needs to be presented in table format.
The table will have a title, three columns (Name, Regular, Overtime), and rows for
each employee returned by the HyperFind query. The Regular and Overtime columns
will hold hours totals for each employee, for the current pay period.
To create this Web Part, perform the following procedures.
Creating the required Genie, HyperFind query, and profiles
Use Workforce Central Setup to perform this procedure:

1. Create a Genie called “Reg and OT Hours Summary” whose column set includes:
– Person Name
– A column for each of the following pay codes: Regular, Overtime
Note: The pay code names are for example purposes. The pay codes can have
different names.
2. Create or edit a Genie profile to include the new Genie.

3. Link the Genie profile to the display profiles assigned to users who need to view
the information in the Web Part.
Because this example requires managers to be able to see all home employees, the pre-
defined “All Home” HyperFind query can be used. By default, all managers can use
the “All Home” query.
If managers needed to view employees based on more specific criteria, you would
create the appropriate query and ensure that each manager’s assigned access profile
allowed access to the query.

Creating a request file for the Reg and OT Hours Summary example
Create an API request file that loads the Genie and HyperFind query, and specifies
a time period for which to view information. You can base the API request file on
an existing request file. The API request files are located in the following
directory:
Kronos.WebParts.Library
Important: Before you edit a configuration file, make a copy of the original file
and give it a new name in case you need to restore the file.
For example, the following illustration shows the default content of the
Genie.xml file that is delivered with the Workforce Central Portal:
<Request action="LOAD">
<WFCGenie GenieName="Pay Period Close"
HyperFindQueryName="All Home">
<Period>
<TimeFramePeriod TimeFrameName="1">
</Period>
</WFCGenie>
</Request>
The values of GenieName and HyperFindQueryName attributes specify

which Genie and HyperFind query is used to retrieve data.
To create an API XML request file for the Pay Code Summary example:
1. Save a copy of Genie.xml to another directory, or save a copy of the file
with a new names. Doing this ensures that you can restore the original file, if
necessary.
2. Open Genie.xml in any text editor.
3. In the file, replace the default Genie and HyperFind query names with Reg
and OT Hours Summary and All Home, respectively.
The value of the TimeFrameName attribute in the TimeFramePeriod
tag determines the type of the time period. For example, the value 1 specifies
the current pay period. Refer to the Workforce Central Developers Toolkit

Reference Guide—Timekeeping for information on using the

TimeFramePeriod tag to specify a time period, specific day, or range of
days.
Note: The Web Parts that you create cannot be connected to the Kronos
Schedule Navigator or Kronos Productivity Monitor Navigator Web Parts that
are supplied by Kronos. Therefore, the information in the new Web Part does
not correspond with the time period in the navigator Web Parts. The time
period is the attribute you specify for TimeFrameName in the XML request
file for the Web Part you create.
4. Save and close the request file with an appropriate, descriptive name. For our
example, you could name the file RegAndOTHoursSummary.xml.

Reading the XML response file for the Reg and OT Hours Summary Web Part
example
The following illustration shows an excerpt of example data returned by the

RegAndOTHoursSummary.xml request file.
<Response Status="Success" ACTION="Load">
<Genie GenieName="Pay Code Summary" GenieType="Detail" HyperFindQueryName="My
Employees"> 1
<GenieColumns>
<GenieColumn ColumnNumber="1" Label="RowKey" Product="N/A" ExtNum="-1"
Width="100"/>
<GenieColumn ColumnNumber="2" Label="Name" Product="WTK" ExtNum="1"
Width="100"/>
<GenieColumn ColumnNumber="3" Label="Regular" Product="WTK" ExtNum="14"
Width="80"/>
<GenieColumn ColumnNumber="4" Label="Overtime" Product="WTK" ExtNum="14"
Width="80"/>
</GenieColumns>
<GenieRows>
<GenieRow Column1="2" Column2="Richie, Betty" Column3="null" Column4="null"/>
<GenieRow Column1="3" Column2="Fryman, Christy" Column3="null" Column4="null"/>
<GenieRow Column1="4" Column2="Diaz, Mercedes" Column3="40:00" Column4="1:00"/>
</GenieRows>
<Period> 2
<TimeFramePeriod TimeFrameName="1"/>
</Period> 3
</Genie>
</Response>
Number Description
1 Information about the columns included in the Reg and OT Hours Summary Genie
for this example. The information includes the labels specified for each column.
2 Names and totals data for the pay codes included in the Genie. The HyperFind
query specified in the request file determines which employees are included in the
response file.
3 Timeframe specified in the request file. In this example, the timeframe is “1,”
which represents the current pay period.

Considerations when creating a transform file for Genie-based Web Parts
This section presents ideas to consider when you create XSL transform files for
Genie-based Web Parts, to make the transform files as efficient and reusable as
possible.
Note: Detailed instructions for creating and editing XSL transform files is beyond
the scope of this guide. Creating and editing XSL transform files requires a
working knowledge of Workforce Central XML APIs, XML, and XSL.
When you create an XSL transform file, consider the following basic guidelines:
• You can use an XSL transform file that is delivered with the Workforce
Central Portal as a starting point, or create a new file. Which method you use
depends on the nature of the Web Part you are creating and how proficient you
are with XSL.
For example, if you are creating a Genie-based Web Part in table format, you
can use Genie.xsl as a starting point for your XSL file. Genie.xsl
shows and formats the maximum number of columns that can be included in a
Genie.
• If you will create multiple Web Parts that contain varying numbers of columns
or types of data, but use the same basic format (table or chart), include logic in
the transform file so that it can be used to format response files for all similar
Web Parts.
For example, the Reg and OT Hours Summary Web Part example is a Genie-
based table that contains four columns of hours totals data. You want to create
another Genie-based Web Part that shows employee exceptions (for example,
missed punches and unexcused absences). Although these Web Parts have a
different number of columns and the response file returns “true” or “false”
values for exceptions, instead of hours totals, the same transform file can be
used for both Web Parts.
The example XSL transform file in this section demonstrates this capability.

Creating an XSL transform file for a custom Web Part
Kronos provides three default XSL files that you can use as templates to format
the Genie data. You can either make a copy of the XSL file that best serves as a
starting point for the custom Web Part, or create a new XSL file.
The three default XSL files that Kronos provides are:
• Genie.xsl — Shows all the columns from the specified Genie
• PayPeriodCloseTable.xsl — Shows a select number of columns
from the Pay Period Close Genie
• PayPeriodCloseChart.xsl — Shows a chart that contains the
percentage of excused and unexcused absences from the Pay Period Close
Genie.
To create an XSL file for the Reg and OT Hours Summary example, perform the
following steps:
1. Make a copy of the Genie.xsl file and save it with an appropriate
descriptive name. For example:
– If you are going to create an XSL file that can be used only for the Reg
and OT Hours Summary Web Part, you could name the XSL file
RegAndOTHoursSummary.xsl.
– If you are going to create an XSL file that can be used to format a variety
of Genie-based table Web Parts, you could name the file
GenieTableWebParts.xsl.
2. Edit the content of the file to format the content of the Web Part. For general
guidance, refer to “Considerations when creating a transform file for Genie-
based Web Parts” on page 281
Important: Remember that the XSL file must include logic to handle all data
that appears in the corresponding XML response file. If you make changes to
the XML request file that changes the data returned in the corresponding
response file, you must update the XSL file to handle the changes.

3. Log on to the SharePoint site as an administrator and perform the following

procedure:
a. Add the Kronos XML API XSLT Table Web Part that comes with the
Workforce Central Portal, to the appropriate portal page. This Web Part is
the initial template for the Web Part.
b. Click the down-facing arrow at the top, right-hand corner of the Web Part
to change and select Modify Shared Web Part. If you do not see the
down-facing arrow in the top, right-hand corner of the Web Part, click
Modify Shared Page and select Design this Page; the arrow should
appear.
After you select Modify Shared Web Part, the dialog box for configuring
the Web Part appears at the right of the screen.
c. Click Configuration and enter the names of the XML request file and
XSL transform files in the appropriate text boxes. For our example, the
names of the files are RegAndOTHoursSummary.xml and
GenieTableWebParts.xsl, respectively.
After you finish the configuration, if data does not show in the Web Part, ensure
that the Workforce Central system is running and that you are logged on. When
you are logged on, the new Web Part displays the data for the employees who
were retrieved by the HyperFind query, and for the time frame. The HyperFind
query and time frame are specified in the request file.

Creating a Web Part for non-Genie data
System administrators perform these actions.

Creating a Web Part that displays non-Genie data is similar to creating a Web Part
that displays Genie data. However, the API request file references a different API.
By default, the WfsoXmlApiRequest.xml file requests data from the
ProductivityMonitor API. You can modify the Date and CategoryPath attributes
of the <ProductivityMonitor> tag to filter the data that is returned from
the Productivity Monitor. To return data for a single day, use the
"LoadDrillDown" action instead of the default action, "Load."
You can modify the WfsoXmlApiRequest.xml file or provide your own
XML API request file to retrieve data from Workforce Central.
The XmlApiXsltTable.xsl file works in conjunction with the default XML
request file to transform the returned XML data into table format.
The KPITable.xsl file works in conjunction with the default XML request file
to transform the returned data into KPIs with threshold indicators. Refer to
“Configuring the Productivity Monitor KPIs (retail)” on page 264 for information
about configuring this file.

Creating a Web Part using the Kronos XML API XSLT Chart

Use the Kronos XML API XSLT Chart Web Part to add a Kronos Web Part that
displays data in chart format. You can request data from any part of the Workforce
Central suite, as long as that data is supported by a Workforce Central API. You
choose the data to retrieve, the time period for which to retrieve the data, and the
employees or business locations for which to retrieve the data.
For a complete list of Workforce Central APIs and how to use them, refer to the
appropriate Developer’s Toolkit Reference Guide.
The Kronos XML API XSLT Chart Web Part requires the following configuration
settings:

XML API request file An XML file that requests data from the Workforce Central
database.
XSL transform file An XSL file that transforms the XML data returned by
Workforce Central into viewable output (in this case, in
chart format).
The default XML API request file is WfsoXmlApiRequest.xml. You can

modify this file or provide your own XML API request file to retrieve data from
Workforce Central.
By default, the WfsoXmlApiRequest.xml file requests data from the
ProductivityMonitor API. You can modify the Date and CategoryPath attributes
of the <ProductivityMonitor> tag in order to filter the data that is returned
from the Productivity Monitor. To return data for a single day, use the
"LoadDrillDown" action instead of the default action, "Load."
The XmlApiXsltChart.xsl file works in conjunction with the default XML
request file to transform the returned XML data into chart format. For instructions
on how to set up an XSL transform file for a chart and to design a chart, refer to
“Configuring the Web Part charts for compatibility with Office Web Components”
on page 270.

Note: All changes that you make to the XML request file must be reflected in the
XSL transform file. Refer to the Workforce Central Developers Toolkit
Programmer’s Guide for more information.
Including logic to perform calculations in a Web Part
You can include logic in an XSL transform file to perform mathematical

calculations. Examples include:
• Converting an hours total value that uses hours:minutes format to a decimal
value. For example, changing 5:30 to 5.5 hours.
• Performing mathematical calculations using two or more values that are
returned by the XML request file. For example, multiplying a wage rate by
the number of hours worked.
The following illustration is an excerpt from an XSL transform file for Web Part
that lists employees, their vacation balances, and vacation pay liability. The XSL
contains logic that converts hours totals in hours:minutes format to decimal
format and multiplies a pay code balance by the employee’s wage rate.
In the example, column 6 is the column in the Genie that holds vacation hours
totals for employees, and column 7 holds the wage rates for employees.
<xsl:otherwise>
$<xsl:value-of select="translate(format-number(@Column7 * format-number(concat(substring-
before(@Column6,':'),'.',substring-after(substring-after(@Column6,':') div
60,'.')),'######.##'),'###,###.00'),'NaN','0.00')"/>
</xsl:otherwise>
The calculation includes dividing the minutes portion of each hours total by 60 to
convert minutes to decimal format. Then, the converted hours total is multiplied
by the employee’s wage rate.

Visual theme for the Workforce Central Portal and Kronos Web Parts
Visual theme for the Workforce Central Portal and

Kronos Web Parts
The Workforce Central system allows system administrators to create a custom
visual theme by changing nearly 150 visual properties, including colors, fonts,
logos, and graphics. The properties are stored in a style sheet that is used by all
Workforce Central products that are installed with a Workforce Central
application server instance.
Notes:
• The Workforce Central Portal uses a default Kronos visual theme. If you
change the visual theme of the Workforce Central system, you can apply that
theme to the Kronos portal page that you create using the Workforce Central
Portal.
• If you add Kronos Web Parts to an existing corporate portal:
– The content of the Kronos Web Parts reflects the Workforce Central
visual theme. The visual theme is the default theme for the Workforce
Central Portal, or the Workforce Central visual theme (if you have applied
it to the Workforce Central Portal page).
– Other elements of the Web Parts, such as the title and the border, inherit
the corporate visual theme.

Customizing and creating Web Part Help topics

Each Workforce Central Portal Web Part includes a context-sensitive Help topic
that a user can view by clicking Help on the drop-down menu for the Web Part.
You can customize the information in Web Part Help topics, and create Help
topics for Web Parts you create.
Customizing Kronos Web Part Help topics

You can customize a Kronos Web Part that is delivered with the Workforce
Central Portal. You can also customize the content of the Web Part’s Help topic to
describe the information in the new display. Help topics for Kronos Web Parts are
HTML files.
For example, suppose you changed the Forecast Map Levels configuration setting
for the Kronos Productivity Monitor Navigator Web Part. Now, you want to
update the related Help topic to indicate the number of organizational levels for
which volume data is summarized and displayed in the retail Web Parts.
To customize a Web Part Help topic:
1. Navigate to the following directory:
drive_letter:\Inetpub\wwwroot\wpresources\
Kronos.WebParts.Library\help\locale
where locale is a directory with a numeric name that indicates the language
version of the Workforce Central Portal that is installed. For example, 1033
is English and 2058 represents Spanish.
2. Locate the Help topic to edit. For example, the Help topic file for the Kronos
Productivity Monitor Navigator is called
Productivity_Navigator.html.
3. Make a backup copy of the file and save it with a new name. For example,
ORIGINAL_Productivity_Navigator.html.
4. Open the original Help topic in a text editor.

5. Locate the text in the Help file. The text is located near the end of the file and
is enclosed by <span> tags. In the following example, the bold text is the
text that you can change:
<a name="wp585913"> </a><span
class="pPopupAppend">This Web Part enables you to
specify a date and store location for which the
Productivity Monitor Table and Productivity Monitor
Chart Web Parts provide forecasted, scheduled, and
actual sales and labor information.</span>
Important: Do not alter any other text in the HTML file.
6. Save the file in the original directory.

When you display the Help file for the Web Part on portal page, you will see the
changes.

Creating and linking a Help topic to a custom Web Part

If you create a custom Web Part, you can create a Help topic for the Web Part and
link the topic to the Web Part.
Creating a Help topic
1. Navigate to the following directory:

Kronos.WebParts.Library\help\<locale>
where <locale> is a directory with a numeric name that indicates the
language version of the Workforce Central Portal that is installed. For
example, 1033 is English and 2058 represents Spanish.
2. Open one of the HTML files in a text editor.
3. Use Save As to save the file into the same directory, and with a name that
reflects the content of the custom Web Part.
4. Locate the text in the Help file. The text is located near the end of the file and
is enclosed by <span> tags. In the following example
(Productivity_Navigator.html), the text that you can change is
bold to clarify what you can change in the file:
<a name="wp585913"> </a><span
class="pPopupAppend">This Web Part enables you to
specify a date and store location for which the
Productivity Monitor Table and Productivity Monitor
Chart Web Parts provide forecasted, scheduled, and
actual sales and labor information.</span>
Important: Do not any other text in the HTML file.
5. After you have edited the text, save the file.

Linking a Help topic to a custom Web Part
After you have created the Help topic for the custom Web Part, you must link it to
the Web Part.
1. Add the custom Web Part to the portal page.
2. In the drop-down menu for the Web Part, select Modify Shared Web Part.
3. In the Advanced portion of the dialog box, scroll to the Help Link text box.
4. Enter the path and name of the custom HTML Help topic you created.
5. Close the dialog box.
When you select Help from the drop-down menu for the Web Part, the custom
Help topic you created appears.

Troubleshooting
In general, Workforce Central Portal users can access the same information using
the portal as they can when they use the full Workforce Central application. Refer
to the table below when the availability of data or the appearance and
functionality of the portal does not match your expectations:
General
Issue Description/Solution
The following error message The user is not authorized to access the Workforce
appears: “XML API Error: The Central XML APIs.
user is not authorized to use Make sure that the API > XML access control point is set
the XML service.” to “Allowed” within the user’s Function Access Profile.
The following error message The user has attempted to log in using a user name or
appears: “XML API Error: The password that contains special characters (for example,
reference to entity ... must end &, %, #, or @).
with the ' delimiter.” Ask a Workforce Central system administrator to change
the user name or password, or both.
The following error message The user does not have access to the data requested in the
appears: “XML API Error: The API, or the value could not be found–for example, the
value for the property is not requested volume driver doesn’t exist.
valid - Name: VolumeDriver, Make sure that the user’s Function Access Profile allows
Value: some_value.” access to the Workforce Manager > Scheduling >
Forecasting access control point.
Make sure that the requested volume driver exists in the
Workforce Central database.
The following error message The user is not authorized to access the data requested by
appears: “XML API Error: the API.
This user is not authorized to Make sure that the user’s Function Access Profile allows
perform the action or it is not a access to the Workforce Manager > Scheduling >
valid action name within the Forecasting access control point.
bean - Bean:
ProductivityMonitor, Action:
Load.”

Troubleshooting
The following error appears The user entered incorrect values or is not authorized to
after a user attempts to log in: use the APIs.
“An incorrect user name or Make sure that the user’s Function Access Profile allows
password was entered. Please access to the Workforce Central XML APIs.
try again.”
The following error appears The name of the link has changed in Workforce Central
during navigation from the since the link or tab was configured, or the user does not
portal to the Workforce Central have permission to access the component in Workforce
application server: Central.
“You do not have permission Compare the value of the MenuText attribute in the Web
to access the requested Part’s configuration file with the text of the same link in
resource.” the Workforce Central navigation menu. These values
must be the same.
Make sure that the user’s access profile allows access to
the selected Workforce Central component.
A prompt for a user name and The Web browser’s security setting is not allowing the
password appears when the request.
user clicks on a tab. Add the Workforce Central application server URL to
the list of sites in the local intranet zone:
In the Internet Explorer window, select Tools > Internet
Options. In the Security tab, click Sites. If necessary,
click the Advanced button and then enter the Workforce
Central application server URL (for example, http://
application_server_name) and click Add.
Blank or unexpected columns A Genie column number has changed since the Web
appear in a Web Part that Part’s XSL transform file was configured. This results
contains Genie data. from a change to the Genie column set in Workforce
Central Setup.
Modify the XSL transform file to reflect the new Genie
column set.

The following error message The name of the Genie has changed since the Web Part’s
appears: “XML API Error: The XSL transform file was configured. This results from a
value assigned to the property change to the Genie name in Workforce Central Setup.
could not be found - Name: Modify the XSL transform file to reflect the new Genie
GenieName, Value: name.
some_value.”
The user cannot delete an When Workforce Central Portal is accessed using certain
existing Web Part page. versions of Internet Explorer installed on a Windows
The user cannot edit any Web 2003 Server, security issues can occur. Some versions of
Parts on an existing Web Part Internet Explorer are for use only on server operating
page. systems, and therefore are configured differently from
browsers on desktop operating systems.
Kronos recommends viewing the Workforce Central
Portal from a web browser that is installed on a desktop
operating system.
The count of notifications in The count in the Kronos Process Manager Inbox Web
the Kronos Process Manager Part represents all tasks associated with the user. By
Inbox Web Part is different default, the Workforce Central Inbox in the full
from the count in the application shows only Active tasks from the last 30
Workforce Central Inbox. days. You can modify the number of days included in the
count by editing the following property:
wba.wf.tasklist.defaulttaskdays
The following error appears in If you are upgrading to Workforce Central version 5.2
the Workforce Central Portal and Workforce Central Portal version 5.2, and you have
components: customized any XML calls to the Genie API, you must
“Cannot create the object change the name of the API in the XML request files
Genie.” from Genie to WFCGenie.

Troubleshooting
SharePoint
Attempting to navigate to the The XML syntax in the web.config file is invalid.
Workforce Central Portal site Make sure that all the tags in the file are balanced with
URL causes an application opening and closing tags, and that each tag is nested
error that references the properly.
web.config file.


Appendix A
Predefined Data
Kronos provides predefined data to simplify the task of configuring your system.
These values help you to configure your system quickly. You can modify some
predefined data, such as the default logon profile. You cannot modify other
predefined data, such as labor levels. See the Workforce Central Setup online
Help for information about working with the predefined data.
This appendix describes the following predefined data:
• “Workforce Genies” on page 298
• “HyperFind query” on page 301
• “Workforce Genie profile” on page 302
• “People” on page 303
• “Logon profiles” on page 304
Appendix A Predefined Data
Workforce Genies
To access Workforce Genies:
1. In the Setup workspace, select Display Preferences > Workforce Genies.
This opens the list of Genies on your system.
Note: The Genies that appear in the list depends on the Workforce Central
suite add-on products installed at your site. For example, if Workforce
Activities is not installed, the Activity Genies do not appear; if Workforce
Attendance is not installs, Attendance Genies do not appear, and so on
2. Click one of the following Workforce Genies. A <name> Genie window

opens and lists the predefined entries.
Workforce Genie Predefined Entry

Accrual Detail Accrual Reporting Period
Detail Activity Employee Detail
Activity Employee Status
Activity Event Details
Attendance Genie
Biometric Status
Current Event Details
IS Summary
Orphaned Event Details
Pay Period Close
Reconcile Timecard
Shift Close
Shift Start
Schedule Group Detail Schedule Group Assignment
Roll-up Activity Event Rollup
Schedule Group Roll-up Schedule Group Roll-up
QuickFind QuickFind
Schedule Editor Schedule Editor

Workforce Genies
Workforce Genie Predefined Entry

Schedule Assistant Schedule Assistant
Schedule Planner Schedule Planner
Leave Case Detail Leave Cases
Leave Hours
3. To access one of the following predefined Genies, click the name on the list
page. You can edit predefined Genies, which are described in the following
table.
Predefined Values Values Set for This Genie

IS Summary • Default HyperFind Query is All Home.
• Default Time Period is Current Pay Period.
• Column Set is IS Summary.
Pay Period Close • Default HyperFind Query is All Home.
• Default Time Period is Previous Pay Period.
• Column Set is Pay Period Close.
Reconcile Timecard • Default HyperFind Query is All Home.
• Default Time Period is Yesterday.
• Column Set is Reconcile Timecard.
Shift Close • Default HyperFind Query is All Home.
• Default Time Period is Today.
• Column Set is Shift Close.
Shift Start • Default HyperFind Query is All Home.
• Default Time Period is Today.
• Column Set is Shift Start.
Schedule Group • Default HyperFind Query is All Home.
Assignment • No Default Time Period is selected.
• Column Set is Schedule Group Detail.
Schedule Group Roll-up • Default HyperFind Query is All Home.
• Default Time Period is Current Schedule Period.
• Column Set is Schedule Group Roll-up.
Quickfind • Default Time Period is Week to Date.
• Column Set is Quickfind.

Predefined Values Values Set for This Genie

Schedule Editor • Default HyperFind Query is All Home.
• Default Column Set is Schedule Editor.
• Default Interval is Daily Intervals.
Schedule Assistant • Default HyperFind Query is <None>.
• Criteria Set is Eval Rule Set Group Default.
• Column Set is Schedule Assistant.
Schedule Planner • Default HyperFind Query is All Home.
• Default Main tab is Employee.
• Column Set is Scheduler Planner.
• Default Schedule Assistant tab is Schedule Assistant.
• Schedule Assistant is Schedule Assistant.
• Default Interval is Daily Intervals.
Leave Cases • Default HyperFind Query is All Home.
• Column Set is Leave Cases.
Leave Hours • Default HyperFind Query is All Home.
• Default Column Set is Leave Hours.

HyperFind query
HyperFind query
To access the HyperFind query, select Setup > Common Setup > HyperFind
Queries on the navigation bar. The HyperFind Queries window opens and
displays a list of predefined HyperFind Queries, described in the following table.
Predefined Values Definition

All Home This HyperFind query defaults to include a manager’s
employee group and/or Organizational group.
All Home and Scheduled This HyperFind query defaults to include all employees in
Job Transfers the user’s Employee Group and/or Organizational group, as
well as those with jobs that are scheduled in the user’s
organizational group.
All Home and This HyperFind query defaults to include all employees in
Transferred-in the user’s Employee Group and/or Organizational group, as
well as those who are transferred-in to the user’s group.
To add a new HyperFind query, click New on the menu bar. To edit an existing
query, select an entry from the list, then click Edit.

Workforce Genie profile

To access the Workforce Genie profile, in the Setup workspace, select Display
Preferences > Display Profile Building Blocks > Workforce Genie Profiles.
The Workforce Genie Profile window opens and displays the list of profiles on
your system.
To access the predefined Super Access profile, click its name.
Kronos Global Support uses the Super Access profile, which provides access to
all Genies in a specific order. You can edit the predefined Super Access profile.

People
People
The SuperUser person is not accessible. However, to access people other than the
SuperUser:
1. Use QuickFind to select an existing Workforce Employee or Workforce
Manager.
2. With the person selected in the QuickFind workspace, click the People launch
button to access the People Editor.
Kronos Global Support uses the Super Access profile, which provides access
to all settings. You cannot edit the Super Access profile.

Logon profiles
To access Logon profiles, in the Setup workspace, select Access Profiles > Logon
Profile. The Logon Profiles window displays predefined logon profiles.
To view a predefined logon profile, click the logon profile name. You can edit
predefined logon profiles.
Predefined Values Definition

Default This profile has the following settings:
Password
• The password is set to expire in 30 days.
• The minimum length is at least six characters.
• Reuse monitoring is set to remember the previous ten
passwords.
Session Restrictions
• A password change is not required at the next logon.
• Account lockout is enabled and occurs after three failed
logon attempts.
• The lockout duration is set to one minute.
Super Access Kronos Global Support uses the Super Access profile, which
provides access to all settings.
Password
• The password is set to never expire.
• There is no minimum length.
• Reuse monitoring is set to do not keep password history.
Session Restrictions
• A password change is not required at the next logon.
• Account lockout is not used.

Appendix B
System Administration of Process Manager
This appendix contains the following sections:

• “Managing processes with Process Administrator” on page 306
• “Managing tasks in a process using Process Administrator” on page 311
• “Monitoring resources using Process Administrator” on page 317
• “Troubleshooting Process Manager” on page 318
• “Enhancing Process Manager performance” on page 319
Process Administrator enables you to manage the processes that you implement
with Process Designer and Workforce Central across the organization.
Use Process Administrator to manage processes and tasks that are active in your
system.
You can use Process Administrator to do the following:
• View the status of all processes and tasks.
• Abort, delete, and restart processes.
• Abort or reassign tasks, or mark tasks as done.
• View and analyze statistics for processes and tasks.
• Monitor resource workloads.
To start the Process Administrator, select System Configuration > Process
Management > Process Administrator from the Setup workspace.
Appendix B System Administration of Process Manager
Managing processes with Process Administrator

Use Process Administrator to manage all the processes that are active in your
system.
Viewing the status of all processes

To view the status of all processes:
1. From the Process Administrator, click the All Processes tab.
2. Select or clear one or more of the check boxes to filter the list of processes
that is displayed:
Filter Description
Ready Shows all processes that are activated and available but have
not been started by a user. Processes and tasks cannot be both
assigned to a person and in a Ready state. These processes can
be generated with the Event Manager’s pool builder.
Activated-All Shows all processes that have been activated.
Activated-w/Aborted Shows all processes that have be activated and have one or
Tasks more aborted tasks.
Aborted Shows all processes whose root task has a state of ABORT.
Completed Shows all processes that have completed.
Templates Shows all process templates
3. Click the Refresh button on the tab.

4. In the table displayed on the tab, view the following process information:
Column Description
ID The ID of the process.
Process Name The name of the process.

Column Description
App. Unique Key The unique key that is assigned to process templates of the same
type. It is used when the process is designed to reference
templates that are included as subprocesses. It is also used to
ensure that templates of the same type do not have overlapping
effective dates.
State The state of a process in the system:
ACTIVE — the process has been started in the system.
READY — the process template is activated and available but
has not been started by a user, because the process has an
earliest start date that has not yet arrived, or the process has an
instance in the pool.
DONE — the process has finished.
ABORT — the process has been stopped, or aborted. Note that
any aborted task in a process will cause the entire process to
move to the ABORT state.
Aborted Tasks Indicates whether the process contains aborted tasks.
Template ID The ID of the template that was used to initiate the process.
5. After you examine the process information, you can select a process and then
click one of the following functions (some functions may not be available
depending on the state of the process):
– Abort
– Delete
– Restart
– Process Detail
The following sections describe actions that you can perform on processes from
this tab.

Aborting a process
If a process is not working properly or if it needs to be halted, you can use Process
Administrator to abort that process. When the process is ready to resume, you can
use Process Administrator to restart it.
Note that the availability of certain functions depends on the state of the process.
To abort a process:
2. Select the appropriate filtering check boxes and click Refresh.
3. Select the process that you want to stop, or abort.
4. Click Abort and then click Yes in the confirmation message box if you are
sure that you want to abort that process. The screen automatically refreshes to
display the change in status for the process.
Deleting a process
If a process is no longer needed because of some change in your organization’s
business process or if it has been replaced by a revised version, you can use
Process Administrator to delete the unneeded process.
The availability of certain functions depends on the state of the process.
To delete a process:
2. Select the appropriate filtering check boxes and click Refresh.
3. Select the process or processes that you want to delete.
4. Click Delete and then click Yes in the confirmation message box if you are
sure that you want to delete that process or processes. The screen
automatically refreshes to display the change in status for the process or
processes.
To delete a process template:
1. In the Setup workspace, select System Configuration > Process
Management.

2. Click Process Profiles.

3. Under Profile Name, select the profile that you want to edit.
4. From the Process Profiles menu bar, click Edit.
5. Use the Remove button to delete the template from the profile.
6. Click Process Templates.
7. Delete the process template from the Template List.
Note: If a process template is deleted and the processes that use the template exist
in the database, the template is logically deleted. This means that the template will
no longer appear in the Process Templates editor and cannot be included in a
Process Profile.
To delete a logically deleted process template:

1. In Process Administrator, delete all the processes using the template.
2. Delete the process template.
Restarting a process
When a previously aborted process is ready to resume, you can use Process
Administrator to restart it.
Note that the availability of certain functions depends on the state of the process.
To restart a process:
2. Select the appropriate filtering check boxes (include Aborted) and click
Refresh.
3. Select the process that you want to restart.
4. Click Restart. The screen automatically refreshes to display the change in
status for the process.

Viewing process reports

Reports can provide the following kinds of information to help you manage
processes on your system:
• The number of activated, unactivated, completed, and aborted processes.
• How many processes have been run within a certain period of time, which
indicates how many people are using the system.
• How many tasks are assigned to employees, so you can adjust an employee’s
workload by reassigning the tasks to other employees.
To view process reports from the Process Administrator, click the Reports tab and
select the check box to indicate which data you want to see:
Report Description
Summary A count of all processes, by status, and a count of all resources
associated with the processes.
Processes Processed The activation status, along with a count, for all processes.
Resource Workload A list of resource IDs and names along with the corresponding
tasks and statuses: active, completed, or assigned.

Managing tasks in a process using Process Administrator

Use Process Administrator to manage tasks within processes that are active in
your system.
Viewing and changing the status of tasks in a process

To view or change the status of tasks in a specific process:
1. From the Process Administrator, click the Process Details tab.
2. Select the process name.
3. Select one of the following views. Note that you can make changes to tasks in
a process only through the Tabular Details view.
View Description
Tabular Detail A table of all process tasks and their properties. This is the only
view in which you can use the available functions to change the
status of certain tasks. See“Tabular Detail view” on page 312 for
more information.
Graphical Detail A read-only graphical representation based on the process template
in use. See “Graphical Detail view” on page 312 for more
information.
State Analysis A read-only view of the process in plain text. Each line represents a
Detail task and contains the following information:
• Name and ID of the task.
• The state of the task and a brief explanation about that status.
See “State Analysis Detail View” on page 313 for more
information.
XML Detail A read-only view of the process in XML.
Use the XML Detail view to, for example, isolate a problem that is
causing a particular task in the process to fail.
Process A read-only list of resources who are participating in the process.
Resources Use the Process Resources view to, for example, identify a
resource to whom you want to send a message about a particular
task.

Tabular Detail view
The Tabular Detail view provides the following task information:
Field Description
Task ID ID of the task as assigned by the Process Engine.
Name Name of the task.
State One of the following states:
• ACTIVE — A resource is currently working on that task.
• READY — The task is ready but a resource has not yet begun work
on it.
• DONE — The task has been completed.
• ABORT — The task has been aborted.
• PASSIVE — The task is passive in the sense that it will not
execute, by design, because it is the false (“No”) condition of a
Branch task.
Duration Amount of time it took for the task to finish, in milliseconds.
Start date The time at which the task began.
End date The time at which the task finished.
Earliest SD The earliest start date (ESD) at which the task can begin.
Predecessors A list of IDs for tasks that must finish before this task can begin.
Parent ID The ID of the parent task in the task hierarchy within the process.
Template ID The ID of the process template that contains the task.
Graphical Detail view
In the Graphical Detail view, color-coded bars on the tasks indicate the following:
• Blue — The task is ready but a resource has not worked on it.
• Brown/Black — The task is done.
• Red — The task has been aborted.
• Green — The task is active. A resource is currently working on the task.

State Analysis Detail View
Use the State Analysis Detail view to, for example, determine why a particular
task has not been completed.
Changing the status of tasks in a process

To change the status of tasks in a specific process, you use the Tabular Detail view
on the Process Details tab:
3. Select the Tabular Detail view.
4. From this view, you can perform the following actions:
Action Description
Set Done Changes the state of any active task (except a root task) to DONE
Force Done Changes the state of any aborted task (except a root task) to DONE
Force Ready Changes the state of any aborted task (except a root task) to READY
Reassign Allows you to reassign the task to a different resource ID
Properties Displays the properties of the task
The following sections describe each action.
Reassigning a task to another resource
To balance resource workloads and remove bottlenecks from a process, or to

resolve an issue with an aborted task, you may need to reassign a task from one
resource to another. You may also be asked by an authorized employee or
manager to reassign a task if a process template has been configured to prevent
individuals from reassigning their tasks from the Tasks tab of their Inbox during
that particular business process. (See the Workforce Central Process Manager
Programmer’s Guide for specific information about modifying a process template
to control the reassignment of tasks.)

For example, if a resource in a process does not have an assignment in the Reports
To field, the associated task in that process will fail. If you are the administrator
who was assigned in the Business Automation system setting to receive Process
Manager error notifications, you will receive a message about this failed task. You
can then use Process Administrator to reassign the task to an appropriate
individual.
To reassign a task:
3. Select the Tabular Details view.
4. Select the row that contains the task.
5. Click Reassign. (If the Reassign function is not active, it means that you
cannot reassign a task in that state; for example, if the task is ACTIVE.)
6. Enter the ID for the resource that you want to reassign the task to.
7. Click Submit.
Marking a task as done
If an aborted or active task is no longer necessary for the completion of a

particular process and you do not want that task to impede the progress of the
process, you can mark that task as DONE so the process can continue to the next
task.
3. Select the Tabular Details view.
4. Select the row that contains the task and then click one of the following:
– Force Done — Changes the state of any aborted task (except a root task)
to DONE
– Set Done — Changes the state of any active task (except a root task) to
DONE

Process Administrator automatically refreshes the screen to display the status

of that task in the State column as DONE.
Changing the status of a task to READY
If a problem with a previously aborted task has been solved and you want to make
that task available again in the process, you can change the status of that task to
READY.
1. From the Tabular Details view of Process Details tab, select the row that
contains the task that you want to mark as READY.
2. Click the Force Ready button on the menu bar. Process Administrator
automatically refreshes the screen to display the status of that task in the State
column as READY.
Viewing the properties of a task

You can view the properties of a task to help resolve problems with a process. For
example, if a task has aborted, you can use this view to see if there is an error
message.
1. From the Tabular Details view of the Process Details tab, select the row that
contains the task that you want to examine.
2. Click the Properties button on the menu bar. Process Administrator displays
the properties of that task as set in the Process Designer template.
Viewing task statistics for a process

To identify bottlenecks in a process or other problem areas, you can view statistics
for tasks in a specific process. For example, if the statistics show that a particular
task took significantly more time to finish than was originally planned for, you
can modify that task in the process template to either increase the amount of
allotted time or reduce the scope of that task.
To view statistics for tasks in a specific process:
1. From the Process Administrator, click the Process Analysis tab.

2. Select a process from the Template drop-down list on the menu bar.
3. In the table displayed on the tab, you can view the following statistics to help
identify bottlenecks in the process:
Column Description
Task Template ID The ID of the task template.
Task Name The name of the task.
Planned Duration The amount of time allotted to this task when the process
template was designed. This is specified in Process Designer, on
the General Properties tab of the task in the template.
Avg % Time Average percentage of the process execution time it took for this
task to finish.
Avg Time (ms) Average number of milliseconds it took for this task to finish.
Min Time (ms) Minimum number of milliseconds it took for this task to finish.
Max Time (ms) Maximum number of milliseconds it took for this task to finish.

Monitoring resources using Process Administrator
Monitoring resources using Process Administrator

You can monitor and manage the workloads for all resources associated with the
processes in your system by using these previously described Process
Administrator features:
• The Reports tab, described on page 310.
• The Reassign function in the Tabular Detail view of the Process Detail tab,
described on page 313.
For example, if you click the Reports tab and review the Resource Workload data,
you might observe that one resource has many more active (uncompleted) tasks
than another. As a result, several processes are not progressing because that
resource’s tasks have not been completed. After conferring with a manager, you
might be asked to reassign certain tasks from the overloaded resource to a less
burdened resource.
A useful tool for monitoring process resources, especially in a clustered
environment, is the Engines tab. The Engines tab displays the following statistics
to help monitor process resources in a clustering environment:
Column Description
Server Name or IP address of the application server that is running a
Process Engine.
Engine Status Status of the Process Engine on the application server:
“running” or “paused.”
Threads in Use Number of threads in use on the Process Engine.
Total Threads Total number of threads available. This number is determined
by the following system setting:
wba.processengine.threadpoolsize
VM Mem Usage (KB) Kilobytes of memory in use by the Java virtual machine.
VM Total Mem (KB) Kilobytes of memory available for the Java virtual machine.
Click the column name to sort the table on that column.

The data in the columns is refreshed when you click the Engines tab or when you
click the Refresh button at the top of the page.

Troubleshooting Process Manager

The following table summarizes some common process template issues and how
to resolve them:
Problem Solution
User receives the error message “This The user should click Refresh to update his or her
task may no longer be available. Click task list. If the error still appears, an API task has
Refresh to update your task list.” failed. Use Process Administrator to locate the
API failure.
Messages are not being sent to Be sure the E-Mail and Messaging tabs in the
external SMTP e-mail addresses. system settings are configured to send mail to the
SMTP e-mail address.
A process template does not appear in Be sure that you deployed the template from
the Process Templates editor. Process Designer.
Tip: You can also use the WFC.log to troubleshoot. Process Manager
information has the context WBAP.ProcessEngine for Process Engine issues,
and WBAP.Process for non-Engine issues.

Enhancing Process Manager performance

Process Manager includes two ways to enhance performance: clustering and
pooling.
Clustering
Clustering allows multiple Process Engine instances to simultaneously access and
monitor the same set of processes. This is achieved by configuring the Process
Engines to access the same database and coordinate with one another through the
Cluster Manager. Benefits of a cluster include scalability, simplified support for
multiple client application instances, and the ability to implement load-balancing
in process applications via Process Manager.
How clustering works
With clustering, work can be distributed on up to 8 application servers each

running a process engine, depending on how many are needed for your
organization. All of the Process Engines in a cluster connect to the same database
server. Support for clustering includes a Cluster Manager system service, the
ability to start and stop Process Engines as a cluster using Event Manager, and the
addition of an Engines tab to Process Administrator to monitor each engine in the
cluster.
In a clustered environment, process requests from Workforce Central applications
such as Workforce Scheduler are submitted to the local Process Engine on the
application server the request was made from. If a Process Engine is not available
on that server, Cluster Manager will direct the request to an engine on another
application server. Cluster Manager ensures that the request is serviced by one
(and only one) Process Engine to advance the process to the next task that requires
input.
Each application server is eligible (by default) to host the Cluster Manager, based
on the wba.clustermanager.eligible Business Automation system
setting. See “Setting up Cluster Manager” on page 320 for more information.

Setting up Cluster Manager
Cluster Manager is a service that runs on one machine in the cluster. If that
machine should require scheduled maintenance or experience a system failure,
Cluster Manager can run on any of the other application servers as well; the other
Process Engines will automatically register with the new Cluster Manager without
requiring you to restart a server.
Note: You must have a Cluster Manager, even in a single-server environment.
To set up Cluster Manager, you must configure the Workforce Central System
Settings on the machine that you designated as the Cluster Manager during
installation.
The Business Automation tab in System Settings contains properties that allow an
administrator to configure the Process Engine as well as the Cluster Manager.
Those settings include the following:
• wba.clustermanager.eligible — The default setting is true, which
provides failover protection in that any server is automatically eligible to
assume the role of Cluster Manager if there is a system failure. If you want to
exclude particular servers from functioning as the Cluster Manager, specify
false for this setting on those servers.
• wba.rmiregistry.port — The port on which to start the Cluster
Manager.
For more information about the Process Manager system settings, see “Business
Automation settings” on page 99.
Managing the clustered Process Engines
Use the Engines tab of the Process Administrator application to monitor Process
Engines, view individual process instances, and manage the deployment and
pooling of process templates.
Use an Event Manager application to schedule engine pause times and stop and
restart events. An engine pause should be scheduled during peak Workforce
Central server loads, such as payroll processing time. The scheduled engine stop
or restart event coordinates a Process Engine shutdown for all of the Process

Engines in the cluster. Only Workforce Central applications that rely on Process
Manager are affected during this period; other applications will continue to
operate normally.
Process pooling
Process pooling is the ability to configure a preallocated pool of process instances
that are made available for instant retrieval when a user initiates a request. Pooling
allows the system administrator to anticipate heavy process load periods by
preallocating database space for process instances using an event scheduled in an
event manager. Pooling reduces the database CPU load.
The pool size attribute specifies the number of process instances that will be
allocated in advance for this process template when the next pool building event
takes place. The pool building event should be scheduled regularly (such as daily)
during an off peak time.
During the pool building event, all actively deployed process templates with pool
size greater than zero will be instantiated in the database for future use. If the pool
for a given process already exists and is larger than the current pool specified for
that process template, the pool is adjusted down.
During regular operation of the Workforce Central applications, if a request for a
new process instance is made, a preallocated process instance from the pool will
be used. This reduces the response time and database load, because the work to
create a process instance has already been done. The pool is then reduced by one.
If the pool is depleted before the next pool building event, then the standard
process allocation is used.
Setting up process pooling
To set up process pooling:

1. In the Setup workspace, select System Configuration > Process Templates.
2. Select the template that you want to create a pool for.
3. Click Edit.

4. In the Max Pool Size text box, indicate the maximum pool size for the
template. If you do not want to use a pool, enter 0 (zero).
Business Automation and then set the default maximum pool size per server
in the wba.processengine.server.maxpoolsize setting.
For more information about the Process Manager system settings, see
“Business Automation settings” on page 99.
Note: You cannot save a process template on the Process Templates page
whose Max Pool Size value is greater than this Max Pool Size value on the
application server. If the Max Pool Size value on the Process Templates page
and this Max Pool Size system setting are not the same, the Pool Manager will
create template pools whose size is the lesser of the values.
6. Use an event manager application to schedule pool building. Run the pool
builder at non-peak hours to avoid poor performance.

Appendix C
Regional Settings
By default, Workforce Central regional settings support text, date and time, and
currency formats that are appropriate for most North American English-language
environments. In version 6.0, you no longer select languages during installation,
but install languages using a language pack CD.
This appendix provides information about how to implement other languages and
formats.
• “Workforce Central language packs” on page 324
• “Character set support” on page 325
• “Workforce Central instances and regionalization” on page 326
• “How Workforce Central displays regionalized data and text” on page 327
• “Currency support” on page 332
• “Using and modifying predefined names” on page 333
• “Using site-defined text strings in a multilanguage environment” on page 340
Appendix C Regional Settings
Workforce Central language packs

In version 6.0, when you install Workforce Central, the product installs English
language files. If you need other languages, you can install a language pack. The
language pack is a CD that contains a set of language files available for translated
products. The language CD has a single installation program that can install one
or more of the languages on the CD.
After the language CD is installed, a program called Configuration Manager
starts. Configuration Manager enables you to select one or more languages to
deploy to an instance. (Currently, you can deploy many languages to one instance,
but you can configure the instance, using system settings, to run only language.)
Languages are installed onto a server once. You must then configure each instance
individually.
No settings, such as language and country, date and time formats, or display
themes, are modified when the language is deployed. After the installation of the
language, you must then configure the needed system settings to display date,
time, number and currency formats.

Character set support
Character set support

Workforce Central v6.0 supports the Unicode character set, although the
supported languages vary, based on the database version. Regardless of the
databases in use, all supported languages for a database platform can now be set
up in a single database. Separate databases are no longer required for the different
character sets. For example, you no longer need separate databases for Latin 1 and
Latin 2 support.
System settings and driver set up are handled during the installation process. You
must configure settings, such as language and country, date and time formats, and
display themes after installation.
Workforce Central v6.0 supports Unicode setup for all SQL Server and Oracle
databases.
Unicode
Unicode encompasses more than 100,000 characters. The languages and character
sets supported differ, depending on the database. The following table lists the
characters supported by the databases.
Database Characters supported

Oracle 10gR2 All characters within Unicode, except bi-directional (right-to-
left) languages, such as Hebrew and Arabic.
SQL Server 2000 Can be set up using Unicode, however they support only Latin
SQL Server 2005 1, Latin 2, and Latin 9 characters sets.
Oracle 10gR1 Setting up these databases in Unicode allows Latin 1, Latin 2,
and Latin 9 character sets to co-exist in the same database.

Workforce Central instances and regionalization

In a regionalized environment, different configurations for non-U.S. English
instances might be required, depending on the specific conditions. In each of the
following cases, the instance settings connect to a single common database:
• Single Language/Single Country — A company that uses a single language
in a single country, such as Spanish in Mexico, can use one instance. The
instance is set to the appropriate regional settings for the language and
country.
• Single Language/Multicountry — A company that uses a single language in
multiple countries, such as English in the United States and Canada, needs at
least one instance for each country to support the appropriate regional
settings. Each instance is set up to use English as the language, but one
instance has country settings for the United States and the other instance has
country settings for Canada.
• Multilanguage — A company that uses multiple languages in one or more
countries needs at least one instance for each language in each country. For
example, a company that has English- and French-speaking employees in
Canada and English-speaking employees in the United States, uses three
instances (U.S. English, Canadian English, and Canadian French), that
connect to a common database. Users who are connected to the French
instance see the user interface in French, while those connected to the English
instance see the user interface in English. Data entered by users is displayed
as entered, but the time, date, number, and currency are formatted according
to server settings. Sorting is also based on the server’s language and regional
settings.

How Workforce Central displays regionalized data and text
How Workforce Central displays regionalized data and

text
Workforce Central displays various data and text elements differently in:
• “Browser applications” on page 327
• “Reports” on page 329
• “Data collection devices” on page 330
Browser applications
The sections that follow describe how Workforce Central displays various data
and text elements in browser applications.
Themes — In v6.0, system administrators can create a custom theme to change
the appearance of colors and fonts in Workforce Central application pages. The
default theme is Basic. If you need to display multi-byte characters need to be
displayed, change the site.portal.theme.name setting on the Display tab
in system settings to global. To see the new theme, log off, then log on.
Text Display and Online Help — The English or language pack files are
installed on the application server. The text for the GUI is in properties
files.
The text for online Help is in a set of HTML files in the Help directory and its
subdirectories.
To support a language other than the English default, use the following settings to
set the language and country for the appropriate instances:
• site.local.LANGUAGE
• site.local.COUNTRY
Date and Time Data and Display — Date and time data associated with a punch
that was entered using the web originates from the server. Depending on context,
Workforce Central uses the time zone associated with the user’s People record or
the time zone on the Locale tab in system settings.

Date and time data associated with all other actions (for example, audit trail
information) originate from the regional settings of the application server’s
operating system.
To support date formats in a language other than the English default, set the
following properties on the Locale tab in System Settings:
• site.local.DateFormat
• site.local.SHORT_DATE
• site.local.LONG_DATE
• site.local.DAY_MONTH
Notes:
• The order of the day and month must match that of the browser locale.
• If you change the default language and or country, and the long date format of
the language or country you specified is different from the system default, you
must also change the Long Date value to the long date format of the specified
language or country.
If the long date value doesn't match the short date, the calendar displays in
English date format, but the date in each application displays differently than
the long date format. No error message occurs.
For the time display, Workforce Central uses the employee’s Display Profile to
determine whether to display the time in 12-hour or 24-hour format. The default
values for Time and Date display are determined by the country selected in system
settings (site.local.COUNTRY on the Locale tab). You can modify this
information at any time.
Use the 24-hour format or two-letter time markers if the time markers have the
same first letter. For example, in English, you can type 8a to indicate 8 o’clock in
the morning, and 8p to indicate 8 o’clock in the evening. In Hungarian, you must
enter 8de or 8 to indicate 8 o’clock in the morning, and 8du or 20 to indicate 8
o’clock in the evening.
To support time formats in languages other than the English default, you can use
the site.local.TimeFormat setting on the Locale tab in System Settings:

Currency Format — The currency format is based on information in Regional

Settings. If no information is entered in the system settings, the currency setting is
based on the United States. You can use only one currency setting per database.
You can use the following settings for currency on an instance:
• site.local.currency.LANGUAGE
• site.local.currency.COUNTRY
Use site.local.VARIANT and site.local.currency.VARIANT to
specify whether the currency is Euro.
The currency setting determines the view and entry format. Depending on the
language and currency code you’ve chosen, currency appears as follows:
USE English: $1,234.56 (US Dollars)
Canadian English: $1,234.56 (Canadian Dollars)
Canadian French: 1.234,56$ (Canadian Dollars)
French French: 1.234,56€ (Euros)
For additional information about currency settings, see “Currency support” on
page 332.
Number and Amount Formats — The number and amount formats, excluding
currency, are based on the display that is associated with the language and country
installed on the instance. You can change this using site.local.language
and site.local.country on the Locale tab in system settings.
The amount formats for time (for example, durations) are based on the user’s
Display Profile for displaying durations (either HH:MM or HH.hh).
Reports
The sections that follow describe how the system displays various data and text
elements in preconfigured and custom reports.
Text Display — Report file sets are installed in English or the language installed
using the language pack. The language that Workforce Central displays is
determined by the language selected during installation of the language pack for
basic reporting and the browser setting for advance reporting.

Note: All reports use the following font by default: Arial Unicode MS. If this font
is not installed on your system, and you have basic reporting, reports
automatically use a substitute font that is installed, perhaps Arial. If you are using
advance reporting, the browser looks for a Unicode fall-back font on your
machine (minglu). If you have a Unicode font on your machine, it uses that
instead of giving you bad characters.
A substitute font might not provide support for multibyte characters. If you need
to view reports that contain multibyte characters, such as reports in Chinese, make
sure that Arial Unicode MS is installed.
To find out about installing Arial Unicode MS, go to www.microsoft.com and
search “Arial Unicode MS.” Install the font on all client machines and, in the case
of RDLC reports (basic reporting), on the Workforce Central Server.
Date and Time Formats — For displaying time in reports, Workforce Central
uses the format (12-hour or 24-hour) that is specified in the user’s Display Profile.
If no information is available in the user’s Display Profile, the display format is
determined by the settings for time-of-day display in the application server’s
operating system.
The display format for dates in report is depend on report types, if the report is in
RDLC and SSRS report format, the date format base on your browser language
preference of Internet options is displayed. If it is Crystal report, the display
format for dates in reports is determined by the country settings for date display,
in the application server’s operating system.
Currency Format — The format for displaying currency in reports is based on
the report file set that is installed on the instance. The report file set language is
determined by the language that was selected during installation.
Number and Amount Formats — The format for displaying numbers and
amounts (except for currency) in reports is based on the report file set that is
installed on the instance. The report file set is determined by the language that was
selected during installation of the language pack.
Data collection devices
The sections that follow describe how the following data collection devices
display various data and text elements:

• Kronos 4500 Terminal

• Kronos Series 400 terminal
• 150/154 Terminals
Text Display — Data collection devices display text that is already included in
the product, such as error messages, only in English.
Text that you have entered in the database (for example, employee names or labor
level entries) is displayed as you entered it. The following is supported:
• 4500 v2.2 and earlier: Latin 1, Latin 2, and Latin 9 for thick client; Smart
Views are English, French, and Spanish only.
• 4500 v2.3: Unicode, including multibyte, but not bi-directional for both thick
client and Smart Views.
• 400/100 series terminals are ASCII-7 English only
Date and Time Data and Format for Punches Using a Timekeeper terminal
— The Date and Time associated with a punch entered using a Timekeeper
terminal is based on the time zone that is set for the terminal in Data Collection
Manager (DCM).
The display format for the Date and Time that is set for the terminal in DCM.
Currency Format — Data collection devices display currency on terminals in the
format appropriate for the system settings.
Number and Amount Formats — The format for numbers and amounts
(excluding currency) is based on the settings for the terminal in DCM.

Currency support
The Workforce Central database supports a single currency. The display format is
determined by the currency, country, and language settings that are specified in
System Settings. If no format is specified in System Settings, the currency settings
are the Workforce Central default settings, English and United States. The
currency settings determine the display format and entry format.
For example, a U.S.-based company with employees in the U.S. and France uses
two instances (one for U.S.-English and one for French-France) that connect to a
common database. Because the database only supports one currency format, the
company has decided to enter all monetary units in U.S. Collars. Users who are
connected to the French-France instance will still view and enter currency in the
U.S. format (for example, $8.50), and not in the French format (for example,
8,50€).
Kronos recommends that all instances be set to support the same currency format.
If instances are set to support different formats, users on different instances may
become confused about the monetary information they view and enter, and the
monetary amounts might be misconstrued.
For example, a Mexican-American company uses two instances (one Spanish, one
English) that connect to a common database, which stores and displays monetary
amounts in U.S. dollars. If the company sets up the English instance to support
U.S. dollars and the Spanish instance to support pesos, monetary amounts entered
by users in each of these countries will be stored in the database as U.S. dollars. If
a US$500 bonus is entered by a Mexican user as the day’s exchange rate amount
of 4,900 pesos, the amount is recorded and displayed as US$4,900 and could be
paid incorrectly.

Using and modifying predefined names

Workforce Central includes many elements with predefined names, such as the
names of individual Function Access Profiles or reports. If you install a language
from the language CD, the predefined names are automatically translated into the
installed language.
You can modify the text of many of these predefined names. However, if you do,
the translated version displays only the modified name, not the translated name.
Preconfigured names in reports are not translated. For more information, see
“Browser applications” on page 327.
If you change the preconfigured names within one of the predefined elements
without changing the name of the predefined elements, the translation of the
predefined element name remains intact. For example, if you modify the name of
one of the fields in the Time Detail Report, the name “Time Detail Report” is still
correctly translated, but the field name is not.
The following table shows the predefined names and whether you can modify
them.
Element Predefined Name Modifiable?

Data Access All Pay Codes No
Profile All Work Rules No
All Reports No
All Shift Templates No
All Pattern Templates No
All Schedule Groups No
All Availability Templates (Workforce Scheduler No
only)
Empty
Display Profile Default Yes

Super Access Yes


Function Access Default Yes
Profile IS Yes
IS Using Organizational Map Yes
Other Manager Yes
Other Manager Using Organizational Maps Yes
Payroll Manager Yes
Payroll Manager Using Organizational Maps Yes
Professional Employee Yes
Professional Employee Using Organizational Maps Yes
Scheduling Manager Yes
Time Stamp and Hourly Employee Yes
Time Stamp and Hourly Employee Using Org Maps Yes
Generic Data All Access Yes

Access Profile
HyperFind All Home Yes

All Home & Scheduled Job Transfers Yes
All Home & Transferred-in Yes
Labor Level Sets All Labor Accounts No

Empty Profile No
Logon Profile Default Yes

Super Access Yes
People SuperUser No
Reports Absent Employees No


Reports, cont. Accrual Balances and Projections No
Accrual Carryover Limits No
Accrual Codes No
Accrual Date Configurations No
Accrual Date Patterns No
Accrual Debit Activity Summary No
Accrual Detail No
Accrual Earned Grants No
Accrual Earning Limits No
Accrual Fixed Grants No
Accrual Policies No
Accrual Pool Balances No
Accrual Probation Periods No
Accrual Profiles No
Accrual Summary No
Accrual Taking Limits No
Actual vs. Schedule by Job No
Actual vs. Schedule by Labor Account No
All Zone No
Badge Numbers No
Biometric Enrollment Activity No
Biometric Enrollment Detail No
Biometric Enrollment Summary No
Bonus/Deduction Rules No
Break Rules No
Combined Pay Codes No
Comments No
Comments By Employee No
Comments By Location No


Reports, cont. Core Hours Rules No
Coverage-Monthly No
Coverage-Weekly No
Coverage Detail - Weekly No
Daily Rest No
Device Assignments No
Device Groups and Device Assignments No
Device Work Rule Definitions No
Device Work Rule Profiles No
Employee Attendance Profiles No
Employee Discipline Levels No
Employee Hours by Job No
Employee Hours by Job (Excel) No
Employee Hours by Labor Account No
Employee Hours by Labor Account (Excel) No
Employee Schedule - Monthly No
Employee Schedule - Weekly No
Employee Sign-off No
Employee Transactions and Totals No
Employee Transactions and Totals (Excel) No
Employees Currently Earning Time (On Premise) No
Exception Rules No
Fixed Rules No
Float No
Function Access Profiles No
Generic Data Access Profiles No
Holiday Credit Rules No
Holiday Credits No
Holidays No


Reports, cont. Holiday Credit Rules No
Home Labor Account Assignment History No
Hours by Job No
Hours by Job (Excel) No
Hours by Labor Account No
Hours by Labor Account with Graph Summary No
Import Errors No
Import Statistics No
Job Configuration No
Labor Levels No
Leave Hours Detail No
Leave Hours Summary No
Leave Hours Summary (Excel) No
Leave Profiles No
Leave Reasons No
Leave Rules No
Leave Types No
List of Activities No
List of Configurations No
List of Field Definitions No
List of Form Profiles (DAP) No
List of Forms No
List of Result Code Profiles (DAP) No
List of Result Codes No
List of Teams No
List of Units of Measure No
Location Schedule - Weekly No
Location Schedule Detail - Weekly No
Majority Rules No


Reports, cont. Missing Employees No
Monthly Location Schedule No
Night Worker No
On Call No
Open Shifts - Monthly No
Open Shifts - Weekly No
Organizational Job Configuration No
Organizational Map Location Types No
Organizational Map Locations No
Organizational Sets No
Orphaned Activity Events No
Overtime Equalization Detail No
Overtime Rules No
Pay Code Data Access Profiles No
Pay Codes No
Pay rule Audit Trail No
Pay Rules No
Perfect Attendance No
Person Attributes No
Person Job Assignment No
Punch Origin No
Report Data Access Profiles No
Rest Breaks No
Rounding Rules No
Schedule by Labor Account - Monthly No
Schedule by Labor Account - Weekly No
Schedule Deviation Rules No
School Calendar Audit No
Single Zone No


Reports, cont. Staffing Efficiency No
Staffing Sheet - Daily No
Staffing Sheet - Weekly No
Staffing Sheet Detail - Daily No
Terminal Rules No
Time Detail No
Timecard Audit Trail No
Timecard Signoff/Approval Audit Trail No
Users Currently Locked Out No
Weekly Activity No
Weekly Working Time No
Work in Process Activity Status No
Work in Process Cost Detail No
Work in Process Cost Detail by Group No
Work in Process Cost Summary No
Work in Process Cost Summary by Group No
Work in Process Time to Complete No
Work in Process Time To Complete Summary No
Work Rule Data Access Profiles No
Work Rules No
Workforce Requirement Analysis No
Yield Detail No
Yield Detail by Group No
Yield Summary No
Yield Summary by Group No
Young Worker No
Zone Rules No

Using site-defined text strings in a multilanguage

environment
If you define individual text strings and you have a multilanguage environment
(that is, if you use a single database and have different languages installed on
different instances), the text strings that you define always appear in the single
language that you used when you defined the text string. For example, if you
defined a pay code named “Sick,” Workforce Central always displays this pay
code as Sick, regardless of the language of the instance.
Kronos suggests the following for customers who use multilanguage
environments:
• For pay codes, work rules, and reports, create duplicate data in each language.
• Use generic data access profiles to segment the data, making it easier for
administrators who make assignments to employees. See the Setup online
Help for more information about generic data access profiles.
• To each user, assign data access profiles in the appropriate language (assign
data access profiles that use English terms to English-speaking employees,
assign data access profiles that use French terms to French-speaking
employees, and so on).
Note: If you want to provide predefined names in multiple languages, provide text
in both languages in the entry. For example, assume that you have a site with
English- and French-language instances, and a labor level that you would call
“Work” in English and “Travail” in French. To accommodate both languages, you
could define the text for this labor level to be “Work - Travail.”

Appendix D
Registry Keys
This appendix contains information about the registry keys that were set up when
your Workforce Central system was installed:
• “Windows registry keys” on page 342
• “UNIX registry keys” on page 343
Appendix D Registry Keys
Windows registry keys

The following registry keys are established during installation of the Workforce
Central system.
• [HKEY_LOCAL_MACHINE\SOFTWARE\Kronos\WFC]
Common Path=C:\Kronos\WFC\kronoscm
Help Dir=C:\Kronos\wfc\help
Install Path=C:\Kronos
• [HKEY_LOCAL_MACHINE\SOFTWARE\Kronos\WFC\config]
Web Server URL=ORASMOKE
• [HKEY_LOCAL_MACHINE\SOFTWARE\Kronos\WFC\Cross
Launch\COMMENTS]
Executable=comments.exe
Function description=Comments Configuration
Function identifier=Comments
Function name=Comments
Home directory=C:\Kronos\wfc\cmnapps
Icon Preference=LAUNCHER
Launcher icon file=comments.ico
Toolbar icon file=none
• [HKEY_LOCAL_MACHINE\SOFTWARE\Kronos\WFC\Cross
Launch\WTK]
Access profile column=none
Executable=nodialog.exe -iconfigApps.icx
Function description=Foo
Function identifier=TKCS
Function name=Timekeeper CS
Home directory=C:\Kronos\wfc\Config
Icon Preference=LAUNCHER
Toolbar icon file=none

UNIX registry keys
UNIX registry keys

Portions of the Windows registry settings are supported in Workforce Central for
UNIX platforms by a new properties file, Registry.properties. This file
resides in the [WFC.rootdir]/wfc/properties directory.
Note: UNIX commands are case-sensitive.
Here is a sample Registry.properties file:

LastPayPeriodUpdate = 0
OracleDBOwner = TKCSOWNER
SequencePreallocationSize = 100
SqlTrace = false
SqlTraceFile = sql.txt
WebServerURL = cnortonnt3
ServicePack = 4.1.1
Explanation:
LastPayPeriodUpdate: The Background Processor will update this number,

but it defaults to 0.
OracleDBOwner: Required because of multiple instance database
deployment.
SequencePreallocationSize: The number of rows in the database’s sequence
table that an application will capture at a time.
SqlTrace: If true, the database calls will be written to the SQL trace file. If
false, the database calls will not be recorded.
SqlTraceFile: The name of the SQL trace file.
WebServerURL: The Web server used for Background Processor
authentication.
ServicePack: A string used by Workforce Central Setup.

Appendix D Registry Keys

Appendix E
Single Sign-On
You can set authentication to allow users to log on to Workforce Central

automatically without having to re-enter a username or password after they have
logged onto their browser. This process is called Single Sign-on.
To set up Single Sign-on, perform the following procedures:
• “Configuring Workforce Central to enable single sign-on” on page 346
• “Configuring SiteMinder” on page 347
Appendix E Single Sign-On
Configuring Workforce Central to enable single sign-on

To configure Workforce Central to enable single sign-on by using Computer
Associates’ eTrust® SiteMinder®:
1. Log on as SuperUser.
Security.
3. On the Security tab, do the following:
a. Set site.security.singlesignon to true
b. Set site.security.singlesignon.module to
com.kronos.auth.SSOSiteMinderSubject
c. Set site.security.singlesignon.module.properties to
WFC.rootdir/wfc/properties/
SSOSiteMinder.properties
4. In SSOSiteMinder.properties, do the following:
a. Set sso.log.file to
WFC.rootdir\wfc\logs\SSOSiteMinder.log
b. Set sso.log.level to DEBUG.
c. Set sso.principal.key to what identifies the users credentials. The default
is SMUSER.
5. In WFC.properties, set com.kronos.wfc.wfp.security.logoffurl to
/wfc/html/kronos-sso-restart.jsp
6. Verify that the ISAPI SiteMinder Agent Filter precedes the ISAPI JBoss
Filter. You can verify this using the Microsoft Management Console.
7. Configure SiteMinder to work with Workforce Central.

Configuring SiteMinder
Configuring SiteMinder
This section assumes that you have SiteMinder installed, and that you understand
basic SiteMinder configuration. For more information about configuring
SiteMinder, see the SiteMinder documentation.
To configure SiteMinder:
1. Use the SiteMinder Policy Server to create authentication schemes for
Workforce Central (WTK).
a. Create an anonymous authentication scheme named WFCAnon.
For example, WFCAnon contains “ou=People, dc=Kronos, dc=com” for
the User DN.
b. Create a basic or form authentication scheme named
WFCFormAuthentication
2. Use the SiteMinder Policy Server to create realms for Workforce Central, in
your policy domain.
a. Create a realm for Workforce Central non-logon URLs named
WFCRealm
Set the resource Filter to /wfc/ and the authentication scheme to
WFCAnon
b. Create a realm for Workforce Central logon URLs named
WFCLogonRealm
The WFCLogonRealm should be a sub-realm of WFCRealm. Set the
resource Filter to logonWithUID and the authentication scheme to
WFCFormAuthentication
3. Use the SiteMinder Policy Server to create rules for Workforce Central.
a. Create a rule that will handle all non-logon WFC URLs in the WFCRealm
named WFCAllowAllRule
Set the effective resource to the wildcard character *, select the Perform
regular expression pattern matches check box, set the Actions button to
Web Agent actions, and select all types of HTTP methods (Get, Post, and
Put).

Appendix E Single Sign-On
This rule activates for all non-logon WFC URLs accessed by the HTTP
methods Get, Post, and Put. Since this rule is part of the WFCRealm, it
uses anonymous authentication. Therefore, all WFC URLs are passed
through WFC without an authentication check by Siteminder. WFC only
allows access to protected non-logon URLs by previously authenticated
users.
b. Create a rule that will handle all logon WFC URLs in the
WFCLogonRealm named logonWithUIDRule
Set the effective resource to the wildcard character *, select the Perform
regular expression pattern matches check box, set the Actions button to
Web Agent actions, and select all types of HTTP methods (Get, Post, and
Put).
This rule activates for all logon WFC URLs accessed by the HTTP
methods Get, Post and Put. Since this rule is part of the
WFCLogonRealm, it uses basic or form authentication. Therefore, access
to all logon URLs are redirected to the form identified in
WFCFormAuthentication. All users are prompted for their credentials,
username, and password.
If SiteMinder authenticates a user accessing this logon URL, it informs
WFC that this user has been authenticated.
4. Use the SiteMinder Policy Server to create policies for Workforce Central.
a. Create a policy for Workforce Central non-logon URLs named
WFCAllowAllPolicy
Configure this policy to contain the WFCAllowRule and your LDAP
users that you want to access Workforce Central.
b. Create a policy for Workforce Central logon URLs named
AllowLogonWithUIDPolicy
Configure this policy to contain the logonWithUIDRule and your
LDAP users that you want to access Workforce Central.

Appendix F
Diagnostic Tools
The diagnostic tools are designed to assist in diagnosing run time, Workforce
Central Web server, and services errors.
Note: Some of the diagnostic tools require you to have the JRE Plug-in installed

• “Diagnostic Tools user interface” on page 350
• “Diagnostics Tools and usage” on page 351
Appendix F Diagnostic Tools
Diagnostic Tools user interface

To start the diagnostic tools, double-click the diagnostic tools icon. The
Diagnostic Tools Logon screen appears.
Diagnostic Tools logon screen

The first time that you log on to the Diagnostic Tools main menu, you must:
1. Enter the Superuser user name in the Enter User Name box.
2. Enter the Superuser password in the Enter Password box.
3. If your server uses SSL connection, select the SSL check box.
4. Click OK.
Launching a specific application

After you enter information in the logon screen and click OK, the Diagnostic
Tools main window appears. This window contains two panes.
• The left side of the window displays a tree-type structure with folders that
contain the different diagnostic and troubleshooting tools.
• The right side of the window displays instructions and information about a
selected diagnostic tool. At the bottom of the right pane is a Launch button, to
start a selected diagnostic tool.
To use a specific diagnostic tool:
1. Select the primary host name in the upper left-hand corner in the left pane.
2. Click the tool name in the left pane.
3. Click Launch at the bottom of the right pane.

Diagnostics Tools and usage

The diagnostic tools for Workforce Central (WFC) include:
• SMTP Mail Server
• SMTP Mail To Launcher
• Shift Builder
Running the SMTP Mail Server Diagnostic Tool

The SMTP Mail Server Diagnostic Tool validates SMTP connectivity.
To run the SMTP Mail Server Diagnostic Tool:
1. In the left pane of the Diagnostic Tools main window, select
SMTPMailServerDiagnostic from the email folder.
2. Click Launch. The STMPMailServerDiagnostic dialog box appears.
3. Enter values into each box:
– FromEmail — Enter the From e-mail address.
– SMTPHostName — Enter the mail server SMTP. The mail server SMTP
is listed in the site.email.smtp_url key in Workforce Central
System Configuration > System Settings > Email.
– ToEmail — Enter the To e-mail address.
– Subject — Enter a test subject.
– Message — Enter a test message.
4. Click Start.
The diagnostic tool sends an e-mail to the address listed in the ToEmail box
and lists the results in the Results box.
Running the SMTP Mail to Launcher Diagnostic Tool

The SMTP Mail to Launcher Diagnostic Tool provides the capability to test and
qualify the customer’s client e-mail software. Some Workforce Central

applications launch the customer’s e-mail client using the W3C3 e-mail to url
syntax. Some e-mail client software packages, such as Novell, do not support the
latest W3C e-mail to url format and do not work correctly with the Workforce
Central product.
Note: This tool can only be run if the Diagnostic Tools client setup is installed at
the Workforce Central server.
To run the SMTP Mail to Launcher Diagnostic Tool:

SMTPMailToLauncher from the e-mail folder.
2. Click Launch. The MailToTester page appears.
3. Fill in the appropriate information:
– To — Enter the To e-mail address.
– Subject — Enter a test subject or accept the default.
– Body — Enter a test message.
4. Click Launch.
The user’s e-mail client opens. If the e-mail client is displayed with the same
information that appears on the MailToTester page, then the application works
correctly.
5. In the e-mail client application, click Send.
This validates that the information is parsed correctly and that the e-mail is
being sent to the individual designated in the To: box.
Running the Shift-Builder Diagnostic Tool

The Shift Builder diagnostic tool logs onto Workforce Central and checks:
• The ScheduleProc database table record count
• The SchedPatrnDate next run date database table
• For failed shiftbuilder employees in the database
• The WtkGlobalSettings.properties file, for XML user/password

• The WPKSite.properties file, for Event Manager key and values

To run the Shift-Builder diagnostic tool:
ShiftBuilderDiagnostic from the shiftbuilder folder.
2. Click Launch. The ShiftBuilderDiagnostic dialog box appears.
3. Click Start.
The buttons at the bottom of the ShiftBuilderDiagnostic dialog box disappear
while the tool is running.
The diagnostic tool lists the results in the text boxes. A restart button appears
when the tool is finished running.
The diagnostic tool lists the results in the text boxes as in the following table:
Text box Description

ScheduleProc Returns the number of Shift Builder tasks that have not yet been
(count) completed. There are three types of Shift Builder tasks:
• A schedule group may exist that needs to have shifts built for it.
• An employee may have an individual schedule pattern and needs to
have shifts built for that pattern.
• An employee may be added into a schedule group. In this case, the
shifts that the employee inherited from the group need to be built.
If the value in the ScheduleProc(count) text box is zero (0), the Shift
Builder has finished running and has no tasks left to complete. If the
value is greater than zero, then the Shift Builder is currently running,
or the Shift Builder has stopped running, but was unable to complete
all of its tasks.
SchedPatrnDate Designates the date and time after which no shifts have been built. The
user cannot call up an editable Schedule Editor for any date after the
one designated in the SchedPatrnDate text box.
To the right side of this text box is a zero (0) or a one (1).
• A zero indicates that the Periodic Shift Builder will not be run on
the next startup of the system, unless the
AlwaysBuildShiftsOnStartup property has been set.
• A one indicates that the Periodic Shift Builder will be run on the
next startup of the system.


FailedEmployees Lists the employee IDs of any employees who failed to run in the Shift
Builder. For example, if a schedule group failed to process properly,
the IDs of all the employees associated with that schedule group are
listed.
WtkGlobal Lists the encrypted username and password that is used to log on to the
Settings Workforce Central server. The Event Manager can have problems if
the XMLUSER username and password defaults have been changed in
this location. The username and password that are returned in the
WtkGlobalSettings field must match the username and password that
appear in the USERACCOUNT table.
WPKSite(Event Lists the site.eventmanager.enabled.required key. This should be set to
Manager Info) true in order for the Shift Builder to run through this server’s event
manager. This property is found in System Configuration > System
Settings > Event Manager.


ShiftBuilder The following properties are listed:
(properties) • site.service.ShiftBuilder.AlwaysBuildShiftsOnStartup — If this
property is set to true, the periodic shift builder is run every time
the server starts up. This is set to true by default, for KDEMO
databases. This property is found in System Configuration >
System Settings > Service.
• Global.WtkScheduler.ShiftBuilderGovernor.Active — If this
property is set to 1, a limit is placed on the number of days
populated by the periodic shift builder. The default value for this
property is 1. This property is found in System Configuration >
System Settings > Global Values.
• Global.WtkScheduler.ShiftBuilderGovernor.Days — This
property designates the maximum number of days populated by the
periodic Shift Builder, if the
global.WtkScheduler.ShiftBuilderGovernor.Active key is set to 1.
The default value for this property is 30 days. This property is
found in System Configuration > System Settings > Global
Values.
• Global.WtkScheduler.ShiftBuilderThreads.Max — This
property designates the maximum allowed number of concurrent
periodic shift builder threads. The default value is 5. This property
is found in System Configuration > System Settings > Global
Values.
• Global.WtkScheduler.MaximumDaysInFutureToCreateShifts
— This property designates the maximum number of future days
for which shifts will be populated, starting with the current day.
The default value is 270. This property is found in System
Configuration > System Settings > Global Values.


Index
A clustering
monitoring resources 317
access control points
Process Engine 317
Messaging system 47
color
Process Manager 47
select for custom theme 181
Active X
specify custom colors in images 189
enabling 25
configuration settings
All Servers system information 55
before editing 94
Applications system information 57
editing 95
archiving system log reports 83
creating 317
Audit system settings 98
custom Web Parts 274 to 286
authentication
considerations for transform files 281
LDAP default method 164
creating non-QuickNav-based Web Parts 284
OTHER 165
creating QuickNav-based Web Parts 277 to
proprietary 163
283
Windows Integrated authentication 164
creating with the XML API XSLT Chart 285
WinNT, multiple domains 163
examples 275
WinNT, single domains 164
including calculation logic in Web Parts 286
strategy for creating 276
B customization
Background Processor create custom theme 179
employees excluded 58, 59
workspace 58 D
Business Automation system settings 99
data access profiles
delegates 51
C Data Source system settings
Clock Synchronize system settings 105 adding 108
Cluster Manager 44 overview 107
about 319 database
setting up 320 deleting a report 63
displaying a report 63
Index
report display 62 E
report status 61
e-mail
running a report 63
available notifications 40
switching databases 110
diagnostics 351
system information 60
multi-instance environment configuration 37
system settings 109
notification types 39
viewing a report 63
system settings 117
working with reports 63
employees excluded
database reports
retroactive pay calculation 59
available reports 60
totals calculation 58
creating DRD files 63
Engines tab
deleting 63
Process Administrator 317
Display workspace 62
Enterprise eTIME
displaying 63
software components 36
DRD creation guidelines 65
Enterprise eTIME Portal
running 63
adding and connecting Web Parts 249 to 254
viewing 63
changing ADP-specific Web Part
delegate authority
settings 258
data access profile 51
changing Web Part labels 260
using 50
changing Web Part titles and appearance 257
deleting a logically deleted process
configuring charts for OWC
template 309
compatibility 270 to 272
deleting a profile 317
configuring health care Web Parts 262 to 264
deploy
configuring KPIs 264 to 269
custom theme 195
creating a visual theme 287
diagnosis
creating custom Web Parts 274 to 286
run time 349
creating Help for custom Web Parts 290
service 349
customizing ADP Web Parts 257 to 273
Web server 349
customizing sample portal pages 255
diagnostic tools
customizing Web Part Help topics 288
Shift-Builder Diagnostic tool 352
linking Help to custom Web Parts 291
SMTP Mail Server Diagnostic tool 351
match suite custom theme 196
SMTP Mail to Launcher Diagnostic tool 351
page configuration options 245
starting 350
purpose 244
Display system settings 116
sample portal pages 245, 247
DRD files
troubleshooting 292
creating 63
using the ADP Web Part page template 256
guidelines for creating 65
Web Parts 245 to 247
duplicating a profile 317
environments
multi-instance 36

Index
Event Manager L
multi-instance environment configuration 37
LDAP authentication
system settings 120
default method 164
working with system settings 122
Licenses system information 67
Locale system settings 140
F log file gathering
function access profiles collecting files 88
Messaging system 47 gathering files 88
Process Manager 47, 305 listing files to be gathered 86
opening gathered files 89
G overview 85
Global Values system settings 126 log files
Global Values tab archiving system log reports 83
Process Manager settings 46 system settings 145
vacation bidding application settings 46 log on
group edits changing the relogon session timeout 31
clearing results screen 138 enabling Active X 25
multi-instance environment configuration 37 overview 24
system settings 136 single sign-on 24
Log Reports
H filtering 82
overview 76
HyperFind queries
running 82
and Reports To field 48
log reports
archiving 83
I Logging Context system settings 148
images logo
specify colors for custom theme 189 prepare for custom theme 184
logoff timer, changing 165
J logs
Java Plug-in system settings 139 Event Manager 123
K M
key performance indicators Messaging system
configuring 264 to 269 access control points 47
K-mail task system settings 149
and system settings 149 Meters system information 68
KPIs multi-instance environments
configuring 264 to 269 configuration overview 36

Index
configuring E-mail 37 customizing sample portal pages 255

configuring Event Manager 37 customizing Web Part Help topics 288
configuring Group Edits 37 linking Help to custom Web Parts 291
match suite custom theme 196
N page configuration options 245
navigation, offline 25 purpose 244
new process profile 317 troubleshooting 292
Notification server 39 using the ADP Web Part page template 256
predefined data
O Enterprise eTIME QuickNav profile 302
HyperFind Query 301
offline mode 25 logon profiles 304
changing superuser account 29 people 303
online mode Primary Labor Account
changing SuperUser account 29 system information 69
OTHER authentication 165 printers
Overtime equalization enabling 151
enabling in system settings 127 system settings 150
overview 317 printing list of profiles 317
Process Administrator 45
P abort a process 308
People Editor changing status of tasks 314, 315
updating Reports To field 49 changing status tasks 313
pooling delete a process 308
about 321 delete a process template 308
pool building 321 Engines tab 317
setting up 321 marking completed tasks 314
Portal, Enterprise eTIME overview 305
adding and connecting Web Parts 249 to 254 Process Analysis tab 315
changing ADP-specific Web Part Process Details tab 311
settings 258 process status 306
changing Web Part labels 260 reassigning tasks 313
configuring charts for OWC reports 310
compatibility 270 to 272 resource workload 317
configuring health care Web Parts 262 to 264 restart a process 309
configuring KPIs 264 to 269 start 305
creating a visual theme 287 status of all tasks 311
creating custom Web Parts 274 to 286 task statistics 315
creating Help for custom Web Parts 290 viewing task properties 315
customizing ADP Web Parts 257 to 273

Index
Process Analysis tab Process Templates editor 44

Process Administrator 315 overview 317
Process Designer 44 viewing 317
logging on with Windows Vista 44 processes
overview 44 aborted 307
Process Details tab aborting 308
Graphical Detail view 312 active 307
Process Administrator 311 changing task status 313
Process Resources view 311 counts 310
State Analysis Detail view 313 deleting 308
Tabular Detail view 312 done 307
XML Detail view 311 Graphical Detail view 312
Process Engine 44 Process Resources view 311
clustering 317 ready 307
Process Manager restarting 309
access control points 47 State Analysis Detail view 313
activating templates 317 status 310
categorizing process templates 317 Tabular Detail view 312
components 44, 45 task statistics 315
deactivating templates 317 viewing reports 310
Global Values settings 46 viewing status 306
overview 44 viewing task status 311
system settings 99, 305 XML Detail view 311
troubleshooting 318 profiles
upgrading 45 creating new process profile 317
process profiles deleting a process profile 317
creating new 317 duplicating a process profile 317
deleting 317 editing a process profile 317
duplicating 317 printing list of process profiles 317
editing 317 renaming a process profile 317
printing list 317 properties
renaming 317 modifying 34
Process Profiles editor 44, 317 properties files
starting 317 file types 34
process templates groups 34
activating 317 overview 34
categorizing 317 properties validation 97
deactivating 317 property groups 34
deleting 308 proprietary authentication 163

Index
R S
registry keys security
UNIX 343 client 28, 30
Windows 342 overview 28
relogon session timeout password 28
changing Enterprise eTIME session 32 single sign-on 28, 346
changing JBoss session 32 system settings 160
overview 31 server
renaming a profile 317 All Servers system information 55
report terminology 199 logging on and off 24
reports managing remotely 26
concept overview 198 Web and App Server system settings 173
for processes 310 Service system settings
system settings 157 overview 167
terminology 199 settings
Reports tab system configuration 22
Process Administrator 310 severity levels
Reports To field Event Manager log 124
Process Manager configuration 48 single sign-on
updating with People Editor 49 configuring Enterprise eTIME 346
reports, system configuring SiteMinder 347
database report display 62 logging on 24
deleting a database report 63 SMTP connectivity
displaying a database report 63 validating 351
Log Reports 75, 76 SQL Coverage system settings
running a database report 63 overview 169
viewing a database report 63 SQL tracing, enabling 170
resources Startup system settings 171
counts 310 status
viewing workload 317 of processes 310
response file (XML) of tasks 310
reading 280 SuperUser account
Retention Policy Affected Databases changing 29
system settings 152 system administration
Retention Policy Database Setup adding data source names 108
system settings 153 adding printers 151
Retention Policy Options and Tuning changing logoff timer 165
system settings 154 clearing Group Edit Results 138
enabling printers 151
enabling SQL tracing 170

Index
offline mode 25 viewing a database report 63

switching databases 110 working with database reports 63
understanding authentication 163 system security
working with Event Manager 122 authentication 163
System Configuration system settings
Log Report 75, 76 Audit Settings 98
overview 23 before editing 94
Process Profiles editor 317 Business Automation 99
Process Templates editor 317 Clock Synchronize 105
System Settings 91, 93 Data Source 107
system configuration Database 109
overview 22 Display 116
Process Administrator 305 editing 95
system information 53, 54 E-mail 117
system information Enterprise eTIME Portal 116
All Servers 55 Event Manager 120
Applications 57 Global Values 46, 126
Background Processors 58 Group Edits 136
database information 60 Java Plug-in 139
database report status 62 Locale 140
Database workspace 60 Log File 145
employees excluded 58, 59 Logging Context 148
Licenses 67 Messaging tab 149
Meters 68 overview 91, 93
overview 53, 54 Printers 150
Primary Labor Account 69 Process Manager 305
Threads 71 Reports 157
User 73 Retention Policy Affected Databases 152
system log reports Retention Policy Database Setup 153
archiving 83 Retention Policy Options and Tuning 154
filtering 82 Security 160
overview 75, 76 Service 167
running 82 SQL Coverage 169
system reports Startup 171
database report status 61 task buttons 95
deleting a database report 63 Transformation 172
displaying a database report 63 values validation 97
Log Reports 75, 76 Web and App Server 173
running a database report 63 working with 95

Index
T U
tasks UNIX registry keys 343
changing status 313, 314, 315 User system information 73
marking as done 314
reassigning 313 V
status 310 vacation bidding application
viewing properties 315 Global Values settings 46
viewing statistics 315 validate
viewing status 311 SMTP connectivity 351
template categories 317 validation, system settings 97
templates visual theme
activating 317 creating for the Enterprise eTIME Portal 287
categorizing 317
deactivating 317 W
Web Part page for Enterprise eTIME
Portal 256 Web and App Server system settings 173
theme Web Part Help
create custom theme overview 27 customizing 288
create new theme folder for custom Web Part Help topics
theme 180 creating 290
deploy 195 linking to custom Web Parts 291
edit theme style sheet 185 Web Part page template 256
extend to Enterprise eTIME Portal 196 Web Parts
select colors for 180 adding and connecting 249 to 254
specify custom colors in images 189 changing ADP-specific settings 258
test 194 changing labels 260
use custom logo 184 changing titles and appearance 257
theme.css file 185 configuring charts for OWC
Threads system information 71 compatibility 270 to 272
tools configuring health care Web Parts 262 to 264
diagnostic 349 considerations for transform files 281
transform file (XSL file) 282 creating custom Web Parts 274 to 286
Transformation system settings 172 creating non-QuickNav-based Web Parts 284
troubleshooting creating QuickNav-based Web Parts 277 to
Enterprise eTIME Portal 292 283
SQL tracing 170 creating with the XML API XSLT Chart 285
customizing 257 to 273
examples of custom Web Parts 275
how they work 274

Index
including calculation logic in Web Parts 286

strategy for creating 276
Windows Integrated Authentication 164
Windows Vista
logging on to Process Designer 44
WinNT authentication
mulitiple domains 163
single domains 164
workflow notifications
access 42
available notifications 40
notification types 39
overview 39
setting up 41
X
XML response file
reading 280
XSL transform file 282

Index

System Administrators Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Administrators Guide

Uploaded by

Copyright:

Available Formats

Workforce Central ®

An administrator’s guide to the Workforce Central system.

Kronos Workforce Central Suite

Document Part Number: 4703953-001

Published by Kronos Incorporated

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

Document Revision History

Document Revision Product Version Release Date

A Workforce Central 6.0 June 2007

About This Guide

Configuring a multi-instance environment .................................................36

Chapter 2: System Information

Resubmit All People for Account Update ............................................ 69

Chapter 3: Log Report

Chapter 4: Log File Gathering

Chapter 5: System Settings

Workforce Central System Administrator’s Guide 5

Event Manager settings ..............................................................................120

Chapter 6: Create a Custom Theme

Chapter 8: Workforce Central Portal Configuration

Workforce Central System Administrator’s Guide 7

Configuring the Productivity Monitor KPIs (retail) ............................264

Clustering ............................................................................................ 319

Workforce Central System Administrator’s Guide 9

This preface contains the following sections:

Organization of this guide

Workforce Central System Administrator’s Guide 13

Abbreviations and Terminology

Workforce Central System Administrator’s Guide 15

Workforce Central suite documentation

Workforce Central documentation

• Workforce Central Import User’s Guide provides information about setting up

Workforce Timekeeper documentation

Workforce Central System Administrator’s Guide 17

• Workforce Central Process Manager Programmer’s Guide—Timekeeping and

Workforce Record Manager documentation

Developers Toolkit documentation

Workforce Central System Administrator’s Guide 19

Workforce Central infrastructure

System configuration overview

Workforce Central System Administrator’s Guide 23

Logging on to Workforce Central

Logging on with Single Sign-on

Enabling Active X controls and plugins

Workforce Central System Administrator’s Guide 25

Managing an instance remotely

Configure a visual theme

Workforce Central System Administrator’s Guide 27

Working with passwords

Change user passwords

Use the single sign-on feature

Set users’ browsers to remember passwords

Caution: Use discretion if you decide to use this capability.

Use the following methods to enable or disable Password Save:

Change the SuperUser Password

Note: For an SQL Server 2000 database, SuperUser name is case-sensitive in

To change the SuperUser password in online mode:

To change the superuser password in offline mode:

Workforce Central System Administrator’s Guide 29

Changing the Relogon session timeout

Note: Inactivity is defined as any action that results in direct communication to

Workforce Central System Administrator’s Guide 31

Changing the JBoss Session timeout setting

Note: You should copy the web.xml file (WFC.rootdir/Kronos/jboss/