Features Introduced in Enterprise eTIME Suite 6.3

Transcription

Features Introduced in
Enterprise eTIME Suite 6.3
Service Packs
ADP Enterprise eTIME Suite
Version 6.3
The information in this document is subject to change without notice and should not be construed as a commitment by ADP, LLC. 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 and QuickPunch are registered trademarks of ADP,
LLC.
CardSaver, Kronos, Kronos InTouch, 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, Kronos 4500 Touch ID, Kronos
Enterprise Archive, 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
Task Management, 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, LLC
One ADP Boulevard
Roseland, New Jersey 07068
For more information, see the following ADP Web page:
http://www.adp.com
Service Packs
Document Release Date
6.3.1 through 6.3.14
April 2015
Contents
Contents
Introduction ................................................................................................................................................. 5
Enterprise eTIME suite ............................................................................................................................... 8
Enhancements to the Electronic Timecard Mirror report (6.3.13) .................................................. 8
Device time zone assignment with Brazilian Data Collection (6.3.12) ........................................... 8
Increased number of custom fields (6.3.12)................................................................................... 9
Custom Inventory report (6.3.6) ..................................................................................................... 9
MLSI support in SiteMinder (6.3.2) .............................................................................................. 10
Support for French (France) language pack (6.3.1)..................................................................... 12
MLSI support for password security questions (6.3.1) ................................................................. 12
Workflow Notification changes to support MLSI (6.3.1) ............................................................... 13
Enterprise eTIME ...................................................................................................................................... 15
Bank of hours data in ACJEF report (Brazilian Data Compliance) (6.3.14) ................................. 15
Enhancement to Move Amount dialog box (6.3.12) ..................................................................... 15
New global setting for processing of adjacent shifts (6.3.12)....................................................... 16
Language Support and Manager Delegation — URL Approach (6.3.10)..................................... 16
Function access control for kiosk users (6.3.9)............................................................................ 17
Enhanced configuration of grant expirations (6.3.9) .................................................................... 17
Display of threshold settings for biometric templates in People Editor (6.3.9) ............................. 17
Signed applets and setting for custom theming (6.3.8)................................................................ 18
Pay Code Definition enhancements (6.3.7) ................................................................................. 19
Reporting of pay code edits with no hours (6.3.7) ....................................................................... 22
Enhancements to the Brazil Data Collection feature (6.3.2) ........................................................ 22
Brazil Data Collection feature (6.3.1) ........................................................................................... 22
Data Only reports (6.3.1) ............................................................................................................. 23
Enterprise Scheduler ................................................................................................................................ 23
System setting for shifts in defined night periods (6.3.13) ........................................................... 23
Time Period selector in the Contact Tracking dialog (6.3.12 SP) ................................................ 24
Location-specific holiday assignments (6.3.8) ............................................................................. 25
Applying pay codes to days with multiple shifts (6.3.8)................................................................ 26
Property setting for detecting schedule rule violations (6.3.7) ..................................................... 27
Enterprise Activities .................................................................................................................................. 28
Control over how Report Results form information is applied to activities (6.3.14)...................... 28
Control of activities to use for idle time (6.3.13) ........................................................................... 28
Ability to submit activity forms for approved dates in the timecard (6.3.12) ................................. 28
Ability to select eligible shifts to associate with durations (6.3.11 SP) ......................................... 29
Property setting to disable concurrency of durations (6.3.11)...................................................... 30
Processing of non-chronological Start Only forms (6.3.10).......................................................... 31
Enhanced matching of form durations to shifts (6.3.10) .............................................................. 32
Employee filter setting for Cell Monitor (6.3.7) ............................................................................. 32
Cell event filter for Cell Monitor (6.3.7)......................................................................................... 33
Duration forms that do not create a Clock In punch (6.3.7) ......................................................... 33
Ability to apply labor standard changes to cell members (6.3.4).................................................. 33
Enterprise Attendance .............................................................................................................................. 34
Attendance Incident Tab report (6.3.8) ........................................................................................ 34
New document tags for filtering incidents (6.3.6) ......................................................................... 34
Enterprise Leave....................................................................................................................................... 35
Date-related custom tags (6.3.11) ............................................................................................... 35
Navigator................................................................................................................................................... 37
Use with screen readers (6.3.7) ................................................................................................... 37
Performance improvements (6.3.7) ............................................................................................. 37
More usable screen space for maximized widgets (6.3.7) ........................................................... 37
3
Contents
Passing of custom time frames to “classic” pages (6.3.7) ............................................................
Approval validation options for request sub-types (6.3.7).............................................................
New global time off request templates (6.3.7) ..............................................................................
Approval of time off requests that cause accrual overdrafts (6.3.7) .............................................
Timestamp editing in employee-approved time periods (6.3.7)....................................................
Ability to set default HyperFind in the Schedule widget (6.3.6) ....................................................
Constraints on opening simultaneous instances of classic pages (6.3.6) ....................................
New options for the Call List widget (6.3.6) ..................................................................................
Performance improvements (6.3.6) ..............................................................................................
Enhancements to the Staff Management widget (6.3.2)...............................................................
New location selection options .....................................................................................................
New function access control point for Navigator Import feature (6.3.2)........................................
Multiple selection support in list pages (6.3.2)..............................................................................
Single-instance control for Schedule Editor/Schedule Planner ....................................................
Setting to enable Go To Navigation options for Single and Quick Link widgets (6.3.2)................
Default Support workspace and widgets (6.3.2) ...........................................................................
Translation of widget parts, widgets, and workspaces (6.3.2) ......................................................
Workflow Enhancements - Request Manager (6.3.2)...................................................................
Editing shift segments using the Schedule widget (6.3.2) ............................................................
Enhanced Show function in the Schedule widget (6.3.2) .............................................................
Comments and notes (6.3.2) ........................................................................................................
Other Navigator enhancements (6.3.2) ........................................................................................
Enterprise Worksheet ................................................................................................................................
Reporting enhancements and product support changes (6.3.1)...................................................
Enterprise Device Manager .......................................................................................................................
Settings to control display of device status information (6.3.10)...................................................
Support for ADP QuickPunch Plus biometric templates (6.3.10)..................................................
MLSI support for transactions at ADP InTouch (6.3.1) .................................................................
Global Time Off requests at the ADP InTouch device (6.3.1).......................................................
Shift Swap QuickGlance Support at ADP InTouch (6.3.1)............................................................
Enterprise Forecast Manager ....................................................................................................................
Task-Level Labor Distribution (6.3.7)............................................................................................
Smart Operations (6.3.5) ..............................................................................................................
Enterprise Archive .....................................................................................................................................
Enhanced copy job performance (6.3.8).......................................................................................
4
37
38
38
39
40
40
40
41
42
42
44
46
47
47
47
48
48
49
51
53
53
55
57
57
58
58
58
59
59
60
60
60
65
65
65
Introduction
Introduction
This document describes new features that are introduced in Enterprise eTIME® suite version 6.3 service packs. In
some cases, the new feature information is in a separate document and is noted in the following list of features.
Note the following information:
•
The following list is sorted by service pack number.
•
The document itself presents the features, by product, and beginning with the latest feature for each product.
Each feature heading includes the service pack number in which the feature was introduced.
Service pack
number
Product
Features
6.3.14
Enterprise Activities
“Control over how Report Results form information is applied to activities (6.3.14)”
on page 28
Enterprise eTIME
“Bank of hours data in ACJEF report (Brazilian Data Compliance) (6.3.14)” on page
15
Enterprise eTIME suite
“Enhancements to the Electronic Timecard Mirror report (6.3.13)” on page 8
Enterprise Scheduler
“System setting for shifts in defined night periods (6.3.13)” on page 23
“Control of activities to use for idle time (6.3.13)” on page 28
“Device time zone assignment with Brazilian Data Collection (6.3.12)” on page 8
6.3.13
6.3.12
“Increased number of custom fields (6.3.12)” on page 9
Enterprise eTIME
“Enhancement to Move Amount dialog box (6.3.12)” on page 15
“New global setting for processing of adjacent shifts (6.3.12)” on page 16
6.3.11
“Ability to submit activity forms for approved dates in the timecard (6.3.12)” on page
28
“Time Period selector in the Contact Tracking dialog (6.3.12 SP)” on page 24
Enterprise Leave
“Date-related custom tags (6.3.11)” on page 35
“Ability to select eligible shifts to associate with durations (6.3.11 SP)” on page 29
“Property setting to disable concurrency of durations (6.3.11)” on page 30
6.3.10
Enterprise eTIME
“Language Support and Manager Delegation — URL Approach (6.3.10)” on page
16
“Processing of non-chronological Start Only forms (6.3.10)” on page 31
“Enhanced matching of form durations to shifts (6.3.10)” on page 32
Enterprise Device Manager
“Settings to control display of device status information (6.3.10)” on page 58
“Support for ADP QuickPunch Plus biometric templates (6.3.10)” on page 58
6.3.9
Enterprise eTIME
“Function access control for kiosk users (6.3.9)” on page 17
“Enhanced configuration of grant expirations (6.3.9)” on page 17
“Display of threshold settings for biometric templates in People Editor (6.3.9)” on
page 17
6.3.8
Enterprise eTIME
“Signed applets and setting for custom theming (6.3.8)” on page 18
“Location-specific holiday assignments (6.3.8)” on page 25
“Applying pay codes to days with multiple shifts (6.3.8)” on page 26
Enterprise Attendance
“Attendance Incident Tab report (6.3.8)” on page 34
5
Introduction
Service pack
number
6.3.7
Product
Features
Enterprise Archiver
“Enhanced copy job performance (6.3.8)” on page 65
Enterprise eTIME
“Pay Code Definition enhancements (6.3.7)” on page 19
Navigator
“Use with screen readers (6.3.7)” on page 37
“Reporting of pay code edits with no hours (6.3.7)” on page 22
“Performance improvements (6.3.7)” on page 37
“More usable screen space for maximized widgets (6.3.7)” on page 37
“Passing of custom time frames to “classic” pages (6.3.7)” on page 37
“Approval validation options for request sub-types (6.3.7)” on page 38
“New global time off request templates (6.3.7)” on page 38
“Approval of time off requests that cause accrual overdrafts (6.3.7)” on page 39
“Timestamp editing in employee-approved time periods (6.3.7)” on page 40
“Duration forms that do not create a Clock In punch (6.3.7)” on page 33
“Employee filter setting for Cell Monitor (6.3.7)” on page 32
“Cell event filter for Cell Monitor (6.3.7)” on page 33
6.3.6
“Property setting for detecting schedule rule violations (6.3.7)” on page 27
Enterprise Forecast
Manager
“Task-Level Labor Distribution (6.3.7)” on page 60
“Custom Inventory report (6.3.6)” on page 9
Navigator
“Ability to set default HyperFind in the Schedule widget (6.3.6)” on page 40
“Constraints on opening simultaneous instances of classic pages (6.3.6)” on page
40
“New options for the Call List widget (6.3.6)” on page 41
“Performance improvements (6.3.6)” on page 42
“New document tags for filtering incidents (6.3.6)” on page 34
6.3.5
Enterprise Forecast
Manager
“Smart Operations (6.3.5)” on page 65
6.3.4
6.3.3
6
“Ability to apply labor standard changes to cell members (6.3.4)” on page 33
No 6.3.3 release
Introduction
Service pack
number
Product
Features
6.3.2
“MLSI support in SiteMinder (6.3.2)” on page 10
Enterprise eTIME
“Enhancements to the Brazil Data Collection feature (6.3.2)” on page 22
Navigator
“Enhancements to the Staff Management widget (6.3.2)” on page 42
“New function access control point for Navigator Import feature (6.3.2)” on page 46
“Multiple selection support in list pages (6.3.2)” on page 47
“Single-instance control for Schedule Editor/Schedule Planner” on page 47
“Default Support workspace and widgets (6.3.2)” on page 48
“Setting to enable Go To Navigation options for Single and Quick Link widgets
(6.3.2)” on page 47
“Translation of widget parts, widgets, and workspaces (6.3.2)” on page 48
“Workflow Enhancements - Request Manager (6.3.2)” on page 49
“Editing shift segments using the Schedule widget (6.3.2)” on page 51
“Enhanced Show function in the Schedule widget (6.3.2)” on page 53
“Comments and notes (6.3.2)” on page 53
“Other Navigator enhancements (6.3.2)” on page 55
6.3.1
“Support for French (France) language pack (6.3.1)” on page 12
“MLSI support for password security questions (6.3.1)” on page 12
“Workflow Notification changes to support MLSI (6.3.1)” on page 13
Enterprise eTIME
“Data Only reports (6.3.1)” on page 23
“Brazil Data Collection feature (6.3.1)” on page 22
Enterprise Worksheet
“Reporting enhancements and product support changes (6.3.1)” on page 57
“MLSI support for transactions at ADP InTouch (6.3.1)” on page 59
“Global Time Off requests at the ADP InTouch device (6.3.1)” on page 59
“Shift Swap QuickGlance Support at ADP InTouch (6.3.1)” on page 60
Refer to the release notes for the version of Enterprise eTIME service pack to which you are upgrading for the following
information:
•
Installation and upgrade procedures and considerations
•
Descriptions of issues that were resolved in the service pack
The Enterprise eTIME service pack release notes are available at the site that contains this document.
7
Enhancements to the Electronic Timecard Mirror report (6.3.13)
(CENG-8186) The Electronic Timecard Mirror report (Brazilian Compliance) contains the following enhancements:
•
(CENG-6405) A separate line of information is included in the “Punches\Day Held” section of the report if a shift
crosses the day divide and another shift starts on the day that the first shift ends.
•
The “Reason” column now contains data entries.
•
(CENG-6408) If a timecard is missing punches, phantom punches no longer appear in the “Day Held” section
of the report.
•
(CENG-6409) When an employee works a shift that is either not associated with a schedule, or is associated
with a schedule with no hours (for example, a pay code for time off), the “(TC)” column of the report shows
“0000.”
•
(CENG-6410) The “Reason” text that appears in the report for punches that are deleted from the timecard now
states “Incorrect or duplicate punch.”
•
If multiple breaks are associated with a schedule, all breaks (not just the first break) appear in the “Schedule
contract” section of the report.
Device time zone assignment with Brazilian Data Collection (6.3.12)
(CENG-4255, CENG-3547) The configuration screen for Brazil Devices (Setup > Brazil Device Setup > Devices) has
been enhanced with a “Device Timezone” field. If you select “None” for this field, the device uses the timezone of the
database server. The related default interfaces for importing data have also been enhanced to allow users to specify a
timezone.
8
Increased number of custom fields (6.3.12)
The new Employee Level Fields global value enables system administrators to indicate the maximum number of
custom fields that a user can add to the list of custom fields.
1. Select Setup > System Settings > Global Values
2. Locate global.customFields.count.
3. Enter a value between 10 and 30.
4. Click Save.
5. Click Restart Server.
If users try to enter a value that is less than 10 or greater than 30, an error message appears.
Custom Inventory report (6.3.6)
(WFM-46774) A new report called “Custom Inventory” has been added to the list of database reports on the Database
tab in Setup > System Configuration > System Information. The report allows clients and ADP support personnel to
easily see the following information about an Enterprise eTIME installation:
•
Enterprise eTIME suite products that are installed
•
Custom solutions that are installed
•
Custom reports that are being used
•
Scheduled events and their status (enabled or disabled)
•
Which server is the primary server for Event Manager
9
This information about the installation helps clients and support personnel troubleshoot system issues. Also, if a client
wants to upgrade to a new version of Enterprise eTIME, this information helps to identify potential software conflicts or
incompatibilities that might prevent some functions from working.
The following illustration shows the new report selection:
The Custom Inventory report works on systems with SQL Server or Oracle databases.
MLSI support in SiteMinder (6.3.2)
Note: The feature was not fully supported in 6.3.0 and 6.3.1. This feature is fully supported beginning with
6.3.2.
If MLSI (multiple language on a single instance) is used at your site, users who log on using SiteMinder can log on in a
language other than the one specified in their locale policy.
To enable logging on in a different language:
1. Modify the policy server rules to allow a locale policy parameter.
2. Fetch locale display names using XMLAPI.
3. Add a LOGON_LOCALE_POLICY parameter to SSO logon request URLs to override the default locale for this
session.
To logon, use one of the following URLs, depending on which view (classic, Navigator, HTML) you want:
•
Classic view:
http://<server-name>/1/logonWithUID?LOGON_LOCALE_POLICY=URL.encode(<LOCALE
DISPLAY NAME>,’UTF-8’)
•
Navigator view:
http://<server-name>/1/navigator//logonWithUID?LOGON_LOCALE_POLICY=URL.encode
(<LOCALE DISPLAY NAME>,’UTF-8’)
•
HTML view:
http://<server-name>/1/navigator//logonWithMSS_SSO?LOGON_LOCALE_POLICY=URL.encode
(<LOCALE DISPLAY NAME>,’UTF-8’)
Example:
http://<server-name>/1/navigator//logonwithMSS_SSO?LOGON_LOCALE_POLICY=URL.encode
(‘Francois’,’UTF-8’)
The URL sets the language of the user’s session to that of the display name of the locale, which is passed in
the URL.
To retrieve the list of the display names from the database table called LOCALEPROFILE, use the following XMLAPI
call:
10
Request:
<Request Action=”RetrieveAll”>
<LocalePolicy></LocalePolicy>
</Request>
Response:
<Response Status=”Success” Action=”RetrieveAll”>
To configure this functionality, modify the rules in the Policy Server that is installed for SiteMinder to allow the
parameter LOGON_LOCALE_POLICY to be part of the URL. Follow these steps:
1. Open the SiteMinder Rule dialog box.
2. For the following realms, update the URL:
a. LoginWithUID
b. \navigator\loginWithUID
c.
\logonESS_SSO
3. Update the resource as:
?LOGON_LOCALE_POLICY=[a-z||A- ||0-9||%||-]*
11
Support for French (France) language pack (6.3.1)
(WFM-39854, WFM-38758) French (France) translation of the user interface and documentation is being provided,
beginning with the Enterprise eTIME Suite 6.3.0 Language Pack. Enterprise eTIME supports the French/France
translation beginning with version 6.3.1. Support includes multi-language/single instance capability.
A new sample locale policy to support the French (France) language is included in Enterprise eTIME 6.3.1. The sample
policy is automatically added when you install Enterprise eTIME, and is configured with the following default values:
Name:
France French
Display Name:
Français France
Description:
France French Locale Settings
Long Date:
dd/MM/yyyy
Short Date:
E dd/MM
Day Month:
dd/MM
Success Indicator Time:
E HHmm
Server Date:
EEEE d MMMM yyyy
Terminal:
HHmm
Status:
Inactive
MLSI support for password security questions (6.3.1)
The Forget Password-Security Questions feature has been enhanced to support MLSI (Multiple Language on a Single
Instance). Prior to this enhancement, the Forget Password feature allowed only one language or locale per instance,
which is not consistent with the MLSI feature in v6.3.
Prior to v6.3.1, security questions were entered on the Security tab in System Settings. Users could select one or more
security questions and answers, which allowed them to reset their password without contacting a system administrator.
Because the security questions were configured in system settings, they were not easily translated for sites that
supported multiple languages.
The following changes were made:
•
Configuration of security questions was moved from the Security tab in System Settings to a Global Text option
in System Configuration
•
Settings for configuring the Forget Password-Security Questions feature were moved from the Security tab to
the Global Values tab in System Settings
Configuring security questions
In v6.3.1, security questions can be configured using the new Global Text option in the System Configuration module in
Setup. The Global Text option enables administrators to create security questions on a new Global Text screen. This
supports the MLSI feature by making it easier to translate security questions.
A new Global Text option was added to the Entity list on the Export tab of the Translation Support option in System
Configuration in v6.3. On the Export tab, administrators can select a country, language, and the Global Text entity,
which creates an Excel spreadsheet that contains the security questions. The questions can then be translated and
imported back into the system.
12
When users log on and need to select or answer security questions, the questions appear in the language assigned to
them in their locale policy or the locale they selected on the logon screen.
Refer to the Enterprise eTIME Service Pack Release Notes for instructions about configuring security questions and
behavior.
Workflow Notification changes to support MLSI (6.3.1)
Workflow Notifications enables you to create messages that an application sends to inform users of specific system
events or to remind them of an action for which they are responsible. It includes custom tags that can be used to pass
data such as manager, name, pay period, and start date in messages.
Tags are data placeholders in the body or subject line of a notification message. Values for tags are captured when the
message is initiated, such as when a security alert triggers or an overtime limit has been crossed. These values are
assigned to tag keys and travel through the notification process, where they replace the tags just before the message
is sent.
In v6.3, users could implement translations of the subject and message of notification messages using the Workflow
Notifications entity in the new Translation Support feature. These translations are handled just like any text label and
are stored in the same database location (but, because they can be much larger, they are not cached like other text
labels). Otherwise import, export, and retrieval are the same as for other entities, such as pay code names.
In v6.3.1, the notification process has been enhanced to identify the locale of recipients and use that information to
render the message. If translations exist, the message is presented to the recipient in the language of his or her
assigned locale. This includes the message subject and body as well as certain tags that have been localized. Dates
are formatted using the rules in the corresponding locale profile. If a message is sent to more than one locale, multiple
translations are provided within the message.
Note: When translating workflow notification message or body text it is essential that tag names not be
translated or altered in format. However, tags can be relocated as a unit or deleted when making a
translation.
Group Edit notifications are handled in a slightly different way. The Details tag in Group Edits is actually a mini-log that
accumulates information in the user’s language as the group edit occurs. The detail labels, or fields, are in the
recipient’s language, but the data remains in the language where it was captured. In most situations, the two languages
are the same.
The following text explains the changes in more detail:
•
•
The custom tags in Generic Notification setup have been divided into groups for ease of use and localization.
In v6.3.1, the groups are:
– Leave
– Global Time Off
– Invalid Reviewer
– Overtime
– Security
A number of tag names have been altered to conform to new naming standards. Existing messages that use
any of these tags might require attention so that they continue to work properly. If you are using a message
with an altered tag, edit the message in Workflow Notifications setup.
–
–
Old tag names that differ only in capitalization from the new will continue to work without modification.
For old tag names that lack spaces between words, you might only need to open and save the message
for it to fix itself internally.
13
–
For tag names that differ in text you might need to reinsert the tag. If for example, you have a message
using “Person who performed the edit,” you would insert Group Edit User. The following list contains new
tags and (old tags) for the tag names that differ in text.
Group Edit User (Person who performed the edit)
Event Time (Entered Time)
Log File Names (FileList)
Alert Time Frame (Alert Time Period)
License Available (Available)
Reviewer Employee (Reviewers Employee)
License Feature (Feature)
Reviewer Invalid Reviewer (Reviewers Non-valid
Reviewer)
License Percent (Percent)
Reviewer List Name (Reviewers Reviewer List)
License Limit (Limit)
Reviewer Invalid Reasons (Reviewers Reason Non-valid)
License Threshold (Threshold)
Reviewer Type (Reviewers Reviewer Type)
Database Error Code (Id)
Reviewer Basis Reviewer (Reviewers Basis Reviewer)
Database Error Message (Error Message)
Reviewer Status (Reviewers Reviewer Status)
•
Existing applications were modified to use the new tags.
•
The Workflow Notification window in setup was modified to display localized tag names and to limit tag
insertion to tags that are relevant to the type of notification.
•
The scope includes all notifications (generic or otherwise) except the generic notifications issued through
Device Manager.
Notifications & Tags - FAQ
How is locale determined when a recipient is a
person in the system?
The notification process uses the locale assigned to the person. If none is
assigned, it uses the (default) site locale.
How is locale determined when only an e-mail
address is provided?
The notification process looks for a person in the system that uses the email address. If none is found, it uses the (default) site locale. If one or
more persons are found, it arbitrarily uses the first to determine locale.
Which types of tags are localized in the message?
Dates are formatted according to rules set in the corresponding locale
profile. Tags that display ADP property values are also localized.
Can a single recipient have multiple e-mail
addresses?
Yes, and each e-mail address is processed separately when extracting
locale preferences.
Is it possible to change the language delimiters in the
message subject or body?
Yes, both delimiters can be modified in Systems Settings on the E-mail
tab.
What special limitations apply to translations of
notification subject or body?
• Do not translate or otherwise modify tag names. Tags can be relocated
intact or removed to suit the translation.
• Carriage returns are not permitted in the subject line.
What is the peculiar tag name format that appears in
the translation import/export file?
The import/export file uses the internal “neutral” name that enables
localization by recipient. The neutral name is generally the same as US
English but with no spaces between words.
In what order do languages appear in a single
message?
Languages appear in the same order that they were discovered when the
recipient list was processed - with one exception: if the (default) site locale
is included, it is placed first.
Can tags be entered manually in Workflow
Notifications setup?
Yes, but they must match the intended tag name exactly, including
capitalization and spacing.
Do not put spaces before or after the tag name inside the tag < >
delimiters, nor more than one space between words.
Note: Using the insert custom tag option is easier and more accurate.
14
Enterprise eTIME
Can tags be entered manually in a localized
language?
Yes, Workflow Notifications setup UI uses tag names that match your
locale. For example, when you edit a notification with the UI set to
Mexican Spanish, you should enter the Mexican Spanish version of the
tag name.
Note: Using the insert custom tag option (which displays localized tag
names) is easier and more accurate.
What does it mean when a tag remains in the
message that is sent to a recipient?
Either the tag was not recognized or the notification process did not
receive data to replace the tag. Each type of notification supports a limited
list of tags. A tag that is not supported remains in the message. If a tag is
supported but does not seem to work properly, try reinserting the tag in
Workflow Notifications setup.
Enterprise eTIME
Bank of hours data in ACJEF report (Brazilian Data Compliance) (6.3.14)
(CENG-9354) To enable reporting of bank of hours data In the ACJEF reportThe following settings have been added to
Setup > System Configuration > System Settings > Brazilian Compliance tab:
•
site.brc.treatment.paycode.category.bankofhourscredit.name
•
site.brc.treatment.paycode.category.bankofhoursdebit.name
For each field, enter the name of a pay code defined in the system. When these fields are set, bank of hours
information appears in fields 22 and 23 of the ACJEF report.
Enhancement to Move Amount dialog box (6.3.12)
A new property setting allows you to choose the default setting for the “To: Transfer” field in the Move Amount dialog
box.
The Move Amount function is accessed from the Totals and Schedule tab in the timecard and is used to move hour
amounts between pay codes. You can also specify a labor transfer to associate with the transaction. By default, the
“To: Transfer” field indicates the same labor account as in the “From: Transfer” field. Some clients would rather have
this field be blank by default.
To allow you to choose the default behavior of the “To: Transfer” field, the following property has been added to the
custom_wpksite.properties file located in \adp\1\applications\wpk\properties:
timecard.moveAmount.preloadToTransfer=
If the property is set to “true,” the field specifies the same labor account as the “To: Transfer” field.
If the property is set to “false,” the field is blank.
15
Enterprise eTIME
New global setting for processing of adjacent shifts (6.3.12)
(CENG-6376) A global setting has been added to allow adjacent shifts to be placed in the employee’s timecard. For
example, if an employee has a 7:00 a.m. to 1:00 p.m. shift and a 1:00 p.m to 5:00 p.m. shift, the shifts are placed in the
timecard with the end time of the first shift identical to the start time of the second shift. This feature applies to manually
entered shifts, shifts from pay code edits, and schedules generated by Pay-from Schedule.
The setting is called:
global.AdjacentShifts.ScheduleMergeSetting.AllowAdjacentShifts
and is located in Setup > System Configuration > System Settings > Global Values tab.
•
If the setting is set to “true,” the shifts are imported as adjacent shifts.
•
If the setting is set to “false,” the system uses the setting for global.AdjacentShifts.ScheduleMergeSetting on
the Global Values tab.
Language Support and Manager Delegation — URL Approach (6.3.10)
Language support
The Language Support feature ensures that a user’s primary language functions the same way in both Enterprise
eTIME and Vantage.
When a user logs on, the workspaces that he selects appear in the language specified in his Locale Policy. The Locale
Policy also determines cultural preferences, such as date formats. The Locale Policy is stored in the user’s People
record.
When a user passes in a Locale Policy change as a parameter on the URL the new Locale Policy is saved in the
currently logged on user’s People record which can be viewed through the People Editor. Since it is saved in the user’s
People record, the next time the user logs on their new session will reflect that current Locale Policy change.
For example, if a user changes his language from English to French, the Locale Policy for French is stored in his
People record and his workspaces appear in French the next time that he logs on.
Manager delegation
The Manager delegation feature sends the encrypted AOID/COID of the delegator in the URL rather than the HTTP
header. In addition, it sends the URL encoded Locale Policy of the logged-on user in the URL.
When the feature is enabled and a delegate has accepted a delegation, then when the delegate selects to act in the
delegator’s role, the system checks that the delegator’s AOID/COID is valid.
16
•
If the AOID/COID passed in the URL is for a valid delegation and the workspace requested is one that is
accessible in the delegator’s role (Role Profile) then that workspace remains accessible until the user
(Delegate) logs off or changes workspaces or delegation.
•
If the delegator’s AOID/COID is invalid, the logged on user (delegate) gets an error message in his active
language. A blank page displays when he closes the error message: Vantage Time cannot authenticate your
delegation information. Contact your ADP functional expert for assistance.
•
If a user already has access to a requested workspace using his own (delegate) role, the workspace appears.
•
When a delegate is acting on behalf of a delegator who’s status in inactive, he is able to do all assigned
delegations.
Enterprise eTIME
•
If there are multiple delegations between the same two employees for the day, then the first one found is
selected. We recommend not having delegations with more than one role profile between two people for
overlapping days.
Note: This section provides and overview of the URL approach for language support and manager
delegation. For details about this feature, see EeT_Language_Support.pdf that is delivered with this
service pack.
Function access control for kiosk users (6.3.9)
(WFM-56233) Enterprise eTIME provides enhanced control of system access for users who perform kiosk form
transactions.
A function access profile called “Kiosk_Mode_User” has been added to Setup > Access Profiles > Function Access
Profiles. By default, this profile allows limited access to the system. You can modify the profile to configure the access
level required of your kiosk users.
The following system settings have been added to Setup > System Settings > Global Values tab:
•
global.kiosk.login.username
•
global.kiosk.login.password
These global settings default to the values for a system-defined “KioskUser” which references the Kiosk_Mode_User
function access profile.
The solution included the creation of a new script called WTK160108.sql.
Enhanced configuration of grant expirations (6.3.9)
(WFM-52903) Some clients want accrual grants that are triggered by historical edits or moves to expire based on the
edit’s historical date instead of its effective date. To do this, use the following new global setting:
global.WtkTotalizer.ExpirationsBasedOnHistoricalDate
By default, this setting is set to “No” on and the grant expiration period (defined in employees’ accrual grant rules) is
measured from the historical edit’s effective date. To base the expiration on the historical date, change the setting to
“Yes.”
Whether this setting is turned on or off, the date of the accrual grant itself is equal to the historical edit’s effective date.
Note: With the setting turned on, if the grant expiration date is due to occur before the historical edit’s
effective date, the system moves the expiration date to the effective date.
Display of threshold settings for biometric templates in People Editor (6.3.9)
Identification templates
On the Biometrics tab in People Editor, the “Threshold” setting for every identification template appears. With previous
versions of Enterprise eTIME, an identification template’s threshold setting appeared only if the setting was “Normal,”
“Low,” or “None.” Beginning with version 6.3.9, threshold settings of “High” appear with the corresponding identification
templates.
17
Enterprise eTIME
Note: You cannot change the threshold setting for identification templates in People Editor.
Verification templates
“High” threshold is not supported for verification templates. If you select the “High” threshold setting in People Editor,
the system saves the threshold setting for that template as “Normal.”
Signed applets and setting for custom theming (6.3.8)
JRE 1.7 update 21 enforces new security measures that caused Enterprise eTIME clients to see warning messages
about our product applets. These messages appear for applets that are unsigned.
The following new features have been added to Enterprise eTIME to accommodate these security measures:
•
Enterprise eTIME applets are signed and a message appears when you log on to Enterprise eTIME that asks
whether you want to run the application from the publisher. You can choose to press Run or Cancel.
•
For custom theming, the themes.jar file is no longer created each time an Enterprise eTIME instance is
modified. The file is created once, digitally signed with VeriSign certificates, and delivered with the installation
kit.
You can use a new setting that determines whether Enterprise eTIME uses images in the <instance>static URL
rather than the themes.jar. The setting is located in Setup > System Configuration > System Settings > Display,
and is called:
site.portal.theme.from.server
When set to true, the application uses images in <application folder><instance
name>\applications\wpk\themes
If you change the setting, you must restart Enterprise eTIME for the setting to take effect.
If network latency is a problem, you need to modify the themes.jar file and apply your own JAR signing
certificate using the jarsign utility from the JDK.
18
Enterprise eTIME
Pay Code Definition enhancements (6.3.7)
Association of day and hours pay codes for contract employees
Some clients who manage contract employees’ accrual balances in half or full-day increments need the ability to
distribute the hours in those durations for overtime or premium pay purposes. The Pay Code Definition screen has
been enhanced to allow clients to associate an hours pay code with a day-based pay code.
When a user performs a day-based pay code edit in a timecard, that pay code and the associated hours pay code
appears. The amount in the duration pay code defaults to the full contract amount and debits the corresponding accrual
amount. The amount in the hours pay code is the equivalent of the full contract hours and determines what the
employee is paid. The pay code amounts are editable in the timecard.
In the “Unit” portion of the Pay Code Definition screen, a prompt called “Associate with pay code” has been added.
Open the Pay Code Definition screen for the day-based pay code and use the prompt to select the hours pay code to
associate with it.
19
Enterprise eTIME
Intermediate and replacement pay codes for duration processing
(WFM-51524) Some clients use many types of time off, each of which is represented by a different duration pay code
for accrual tracking. The client had to create individual pay code distributions to properly distribute the duration hours to
appropriate pay codes for pay processing. To avoid this configuration work, the Pay Code Definition screen has been
enhanced with a section called Totals Pay Code Replacement.
Using this section, you specify one or more intermediate and replacement pay code pairs:
•
The intermediate pay code should be a pay code that is processed and paid in exactly the same way as the
duration pay code you are defining on the New Pay Code Definition screen.
•
The replacement pay code is the pay code into which you want the duration hours to be placed.
Assign the duration pay code to a pay code distribution that references the intermediate pay code. Do this by using the
“Work Rule” setting to specify a work rule to which the pay code distribution is linked. The replacement pay code
overrides the pay code specified in the pay code distribution.
Example
20
•
You have a “Personal Time” duration pay code assigned to a work rule called “Personal Work Rule.” The work
rule is associated with a pay code distribution that processes personal time to the “Personal Hours” pay code.
•
Vacation time is processed in the same manner as personal time except that the totals should go to a
dedicated vacation pay code.
•
You create a “Vacation Time” duration pay code and a “Vacation Hours” pay code to hold vacation totals.
•
Vacation time is processed in the same manner as personal time. Instead of creating a work rule and pay code
distribution for vacation time, you assign the “Personal Work Rule” to the “Vacation Time” pay code.
•
Specify “Personal Hours” as the intermediate pay code; specify “Vacation Hours” as the replacement pay code.
Enterprise eTIME
The following illustration summarizes the configuration:
Work rule and associated pay
code distribution
Pay code definition
“Vacation Time”
(duration)
Assigned to work rule
“ Personal Work Rule”
“ Personal Time”
(pay code distribution)
Specify
”Personal
Hours” as
intermediate
pay code.
Specify
”Vacation
Hours” as
replacement
pay code.
During processing of vacation time,
system uses the “Vacation Hours”
pay code wherever the “Personal
Hours” pay code is indicated.
Vacation time will be processed in the same manner as personal time, but the totals will be placed in the “Vacation
Hours” pay code.
By creating pay code distributions that contain appropriate intermediate pay codes for other time off duration pay
codes, you can “re-use” the distribution instead of creating separate ones.
Important: If the pay code you specify for the “Intermediate pay code” prompt is not in the pay code
distribution, the default distribution is used to process the durations.
This feature required the creation of a database script called WTK160086.sql.
Important: If you uninstall Enterprise eTIME 6.3.7
Important: If you use the Pay Code Definition enhancements and later downgrade from Enterprise eTIME
6.3.7 or higher, pay code totals include the effects of the pay code configurations used with the
enhancements. After the downgrade, the features are not enabled. You can keep the pay code
configurations if you anticipate upgrading to 6.3.7 or higher later.
If you want to remove the associated pay code configurations after downgrading, you need to install a
patch that includes a script to remove the configurations. Contact ADP Functional Expert to obtain the
patch and instructions to install and use it.
21
Enterprise eTIME
Reporting of pay code edits with no hours (6.3.7)
(WFM-45657) You can choose whether the Employee Transactions and Totals report should show pay code edit totals
that are 0.00. A new setting called “Display Empty Totals” has been added as an option to select when generating the
report. If this option is set to “No,” pay code edits that total to 0.00 are not included in the report. If the option is set to
“Yes,” 0.00 totals are included in the report.
Enhancements to the Brazil Data Collection feature (6.3.2)
New system settings have been added to the Brazilian Compliance System Settings tab. These settings allow you to
select individual software services called “workers” that are part of the Brazilian Compliance (BRC) Service. The
settings are only relevant when the EnableBRCService setting is set to “true.”
•
:enableretrievepunchesworker — Runs the “Import From Device Interface” for each of the active
Brazilian devices.
•
enableprocesspunchesworker — Moves punches from the Punch staging table to the PunchEvent table.
•
enableupdatedevicesworker — Runs the “Export To Device Interface” for each of the active Brazilian
devices.
Note: Set enableupdatedevicesworker to “false” unless you use a custom interface capable of
sending information to Brazil-compliant data collection devices in a multi-threaded fashion.
Brazil Data Collection feature (6.3.1)
(WFM-38757) The Brazilian Compliance module supports integration between Enterprise eTIME and data collection
devices used in Brazil.
Setup items specific to the Brazil Data Collection module include:
•
“Brazil Device Setup” access control point
•
“Brazil Timecard Mirror Report” selection in the Report Data Access Profiles
•
”Brazilian Compliance” System Settings tab
•
”Brazil Device Group” QuickNav Column in Detail QuickNav Column Set setup
The following implementation steps apply to Brazilian (and multi-national) clients who hold the appropriate license:
•
Setting up and deploying interfaces for data collection
•
Configuring Brazil Companies, Device Types, Devices, and Device Groups
•
Configuring People with PIS numbers and Brazil Device Group assignments
•
Enabling the Brazil Controller for automated integration with Brazilian devices
4. Please contact your TLM Representative for more information.
22
Data Only reports (6.3.1)
With Enterprise eTIME 6.3.1, you can generate many Enterprise eTIME reports so that they contain raw data. You can
export the raw data to different report formats such as Microsoft Excel. This feature was implemented in Enterprise
eTIME 6.2.x and was available only to clients who used SSRS report generation (Advanced reporting). The use of
SSRS for reporting was eliminated beginning with Enterprise eTIME 6.3.0 so the Data Only reports feature was not
available in that version of Enterprise eTIME.
Beginning with 6.3.1, the Data Only reports feature is implemented with Basic reporting. All clients can take advantage
of generating raw report data for exporting to other formats. To configure Data Only reports, navigate to Setup >
Common Setup > Report Setup > Create Data Only Reports. This feature applies to many, but not all, If you used
Data Only reports with Enterprise eTIME 6.2.x, note that the user interface for this feature is different in 6.3.1 and
higher.
Refer to the online Help for instructions.
System setting for shifts in defined night periods (6.3.13)
Sometimes, employees’ schedules which seemed to violate the maximum number of nights per week that they were
allowed to work (set in their schedule rule), did not result in a violation tab in Schedule Planner.
This issue occurred in the following scenario:
•
Night periods were defined to cross the day divide. For example, night periods were defined as starting at 6
p.m. and ending at 8 a.m. on the following day.
•
An employee’s first of a series of worked night shifts started on the last day of the current week and crossed
the week divide.
By default, shifts worked during a night period count toward the day on which the night period starts. Therefore, the first
night shift did not apply to the current week and was not used to determine a rule violation for that week.
Some clients want to be able to control whether night shifts that cross from one week to another are used to determine
rule violations. To allow this control, the following system setting has been added to Setup > System Configuration >
System Settings > Scheduling tab:
site.scheduling.ruleevaluation.countNightShiftsOnDayStarted
Valid settings are:
true
Apply night shifts to the days on which the shifts start.
false
Apply night shifts to the days on which the relevant night periods start.
23
Time Period selector in the Contact Tracking dialog (6.3.12 SP)
The Contact Tracking dialog box in Schedule Planner now contains a “Time Period” drop-down list. This eliminates the
need to exit the Contact Tracking dialog box, select another time period or date in Schedule Planner, and open the
dialog box again.
24
Location-specific holiday assignments (6.3.8)
(WFM-52180) You need the ability to indicate to Workload Planner to which locations holidays that are configured in
Enterprise eTIME apply. For example, locations in different countries or states do not celebrate all of the same holidays
or do not celebrate them on the same day. Because Workload Planner cannot currently recognize these holiday
scenarios, workloads that are generated for periods that contain a holiday for one or more location can be inaccurate
for other locations.
The ability to associate holidays with locations has been added to the Location Profiles Setting dialog box in Setup >
Scheduler Setup > Location Settings > Location Profiles. Holidays are listed in the “Selected Holidays” or “Available
Holidays” boxes. System administrators move the holidays to the appropriate box so that the correct holidays are
associated with the locations that are assigned to the location profile.
The following illustration shows an example list of holidays before the appropriate holidays are moved to the “Selected
Holidays” list:
If clients want to associate non-established holidays such as Black Friday in the United States, they define the holiday
in Setup > Pay Policies > Holidays. The holiday will appear in the Location Profiles Setting dialog box and be available
to select.
Note the following information:
•
When you upgrade to Enterprise eTIME 6.3.8 or higher, all existing location profiles are populated with the full
list of holidays in the “Selected Holidays” box.
•
If no location profiles exist at the root node of the organizational map, the system creates create a location
profile called “Default Workload Planner Holiday” and assigns it to the root level of the organizational map. The
profile contains all of the configured holidays in the “Selected Holidays” box.
25
Applying pay codes to days with multiple shifts (6.3.8)
(WFM-51705) If an employee is assigned multiple shifts during a day, Pay Code Amount in the Schedule Toolbar and
Action Palette allows you to choose to replace a single or all shifts that day with a pay code.
Example use case
An employee is assigned to work two shifts during a day but needs to be absent. You can perform a pay code edit to
equal the entire duration of the day’s shifts using either of the following strategies:
•
When you select the pay code edit, you un-assign all shifts from the employee that day and create open shifts
to replace all of those shifts.
•
Leave all of the shifts assigned to the employee except the shift that you select. Also create one open shift to
replace that shift.
How to configure the pay code amount
(Optional) To configure the behavior of the Schedule Day option:
1. Select Setup > System Configuration > System Settings > Global Values tab.
2. Edit:
global.WTKScheduler.OverrideAllShiftsForFullScheduledDayEdit
True (default) – Select to override all shifts during a day if Schedule Day is selected.
–
–
Schedule Day – Add all shifts that day to calculate the amount for the pay code edit, remove all shifts and
replace each with open shifts.
Selected Shifts – Calculate the amount for the pay code edit amount only for the selected shift, remove
that shift and replace it by one open shift. The behavior does not change if the system setting is True or
False.
False – Select to not override all shifts during a day if Schedule Day is selected.
–
Schedule Day – Add all shifts that day to calculate the amount for the pay code edit, but remove only the
selected shift and replace it by one open shift.
– Selected Shifts – The behavior is the same if the system setting is True.
3. Click Save.
How to apply pay codes to days with multiple shifts
1. Move the Schedule Planner to the primary position.
2. Select the By Employee or By Job tab.
3. Either:
– Select View > Schedule Toolbar.
– Select Actions > Display Action Palette.
4. Click the down arrow that is beside the Pay Code button.
26
5. Select either:
–
Schedule Day (default) – Use all shifts that day to calculate the value of the pay code. Replacement of the
shifts by open shifts depends on the system setting.
– Selected Shifts – Replace only a selected shift with the pay code.
6. Click the Pay Code button.
7. Select the pay code.
8. In the schedule, select the shift.
Property setting for detecting schedule rule violations (6.3.7)
The Scheduler cannot always detect schedule rule violations in the following scenario:
•
A schedule rule set was configured with the setting "Use Actual Hours to Evaluate Schedule Rules" selected.
•
The schedule rule set was assigned to an employee who performed a request to cover a shift.
By default, the Scheduler only checks the day on which the request was made for schedule violations.
Some clients want the Scheduler to check the entire week of the request for violations in this scenario. To activate this
behavior, add a setting to a custom properties file using the following procedure:
1. Create a file called custom_wpk_properties in the \adp\1\applications\wpk\properties if a file with that name
does not already exist.
2. Add the following setting to the file:
site.WTKScheduler.ActualHours.ToEvaluate.WeeklyScheduleRules=true
3. Stop and re-start Enterprise eTIME.
27
Control over how Report Results form information is applied to activities
(6.3.14)
CENG-10663) By default, when users submit a Report Results form, the results are applied to the specified activity if
there is an earlier span for that activity. Otherwise, a span with a length of 0 hours (start and end time are the same) is
created for the results.
Some clients never want Report Results information to be associated with an existing activity span. The following
setting has been added to Setup > Activity Setup > Activity Settings:
Apply Report Results form data to eligible earlier Activity spans 1 = yes 0 = no
The default value is “1” which causes results to be applied to an earlier activity span, if one exists.
If set to “0,” results submitted using the Report Results form are never applied to an existing activity span. The results
are always associated with a zero-length activity event that is created when a user submits the Report Results form.
Control of activities to use for idle time (6.3.13)
(CENG-3671) By default, cell idle activities are applied to employees who incurred idle time before joining a cell or after
leaving a cell during a shift. The idle time activity specified in the cell’s activity profile is applied.
Example
•
Susan clocked in at 7:00 a.m. but did not join or start a cell. Her timecard correctly applied the idle activity
specified in her activity profile starting at 7:00 a.m.
•
Susan joined a cell and started the cell at 8:00 a.m.
The idle activity from 7:00 a.m. to 8:00 a.m. changed to the idle activity specified in the cell’s activity profile. The
idle activity should not change in this scenario.
If you want to apply the employee’s default idle activity or the activity specified in the employee’s activity profile to cell
idle time:
1. Add the following property to custom_WFA.properties file in adp\1\applications\wfa\properties:
USE_CELL_MEMBERSHIP_TO_DETERMINE_IDLE_ACTIVITY=false
2. After you add the property or edit its value, save custom_WFA.properties.
3. Re-start Enterprise eTIME to cause the setting to take effect.
Ability to submit activity forms for approved dates in the timecard (6.3.12)
(CENG-4934) Some clients want their employees to be able to submit activity forms for dates that were approved in the
timecard. To provide this capability, you 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=false
If you edit the file, save it and re-start Enterprise eTIME to cause the setting to take effect.
28
Ability to select eligible shifts to associate with durations (6.3.11 SP)
(CENG-338/WFM-59178) If you enter an activity duration and there are multiple eligible shifts, you can select which
shift to associate to the duration. This capability overrides the default shift that the Activities application uses when it
processes the duration.
When you double-click the “Allocated Hours” value for a duration in the Activities tab of the timecard, the Activities
Details dialog box appears. A new “Shift” tab shows eligible shifts for that duration; by default, the duration span’s
current shift is selected.
Note: The default shift is based on the configured method for associating shifts with durations. There are
two methods:
•
Select the shift that has the most hours on the date of the duration entry.
•
Select the shift that has a start or stop time that is closest to the duration entry time.
The adjusted start and stop times for the duration are based on the start time of the selected shift.
To change the shift to associate with the duration:
1. In the Activities Details dialog box, select the shift to associate with the duration.
2. Click OK.
Shifts must fulfill the following criteria to be eligible for association with a duration:
•
The shift must have a start time. An end time is not necessary for eligibility.
•
The shift must start or end on the selected date for the duration.
•
The shift has an apply date that includes the selected date of the duration.
If the selected shift does not have time left to fill, the duration is processed as an orphan duration. The start time of the
duration is the same as the selected shift.
29
The Event Audits tab tracks shift selection changes for the duration by showing:
•
Date and start time of the shift that was previously selected (“Before”)
•
Date and start time of the current shift selection (“After”)
Note: There is no API support for the ability to select shifts to associate with durations; it is available only from the user
interface.
Property setting to disable concurrency of durations (6.3.11)
(CENG-338/WFM-59178) Some clients do not want durations to be treated as concurrent durations. To turn off
concurrency, clients can add a property setting to custom_WFA.properties. If concurrency is turned off:
•
The system does not refer to configuration settings related to concurrency when allocating hours to durations.
•
No “Concurrent” column appears in the Activities tab in timecards.
To turn off concurrency:
1. Navigate to ..\adp\wfc\applications\wfa\properties.
2. Find the file called custom_WFA.properties. If a file of that name does not exist, create one with a text
editor.
3. Edit or add the following property setting:
com.kronos.wfa.DISABLE_DURATION_CONCURRENCY=true
4. Save the file and stop and then re-start Enterprise eTIME.
Note: If concurrency is turned off, durations are not considered concurrent even if the activity duration form
contains a step for concurrency.
30
Processing of non-chronological Start Only forms (6.3.10)
(WFM-55709) You can configure Activities to allow Start Only forms for an employee to be submitted in nonchronological order. By default, the system does not allow forms to be submitted in non-chronological order for an
employee who is currently punched in.
Example:
•
Your business imports Start Activity forms using an interface to Enterprise eTIME.
•
Start Only employees submit Start Activity forms using ADP data collection devices or in their timecards.
•
The system configuration allows only one activity to be open for an employee at any time.
•
Today, an employee submits a Start Only activity form. The employee is still working on the activity.
•
The business interface runs and tries to import a Start Activity form for the employee. The form is effective
today. It also has a start time that is earlier than the time of the form that the employee submitted.
Since the employee is still punched in, the import of that activity form fails.
Enabling the feature
1. Add or edit the following setting in the custom_WFA.properties file:
com.kronos.wfa.ACCEPT_NONSEQUENTIAL_STARTONLY_STARTACTY_FORMS=true
2. You can control how many hours into the future that the system looks for a Start Activity in-punch to remove in
this scenario. To do this, add or edit the following setting in the custom_WFA.properties file:
com.kronos.wfa.MODIFY_SHIFT_START_LIMIT_FOR_NONSEQUENTIAL_STARTONLY_
STARTACTY_FORMS=<number of hours>
The default value is 4 hours.
The following example explains how this setting affects in-punches for existing Start Activity forms when a form
with an earlier start time is submitted:
–
–
–
A system administrator specifies the following setting:
com.kronos.wfa.MODIFY_SHIFT_START_LIMIT_FOR_NONSEQUENTIAL_STARTONLY_
STARTACTY_FORMS=4
An employee submits a Start Activity form with a time of 10:00 a.m. The system “clocks” the employee in at
10:00 a.m and the punch is inserted in the timecard.
Another Start Activity form for the employee is imported through a business interface with a time of 8:00
a.m. for the same day.
The system makes the following adjustments:
–
–
–
Removes the 10:00 a.m. punch
Inserts the 8:00 a.m. punch
Removes quantities or other results associated with the original Start Activity punch.
31
Enhanced matching of form durations to shifts (6.3.10)
WFM-56892) Activities was enhanced to improve the way that durations entered by users are matched to shifts if there
is more than one eligible shift. A new setting in the WFA.properties file controls whether Activities uses:
•
Standard logic that determines which scheduled shift has the most hours on the day of the entry. If two eligible
shifts contain the same number of hours on that day, the duration is matched to the earlier shift.
•
The effective date and time of the form used to enter the duration.
The new setting is called:
com.kronos.wfa.ASSIGN_DURATION_TO_SHIFT_USING_EFFECTIVEDTM
The default setting is “false” and causes Activities to use the standard logic to select the best shift.
If the setting is set to “true,” Activities uses the duration’s date and start time to determine with which shift to associate
the duration. The duration is associated with an eligible shift that has a start or end time closest to the time of the
duration.
Employee filter setting for Cell Monitor (6.3.7)
(WFM-49969) A new setting has been added to WFA.properties to specify which employees managers can select
when defining the membership of a cell. The setting is called:
com.kronos.wfa.useEmployeeGroupToFilterAvailableListInCellMemberEditor
Valid settings are:
false (default)
All Activities employees appear in the Available list.
true
Employees whose primary labor accounts are valid for the employee group set of the manager appear
in the Available list.
Note the following additional scenarios:
32
•
If the manager is not assigned to an employee group, the labor level transfer set that is specified for the
manager in People Editor > Job Assignment > Employee Role determines which employees can be selected.
•
If the user working in the Cell Monitor is not a manager, their labor level transfer set is used to determine which
employees are available to select.
Cell event filter for Cell Monitor (6.3.7)
(WFM-49967) The labor level set drop-down list in Event Monitor included a blank entry which, if selected, allowed
managers to view and edit any cell events. Some clients want access to cell events to be restricted, based on each
manager’s assigned labor account set group.
You can add a property setting to a custom properties file to override the default behavior of allowing managers to have
unrestricted access to cell events:
1. Create a text file called custom_WFA.properties in ..\<instance>\applications\wfa\properties
Note: If a file with that name already exists, proceed to the next step.
2. Add the following entry to custom_WFA.properties:
com.kronos.wfa.includeBlankRowInEventMonitorLaborLevelSetList=false
With this setting, the labor level set drop-down list in Event Monitor > Cell tab does not include a blank entry. It does
include the labor transfer set of the manager. If the manager also has a labor account set group, that group is also in
the list.
Duration forms that do not create a Clock In punch (6.3.7)
(WFM-51056) If scheduled employees submit a duration form, the system normally creates a clock-in punch at the time
of the employee’s scheduled shift start. If you do not want the system to create a clock-in punch in this scenario:
1. Access Form Builder (Setup > Activity Setup > Form Builder)
2. Create a new form or duplicate a form that you have already created.
3. Add a step and select “_Perform Clock IN” for the Field Definition setting.
4. For the Default Value field, type N. (“N” indicates “No” so that the system will not create a clock-in punch.)
5. For the Entry field, select “Hidden” or “Read Only.”
This form configuration explicitly tells the system not to create a clock-in punch when the form is submitted.
Note: If you inadvertently include another step in this form with a “_Clock IN Time” field definition, the
system ignores data that is entered in that field.
Ability to apply labor standard changes to cell members (6.3.4)
Labor standard text fields have been added to the Cell Event Editor so that users can edit the standards. The
application integrates the changes into the calculations for individual person or resource spans. The new text fields are:
Labor Standard hours
Labor Standard rate
Labor Standard quantity
Labor Standard cost
Note: These settings override the labor standard settings that are part of the activity configuration only for
the event you are editing. The activity configuration settings are always in effect unless you override them
in the Cell Event Editor.
33
Attendance Incident Tab report (6.3.8)
(WFM-54228) Some ADP clients have a business requirement to print the Attendance Incidents tab in report form
because their managers/supervisors are not given access to the tab through the user interface. The existing
Attendance Detail report cannot be modified to produce the Incidents tab presentation because of Microsoft reporting
limitations.
To satisfy this need, a new report called “Attendance Incident Tab” has been added to the Attendance application. The
report is available to run from General > Reports, and available to configure in Setup > Common Setup > Report Setup.
Note: This new report is not supported in Advanced Reporting (SSRS). The existing Attendance Detail report will still
be available to support clients using Advanced Reporting.
New document tags for filtering incidents (6.3.6)
(WFM-46071) The following document tags have been added for attendance documents so that clients can choose to
show all incidents or just the incidents that contributed toward triggering an action.
[incidents-list-by-balance]
Lists positive or negative points incurred by incidents that contributed
toward triggering the action.
[incidents-list-filtered]
Lists only positive points or only negative points, depending on
whether the balance is an ascending or descending balance.
The new tags can be used only with Total Balance policies.
Note: The [incidents-list] has not been changed; it continues to list all incidents.
34
Enterprise Leave
Enterprise Leave
Date-related custom tags (6.3.11)
(CENG-3203) Two date-related tags were added for use in Leave document templates. The addition of these tags
allows flexibility in rendering the actual or revised due date for a document. The tags complement the current
[document-due-date] variable for documents where you need to refer to a previous due date or an extended due date.
The new tags are:
•
due-date — This tag evaluates to the document-extended-due-date if one is present; otherwise it evaluates to
the system generated document-due-date
•
document-extended-due-date — This tag evaluates to the extended due date for the document. If no
extended date is specified, the variable is ignored if an extended date is not specified (evaluates to an empty
string) in the Leave case data.
Example: Show the extended due date only
The Leave administrator has entered an extended due date on the document status screen, and wants to show only
the extended due date in the letter. This example demonstrates use of the “document-extended-due-date” tag.
[document-generated-date]
[first-name] [last-name]
[address-street]
[address-city], [address-state] [address-postal-code]
Re: Leave of Absence
Dear [first-name]:
We received your Fitness for Duty form but it was incomplete.
We have extended your due date for the form.
Please return it by [document-extended-due-date].
Sincerely,
35
Enterprise Leave
Example: Show the system-generated due date and the extended due date
The Leave administrator has entered an extended due date on the document status screen, and wants to show the
system-generated due date and the extended due date in the letter. This example demonstrates use of the “documentextended-due-date” tag.
[address-street]
Re: Request for information.
Hello,
You have not provided the necessary forms to continue processing your Leave request. The forms were due on
[document-due-date].
The due date has been extended to [document-extended-due-date].
Example: Show the extended due date or the system-generated due date
In the example below, the system-generated due date is appropriate for some employees. However, for other
employees, the Leave administrator will enter an extended due date as an alternative to the system-generated due
date. The letter shows the extended due date if one is present; otherwise, the system-generated due date is used. This
example demonstrates use of the “due-date” tag.
[address-street]
Dear [first-name]:
We have received your request for Leave of Absence. Included in this packet of information is a Medical
Certification Form. Please take it to your doctor to complete. The form is due back to the Leave Office on
[due-date].
Sincerely,
36
Navigator
Navigator
Use with screen readers (6.3.7)
(WFM-47433) Beginning with version 6.3.7, you can use Navigator with assistive technology screen readers by
appending the following parameter to the Navigator URL:
?accessReader=true
Performance improvements (6.3.7)
(WFM-42333) Applet pages load more quickly in Navigator.
(WFM-48759, WFM-49242) The system loads only the Request Manager alerts that relate to the products that the
logged in user is licensed to use. As a result, Request Manager alerts load and refresh more quickly.
(WFM-49230, WFM-49876, WFM-51974) Time Off Request widget transactions such as approving or rejecting a
request and loading the next schedule period complete more quickly.
Other issues have been resolved to improve performance when logging on to Navigator.
More usable screen space for maximized widgets (6.3.7)
(WFM-49255) When users maximize a widget in Navigator, the view uses all vertical space except for the browser
menu, address line, and toolbar. All other elements of the Navigator page (for example, Related Links, alerts,
workspace carousel) are hidden so that the widget appears in a larger area.
Passing of custom time frames to “classic” pages (6.3.7)
The “classic” pages in Enterprise eTIME have not supported the following time period selections that are available in
Navigator:
•
Yesterday, Today, Tomorrow
•
Yesterday plus 6 days
•
Last 30 days
Beginning with version 6.3.7, if a user selects one of these time frames in Navigator and then navigates to a single-link
or quick-link page, the time frame context is passed as a range of dates. For example, “Last 30 days” is passed with a
start date of 30 days ago and an end date of today.
This enhancement also works with custom time frames that clients create in Navigator.
37
Navigator
Approval validation options for request sub-types (6.3.7)
(WFM-48091, WFM-43196) New options have been added to the Request Subtype configuration dialog box to control
validation of the request subtype when submitted by managers or employees.
The current default approval requirement is that validation is performed when an employee submits a request and
when a manager approves a request. This strategy remains the default strategy. However, the following new options
allow you to change the approval requirement:
•
Perform Validation at Employee Submission — This option is automatically selected to preserve the default
approval requirement.
•
Perform Validation at Manager Submission — This option is not automatically selected to preserve the
default approval requirement.
Recommendation: When you configure time-off requests – whether global, days, or hours time-off requests – select
both options so that the system validates requests when they are submitted and when they are approved. If not
selected, validation is done only when requests are approved. As a result, requests can exceed available balances.
New global time off request templates (6.3.7)
(WFM-49253) The following Process Manager templates have been added for use with the global time off request
subtype:
Reminder
Used to cause reminders to approve time off requests to appear for the manager. The
system administrator specifies when the reminders appear.
Automatic Action
Used to indicate that actions defined in the Approval Settings Editor should occur
automatically. The system administrator specifies which actions occur at which part of the
workflow.
You do not have to deploy these templates from Process Manager; they are available as part of the Request Subtype
configuration. You can use these templates as they are or edit them for their needs. These templates contain the
following information:
•
– Display name: (“Automatic Action” or “Generic Notification Timer”)
•
– Template Category: GTOR
•
– Start Effective: 1/1/2000
•
– End Effective: Forever
•
Status: Active
The following prompts have been added to the request subtype configuration screen:
•
Reminder Template
•
Automatic Action Template
The default setting for both prompts is <none>. A drop-down list for each prompt allow you to select the template.
38
Navigator
Approval of time off requests that cause accrual overdrafts (6.3.7)
(WFM-48199) The following enhancements have been made to the process for approving time off requests:
•
If a manager tries to approve a time off request that will cause the associated accrual balance to become
negative, a message appears in the Approve Time-Off Request dialog box. For example:
“Warning(s) for this edit: Vacation balance on 2/20/2013> is 0:00 (overdrawn by 8:00)”
The manager can click Override to approve the request, or Cancel.
•
If a manager tries to approve a request for an employee who does not have enough overdraft allowance time,
the following error message appears in the Approve Time-Off Request dialog box:
“WTK-03285 This edit cannot be made. Vacation balance on 2/20/2013> is -20.00 (overdrawn by 28:00)”
•
If a manager selects multiple requests to approve, the system provides feedback to indicate which request
failed because of accrual warning or error messages. For example:
Time off requests that were not approved because of accrual warnings appear in orange rows; requests that
were not approved because of accrual errors appear in red rows.
The Approve button is not enabled because the manager cannot approve requests in red and must address
the requests in orange individually.
39
Navigator
Timestamp editing in employee-approved time periods (6.3.7)
(WFM-48811) The standard behavior of the system is to prevent employees from creating or editing timestamps within
a time period that has been approved by the employee. Some clients wanted the ability to edit and allow punches within
approved time periods.
To allow this flexibility, the following system setting (Setup > System Settings) has been added:
site.timekeeping.recordTimestampAfterApproval
Valid settings are:
false
(default setting)
Disallow creation and editing of timestamps in a time period that has been
approved by the employee
true
Allow creation and editing of timestamps in a time period that has been
approved by the employee.
The default setting is false and prevents employees from creating or editing timestamps in a time period that has
been approved. To enable the feature, change the setting to true.
Ability to set default HyperFind in the Schedule widget (6.3.6)
(WFM-46697) Users with privileges to edit widget configurations can change the default HyperFind for the Schedule
widget from “All Home Employees” to “None.” This is useful for performance reasons for managers who do not always
need to see all home employees, and want to use a narrower search.
Note: If the workspace that contains the widget is configured to pass context to widgets (“Workspace
Context Available” configuration setting), the default HyperFind query for a widget is replaced by the query
currently being used by the workspace.
Constraints on opening simultaneous instances of classic pages (6.3.6)
Navigator version 6.3.0 introduced the ability for users to have multiple Enterprise eTIME classic interface pages open
at the same time. However, if certain classic pages are opened more than once at the same time, the integrity of the
data on those pages could be compromised. Version 6.3.6 provides enhancements to identify which classic pages
should not be opened more than once at the same time.
Constraints
A user cannot open specific Enterprise eTIME web pages multiple times so that they are open at the same time during
a session. The following scenarios are no longer allowed:
•
40
Users cannot open more than one instance of any of the following classic pages at the same time:
Timecard
My Leave Cases
Schedule Planner
My Timecard
People Editor
Actions
Reports
Attendance Editor
My Actions
My Reports
My Attendance
Leave Cases
Schedule Editor
Navigator
•
Users cannot open any of the following page pairs from a QuickNav (using either the right-click method or the
Go To links) or a wizard, if either page is already open.
–
–
–
–
–
–
Timecard/My Timecard
Reports/My Reports
Leave Cases/My Leave Cases
Attendance Editor/My Attendance
Schedule Editor/Schedule Planner
Actions/My Actions
Warning messages
•
If a user tries to open a Web page more than once at the same time, a message appears that indicates that
another instance of the page is open and must be closed. An example message is:
“This action opens a page that is already open with <widget name>. You need to close the widget before
this action can be allowed.”
•
If multiple widgets in a workspace are configured to open the same classic page, the following message
appears when the user opens the workspace:
“This workspace contains multiple widgets configured with the same page. Some widgets will be moved to
the Related Items pane.”
This is a proactive measure to minimize the possibility of users opening simultaneous instances of classic
pages.
New options for the Call List widget (6.3.6)
(WFM-47279) Two options have been added to the Call List widget configuration screen to control the number of items
initially returned each time a manager opens the widget.
Default Show Location Selector to None
Changes the default setting of “All Home Locations” to “None.” This setting allows managers to give control to users to
specify which locations are returned. This provides an alternative to causing the application to take time to return a long
list of locations that may not be what the user wants. When users open the Call List widget, no locations, employees, or
open shifts appear. Then, the user can choose to select “All Home Locations” or a specific set of locations.
Note: If the workspace that contains the widget is configured to pass context to widgets (“Workspace
Context Available” configuration setting), the default HyperFind query for the Call List widget is replaced by
the query currently being used by the workspace.
Override Locations in Procedure Sets
Excludes locations that are associated with procedure sets. When this option is selected, the manager can specify the
locations to include, using the Show Location Selector field.
41
Navigator
Performance improvements (6.3.6)
(WFM-46595, WFM-47227, WFM-47229) When logging in to the Navigator, the application page appears much more
quickly than it has in the past.
(WFM-46594) Default widgets load more quickly when users log in to the Navigator. When users drag widgets in the
workspace into the primary position, they load more quickly and efficiently than in the past.
(WFM-47901) Schedule Planner loads completely and quickly for use.
(WFM-47852) When users close widgets that contain unsaved data, they are always prompted to choose to save or
discard the data, as expected.
(WFM-46709) Modifications have been made so that applet-based screens that users access from the Navigator open
much faster than they did in previous versions.
Enhancements to the Staff Management widget (6.3.2)
Adding and modifying shift segments
It is now possible to create, edit, or delete a shift segment in the Staff Management widget.
You can edit or delete Breaks. Select Breaks on the Action Menu to create a break. You cannot delete all segments
from a shift. At least one non-break segment must remain in the shift.
You cannot make changes to a locked shift or to a shift on a locked day.
Configuring the Actions Menu
To use this feature, the employee must have an Enterprise Manager - Department license for Enterprise Scheduler or
Enterprise eTIME. The manager must have access Allowed for the FAP Manager/Scheduling/Schedule
Adding or editing a shift segment
To add or modify a shift segment:
1. Select an assigned shift.
2. Left-click to open the Action Menu, and select Change Segment. The Change Segment dialog box opens with
all shift segment information, including breaks.
42
Navigator
3. To show segment details, click the right arrow next to the segment start and end times
..
Click to show segment details.
Click again to hide them.
4. To edit a segment, enter your changes, and click OK.
5. To delete one or more segments, click the red Delete button
must remain in the shift.
6. To Add a segment, click
and click OK. At least one non-break segment
Add Segments. The New Segment opens.
Click to delete the segment
Click to add a segment
7. In the new segment, optionally, select a different Start date.
8. Enter a Start time. You cannot overlap the new segment with any part of the original shift. It must start and end
before or after the original shift.
9. Enter Duration in the format hh:mm.
10. Optionally, select Details from the drop-down menu.
11. To add another segment, repeat from step 6.
12. Click OK.
43
Navigator
13. To see the added segment in a tool-tip, hover over the shift.
Job Transfer
New location selection options
Large organizations, such as hospitals, use a central staffing office to manage schedules and coverage for large
numbers of employees (200+). Although the staffing office needs access to a large number of employees, they do not
necessarily need to see all the employees at one time, and loading all employees at once slows down the performance
of the system.
To enhance performance, it is now possible for scheduling personnel to select only the specific locations (and
associated employee pools) that they need to work with.
Specific locations can now be selected in Preferences or in the Staff Management widget. A manager can select
Custom Locations that he or she created in the Schedule Planner from either of the Location drop-down lists.
Selecting None for Location in Preferences
In Preferences, you select what you want to see as the default context in the Staff Widget. If you select None in
Preferences, then the Staff Management widget opens with no data displayed in the context. You can then select the
data and locations that you need to deal with.
To select locations in the Staff Management widget:
1. From the Staff Management widget, select Preferences.
2. Select None in Location.
44
Navigator
3. Select Save. The Staff Management widget opens with no locations. Select Location... displays in the context.
4. Choose Select Locations to select only the locations that you need to work with from the organizational map.
Or select another option from the drop-down list.
Selecting specific locations in Preferences
If you select locations from the organizational map in Preferences, the locations that you selected load into the Staff
Management widget.
To select locations in the Staff Management widget
1. From the Staff Management widget Gear icon, select Preferences.
2. In Location, select Select Locations.
3. The Select Locations page opens.
45
Navigator
4. If necessary, click Clear Locations to move all selected locations back to the left area.
5. Select the locations that you want from the left area. Use the right arrow to move each selected location to the
right area.
6. Click Select to return to the Preferences page.
7. Select Save. The Staff Management widget opens with Selected Locations in the context and the details for
those locations loaded.
Using custom locations in the Staff Management Widget
You can create a custom location in Enterprise Scheduler and save it with a name. The custom locations that you
create then show up on the Location drop-down list in both the Staff Management widget and in Preferences. The
custom locations that are on the Location list appear only on your list. Other managers cannot see or use your custom
locations.
To create and save a custom location:
1. In the Schedule Planner in Show, select Select Locations. The organizational map appears.
2. To deselect the check marks, click Clear All.
3. Select the location or locations that you want.
4. Click Save As.
5. Enter a unique name for the locations. Click OK.
The Schedule Planner appears with your custom location selected. When you go to the Staff Management
widget, the custom locations that you created and saved are on the Location list in both Preferences and the
Staff Management widget.
New function access control point for Navigator Import feature (6.3.2)
(WFM-39591) Beginning with 6.3.2, you can restrict access to the Import feature of Navigator. Users must be given
access to this feature through their assigned function access profiles. A new function access control point has been
added at the following location in Setup for function access profiles:
Enterprise eTIME Manager – Common Setup -> Navigator Framework -> Import Feature
To enable the feature, set “Access scope” to “Allowed.”
46
Navigator
Multiple selection support in list pages (6.3.2)
(WFM-39320) List pages have been enhanced to support multiple selection of widget parts, widgets, workspaces, and
Navigators to delete. If the user selects multiple items in a list, the Copy and Edit buttons become inactive.
Single-instance control for Schedule Editor/Schedule Planner
The Navigator framework has been enhanced to allow only one instance of the schedule editor or Schedule Planner to
be open at the same time. This enhancement reduces the likelihood of data corruption that can happen if more than
one of these pages are edited at the same time.
Setting to enable Go To Navigation options for Single and Quick Link widgets
(6.3.2)
(WFM-39590) A configuration check box has been added to single and quick link widgets and valid page widget parts
to control whether the Go To Navigation options (for example, Schedule, People, Timecard, Reports) appear when that
widget shows in Navigator. The check box is called "Show Go To Navigation" and appears when you configure the
applicable widgets and widget parts using Manage Navigators.
After you upgrade to 6.3.2 or higher, the default setting for new single or quick links that you create is checked, or
“true.” These links automatically show in the Go To Navigation bar. For existing single or quick links, the default setting
is unchecked, or “false.” These links do not show in the Go To Navigation bar unless you change the setting in Default
Manage Navigators.
The following illustration shows the Go To Navigation bar:
Enabling the Go To Navigation allows users to replicate common Enterprise eTIME workflow patterns, easily moving
between frequently-used locations and editors. This feature will be particularly helpful for Enterprise Absence Manager
users.
47
Navigator
Default Support workspace and widgets (6.3.2)
(WFM-39583) Beginning with 6.3.2, a workspace called “Default Support” appears in the following Navigator pages:
•
Default Manager
•
Default Superuser
•
Default System Administrator
The label for the workspace is “Get Support.”
The Default Support workspace allows access to Enterprise eTIME online Help through a Default Help widget. The
label for the widget is “Help.” This widget is available in the Widget list; and can be included in other workspaces and
made accessible as a single link in primary views. The Default Help widget supports locale policies so that online Help
appears in the language specified by users’ locale policies.
Translation of widget parts, widgets, and workspaces (6.3.2)
(WFM-39853) In the past, Navigator supported the display of translated names and labels for all Enterprise eTIME
objects except widget parts, widgets, and workspaces. Beginning with 6.3.2, system administrators with the appropriate
privileges can perform the following operations for Navigator names and labels for widget parts, widgets and
workspaces.:
•
Translate user-configured text objects using Setup > System Configuration > Translation Support. The
Entity Type table that appears includes widgets, widget parts, and workspaces to translate.
•
Export existing object names and labels from Navigator to an Excel spreadsheet. To do this:
a. Select Setup > System Configuration > Translation Support.
b. Select the entity type to export (for example, “Widgets”).
c.
Click Export.
The spreadsheet can be used by localization services for translation purposes.
•
Import translated text from an Excel spreadsheet into Navigator. To do this:
a. Select Setup > System Configuration > Translation Support.
b. Click Import and browse to the Excel spreadsheet to import on the client machine.
c.
Click Import.
Note: There is a known issue with this feature (WFM-42628). The translated text for workspaces does not
appear after you import the translation; the English continues to appear. You need to edit one of the
workspaces in some way (for example, edit the description), save it, and refresh the browser. Then, when
you open any workspace that was translated, the labels will appear in the new language.
The implementation of this feature included the creation of a new database script called WTK160019.sql.
48
Navigator
Workflow Enhancements - Request Manager (6.3.2)
Multi-Period Indicator
(WFM-41124) The multi-period indicator enables users to quickly identify Global Time Off requests that contain multiple
duration types or non-contiguous days. A new icon appears in an untitled column in the Request Manager grid to
indicate these requests:
Users can hover over the icon to see a tool tip that shows the periods in the request. Multiple period details also appear
in the Details panel.
To add the Multi-Period indicator column to the Request Manager grid, users can select Multiple Period Indicator in the
Available Request Type Columns in the Request Manager widget part in Manage Navigators. The column has no title.
Multiple selections
Users can now select one or more statuses to expand the requests listed in the Request Manager grid. When users
select more than one status, the status selection changes to “Multiple.”
Request Manager Alert statuses expanded and externalized
The Request Manager Alert badge, by default, now counts requests that have the status of Draft, Submitted, Pending,
Offered, Cancel Submitted (statuses associated with My Request requests), and Active. In 6.3.0, only requests with
Submitted or Active status were counted.
49
Navigator
Reassign
The Reassign action button appears for process manger requests in the manager view of Request Manager.
A new Reassign dialog box enables managers to search and display one or more manager names.
Managers can select another manager who should receive the request and enter a note to explain the reassignment.
After reassigning a request, the system removes it from the list in the requestor’s Request Manager grid.
Resume API
The Resume API task in Process Designer allows users to resume a suspended global time off request. This API is
used exclusively for requests that have been configured to invoke a custom Process Designer template between two
states in the global time off request workflow. After the custom process completes, the Resume API action allows the
global time off request to continue its workflow.
A new tool tip was added to describe the Resume API task.
50
Navigator
Editing shift segments using the Schedule widget (6.3.2)
From the Schedule widget, managers can create, edit, or delete shift segments or add segment details.
Adding shift segments
1. Click an assigned shift.
2. Select Change Segments from the Shift menu.
3. Click Add Segments. New Segment opens by default.
4. (Optional) Select another Start Date.
5. Select another Start Time to change it from the start time of the first segment. You can edit the start or end time
of the shift but only within the time period in the Schedule widget.
6. Enter a Duration in the format hh:mm.
7. (Optional) Select Details from the drop-down menu.
A Detail icon indicates segments that have details defined.
To display the details, hover the cursor over the shift.
8. Click OK.
51
Navigator
Editing shift segments
2. Select Change Segments from the Shift menu.
3. Edit the segments one-by-one. The segments are in order from first to last. Click the triangle of a segment to
edit or close it.
Segment to edit
Closed segment
a. (Optional) Select another Start Date.
b. Select another Start Time to change it from the start time of the first segment. You can edit the start or end
time of the shift but only within the time period in the Schedule widget.
c.
Enter a Duration in the format hh:mm.
d. (Optional) Select Details from the drop-down menu.
4. Click OK.
Note: If a segment cannot be created, a warning message displays the probable reasons.
Deleting shift segments
2. Select Shift Segments from the Shift menu.
3. Click the red button on a segment to delete it. If the shift has only one segment that is not a break, you cannot
delete it.
Delete
4. Click Yes to confirm. If you delete the first segment, the second segment becomes the first segment, and the
start time and duration of the segment do not change.
5. Click OK.
52
Navigator
Effect of segment edits on breaks
Breaks are treated as segments. You can edit or delete them the same as for other types of segments. However, you
cannot use Change Segments to create a break.
Enhanced Show function in the Schedule widget (6.3.2)
You must use Show to select a location or a HyperFind query from the Schedule widget > Preferences.
Show behaves differently depending on the context.
In Enterprise Scheduler, based on saved locations or HyperFind queries, Show may display the following:
•
All Home Locations
•
Custom locations
•
Select locations
•
HyperFind queries
If you configure locations in tabs such as Metrics, Coverage or Rule Violations, or you select View > By Job in the
Preferences, but then select a HyperFind query, the Schedule widget loads the HyperFind query and ignores the other
location selections.
If only Enterprise eTIME is installed:
•
Show displays All Home and saved HyperFind queries. If locations are configured, it also displays Selected
Locations. If not, Selected Locations shows only Organizational Node.
•
Tabs such as Metrics, Coverage, or Rule Violations, or View > By Job are not available.
Comments and notes (6.3.2)
Comments for request status changes
You cannot delete comments that were entered for status changes to Employee Self-Scheduling (ESS) requests.
Notes in request details
Non-default comments and notes are not displayed.
Action dialog boxes, such as to Approve, Refuse, Pending, Retract, Cancel requests, display all comments and notes
entered by the employee.
53
Navigator
Multiple comments or notes
Managers can add or edit multiple comments or notes in time-off requests. Request details and history list all
comments and notes, and group all notes for the same comment together.
Note: Multiple comments and notes are available only for time-off requests.
1. Click and drag the Request Manager widget to the primary position.
a. Select the time period and location.
b. Select the Time-Off request type.
c.
Select the status.
d. Select a request.
2. Click Edit.
3. In Edit Time-Off Request:
a. Select a Comment.
b. Click Add. The current comment and note are saved.
c.
Select the same or another Comment.
d. Enter a new Note.
4. To add more comments or notes, repeat step 3.
5. Click Edit.
Enhanced function for adding comments to requests
The feature for adding comments to requests has been enhanced so that employees cannot enter a comment if there is
no default comment configured for the request subtype. There must be a default comment configured for the subtype
before employees can add comments.
54
Navigator
Other Navigator enhancements (6.3.2)
Staffing widget – improved performance for large groups
Previously, the Staffing widget loaded organizational groups and job transfer sets with more than 200 employees too
slowly.
Large organizations, such as hospitals, have a central staffing office that manages scheduling and coverage. To
maintain coverage, the staffing office moves employees between departments, floors, or locations. A floating pool of
employees may be available for dispatch were needed. Although the staffing office has access to a large number of
employees, they don’t need to see them all at once. Instead, they need to be able to select only the employee groups
that are needed at any time.
1. Click and drag the Staffing widget to the primary position.
2. In Location, select <none> to load the widget quickly.
3. Select only the locations that you need.
Alternatively:
1. Click and drag the Schedule widget to the primary position.
2. Select only the locations that you need. Do not select a HyperFind query.
3. Click and drag the Staffing widget to the primary position. The Staffing widget loads only the locations that you
selected in the Schedule widget.
Enhanced Alerts
(WFM-39242) The Alerts widget displays notifications that come from other widgets such as Exceptions and Schedule.
•
Categories of alerts include: Metrics, Exceptions, Time off Requests (TOR), and Schedule.
•
Severity has High (Severe), Medium (Warning), and Low (Informational) levels.
•
The alert icon displays the total number of alerts for a category or severity level. For example: TOR2 indicates
that the manager has 2 time-off requests.
•
Hover the cursor over on the category to display a list of alerts for further action. Click the alert to open the
corresponding widget and act upon the alert to clear it.
Changes for version 6.3.2:
•
Navigator can display a maximum of 7alert icons.
•
The Refresh button has moved to the left bottom of the Alert icon. Click it to refresh the alert counters and the
Last Updated Time in the pop-up list of alerts.
Enhancement to Timestamp widget
(WFM-40127) The Timestamp widget has been enhanced to present information in a more visually pleasing way. In the
maximized and minimized views, all text and buttons are centered. The minimized view has been restructured for ease
of use. The Record Timestamp button is now larger and includes an icon.
55
Navigator
Enhanced presentation of Related Items
(WFM-39241) Related Items lists widgets on the right side of the page. You can drag these widgets onto the current
workspace or open them in a temporary workspace.
•
Related Items is on the right side of the screen and replaces the Drawer.
•
Use the horizontal arrow buttons to open and collapse the list.
•
Use a workspace setting to collapse or open the list when you first load the workspace.
•
The workspace never covers the Related Items.
•
Related Items lists all widgets that are configured for the workspace. Widgets that are currently displayed in the
workspace or are displayed in a temporary workspace are shaded to indicate that you cannot use them.
•
To return a widget to Related Items, drag it back to Related Items from the current workspace, whether Related
Items is closed or open.
•
The rules of temporary workspaces apply to any widget that is open in a temporary workspace.
•
When Related Items is open, hover the cursor over actionable widgets to show the widget name and highlight
the borders of the widget.
•
When Related Items is open and you hover the cursor over shaded widgets, nothing happens because the
item is disabled.
•
Related Items is not displayed if a temporary workspace is centered.
•
The title Related Items cannot be changed.
•
If the workspace is not full, you can drag widgets from Related Items to the workspace.
•
If the workspace is full, you can swap widgets from Related Items with primary or secondary widgets in the
workspace.
Changes for version 6.3.2:
•
To open a widget in a temporary workspace, click the widget or click and drag it to the Active Bar even if the
Related Items pane is closed.
•
To open a widget in the current workspace, click and drag it to the current workspace even if the Related Items
pane is closed. The widget must meet the constraints of the workspace. For example, the workspace is not full.
•
An overflow mechanism prevents more than one widget from being displayed at once. You can use the scroll
bar to cycle through all widgets in the Related Items. The scroll bar replaces the up and down buttons.
•
When Related Items is closed, hover the cursor over actionable widgets to show the widget name. Also, you
can use the widget.
•
When Related Items is closed and you hover the cursor over shaded widgets, the widget name is displayed.
However, the widget is disabled, so you cannot drag or click it to open.
Enhanced performance of selector dialog boxes (organizational jobs, labor transfers)
Labor transfer and organizational job selector dialog boxes have been enhanced to load more quickly and efficiently
when there are very large amounts of data to show.
Enhanced Wizard parameters page
(WFM-39321) The label of the button on the parameter page of the Navigator wizard has been changed from “Submit”
to “Save.” This label more clearly indicates that the button is used to save changes to the database.
56
Reporting enhancements and product support changes (6.3.1)
Enterprise Worksheet has been upgraded with this release and includes the enhancements summarized below.
Translations into four additional languages have been added: Chinese-Taiwan, German, French-France, DutchNetherlands.There have been no changes to License requirements and deployment mechanisms. Enterprise
Worksheet continues to access data from QuickNavs in the same manner and still supports Data-Only reports.
Single Reporting interface: Impact on Enterprise Worksheet
•
In Enterprise eTIME 6.3, Advanced reports (that were delivered through Microsoft SSRS) are now available
within a single reporting interface that uses the RDLC 2010 reporting engine. Advanced Reporting based on
Microsoft SQL Server 2005 or 2008 Reporting Services (SSRS) is not required or supported for Standard
reporting. Enterprise Worksheet no longer requires Advanced Reporting (SSRS) to extract data from reports.
•
Users can designate any report as a favorite in Enterprise eTIME for easy access to reports that are used
regularly, using the Favorites buttons in the Select Report tab. The favorite report name appears below the
Favorites category on the left side of the page. Only the person who created the favorite can access the report
by this name. Two URLs for the report, labeled Report Link and Data Link, appear in the Favorite page. The
Data Link contains the URL to a report that can be accessed only by Excel, through Enterprise Worksheet.
Anyone who has the appropriate report access profile can access a report using the URL of the report.
Office 2007 and Office 2010 support
The Enterprise eTIME 6.3.1 release of Enterprise Worksheet is qualified with Office 2007 and Office 2010. Enterprise
eTIME clients using an earlier Excel version must upgrade to Excel 2007 or 2010.
57
Settings to control display of device status information (6.3.10)
You can choose either of the following ways to show information in the “Devices and Device Groups” page in Device
Manager:
•
Show multiple rows of information for a device that is assigned to multiple device groups. Each row is devoted
to one of the device group assignments.
•
Show one row of consolidated information for a device that is assigned to multiple device groups, and specify
how many of the group assignments are listed.
The following settings have been added to Setup > System Settings > Device Management:
•
site.wdm.show.single.row.per.device
The default setting is “false” and causes Device Manager to show multiple rows of information, one row for
each device group assignment.
If the setting is changed to “true”:
•
– One row appears for the device.
– In that row, the “Device Group” column shows a list of device groups to which the device is assigned.
site.wdm.device.max.groups
Applies only if site.wdm.show.single.row.per.device setting is set to “true.” The default setting is “3.” With the
default setting, up to three device groups appear in the “Device Group” column for the device. If the device is
assigned to a number of groups that exceeds this setting value, the rest of the group assignments are not
listed. Group assignments are listed in alphabetical order.
If this setting is set to “0,” all device group assignments appear in the “Device Group” column.
Note: If the server runs multiple instances of Enterprise eTIME, these display settings apply only to the instance on
which they are configured.
Support for ADP QuickPunch Plus biometric templates (6.3.10)
Device Manager 6.3.10 and higher 6.3.x versions support ADP QuickPunch Plus biometric templates. The templates
can be used with InTouch data collection devices beginning with the 2.0.0 firmware. In Enterprise eTIME 6.3.10 and
higher 6.3.x versions, the People Editor provides support for showing the biometric template types on the Biometrics
tab. A new column called “Template Type” shows Type 1 (ADP QuickPunch template) or Type 2 (ADP QuickPunch Plus
template).
For detailed information about ADP QuickPunch Plus, refer to the following documentation:
58
•
InTouch v2.0 Release Notes
•
ADP QuickPunch User Guide
•
ADP QuickPunch Plus Installation Guide
•
ADP QuickPunch Plus Quick Reference Guide
MLSI support for transactions at ADP InTouch (6.3.1)
Device Manager has the capability to send employees’ assigned locale policies and translated names for pay codes,
comment codes, and accrual codes to ADP InTouch devices version 1.0.3 or higher. This capability allows support for
multiple language/single instance environments for transactions at the devices.
The language that appears on the device when a user initiates a local transaction depends on the following factors:
•
Whether the user selects a language from the language bar on the device touchscreen.
•
Whether the user is assigned a locale policy.
•
Whether the user performs a local transaction or a QuickGlance transaction.
•
Which languages are available on the ADP InTouch device (for local transactions) or the Enterprise eTIME
server (for QuickGlance transactions).
For local transactions, the order of priority that the system uses to determine which language to use is:
•
Language selected at the device
•
User’s locale policy
•
Default language of the device
For QuickGlance local transactions, the order of priority is:
•
Language selected at the device
•
User’s locale policy
•
QuickGlance locale policy
•
Default language of the server
Global Time Off requests at the ADP InTouch device (6.3.1)
ADP InTouch version 1.0.3 or higher supports Global Time Off requests that allow employees to submit or cancel
multiple time off requests with one transaction. For example, if employees want to request two days off this week and
one day off the following week, they can do this with one transaction. Before this capability, employees had to perform
a transaction for each time off request.
Global Time Off requests are QuickGlance transactions that reference the Enterprise eTIME database. What
information and selections appear on the device screen depend on how the request sub-types are configured.
Examples:
•
If the request sub-type is configured with only “Hours” as the symbolic amount, the Hours selection appears on
the device screen and cannot be changed. A Duration text box appears and the employee must enter a
number of hours.
•
If the request sub-type allows any of the three entry choices — Full day, Half day, Hours — the options are
listed on the device screen and the employee must select one.
59
Enterprise Forecast Manager
Shift Swap QuickGlance Support at ADP InTouch (6.3.1)
The New Request QuickGlance transaction now supports the Shift Swap feature on the ADP InTouch device. Shift
Swap allows an employee to swap a scheduled shift with another employee that has a scheduled shift for a specific
date. This feature is supported on ADP InTouch 1.0.3 and higher.
Task-Level Labor Distribution (6.3.7)
The Task-Level Labor Distribution feature allows you to combine labor standards in Enterprise eTIME at the Task level.
This allows the available resource pool to be distributed also at the Task level using combined labor distribution
methods.
The combined distribution at the Task level continues to follow the existing distribution method. In addition, this
software distributes labor across the day divide when the labor period crosses the day divide.
There are two major changes to how combined distribution is configured.
•
The Combined Distribution tab has been removed from the Task and Task Group page as an independent
page. It contains the combined labor distribution parameters and the options for distributing labor that crosses
the day divide.
•
The Task and Task Group configuration pages have a new drop-down list of configured Combined Distribution
items.
Combined distribution items that existed with Task Groups before the 6.3.2 Service Pack was installed are
automatically moved to the Combined Distribution page and drop-down list when 6.3.2 is installed. These preservice pack items have a –CLD following their name; for example, OldTaskGroupname–CLD.
Enabling the feature
There is a new function access control point called Combined Distribution. It is located at Setup > Access Profiles >
Function Access Profiles under Forecast Configuration.
To enable the feature, change the Disallow settings in Edit and View to Allow.
Configuring Combined Distribution
Labor from a labor standard that cannot be spread evenly throughout the labor period goes into the resource pool.
Depending on the configuration, the system uses this labor to fill gaps and to meet minimum requirements in each 15minute labor period. Labor that remains after that process is distributed according to one of the following methods:
60
•
Spread Remainder Left — Start at the beginning of the time period (left) and spread forward toward the end of
the time period.
•
Spread Remainder Right — Start at the end of the time period (right) and spread back toward the beginning
of the time period.
•
Optimal Remainder Spread — At the task level, optimal remainder spread works most effectively when raw
task-level labor is expected to vary throughout the week; otherwise, using Optimal Spread could affect
performance.
To set up combined labor distribution at the task level:
1. Go to Setup > Forecaster Setup > Combined Distribution. The page displays the list of combined labor
distribution items.
2. Select a Generic Department. The combined distribution item is defined for jobs in this department.
3. To create or modify a combined distribution, click New or Edit. The Combined Distribution page opens.
4. .Enter a Name and an optional Description.
5. Select a Distribution Type for distributing the resource pool labor.
If you select the Optimal Remainder Spread distribution type, select a Spread Excess Labor option — Left
or Right — to distribute any labor that may remain in the resource pool after the optimal spread.
6. Select a Distribution Time Period (labor period). For more details about the Labor Period, check the online
Help for Labor Standards.
7. Select the Day on which the time period applies.
Note: Every day means every day except those that are specifically called out in another row under the
selected Distribution Time Period.
– For Absolute Hours, select the Start and End times.
– For Hours of Operation, select the Every day to define the labor period as hours of operation for each
day the store is open, or select the day on which the hours of operation apply. Click the Add Row icon to
add another day.
– For After Open Hours, select the start of the labor period as an amount of time relative to the store open.
A positive amount of time starts the labor period after the store opens; a negative amount of time starts the
labor period before the store opens.
– For After Close Hours, select the start of the labor period as an amount of time relative to the store close.
A positive amount of time starts the labor period after the store closes; a negative amount of time starts the
labor period before the store closes.
8. Select Distribute only when labor period is available to ensure that the system distributes the labor only
inside of the time period defined by the combined labor standards.
9. For Allocating labor outside of the defined distribution period, select a preferred way to distribute
(allocate) labor outside of the distribution time period, including when it crosses the day divide.
–
–
–
–
Same as selected distribution period — labor is maintained within the distribution time period.
Start before distribution period — Distribute the combined labor before the distribution period (including
across the day divide)
Amount: Select the number of offset hours (up to 8 hours).
Start after distribution period — Distribute the combined labor after the distribution period (including
across the day divide)
Amount: Select the number of offset hours (up to 8 hours).
10. Select Save and Return.
61
Linking or unlinking the combined labor distribution to a Task and/or Task Group
You can select a Combined Distribution item to link to either a Task or Task Group, or both.
Notes:
–
–
–
If you link an item to a job at both the Task and Task Group level, it is possible that the resource pool may
have been used up at the Task level and there is no available labor to distribute at the Task Group level.
If a labor standard is configured to be distributed using spread left or spread right, then it cannot be used
for combined labor distribution.
You must select a time dependent task to use the Combined Labor Distribution method.
To assign a combined distribution item to a Task or Task Group:
1. Complete the Tasks page by entering a Name and optional Description. Click Help for specific field definitions.
2. In the new field, Combined Distribution, select an item from the drop-down list. This combined labor
distribution configuration is applied to the set of labor standards for this task.
Note: Two or more labor standards in the Selected area must be selected for Combined Distribution.
3. You can select the same Combined Distribution item in the Task Groups page to link the combined distribution
item to a Task Group. If there is labor remaining in the labor pool, it is distributed according to the Combined
Distribution item’s parameters.
Sample XML APIs
There are three new XML APIs:
•
TaskGroup_Update
•
Tasks
•
Combined Labor Distribution
Note: The Task Group APIs that were used before this custom software are still supported (backward
compatible).
TaskGroup_Update
A new tag, <CombinedLaborDistributionName>, has been added. There are no changes to actions.
Note that if the old <CombinedDistributionSetting> block is used, a new combined labor distribution is created
with a system-generated name, taskGroupName-CLD. The block is not displayed in retrieve; the system
automatically replaces it with the new <CombinedLaborDistributionName>.
The following is a sample of the XML API code:
<Request ACTION="update">
<TaskGroup>
<Description>Manager22</Description>
<GenericDepartmentName>Manager</GenericDepartmentName>
<IsActive>true</IsActive>
<TaskGroupName>Manager22</TaskGroupName>
<LaborHourAllocationRule>Actual day</LaborHourAllocationRule>
62
<SkipBreaksInLabors>false</SkipBreaksInLabors>
<MaximumBreakDuration>0</MaximumBreakDuration>
<BreakPlacementWindow>0</BreakPlacementWindow>
<CombinedLaborDistributionName>mm1</CombinedLaborDistributionName> <Tasks>
<Task GenericDepartmentName="Manager" IsActive="true" IsTimeDependent="true"
TaskDescription="Manager" TaskName="Manager" AllocateExtraResourceBeforeTrafficFirst="true" />
</Tasks>
</TaskGroup>
Tasks
A new tag, <CombinedLaborDistributionName>, has been added. There are no changes to actions.
The following samples are of the XML API code for the update and load actions:
<Request Action = "Update">
<Task>
<TaskName>Task333</TaskName>
<CombinedLaborDistributionName>mm1<CombinedLaborDistributionName>
<LaborStandardAssignments>
<LaborStandard GenericDepartmentName="Manager" LaborStandardName="mm1"/>
</LaborStandardAssignments>
</Task>
</Request>
<Request Action = "Load">
<Task>
<TaskName>Task1</TaskName>
</Task>
</Request>
63
Combined Labor Distribution
Note that <CombinedDistributionSetting> block is the same as the one in the existing <TaskGroup> API
The following samples are of the XML API code for the update, delete, load, retrieve For Update, and
retrieveAllnames actions:
<Request ACTION="update">
<CombinedLaborDistribution>
<name> aaa</name>
<description> aaaa</description>
<IsActive>true</IsActive>
<GenericDepartmentName>Counter</GenericDepartmentName>
<CombinedOffsetTypeName>Start before distribution period</CombinedOffsetTypeName>
<OffSetTimeAmount>20</OffSetTimeAmount>
<CombinedDistributionSetting>
<CombinedDistribution>
<CombinedDistributionType>Optimal Remainder Spread</CombinedDistributionType>
<DistributeWithLaborPeriod>True</DistributeWithLaborPeriod>
<SpreadExcessLabor>right</SpreadExcessLabor>
<PeriodsOfApplicationUsed>
<CombinedPeriodsOfApplication>
<POAElementList>
<AbsolutePOAElement>
<DayOfWeek>2</DayOfWeek>
<StartTime>00:00</StartTime>
<EndTime>12:00</EndTime>
</AbsolutePOAElement>
<AbsolutePOAElement>
<DayOfWeek>3</DayOfWeek>
<StartTime>07:00</StartTime>
<EndTime>08:00</EndTime>
</AbsolutePOAElement>
</POAElementList>
<POAReferenceTypeName>Absolute</POAReferenceTypeName>
</CombinedPeriodsOfApplication>
</PeriodsOfApplicationUsed>
64
Enterprise Archive
</CombinedDistribution>
</CombinedDistributionSetting>
</CombinedLaborDistribution>
</Request>
Smart Operations (6.3.5)
Creating new locations, such as stores, can be a long and repetitive process. Use Smart Operations, which includes
Smart Copy and Smart Move, to create multiple locations by copying or moving existing locations – along with the
associated configuration rules and option sets – from the organizational and forecast maps.
For detailed information see Feature Guide - Smart Copy and Move.pdf that is available at the site that
contains this service pack documentation.
Enterprise Archive
Enhanced copy job performance (6.3.8)
(WFM-54687) Important: This new feature applies to clients who:
•
Use Enterprise Archive or Express Archive to archive their database
and
•
Use the group shift feature in Enterprise eTIME system to assign shifts to groups of employees
or
•
Use Enterprise Attendance.
Enterprise eTIME 6.3.8 and higher 6.3 service packs provide an enhancement to optimize the performance of
Enterprise Archive copy jobs. The copy mechanism for the GroupShift and Enterprise Attendance database tables is
adjusted for faster performance. You receive the enhancement when you upgrade from Enterprise eTIME 6.3.7 or a
lower 6.3 version to 6.3.8 or a higher 6.3 version.
What to do after you upgrade:
•
If you use Enterprise Attendance, data will no longer be archived by Enterprise Archive or Express Archive.
Data that was archived before you upgraded to Enterprise eTIME 6.3.8 is still available in the archive
database. Going forward, you must use your production database to look for historical attendance data.
•
If you use Express Archive, you must use version 6.3.8 or higher to archive data.
•
If you use Enterprise Archive and use the group shift feature to assign shifts, you must run a data maintenance
script against your archive database. This allows you to run Enterprise Archive copy jobs after you upgrade
Enterprise eTIME.
65
Enterprise Archive
To run the data maintenance script:
a. Install the Enterprise eTIME 6.3.8 or higher service pack in your production and archive environments.
Note: After you upgrade to Enterprise eTIME 6.3.8 or higher service pack, Enterprise Archive will not run
until you run the data maintenance script. If you try to run Enterprise Archive, the following message
appears:
“Your request cannot be processed: WFP-83616 Perform data maintenance against the ARCHIVE
database before the next copy job for start date of <copy start date>. Refer to the WFC.log file for details.”
b. Back up the archive database against which you intend to run the data maintenance script.
Important: Ensure that you run the script against the archive database.
c.
Navigate to the following directory:
adp\deployments\servicepack\<current service pack number>\shared_staging\archiveScripts
d. Use a text editor to open the appropriate database maintenance script for editing:
If your system runs on a SQL Server database, open mss-WFM51202-patch.sql.
If your system runs on an Oracle database, open ora-WFM51202-patch.sql.
e. Enter the copy start date. This date represents the day after the end date of the last Enterprise Archive
copy job’s date range. To enter the date:
If your system runs on a SQL Server database, find the line that begins with “set @archive_date” and
replace the default date with the copy start date.
If your system runs on an Oracle database, find the line that begins with “v_archive_date” and replace the
default date with the copy start date.
f.
Save the edited script.
g. Use a database query tool to run the edited database maintenance script against the archive database
only.
66

Features Introduced in Enterprise eTIME Suite 6.3

Transcription

Similar documents

Key Feature s - BeneDirect

How to use Encyclopedia How to use Encyclopedia Britannica Online

Enterprise eTIME

WebsPlanet Designer`s Guide

POEMS 2.0 USER GUIDE

ELECTRONIC TIME CARDS WITH KRONOS QUICK START GUIDE

Georgia Navigator – Past, Present and Future

Getting Started With Enterprise eTIME

comedian runs for president ginnie spring adventure picasso meets

Comping Guide - Compers News

The Mortician`s Guide to Retail Banking David W. Furnace President

Testing 101: Understanding Compliance Testing