Enterprise eTIME Suite 6.2.17 Service Pack - Home

Enterprise eTIME Suite 6.2.17 Service Pack - Home
Enterprise eTIME Suite 6.2.17
Document Release Date: February 2015
Service Pack Release Notes
Contents
Introduction .................................................... 1
International considerations........................... 3
Product compatibility information................... 3
What’s New?.................................................. 4
Documentation corrections/supplemental
information .................................................. 4
Enterprise eTIME ........................................ 4
Enterprise Scheduler................................. 13
Enterprise Device Manager....................... 15
Enterprise Integration Manager................. 16
Enterprise Activities................................... 17
Installing Service Pack 17............................ 18
Who Should Install Service Pack 17? ....... 18
Installation Considerations ........................ 18
Installing on Windows systems ................. 22
Uninstalling or removing the service
pack from Windows systems .................. 28
Installing on AIX or Solaris systems.......... 31
Uninstalling from AIX or Solaris
systems .................................................. 34
Upgrading a database from 4.x.x through
6.1.x to 6.2 ................................................ 37
Procedure.................................................. 37
Implementation considerations .................... 40
ADP InTouch............................................. 40
Load balancing and QuickGlance
transactions ............................................ 41
Vertically-scaling and device
communication ....................................... 41
Database — Oracle................................... 41
Reports...................................................... 42
Translation and customization .................. 42
Enterprise Activities................................... 42
Enterprise eTIME ...................................... 44
Enterprise Device Manager....................... 45
Enterprise Integration Manager................. 46
Enterprise Scheduler................................. 47
Enterprise Worksheet................................ 47
Known issues............................................... 48
Enterprise eTIME ...................................... 48
Known false error condition ......................... 48
Database changes....................................... 49
Database scripts ....................................... 49
Other database changes ............................. 56
New Device Manager database tables
(introduced with 6.2.7) ............................ 56
Product
compatibility
information
”What’s New?”
Installing Service
Pack 17
Implementation
considerations
Introduction
This document provides information about Enterprise eTIME® suite version 6.2.0
Service Pack 17. ADP recommends that you read this document before you
install Service Pack 17, and that you keep a printed copy with the product
documentation.
This service pack includes the following products:
Enterprise eTIME Accruals
Enterprise Archiver
Enterprise Activities
Enterprise eTIME
Enterprise Attendance
Enterprise Scheduler
Enterprise Integration Manager
Enterprise Worksheet
Enterprise Leave
Enterprise Device Manager
Note: Enterprise eTIME Professional, Enterprise eTIME Manager, and ADP
QuickPunch® are integrated into the Enterprise eTIME suite. They are not
separate products.
This document provides the following information about Enterprise eTIME 6.2
Service Pack 17:
•
Product compatibility information
•
Installation instructions
•
Information about documentation updates and corrections
•
Descriptions of issues that were resolved in the Service Pack.
“What’s New?” on page 4 explains where to find information about new features
in Service Pack 17.
Introduction
Issues Resolved in Service Pack 6.2.17 ..... 59
Database................................................... 59
APIs .......................................................... 59
Enterprise Activities .................................. 60
Enterprise Attendance .............................. 61
Enterprise eTIME ...................................... 61
Enterprise Scheduler ................................ 64
Device Manager........................................ 65
Integration Manager.................................. 65
Appendix: Enterprise eTIME products
and SharePoint on the same server ......... 67
Initial configuration procedure................... 67
Procedure for Microsoft IIS version 7........ 68
Procedure for Microsoft IIS version 6........ 69
Legal statement .......................................... 71
2
International considerations
International considerations
Beginning with version 6.2, the Enterprise eTIME suite of products supports Traditional Chinese language. This language
support is in addition to previously supported languages (French, Spanish, German, Dutch, Simplified Chinese, Brazilian
Portuguese).
Product compatibility information
The following product versions are compatible with Enterprise eTIME 6.2 Service Pack 17.
Important: This table represents compatibility among products that are available on the release date of this
service pack. Check the Release Notes that accompany the latest service packs for add-on products, to see if
they list compatibility with Enterprise eTIME 6.2 Service Pack 17.
Product
Version
Navigator (Next Generation User Interface, or NGUI)
6.2.17
Setup Data Manager
6.2.17
Note: You can use any version of Setup Data Manager (SDM) 6.2
with any Enterprise eTIME 6.2 service pack. However, to take
advantage of all current SDM issue solutions, use the latest released
version of SDM 6.2.
Express Archive
6.3.8
ADP InTouch
1.0.x, 1.1.x, 2.0.x, 2.1.x
ADP 4500
2.1.x, 2.2.x, 2.3.x, and 3.0.x
Note: A-Connect 6.0.x is also compatible with Enterprise eTIME 6.2 Service Pack 17. This allows clients to
continue using A-Connect instead of Enterprise Integration Manager when they upgrade to Enterprise eTIME
6.2 Service Pack 17.
The following table indicates which of the separate product service packs are recommended or required when you upgrade
to Enterprise eTIME 6.2.17. The products listed in the table are delivered with the Enterprise eTIME Service Pack, but they
are not part of the installation of Enterprise eTIME. A product service pack is designated “Required” if the issues that were
resolved are critical for complete and proper functioning of the product.
Product
Required or recommended installation
Enterprise eTIME Portal
_X_ Recommended if you are using Enterprise eTIME Portal
___ Required if you are using Enterprise eTIME Portal
Enterprise Worksheet
_X_ Recommended for all client workstations using Enterprise Worksheet
___ Required for all client workstations using Enterprise Worksheet
SQL Server Reporting Services 2005
(SSRS), 32-bit
SQL Server Reporting Services 2008
(SSRS), 32-bit and 64-bit versions
_X_ Recommended for all client workstations using Advanced Reports. Use the
version that corresponds to the version of SQL Server you are using.
___ Required for all client workstations using Advanced Reports. Use the version that
corresponds to the version of SQL Server you are using.
3
What’s New?
What’s New?
Product
Feature
Enterprise eTIME
“Start Day” setting in display profile for timecards
Note: For information about features that were introduced with earlier 6.2.x service packs, refer to
EeT_NewFeatures_6.2_SPs.pdf that is available at the site that contains these Release Notes.
Documentation corrections/supplemental information
Enterprise eTIME
Correction to “Batch events” online Help topic
The online Help for Enterprise eTIME 6.2.x contains an error in the “Batch events” topic. The following example of a batch
command does not have quotation marks around it:
c:\admin batch\daily\syn cup.bat argument1 argument2
The example should have quotation marks around it because there is a space in the path:
“c:\admin batch\daily\syn cup.bat argument1 argument2”
Corrections to configuration procedure for single sign-on with SiteMinder
(WFM-51475) The System Administrator’s Guide — Enterprise eTIME contains some incorrect information related to
configuring single sign-on with SiteMinder.
•
The following corrections pertain to paths:
–
Step 3b states to set site.security.singlesignon.module to:
com.kronos.auth.SSOSiteMinderSubject
The correct path is:
com.kronos.wfc.platform.security.business.authentication.ssoplugin.SSOSiteMinderS
ubject
–
Step 3c states to set site.security.singlesignon.module.properties to:
installation_directory\instance\properties/ SSOSiteMinder.properties
The correct path is:
installation_directory\instance\applications\wcb\properties\SSOSiteMinder
.properties
•
Step 4 of the documentation refers to ‘SSOSiteMinder.properties’ but does not explain how this file is created. Here
is additional information:
Enterprise eTIME requires a file called SSOSiteMinder.properties, which is not provided by default. Because of
this, you must create it. After you create the empty file, add the following information to the file:
4
Documentation corrections/supplemental information
Set sso.log.file to 1.rootdir\1\logs\SSOSiteMinder.log.
– Set sso.log.level to DEBUG.
– Set sso.principal.key to what identifies the user’s credentials. The default is SMUSER.
If you are using Microsoft IIS, the documentation states that the Default Application Pool should be configured as
Integrate. This is incorrect. It needs to be configured as Classic.
–
•
Correction to definition of single sign-on setting
In the Enterprise eTIME System Administrator Guide, the setting called “site.security.singlesignon.logoffurl“ is incorrectly
defined as “...the logoff URL to be used if single sign-on is enabled...” The setting is not specific to single sign-on. The
correct description is “...the logoff URL to be used.”
Clarification about workflow notification configuration
(WFM-41877) The online Help topic called “Creating Notifications” does not indicate that several of the configuration
options do not apply to Device Manager generic notifications. Device Manager generic notifications include:
•
Device Manager Device Error (device status changes from green/yellow to red error)
•
Device Manager Event Error (scheduled event fails to execute)
•
Device Manager System Error (system status changes from green/yellow to red (error) when any device changes
to red status)
The following options on the Workflow Notifications configuration screen are not applicable to the Device Manager
notifications. They do not apply because the notifications do not concern the employees or manager.
•
Send to employee’s Attendance administrator
•
Send to employee’s Leave administrator
•
Send to employee’s manager
•
Send to employee
Also, the following configuration settings do not apply because there are no subsequent events relevant to the notifications
to trigger more notifications:
•
Re-send every day
•
Re-send every <number of minutes> minutes
•
Do not suppress duplicates
5
Documentation corrections/supplemental information
Revisions to online Help topics
The following text represents revisions to online Help text that was delivered with Enterprise eTIME 6.2.0. If you need to
view these topics in the online Help, refer to this revised text.
Accrual profiles
Use the Accrual Profile table to assign one or more accrual profiles. An Accrual profile contains accrual policies, which
determine how employees accrue their time, money, or both.
If an employee is new, or has no accrual profiles assigned, the table is blank. If an employee has accrual profiles
assigned, they are listed in the table, along with effective dates.
Notes on accrual profiles:
–
–
–
–
–
–
–
–
Time gaps might exist among accrual profile assignments, and can be determined by checking the start and
end dates of the displayed assignments.
When you delete an accrual profile assignment, the previous assignment is not affected. The previous
assignment does not become effective through the deleted assignment's end date. If you want to extend the
previous assignment, change its end date.
Grants from a previously assigned accrual profile expire, even if their “expire-to” codes are not in the newly
assigned profile. If, at some point, you reassign a profile that contains the “expire-to” accrual code, the expired
grants in that accrual code might affect balances accordingly.
You cannot save accrual profile assignments that have overlapping dates.
A selected accrual profile needs both a start date and an end date.
When you delete an Accrual Profile assignment, the previous assignment is not affected. The previous Accrual
Profile assignment does not become effective through the deleted assignment's end date. If you want to extend
the previous assignment, change the end date of the previous assignment.
Grants from a previously assigned Accrual profile will expire, even if their “expire-to” codes are not in the newly
assigned profile. If at some point, you re-assign a profile that contains the “expire-to” accrual code, the expired
grants will be in that accrual code and might impact balances accordingly.
To maintain your current FMLA policies, you need to use the same FMLA-related policy and accrual codes in
all Accrual profiles.
To assign an accrual profile, select a profile, start and end dates, then click Save. Use the plus arrow and X to add or
delete rows.
Full-time equivalency
Full-Time Equivalency is a number greater than 0 and less than or equal to 1 that the system uses in calculating
accruals. You can express Full-Time Equivalency as a percentage or as a ratio of Employee Hours to Full-Time Hours.
For example, suppose a full-time employee works 40 hours per week and you are creating a profile for a part-time
employee who works 20 hours per week. You could express this full-time equivalency as either a percentage (= 50%)
or as a ratio (Employee Hours = 20, Full-Time Hours = 40).
6
Documentation corrections/supplemental information
Cascading profile
Cascading profiles contain cascading policies that define the pay codes used to trigger cascading accrual takings. For
example, a cascading policy that allows the system to take time from both vacation accrual holdings and sick accrual
holdings if an employee does not have an adequate amount of vacation time accrued.
Assign the Cascading profile in the Accruals & Leave workspace. To assign a cascading profile, use the drop-down
arrow in the Cascade Profile field to show or search for a list of cascading profiles.
Leave profile and leave administrator
Leave profiles contain groupings of leave categories. For example, employees working in different states might have
different Leave profiles because of differences in state family or medical leave rules. The profile could reflect the
categories selected for leave cases in each state. A leave profile is required for an employee’s leave case. A leave
administrator is not.
Clarification about workflow notification configuration
(WFM-41877) The online Help topic called “Creating Notifications” does not indicate that several of the configuration
options do not apply to Device Manager generic notifications. Device Manager generic notifications include:
•
Device Manager Device Error (device status changes from green/yellow to red (error))
•
Device Manager Event Error (scheduled event fails to execute)
•
Device Manager System Error (system status changes from green/yellow to red (error) when any device changes
to red status)
The following options on the Workflow Notifications configuration screen are not applicable to the Device Manager
notifications. They do not apply because the notifications do not concern the employees or manager.
•
Send to employee’s Attendance administrator
•
Send to employee’s Leave administrator
•
Send to employee’s manager
•
Send to employee
Also, the following configuration settings do not apply because there are no subsequent events relevant to the notifications
to trigger more notifications:
•
Re-send every day
•
Re-send every <number of minutes> minutes
•
Do not suppress duplicates
7
Documentation corrections/supplemental information
Increased maximum number of Punch Interpretation Rules
(CE-23626) The Enterprise eTIME software now allows users to create up to 256 Punch Interpretation rules. The previous
maximum number of rules that could be created was 16, which is currently stated in the 6.2.0 online Help. Punch
Interpretation rules are created in Setup.
Error in Labor Levels tab topic
(DCS-9415) The online help for the Labor Levels tab of the Transaction Settings Editor contains an error in the instructions
for specifying labor level-related parameters. The text states that the Allow ad hoc check box is selected by default. It is not
selected. It must be selected by the user if the host application has defined ad hoc labor levels.
Column header change in Biometric Status QuickNav
(WFM-32859) In the Biometric Status QuickNav, the column header “Is Enrolled” has been changed to “Enrolled
Verification” to clarify that the column indicates whether the employee is enrolled for biometric verification.
New database views
(WFM-32783) The following database views are not documented in the Enterprise eTIME Database Views Reference
Guide for version 6.2 because they were introduced in the 6.2.6 service pack.
VP_PERSONEXPORT
The Person Export view stores exported data about the person.
Columns, Data Types, and Null Constraints
8
Column
Oracle
SQL Server
Null Constraint
PERSONNUM
nVarChar2(15)
nVarChar(15)
Not Null
FIRSTNM
nVarChar2(30)
nVarChar(30)
Null
MIDDLEINITIALNM
nVarChar2(1)
nVarChar(1)
Null
LASTNM
nVarChar2(30)
nVarChar(30)
Not Null
BIRTHDTM
Date
DateTime
Null
UPDATEDTM
Date
DateTime
Not Null
HOMELABORACCTNAME
nVarChar2(230)
nVarChar(230)
Null
HOMELABORLEVELNAME1
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME2
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME3
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME4
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME5
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME6
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME7
nVarChar2(50)
nVarChar(50)
Null
HOMELABORACCTDSC
nVarChar2(230)
nVarChar(230)
Null
HOMELABORLEVELDSC1
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC2
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC3
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC4
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC5
nVarChar2(250)
nVarChar(250)
Null
Documentation corrections/supplemental information
Columns, Data Types, and Null Constraints
Column
Oracle
SQL Server
Null Constraint
HOMELABORLEVELDSC6
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC7
nVarChar2(250)
nVarChar(250)
Null
CONTACT1
nVarChar2(35)
nVarChar(35)
Null
CONTACT2
nVarChar2(35)
nVarChar(35)
Null
STREETADDRESSTXT
nVarChar2(100)
nVarChar(100)
Null
CITYNM
nVarChar2(25)
nVarChar(25)
Null
STATENM
nVarChar2(25)
nVarChar(25)
Null
POSTALCD
nVarChar2(25)
nVarChar(25)
Null
Column Definitions
PERSONNUM — The Person Number column contains the unique identification number that is assigned to the
person. The person number is stored as a character string. Typically, only numeric values are stored in this
attribute; however, you can include one or more alphabetic characters.
FIRSTNM — The First Name column contains the first name of the employee.
MIDDLEINITIALNM — The Middle Initial Name column contains the middle initial of the employee.
LASTNM — The Last Name column contains the last name of the employee.
BIRTHDTM — The Birth Date column contains the date of birth of the employee in the format that is specified
during configuration.
UPDATEDTM — The Update Date and Time column contains the date and time of the last record update.
HOMELABORACCTNAME — The Home Labor Account Name column contains the name of the employee’s
home labor account. This column is a concatenation of the existing labor levels, up to seven levels.
HOMELABORLEVELNAME1 — The Home Labor Level Name 1 column contains the name of the first home labor
level.
HOMELABORLEVELNAME2 — The Home Labor Level Name 2 column contains the name of the second home
labor level.
HOMELABORLEVELNAME3 — The Home Labor Level Name 3 column contains the name of the third home
labor level.
HOMELABORLEVELNAME4 — The Home Labor Level Name 4 column contains the name of the fourth home
labor level.
HOMELABORLEVELNAME5 — The Home Labor Level Name 5 column contains the name of the fifth home labor
level.
HOMELABORLEVELNAME6 — The Home Labor Level Name 6 column contains the name of the sixth home
labor level.
HOMELABORLEVELNAME7 — The Home Labor Level Name 7 column contains the name of the seventh home
labor level.
HOMELABORACCTDSC — The Home Labor Account Description column contains a description of the home
labor account.
9
Documentation corrections/supplemental information
HOMELABORLEVELDSC1 — The Home Labor Level Description 1 column contains a description of the first
home labor level.
HOMELABORLEVELDSC2 — The Home Labor Level Description 2 column contains a description of the second
home labor level.
HOMELABORLEVELDSC3 — The Home Labor Level Description 3 column contains a description of the third
home labor level.
HOMELABORLEVELDSC4 — The Home Labor Level Description 4 column contains a description of the fourth
home labor level.
HOMELABORLEVELDSC5 — The Home Labor Level Description 5 column contains a description of the fifth
home labor level.
HOMELABORLEVELDSC6 — The Home Labor Level Description 6 column contains a description of the sixth
home labor level.
HOMELABORLEVELDSC7 — The Home Labor Level Description 7 column contains a description of the seventh
home labor level.
CONTACT1 — The Contact 1 column contains the employee’s first contact.
CONTACT2 — The Contact 2 column contains the employee’s second contact.
STREETADDRESSTXT — The column contains the employee’s street address.
CITYNM — This column contains the employee’s city name.
STATENM — This column contains the employee’s state name.
POSTALCD — This column contains the employee’s postal code.
10
Documentation corrections/supplemental information
VP_PUNCHEXPORT
The Punch Export view stores information about exported punches.
Columns, Data Types, and Null Constraints
Column
Oracle
SQL Server
Null Constraint
EMPLOYEEID
Number(12)
Int
Not Null
PERSONNUM
nVarChar2(15)
nVarChar(15)
Not Null
HOMELABORACCTNAME
nVarChar2(230)
nVarChar(230)
Null
HOMELABORLEVELNAME1
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME2
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME3
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME4
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME5
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME6
nVarChar2(50)
nVarChar(50)
Null
HOMELABORLEVELNAME7
nVarChar2(50)
nVarChar(50)
Null
HOMELABORACCTDSC
nVarChar2(230)
nVarChar(230)
Null
HOMELABORLEVELDSC1
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC2
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC3
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC4
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC5
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC6
nVarChar2(250)
nVarChar(250)
Null
HOMELABORLEVELDSC7
nVarChar2(250)
nVarChar(250)
Null
PUNCHDTM
Date
DateTime
Not Null
UPDATEDTM
Date
DateTime
Null
Column Definitions
EMPLOYEEID — The Employee ID column contains a system-generated number that uniquely identifies the
employee.
PERSONNUM — The Person Number column contains the unique identification number that is assigned to the
person. The person number is stored as a character string. Typically, only numeric values are stored in this
attribute; however, you can include one or more alphabetic characters.
HOMELABORACCTNAME — The Home Labor Account Name column contains the name of the home labor
account. The column is a concatenation of the existing labor levels, up to seven levels.
HOMELABORLEVELNAME1 — The Home Labor Level Name 1 column contains the name of the first home labor
level.
HOMELABORLEVELNAME2 — The Home Labor Level Name 2 column contains the name of the second home
labor level.
HOMELABORLEVELNAME3 — The Home Labor Level Name 3 column contains the name of the third home
labor level.
11
Documentation corrections/supplemental information
HOMELABORLEVELNAME4 — The Home Labor Level Name 4 column contains the name of the fourth home
labor level.
HOMELABORLEVELNAME5 — The Home Labor Level Name 5 column contains the name of the fifth home labor
level.
HOMELABORLEVELNAME6 — The Home Labor Level Name 6 column contains the name of the sixth home
labor level.
HOMELABORLEVELNAME7 — The Home Labor Level Name 7 column contains the name of the seventh home
labor level.
HOMELABORACCTDSC — The Home Labor Account Description column contains a description of the home
labor account.
HOMELABORLEVELDSC1 — The Home Labor Level Description 1 column contains a description of the first
home labor level.
HOMELABORLEVELDSC2 — The Home Labor Level Description 2 column contains a description of the second
home labor level.
HOMELABORLEVELDSC3 — The Home Labor Level Description 3 column contains a description of the third
home labor level.
HOMELABORLEVELDSC4 — The Home Labor Level Description 4 column contains a description of the fourth
home labor level.
HOMELABORLEVELDSC5 — The Home Labor Level Description 5 column contains a description of the fifth
home labor level.
HOMELABORLEVELDSC6 — The Home Labor Level Description 6 column contains a description of the sixth
home labor level.
HOMELABORLEVELDSC7 — The Home Labor Level Description 7 column contains a description of the seventh
home labor level.
PUNCHDTM — The Punch Date Time column contains the punch date and time.
UPDATEDTM — The Update Date and Time column contains the date and time of the last record update.
12
Documentation corrections/supplemental information
Enterprise Scheduler
The following revisions to documentation topics are not in the Enterprise eTIME version 6.2 online Help or the Enterprise
eTIME System Administrator’s Guide—Scheduling.
Correction to “% Effective” example
(CENG-502/WFM-55805) The online Help topic called “About the Productivity Monitor” correctly states that “% Effective” is
calculated by dividing earned hours by actual hours. However, the example in the topic incorrectly illustrate the calculation
as being actual hours divided by earned hours.
The example in the Help states:
“If you actually worked 1000 hours and you earned 800 hours, then your schedule is 125% effective (1000/800 x 100).
This result means that you have probably over-scheduled.”
The text should state:
“If you actually worked 1000 hours and you earned 800 hours, then your schedule is 80% effective (800/1000 x 100).
This result means that you have probably over-scheduled. “
Correction to “Terminated employees” topic
(WFM-23157) The following note was added to the topic:
Note: For custom HyperFind queries, configure the query to filter terminated employees. Otherwise, the
schedule displays all employees – active and terminated. Contact your system administrator.
Correction to “Configuring shift templates” topic
The following text was corrected in this topic:
Off — Time associated to a work rule, for example, employee is scheduled to be off. A shift with an Off segment cannot
have other segments. If the employee is on-call and comes to work, the pay amount changes. Tip: Off segments are
not paid according to the work rule, and these shifts do not appear in the On-Call report. Rather than use Off segments
for on-call employees, use Regular segments and configure the work rule to not count towards coverage.
Corrections to “Overriding schedule rules and rule sets” topic
Auto-Scheduler
1. The Auto-Scheduler can create a baseline schedule for employees to choose shifts:
a. Select the Schedule Rules.
b. Select the Effective Date.
c.
Select the Expiration Date.
2. To override a schedule rule set:
a. In Override, enter values as required.
b. Select the Schedule Rule Set Optimization Override.
c.
Select the Effective Date.
13
Documentation corrections/supplemental information
3. To use the original schedule rule set, disable all rule set overrides:
a. From Schedule Rule Set Optimization Override, select the Empty Employee Profile rule set.
b. Select the Effective Date to become the expiration date of the previous rule set override. The effective date
cannot be in the future.
c.
Click Save. The new override replaces previous overrides.
4. Click Save.
Correction to “Configuring schedule zone categories”
(WFM-22903) The following introductory text is corrected for this topic:
A schedule zone category groups zones from different schedule zone sets.
–
–
For example, use a zone category called Breakfast to group the 9a – 11a Breakfast zone at location A with the
6a – 8a Earlyriser and 8a – 10a Breakfast zones at location B.
The Priority Scheduling Engine (PSE) can sort shifts or match employees to shifts by preferred zone set.
Corrections to Auto-Scheduler system setting descriptions
The following text presents corrected descriptions for two Auto-Scheduler system settings:
•
global.AutoScheduler.enforceMinimumHours
True – Meet minimum hours each week for each person by extending start or end time of shifts. Enables the
“Schedule even if labor requirements are zero” coverage option to enforce the schedule even when labor
requirements are zero.
False – Do not extend shifts to meet minimum hours. Hides the “Schedule even if labor requirements are zero”
coverage option.
•
global.AutoScheduler.preventZeroCoverage
True – Prevent zero coverage.
False – Allow zero coverage.
Corrections to Enterprise Scheduler Database Tables Reference Guide
In the Enterprise Scheduler Database Tables Reference Guide, the following columns in the SHIFTCODE database table
are incorrectly identified as holding integer values for SQL Server, instead of decimal values. The following lines of text
from the database table description show the corrections in italic type:
Column Name
Oracle
SQL Server
Null Constraint
ACCRUALAMOUNT
Number(16,6)
Decimal(16,6)
Null
PCEMONEYAMT
Number(16,6)
Decimal(16,6)
Null
OVERRIDEACCRUALAMT
Number(4,2)
Decimal(4,2)
Null
PCEDAYSQTY
Number(16,6)
Decimal(16,6)
Null
14
Documentation corrections/supplemental information
Enterprise Device Manager
Database changes in 6.2 service packs
See “Other database changes” on page 56 for information that supplements the 6.2.0 version of the Enterprise Device
Manager Database Tables Reference Guide.
Clarifications to Enterprise eTIME System Administrator’s Guide — Device Manager and online
Help
•
In the section called “About Screensavers,” there is reference to video plug-in. ADP InTouch does not support
streaming video.
•
In the System Administrator’s Guide, the “Configuring Alerts” section does not indicate that several of the workflow
notification configuration options do not apply to Device Manager generic notifications. See “Clarification about
workflow notification configuration” on page 7 for detailed information.
•
(CE-24394) The site.wdm.alternate.phone.book.path setting is used in communications for a modem
device that is defined with a phone number and configured with the server-initiated protocol. The Enterprise eTIME
System Administrator’s Guide — Device Manager and online Help for version 6.2 incorrectly state that this
property requires the following complete phone book location path without the filename appended to the end:
C:\Documents and Settings\All Users\Application
Data\Microsoft\Network\Connections\Pbk
Append the phone book filename to the end of the phone book location path as follows:
C:\Documents and Settings\All Users\Application
Data\Microsoft\Network\Connections\Pbk\rasphone.pbk
•
The Enterprise eTIME System Administrator’s Guide—Device Manager and online Help for version 6.2 did not
include the following important information:
Vertically scaled Enterprise eTIME installations do not support server-initiated device communication. You must
configure Series 4000 timeclocks to use device-initiated communication.
Note: Because Enterprise eTIME supports 64-bit operating systems, there is no longer a need for vertical
scaling: a single instance of Enterprise eTIME can take advantage of the machine’s total memory capacity. For
more information, contact your TLM Representative.
15
Documentation corrections/supplemental information
Enterprise Integration Manager
Enabling batch processing and sorting for output
When configuring the output for a link, you cannot select the Enable batch processing check box and the Sort Output
File check box at the same time. Specifying both settings may produce unexpected results in the output.
Running interfaces with a Windows (MS-DOS) command
The following information supplements the text in Chapter 11, “Running Interfaces” of the Enterprise Integration Manager
Programmer’s Guide, in the sections about using a command line and running a batch job:
To ensure that an interface completes its execution before any subsequent commands are executed, ADP recommends
that you use the Windows (MS-DOS) command START with the /WAIT switch to run the interface. Do this either from a
single command line or as part of a batch operation. For example, the following command will block the execution of any
subsequent commands until the interface “TestInterface” has completed its execution:
START /WAIT knx.exe /run=TestInterface
For more information about using Windows (MS-DOS) commands, see the Microsoft Windows documentation.
Additional XML API reference information
The following XML API tag information supplements the tag descriptions in the Enterprise eTIME Developers Toolkit
Reference Guide—Data Integration:
WIM Lookup Table
Retrieves the lookup tables.
Function Access Control Point: KNX
Introduced in v6.1; last changed in v6.1
Action Descriptions
RetrieveAll
Retrieves a list of LookupTable beans stored in the database.
Return Value Type: WimLookupTable bean list
Required Properties: None
Access Control Point Name: View
Introduced in v6.1
Retrieve
Retrieves a LookupTable for the specified name.
Return Value Type: WimLookupTable
Required Properties: Name
Access Control Point Name: View
Introduced in v6.1
16
Documentation corrections/supplemental information
Action Parameters
Parameter Name
Description
Additional information
LoadAssocInterfaces
When set to true loads the associated
WimInterfaces for this LookupTable.
Optional
Introduced in v6.1
LoadAssocLinks
When set to true loads the associated
WimLink for this LookupTable.
Optional
Introduced in v6.1
LoadLightLinks
When set to true only the lightweight
WimLinks associated with the
LookupTable are loaded
Optional.
Introduced in v6.1
Documentation summarizing differences between A-Connect 6.0 and Integration Manager 6.2
A document called Differences between A-Connect 6.0 and Enterprise Integration Manager 6.2 is available at the same
site as these Release Notes. The file name is EIM_A-Connect_Differences_6217.pdf.
Enterprise Activities
Correction to feature description in the Enterprise eTIME 6.2.0 Release Notes
(WFM-37860) In the “New Features” section of the Enterprise eTIME Suite 6.2 Release Notes, the location for the following
function access profile setting is incorrect:
Allow Entry of Durations as Hours in Timecard Editor
The location indicated is Enterprise eTIME Manager - Department Manager > Activities in Timecard Editor.
The setting is not part of the function access profile for managers; the setting is relevant to Enterprise eTIME Professional
function access profiles only.
Employees in a manager’s group can be both hours and percentage entry employees. The “Allow Entry of Durations as
Hours in Timecard Editor” setting in an employee’s function access profiles determines which column in the employee’s
timecard the manager can edit, hours or percentage. This requires that either the employee or the manager have an
Enterprise eTIME Professional license. If the manager only has an Enterprise eTIME Manager license, the default
behavior of disallowing hours entry is used.
17
Installing Service Pack 17
Installing Service Pack 17
Important: Please read the installation and database upgrade instructions carefully.
This section contains the following topics:
•
“Who Should Install Service Pack 17?” on page 18
•
“Installation Considerations” on page 18
•
“Installing on Windows systems” on page 22
•
“Uninstalling or removing the service pack from Windows systems” on page 28
•
“Installing on AIX or Solaris systems” on page 31
•
“Uninstalling from AIX or Solaris systems” on page 34
Who Should Install Service Pack 17?
All clients who installed Enterprise eTIME version 6.2.0 and who want to acquire new features and quality improvements
should install Service Pack 17.
Installation Considerations
Basic guidelines
•
Service Pack 17 must be installed wherever Enterprise eTIME version 6.2 is installed, including all application
servers and web servers. If you are installing the service pack in an environment where the application server and
web server are on separate machines, run the installation program on each machine.
•
You must log off and stop all ADP applications before you install the service pack. ADP also recommends that you
log off and close all client browsers. Restart the applications and client browsers after the service pack installation
is complete. Client browsers will then be updated with the latest versions of the application’s .jar files.
•
The service pack inspects the installed software, and updates items as necessary. The service pack installation
cannot update files that are open and being used by any Enterprise eTIME suite applications.
•
All instances of Enterprise eTIME that use the same database must use the same service pack. You must stop all
instances before you install a service pack, regardless of whether the instances are on different machines or the
same machine.
Instances of Enterprise eTIME that do not use the same database can use different service packs from the same
major release. For example, instance 1 could be running Service Pack 2 while instance 2 is running Service Pack
1.
18
Installing Service Pack 17
Installation environment
•
If you install Enterprise eTIME 6.2 products and then want to install SharePoint on the same machine, you must
perform additional configuration tasks on SharePoint and the Microsoft IIS web server. If you do not, the Enterprise
eTIME products will not be accessible.
To install the Enterprise eTIME products, follow the instructions in “Installing on Windows systems” on page 22.
After installing SharePoint, see “Appendix: Enterprise eTIME products and SharePoint on the same server” on
page 67 for detailed configuration procedures.
•
When Enterprise eTIME and the application server are installed on one machine and the web server is on another
(a “separated installation”), the same naming convention must be used during configuration on both machines. For
example, if you enter a fully qualified domain name for the application server when you install the web server, you
must continue to use fully qualified domain names throughout the configuration on both machines.
•
If you install a single instance of the service pack and then you install an add-on product, the new product will pick
up the service pack automatically, upon installation. No additional step is required.
•
If the Enterprise eTIME installation is configured as described next, read the instructions that follow about data
collection device configuration. Data collection devices include the Series 4000 timeclock and ADP InTouch.
–
–
The installation consists of application servers with multiple instances to support multiple languages.
QuickGlance transactions will be assigned to data collection devices.
To configure the data collection devices to show QuickGlance transaction pages in the same language that the
devices are configured to show:
a. Create a General Device Settings building block and select the language that the data collection devices
assigned to this building block will use.
b. For ADP InTouch devices, when you create the Soft Key Settings building block, select the same language that
you selected for General Device Settings.
c.
Create a Device Communications Settings building block. Specify the primary Web server and instance ID of
an Enterprise eTIME instance that uses the language you specified in the General Device Settings building
block.
d. When you create the Device configuration profile for the data collection device, assign the corresponding Soft
Key Settings, General Device Settings, and Device Communications building blocks that you created.
If not all data collection devices will use the same language, create separate General Device Settings, Device
Communications Settings, Soft Key Settings, and Device building blocks for each language.
Note: Enterprise Activities QuickGlance transaction pages display in the same language as other QuickGlance
transaction pages. However, the language of the Enterprise Activities QuickGlance soft key labels match the
language of the application server which processed the device initialization. In a multi-instance configuration, it
is possible that the language of the soft key labels for Enterprise Activities QuickGlance transactions will not
match the language of their transaction pages.
This language mismatch can occur because the device initialize action that loads soft key labels may be
processed by any available language instance that is configured to process Device Manager actions in Setup
> System Configuration > Batch Controller Configuration. If you want to ensure that the labels display in a
particular language, you can disable Device Manager actions on all instances except the one that has the
language you want. The download process will use that instance and labels will appear in the language of that
instance.
19
Installing Service Pack 17
•
(WFM-35822) If an ADP InTouch device is configured to use one or more languages whose currency decimal
separator differs from the separator used by the Enterprise eTIME server, read the following information:
Currency transactions at devices using languages with decimal separators that differ from the separator used by
the Enterprise eTIME server will fail. The failed transactions are sent to Transaction Assistant.
The following languages use a comma separator:
–
–
–
–
–
French Canada
French France
Dutch
German
Portuguese
The following languages use a period separator:
–
–
–
–
English
Spanish
Simplified Chinese
Traditional Chinese
Workarounds
There are three possible workarounds for this situation.
Option 1
Configure all Enterprise eTIME servers and devices to use languages that use a common decimal separator.
Note: You configure the default language for the Enterprise eTIME server using the following settings in the Locale
tab of the Enterprise eTIME System Settings:
–
–
–
–
site.local.LANGUAGE
site.local.COUNTRY
site.local.currency.LANGUAGE
site.local.currency.COUNTRY
You configure the device language in the General Device Settings Editor.
Option 2
Manually edit all failed money transactions. To do this:
a. Log into Enterprise eTIME.
b. Navigate to Transaction Assistant and locate the appropriate money transactions.
c.
Edit the transaction and verify that the decimal separator in the transaction matches the separator of the server
that you are logged on to.
d. Click Resubmit.
Option 3
Upgrade to Enterprise eTIME 6.3.x or higher which supports devices and Enterprise eTIME servers using different
decimal separators.
20
Installing Service Pack 17
Product-specific considerations
•
If you are running the Navigator (Next Generation User Interface, or NGUI), you must uninstall your current version
of Navigator before you install Enterprise eTIME 6.2.17.
•
If you include Enterprise Activities in a new installation, or upgrade a system that already includes Enterprise
Activities, you must do the following before you upgrade to Enterprise eTIME version 6.2.17:
a. Run Enterprise eTIME version 6.2.0.
b. Log out of the Enterprise eTIME system.
Doing this ensures that Enterprise Activities will be properly installed.
•
Beginning with service pack 6.2.2, Enterprise eTIME Portal supports 64-bit operating systems.
•
If you will install the Enterprise eTIME Portal and apply a language pack to the installation, you must create an
English language Enterprise eTIME instance and do either of the following before you install the Portal application:
–
Apply the language pack to the English instance to incorporate the language you want to use and then install
the Portal application.
or
–
Create another English language Enterprise eTIME instance and apply the language pack.
The section called “Installing Enterprise eTIME Portal 6.2.17” on page 26 presents instructions for installing the
Portal, and explains a special situation where you might need to modify the Portal branding file.
Resolved service pack upgrade issue
WFM-40615
If clients changed settings in the workers.properties file according to Device Manager
best practices, and then upgraded the Enterprise eTIME to a different service pack, the
application became unresponsive. This issue occurred because the upgrade process changed
the “connection_pool_size” property in the workers.properties file back to its default
setting. The user interface did not indicate the nature of the problem.
This issue has been resolved by preventing the upgrade process from altering the
“connection_pool_size” setting when reconfiguring an Enterprise eTIME instance.
21
Installing Service Pack 17
Installing on Windows systems
•
The service pack uses the location \root_directory\deployments\servicepack as a staging area;
usually, root_directory is \ADP. The 6.2 files are stored in \root_directory\deployments\release.
Do not modify or delete the staging or release folders; they contain files that are required for a successful uninstall.
The \root_directory\ also contains a backup folder. Modifying or deleting the backup folder could make
the system uninstallable.
•
If you are using multiple instances of Enterprise eTIME, the service pack installation program automatically runs
Configuration Manager so you can select the instance to which to apply the service pack.
•
At times during the installation, there may be no indicator of the status of the installation. For example, after the
installation executable is launched, the screen may appear to be unresponsive until text appears in the install
dialog.
Requirements — Windows systems
•
Be sure that Enterprise eTIME version 6.2 is installed.
•
Stop the application server, background processor, web server, A-Connect (if used), and other related timekeeping
applications.
•
Know the database owner’s user name and password. If they are not automatically provided during the installation,
you must enter them.
•
If your system includes multiple application servers or web servers pointing to the same database, you must stop
all the application servers and web servers before you install Service Pack 17. After you have installed the service
pack successfully on one server, upgrade the remaining servers, one by one.
•
If you plan to load ADP InTouch .KRX firmware files in Enterprise Device Manager, ensure that the application
server has a minimum of 4 GB RAM.
Installing Enterprise eTIME 6.2.17
Note the following important information:
•
If you are upgrading from a previous version of Enterprise eTIME (versions 4.x.x through 6.1.x), install Enterprise
eTIME 6.2 and the service pack before you upgrade the database or apply the service pack to an instance.
•
After the Cancel button is disabled, do not try to cancel the installation process. Canceling the installation by any
other method might corrupt your existing Enterprise eTIME installation. If problems occur, complete the installation,
then perform an uninstall.
•
When you upgrade multiple instances, you must complete the upgrade of one instance before you upgrade the
next instance, as instructed in this procedure.
•
You can install the database scripts separately by locating the install folder \ADP\boms\bin and launching the
Patchelizer.bat utility. This utility only installs and executes the database script files.
Note: If you consider using this utility for any reason, first consult with your TLM Representative.
To remove the database script changes from the database, follow the uninstall procedure. See “Uninstalling or
removing the service pack from Windows systems” on page 28.
22
Installing Service Pack 17
To install the Enterprise eTIME 6.2.17 software:
1. Back up the database.
2. Contact TLM Support to get the service pack executable file.
3. If you are running the Navigator (Next Generation User Interface, or NGUI), uninstall it now.
4. Navigate to the folder that contains the service pack package.
5. Run the installation executable. If you are using Windows Server 2008, right-click the installation executable and
select Run as Administrator.
6. Click Next when the Welcome message appears.
7. Review the summary information, and then click Next.
After you click Next, the installation program installs the applicable files and configures the installation. This
process may take several minutes; the active window displays the log file as it is generated.
Important:
–
–
After the Cancel button on the installation dialog is disabled, do not click the Close icon in the installation dialog
box. If you do, the existing Enterprise eTIME installation might become corrupted.
If the Enterprise eTIME desktop icon disappears during the installation, refresh the desktop after the
installation finishes. Do this by pressing F5 or by right-clicking on the desktop and clicking Refresh.
If the machine contains only one instance (by default, “1”), the service pack is applied to that instance; go to step 8.
If the machine contains more than one instance, Configuration Manager opens:
a. Click Next when the Welcome to Configuration Manager screen appears.
b. In the Configuration Action screen, select Modify an instance, then click Next.
c.
In the Select Instance screen, select the instance to apply the service pack from the list in the left side of this
dialog box. When you select an instance, details about that instance appear in the right side of the box. Click
Next when finished.
d. In the Actions screen, select Add or Remove Suite Service Pack, and then click Next.
e. Select the service pack to apply to the selected instance, and then click Next.
f.
In the Modification Confirmation screen, verify that the information in the confirmation window is correct and
then click Next.
8. The Database Patchelizer appears. Enter the appropriate information in the Database Patchelizer screen so that
the database can be updated:
DBMS — Select Mss (SQL Server) or Ora (Oracle).
Username and password — Enter the database owner logon information.
Connection Method — If the database is on a separate server, select Server and enter the server name and
database or SID name. Change the database port number if the database uses a non-default port number. If
the database is on the same server as the application, select JDBC URL and verify that the information is
correct.
SP Version — Select the service pack version to apply.
Click Run Scripts.
9. When the success message appears, click Exit.
23
Installing Service Pack 17
10. When the Patchelizer finishes updating the database, the Configuration Manager Finished page appears.
–
Click Next to apply the service pack to additional instances. If you have multiple instances connecting to the
same database, all instances must use the same service pack.
– If you are finished modifying instances, click Cancel to exit Configuration Manager.
11. If you are finished with Configuration Manger, the service pack installer appears. Click Finished.
12. Restart the application server by double-clicking the green Go icon on the desktop.
13. If you are upgrading from Enterprise eTIME 4.x.x through 6.1.x, you must upgrade the database. Proceed to
“Upgrading a database from 4.x.x through 6.1.x to 6.2” on page 37.
If you will install SharePoint on the same machine, you must perform additional configuration tasks on SharePoint
and the Microsoft IIS web server. If you do not, the Enterprise eTIME products will not be accessible. After you
install SharePoint, see “Appendix: Enterprise eTIME products and SharePoint on the same server” on page 67.
Installing Advanced Reports 6.2.17
Note the following important information:
•
If you are installing Advanced Reports for the first time, refer to the Enterprise eTIME 6.2.0 installation
documentation for instructions.
•
The Advanced Reports 6.2.17 software can be used to upgrade from earlier versions of 6.2.
•
There are three Advanced Reports installation executables from which to choose. For more details, refer to the
procedure that follows.
To install Advanced Reports Service Pack 6.2.17 on the SSRS server:
1. From the 6.2.17 Service Pack installation directory, run one of the following SSRS executables, based on the
version of Microsoft SQL Server that you are using:
SQL Server version
SSRS executable to use
2008 for 64-bit systems
EeTSSRS2008_64_SP6217.exe
2008 for 32-bit systems
EeTSSRS2008_SP6217.exe
2005 (32-bit only)
EeTSSRS2005_SP6217.exe
2. When the Welcome screen appears, click Next.
3. Follow the prompts on the subsequent installation screens until the installation is finished.
4. Click Finish to complete the installation process.
Note: If you are upgrading Advanced Reporting from 6.0.x to 6.2.17, the ARC Manager displays a list of
partially upgraded instances after the installation. To complete the upgrade process, edit each instance
separately, updating the values of passwords and other information that was not migrated during the upgrade
process.
5. For configuration instructions, refer to the document called Installing and Configuring Advanced Reports with
Enterprise eTIME. The document is included on the product suite documentation CD.
24
Installing Service Pack 17
Installing Process Designer 6.2.17
Note the following important information:
•
If you are installing Process Designer for the first time, refer to the Enterprise eTIME 6.2.0 installation
documentation for instructions.
•
Process Designer 6.2.17 software can be used to upgrade from earlier versions of 6.2.
To install Process Designer 6.2.17 on the client system:
1. From the 6.2.17 Service Pack installation directory, start the installation by running EeTPRCDES_SP6217.exe.
The welcome screen appears.
2. Click Next.
3. Follow the prompts on the subsequent installation screens until the installation is finished.
4. Click Finish to complete the installation process.
5. On the client system, open the Process Designer. At the prompt, point to the application server.
6. Launch Process Designer.
7. Under the File menu, click Check For Extensions.
Extension updates may take a few minutes. During the process, status messages will tell which extensions are
being downloaded from the Application Server.
8. Repeat this procedure for each client system on which Process Designer should be installed.
(CE-26159) Note: There are no longer potential screen refresh issues with Process Designer on a system
running Windows 7.
Installing Interface Designer 6.2.17
You must install the version of Interface Designer that is included with the 6.2.17 service pack to support the Enterprise
Integration Manager changes that are described in the 6.2.17 release notes.
Upgrading from 6.2.0 to 6.2.17
1. Close all instances of Interface Designer.
2. Make back-ups of interfaces, links, and associated files.
3. Save the self-extracting executable file to the Interface Designer installation directory (the default directory is
<drive_letter>:\adp\InterfaceDesigner).
4. Run the self-extracting .exe file to launch the Integration Manager – Interface Designer installer, and provide the
requested information.
Upgrading from 6.1.x to 6.2.17
If there is an existing 6.1.x version of Interface Designer already installed on the system, you can uninstall that version
before you install the version 6.2.17. However, if you want to retain the existing 6.1.x version on the system and also install
version 6.2.17, specify a different folder location during the 6.2.17 installation procedure. (The installation wizard displays a
message if it detects an existing Interface Designer folder.)
25
Installing Service Pack 17
Installing Enterprise eTIME Portal 6.2.17
Important: Beginning with service pack 6.2.2, Enterprise eTIME Portal supports 64-bit operating systems.
If you are installing Enterprise eTIME Portal for the first time, refer to the Enterprise eTIME 6.2.0 installation documentation
for instructions.
Note the following important information:
•
If the Service Pack includes a Site Template, the Portal Configuration Manager deletes and recreates the Portal
sites or instances. If Portal sites were customized in any way, the following upgrade process removes those
customizations. For information about how to preserve customized Web Parts, refer to the Enterprise eTIME Portal
installation documentation.
•
When using the Portal configured with the SSL terminator, use the following URL to log on:
http(s)://portal_server_name.domain/sites/site_name/Default.aspx
1. From the 6.2.17 Service Pack installation directory for Enterprise eTIME Portal, start the installation by running
EeTPortal_SP6217.exe or, for 64-bit environments, EeTPortal_64_SP6217.exe. The welcome screen
appears.
2. Click Next. Summary information about the location of the Enterprise eTIME Portal installation and the total size of
the installation is displayed.
3. Follow the prompts on the subsequent installation screens. The installation installs the needed files, and then runs
the Portal Configuration Manager.
Important: If the Service Pack includes a Site Template, the Portal Configuration Manager deletes and
recreates the Portal sites or instances. If Portal sites were customized in any way, this process removes those
customizations.
4. Click Finish.
5. In the following situation, you must modify the Portal branding file to enable the Portal Web Parts to show data:
a. You create multiple instances of Enterprise eTIME, one of which is called “1.”
b. After you install the Portal software, you create the first Portal site and point it to the “1” instance.
c.
You create one or more additional Portal sites which point to instances other than “1.”
d. You stop or remove the “1” instance and stop using the Portal site that points to that instance.
You must modify the Portal branding file to reference the name of one of the active instances.
To modify the Portal branding file:
a. Open the KronosBranding.css file located in the following directory:
<drive_letter>:\Inetpub\wwwroot\wss\VirtualDirectories\80\wpresources\
Kronos.WebParts.Library\css\
b. Replace the server and instance names with the names of the server and instance on which you installed the
Portal application.
26
Installing Service Pack 17
Installing Enterprise Worksheet 6.2.17
Important: If you are installing Enterprise Worksheet for the first time, refer to the Enterprise eTIME 6.2.0
installation documentation for instructions.
1. From the 6.2.17 Service Pack installation directory, start the installation by running EeTWFWS_SP6217.exe. The
welcome screen appears.
2. Click Next.
3. Follow the prompts on the subsequent installation screens until the installation is finished.
4. Click Finish to complete the installation process.
27
Installing Service Pack 17
Uninstalling or removing the service pack from Windows systems
Difference between “uninstalling” and “removing” service packs
Enterprise eTIME version 6.2 products are deployed in two phases: The installation phase of the deployment process
installs the applicable files on the host machine and the configuration phase makes the system ready to use. Because of
this two-phase process, you can remove a service pack from Enterprise eTIME instances, or uninstall it completely from the
machine.
•
Removing a service pack from one or more instances does not remove it from the machine. The instance reverts
back to the service pack you select or the base version of the software (for example, 6.2.0). The service pack is
available to re-apply to the Enterprise eTIME instances.
Example:
–
–
You are running service pack 1 on an instance, and then install service pack 2 and apply it to the same
instance.
Later, you decide that you don’t want to use service pack 2.
You can remove service pack 2 from the instance and choose to revert to service pack 1 or the base version of the
product. Service pack 2 remains on the machine.
•
Uninstalling a service pack removes it completely from the machine. When you uninstall a service pack:
–
–
–
All instances of Enterprise eTIME that are at the current level revert to version 6.2.0.
The selected service pack is removed from the machine.
If the option to remove scripts is chosen, the database reverts to 6.2.0.
If you want to re-apply the service pack to Enterprise eTIME instances, first you need to download and re-install the
service pack.
Before you begin
Before you remove or uninstall the service pack, do the following tasks:
28
•
Ensure that all servers and the database are running the same version of Enterprise eTIME. This allows the system
to come up in online mode after you remove or uninstall the service pack.
•
Stop the application server and other applications related to the timekeeping system. If your system includes
multiple application servers that point to the same database, you must stop all of the application servers before you
uninstall the service pack.
•
Obtain the database owner’s user name and password.
Installing Service Pack 17
Removing Enterprise eTIME 6.2.17 from instances
To remove a service pack from one instance of Enterprise eTIME:
1. Back up the database.
2. Start Configuration Manager.
3. Select Modify instance and then click Next.
4. Select the instance from which you want to remove the service pack and then click Next.
5. Select Add or remove service pack and then click Next.
6. At the Service Pack version prompt, select the service pack to which you want to revert, or select the base version.
After the Configuration Manager starts reconfiguring the instance, the Patchelizer screen appears.
7. Enter the database owner’s user name and password.
8. If you want to uninstall database changes that were made by the service pack installation, click Run Scripts.
If you want to keep the database changes, click Cancel.
When Configuration Manager finishes, the instance reverts to the selected installed service pack; all the other instances
are left intact. In this case, \root_directory\deployments\servicepack\release_number remains. Usually,
root_directory is \ADP.
If you want to remove the service pack from another Enterprise eTIME instance, repeat this procedure, selecting the
appropriate instance.
Uninstalling Enterprise eTIME 6.2.17
Important: This procedure removes the service pack from all Enterprise eTIME instances and removes it from
the machine. You cannot re-apply the service pack without first downloading and re-installing it on the
machine.
1. Back up the database.
2. Stop all instances of Enterprise eTIME.
–
If the Enterprise eTIME environment uses a JBoss application server that was installed by the Enterprise
eTIME installation program, click the Stop button
– If the Enterprise eTIME environment uses a pre-installed JBoss application server, select Start > Settings >
Control Panel, and then select Administrative Tools > Services. Right-click JBoss and then click Stop.
3. In Control Panel, select ADP Enterprise eTIME Service Pack 6.2.17 and click Change/Remove.
4. When the welcome message appears, click Next.
5. Summary information appears. If it is correct, click Next.
6. When the Database Patchelizer appears, choose to uninstall or leave the database changes.
To leave the database unchanged, click Cancel.
To remove the service pack components from the database, enter the appropriate information so that the database
can be updated:
29
Installing Service Pack 17
–
–
–
DBMS — Select Mss (SQL Server) or Ora (Oracle).
Username and password — Enter the database owner logon information.
Connection Method — If the database is on a separate server, select Server and enter the server name and
database name. Change the database port number if the database uses a non-default port number. If the
database is on the same server as the application, select JDBC URL and verify that the information is correct.
– SP Version — Select the service pack version to remove.
– Click Run Scripts.
– When the success message appears, click Exit.
7. When the service pack has been uninstalled, a confirmation message appears. Click Finish.
Important: Data collection devices and downgrading to earlier service packs
•
If you created ADP InTouch data in Device Manager and then want to uninstall 6.2.6 or higher to run 6.2.4 or an
older 6.2 version on the same database, contact TLM Support before you begin the downgrade process. You will
need instruction to delete the ADP InTouch data because service pack 6.2.4 and lower 6.2 service packs do not
support ADP InTouch.
•
If you use Series 4000 or ADP InTouch devices and you want to downgrade from Device Manager 6.2.7 or higher
to an earlier 6.2.x version of Device Manager, contact TLM Support before you begin the downgrade process. You
will need instruction to restore the ability to import and softload firmware files after downgrading.
Uninstalling other Enterprise eTIME 6.2.17 software
Important: When you uninstall version 6.2.17 of any of the products discussed in this section, the products are completely
removed. The uninstallation process does not cause the products to revert to the 6.2 version.
To remove any of the following products, use the remove function in Control Panel:
30
•
Advanced Reports
•
Process Designer
•
Interface Designer
•
Enterprise eTIME Portal
•
Enterprise Worksheet
Installing Service Pack 17
Installing on AIX or Solaris systems
It is mandatory to have a properly configured Windows companion server for the UNIX server on which you need to install
the service pack.
•
You can install the service pack using InstallShield GUI Mode or using the InstallShield Console Mode (command
line). Instructions for both are included here.
•
The service pack uses the location <adp_root>/deployments/servicepack/release_number as a
staging area; usually, adp_root is /adp. The 6.2 files are stored in <adp_root>/deployments/release. Do
not modify or delete the staging or release folders; they contain files that are required for a successful uninstall.
The <adp_root> directory also contains a backup folder. Modifying or deleting the backup folder could make the
system uninstallable.
•
When you apply the service pack to the Windows companion server, you are prompted to indicate whether to
execute the database upgrade scripts. The companion server and the UNIX server need to be at the same level in
terms of installed products and the database level.
If you have multiple instances of Enterprise eTIME installed on the same machine, Configuration Manager will
open when you install a service pack. All instances that point to the same database must be at the same service
pack level.
Requirements
•
Be sure that Enterprise eTIME version 6.2 is installed.
•
Stop the application server and other applications.
•
If your system includes multiple application servers pointing to the same database, you must stop all the
application servers when installing Service Pack 17. After you have installed the service pack successfully on one
server, upgrade the remaining servers, one by one.
Installing using the InstallShield GUI mode
1. Back up the database.
2. Stop all instances of Enterprise eTIME by executing <adp_root>/adp/1/bin/wfc stop at the command
prompt.
3. Obtain the Service Pack from your TLM Representative.
4. Open a command prompt window and navigate to the service pack installation directory.
5. Untar the file to your local system. The file for AIX is EeTspAIX6217.tar. The file for Solaris is
EeTspSOL6217.tar.
6. Type ./file_name
where:
the file_name for AIX is EeTspAIX.
the file_name for Solaris is EeTspSparc.
7. After the Welcome message, when prompted, click Next.
8. Review the summary information, and then click Next.
After you click Next, the installation program installs the applicable files and configures the installation. Although
this process may take several minutes, the active window displays the log file as it is generated.
31
Installing Service Pack 17
If the machine contains more than one instance, Configuration Manager opens.
a. Click Next when the Welcome to Configuration Manager screen appears.
b. Under Configuration Action, select Modify an instance, then click Next.
c.
From the list under Select Instance, select the instance to which you want to apply the service pack.
Note: When you select an instance, details about that instance appear in the right side of the dialog box. You
can only select one instance at a time here.
Click Next.
d. Check Add or Remove service pack, then click Next.
e. Choose the radio button that corresponds to the appropriate service pack, then click Next.
f.
Under Modification Confirmation, click Next. The Patchelizer runs and updates the database.
g. When the Finished box appears, click Next to apply the service pack to another instance. If you are finished
modifying instances, click Cancel to exit Configuration Manager.
h. Restart the application server by executing <adp_root>/adp/1/bin/wfc start at the command prompt.
9. If you are upgrading from Enterprise eTIME 4.x.x through 6.1.x, you must upgrade the database. Proceed to
“Upgrading a database from 4.x.x through 6.1.x to 6.2” on page 37.
Installing using the InstallShield Console mode
1. Back up the database.
2. Stop all instances of Enterprise eTIME by executing <adp_root>/adp/1/bin/wfc stop at the command
prompt.
– To stop Java: <adp_root>/adp/1/bin/wfc stop
– To stop Apache: <adp_root>/adp/1/bin/wfc stop_web
3. Obtain the Service Pack from your TLM Representative.
4. Open a command prompt window and navigate to the service pack installation directory.
5. Untar the file to your local system. The file for AIX is EeTspAIX6217.tar. The file for Solaris is
EeTspSOL6217.tar.
6. Start the installation executable by entering
./<file_name> -console
where:
the <file_name> for AIX is EeTspAIX
the <file_name> for Solaris is EeTspSparc.
7. After the Welcome message, at the prompt, press “1” for Next.
8. After the installation total size is posted, at the prompt, press “1” for Next. The installation begins and may take
several minutes.
9. At the end of the installation, run Configuration Manager. To do this:
a. Type cd <adp root>/configuration/boms/bin
Note: A typical example of <adp root> is /usr/local/adp.
b. Type ./cfgmgr -console
c. Press “1” for Next when the Welcome to Configuration Manager screen appears.
d. Under Configuration Action, select Modify an instance and then press “1” for Next.
32
Installing Service Pack 17
e. From the list under Select Instance, select the instance to which you want to apply the service pack. Then
press “1” for Next.
f.
Press “1” for Next.
g. Select Add or Remove service pack, then press “1” for Next.
h. Choose the number that corresponds to the appropriate service pack, then press 1 for Next.
i.
Under Modification Confirmation, press “1” for Next.
10. After the completion message, at the prompt, press “3” for Finish.
11. Run Patchelizer. To do this:
a. Type cd <adp root>/configuration/boms/bin.
b. Type ./patchelizer.sh -console.
12. Restart the application server by executing <adp root>/1/bin/wfc start at the command prompt.
13. If you need to upgrade the database from Enterprise eTIME 4.x.x through 6.1.x, perform the database upgrade
procedure presented on page 37.
33
Installing Service Pack 17
Uninstalling from AIX or Solaris systems
Difference between “uninstalling” and “removing” service packs
Enterprise eTIME version 6.2 products are deployed in two phases: The installation phase of the deployment process installs
the applicable files on the host machine and the configuration phase makes the system ready to use. Because of this twophase process, you can remove a service pack from Enterprise eTIME instances, or uninstall it completely from the machine.
•
Removing a service pack from one or more instances does not remove it from the machine. The instance reverts
back to the service pack you select or the base version of the software (for example, 6.3.0). The service pack is
available to re-apply to the Enterprise eTIME instances.
Example:
–
–
You are running service pack 1 on an instance, and then install service pack 2 and apply it to the same
instance.
Later, you decide that you don’t want to use service pack 2.
You can remove service pack 2 from the instance and choose to revert to service pack 1 or the base version of the
product. Service pack 2 remains on the machine.
•
Uninstalling a service pack removes it completely from the machine. When you uninstall a service pack:
–
–
–
All instances of Enterprise eTIME that are at the current level revert to version 6.2.
The selected service pack is removed from the machine.
If the option to remove scripts is chosen, the database reverts to 6.2.
If you want to re-apply the service pack to Enterprise eTIME instances, first you need to download and re-install the
service pack.
Before you begin
Before you remove or uninstall the service pack, do the following tasks:
34
•
Ensure that all servers and the database are running the same version of Enterprise eTIME. This allows the system
to come up in online mode after you remove or uninstall the service pack.
•
Stop the application server and other applications related to the timekeeping system. If your system includes
multiple application servers that point to the same database, you must stop all of the application servers before you
uninstall the service pack.
•
Obtain the database owner’s user name and password.
Installing Service Pack 17
Uninstalling Enterprise eTIME 6.2.17
Enterprise eTIME version 6.2 products are deployed in two phases: The installation phase of the deployment process
installs the applicable files on the host machine and the configuration phase makes the system ready to use. Because of
this two-phase process, you can remove a service pack from an instance of Enterprise eTIME without removing it from the
machine or you can completely remove it from the machine:
•
To remove a service pack version from an instance of Enterprise eTIME without removing it completely from the
machine, use Configuration Manager. When you do this, the instance reverts to the selected service pack or RTM
version.
For example, consider the following scenario: You are running service pack 5 and then install service pack 6. You
then decide that you don’t want to use service pack 6 now. Using Configuration Manager, you can select service
pack 5 or RTM or another installed service pack version to which to revert. Service pack 6 remains on the machine
and can be reapplied at any time by running Configuration Manager.
Note: This process only removes the service pack from one instance of Enterprise eTIME at a time. If you have
multiple instances running on the machine, you must remove the service pack from each instance, one at a time.
•
To remove a service pack completely from a machine, run the uninstaller. When you do this:
–
–
–
All instances of Enterprise eTIME that are at the current level revert to version 6.2.
Most files and registry entries are restored to their version 6.2 state.
The selected service pack is removed from the machine.
To apply a service pack at a later date, you must obtain the service pack and repeat the installation process.
Regardless of the process you use:
•
Before you begin the uninstallation, stop the application server and other applications.
•
If your system includes multiple application servers that point to the same database, you must stop all the
application servers before you uninstall the service pack.
•
All servers and the database must be running at the same version in order for the system to come up in online
mode.
•
If you plan to uninstall Service Pack 6 or higher and run an older version of Enterprise Device Manager that does
not have ADP InTouch Support, please read “Important: Data collection devices and downgrading to earlier service
packs” on page 36 before you begin the uninstallation.
Using Configuration Manager to remove the service pack from one instance of Enterprise eTIME
1. Back up the database.
2. Start Configuration Manager.
3. Select Modify instance > Add/Remove Service Pack.
4. At the Service Pack version prompt, select the service pack to which you want to revert.
When the Configuration Manager finishes, that particular instance reverts to the selected installed service pack; all the
others instances are left intact. In this case, /root_directory/deployments/servicepack/release_number remains.
35
Installing Service Pack 17
Using the uninstaller to uninstall the service pack from an AIX or Solaris Server
1. Back up the database.
2. On the UNIX server, stop all ADP processes by navigating to the /1/bin subdirectory of the installation directory
(typically <adp_root>/adp)and executing ./wfc stop.
3. Ensure that all ADP processes have stopped, by executing ps -eaf|egrep installation_directory. Any
lingering processes must be manually stopped by executing kill -9 pid where pid is the process ID.
4. Open a command prompt window and navigate to the service pack installation directory, typically
<adp_root>/adp.
5. Run the uninstaller by executing ./uninstall/servicepack/6.2.17/uninstaller.bin -console
If you are using an x-terminal window in a UNIX window manager, you do not need to specify -console option.
6. Uninstall the corresponding service pack from the Windows companion server to this UNIX server by going to the
Windows companion server and following the instructions in “Uninstalling or removing the service pack from
Windows systems” on page 28.
7. On the UNIX server, restart all ADP processes by navigating to the <adp_root>/1/bin subdirectory of the
installation directory and executing ./wfc start.
Important: Data collection devices and downgrading to earlier service packs
36
•
If you created ADP InTouch data in Device Manager and then want to uninstall 6.2.6 or higher to run 6.2.4 or an
older 6.2 version on the same database, contact TLM Support before you begin the downgrade process. You will
need instruction to delete the ADP InTouch data because service pack 6.2.4 and lower 6.2 service packs do not
support ADP InTouch.
•
If you use Series 4000 or ADP InTouch devices and you want to downgrade from Device Manager 6.2.7 to an
earlier 6.2.x version of Device Manager, contact TLM Support before you begin the downgrade process. You will
need instruction to restore the ability to import and softload firmware files after downgrading.
Upgrading a database from 4.x.x through 6.1.x to 6.2
Upgrading a database from 4.x.x through 6.1.x to 6.2
Important: Read this section if you need to upgrade the database from Enterprise eTIME 4.x.x through 6.1.x to
6.2.x. Note that the procedure works only on Windows systems. UNIX users must execute this procedure on
the Windows companion server.
Procedure
Important:
•
The Upgrading Enterprise eTIME document identifies the steps needed to upgrade from a pre-6.2.0 version to
version 6.2.0. It also provides details for running the installation procedure, Database Manager, and Configuration
Manager.
If you are upgrading from a pre-6.2.0 version to 6.2.17, use the following steps, which ensures that all database
upgrade scripts introduced in the service pack are used. For details about running the installation procedure,
Database Manager, and Configuration Manager, refer to Upgrading Enterprise eTIME.
•
(CE-24783) If you will upgrade an Oracle database on 10gR1 or later, clear the Oracle Recycle Bin before you
begin the upgrade process.
1. Stop Enterprise eTIME.
2. Uninstall the earlier version of Enterprise eTIME (for example, 6.1.x, 6.2.x).
3. Install Enterprise eTIME 6.2.0. Refer to the Enterprise eTIME upgrade product documentation.
Important: Do not run Database Manager immediately after you install version 6.2.0. You will run Database
Manager later in this procedure.
4. Install Enterprise eTIME 6.2.0 Service Pack 17.
If you have a Windows system, See “Installing on Windows systems” on page 22.
If you have a Solaris system, see “Installing on AIX or Solaris systems” on page 31.
Notes:
–
If there is more than one instance of Enterprise eTIME, install the service pack on an instance that uses the
target database. The upgrade.sql file will be installed, but the service pack installation will not complete.
– When the Patchelizer screen appears, do not run it. Instead, exit the screen.
5. Start Enterprise eTIME 6.2.17. The application will start in offline mode because the you have not upgraded the
database yet.
6. If the database is an Oracle database, run the following statement before executing a database upgrade:
GRANT execute ON DBMS_REDEFINITION TO TKCSOWNER
Note: This step addresses CE-16523.
7. Run Database Manager to upgrade the database to version 6.2.0. When the upgrade is complete, stop the server.
Note: If you have multiple Enterprise eTIME instances pointing to the same target database, perform the following
steps on only one of the instances. You do not need to perform these steps on every instance:
8. Run Configuration Manager and remove the Service Pack from the instance on which you installed it.
Note: When the Patchelizer screen appears, do not run it. Instead, exit the screen.
37
Upgrading a database from 4.x.x through 6.1.x to 6.2
9. Perform this step only if you are upgrading from Enterprise eTIME 6.0.x or earlier, and also upgrading from Data
Collection Manager to Enterprise Device Manager 6.2.x. Otherwise, go to step 10.
Before starting the server, run the following statement to disable the Enterprise Device Manager upgrade:
update WDMUPGRADESTATUS set UPGRADESTATETYPENUM = 0
10. Start the Enterprise eTIME application server to populate the database with 6.3.0 silver data.
11. After the application server has started, stop the server.
12. Run Configuration Manager and add the Service Pack to the instance. When the Patchelizer screen appears, enter
the information:
DBMS — Select Mss (SQL Server) or Ora (Oracle).
Username and password — Enter the database owner logon information.
Connection Method — If the database is on a separate server, select Server and enter the fully-qualified
domain server name and database or SID name. Change the database port number if the database uses a
non-default port number. If the database is on the same server as the application, select JDBC URL and verify
that the information is correct.
SP Version — Select the service pack version to apply.
Click Run Scripts.
13. When the success message appears, click Exit. The configuration process finishes.
14. Perform this step only if you are upgrading from Enterprise eTIME 6.0.x or earlier, and also upgrading from Data
Collection Manager to Enterprise Device Manager 6.2.x. Otherwise, go to step 15.
Enable the Enterprise Device Manager upgrade by running the following statement:
update WDMUPGRADESTATUS set UPGRADESTATETYPENUM = 1
15. Start the application server. The Enterprise Device Manager upgrade begins.
16. Perform this step only if you are upgrading from Enterprise eTIME 6.0.x or earlier, and also upgrading from Data
Collection Manager to Enterprise Device Manager 6.2.x.
Review the application log files for issues related to converting Data Collection Manager (DCM) device
configuration to the Device Manager device profile configuration. If there are any errors, contact TLM Support.
Notes:
38
•
After you upgrade the database, the Background Processor (BGP) runs and totals data for all employees. This
processing of information inserts and updates database records.
•
It is a good practice to update database statistics. Performing this task may enhance system performance.
•
After you upgrade the database, you can install the client components of the Enterprise eTIME system that your
site uses (for example, Process Designer).
Upgrading a database from 4.x.x through 6.1.x to 6.2
–
If you have a Windows system, refer to the appropriate product installation instructions in “Installing on
Windows systems” on page 22.
Important upgrade information
(CE-22341) If you upgrade from Enterprise eTIME version 4.1 and lower to 4.3 and higher, and then interrupt the start-up
process of the application server after the upgrade, the following error appears in the StartupError.log:
“<date and time> ERROR: The CHNO0376 utility is currently running. Due to this, all BGP processes will be prevented
from starting. To resolve, restart after the CHNO0376 utility completes.
<date and time>2008-Sep-10 14:11:00 ERROR WFCService / startIt(): *** Failed to start service CHNO0376Service.”
This error condition prevents the Background Processor from running, and the error appears for all subsequent attempts to
start the application server.
This issue occurs if the startup of the application server is interrupted while the CHNO0376 service is running. When the
CHNO0376 process is interrupted, it cannot restart. In turn, the application server cannot restart without the CHNO0376
process running to completion.
If this situation occurs during the upgrade process, perform the following steps:
1. Stop all application servers.
2. Use an interactive SQL database tool (for example, SQL Plus or Query Analyzer) to do the following:
a. Access the KCSUPGRADEHISTORY database table.
b. In the table, change "UPGRADE.SQL CHNO0376" to "UPGRADE.SQL," using the following syntax:
update kcsupgradehistory set upgradescriptname = 'UPGRADE.SQL' where
upgradescriptname = 'UPGRADE.SQL CHNO0376'
3. Restart one application server to allow the CHNO0376 service to run to completion. To ensure that the service is
running, open the StartupInfo.log file and look for the following message:
“Starting the CHNO0376 utility. This may take several hours to complete.”
4. To ensure that the CHNO0376 utility ran to completion, look in StartupInfo.log for the following messages:
“CHNO0376 processing is complete.”
“The WFC Server has started in Online [or Offline] mode.”
Note the following important information:
•
The CHNO0376 service needs to update the database only once after upgrading from Enterprise eTIME version
4.1 or lower to version 4.3 and higher. During subsequent application server start ups, including upgrades to later
versions, the CHNO0376 service will recognize that it ran to completion and continue the startup process.
Do not disable or bypass the CHNO0376 service from running. If you do this, employees who were not updated may have
incorrect vested and probationary accrual balances.
39
Implementation considerations
Implementation considerations
ADP InTouch
Disabling/enabling ADP InTouch in Device Manager
ADP InTouch features are enabled by default in Device Manager. If you will not use ADP InTouch and you need to disable
the ADP InTouch setup options from the user interface, follow the instructions below.
Important: If you created any ADP InTouch devices or building blocks, delete them before you disable ADP InTouch.
To disable ADP InTouch support in Device Manager:
1. Stop Enterprise eTIME using the desktop icon.
2. Create or edit a file called custom_WDMSite.properties in \adp\1\applications\WDM\properties and
add the following line exactly as shown, using all lowercase letters.
private.site.wdm.config.hide.intouch=true
3. Restart Enterprise eTIME.
To enable ADP InTouch support in Device Manager:
1. Shut down Enterprise eTIME.
2. Edit the file called custom_WDMSite.properties in \adp\1\applications\WDM\properties and change
the following line:
private.site.wdm.config.hide.intouch=false
3. Restart Enterprise eTIME using the desktop icon.
Timeout setting for transferring ADP InTouch soft key settings
If your system includes ADP InTouch data collection devices, change the Enterprise eTIME API Timeout value in Setup
Data Manager to 600 seconds or higher. This allows sufficient time to load soft key settings to the devices. If you try to load
soft key settings using the default value of 30 seconds, the following error messages appear:
“Cannot communicate with Enterprise eTIME application server: <application server name>
Contact your system administrator to ensure application server is running”
or
“No items have been configured for the source data setup category: Soft Key Settings”
To change the timeout value:
1. In Enterprise Archiver - Setup Data Manager, select Admin > Change Enterprise eTIME API Timeout.
2. In the dialog box, change the setting to 600 and click OK.
40
Implementation considerations
Maximum content length setting on IIS 7 servers
If you are using IIS 7, verify that the IIS server accommodates a maximum content length of at least 300 MB. Do this before
you import ADP InTouch .krx to the server.
To increase the maximum content length:
1. Click START > RUN > inetmgr on the IIS 7 server.
2. When the screen appears, select the appropriate system name under Connections.
3. On the same screen, click Request Filtering under IIS.
4. In the Actions pane, click Edit Feature Settings. A popup window appears.
5. In Edit Request Filtering Settings > Request Limits, change the value in the Maximum allowed content length
(bytes) field to 300000000.
6. Click OK and close inetmgr.
Load balancing and QuickGlance transactions
(CE-25272) If the Enterprise eTIME system uses load balancing and employees perform QuickGlance transactions on
Series 4000 timeclocks, the overall performance of the system can be greatly reduced.
To prevent performance from being affected, set the security setting called
site.security.authentication.urldispatcher in System Settings to the following value:
com.kronos.wfc.platform.server.servlet.urldispatcher.security.
AnyBrowserAuthentication
Vertically-scaling and device communication
If you will use Series 4000 timeclocks and implement vertical scaling with your Enterprise eTIME installation, you must
configure the timeclocks to use device-initiated communication. Vertically scaled installations do not support serverinitiated device communication.
Note: Because Enterprise eTIME supports 64-bit operating systems, there is no longer a need for vertical
scaling: a single instance of Enterprise eTIME can take advantage of the machine’s total memory capacity. For
more information, contact your TLM Representative.
Database — Oracle
Use the default Oracle value of EXACT, for CURSOR_SHARING
ADP recommends that you use the default Oracle value of EXACT, for CURSOR_SHARING. This setting has provided the
most predictable performance and functionality in both ADP benchmarks and client production systems.
ADP strongly recommends that you do not use the values of SIMILAR or FORCE, because these values have caused
isolated instances of significant performance degradation or internal Oracle errors.
41
Implementation considerations
Reports
•
(CE-19080) When Configuration Manager is used to uninstall suite products one at a time, reports that have been
removed continue to appear on the report selection list.
•
(CE-19081) Due to a Microsoft problem, when a user views the Employee Schedule – Weekly report in HTML in
the Microsoft SQL Server Reporting Services (SSRS), the following may occur: Extra pages may be displayed in
addition to the pages that contain the report data. These pages display only the report title and the header and
footer areas. When the report is exported to another format, such as PDF, the extra pages do not appear.
Translation and customization
(WFM-25997) For translation and customization purposes, the following text files are available that contain the text strings
that have changed since Enterprise eTIME 6.2.0:
•
changedStringFilesFull.6217.txt — Contains text string changes for all Enterprise eTIME 6.2.x
service packs including the current service pack.
•
changedStringFilesIncr.6217.txt — Contains text string changes associated with the current service
pack only.
The files indicate in which properties file each text string appears and, if the properties file is contained in a .jar file, the
name of the .jar file.
These files are installed with the service pack. After installation, the file is located in \adp or \<install_directory> on
Windows systems. On UNIX systems, the file is installed in <adp_root> or /usr/local/<install_directory>.
Enterprise Activities
Property setting to control cache activity
(WFM-39488) Beginning with 6.2.8, the following property has been added to WFA.properties to control cache activity and
maintain performance in heavy system use scenarios. For example:
•
Multiple instances of Activities are pointed to the same database server.
•
The system contains several thousand Activities employees.
•
The client imports new Activities employees or updating existing employees.
Performance can slow down because the application empties and then re-loads the Activities employee cache for each
employee insert, update, or delete operation.
The property is called:
com.kronos.wfa.MAX_EMPLOYEE_CACHE=<value>
The value represents a number of Activities employees. If the number of Activities employees in the system is less than or
equal to the value when Enterprise eTIME starts, the Activities employee cache pre-loads. Then, if you import or update
employees, the cache does not empty and re-load during the process.
The default value for the property is 6000. If you want to change the value of this property:
1. Create a file called custom_WFA.properties.
2. Add the setting to the file and specify the value you want to use. You cannot specify zero (0) or negative numbers.
42
Implementation considerations
Alternative method of associating durations with shifts
(WFM-40240) Two properties have been added to WFA.properties to provide the option of associating durations with shifts
based on the date and time of the creation of the duration.
The new properties are
•
•
com.kronos.wfa.ASSIGN_DURATION_TO_SHIFT_USING_INSERTEDDTM
Setting
Description
true
The application uses the date and time of the creation of the duration span to determine with which shift
the duration should be associated. If there are multiple eligible shifts, the application uses the shift with a
scheduled start time that is closest to the time of the creation of the span.
false
This is the default setting. The application uses the standard method of choosing a shift is used (the
schedule service selects the shift based on scheduled start times).
com.kronos.wfa.DURATION_INSERTEDDTM_LIMIT
Note: This property applies only if
com.kronos.wfa.ASSIGN_DURATION_TO_SHIFT_USING_INSERTEDDTM is set to “true.”
This setting indicates the maximum number of hours that a span’s creation date and time can be from the eligible
shift start/stop times, to be associated with one of the eligible shifts. This setting addresses situations where
supervisors enter durations or submit forms after the employees have worked the time. If the creation date is
beyond the set limit, the application uses the standard method of choosing a shift.
Valid values are 0 to 13. The default value is 8 hours.
To change the property settings:
1. Create a custom_WFA.properties file in a text editor.
2. Add the properties and settings you want to use to the file.
3. Save the file and stop and then re-start Enterprise eTIME.
Support for SharePoint 2007
(CE-19597 and CE-19348) Enterprise eTIME 6.2 Service Pack 17 provides Enterprise Activities support for SharePoint
2007.
Property setting for processing labor account transfers with activities
(CE-24256) A property setting has been added to wfa.properties to allow clients who use Activity teams and Stop
forms only to choose whether account transfer times are considered when the application adjusts activity start and end
times. The new property setting is called:
com.kronos.wfc.activities.calculator.business.INCLUDE_TRANSFERS_IN_FIRST_LAST_
VARIANCE
•
To cause account transfer times to have an effect on how activity start times are adjusted, set the property value to
true. This causes account transfer times and activity start times to be synchronized appropriately.
•
To prevent account transfer times from having an effect on how activity start times are adjusted, set the property
value to false.
Important: This setting is a global setting that applies to all employees.
43
Implementation considerations
The following is an example scenario for which this setting is important:
•
At 8:00 a.m., an employee joins Team 1 to perform an activity associated with labor account /101//////.
•
At 9:00 a.m., the team leader submits a Stop form for the activity.
•
At 9:15, the employee leaves Team 1 and joins Team 2 to perform an activity associated with /102//////
•
At 10:00 a.m., the leader of Team 2 submits a Stop form for the activity. The system calculated 9:00 a.m. as the
start of the activity.
If the property value is set to false, the results for this employee are:
•
The first activity starts at 8:00 a.m. and ends at 9:00 a.m. Only account /101////// is associated with the activity.
•
The second activity starts at 9:00 a.m. and ends at 10:00 a.m. Account /101////// is associated with the period from
9:00 a.m. to 9:15 a.m.; account /102////// is associated with the period from 9:15 a.m. to 10:00 a.m.
If the property value is set to true, the results for this employee are:
•
The first activity starts at 8:00 a.m. and ends at 9:15 a.m. Only account /101////// is associated with the activity.
•
The second activity starts at 9:15 a.m. and ends at 10:00 a.m. Only account /102////// is associated with the activity.
Enterprise eTIME
System settings added to Logging Context tab
(WFM-29655, WFM-42355) The following system settings have been added to help prevent performance issues related to
logging activity. The settings are located in System Configuration > Logging Context tab and are called:
•
site.LoggingContext.WFC.BUSINESS.CALLABLETOTALIZER.REPORT (added in the 6.2.4 service pack)
•
site.loggingContext.WFC.BUSINESS.TOTALIZER.REPORT (added in the 6.2.9 service pack)
These settings override the site.log.loglevel setting (Setup > System Settings > Log File tab), but only for the
corresponding Totalizer-related activity. For example, if site.log.loglevel is set to “DEBUG” and the logging context settings
are set to “ERROR,” all logging activity except for the Totalizer is performed in “debug” mode.
The default value for the new logging context settings is “ERROR.”
New location for function access control point
(CE-26851) The following function access control point is located in a different part of the access control point tree:
Consolidate Labor Values in Productivity Monitor
The control point used to be at a level below the control point for access to Productivity Monitor. Both control points are now
at the same level.
44
Implementation considerations
Enterprise Device Manager
Global setting to for re-submitting transactions
If an exception occurred during a transaction upload from a data collection device to Enterprise eTIME, the transaction
could not be resubmitted for 24 hours. A new global setting in Setup > System Settings > Global Values allows you to
control when transactions that failed to load from data collection devices to Enterprise eTIME are re-submitted. The setting
is called: global.wdm.transaction.status.pendingtimeout.minutes.
Two hours (120 minutes) is the default setting. To change the setting, enter an amount of time, in minutes, and then re-start
Enterprise eTIME. The minimum setting is 10 minutes.
Property setting to control master instance designation
(WFM-40249) Beginning with 6.2.9, you have more control over which Device Manager instances can be designated as the
master instance. Do this by adding an instance property to the custom_wdmsite.properties file. The property is
called:
site.wdm.server.master.eligible
Valid settings are “true” and “false.” A “true” setting means that instance can be a master instance.
Note the following information about setting and changing the property value:
•
If you add the property while the instance is running, stop and restart the instance so that the property takes effect.
•
After you add the property to the custom_wdmsite.properties file, you can change the setting in System Settings >
Device Manager tab. If you use this method to change the setting (instead of editing the properties file), you do not
need to stop and restart the instance.
•
If you change the setting to from “true” to “false” using System Settings > Device Manager, the instance stops
being the master instance when the next Instance Monitor cycle begins.
Setting to resolve unauthorized access to transactions
An issue related to unauthorized access to transactions was resolved in 6.2.2. However, the description did not include
information about a property that was created to support the resolution. The text that follows is the corrected text for the
issue. Please note the information about the new setting.
Note: This text has also been updated in the document called Summary of Resolved Issues in Enterprise
eTIME Suite 6.2 Service Packs that is delivered with every 6.2.x service pack documentation set.
WFM-22843
(CE-28898)
The system incorrectly allowed employees to perform pay code edit transactions at a Series
4000 timeclock in the following scenario:
•
The employee was not assigned to timeclock as a home employee.
•
The timeclock was configured to not allow non-home employees to swipe in and out at
that timeclock.
The specific transactions that were allowed in this scenario were:
•
Pay Code Hours Edit
•
Pay Code Money Edit
•
Pay Code Move Amount
45
Implementation considerations
This issue has been resolved by supporting a configuration setting that users add to the
custom_WDMSite.properties file. The name of the setting is:
private.site.wdm.paycode.edits.nonhome.alwaysenabled
To add the configuration setting:
1. Navigate to the \adp\1\applications\wdm\properties folder to find
custom_WDMSite.properties. If the file does not exist, create the file using a text
editor. Otherwise, open the file with a text editor.
2. Add the new setting to the file and set the value to false. For example:
private.site.wdm.paycode.edits.nonhome.alwaysenabled = false
3. Save the file.
4. Perform these steps on every Device Manager server in the system.
After you save the properties file, initialize all Series 4000 timeclocks to load device
configuration information.
Property setting to control re-submission of pending activities
(WFM-40250) To help prevent performance problems related to server-initiated devices and pending actions in Device
Manager, clients can add the following property to the custom.properties file:
private.site.wdm.pendingaction.hours
The property allows you to decrease the time frame that is scanned for pending actions. The default setting is 24 hours. If
you want to change the time frame:
1. Create a text file called custom.properties if the file does not already exist.
2. Add the property name and value to use. For example:
private.site.wdm.pendingaction.hours=48
3. Stop and restart the server.
For more information, contact your TLM Representative.
Enterprise Integration Manager
Viewing Link XML Log reports
(WFM-7249, WFM-24606) To view Link XML Log reports on systems that use the Apple Safari 4 or 5 browser, you must
use the “View Frame Source” option for viewing in the browser. Otherwise, the Link XML Log reports view window is blank.
46
Implementation considerations
Enterprise Scheduler
Custom location sets
(WFM-24707) The Scheduler and Workload Planner do not share custom location sets. You have to create or edit the sets
separately for each application.
System setting for future use
(WFM-42957) The site.MobileContact.defaultSequentialCallingWaitTime system setting in Setup > System
Settings >Mobile Contact is intended for future use only.
Enterprise Worksheet
Indicating when an upgrade to the Enterprise Worksheet client is recommended or required
An administrator can indicate to Enterprise Worksheet users that an upgrade to the Enterprise Worksheet client is required
or recommended by adjusting the following settings in the
\1\applications\wpk\properties\wpk.properties file:
•
oba.plugin.current.version
•
oba.plugin.lowest.supported.version
If the version of the Enterprise Worksheet client installed on the user’s system is greater than or equal to
oba.plugin.lowest.supported.version, but less than oba.plugin.current.version, a message is
displayed when the user invokes the client, indicating that the upgrade is recommended. The client can still be used in this
case.
If the version of the Enterprise Worksheet client installed on the user’s system is less than
oba.plugin.lowest.supported.version, a message is displayed when the user invokes the client, indicating
that the upgrade is required. The client’s controls are disabled until the upgrade is completed.
If the version of the Enterprise Worksheet client installed on the user’s system is greater than or equal to
oba.plugin.current.version, no message is displayed.
47
Known issues
Known issues
Enterprise eTIME
WFM-37964
Managers cannot add a comment to a punch that cannot be edited punch if they change the
shift’s work rule.
WFM-24994
If an employee is in a different time zone than the database server, justification of absences
does not update the timecard.
The Justification dialog box in the timecard has the wrong times for the missed span
associated with the absence exception. After you justify the exception, you can see the
justification in the Audits tab and the Sign-offs, Requests & Approvals tab with the wrong Start
Time, but the actual data in the timecard is not updated.
Workaround: Justify the absence exception a second time in the timecard.
Known false error condition
WFM-27027
(CE-27868)
In Enterprise Device Manager, the Devices screen shows a false error condition for random
Series 4000 timeclocks in the following scenario:
•
In Device Manager, a user selects all timeclocks and stops data collection.
•
After all timeclocks have stopped data collection, the user re-starts data collection.
On the Devices screen, the status icon next to one or more random timeclocks turns red and
an error is posted in the log file (WFC.log). The icon remains red until the next netcheck
occurs to verify communication between the timeclocks and Device Manager. (The length of
time between netchecks is configurable, but is generally very short.)
You can ignore this error condition; there is no negative effect on Device Manager or the
timeclocks.
48
Database changes
Database changes
Database scripts
The following table lists the script files that are included in this release:
Script
Resolved issue
Description
WTK140001.sql
Placeholder for future use.
WTK140002.sql
Placeholder for future use.
WTK140003.sql
CE-27028
Database schema changes to support batch framework enhancement for Integration
Manager interface requests.
WTK140004.sql
WFM-21470
(CE-29305)
Performance enhancements to the Activities Transactions by Employee report.
Applies only to Oracle.
WTK140005.sql
WFM-23445
Update to view called VU_RPTABSENCE to correct a data reporting problem. Applies
only to Oracle.
WTK140006.sql
WFM-21458
(CE-29321)
Resolve potential performance issues when loading applets in the timekeeping
application.
WTK140007.sql
WFM-23277
Update the time zone data for the Mexico and Chihuahua time zones.
WTK140008.sql
WFM-23353
Support for Device Manager instance management feature.
WTK140009.sql
WFM-21335
(CE-29245)
Update the RPTSP_WEEKLY_COVERAGE_DETAIL stored procedure to correct
duplications in the Coverage Detail Weekly report. Applies only to Oracle.
WTK140010.sql
WFM-22948
Support Enterprise Archiver purge operations.
WTK140011.sql
WFM-23901
Add a new foreign key to the database. Applies only to Oracle.
WTK140012.sql
WFM-22424
(SCH-13608)
Provide choice of full or abbreviated pay code name display for the Location Schedule
- Weekly report.
WTK140013.sql
WFM-22361
Remove parent function access profile values that were erroneously saved in the
database. Prevent the application from saving parent function access profile values in
the future.
WTK140014.sql
WFM-21329
(CE-29239)
Add option to Coverage Counting page in Employee Self-Service scheduling to allow
or disallow scheduling overcoverage.
WTK140016.sql
WFM-21448
(CE-29291)
Correct cell rendering issue for QuickNavs that include exceptions as part of their
detail column set.
WTK140017.sql
WFM-22685
Optimize SQL scripts for Employee Self-Service requests. Includes new database
indexes for tables.
WTK140018.sql
WFM-23196
Update the RPTSP_TimeDetails stored procedure to prevent Time Detail report
failures. Applies only to SQL Server.
WTK140019.sql
WFM-23778
Support Simplified Chinese characters for the Employee Hours By Labor Account
Advanced Report. Applies only to SQL Server.
WTK140020.sql
WFM-21451
Add a new primary key to the PUNCHEVENTTRC data table to correct checksum
validation errors on Enterprise Archiver copy tasks.
WTK140021.sql
WFM-24774
Includes new database index to optimize queries on the REQSTATECHANGE table.
WTK140022.sql
WFM-24817
Improve performance of Enterprise Archiver purge operations when Enterprise
Activities is also installed. Applies only to SQL Server.
WTK140023.sql
WFM-21430
Correct hours calculations in the Staffing by Zone Report for shifts that span the day
divide. Applies only to SQL Server.
WTK140024.sql
WFM-25380
Support for Navigator (Next Generation User Interface, or NGUI).
49
Database changes
Script
Resolved issue
Description
WTK140025.sql
WFM-25901
(CE-27312)
Resolve unpredictable behavior of the Activities Event Monitor when showing
relationships between cells and labor level sets. Applies only to Oracle.
WTK140026.sql
WFM-25981
Resolve index issue with REQSTATCHANGE table.
WTK140027.sql
WFM-26524
(CE-27312)
Cause edits to labor account sets that contain only accounts used in cells or
resources, to show in Event Monitor.
WTK140028.sql
WFM-25600,
WFM-24403
Resolve sort order of jobs in Location Schedule - Monthly report when employees
transfer to different jobs within the same location.
WTK140029.sql
WFM-26137
Improve performance of Comments by Employee report. Applies only to Oracle.
WTK140030.sql
Placeholder for future use.
WTK140031.sql
WFM-26576
Database changes to support the budget-adjusted labor forecast feature.
WTK140032.sql
WFM-27392
Resolve issue with editing labor levels with wild cards. Applies only to Oracle.
WTK140033.sql
WFM-27076
Database changes to support issue pertaining to week divides with the budgetadjusted labor forecast feature.
WTK140034.sql
WFM-26895
Resolve issue with report transformers on 64-bit operating systems.
WTK140035.sql
WFM-27464
Resolve issue with process of importing new items into labor level sets using wild
cards. Applies only to Oracle.
WTK140036.sql
WFM-27724
Improve the order of widget loading for the Navigator (Next Generation User Interface,
or NGUI).
WFM-27815
Improve performance of queries related to the Background Processor (BGP).
WTK140037.sql
WTK140038.sql
Placeholder for future use.
WTK140039.sql
Placeholder for future use.
WTK140040.sql
WFM-28188
Resolve issue with the Event Manager not including results from certain labor level
sets.
WTK140041.sql
WFM-28468
Database updates (for internal use).
WTK140042.sql
WFM-28469
Database changes to support feature development.
WTK140043.sql
WFM-26706
Database changes to support feature development.
WTK140044.sql
WFM-28314
Database changes to support Navigator (Next Generation User Interface, or NGUI)
development.
WTK140045.sql
WFM-28313
Database changes to support Navigator (Next Generation User Interface, or NGUI)
development.
WTK140047.sql
WFM-28630
Resolve incorrect calculation of daily labor requirements in Schedule Planner when
forecasted labor crosses the day or week divide.
WTK140048.sql
WFM-25534
Resolve issue with the Location Schedule with Coverage report for all default pay
codes not including all of the pay codes in the pay code total.
WTK140049.sql
WFM-29746
Resolve issue with the database reconciliation reports following a database upgrade.
Applies only to Oracle.
WTK140050.sql
WFM-29483
Resolve issue with the Comments by Location report not displaying correct data after
the name of a labor level entry was changed in the organizational map.
WTK140051.sql
WFM-30340
Resolve issue where the Staffing by Zone report fails for certain employees and
locations. Applies only to SQL Server.
WTK140052.sql
WFM-29924
Resolve issue where the Comments by Employee report shows rounded punches
instead of actual punches.
WTK140053.sql
WFM-30487
Update widget descriptions for the Navigator (Next Generation User Interface, or
NGUI).
WTK140054.sql
WFM-30524
Database changes to support feature development.
50
Database changes
Script
Resolved issue
Description
WTK140055.sql
WFM-27363
Resolve issue with Schedule Editor and Schedule Planner not showing multiple day
time periods without the user having to scroll.
WTK140056.sql
WFM-31075
Resolve performance issue related to opening a Reports window.
WTK140057.sql
WFM-31258
Update the database with the correct start and end dates and times for Daylight
Savings time for Mexico City/Chihuahua.
WTK140058.sql
WFM-29749
Changes to database to prevent false errors in upgrade reconciliation reports.
WTK140059.sql
WFM-29789
Resolve performance issue with the All Zone report. Applies only to Oracle.
WTK140060.sql
WFM-30046
Resolve issue with pay code edits for full scheduled days not replacing existing shifts
with open shifts properly.
WTK140061.sql
WFM-31480
Database changes to resolve issue with INI job failures when running core loads with
Workforce Analytics. Applies only to Oracle.
WTK140062.sql
WFM-32110
Support ability to configure a soft key on a Series 4000 timeclock with a Request Time
Off QuickGlance transaction that supports day-based pay codes.
WTK140063.sql
WFM-32783
New database views to support Enterprise eTIME 6.2 integration for TeleStaff.
WTK140064.sql
WFM-32289
Resolve performance issues when repeatedly loading the Schedule Editor with
several employees.
WTK140065.sql
WFM-32345
Database change related to support for QuickGlance transactions in Device Manager.
WTK140066.sql
WFM-32867
Resolve performance issues when saving schedule edits for large groups of
employees.
WTK140067.sql
WFM-33601
Resolve issue with the Activity Transactions by Employee report including irrelevant
data when the user specifies Effective Date type and “Previously Selected
Employees.”
WTK140068.sql
WFM-29455
Support for Mobile QuickGlance with the Navigator (Next Generation User Interface,
or NGUI).
WTK140069.sql
WFM-23679
Provide added support in Device Manager for server-initiated device balancing.
WTK140070.sql
WFM-32730
Resolve the issue of multiple XML API labor standard updates interfering with each
other and creating duplicate labor standards in the database.
WTK140071.sql
WFM-32259
Provide added support for reporting invalid punch attempts.
WTK140072.sql
WFM-34921
Resolve performance issue when users enter responses to password security
questions.
WTK140073.sql
WFM-34961
Enhance performance of Enterprise Activities reports.
WTK140074.sql
WFM-28804
Add index to the KNXRUNHISTORY table to improve system performance.
WTK140075.sql
WFM-34974
Enhance Device Manager performance by adding an index to the WTKEMPLOYEE
database table.
WTK140076.sql
WFM-33108
Update database metadata for upgrade situations.
WTK140077.sql
Placeholder for future use.
WTK140078.sql
WFM-34637
Support for enhanced performance monitoring.
WTK140079.sql
WFM-31528
Resolve the issue of the Accrual Balances and Projections report showing incorrect
projected balances for employees.
WTK140080.sql
WFM-35481
Resolve performance issue with the Single Zone report.
WTK140081.sql
WFM-32113
Resolve issue related to sites that use instance management with Device Manager.
Users were not able to access Device Manager when using an Enterprise eTIME
instance that did not include Device Manager.
WTK140082.sql
WTK140083.sql
Placeholder for future use.
WFM-35282
Update a database table column data type for ADP InTouch support.
51
Database changes
Script
Resolved issue
WTK140084.sql
Description
Placeholder for future use.
WTK140085.sql
WFM-35891
Resolve issue of null forecasts in categories with insufficient POS data.
WTK140086.sql
WFM-39442
Correct hard-coded index tablespace name. Applies only to Oracle.
WTK140087.sql
WFM-38445
Resolve issue with calendar month-based grant expirations expiring at the start of the
last day of the month instead of at the end of the day.
WTK140088.sql
WFM-38764
Resolve issue with permissions when attempting to import School Calendar data.
WTK140089.sql
WFM-38732
Resolve issue with permissions when users try to update OrgSet data.
WTK140090.sql
WFM-38036
Resolve issue with SQL query consuming high amounts of CPU power and causing
poor performance when multiple users access the database simultaneously.
WTK140091.sql
WFM-36119
Resolve failure of the LoadAllowedPermissions action of the AccessProfile API to
extract all access point settings.
WTK140092.sql
WFM-39062
Resolve performance issue when loading shift segment data.
WTK140093.sql
WFM-37644
Resolve issue with SQL query causing severe system performance degradation
because of sensitivity to data size or distribution changes.
WTK140094.sql
WFM-38378
Resolve issue with some attributes showing as Unavailable in JConsole. Applies only
to Oracle.'
WTK140095.sql
WFM-30234
Resolve misalignment of days and total shift counts in the Location Schedule with
Coverage report.
WTK140096.sql
WFM-32159
Resolve issue with Sales being doubled in the Metrics tab.
WTK140097.sql
WFM-32195
Resolve issue with the timeout value for socket connections.
WTK140098.sql
WFM-21792
Resolve problem in the Activity Detail by Group report where there was a discrepancy
between the report data and the time card data.
WTK140099.sql
WFM-38534
Resolve issue with The VP_EMPLOYEESIGNOFF view creating a large number of
duplicate rows for each employee. Applies only to SQL Server.
WTK140100.sql
WFM-41304
Resolve database blocking issue that prevented connections from accessing the
database.
WTK140101.sql
WFM-42109
Resolve slow performance of the Time Detail report with the “Adjusted” option
selected. The script updates the RPTSP_TIMEDETAILS stored procedure. Applies
only to Oracle.
WTK140102.sql
WFM-39754
Resolve issue with Timecard Audit Trail report showing, under certain conditions,
punches from data collection devices when data source is set to “Timecard.”
The script performs the following actions:
• Updates the RPTSP_TIMECARDAUDITTRAIL stored procedure
• Adds FUNCTAREAID_PU1 and FUNCTAREANM_PU1 to the RPTSP_PT_TEMP
database table.
WTK140103.sql
WFM-42422
Resolve failure of group edit transactions with Activity Durations forms that contain 20
or more fields. The script modifies the data type for the PARAMETERSTRTXT column
of the GROUPEDIT database table. For Oracle, the data type is NCLOB; for SQL
Server, the data type is NVARCHAR(MAX).
WTK140104.sql
WFM-41174
Improves database performance with respect to Device Manager locking by adding an
index to the WDMDEVFILES table:
X1_WDMDEVPKGDEVFILEMM ON WDMDEVPKGDEVFILEMM
X2_WDMDEVPKGDEVFILEMM ON WDMDEVPKGDEVFILEMM
X1_WDMTRXEXCEPTIONS ON WDMTRXEXCEPTIONS
X2_WDMTRXEXCEPTIONS ON WDMTRXEXCEPTIONS
Applies to Oracle and SQL Server.
52
Database changes
Script
Resolved issue
Description
WTK140105.sql
WFM-39748
Resolve issue with the Restore Taking functionality in accruals not working when
employees were assigned an accrual profile through employment terms. For those
employees, the script updates the accrualprofileid in the PERSON database table to
match the one in the ASSIGNACCRUAL database table.
WTK140106.sql
WFM-43116
Resolve database blocking issue that prevented connections from accessing the
database. The following new index was created for the RETROCOMMENTMM
database table:
X1_RETROCOMMENTMM ON RETROCOMMENTMM
Applies to Oracle and SQL Server.
WTK140107.sql
WFM-41584
Add system setting to specify whether the application should generate shifts for
inactive employees who are assigned to a schedule pattern. The setting is called:
global.WtkScheduler.ShiftPattern.Update.PopulateSchedule
PatternsForInactiveEmployees
WTK140108.sql
WFM-42088
Resolve database locking issues. The resolution included creating the following
indexes:
X1_DATASOURCE ON DATASOURCE
X2_REQSTATCHGCMNTMM ON REQSTATCHGCMNTMM
X3_REQSTATCHGCMNTMM ON REQSTATCHGCMNTMM
X4_REQSTATCHGCMNTMM ON REQSTATCHGCMNTMM
X2_SHFTASGNCOMNTMM ON SHFTASGNCOMNTMM
X3_SHFTASGNCOMNTMM ON SHFTASGNCOMNTMM
X4_SHFTASGNCOMNTMM ON SHFTASGNCOMNTMM
X7_SHIFTASSIGNMNT ON SHIFTASSIGNMNT
X8_SHIFTASSIGNMNT ON SHIFTASSIGNMNT
X9_SHIFTASSIGNMNT ON SHIFTASSIGNMNT
XF_TIMESHEETITEM ON TIMESHEETITEM
XG_TIMESHEETITEM ON TIMESHEETITEM
X2_TIMEOFFREQITEM ON TIMEOFFREQITEM
X2_TSCOMMENTMM ON TSCOMMENTMM
X3_TSCOMMENTMM ON TSCOMMENTMM
X4_TSCOMMENTMM ON TSCOMMENTMM
WTK140109.sql
WFM-40718
Address incorrect forecast calculations issue by adding additional retention category
WRMDTACATEGORY to associate with the FCEVENTVOLUME database table.
Allows the database table to have a different set of retention policy rules than the other
POS tables.
WTK140110.sql
WFM-40814
Resolve performance issue with Workload API. The script adds the following index to
the WKLPATTRNASGN database table:
X4_WKLPATTRNASGN ON WKLPATTRNASGN
WTK140111.sql
WFM-42982
Resolve issue with Comments by Employee report failing to run if a comment was
associated with a time amount in the timecard that consisted of more than two decimal
places. The script modifies the RPTSP_COMMENTS procedure. Applies to Oracle
only.
WTK140112.sql
WFM-43257
Resolve issue that allowed users to delete markers from attendance events even if
their assigned function access profile was configured to disallow that capability. The
script adds a system setting called
global.attendance.attendanceEditor.useEditAttendanceEventsFAPForMarkers
(System Settings > Global Values tab).
53
Database changes
Script
Resolved issue
Description
WTK140113.sql
WFM-43082
Resolve issue with Timecard Audit Trail report not indicating “Marked as Reviewed”
status for punches. The script performs the following actions:
Updates the RPTSP_TIMECARDAUDITTRAIL stored procedure
Adds FUNCTAREAID_PU1 and FUNCTAREANM_PU1 to the RPTSP_PT_TEMP
database table.
WTK140114.sql
WFM-39025
Provide ability to change the amount of time that must pass before a transaction that
failed to upload from a data collection device can be re-submitted. The script adds a
new global setting called
global.wdm.transaction.status.pendingtimeout.minutes
The default value is 120 minutes; the minimum value is 10 minutes.
WTK140115.sql
WFM-44940
Script reserved for future development.
WTK140116.sql
WFM-44031
Resolve issue with an erroneous row of data being added for an employee to the
ASSIGNPAYRULE database table when data was extracted for payroll.
WTK140117.sql
WFM-44656
Resolve issue with the Activity Detail by Group report not returning data when it is
generated with a specific date. Modified the WFA_FLATTEN_REPTOTAL procedure.
WTK140118.sql
WFM-47332
Resolve issue of durations in the Comments by Employee and the Comments by
Location reports not showing in the proper format (decimal or minutes).
WTK140119.sql
WFM-47410
Resolve failure of “Purge Old Device Data” to delete records by adding the following
indexes:
X2_WDMDEVPKGDEVFILEMM (WDMDEVPKGDEVFILEMM database table,
WDMDEVFILESID column)
X3_WDMDEVACTIONS (WDMDEVACTIONS database table, WDMDEVPACKAGEID
column)
WTK140120.sql
Placeholder for future use.
WTK140121.sql
WTK140122.sql
Placeholder for future use.
WFM-47790
WTK140125.sql
Resolve failure to totalize information for employees who were ever assigned to a job
that was now marked for deletion.
Add licensing data changes.
WTK140126.sql
WFM-50058
Resolve issue of Activity columns not showing in Activity QuickNavs. Corrects the
Java class definition for the Activities column loader.
WTK140127.sql
WFM-49727
Resolve issue with the Perfect Attendance report including employees who did not
have perfect attendance, in certain scenarios.
WTK140128.sql
WFM-51583
Resolve issue with the performance of the database server when clients ran updates
against labor level sets.
WTK140130.sql
WFM-52091
Script for future development.
WTK140131.sql
WFM-53339
Resolve incorrect totals in the Attendance Incident Detail report when there was a
worked pay code and an exception on the same day.
WTK140132.sql
WFM-54310
Resolve ordering problem with Accrual Detail report. Applies only to SQL Server.
WTK140133.sql
WFM-55295
Resolve issue with the BatchJobTask process taking an unacceptably long time to
complete and slowing down system performance.
WTK140134.sql
WFM-56198
Resolve issue with transactions that are submitted at a data collection device after a
timecard is approved being sent to Transaction Assistant. Adds the following new
setting to WTKGLOBALSETTING database table:
global.wdm.dataCollection.allow.transactions.after.timecard.approval=true
WTK140135.sql
WFM-56175
Resolve issue related to the system incorrectly carrying forward overtime hours for
employees even if they did not qualify for overtime during the previous pay period.
54
Database changes
Script
Resolved issue
Description
WTK140136.sql
WFM-56119
Added a column called SHIFTLOCATORDTM in the WFAREPACTYSPAN database
table to support the ability to select which eligible shift to associate with an activity
duration.
WTK140137.sql
CENG-417/
WFM-58268
Update stored procedure called PROCEDURE RPTSP_PersonJobAssignment to
improve performance when users generate the Person Job Assignment report.
WTK140138.sql
CENG-1098/
WFM-58159
CENG-431/
WFM-58159
Add a record retention policy to prevent Attendance audit data from being purged by
Enterprise Archiver and Express Archive.
WTK140139.sql
CENG-273/
WFM-59577
Resolve issue in Event Manager that prevented a user from viewing other event
details after viewing the Batch Service Performance Records Purge event.
WTK140140.sql
CENG-588/
WFM-59565
Support for HyperFind-based address book by modifying the WTKGLOBALSETTING
database table.
WTK140141.sql
CENG-1367
Support for Inbox audit feature by adding a new database table called
MSGAUDITLOG.
WTK140142.sql
CENG-937
Resolve issue with the Generic Data Access Profiles report not generating if the name
of the report contained more than 50 characters.
WTK140143.sql
CENG-3226/
WFM-57059
Resolve issue with incorrect accrual balances in the Accrual Detail report in certain
scenarios.
WTK140144.sql
CENG-3748
Resolve issue with some QuickNavs taking an unacceptably long time to load.
WTK140145.sql
CENG-3814
Script for internal development work.
WTK140146.sql
CENG-4812
Resolve issue with Accrual Detail report not showing correct balance forward amounts
related to expiring grants.
WTK140147.sql
CENG-5420
Resolve issue with the Accrual Reporting Period QuickNav not showing projected
balances as a combination of projected amount and vested amount, as expected.
WTK140148.sql
CENG-6821
Resolve issue with the Express Archiver copy process creating unnecessary indexes
preventing clients from being able to purge their databases.
WTK140149.sql
CENG-7239
Resolve issue with offline activities punches at InTouch devices being duplicated when
Device Manager collected them.
WTK140150.sql
CENG-7590
Update to the RPTSP_COMMENTS stored procedure to esolve issue with duplicate
records in the LABORACCT database table.
WTK140151.sql
CENG-7826
Resolve issue with the Weekly Rest report indicating rest time violations when
none had occurred. Updated database function to properly process rest
periods that cross two weeks and contain enough rest for both weeks.
WTK140152.sql
CENG-5766
Resolve issue with data being removed from the EMPACCRUALS database table
when users edit accrual policies.
55
Other database changes
Other database changes
Because the following changes occurred in 6.2 service packs, the corresponding information is not in the version 6.2.0
product documentation. It is presented here as supplements to the indicated documentation.
New Device Manager database tables (introduced with 6.2.7)
This information supplements the 6.2.0 version of the Enterprise Device Manager Database Tables Reference Guide.
WDMSERVERDEVICES
The Device Manager Server Devices table contains a list of the devices for a particular server.
Columns, Data Types, and Null Constraints
Column Name
Oracle
SQL Server
Null Constraint
WDMSERVERMGRID (pk)
Number(12)
Int
Not Null
DEVICEIDLISTTXT
NCLOB
nVarChar(max)
Null
UPDATEDTM
Date
DateTime
Not Null
VERSIONCT
Number(12)
Int
Not Null
Column Definitions
WDMSERVERMGRID — The Device Manager Server Manager ID column contains a system-generated number that
uniquely identifies the server manager. This column is the primary key for the table.
DEVICEIDLISTTXT — The Device ID List Text contains a list of the devices on the server.
UPDATEDTM — The Update Date Time column indicates the date and time of the last record update.
VERSIONCT — The Version Count column stores the version number of the row. It is modified each time the row is
created or updated. This attribute is provided for internal system use only. It enables optimistic locking when more than
one person is editing the same database row.
WDMSERVERMGR
The Device Manager Server Manager table contains information about the Server Manager, which controls data flow from
the Device manager server to and from devices using the server-initiated protocol.
Columns, Data Types, and Null Constraints
Column Name
Oracle
SQL Server
Null Constraint
WDMSERVERMGRID (pk)
Number(12)
Int
Not Null
HOSTNAME
nVarChar2(250)
nVarChar(250)
Not Null
HEARTBEATDTM
Date
DateTime
Not Null
VERSIONCNT
Number(12)
Int
Not Null
INSTANCENAME
nVarChar2(250)
nVarChar(250)
Not Null
ISMASTERSW
Number(12)
Int
Not Null
ISACTIVESW
Number(12)
Int
Not Null
56
Other database changes
Columns, Data Types, and Null Constraints
Column Name
Oracle
SQL Server
Null Constraint
WEBSERVERNM
nVarChar2(250)
nVarChar(250)
Null
WFCSERVERID
Number(12)
Int
Null
ALTERNATEWEBSERVERNM
nVarChar2(1000)
nVarChar(1000)
Null
HASDUNCONNECTIONSW
Number(12)
Int
Not Null
APPSERVERSTARTDTM
Date
DateTime
Not Null
DEVICEIDLISTTXT
NCLOB
nText
Null
HOSTADDRESSTXT
nVarChar2(250)
nVarChar(250)
Null
Column Definitions
WDMSERVERMGRID — The Device Manager Server Manager ID column contains a system-generated number that
uniquely identifies the server manager. This column is the primary key for the WDMSRVRMGR table.
HOSTNAME — The Host Name column contains the name of the device that is registered and stored in your Domain
Name System (DNS) database.
HEARTBEATDTM — The Heartbeat Date Time column reports the current database upgrade date and time.
UPDATEDTM — The Updated Time column indicates the date and time of the last record update.
VERSIONCNT — The Version Count column stores the version number of the row. It is modified each time the row is
created or updated. This attribute is provided for internal system use only. It enables optimistic locking when more than
one person is editing the same database row.
INSTANCENAME — The Instance Name column contains a name that is assigned to an instance of the suite after it is
installed.
ISMASTERSW — The Is Master Switch column indicates whether the server is a master.
0 = The server is not a master. (Default)
1 = The server is a master.
ISACTIVESW — The Is Active Switch column indicates whether the server is active.
0 = The server is inactive. (Default)
1 = The server is active.
WEBSERVERNM — The Web Server Name column contains the name of the web server.
WFCSERVERID — The Server ID column contains the ID of the server.
ALTERNATEWEBSERVERNM — The Alternate Web Server Name column contains the name of the alternate web
server.
HASDUNCONNECTIONSW — The Host Application Server Dial-Up Network Connection Switch column indicates that
the server has Dial-Up Networking (DUN) connections available. In a multi-server configuration modem devices (4500
and eventually 4530) can only be assigned to a server with DUN connections. Each device will have a phone number
in its connection information to indicate that it is a dialup (modem) device.
0 = There is not a dial-up network connection available. (Default)
1 = There is a dial-up network connection available.
57
Other database changes
APPSERVERSTARTDTM — The Application Server Start Date Time Column contains the start date and time of the
application server.
DEVICEIDLISTTXT — The Device ID List Text contains a list of the devices on the server.
HOSTADDRESSTXT — The Host Address Text column contains the host name or address of the network interface
used by Device Manager.
Change to WDMFRMWAREFILELOAD table (introduced in the 6.2.8 service pack)
Changes to the database table pertain to the WDMFRMWAREFILELOADDATA column. The changes are italicized in the
following illustration. This information supplements the 6.2.0 version of the Enterprise Device Manager Database Tables
Reference Guide.
Column Name
Oracle
SQL Server
Null Constraint
WDMFRMWAREFILELOADID (pk)
Number(12)
Int
Not Null
WDMFRMWAREFILELOADNM
nVarChar2(50)
nVarChar(50)
Not Null
WDMFRMWAREFILELOADDATA
BLOB
VARBINARY
Null
WDMFRMWAREFILEID (fk)
Number(12)
Int
Not Null
58
Issues Resolved in Service Pack 6.2.17
Issues Resolved in Service Pack 6.2.17
Within each section, issues are listed in descending, numeric order.
Database
CENG-6821
The Express Archiver copy and reconcile process did not complete properly resulting in clients
not being able to purge their databases.
The solution included the creation of a new script called WTK140148.sql.
CENG-5259
If a client started Enterprise eTIME on a 2012 SQL server instance, the following error
message appeared in the startuperror.log file:
“Could not find stored procedure ‘sp_dboption’”
The error condition did not affect operation of the system, but clients understandably
interpreted the message as indicating a problem.
APIs
Enterprise eTIME
CENG-5526
When users attempted to update information relating to employment terms in their generic
data access profiles through the XML API, the update failed and the following error message
appeared:
“WFP-00435 This type is not under GDAP Control”
Enterprise eTIME
CENG-4881
Using the XML API to add triggers to the definition of a tip compliance rule caused the following error
message to appear:
"WTK-01281 The trigger sequence numbers must be unique per revision."
The import added the triggers, but all triggers were assigned a sequence number of “1.”
Sequence numbers should be automatically generated for triggers that are added. The
sequence number tag for the XML API is optional; users should not have to include the tag to
ensure that imported triggers are sequenced.
Enterprise eTIME
CENG-4505
Enterprise eTIME
CENG-4559
Using the XML API, users could not add notes to existing comments for punches in timecards.
This issue has been resolved by adding an action called "UpdateComment" to the Punch XML
API tag. This action allows users to add and edit comments with or without notes.
The API for importing manager IDs to a Delegate Profile list did not include an action to
remove specific managers from the list. The user interface does allow users to remove
managers from Delegate Profile lists.
This issue has been resolved by adding an action called “DeleteEntryList.”
59
Issues Resolved in Service Pack 6.2.17
Enterprise Activities
CENG-7239
Large numbers of duplicate activities punches were created in the following scenario:
•
Employees used InTouch devices to enter punches.
•
Enterprise eTIME was offline while employees entered punches. The punches were
stored as offline transactions.
•
When Enterprise eTIME came back online, the punches were sent to the timecards.
At the InTouch device, the collection status of the punches did not change to indicate that the
punches were collected. This condition caused system to continually try to collect the
punches, create duplicate punch entries in the WFAPUNCH database table, and adversely
affect performance.
The solution included the creation of a new script called WTK140149.sql.
CENG-6204
For employees with “Start Only” tracking status, activity stop times were incorrect in the
following scenario:
•
Yesterday, the employee performed the following actions:
–
–
–
•
Swiped in at a data collection device.
Submitted an Activity Start form after the in-punch.
Swiped out at a data collection device. The time of the swipe implicitly ends the
activity. The actual stop time remains blank in the Activity Events tab.
Today, the employee performs the following actions:
– Swiped in at a data collection device.
– Submitted an Activity Start form after the in-punch.
The actual stop time for the previous day’s activity changed from blank to today’s activity start
time. The stop time should remain the same as the out-punch time.
CENG-5976
Sometimes, the Background Processor (BGP) could not total an employee’s data because one
or more pay code edits were being processed incorrectly. The issue occurred if the system
could not determine the pay code types because of their complexity.
CENG-5698
After a manager approved an employee’s timecard, the Event Audits tab in the timecard
showed the employee’s name in the “Updated By” field for the approval. The field should show
the manager’s name.
CENG-5331
In activity profiles, the setting for the maximum duration allowed a maximum value of 23
minutes and 59 seconds. This issue has been resolved by changing the maximum setting
allowed to be 24 hours.
CENG-4933
An employee could not submit activity forms for a date that was approved in the timecard.
Some clients want their employees to be able to do this.
To provide this capability, clients can add or edit the following property to the
custom_WFA.properties file in adp\1\applications\wfa\properties:
com.kronos.wfa.DISABLE_FORM_VALIDATION_APPROVAL=true
This overrides the default behavior which prevents activity forms to be submitted for a day that
has already been approved.
If you edit the file, save it and re-start Enterprise eTIME to cause the setting to take effect.
60
Issues Resolved in Service Pack 6.2.17
Enterprise Attendance
CENG-7042
Attendance actions were not triggered as expected, based on the thresholds configured in the
employee’s Total Balance policy. This issue occurred if the difference between the threshold
settings was .01.
CENG-5824
If the automatic Attendance processor ran from Event Manager, the dates of discipline level
changes were not processed. This issue caused the following error message to appear:
“There has been no database created yet.”
If users manually ran the Apply Rules function for a time period that included discipline level
changes, the dates of the changes were processed correctly.
CENG-5783
In the Attendance Incident Tab report, the “Actual Amount” column shows amounts in
hours:minutes format (HH:MM) even if the “Durations Display” setting in the user’s display
profile was set to display durations in decimal format (HH.hh). The amounts in the Attendance
Editor appeared in the correct format.
CENG-3837
Sometimes, HyperFind queries that were configured to find employees with a certain type of
attendance event returned employees for whom the event had been deleted using the
Attendance Editor.
Enterprise eTIME
CENG-8714
If users selected a date range that defined a month for a Worked Account Detail QuickNav,
home accounts were not included in the information that was returned.
The Worked Account Detail QuickNav did not show worked account rows in their entirety in
the following scenario:
•
The roll-up column set for the QuickNav included any of the following columns:
•
– Pay Code Total|Actual
– Pay Code Total| Contracted
– Pay Code Total| Projected
– Pay Code Total| Scheduled
Totals became unusually large.
CENG-8288
When two managers exported QuickNav information to Excel at the same time, only one of the
manager’s employee lists was exported. When the managers opened the reports they had
created, both reports contained information about the same employee list.
CENG-7896,
CENG-7707
Java-related issues occurred when users accessed specific QuickFind and scheduling pages.
CENG-7826
The Weekly Rest report indicated a violation of required rest time when no violation had
occurred. For example, the report indicated that an employee did not receive the required 48
hours of weekly rest even though the employee did not work for at least two days.
The solution included the creation of a new script called WTK140151.sql.
CENG-7602
Sometimes, batch servers became unresponsive and could not perform batch processing
tasks. This issue occurred with batch servers that were not used by personnel to log on to the
system.
61
Issues Resolved in Service Pack 6.2.17
CENG-7590
The LABORACCT database table accumulated duplicate records. This issue caused the
system to exclude employees from the Background Processor totalization process, and
prevented users from opening employees’ timecards.
The solution included the creation of a new script called WTK140150.sql.
CENG-7480
If a QuickNav was configured to include the following columns, no data appears in them even
if an employee is on probation:
•
Accrual Ending Probationary
•
Accrual Opening Probationary
•
Accrual Prior End Probationary
CENG-7285
If Enterprise eTIME and Process Designer were installed on a drive other than the C: drive,
and users tried to run Process Designer using the “Run as administrator” option, the
application did not run.
CENG-6269
Sometimes, when users generated the Function Access Profile report, all settings were listed
but some of the labels that identified the access control points did not appear.
CENG-5981
Employees did not always receive the correct number of holiday credit hours based on the
shifts that were added to their timecards for the holiday. This issue occurred if the shifts
included in and out punches for breaks.
CENG-5918
In the HTML timecard, users could not save a pay code edit that involved a pay code with a
plus sign (+) in its name. When the user clicked Save, the edit did not appear in the timecard.
CENG-5766
Editing accrual policies and saving the edits caused data in the EMPACCRUALS database
table to be removed. This issue caused all Accrual reports to return no data.
The solution included the creation of a new script called WTK140152.sql.
CENG-5526
When users attempted to update information relating to employment terms in their generic
data access profiles through the XML API, the update failed and the following error message
appeared:
“WFP-00435 This type is not under GDAP Control”
CENG-5127
A manager whose function access profile was configured to not allow deleting notes that other
managers entered in the timecard were able to delete the notes.
CENG-5102
In the Audit tab in the project view or hourly timecard, the “User” and “Data Source” columns
showed incorrect information for employees who were paid from schedules and edited their
hours in the timecard. The incorrect information also showed on the Timecard Audit Trail
report.
For example, if an employee edited hours in the timecard, the “User” column showed
“SYSTEM:SYSTEM::SYSTEM” and the “Data Source” column showed “Schedule.” The two
columns should show <user account:server url::IPaddress> and “Timecard,” respectively.
62
Issues Resolved in Service Pack 6.2.17
CENG-4881
Using the XML API to add triggers to the definition of a tip compliance rule caused the following error
message to appear:
"WTK-01281 The trigger sequence numbers must be unique per revision."
The import added the triggers, but all triggers were assigned a sequence number of “1.”
Sequence numbers should be automatically generated for triggers that are added. The
sequence number tag for the XML API is optional; users should not have to include the tag to
ensure that imported triggers are sequenced.
CENG-4679
The Project View timecard incorrectly showed a two-week time period in the following
scenario:
•
The user’s assigned display profile was configured with Monday as the start of a week
(Display Profile > Timecard > Project View > Project View Start Day)
•
The user opened the timecard using the “Week to Date” time period selection.
This issue did not occur with any other day designated as the start of a week.
This issue has been resolved so that the Project View and Hourly timecards reference this
“start day” setting in the display profile when the “Week to Date” time period is selected.
CENG-4559
The API for importing manager IDs to a Delegate Profile list did not include an action to
remove specific managers from the list. The user interface does allow users to remove
managers from Delegate Profile lists.
This issue has been resolved by adding an action called “DeleteEntryList.”
CENG-4537
The TeleTime BulkPunches API incorrectly allowed duplicate punches to be imported. The
expected error message, “WTK-03273 Cannot duplicate a punch” did not appear. The
duplicate punches were inserted into timecards.
CENG-4505
Using the XML API, users could not add notes to existing comments for punches in timecards.
This issue has been resolved by adding an action called "UpdateComment" to the Punch XML
API tag. This action allows users to add and edit comments with or without notes.
CENG-4119
In multi-server environments, when a client imports configuration changes to the
organizational map, it takes an unacceptably long time for the changes to appear in the
forecast map at other servers.
CENG-4025
The system did not process overtime hours correctly in the following scenario:
•
The employee’s overtime rule was configured to reset the overtime counter each week on
a specified day and at a specified time (for example, every Friday at noon).
•
The employee’s worked hours exceeded the overtime limit on the day that the counter
resets, but before the time of the reset.
The hours over the limit were not processed as overtime.
63
Issues Resolved in Service Pack 6.2.17
CENG-3968
The Background Processor (BGP) could not total information for employees in the following
scenario:
•
The application server was in a United States time zone.
•
Employees worked in other time zones.
•
Employees in other time zones worked on the day of the spring Daylight Saving time
change that occurred in the United States.
•
On that day, employees worked before 2:00 a.m. according to United States time.
CENG-3870
A Late IN exception appeared in an employee’s timecard for a punch that was not late. This
issue occurred for in-punches for a scheduled shift that started after a scheduled on-call work
rule transfer shift. The Late IN exception disappeared if the on-call shift was removed or when
the employee punched out for the day.
CENG-3650
If a client performed extensive network monitoring, many “IE 404” error messages appeared.
This issue occurred if the site.portal.theme.from.server setting (Setup > System Configuration
> System Settings > Display tab) was set to “true.”
This issue has been resolved so that the error messages do not appear whether the
site.portal.theme.from.server setting is set to “true” or “false.”
CENG-3409
Under certain conditions, multiple rows were created in the LABORACCT database table for
the same combination of labor level entries. This issue caused the database table to be much
larger than it had to be, affecting system performance.
Enterprise Scheduler
CENG-9758
When using any of the following requests with the WSAScheduleGroupRollup XML API, if the
user specified “<None>” for the default HyperFind query, the API did not run successfully:
•
Retrieve
•
RetrieveForUpdate
•
Update
The following message appeared in the XML responses:
“WTK-02566 Unable to find Default HyperFind Query”
CENG-7582
In Schedule Planner, when a manager accessed the schedule for an employee who was
assigned a percent allocation rule, the scheduled hours total was incorrect. If the manager
edited the schedule (for example, added a shift), the scheduled hours total changed to the
correct value. Then, when the manager saved the schedule, the total became incorrect again.
CENG-6992
If employees were removed from a schedule group that had an effective date span beyond the
shift builder’s “populate through” date, a row sequence error condition occurred. The following
error message appeared:
“WFP-01037 SQL Statement Failed (may be caused by database issues).”
This issue resulted in users not being able to add or edit schedules.
CENG-6340
64
A “Null Parameter” error condition occurred when users tried to add shifts in the “By Job” tab in
the Schedule Planner.
Issues Resolved in Service Pack 6.2.17
CENG-5011
In Schedule Planner, the Hours Summary tab showed incorrect totals for a pay code for
signed off date ranges.
CENG-4731
When users selected Shift Swap Request from My Requests, it took an unacceptably long
time to show the information and user interface for swapping shifts. Also, there was no visual
indicator that the system was trying to respond.
CENG-4470
Sometimes, when users tried to run the Schedule Generator to create open shifts for locations
in Schedule Planner, the following error message appeared:
"WTK-02627 The segment span overlaps with existing span in the shift code."
Existing shift segments should not interfere with the creation of open shifts.
CENG-4448
If any shifts were locked when users tried to run Schedule Generator to create open shifts, the
operation failed and the following error message appeared:
“WTK-02914 Shift is locked.”
Device Manager
CENG-5911
Modem communication between Device Manager servers and data collection devices failed
after Device Manager was restarted. The following error message appeared:
"Unable to successfully communicate with the device. [50046];BATCHDC)"
The following type of entry appeared in the Enterprise eTIME log file each time the server tried
to communicate with the devices:
“Can't connect DunConnection for the device: This connection is already being
dialed.(756)”
CENG-5661
Communication with data collection devices fail in the following scenario:
•
The devices are configured for server-initiated communication.
•
The devices use secure communication (HTTPS).
•
Network connectivity issues occur and then are resolved.
Communication with the devices does not resume as expected. The client needs to restart the
application server.
Integration Manager
CENG-3698
Exporting a negative value to a field that is defined as HH:mm always showed the leading
negative sign, even if the option to show the sign was not selected in the Output Field portion
of the interface configuration.
65
Issues Resolved in Service Pack 6.2.17
66
Appendix: Enterprise eTIME products and SharePoint on the same server
Appendix: Enterprise eTIME products and SharePoint on the
same server
Important: This appendix applies only to clients who install Enterprise eTIME 6.2 products and then want to
install SharePoint on the same machine. You must perform additional configuration tasks for SharePoint and
the Microsoft IIS web server. If you do not, you cannot access the Enterprise eTIME products.
There are three sections:
•
“Initial configuration procedure” on page 67
•
“Procedure for Microsoft IIS version 7” on page 68
•
“Procedure for Microsoft IIS version 6” on page 69
Initial configuration procedure
1. After you install Enterprise eTIME 6.2.17:
a. Log on to the system and select Setup > System Configuration > System Settings.
b. Select the Web/App Server tab and enter the name of the web server machine in the
site.webserver.webServerHostName field.
2. Install Microsoft Windows SharePoint Services 3.0 or Microsoft Office SharePoint Server 2007.
3. Add alternate access mappings for the top-level Sharepoint-80 web site. To do this, execute the following
command:
stsadm.exe -o addzoneurl
-url <protocol://existing.WebApplication.URLdomain>
-urlzone <default, extranet, internet, intranet, custom>
-zonemappedurl <protocol://outgoing.url.domain>
-resourcename <non-web application resource name>
Example:
Stsadm -o addzoneurl
-url http://zepher
-urlzone Default
-zonemappedurl http://zepher.adp.com
where zepher is the URL for the SharePoint Server web application.
If the alternate mapping is successful, the message “Operation completed successfully” appears.
4. Proceed to one of the following procedures, depending on which version of Microsoft IIS you use:
–
–
“Procedure for Microsoft IIS version 7” on page 68
“Procedure for Microsoft IIS version 6” on page 69
67
Appendix: Enterprise eTIME products and SharePoint on the same server
Procedure for Microsoft IIS version 7
1. Ensure that you have completed the steps in “Initial configuration procedure” on page 67.
2. Select Start > Administrative Tools > Internet Information Services (IIS) Manager. In the IIS Manager window,
expand the contents of the local computer. Then, expand the contents of the Sites folder.
3. Enable anonymous access to Sharepoint-80:
a. Select Sharepoint-80.
b. Select Authentication under IIS section in Featured View.
c.
Click Open Feature option from Actions tab.
d. In the Features View select Anonymous Authentication and Click on Enable in Actions tab.
4. Add a “jakarta” virtual directory to the Sharepoint-80 web site:
a. Right-click Sharepoint-80 and select Add Virtual Directory.
b. Add a virtual directory called “jakarta” (case-sensitive) as Alias.
c.
Enter the following physical path, and then click OK:
C:\ADP\jboss_connectors\IIS
d. Select Jakarta virtual directory and then open Handler Mappings from Features View.
e. Click on Edit Feature Permissions... from Actions tab and select Scripts and Execute.
5. Add a “1static” virtual directory to the Sharepoint-80 web site:
a. Right-click Sharepoint-80 and select Add Virtual Directory.
b. Add a virtual directory called “1static” (case-sensitive) as Alias.
c.
Enter the following physical path, and then click OK:
C:\ADP\1
d. Select the 1static virtual directory; then open Handler Mappings from Features View.
e. Click on Edit Feature Permissions.. from the Actions tab, and select Scripts.
6. Add applications, plug-ins, and help virtual directories to the wfcstatic virtual directory.
To add an applications virtual directory
a. Right-click 1static and select Add Virtual Directory.
b. Add a virtual directory called “applications” (case-sensitive) as Alias.
c.
Enter the following physical path, and then click OK:
C:\ADP\1\applications)
To add a plug-ins virtual directory:
a. Right-click 1static and select Add Virtual Directory.
b. Add a virtual directory called “plugins” (case-sensitive) as Alias.
c.
Enter the following physical path, and then click OK:
C:\ADP\1\plugins
To add a help virtual directory:
a. Right-click 1static and select Add Virtual Directory.
b. Add a virtual directory called “help” (case-sensitive) as Alias.
68
Appendix: Enterprise eTIME products and SharePoint on the same server
c.
Enter the following physical path, and then click OK:
C:\ADP\help)
7. Add a “5001” virtual directory to the Sharepoint-80 web site:
a. Create a temporary folder on the C:\ drive. For example, C:\test.
b. Right-click Sharepoint-80 and select Add Virtual Directory.
c.
Add a virtual directory called “5001” (case-sensitive) as Alias.
d. Enter the path of the temporary folder (for example, C:\test), and then click OK:
e. Select 5001 virtual directory and then open Handler Mappings from Features View.
f.
Click on Edit Feature Permissions... from Actions tab and select Scripts.
g. Select 5001 and double-click HTTP Redirect in the IIS section.
h. Select the check box called “Redirect request to this destination” and enter /1.
i.
Select the permanent (301) from the Redirect Behavior section.
8. Remove the jakarta, 1static, and 5001 directories from the default web site:
a. Expand the Default Web Site.
b. One at a time, right-click on each directory and click Delete.
9. Select the default web site and double-click on the ISAPI filters icon. Ensure that there is no Jakarta entry. If there
is, delete the entry.
10. Select the SharePoint 80 web site double-click on the ISAPI filters icon. Ensure that there is a Jakarta entry. If a
Jakarta entry is not there, use the add ISAPI plus sign and add the filter. Specify the following information:
– Filter Name: Jakarta
– Executable: C:\adp\jboss_connectors\IIS\ isapi_redirect.dll
11. Restart IIS.
Procedure for Microsoft IIS version 6
1. Ensure that you have completed the steps in “Initial configuration procedure” on page 67.
2. Select Start > Administrative Tools > Internet Information Services (IIS) Manager. In the IIS Manager window,
expand the contents of the local computer. Then, expand the contents of the WebSites folder.
3. Enable anonymous access to Sharepoint-80:
a. Right-click Sharepoint-80 and select Properties.
b. Click the Directory Security tab and click Edit in the Authentication and access control group box.
c.
In the Authentication Methods dialog box, select the “Enable anonymous access” check box. Then, click OK.
4. Add a “jakarta” virtual directory to the Sharepoint-80 web site:
a. Right-click Sharepoint-80 and select New > Virtual Directory.
b. Add a virtual directory called “jakarta” (case-sensitive) as Alias.
c.
Enter the following physical path, then click OK:
C:\ADP\jboss_connectors\IIS
d. In the Virtual Directory Access Permissions box, select Run scripts and Execute.
5. Add a “1static” virtual directory to the Sharepoint-80 web site:
a. Right-click Sharepoint-80 and select New > Virtual Directory.
b. Add a virtual directory called “1static” (case-sensitive) as Alias.
69
Appendix: Enterprise eTIME products and SharePoint on the same server
c.
Enter the following physical path, and then click OK:
C:\ADP\1
d. In the Virtual Directory Access Permissions box, select Run scripts.
6. Add applications, plug-ins, and help virtual directories to the wfcstatic virtual directory.
To add an applications virtual directory:
a. Right-click 1static and select New > Virtual Directory.
b. Add a virtual directory called “applications” (case-sensitive) as Alias.
c.
Enter the following physical path, and then click Next:
C:\ADP\1\applications)
To add a plug-ins virtual directory:
a. Right-click 1static and select New > Virtual Directory.
b. Add a virtual directory called “plugins” (case-sensitive) as Alias.
c.
Enter the following physical path, and then click Next:
C:\ADP\1\plugins
To add a help virtual directory:
a. Right-click 1static and select New > Virtual Directory.
b. Add a virtual directory called “help” (case-sensitive) as Alias.
c.
Enter the following physical path, and then click Next:
C:\ADP\help)
7. Modify the newly-created jakarta and 1static virtual directories by performing the following steps for each
directory:
a. Right-click the name of the virtual directory, select Properties, and then select the Virtual Directory tab.
b. In the Local path box, select Read, Log Visits, and Index this Resource, and then click OK.
8. Remove the jakarta and 1static directories from the default web site:
a. Expand the Default Web Site.
b. One at a time, right-click on each directory and click Delete.
9. Restart IIS.
70
Legal statement
Legal statement
The information in this document is subject to change without notice and should not be construed as a commitment by ADP, Inc. ADP is not
responsible for any technical inaccuracies or typographical errors which may be contained in this publication. Changes are periodically made to
the information herein, and such changes will be incorporated in new editions of this publication. ADP may make improvements and/or changes in
the product and/or the programs described in this publication at any time without notice. This document or any part thereof may not be reproduced
in any form without the written permission of Kronos Incorporated. All rights reserved. © 2015 Kronos Incorporated.
ADP provides this publication "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose. The ADP Logo, Enterprise eTIME and QuickPunch are registered trademarks of ADP, Inc.
CardSaver, Kronos, Kronos Touch ID, the Kronos logo, TeleTime, Timekeeper, Timekeeper Central, Workforce Accruals, Workforce Central,
Workforce Genie, and Workforce TeleTime are registered trademarks of Kronos Incorporated or a related company. "Experts at Improving the
Performance of People and Business," HyperFind, Kronos 4500 Touch ID, Kronos 4500, Schedule Assistant, Smart View, Workforce Activities,
Workforce Attendance, Workforce Central Portal, Workforce Connect, Workforce Employee, Workforce Leave, Workforce Manager, Workforce
Record Manager, Workforce Scheduler, Workforce Timekeeper, and Workforce Worksheet are trademarks of Kronos Incorporated or a related
company.
The source code for Equinox is available for free download at www.eclipse.org.
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 ADP, Inc.
Automatic Data Processing, Inc.
One ADP Boulevard
Roseland, New Jersey 07068
For more information, see the following ADP, Inc. Web page:
http://www.adp.com
71
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement