Time & Attendance Suite 7.0.9 Document Release Date: October 2015
Service Pack Release Notes
Contents Introduction .................................................... 1 International considerations........................... 3 Product compatibility information................... 3 What’s New?.................................................. 4 New features introduced in 7.0.9 ................ 4 Features introduced in previous 7.0.x service packs ................................... 6 Installing the service pack............................ 13 Implementation considerations .................... 13 Support for JRE v1.8................................. 13 Discontinued support for Java with the Chrome browser ............................... 13 Setting for future implementation .............. 14 Maintaining log files with an Apache web server .............................................. 14 Translation and customization .................. 14 Activities .................................................... 15 Time & Attendance suite ........................... 17 Time & Attendance.................................... 17 Setup Data Manager ................................. 19 Device Manager ........................................ 19 Integration Manager .................................. 20 Scheduler .................................................. 20 SMS Quick Fill settings moved from Custom_WMC.properties ....................... 20 Forecast Manager ..................................... 21 Budgeting (formerly “Operations Planner”) ............................. 23 Operational Reporting ............................... 23 SuccessFactors integration ...................... 23 Updated instruction to change the logon page logo ...................................... 23 Documentation updates............................... 23 Update to Time & Attendance System Administrator’s Guide ................ 23 Correction to Scheduler System Administrator Guide................................ 24 Operational Reporting documentation ...... 24 Collaboration documentation .................... 24 Database scripts .......................................... 25 Known anomalies ........................................ 34 Known anomaly ........................................... 34 Issues Resolved in Service Pack 7.0.9........ 37 APIs........................................................... 37 Database................................................... 38 Installation ................................................. 38 Activities .................................................... 39 Attendance ................................................ 41
Product compatibility information
Installing the service pack
Issues Resolved in Service Pack 7.0.9
Introduction This document provides information about Time & Attendance version 7.0 Service Pack 9. ADP recommends that you read this document before you install Service Pack 9, and that you keep a printed copy with the product documentation. This service pack includes the following products: Accruals
Budgeting (formerly known as “Operations Planner”)
Time & Attendance
Note: Time Entry Employee, Time Manager, and ADP QuickPunch are integrated into the Time & Attendance suite. They are not separate products. This document provides the following information about Time & Attendance 7.0 Service Pack 9: •
Product compatibility information
Information about documentation updates and corrections
Descriptions of issues that were resolved in the Service Pack.
“What’s New?” on page 4 explains where to find information about new features in Service Pack 9.
Leave ........................................................ 42 Time & Attendance ................................... 43 Integration Manager.................................. 54 Scheduler.................................................. 55 Budgeting (formerly “Operations Planner” 62 Forecast Manager..................................... 62 Task Management .................................... 63 Navigator................................................... 64 Device Manager........................................ 65 QuickGlance ............................................. 66 TeleTime IP............................................... 66 Legal statement .......................................... 67
International considerations All non-English implementations of Time & Attendance 7.0.x require a Time & Attendance 7.0.x Language Pack which provides translations of new and corrected text strings in the suite of products. The language pack must be installed after the Service Pack is installed. Note: All new features released with the 7.0.9 service pack will be supported in all languages in the 7.0.9 language pack.
Product compatibility information The following product versions are compatible with Time & Attendance 7.0 Service Pack 9. This table represents compatibility among products that are available on the release date of this service pack. Check the Release Notes that accompany the latest service packs for add-on products, to see if they list compatibility with Time & Attendance 7.0 Service Pack 9. Note: Navigator is not listed in the compatibility table because it is an integral part of Time & Attendance. Product
Setup Data Manager
2.1.x, 2.2.x, 2.3.x, and 3.0.x
1.0.x, 1.1.x, 2.0.x, 2.1.x
Translation and Customization Toolkit
What’s New? New features introduced in 7.0.9 The following features are being introduced in Time & Attendance 7.0.9. This section presents brief descriptions of the features. For detailed information about any feature, refer to the feature guide PDF file or other documentation listed with the feature. Feature guides are available at the site that contains these Release Notes. Feature
Copy activity details
Gives duration entry employees the ability to copy detail information associated with an activity to another activity on a different day. This feature works in hourly or project view timecards.
Copy Activity Details
Enhanced future dating validation period
Enhancements to further validate activity events entered for future days (current pay period + 1 day; today + 1 day). The system may reject an entry or prevent the user from saving the timecard, depending on the entry method (for example, timecard form, web forms, API).
Enhancements to Future Dating Validation Period
Work Time Request allows an employee or a manager to request additional work time for an employee. This new request can be configured to allow the requester to alter the default values of the shift, such as location, job, labor account, work rule, and so on. The Work Time Request can also be configured to support approval settings, such as those found in Global Time Off Requests, and to allow the approving manager to alter the request's parameters. The Work Time Request is only available through the Navigator user interface.
Work Time Request
Brazilian Audit reports enhancements
Enhancements include capaibity to configure reports from a HyperFind query or Device group, capability to configure a new pay code attribute buidling block, and to use the standard reports framework to generate and view reports withoin the application.
Enhancements to Brazilian Audit Reports
Brazilian Data Collection: Punch and shift tolerance
The Punch and Shift Tolerance feature provides the ability to configure the maximum tolerance in minutes allowed per shift, for all punches in a shift, for both discount and extra time. This feature can be used only for employees with a fixed schedule.
Punch and Shift Tolerance
Scheduling Work Time Request
Brazilian Data Collection
This feature supports Brazilian Compliance rules specifically. For organizations in Brazil, this feature provides configurable support for Brazilian rounding rules; reporting of punches in AFDT, ACJED, nd Timecard Mirror reports will not be affected.
Enhanced to support effective-dated versions of labor standards. You can continue to use the previous version of the LSBI with labor standards that are not effective- dated. You can also use the enhanced version of the LSBI API with labor standards that are not effective- dated – it is backward compatible. However, when you use the enhanced LSBI, you can no longer use the previous version.
Enhancement for Labor Standard Integration with Accenture StandardsPro
Timekeeping Labor Standard Bulk Import API
Technology Support for Microsoft Windows 10
Beginning with v7.0.9, Microsoft Windows 10 with Internet Explorer 11 is supported. Microsoft Edge browser is not supported.
Features introduced in previous 7.0.x service packs For information about features, refer to the feature guide PDF files or other documentation that can be accessed from the site that contains the Release Notes for each service pack.
7.0.8 service pack Product
Time & Attendance suite
Enhanced integration APIs
Time & Attendance
Enhanced value profile setup Extended translation support Challenge filter for Leaderboard
Ability to request one day off using two half day requests Employee compliance call log Work time request Processing of time off requests for unscheduled days
Operational reporting for Fatigue Management
7.0.7 service pack Support for Windows Server 2012 — Beginning with service pack 7.0.7 introduces support for Windows Server 2012 server and Windows Server 2012 R2.
7.0.6 service pack Product
Time & Attendance suite
Leaderboard widget Enhancement to Log Gathering tool Enhancements to the Electronic Timecard Mirror report Enhanced control over content of error content in log files
Time & Attendance
Accruals validation for cascading pay codes
Activity validation (enforce variance between shifts and allocated activity hours, prevent users from entering future-dated activities)
System setting for shifts in defined night periods Prevention of pay code edits for time off requests on public holidays Automatic approval of cancelled global time off requests Control of available pay codes for time off request types
Metrics indicators for budget-adjusted labor forecast
7.0.5 service pack Product
Feature New global setting for accruals lookback period Note: This feature was inadvertently not included in the original 7.0.5 Release Notes. See CENG-7907 in the Summary of Resolved Issues - Time & Attendance Suite 7.0 Service Packs that is posted with these Release Notes. Global setting for processing adjacent shifts Enhancement to Accrual Detail report
Grant and Project Tracking widget Form submission for days that have been approved Control of activities to use for idle time
Staffing widget feature enhancements Menu enhancement in the Schedule widget Schedule totals for Schedule widget
Time period selection in Contact Tracking dialog box Property setting for “Override Shift” option Enhancements to Coverage tab in Schedule Planner
Global settings for submitting punches for approved days Improved format of two operational reports
7.0.4 service pack Product
Time & Attendance suite
Linux App Tier Chrome support Application Health Monitoring Report pagination Excel-based operational reporting Device time zone assignment with Brazilian Data Collection Improved performance of reports and QuickNavs in hosted environments
Time & Attendance
Increased number of custom fields 24-hour rule overlap
New “Delete Duration Event” activity form Enhancement to duration entry in forms
Staffing widget feature enhancements Menu enhancement in the Schedule widget Schedule totals for Schedule widget
Flexible open shift management
Setup Data Manager
Support for HyperFind filters
Product name change: Operations Planner now called “Budgeting” Beginning with Time & Attendance 7.0.4, the name “Operations Planner” changes to “Budgeting.” The following table shows the effect of the name change on the related operations planning applications: Previous Name
Basic Operations Planner
Basic Budget Planner
Operations Planning Option Sets
Budgeting Option Sets
The name change affects the user interface, but does not affect the product functionality. Two PDF manuals have been updated with the new name: • Budgeting Configuration and User Guide • Getting Started with the Budgeting API The online help will remain unchanged for 7.0.4, and will be updated with the new name with version 8.0.
7.0.3 service pack Product
Form duration entry for project view employees
New template tags for leave documents
Alphabetical listing of work rules in Staffing and Schedule widgets Work rule transfer included in tooltips
Issue tracking Ability to print project details and the project calendar
Note: Features introduced in Task Management versions 6.3.7 through 6.3.9 are included in version 7.0.1 and higher.
7.0.2 service pack Product
Time & Attendance suite
Application health monitoring Enhanced custom message display on login screen
Time & Attendance
Consistent display of amount in timecards and schedules Enhanced configuration of grant expirations Express Upgrade integration with Configuration Manager Sorting the Time Detail Report by primary labor account Sorting the Leave Hours Summary Report by leave case fields Support for ADP QuickPunch Plus biometric templates Employee photos
Processing of non-chronological Start Only forms Enhanced matching of form durations to shifts
Support for InTouch v2.0 new features and enhancements
Logs in HTML format
Hours of operation in skill & certification workloads Employee Self-Scheduling (ESS) enhancements
Alerts Metrics Ability to edit a released project
Note: Features introduced in Task Management versions 6.3.7 through 6.3.9 are included in version 7.0.1 and higher.
Enhanced configuration of grant expirations (7.0.2) (WFM-57438) 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 in Setup > System Configuration > System Settings > Global Values tab: global.WtkTotalizer.ExpirationsBasedOnHistoricalDate The default setting is “No.” 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. The solution included the creation of a new script called WTK070002003.sql.
7.0.1 service pack Product
Time & Attendance
Short names for valid labor accounts Overlapping durations Historical edits with pay from schedule punches
Activity name search in the Activity widget New system activity queries
Multiple template Import API Enter Time Off Applying pay codes to one shift of a multiple-shift day Associating holidays with locations Checking for schedule rule violations for week-long periods Preserve Pattern Shifts Auto-approval of global time off requests
Task Management Note: Features introduced in versions 6.3.7 through 6.3.9 are included in version 7.0.1 and higher
Recurring projects Licensing Function access control point for cancelling projects New priority level and completion status Managers can assign tasks to employees either at the store or department level. Department managers can access their department(s) as defined in their Forecast Map Profile. Users can edit the “Project Type” field at any time before the project is submitted for approval. Store managers can see task descriptions. Users can add attachments to a completed project. A Refresh button has been added for updating the data on a page. Variance in Monitoring now shows “Hours Less than Allocated Hours” as well as “Hours Greater than Allocated Hours.” Users can add actual hours from the “Project Start Date” as well as the “Task Start Date.” “Day Name” appears with the date on the Manage Tasks page. A new field on Priorities, Show List View, lets you show List Details rather than the Gantt chart view on the Project List page. A warning dialog displays when a user submits a project or changes the status of a project (“Are you sure you want to …?”). The Calendar Start Date and End Date come up in the same month that was entered for the Release Date. Store managers are not required to select a job for a task. An urgent project can be released on the same day that it is created on. It does not wait for the nightly batch process.
Enhanced copy job performance
Support for ODP .NET client-side drivers for Oracle 11gR2 Support for MBean attributes to monitor system health Additional protection against CSRF vulnerabilities Encryption of SSO-related cookies
Improved performance when Schedule Planner loads (7.0.0) (WFM-36905) Time & Attendance version 7.0.0 and later versions, the performance of Schedule Planner when it loads a large number of labor transfer sets or locations has been improved. Before this improvement, the process of loading Schedule Planner sometimes caused application wait events on the database server which slowed performance to an unacceptable level.
Installing the service pack
Installing the service pack For complete instructions for installing the service pack, see the document called Time & Attendance — Applying a 7.0.x Service Pack (Applying7 0 xServicePacks_ADP.pdf) in the same location as these Release Notes.
Implementation considerations “Support for JRE v1.8” on page 13
“Device Manager” on page 19
“Discontinued support for Java with the Chrome browser” on page 13
“Integration Manager” on page 20
“Setting for future implementation” on page 14
“Scheduler” on page 20
“Maintaining log files with an Apache web server” on page 14
“Forecast Manager” on page 21
“Translation and customization” on page 14
“Budgeting (formerly “Operations Planner”)” on page 23
“Activities” on page 15
“Operational Reporting” on page 23
“Time & Attendance” on page 17
“Updated instruction to change the logon page logo” on page 23
“Setup Data Manager” on page 19
Support for JRE v1.8 To maintain compatibility with Oracle’s product life cycle for Java, the following changes have been made to the Time & Attendance suite’s level of support for Java: •
Beginning with version 7.0.6, the Time & Attendance suite supports the Java 1.8 Plug-in.
Beginning with version 7.0.6, the Time & Attendance suite no longer supports the Java 1.6 Plug-in.
Discontinued support for Java with the Chrome browser Google’s Chrome browser will support Java, by default, until January 2015. After January, Google will not continue to support the Netscape Plug-in API (NPAPI) that is required to run Java on client machines. Much of the employee functionality in Time & Attendance 7.0.4 can be configured without the need for Java; therefore, you can continue to use the Chrome browser on properly configured Time & Attendance servers with version 7.0.4 and higher. Important: If you use the Chrome browser for versions of Time & Attendance that were released before version 7.0.4, you will see messages about an incompatible browser version. ADP recommends that you do not use the Chrome browser for earlier versions of Time & Attendance. If you choose to continue to use the Chrome browser, disable the browser’s auto-update feature.
Setting for future implementation The following setting on the Global Values tab in System Settings is not active: global.wdm.punchsync.hours Do not consider this setting when configuring your system.
Maintaining log files with an Apache web server If you use an Apache web server, the log files can become extremely large and purging them manually requires a server restart. To avoid this, you can change the httpd.conf file so that the logs are rolled back daily and deleted weekly: 1. On the web server machine, navigate to \\ADP\apache\conf and open httpd.conf with a text editor. 2. Search for the following line: CustomLog "logs/access.log" common 3. And change it to: CustomLog "|bin/rotatelogs logs/access.log.%Y%m%d 10" common 4. Save the file. 5. Restart Apache.
Case-sensitivity of custom_WDMSite property file name The name of the custom_WDMSite properties file (if you use it) must use upper and lower case exactly as shown in this paragraph for case-sensitive operating systems such as AIX and Solaris. This is also true if you use Linux and have it configured to be case-sensitive. If the property file name is not represented exactly as custom_WDMSite.properties, the property file is not recognized.
Translation and customization Changed text strings For translation and customization purposes, the following text files are available that contain the text strings that have changed since Time & Attendance 7.0: •
changedStringFilesFull.709.txt — Contains text string changes for all Time & Attendance 7.0.x service packs including the current service pack.
changedStringFilesIncr.709.txt — Contains text string changes associated with the current service pack only.
The files indicate in which properties file each text string appears and, if the properties file is contained in a .jar file, the name of the .jar file. These files are installed with the service pack. After installation, the file is located in \adp or \ on Windows systems. On UNIX systems, the file is installed in or /usr/local/.
Activities Enhanced auditing of events with activity name changes (CENG-14770) If you have existing Activities transaction hours export interface, data in the Activities database tables change if an Activity name is changed. A change to the Activity Name will trigger the deletion of the original transaction and the creation of a new transaction with the new Activitiy Name and a new internal database transaction spanid: Previous processing (example)
New processing (example)
• In the Activity timecard editor, a user changes the name of the activity that is associated with an 8-hour span, from “Activity A” to “Activity B.” • The internal database transaction span ID is “10” and does not change when the activity name is changed. • In the Activity timecard editor, a user deletes a transaction 8hour span for Activity A and creates a new transaction using Activity B. • The internal database transaction spanID is 10 for the original record —(Activity A) — and will show as deleted.” • The internal database transaction spanID is 20 for the new record —(Activity B).
• In the Activity timecard editor, a user changes the name of the activity that is associated with an 8-hour span, from ‘”Activity A” to “Activity B.” • The internal database transaction spanID for the original transaction Activity A is marked as deleted when the activity name is changed. • A new internal database transaction spanID is created for Activity B.
If you have results export interfaces for Activities and do not modify them for this new behavior, the interface associates all of an activity’s data with its new name; there is no indication of the activity’s previous name in the results output.
If you modify your results export interfaces to accommodate changes to previously reported results that include a name change, the new and previous activity names are included with their associated data in the results output.
Property setting to control cache activity (WFM-40713) Beginning with 6.3.2, the following property has been added to WFA.properties to control cache activity and maintain performance in heavy system use scenarios. For example: •
Multiple instances of Activities are pointed to the same database server.
The system contains several thousand Activities employees.
The client imports new Activities employees or updates existing employees.
The property is called: com.kronos.wfa.MAX_EMPLOYEE_CACHE= The value represents a number of Activities employees. If the number of Activities employees in the system is less than or equal to the value when Time & Attendance starts, the Activities employee cache pre-loads. The default value for the property is 6000. If you want to change the value of this property: 1. Create a file called custom_WFA.properties. 2. Add the setting to the file and specify the value you want to use. You cannot specify zero (0) or negative numbers.
Property setting for processing labor account transfers with activities (CE-24256) A property setting has been added to wfa.properties to allow clients who use Activity cells and Stop-only forms only to choose whether account transfer times are considered when the application adjusts activity start and end times. The new property setting is called:
com.kronos.wfc.activities.calculator.business.INCLUDE_TRANSFERS_IN_FIRST_LAST_ VARIANCE •
To cause account transfer times to have an effect on how activity start times are adjusted, set the property value to true. This causes account transfer times and activity start times to be synchronized appropriately.
To prevent account transfer times from having an effect on how activity start times are adjusted, set the property value to false.
Important: This setting is a global setting that applies to all employees. The following is an example scenario for which this setting is important: •
At 8:00 a.m., an employee joins Cell 1 to perform an activity associated with labor account /101//////.
At 9:00 a.m., the cell leader submits a Stop form for the activity.
At 9:15, the employee leaves Cell 1 and joins Cell 2 to perform an activity associated with /102//////
At 10:00 a.m., the leader of Cell 2 submits a Stop form for the activity. The system calculated 9:00 a.m. as the start of the activity.
If the property value is set to false, the results for this employee are: •
The first activity starts at 8:00 a.m. and ends at 9:00 a.m. Only account /101////// is associated with the activity.
The second activity starts at 9:00 a.m. and ends at 10:00 a.m. Account /101////// is associated with the period from 9:00 a.m. to 9:15 a.m.; account /102////// is associated with the period from 9:15 a.m. to 10:00 a.m.
If the property value is set to true, the results for this employee are: •
The first activity starts at 8:00 a.m. and ends at 9:15 a.m. Only account /101////// is associated with the activity.
The second activity starts at 9:15 a.m. and ends at 10:00 a.m. Only account /102////// is associated with the activity.
Time & Attendance suite “Admin” user name for notification servers only Do not use “Admin” as a user name for any server other than the Time & Attendance notification server (for use with the Alerts feature). If you try to log in as “Admin” to any other Time & Attendance server, the following error message appears: "Could not connect to Notification Server."
Character restriction for database and XMLUSER passwords The KRencryptNS.bat tool for Time & Attendance version 8.0.x that is used to encrypt database and XMLUSER passwords does not support the use the “less than” sign ( System Settings > Global Settings: global.security.external.product.sessionID.enabled
Configurable single sign-on settings The following new system settings have been added to “site.security” as part of configurable single sign-on (SSO) support: •
Enhanced platform support/protection The following enhancements were introduced with version 7.0.1:
Support for ODP .NET client-side drivers for Oracle 11gR2.
Support for MBean attributes required to monitor the health of the Time & Attendance system.
Support for Integrated Windows Authentication.
Support for encryption of ADP SSO-related cookies.
More protection against cross-site request forgery (CSRF) vulnerabilities. Includes additional CSRF guard tokens to protect more Time & Attendance application pages
Support for HTTP Only flag on cookies
Setting removed from Web & App Server tab in System Settings (CENG-11899) Beginning with Time & Attendance version 7.0.8, the following setting is removed from Setup > System Settings > Web & App Server: site.webserver.sharepoint.session.timeout
Compatibility View-related error message in IE If you log into Time & Attendance using Internet Explorer, you might see the following message: "Unsupported browser. Users of IE 8 and higher should turn off Compatibility View." This error can occur even if the Compatibility View icon is not in the Address Bar and the Compatibility View option is not in the Settings menu. However, Compatibility View may be enabled for intranet sites. To check this: 1. From the browser, select the Tools Menu and select Compatibility View Settings. 2. Check to see if the option called “Display intranet sites in Compatibility View” is selected. If the setting is selected, de-select it. 3. Refresh the browser.
Ad hoc option user interface for custom reports (WFM-45546) If clients with ad hoc options for custom reports upgraded from Time & Attendance version 6.2.x or lower to version 6.3.1 through 6.3.4, the ad hoc option was not available. Beginning with version 6.3.5, the ad hoc option has been re-instated. The user interface for selecting ad hoc values is different from previous versions. Use the following guidelines: •
For fields that use drop-down lists, enter the ad hoc value in the text box next to the list. Then, click the blue arrow to place the value into the list as the selected item.
For a multiple selection setting that uses “Available” and “Selected” list boxes, enter the ad hoc value in a text box below the list boxes. Then, click the blue arrow next to the text box to place the entry into the “Selected” list.
Note: If you enter an invalid value in an ad hoc field, the report will not run successfully. When you create the custom option setting, provide a description that clearly states what type and range of values the field accepts.
Setup Data Manager No support for job or TeleTime IP-related HyperFind filters Setup Data Manager cannot copy and transfer HyperFind queries that contain any HyperFind filters that are related to jobs or TeleTime IP. An error message appears stating that the HyperFind query cannot be read.
Device Manager Property setting to control master instance designation (WFM-43695) Beginning with 6.3.4, you have more control over which Device Manager instances can be designated as the master instance. Do this by adding an instance property to the custom_WDMSite.properties file. The property is called: site.wdm.server.master.eligible Valid settings are “true” and “false.” A “true” setting means that instance can be a master instance. Note the following information about setting and changing the property value: •
If you add the property while the instance is running, stop and restart the instance so that the property takes effect.
After you add the property to the custom_WDMSite.properties file, you can change the setting in System Settings > Device Manager tab. If you use this method to change the setting (instead of editing the properties file), you do not need to stop and restart the instance.
If you change the setting to from “true” to “false” using System Settings > Device Manager, the instance stops being the master instance when the next Instance Monitor cycle begins.
Property setting for Activities QuickGlance transaction URLs (WFM-44146) A new custom property has been introduced to ensure that Activities QuickGlance transaction URLs reference the correct language in the following scenario: •
The site uses multiple Time & Attendance instances for multiple languages. The instances are named to differentiate which language they used. For example, an English instance may be called “EN_Instance” and a French instance may be called “FR_Instance”.
The site uses data collection devices. Each device is configured to use one of the languages and to communicate with the Device Manager instance that uses that language.
The new custom property that ensures that Device Manager uses the IP address that is specified in the com.kronos.wdm.wfa.remotetransactions.ip when it creates the URLs for Activities QuickGlance transactions. To add the custom property: 1. Use a text editor to create a property file called custom_wdm.properties in the following directory: \1\applications\wdm\properties 2. Add the following property and setting to the property file: com.kronos.wdm.wfa.remotetransactions.ip.enabled=true
Integration Manager Requirement for multi-server installations (CENG-11641) The Time & Attendance product installation documentation for version 7.0 stated that, for clients who use Integration Manager, the application did not need to be installed on all application servers. This is incorrect - you must install Integration Manager on all application servers. The product installation documentation has been updated to correct this error.
Viewing Link XML Log reports (WFM-7249, WFM-24606) To view Link XML Log reports on systems that use the Apple Safari 4 or 5 browser, you must use the “View Frame Source” option for viewing in the browser. Otherwise, the Link XML Log reports view window is blank.
Restricted name for location sets (WFM-48269) Do not give a location set the name “Selected Locations.” If a location set with that name already exists in your system, delete the location set and recreate it with another name. This is necessary to prevent an issue when selecting a location in Schedule Planner.
Forecast Manager Labor standard configuration in multiple language Time & Attendance systems For sites with multiple language instances of Time & Attendance, you can enable the ability to configure labor standards with different language generic categories. During configuration of a labor standard, the application checks for a generic category instance of the same language. If one does not exist, the application uses the English version. Without this capability, if a labor standard is configured with a different language generic category, the application could not create a forecast at the category level. To enable this capability, add the following property setting to the custom_WFSO_Site.properties file:
forecaster.GenericSite.ResolveMultiLanguageGenericCategories=true To disable the capability, change the setting to false or remove the property from the file.
Utility to insert missing generic forecast categories (WFM-15849/CE-22604, WFM-15289/CE-23383) With Time & Attendance 6.1.0 through 6.1.3, if a user moved an effective-dated category and its associated nodes to a position under a different node in the Forecast Map, the appropriate generic categories were not added to the database. This issue prevented the user from importing labor standards into the application. The solution for CE-22604 fixed the problem of generic categories not being created after a move. Also, a utility is available for clients who upgrade to version 6.2.x and need to insert generic categories that are missing because of category moves they performed before the issue was resolved. Specifically, the utility does the following: •
Adds the generic forecast categories to the database
Restores the corresponding relationships between the generic categories and the actual categories that are already in the database.
The utility is included in the Forecast Manager installation. (WFM-15092/CE-23685) With the release of Time & Attendance version 6.2.1, the generic category repair utility was enhanced to provide the following options: •
log only – Allows you to monitor and detect inconsistent generic categories
log and repair – Logs inconsistent generic categories and repair them
To enable the “log and repair” option: 1. Shutdown all of the Time & Attendance application servers that are connected to the Time & Attendance system database. 2. Select only one of the servers and add the following system settings to the custom_WFSO_Site.properties file that is located in /1/applications/wfso/properties.
– – –
WFF.GenericCategoryRepairService.LogAndRepair = true WFF.GenericCategoryRepairService.startDate=1/1/2010 WFF.GenericCategoryRepairService.endDate=12/31/2010
3. Restart the server. While the server restarts, if the repair utility detects and repairs inconsistent generic categories, they are listed in wfc.log. The log file is located in /1/log. 4. Restart the remaining servers. To enable the “log only” option: 1. Shut down any of the Time & Attendance application servers that are connected to the Time & Attendance system database. 2. Add the following system setting to the custom_WFSO_Site.properties file that is located in: /1/applications/wfso/properties:
WFF.GenericCategoryRepairService.Log = true 3. Restart the server. While the server restarts, if the repair utility detects missing generic categories, they are listed in the wfc.log located in /1/log. To enable multi-language support for “log only” and “log and repair” options, add the following system setting to custom_WFSO_Site.properties:
forecaster.GenericSite.ResolveMultiLanguageGenericCategories=true To disable the repair utility, remove the system setting(s) that you added to custom_WFSO_Site.properties.
Forecast Category Repair utility to correct expiration dates of forecast categories (CE-23685) With earlier versions of Time & Attendance 6.1.x, if a user changed the expiration date of a parent category in the Forecast Map, the change was not applied to some of the child categories. This issue has been resolved. As part of the solution, a Forecast Category Repair utility is available for clients who need to correct the expiration dates of forecast categories because parent forecast categories were de-activated before the issue was resolved. To activate and use the utility: 1. Stop the Time & Attendance application server. 2. Add the following properties to custom_WFSO_Site.properties located in: \ADP\1\applications\wfso\properties If the file does not exist, create it now.
#Automatic Forecast Category Repair WFF.ForecastCategoryRepairService=true WFF.ForecastCategoryRepairService.startDate= (for example, 05/01/2009) WFF.ForecastCategoryRepairService.endDate= (for example, 08/30/2009) 3. Restart the Time & Attendance application server. The effective dates of the forecast categories are corrected. 4. After the utility updates the database, turn the utility off in either of the following ways: –
Delete the properties you added to custom_WFSO_Site.properties.
Change the value of the WFF.ForecastCategoryRepairService property to false.
Budgeting (formerly “Operations Planner”) Important: Beginning with version 7.0.4, “Budgeting” is the new name for Operations Planner.
Recommended system settings related to generating sales plans ADP recommends that you use the following combination of values for the indicated system settings to help ensure that sales plans generate successfully: •
System Settings > Budgeting:
site.budgeting.VolumeBudgetEngine.useAdaptiveModelSelectionMethod = true and •
System Settings > Forecasting:
Operational Reporting The Validate Template feature does not work with Time & Attendance servers that are not configured as report server instances.
Updated instruction to change the logon page logo The instructions in the Time & Attendance Translation and Customization Guide for changing the logo on the Time & Attendance logon page do not show the correct name for the logo graphic. The correct name of the graphic is “logon_logo.png” -- not “logo-tagline.gif.” As stated in the guide, the location of the logo graphic is: /wfcstatic/applications/wpk/html/images/branding/logon_logo.png
Documentation updates Update to Time & Attendance System Administrator’s Guide (CENG-13422) The following information is not in the 7.0 version of the Time & Attendance System Administrator’s Guide: Beginning with Time & Attendance version 7.0.9, the following system setting is removed from Setup > System Settings > Global Settings: global.security.external.product.sessionID.enabled
Correction to Scheduler System Administrator Guide (CENG-9919) The Scheduler System Administrator Guide incorrectly states that the daily coverage counts ignore the “Exact Match and “RequireExactMatch” settings when a shift set unit chooses 1-hour, 4-hour, 8-hour, and 12-hour spans in Schedule Planner. The settings are not ignored; if the settings are enabled and there are no exact matches, the coverage count shows as “0.”
Operational Reporting documentation 7.0.6 The Getting Started with Excel-based Operational Reporting guide has been updated for Time & Attendance 7.0.6 and higher with the following information: •
Provides navigation and setting for the new Validate Template Function Access Profile.
Notes that Validate Template works only from the Windows Companion server when in a Unix environment.
The Operational Reporting Beans Reference Guide has been updated for Time & Attendance 7.0.6 and higher with the following information: •
The attribute named periodwithtransfer has been added to the Report Shifts bean
The PeriodTotalSummary bean has been added to the Total Summary bean
The Custom fields have been added to the Personality bean.
7.0.8 These same operational reporting documents and the Fatigue Management documentation were updated for version 7.0.8 with the release of operational reporting for fatigue management.
Collaboration documentation The Collaboration Configuration Guide has been updated with the following information which applies to version Time & Attendance 7.0.4 and higher: The phone mapping was removed completely and the labels in tibbr were changed to mirror those of the People Editor in Time & Attendance (i.e. Phone 1, Phone 2,...). Phone mapping is now automatic; you do not need to configure settings in the Social tab in System Settings.
Database scripts The following table lists the script files that are included in this release. The shaded scripts are new in version 7.0.9: Script
Modify data in report template to resolve issue with the Person Details (Spreadsheet Export) report not including the “Additional Information” column.
Resolves performance issue for Labor Accout Set update action for Emloyee Group type
Resolve issue with the Employee Hours by Day (Spreadsheet Export) report
Update RPTSP_TIMEDETAILSEXCEL to resolve issue with the Time Detail (Excel) report showing some hours worked for transfer shifts as being charged to employees’ home accounts.
Resolve issue with the All Zone report showing an employee with no transfer for the first segment of a shift and a transfer for the second segment of the shift.
Modify the RPTSP_ActivityAudit stored procedure to resolve issue with Activity Audit report not showing activity span deletions.
Modify the EOUKBAPROPERTYINST database table to resolve the issue with employee deletion operations not entirely deleting the employee from the database.
Resolve issue with the Employee Time Detail (Spreadsheet Export) report opening the last tab by default instead of the first tab.
Resolve discrepancies between employees’ allocated hours shown on the Activities tab in the timecard and in the Activity Detail by Group report.
Resolve issue with punches showing as “Marked as Reviewed” on the Mirror report (Brazilian Data Compliance) not matching the punches shown on the AFDT report (Treated Data Source File).
Resolves a performance issue on the ACJEF report.
Resolve duplicate entries for each shift that is offered.
Resolve issue regarding inability to use or edit HyperFind queries with full-time equivalency conditions after upgrading to Time & Attendance version 7.0.x.
Resolve issue with historical edit hours appearing in the Actual vs. Schedule by Labor Account (Data) report when the user specified that the hours should not affect totals.
Support for ClickSoftware integration.
Resolve issue with discrepancies, in certain situations, between accrual balances in the timecard (Accrual tab) and the Accrual Detail report.
CENG-14942, CENG-13422 CENG-13589
Remove global.security.external.product.sessionID.enabled from system settings.
Modifies Foreaster tables to accept labor standard bulk import
Support enhancements to Brazilian Compliance reports.
Resolves failure to complete processing on the Activity Summary report
Resolves issue with interfaces having five or more variables showing as Running but did not start.
Support for the copy/paste activity details feature.
returning information based on employee names instead of employee IDs.
Resolve issue with duplicate entries appearing in the transaction section of the Employee Transactions and Totals (Excel) report.
Resolve issue with continuously running query on database server causing performance issues on the database server.
Support Brazilian Shift Tolerance feature.
Resolves issue that displayed pay codes when options Visible in Report and Report Totlas were not enabled.
Resolves intermittent error for some managers when selecting or editing overdue tasks.
Added a column to the WATPOINTBAL database table as part of resolution for [incidents-list-filtered] and [incidents-list-by-balance] document tags returning no values if the point balance which triggered the action and associated document was being reset.
Resolve issue with punches showing as “Marked as Reviewed” on the Mirror report (Brazilian Data Compliance) not matching the punches shown on the AFDT report (Treated Data Source File).
Resolve slow performance during confirmation of punches that were submitted using the Attestation module.
Resolves the issue that the View VP_PUNCHORIGIN did not have the corerction function code foro Teletime-IP
Resolve issue with the Restore Volume function access control point not making the function available to those whose access profiles had the feature turned on.
Updated stored procedures for the ACJEF and Mirror reports (Brazilian Data Compliance).
Resolve issue with the Generic Data Access Profile report failing to generate in PDF format.
Support for Project View timecard access in Mobile. Adds the TCEDITBYTYPE table, and TCEDITBYTYPEID column to TIMESHEETITEM and PUNCHEVENT.
Resolve issue with volume forecasts not accepting an entry in a foreign currency that was greater than 999,999,999 even if the conversion to dollars was less than that amount.
Resolve issue with the ACJEF report (Brazilian Data Compliance) including
contractual schedule codes on scheduled pay codes.
Resolve issue with the Weekly Rest incorrectly reporting that an employee did not receive the required rest time during a week.
Support for feature that allows users to request one day off using two half day requests.
Resolve issue with the Payroll Preparation Totals report not always showing
correct hour totals.
Reserved for future development.
Resolve issue with the Attendance Incident Tab report showing employees’ database ID numbers instead of the ID numbers that were assigned to them in People Editor. Add a PERSONNUM column to the RWATINCIDENTTAB database table.
Support for Project View timecard access in Mobile.
Resolve issue with accrual reports failing to run for large numbers of employees.
Resolve issue with poor performance when running interfaces after upgrading to the cloud environment.
Schema changes to resolve issue with the Accrual Balances and Projections report failing to run if included employees had currency assignments.
Resolve run-time error when a user opened the Employee Hours By Day (Spreadsheet Export) template.
Resolve issue with the REQUESTSTATUSDSC column of the REQUESTSTATUS database table stating that a manager retracted a time off request when an employee had retracted the request.
Change database schema to support extended user interface translation feature.
Resolve issue with an accrual balance increasing after an employee’s balance is reset and the employee uses some of the hours.
Resolve issue with columns for labor level names in QuickNavs showing the labor level descriptions when time periods not based on pay periods were selected.
Resolved issue related to users not being able to open, edit, or create a Staffing widget after deleting a job code for a job.
Resolve issue with the Location Schedule Detail (Spreadsheet Export) failing to run if a user selected a location that contained sub-locations to include in the report.
Resolve issue with Brazilian Timecard Mirror Report not displaying the employees’ PIS number.
Resolve issue with the RequestSubtype XML API output not including parameter values that were configured for the sub-types.
Support for Workday integration with Time & Attendance. Adds needed global system settings and audit types.
Add a new schedule validation rule in employee rule sets to support operational reporting of fatigue management.
Support for Employee Compliance Call Log.
Resolve issue with duplicate entries in the Comments by Employee and Comments by Location reports.
Support for feature to process time off requests for unscheduled days.
Resolve issue with server coming up in offline mode after upgrading Time & Attendance from 6.3.14 to 7.0.x.
Support for enhancement to the Labor Standards Batch Import XML API for importing data from StandardsPro for Retail to Forecast Manager.
Support for Worked Time Request feature.
Resolve issue with the unsuccessful exports of the Treated Data Source File (AFDT report for Brazilian Data Compliance).
For internal development.
Resolve issues with Brazilian Data Compliance reports.
For internal development.
Reserved for future development.
Resolve issue of backlog of reports in “WAITING” status.
Resolve issue with slow performance of the ACJEF export process (Brazilian Data Compliance).
Update stored procedure to resolve issue with unsuccessful AFDT exports if the NSR number for a punch was similar to another punch from a different device.
Resolve issue with inability to create or edit request sub-types.
Resolve issue with users not being able to generate the Generic Data Access Profile report in PDF format.
Reserved for future development
Resolve issue with the volume forecast not accepting an entry in a foreign currency that was greater than 999,999,999 even if the conversion to dollars was less than that amount.
Resolve issue with the ACJEF report (Brazilian Data Compliance) including contractual schedule codes on scheduled pay codes.
Resolve issue with the Weekly Rest report reporting violations that did not occur.
Modify SP_BRCTreatedDetail stored procedure for Brazilian Compliance to resolve incorrect sequencing of punch records in the AFDT audit file. Applies only to SQL Server.
Both scripts used to resolve incorrect reporting and totals of exceptions in Exceptions reports.
Modify SP_BRCWorkdayControl stored procedure for Brazilian Compliance to resolve incomplete reporting of multiple scheduled breaks in a shift by the ACJEF audit file. Applies only to SQL Server.
Database schema changes to support the Leaderboard feature.
Resolve issue with notifications when user name has more than 64 characters. Allow support for up to 70 characters.
Resolve issue with offline Activities punches at InTouch devices being repeatedly sent to the Time & Attendance database when the system changed to online status.
Resolve issue with duplicate entries being duplicated in LABORACCT database table after clients upgrade to Time & Attendance version 7.0.3.
Database schema changes to restrict pay codes listed for selection to the appropriate pay codes for different request sub-types.
Database schema change to resolve performance issues related to holiday credits and totalization of cascading pay codes.
Reserved for future development.
Support for preventing time off requests from generating pay code edits on public holidays.
Support for automatic approval of time off request cancellations.
Support for enforcing a maximum variance between an employee’s shift and the hours that are allocated to activities for that shift.
Added gold data to the EXTERNALURL table to support project view timecard on mobile devices. Does not include access to timecards on tablets.
Modify RPTSP_Mirrorrpt stored procedure for Brazilian Compliance Mirror Report. Applies only to SQL Server.
Added gold data to the SCHEDINDEXPR and SCHINDEXPROPERMM tables to support budget-adjusted labor forecast metrics indicators.
Resolve issue with the Staffing Sheet - Weekly report showing scheduled shifts on the wrong days of the selected timeframe.
Add a column to the RPTPROCESS database table to resolve issue with storage of uploaded Excel templates when the report server is separate from the Time & Attendance server.
Modify WDMCERTIFICATE database table to resolve issue with failed imports of some authority certificates.
Added index to resolve issue with Activity QuickNavs taking an unacceptably long time to load.
Support upgrade by adding a row in the in the REQUESTSUBTYPEPARMVAL database table. The row contains default values for the GLOBAL_TIME_OFF_EMPLOYEE_SUBMISSION_NOTIFICATION for each REQUESTSUBTYPID.
Add a system user called MONITORINGUSER into the PRSNLICTYPEMM database table.
Modify WDMCERTIFICATE database table to resolve issue with failed imports of some authority certificates.
Create indexes in the ALRTMSGRCVR database table to resolve performance issue with the “Purge Notification Message Records” operation from within Event Manager.
Modification to optimize the database for the gamification functionality. Created indexes in the GAMEEVENT database table for the PERSONID and UPDATEDDTM columns
Resolve issue with DB Manager failing to upgrade a 7.0 Budgeting_Stage database to version 7.0.6.
Add category called “&Point_of_Sale_History” to the WRMDTACATEGORY database table. Resolves the issue of the POSVOLUMEHIST database table being purged even if the configured limit of days in the retention policy had not expired.
Support for enhancement “Assign Breaks” action in Scheduler and Auto-Scheduler.
Resolve issue with slow performance because of multiple connections continuously running queries. Addresses index issue with the FCEVENTFCCATMM database table.
Resolve issue with unusually high CPU load on the database server during
schedule generation. WTK070005022.sql
Resolve issue with employees being able to submit punches from a data collection device for an approved period. Added the following global settings: • global.wdm.dataCollection.allow.transactions.after.manager.timecard.approval • global.wdm.dataCollection.allow.transactions.after.employee.timecard.approval Both settings are set to “true” by default to allow employees to submit punches for days that have been approved by employees or managers.
Resolve issue with TeleTime IP report titles appearing in English regardless of the language used for Time & Attendance.
Add the following global setting to control whether adjacent shifts are allowed in employees’ timecards: global.AdjacentShifts.ScheduleMergeSetting.AllowAdjacentShifts
Reserved for internal use.
Update database schema to support Project and Grant Tracking widget.
Resolve issue with Activities users not being able to access their timecards after Time & Attendance was upgraded from version 7.0.2. Added the SHIFTLOCATORDTM column to the WFAREPACTYSPAN database table.
Support for operational reports enhancements to expose data for: accruals and time detail audits to allow business analysts to create improved Excel reports that suit their needs.
Updated stored procedure to resolve issue with pay codes associated with duration pay codes for auto-resolved exceptions not appearing in the transactions portion of the Employee Transaction and Totals report.
Add new column to WFAPAYCODEACTY database table to support dynamic allocation pay code action feature.
Resolve issue with VP_DATASOURCE query returning no rows if WHERE clause contained FUNCTIONCODE = ‘N’. Added a CASE instruction for FUNCTIONCODE to the query.
Resolve issue with forecast information showing on the Workforce Requirements Analysis report for jobs that were removed and have no hours.
CENG-5676, CENG-6735, CENG-6578
Resolve following issues with the ACJEF audit file of the Brazilian Data Collection kit: • Incorrect reporting of overtime hours • Contractual Schedule record (record type 2) not being populated correctly with a single entry for each unique schedule combination of punches • Incorrect entries for record types 2 and 3, related to no schedule with or without punches for worked hours, and schedules with no hours (for example, pay code edit for time off).
Resolve issue with the AFDT report (part of Brazilian Data Collection kit) showing punch data for two employees instead of only the selected employee.
Resolve issue with the planned number of employees with skills and certification profiles on the Coverage tab in Schedule Planner always showing 0.
Support for clarification of information related to full-time equivalence (FTE) and takings restorations in the Accrual Detail report.
Resolve issue with a manager’s ability to approve his timecard using a group edit not changing when the manager switched roles. Added a column called “DELEGATEID” to the GROUPEDIT database table.
Support resolution to issue of incorrect projected balances in the Accrual Balances and Projection report.
New and updated database tables to support implementation of the Grant and Project Tracking widget for Activities.
Resolve issue with Weekly Labor Recap report taking a long time to run and affecting system performance. Added an index on FCCATEGORY.
Resolve performance issue when thousands of reports are run during a day. Added an index to the RDAILYSCHEDDTL database table, columns PRIMORGJOBID and RPTPROCESSID to speed data retrieval.
Deploy a rewritten version of the accrual_bal_proj stored procedure to resolve issue of incorrect projected balances in the Accrual Balances and Projection report.
Support for Excel-based operational reporting.
Add a setting called “global.NumberToString.RoundingMode” to the Global Values tab to allow clients to choose how “.5” amounts in POS imports should round.
Support for ability of employees using mobile devices to edit unapproved timecards. Associates employee timecard function access control points to employee mobile licenses.
Reserved for future development.
Reserved for future use.
Support for ability to increase the number of custom fields to define. Adds global.customFields.count to Global Values tab in Setup > System Settings.
Support for restricted login feature.
Support for flexible open shift management feature.
Support for contextual menus in the Staffing widget for unit actions and enhanced shift and pay code editing.
Support ability to set time zones for devices with the Brazilian Data Collection interface/setup.
Support for the addition of a system-defined activity form called “Delete Duration Event” (form code 90046).to allow deleting duration events using the XML API.
WTK070004010.sql WTK070004009.sql WTK070004008.sql
Resolve issue of strings appearing in the currency columns in some Excel reports if the system used English/Belgium/Euro for Language/Country/Variant local settings, respectively. • Modify RPTSP_TimeDetailsExcel by adding EMPCURLOCALE from CURRENCYASSIGNMNT table. • Modify RPTSP_WeeklyLaborAccountSched by adding EMPCURLOCALE from CURRENCYASSIGNMNT table • Modify RPTSP_MonthlyLaborAcctSched by adding EMPCURLOCALE from CURRENCYASSIGNMNT table
Schema change to support the 24-hour rule overlap feature. Specifically, implements a new check box on the overtime rule configuration page in Setup.
Resolve issue with some QuickNavs taking an unacceptably long time to load.
Schema changes to support for operational reporting (Excel-based solution for business analysts). Feature addresses the top data requests for Time Detail, Hourly Summary, Scheduling, Employee, and Accruals.
Update stored procedure called RPTSP_TIMEDETAILSEXCEL to resolve issue with pay codes related to historical edits not appearing in the Time Detail (Excel) report.
Update stored procedure called RPTSP_WeeklyStaffingSheet to resolve issue with blank data fields for days and spans in the “Variance” and “Planned” portions of
the Staffing Sheet - Weekly Report.
Reserved for future development
Support for filtering shifts that appear in each staffing unit, based on whether they count toward schedule coverage.
Support for TeleTime IP development.
Support for Activities form duration entry for project view employees.
Change global setting to support for ability to audit changes to system settings.
Add support for issue tracking feature in Task Management.
Change schema related to WFCSERVERROLE for future development.
Update stored procedure RPTSP_WeeklyLaborAccountSched to resolve issue with the Schedule by Labor Account – Weekly (Excel) not showing all data for the selected time period.
Resolve issue with the Generic Data Access Profiles report not generating if the name of the report contained more than 50 characters.
Add a record retention policy to prevent Attendance audit data from being purged by Archiver and Express Archive.
Schema changes as part of the audit feature that allows users to retrieve and review manual changes to system settings for Time & Attendance.
Support ability of the Staffing widget to indicate schedule rule violations.
Reserved for future development.
Update stored procedure called PROCEDURE RPTSP_PersonJobAssignment to improve performance when users generate the Person Job Assignment report.
Update stored procedure called RPTSP_HoursByLaborAccount to resolve incorrect hour amounts on Hours by Labor Account with Chart report.
Add “Activity form entry” option to function access profiles in the Time Entry Employee tree.
Support ability of Kiosk users to have access to all labor accounts.
Modify WDMLANGUAGE database table to support Japanese language translations.
Schema changes to support the Geofencing feature associated with Mobile.
Resolved issue with Integration Manager Interfaces that were scheduled to run automatically not generating reports in HTML format.
Support for employee photographs in the Scheduler widgets.
Support ability of employees to swap their shifts with unposted shifts.
Support “zero-down” re-qualification (ability to remove test data and retain configuration).
Resolve the issue of the Timecard Audit Trail report not generating if a date range and the default audit types were specified.
Insert data related to MONITORINGUSER to support the Application Health Monitoring feature.
Schema change for PREFERENCEPROF table.
Add new index X2_MYWFCIDLIST to enhance performance and scalability of schedule maintenance.
Schema changes to support the Geofencing feature associated with Mobile.
Modify the BIOFINGRSCNTYP and BIOFINGERSCAN database tables to support a new biometrics template type.
Schema change for WFAREPACTYSPAN table.
Remove “Manager Name” custom tag from the Global Time Off workflow notification group.
Modification to Improve support of certificate-based security for data collection devices.
Addition of global system setting named “global.empphoto.enable” to support the Employee Photo feature.
Add global system setting to configure the maximum number of days allowed in date ranges that users specify in the Schedule Planner or Schedule Editor.
Modified the RPTSP_TimeDetails stored procedure to resolve the issue with the Time Detail report not generating.
Deploy the new stored procedure named RPTSP_TimeDetails_Sorted to support sorting of the Time Detail report by primary labor account.
Uninstall data related to Time Detail Sort and Leave Hours Summary Sort reports, when uninstalling the 7.0.2 service pack.
Modified the RPTSP_WeeklyLocScheduleDetail stored procedure to resolve issue with the Location Schedule Detail – Weekly report not sorting employees as expected.
Resolve issue with the Background Processor (BGP) calculating quarterly overtime for random employees incorrectly.
Add support for schedule-to-skill functionality enhancements.
Replace the term “TeleTime IP” in report names in the reports data access profile with "WIVR."
Modify database to allow enhanced Smart Card support at InTouch devices.
Schema change to support new biometrics finger scan device for InTouch device.
Add unique user ID for QuickGlance transactions that are executed at the kiosk.
Resolve issue with the performance of the Employee Transactions and Totals report.
Modify database to accommodate NGUI configuration setting for lateral navigation.
Modified the RPSTP_TimeCardAuditTrail stored procedure to resolve issue with the Timecard Audit Trail report failing to generate for most timeframes and employees.
Add column BIOFINGRSCNTYPID to WDMREGISTRATN database table to support InTouch 2.0 enhancements.
Support for enhanced configuration of grant expirations. Adds new global setting called “global.WtkTotalizer.ExpirationsBasedOnHistoricalDate.”
Resolve issue with some translated text not appearing in non-English language reports.
Add missing foreign key (FK7_0912) information to the KCSDBCOLUMN of the WDMGENERALSETTINGS database table.
Support for alerts and notifications on mobile and tablet devices.
Support for Recurring Projects feature in Task Management.
Support for alerts and notifications on mobile and tablet devices.
Support for feature that allows configuration of short names for valid labor accounts when performing transfers.
Resolve issue with the performance of the Comments by Employee report and the Comments by Location report.
Resolve issue with the BatchJobTask process taking an unacceptably long time to complete and slowing down system performance.
Resolve issue with the VP_ALLPERSONV42 database table view showing the employment term name in the GRPSCHEDNAME column.
Reserved for future development.
Support for the ability to associate holidays with locations. Populates location profiles with list of configured holidays so that they are available to select in the profile configuration screen.
Change RPTSP_TimeDetails stored procedure to correct the calculation of total hours in a combined pay code in the Time Detail report.
Resolve ordering problem with Accrual Detail report. Applies only to SQLServer.
Add function access control point to support ability for managers and employees to perform punch and MobileView operations on mobile devices in offline mode (no connection to the system).
On French instances of Time & Attendance, resolve the issue of the notification messages for approved time off requests containing the English word for the request status (“APPROVED”).
Change RPTSP_TIMEDETAILSEXCEL stored procedure to correct how the Time Detail (Excel) report shows labor account transfers that were created in Schedule Planner.
Known anomaly WFM-38382 If you upgrade from Time & Attendance version 6.2.x or earlier to version 6.3.x or 7.0.x, the system may create duplicate default database connections and XML API connections. These duplicate connections will not affect the execution of any Integration Manager interfaces and links. To eliminate these duplicate connections: 1. Delete all duplicate default connections that the system allows you to delete. 2. Check the configuration (including user name and password) of the remaining default connection for the database and for the XML API, and then test them. Note: This issue does not occur if you upgrade from Time & Attendance version 6.3.x to 7.0.x
Issues Resolved in Service Pack 7.0.9 Within each section, issues are listed in descending, numeric order.
APIs Time & Attendance CENG-14717 If an XML API was used to update or remove an adjustment rule trigger, the import showed a status of “Success” even if the wrong labor account was specified in the request. If the user checked the adjustment rule after the request finished, the user interface correctly showed that the trigger was not updated or changed. Scheduler CENG-14501 The JobPreferences API took an unacceptably long time to import records (Data Integration > Interfaces). Time & Attendance CENG-14175 If an XML API was used to change the wage rate in an adjustment rule, the import showed a status of “Success” but the wage rate was not changed. This issue occurred because the API was not processed to ensure that there was a value for LABOR_ACCOUNT_PATTERN_TO_MATCH. Time & Attendance CENG-13958 The XML API EmploymentTerm Tag ignored the user’s generic access data profile setting that specified how many employment terms to return. For example, if the profile specified to return two employment terms, all terms associated with the manager running the API were returned. This issue did not occur if the manager performed the same operation in the user interface. Time & Attendance CENG-13956 The XML API CascadeProfile Tag ignored the user’s generic access data profile setting that specified how many cascade profiles to return. For example, if the data access profile specified to return two cascade profiles, all profile associated with the manager running the API were returned. This issue did not occur if the manager performed the same operation in the user interface. Scheduler CENG-13698 Users could not delete schedule template assignments using the Schedule API, from a specified date until “Forever.” An error message appeared stating that the request failed and indicated that the specified dates were outside the valid date range. Scheduler CENG-13690 If a user used the XML API to submit a scheduled edit to a pay code for which the “Associate with pay code” option is enabled, and the time value was set to zero, the following error message appeared:
"WFP-01094 A property value is required, but was not specified - Property: AmountInTime." Time & Attendance CENG-12498 If users updated schedule patterns using the XML API, the process took an unacceptably long time to complete. Scheduler CENG-12426 If shifts are imported using the XML API for Auto-Scheduler and one or more of the shifts violates a schedule rule, the import did not run successfully, as expected. However, no error messages appeared and the XML response implied that the import ran successfully. This issue did not occur if the AutoScheduler was run directly using the user interface. Time & Attendance CENG-11122 If users tried to use the XML API to assign badge numbers to personnel who had a manager license but not an employee license, the numbers were assigned with no error message. Sometimes, the badge numbers were correctly not assigned to the personnel, but the import process did not produce an error as expected.
Database CENG-14604 If a client downgraded from Time & Attendance version 8.0.x to version 7.0.x, operational reports could not be generated. The following message is an example of what appeared, using the Employee Hours by Day report as the example: “Error while processing report (Employee Hours by Day (Spreadsheet Export)): com.kronos.wfc.scheduling.reporting.business.excelreporting.beans. ReportFatigueRuleViolationProvider from [Module "deployment.wfc.ear.wfc.war” The solution included updating the script called WTK070008025.sql. CENG-13912 If the execute command for an interface call had more than five variables to pass, the interface appeared to start but remained in the “Running” state. The interface actually never started. This issue occurred whether the Data Integration Interface API or direct XML was used. The solution included the creation of a new script called WTK070009021.sql.
Installation CENG-12380 On application servers running Windows Server 2012 R2, some configuration settings were missing on the Reports tab in Setup > System Configuration > System Settings.
Activities CENG-14684 If employees with default cell assignments in the record (specified in People editor) submitted a form and left the “Cell” field blank, the following error message appeared: “Error: WFA-05036 was not found.” The transaction should automatically use the default cell assignment. CENG-14605 Sometimes when users tried to open a timecard, the following error message appeared: “WTK-03287 Timecard read failed. Please contact your system administrator.” This issue could occur if a shift contained one or more worked durations with 0 hours. CENG-13768 If a manager moved hours in an employee’s timecard from one pay code to another, the Activities tab showed an incorrect number of IDLE hours. Instead of 0, the system showed the sum of the hours moved from the pay code and the hours moved to another pay code. For example, if 8 hours were moved, the IDLE hours result was 16 instead of 0. CENG-13731 If a user navigated between his time card, the Activity Forms Entry or the Event Monitor, and then back to the timecard, the timecard hours format was incorrect. For example, if the user’s display profile is set to show hours in HH.hh format, after navigating back and forth, the hours in the timecard show in HH.mm format. CENG-13666 When a user submitted an Activity Start form with a valid activity name, the following error message still appeared: “Valid Activity required” CENG-13644 The schema file that Interface Designer used did not include the “Paid Break” activity in its Field Definitions list. This issue prevented clients from importing activity profile definitions without having to edit the paid break fields in the user interface after the import. CENG-13532 The Activity Summary did not generate if the user specified a range of dates. The following error message appeared: “Error while processing report (Activity Summary): WFP-01043 Sent a message to the ProduceReport (Server). Expected to see returned. Actually received . Try e-mailing the report using another format, such as doc or rtf. Error Code 4.”
CENG-13368 If a manager edited start and end times of an employee’s activity events so that the activities ended and started at the day divide (adjacent activities), the system created orphan records in the Activity Event Editor. This issue occurred if the employees hours were set to count to the scheduled in day. CENG-13212 The Project/Grant Rollup Daily Totals and Rollup Grant Totals batch job always had the highest priority for execution. If there were other batch jobs that were higher priority for users, there was no way to change the priorities of the jobs. This issue has been resolved by adding the following settings to the Activities tab in Setup > System Configuration > System Settings: •
Use these settings to assign the Rollup Grant Totals and Project/Grant Rollup Daily Totals jobs, respectively, one of the following priorities: Highest, High, Medium, Low, Lowest. The default priority for each setting is “Low.” CENG-12151 Employees’ allocated hours for in the Activities tab and in the Activity Details by Group report did not always match. The solution included the creation of a new script called WTK070009009.sql. CENG-12121 If a user deleted a row in a timecard and the row contained activity spans, the Activity Audit report did not show information about the deletions. The Event Audits tab did show the deletions. The solution included the creation of a new script called WTK070009006.sql. CENG-12116 In Transaction Assistant, when users re-submitted failed transactions, a “WFP-01147” error message appeared stating that value for the property that specifies the activity structure was not valid. However, the activity structure did exist. CENG-11936 The system caused random activity spans to disappear from employees’ timecards. The spans were still in the database. The Audit Events tab did not list actions related to the spans that did not appear in the timecards. CENG-11736 Users could not access Setup > Activities Setup. The following error message appeared: “The HTML Framework has detected an exception in the application that you are attempting to access. The exception has been caught; the application has failed to load. Please contact your system administrator.”
Attendance CENG-14753 If an Ignore Timecard data marker was configured for a future date, when a user ran the Apply Rules function, attendance events were ignored through yesterday. Events were not ignored for the current day. Events should be ignored up until the date of the Ignore Timecard data marker. CENG-14035 The Edit and Delete buttons appeared in My Attendance Editor for users whose assigned function access profiles were configured to not allow those functions. CENG-13753 The [incidents-list-filtered] and [incidents-list-by-balance] document tags would return no values if the point balance which triggered the action and associated document was being reset. The solution included the creation of a new script called WTK070009028.sql. CENG-12980 The Attendance Incident Tab Report did not show the total for a balance type for an employee if the last attendance event for that balance type did not award points. The field was blank. A total should appear for each balance type even if the balance is 0. CENG-12927 The Attendance Incident Tab report did not show system balance resets and adjustments that were due to occur within the time period of the report. This issue prevented employers from obtaining the required supporting information for disciplinary actions. CENG-12923 In Attendance documents, data was not returned for the [incidents-list-by-balance] and [incidents-listfiltered tags. Data was returned for the [incidents-list] tag. CENG-12753 The Apply Rules function in the Attendance Editor did not process attendance events for employees who did not have shifts or schedules in the selected time period. The following error message appeared: “WAT-00015 An unexpected non-SQL system error has occurred.” The error occurred when an employee’s first attendance event is processed. If a user added a shift or schedule for the employee for a day before the event or for the day of the event, the error did not occur.
CENG-12728 If a policy is set to trigger a Lost Time Event when an employee works more hours than scheduled, the system did not trigger the Whole Day Worked Lost Time event. For example, if a shift was 8 hours long and an employee worked 9 hours, the employees worked hours showed as 9. In this example, the employee’s worked hours should not exceed 8. CENG-12458 On the Summary tab in Attendance Editor, balance types for an employee did not always appear depending on the selected date range to review. This issue was related to the system applying resets to balance types incorrectly. CENG-12443 If an employee was subject to a discipline level move and a new profile assignment on the same day, the Summary tab in the Attendance Editor showed confusing discipline level information. Users could not tell which discipline level the employee currently on. CENG-11874 If a pattern in a Perfect Attendance policy was configured to not include Saturdays and Sundays, unexcused absences on those days were still considered part of the attendance pattern. This issue caused the Perfect Attendance policy to disqualify deserving employees from achieving perfect attendance.
Leave CENG-15209 Custom data fields on the “Additional Information” screen in leave cases did not appear in the position order that they were entered by users. Instead, the list reverted to alphabetical order. CENG-14386 If users accessed the employee leave case list using a GoTo widget and then clicked Return, they were not returned to the previous screen. Instead, one of the following screens or messages appeared: •
If using the IIS web server, the “Welcome” screen appeared.
If using single sign-on (SSO), a message stating that “you don’t have permission to access this resource” appeared.
If using the Apache web server, a message stating that the “directory listing is denied” appeared.
CENG-13254 If users split Leave time among days in the “Override Projected Leave Time/Takings” screen, the following error message appeared: “WFL-00094 An unexpected error has occurred” CENG-12670 On the View Leave Case page, the “Committed Paid Leave Time” and “Committed Unpaid Leave Time” did not accurately reflect the committed amounts.
CENG-12667 If an employee had multiple leave cases with the same start date, the Leave Hours Detail report showed only one of the cases. All of the committed time for the multiple leave cases was associated with the listed leave case. Each leave case should be listed separately with its associated committed time. CENG-12431 The system did not show an error message if the taking limit settings in a leave rule for leave case were violated. (Examples of taking limit settings are increments of time for transactions and minimum hours per transaction.)
Time & Attendance CENG-15539 The Time Detail (Spreadsheet Export) report was failing under certain circumstances. The code was modified to fix the problem. CENG-15180 After a client upgraded from Time & Attendance version 7.0.3 to version 7.0.8, the session timeout setting was ignored by Employee Self Service. For example, if the security setting called “site.security.html.ess.global.securityTimeout.Minutes” was set to 25 minutes, the session timed out after one minute had passed. CENG-14994 When employees used the Attestation module to submit punches, it took an unacceptably long time for the punch confirmation page to appear. The solution included the creation of a new script called WTK0800SR014.sql CENG-14953 The punches that showed as “Marked as Reviewed” on the Mirror report (Brazilian Data Compliance) did not match the “Marked as Reviewed” punches in the AFDT report (Treated Data Source File). The solution included the creation of a new script called WTK160189.sql. CENG-14942 CENG-13422 After logging in to Time & Attendance using the Navigator logon, the logon screen appeared again. The solution included the creation of a new script called WTK070009017.sql. CENG-14717 If an XML API was used to update or remove an adjustment rule trigger, the import showed a status of “Success” even if the wrong labor account was specified in the request. If the user checked the adjustment rule after the request finished, the user interface correctly showed that the trigger was not updated or changed.
CENG-14647 The Employee Time Detail (Spreadsheet Excel) report randomly failed to run for selected employees and time periods. CENG-14597 Spreadsheet export reports (for example, Time Detail) showed combined pay codes even though they are configured to be hidden in the reports. This issue did not occur with the corresponding Excel output reports. CENG-14584 A query on the EOUKBAPROPERTYINST database table ran continually and caused excessive CPU load on the database server. This issue caused system performance to become unacceptably slow. The solution included the creation of a new script called WTK070009024.sql. CENG-14566 When users tried to send a report to an e-mail address that contained an apostrophe (‘) before the @ symbol, the following error message appeared: "Please provide a valid email address." CENG-14405 The Employee Transactions and Totals (Excel) report showed duplicate entries in the transactions section of the report. The solution included the creation of a new script called WTK070009023.sql. CENG-14313 If an employee’s schedule contained a pay code that excused an absence and then was absent for a shift and a manager added a pay code edit for the shift that is configured to excuse the absence, the absence exception did not immediately disappear after the manager clicked Save. The manager had to refresh the screen. CENG-14288 The Employee Time Detail (Spreadsheet Export) report showed rounded punch times in the “Actual Start” and “Actual End” columns. CENG-14175 If an XML API was used to change the wage rate in an adjustment rule, the import showed a status of “Success” but the wage rate was not changed. This issue occurred because the API was not processed to ensure that there was a value for LABOR_ACCOUNT_PATTERN_TO_MATCH. CENG-14132 After a client upgraded to Time & Attendance version 6.3.14, use of JBoss memory and the CPU became excessively high and caused system performance to become unacceptably slow.
CENG-14109 At the top of the Function Access Profiles report, there were extra lines of “Allowed” or “Disallowed” settings that did not show the associated access control points. CENG-13958 The XML API EmploymentTerm Tag ignored the user’s generic access data profile setting that specified how many employment terms to return. For example, if the profile specified to return two employment terms, all terms associated with the manager running the API were returned. This issue did not occur if the manager performed the same operation in the user interface. CENG-13956 The XML API CascadeProfile Tag ignored the user’s generic access data profile setting that specified how many cascade profiles to return. For example, if the data access profile specified to return two cascade profiles, all profile associated with the manager running the API were returned. This issue did not occur if the manager performed the same operation in the user interface. CENG-13589 The global system setting: global.securty.external.product.sessionsID.enabled was removed. The database script WTK07009017.sql is associated with this change. CENG-13693 If a user entered a timestamp and refreshed the timecard, an “NGUI-00900” error message appeared. The timestamp was submitted but this was not obvious to users unless they logged out and logged back in again. CENG-13678 Employees were incorrectly paid using their base wage rate in the following scenario: •
The employee was assigned to an adjustment rule that contained one or more wage adjustments that were triggered by working in specific labor accounts.
A manager performed a historical edit with retroactive pay in the employee’s timecard that included a transfer to one of the wage adjustment labor accounts.
The employee was paid for the historical edit hours at the base wage rate instead of the adjusted wage rate. CENG-13653 Sometimes, a seemingly random employee could not access his timecard in Navigator (My Information > My Timecard). An error message containing “TotalBucket cannot be cast” appeared. CENG-13477 If a process template contained an ampersand character (&) and the Time & Attendance instance being used was not called “1,” the following error message appeared when the process form was submitted: “You do not have permission to access the requested resource.”
CENG-13322 When a user selected an employee and tried to open People Editor, the following error message appeared: “Error WFP-00149 The Labor level Entry Name was not found in the database Entry Name: Null DEF ID: Null” CENG-13397 If a user added historical edits and specified that they should not affect totals or accruals, the related hours appeared in the Actual vs. Schedule by Labor Account (Data) for the current pay period. The solution included the creation of a new script called WTK070009014.sql. CENG-13347 Percent allocations calculations in timecards did not produce consistent results for multiple days that contained the same hours or punch information. CENG-13267 If a manager accepted more than two delegation requests for one day, when the manager switched roles for the first time, only the first two delegation requests appeared in the “Switch Roles” drop-down list. CENG-13265 The Brazilian Mirror Report printed in landscape orientation, by default, causing empty space around the information on the page. This issue has been resolved by making portrait orientation the default setting when the report is printed. CENG-13211 Cascading policies with the check box called "Disregard taking limits in accrual policy" selected did not ignore taking limits. Instead of applying hours over the taking limit to the appropriate cascading pay code, the hours went to the pay code defined to hold uncascaded balances. CENG-13159 When a user terminated an employee in People Editor for a day in the future, on that day, the General tab in People Editor correctly showed the employee’s status as “Terminated.” However, the General Information tab showed “Active” status, and the employee was still assigned licenses and an active user account. CENG-13132 Accrual balance amounts changed after timecards were signed off. In some situations, accrual balances were lower than intended. This issue sometimes resulted in expiring grants changing to a negative balance. CENG-13102 If a client had configured a Location Schedule Detail (Spreadsheet Export) report as a favorite, and then tried to upgrade to Time & Attendance version 8.0.x, one of the database upgrade scripts failed to execute properly. The solution included the modification of the script called WTK070008021.sql.
CENG-13067 The “Planned Taking” column in Accrual QuickNavs showed twice the number of hours that were actually being taken for the selected records. CENG-13035 When users specified a relative range of dates for a report and saved the report as a favorite, the relative start date reverted to the default setting of “Days Before Run Date.” This prevented users from saving a report as a favorite that began reporting on a number of days after the run date. CENG-12982 Employees could not approve their timecards unless their function access profiles allowed them to edit punches. CENG-12973 During peak scheduling period, the database server experienced unexpectedly high input/output activity that caused performance to become unacceptably slow. CENG-12962 If the day divide in an employee’s fixed rule was 11:59 p.m. and workflow notifications were set for that time, the notifications were sent 24 hours later. CENG-12951 HyperFind query results were not always accurate. For example, a query to return all employees who were assigned to a specific accrual profile returned a correct result of 10 employees. If the query were changed to search for the employees in that group that had earned a specific number of accrual hours, the number of employees returned was higher than 10. CENG-12906 The Holiday Profile Editor took an unacceptably long time to process edits made to holiday profiles. CENG-12810 When users tried to run the Accruals (Spreadsheet Export) report for any HyperFind query, the following error message appeared: “Error while processing report (Accruals (Spreadsheet Export)): null Error Code 101” CENG-12802 The following error message appeared if employees tried to run the Employee Timecard Audit report for a period in which a pay code edit start time was removed: "WFP-01050 Invalid time format - Time = ." CENG-12764 After a manager seemingly deleted an employee, the employee still appeared in QuickNavs and was included in the results of database queries. The solution included the creation of a new script called WTK070009007.sql.
CENG-12747 The Punch Origin report for a current timecard or current pay period did not show information in the “Data Source” field for all punches in the report. CENG-12742 Sometimes, the Time Detail (Excel) report showed some hours worked by employees for transfer shifts as being charged to their home accounts instead of to the transfer accounts. The solution included the creation of a new script called WTK070009004.sql. CENG-12727 If a punch was reviewed by a manager, the Punch Origin report showed the user name as that manager instead of the original user who entered the punches. CENG-12680 Accrual balances shown in the Accrual tab of the timecard and in the Accrual Detail report did not match. The solution included the creation of a new script called WTK070009016.sql. CENG-12643 When employees were assigned an employment term that included an accrual profile, the accrual profile name and ID was not populated in the database. This issue did not occur if employees were assigned an accrual profile directly in People Editor instead of through and employment term. CENG-12624 The Background Processor (BGP) did not always correctly calculate the number of hours employees should receive on statutory holidays. CENG-12498 If users updated schedule patterns using the XML API, the process took an unacceptably long time to complete. CENG-12446 When users generated a report, the Check Report Status screen did not automatically appear as expected. The user had to click the Check Report Status tab. CENG-12416 If the override shift option was used with duration pay codes on a full contract day, the resulting in and out punches for the duration were incorrect. The punch used the start and end times of the employee’s shift instead of start and end times of the contract. CENG-12408 With Time & Attendance systems that use SSL, if a user clicked the “Forgot Your Password?” link and then canceled from the Security Question screen, they were directed to a non-SSL URL. Because the system requires SSL communication, the message “This page cannot be displayed” appeared.
CENG-12308 If an employee was absent for a shift and a manager added a pay code edit for the shift that is configured to excuse the absence, the absence exception remained. CENG-12303 When an accrual balance for an employee reached 0, the following error message appeared: “WTK-03285 FPO balance on is -0.00 (Overdrawn by 0.00). Maximum overdraw is 0.00” CENG-12249 Managers who have a French Canadian locale policy and log in to a French instance of Time & Attendance see an invalid date error message when they try to run a report from within a wizard. CENG-12236 Sometimes, new employees did not import successfully if they were being assigned to certain pay rules. The failed record was moved to Transaction Assistant. If the user re-submitted the transaction from Transaction Assistant, the submission was successful. CENG-12227 The following reports failed to generate: •
Employee Time Detail (Spreadsheet Export)
Time Detail (Spreadsheet Export)
Employee Hours by Time Frame. (Spreadsheet Export)
The following error message appeared: “WTK-98014 Unknown error found during the process of timecard excel report. Error Code 101 while running Employee Time Detail (Spreadsheet Export).” CENG-12060 If a user ran the Employee Hours by Day (Spreadsheet Export) operational report and multiple employees included in the report had the same name, the Combined Data tab in the report showed the same value in the Person Number column. This issue has been resolved to modify how the report looks up the employees for the reports. The modification has also been applied to the following operation reports: •
Employee Time Detail (Spreadsheet Export)
Employee Hours By Time Frame (Spreadsheet Export)
Time Detail (Spreadsheet Export)
Comprehensive Audit Report (Spreadsheet Export)
The solution included the creation of a new script called WTK070009003.sql. CENG-12026 The system did not apply overtime correctly when an overtime counter was configured to reset at the start of a new shift. This issue occurred if a shift contained a span defined by in and out punches, followed by a duration pay code edit that began at the time of the out-punch. If the total number of hours exceeded the overtime limit (point at which overtime should begin), no overtime was applied.
– An employee should earn overtime for hours worked beyond 8 hours during a shift. – If the employee works another shift on the same day, the overtime counter resets to 0. An employee punched in at 2:00 p.m. and punched out at 7:00 p.m.
A duration pay code edit for 4 hours was applied at 7:00 p.m.
Although the total hours was 9, all hours were paid as regular hours. CENG-12014 When users attempted to punch in using My Timestamp feature through the Attestation module, the punch failed and the following error message appeared: “WFP-00941 the field string value is too long Field Name: ClientName, Max Length: 50” CENG-12012 Users could not approve canceled time off requests that occurred on a holiday or within a range of dates that spanned a holiday. The following error message appeared: “WTK-08149 Cannot process the request. Check the log for more information.” CENG-11995 Managers could not submit time off request for employees in the following scenario: •
A manager delegated authority to an employee who reported to him.
The delegated employee was also a manager.
The delegated employee could not submit time off requests in the delegated role. CENG-11982 Translated text strings in the Translation Support spreadsheet did not always map correctly to the user interface. For example, the name of a work rule in the timecard of an English instance of Time & Attendance was correct. However, the wrong translated string was used in the French instance of Time & Attendance. CENG-11955 When users generate the Employee Time Detail (Spreadsheet Export) report, the report did not open the first tab by default, as expected. Instead, the report opened the last tab. The solution included the creation of a new script called WTK070009008.sql. CENG-11930 The Employee Hours by Day (Spreadsheet Export) report showed a tab called “Stuff.” CENG-11898 The punches that showed as “Marked as Reviewed” on the Mirror report (Brazilian Data Compliance) did not match the “Marked as Reviewed” punches in the AFDT report (Treated Data Source File). The solution included the creation of a new script called WTK070009010.sql.
CENG-11827 Some work rule transfers in the time card did not appear in the Time Detail (Spreadsheet Export) or the Employee Time Detail (Spreadsheet Export) reports. CENG-11772 If managers edited an accrual policy that contained one or more pay codes to which they did not have access, when the edits were saved, those pay codes were removed from the accrual policy configuration. CENG-11754 Users could not easily edit form fields in some transactions that used a process template (for example, Time Off Request). This issue occurred if the user entered an amount of text in field that caused a scroll bar to appear. When the user tried to select a portion of the text to edit, the entire text scrolled to the top and all text was selected. CENG-11747 If multiple languages of Time & Attendance were used, when users updated timecards, a “WFP-01050” error condition occurs with some of the languages. This issue seemed to occur when pre-defined options such as “full contract day” were involved in the edits. CENG-11708 The “Planned Taking” column in Accrual QuickNavs showed twice the number of hours that were actually being taken for the selected records. CENG-11703 When a manager viewed an exception alert that used a sub-category for the time period “Yesterday,” the correct exception appeared, but the date incorrectly showed as two days ago. CENG-11700 Even if users had access rights to perform transfers, when they tried to edit or add comments to punches with transfers, the following error message appeared: “WTK-03300 Access right violation: labor account transfers are not allowed.“ CENG-11687 When decimal hour amounts were imported using the EmployeeStandardHours XML API, they did not always convert and round correctly to an hours:minutes value. For example, if the amount 31.33 was imported as the EmployeeStandardHours value, it appeared as 31:19 in the person record. The amount should round to 31:20. CENG-11451 An error condition occurred in the following scenario: •
An employee submitted a request for time off that was based on a request sub-type and placed a pay code for 0 hours in the schedule.
A manager accessed the schedule through the Schedule QuickNav and tried to make a valid edit to the pay code amount.
The following error message appeared:
“WFP-00986 An unexpected error has occurred. Please contact your System Administrator.” CENG-11390 Users could not perform a “file import from server” operation with Process Manager. The following error message appeared: "The following error occurred while retrieving the remote process: class ‘com.dralasoft.workflow.RemoteKDefaultworkfowImpl_Stub’’s’ Signer Information Does Not Match Signer Information of Other Classes in the Same Package." CENG-11122 If users tried to use the XML API to assign badge numbers to personnel who had a manager license but not an employee license, the numbers were assigned with no error message. Sometimes, the badge numbers were correctly not assigned to the personnel, but the import process did not produce an error as expected. CENG-11020 A manager tried to enter a historical edit with retroactive pay to transfer hours from one labor account to another, the following error message appeared: “EP-00356 Could not find the work rule name in the database...” The error contained the name of one of the labor accounts the manager selected for transferring hours. The name was not the name of work rule as the error message indicated. CENG-10762 For Chrome browser version 40.0.2214.115, users could not assign dates to static drivers in the following areas of Forecaster: •
Setup > Forecaster Setup > Labor Drivers > Select Assign Static Drivers.
Setup > Forecaster Setup > Special Events > Assign Special Events
Setup > Forecaster Setup > Hours of Operation > Create Override Hours
CENG-10722 In People Editor, sometimes when users tried to save edits to employee groups, the save operation failed and a “Null” message appeared. CENG-10716 After a client upgraded to Time & Attendance version 8.0.x, users could not open, edit, or delete HyperFind queries that contained a full-time equivalency condition. A “Null Error” message appeared. This issue also occurred if users tried to use the HyperFind query to return information in a QuickNav. The solution included the creation of a new script called WTK070009013.sql.
CENG-10705 If clients used Internet Explorer versions 10 or 11 with Compatibility Mode turned off, Project Timecard single link widgets had an unnecessary vertical scroll bar which obscured the data in the “Total” column. The presence of the scroll bar required users to scroll horizontally to see the data in the “Total” column. CENG-10357 When users tried to generate the Accruals (Spreadsheet Export) report for all home employees, the report failed and the error message “NULL Error Code 101” appeared. CENG-9512 An error condition occurred in the following scenario: •
Employees were assigned a percent allocation that spread worked hours across multiple labor accounts.
The system was configured so that employees were required to take accrued hours in amounts that were divisible by a specific increment of time (for example, 15 minutes).
Hours were spread across multiple accounts in amounts that were not divisible by the required increment. For example, a labor account received 2.8 hours which is not evenly divisible by .25 hours (15 minutes).
The following error message appeared a number of times equal to the number of allocations to labor accounts that were not divisible by the increment: ‘WTK-03285 This edit cannot be made. PTO edits must be in increments of...” This issue has been resolved so that the requirement that hours be divisible by the specified increment of time applies only to the total number of hours, as expected — not to the individual amounts allocated to labor accounts. CENG-7858 At sites where employees used processes that incorporate timer (reminder) tasks (for example, generic time off requests), Process Manager did not execute the timer tasks. CENG-9925 The attribute VisibleToReports now displays appropriately in reports. Pay codes only appear when attribute Visible in Reports is enabled. This option is used to show pay codes in reports, such as Time Detail. When the opton is selected for the reports, only the pay codes with the field selected will be included in the results.
Integration Manager CENG-14635 If the global setting global.knx.engine.UseBatchProcessingFramework was set to “true,” all interfaces in the queue showed a “Running” state even if some of the interfaces were not running. Interfaces that were not running should show a “Waiting” state. CENG-13552 When users tried to run an interface for the Request Reviewer List API, the interface took an unacceptably long time to complete. CENG-13531 When a user attempts to deploy an interface that contains a link that has the Output Type: Lookup Table, and if the lookup table name has a variable substitution string in the middle of the table name, Interface Designer will display an error message and will not deploy the interface. CENG-13526 For clients in a US locale who did not use the HH:mm duration format, accrual totals extracted by WIM were sometimes incorrect because fractional minutes were truncated. This issue did not occur if the AccrualData XML API was used to extract accrual amounts. CENG-12861 After upgrading to Integration Manager 7.0.x or a higher version, performance of the interfaces was unacceptably slow. CENG-11965 The time it takes a “FULL ViewToFlatFile” interface that pulls large amounts of data including punches, labor transfers, and timecard edits takes longer each day it is run. If the application server was re-started, the amount of time for the interface to run was reduced; however, the interface again took longer to run on each subsequent day. CENG-10810 The Labor Account Set API takes a considerably longer time to perform employee group set updates than level transfer set updates for the same number of records. CENG-10445 Interfaces that contain two links that perform lookups, If one of the links uses a variable for the comparison, the double lookup fails. The following error message appears: WIM-05145 Record# 1: ":EMPLOYEE TYPE". Predefined Error Message: WIM-05002 Record# 1, "" not found in table SALARY.TBL for [:EMPLOYEE TYPE] If the lookups use a transfer from source instead of a variable to perform the comparison, the interface completes successfully.
Scheduler CENG-6384 The Navigator Widget for Self-Scheduling now behaves similarly to teh classic inteface. Shifts now appear in the Transfer area for the Self-Scheduler when the request subtype is configured to use a Shift Template. CENG-15198 Requests for time off were not processed correctly in the following scenario: •
The employee had a contract that should be used as a “fallback” for time off requests.
The employee submitted a request for a date with no schedule.
The employee’s manager approved the time off request using Request Manager.
The date with no schedule was not populated with a time off. If the manager approved the request using the classic schedule editor, the request was correctly applied. CENG-15027 Sometimes, when a user ran the RetrieveWithAll XML API to return information about employees, the response included employees that were not specified in the API request. CENG-14969 The Priority Scheduling Engine assigned shifts to employees for days that the employees were not active. CENG-14881 The process of approving a cancelled time off request did not work as expected in the following scenario: •
An employee requested time off for multiple consecutive days.
A manager approved the request.
The employee cancelled the request for time off.
The manager approved the cancellation without selecting the full date range of the request.
The request days that were not part of the selected date range when the manager approved the cancellation still had the time off request pay code assigned. The shifts for those days were restored. CENG-14747 The Priority Scheduling Engine did not schedule shifts if the user specified a custom sort on location and selected the check box called "Remove all items that do not correspond to the custom sort." If the user did not select the check box, the Priority Scheduling Engine scheduled shifts but not exclusively for the locations in the custom sort. CENG-14728 The Schedule QuickNav allowed more than the configured maximum number of employees allowed to be returned. (The maximum number of employees that can appear is configured using the global setting called “global.LongList.ScheduleSummaryEmployeeThreshold.”) CENG-14533 After a client upgraded from Time & Attendance version 6.1.x to version 7.0.x, open shift rows appeared for jobs when there were no open shifts in Schedule Planner.
CENG-14501 The JobPreferences API took an unacceptably long time to import records (Data Integration > Interfaces). CENG-14431 If the global time off request feature was configured with the Message Center capability, the re-direct URL in the messages that were sent to managers did not show the request submissions for the request period. Managers had to click Refresh to cause the list to appear. CENG-14351 Users could not create an availability pattern for a time period longer than 365 days. A message stating that the date range is invalid appeared. CENG-14300 Employees could not see comments or notes that managers added to requests to change availability in the Employee Self Scheduling calendar. CENG-14253 Half-day boundary rules for global time off requests were being applied to shifts created by templates to which the boundary rules were not assigned. Example •
A boundary rule of three hours was assigned to a shift template called “Shift Template 1.”
A global time off request was associated with an 8-hour shift that was not based on “Shift Template 1.”
The 3-hour boundary rule was applied to the shift and caused the half-day to be defined as three hours instead of four hours for that shift. CENG-14123 Using the Schedule XML API to update employment terms took an unacceptably long time to complete. CENG-14039 In the Weekly Staffing Sheet, the “x” next to an employee’s name whose shift was a transfer was obscured if the employee’s name was long enough to fill the column width. The “x” indicates a transfer shift and needs to be clearly visible. CENG-14431 Global Time Off requests displayed incorrect information for the selected time period causing the user to refresh to see the correct display. This issue was corrected to enable access to the correct information without using the refresh. CENG-13747 When some managers used the “Export to Excel” function in a Schedule Planner QuickNav, the “Shift and Pay Code Edits” tab was not included in the output. Only the “Workload” tab was included.
CENG-13698 Users could not delete schedule template assignments using the Schedule API, from a specified date until “Forever.” An error message appeared stating that the request failed and indicated that the specified dates were outside the valid date range. CENG-13690 If a user used the XML API to submit a scheduled edit to a pay code for which the “Associate with pay code” option is enabled, and the time value was set to zero, the following error message appeared: "WFP-01094 A property value is required, but was not specified - Property: AmountInTime." CENG-13634 In Schedule Planner, if a user selected the Rule Violations tab and then clicked Refresh, the rule violation icons disappear. CENG-13557 In Schedule Planner, if a user created a schedule with a future start day that was one less than the configured maximum number of days, rule violations appeared for the employee being scheduled. Note:The maximum number of days is determined by the following system setting: com.kronos.wfc.scheduling.fatiguemanagement. ruleevaluation.EXTENDED_HORIZON_IN_DAYS For example, if the value for the setting was “20” and the user selected a start date that was 19 days from the current date, a rule violation appeared on the Rule Violations tab.The following error message appeared: “Workset Rule evaluation encountered an unexpected application error when scheduling.” CENG-13515 If a user generated a Location Schedule Coverage report for a 6-week timeframe, header information was missing from random pages. This issue made the report hard to follow from page to page. CENG-13401 Managers could not approve availability requests in Request Manager. When they selected a request and clicked “Approve,” the following error message appeared: “WFP-00930 cannot insert an object that already exists in the database.” CENG-13320 Using the My Requests single link widget, if a user submitted a time off request for a date and time that already has a request submission, the request was entered as a draft with no message to explain why. In this scenario, the request should be rejected with the following error message: “Your request conflicts with a previously submitted request. Please check the request information and resubmit.”
CENG-13312 In Schedule Planner, the value for Hours per Volume Tab > Actual Hours was incorrect when users selected a multiple day view and edited the schedule. This issue did not occur if the user viewed a single day. CENG-13235 When managers tried to run a Location Schedule Detail Weekly report to include posted schedules, the report failed and the following error message appeared: "WFP-00895 Posted data is not available for time frame.” CENG-13130 If a manager tried to send open shift requests to employees in an earlier time zone, the request failed in the following scenario: •
The Time & Attendance application server and the manager was in a later time zone than the zone in which employees who were to receive the request worked.
The start time of the open shift had passed in the later time zone.
The following error message appeared: "You may only contact employees for an open shift in the future.” Example: •
The Time & Attendance application server was in the Eastern time zone of the United States.
The employees to whom the request was to be sent were in the Pacific time zone of the United States (three hours behind the Eastern time zone).
The start time of the open shift was 9:00 a.m. Eastern time.
The manager tried to send the open shift request at 9:30 a.m. Eastern time.
The error message occurred because the system referenced the Eastern time and determined that the open shift had already started. CENG-13062 Users with function access profiles that were set to not allow them to create and edit schedule zone categories (Scheduler Setup > Zone Categories > Edit) were still able to access the function. CENG-12958 In Schedule Planner, when some managers tried to export schedules to Excel format using the “All Home Locations” selection, the resulting output was blank. CENG-12938 If an employee had a transfer in the first part of a shift, that employee was not included in the relevant zone within the All Zone report. The solution included the creation of a new script called WTK070009005.sql. The Quick Fill Details Report has cuplicate entries for each shift offered.
CENG-12831 Employees who submitted half-day time off requests sometimes had their days split incorrectly in the following scenario: •
The system contained multiple half-day rules with the same shift start and end times.
Each half-day rule was configured to split the day differently.
If an employee who was assigned to one of the half-day rules submitted a half-day time off request, sometimes the day was split based on another rule with the same start and end times. CENG-12722 If managers whose assigned display profiles were configured to show durations in decimal format generated the Schedule by Labor Account - Monthly report, durations showed in HH:mm format. CENG-12710 Managers whose function access profiles disallowed access to wage information could see the wage information in the Metrics tab of Schedule Planner. CENG-12703 If the accrual taking limit was set to five days and an employee submitted a time off request for six or more days, the following error message appeared: “This edit cannot be made. The maximum taking limit for RO Relocation is 5:00. The maximum taking limit for RO Relocation is 5:00. “ The error message is accurate, but information in the message needlessly appeared twice. CENG-12507 In the Employee Weekly Schedule report, long location paths of primary jobs were truncated in the “Job” column instead of wrapping to another line. CENG-12483 In Schedule Planner, when a manager approved an open shift request, the coverage count incremented by two instead of one. The coverage count remains incorrect until the screen is refreshed. This issue caused managers to think that coverage for shifts was sufficient when there was not enough coverage. CENG-12426 If shifts are imported using the XML API for Auto-Scheduler and one or more of the shifts violates a schedule rule, the import did not run successfully, as expected. However, no error messages appeared and the XML response implied that the import ran successfully. This issue did not occur if the AutoScheduler was run directly using the user interface. CENG-12410 Sometimes, while users created, edited, or duplicated request sub-types in Setup > Employee Self Service > Request Subtypes, the system became unresponsive.
CENG-12378 Users could not delete a global time off request that had been in a “Suspended” state and then changed to “Draft” state. The following error message appeared: "SQL Statement failed (may be caused by network or database issues). Please contact your system administrator. the system log file may have more detailed information." CENG-12343 When users accessed the Schedule Editor for “All Home” employees, the Request tab showed all requests without regard to the selected time period. CENG-12287 In the Request Manager widget, managers were not able to see scheduling requests to cover for the previous request period. If a manager selected a specific day, he could see scheduling requests to cover for that day. CENG-12255 In Workload Planner, if multiple managers were simultaneously editing Skills and Certifications patterns for different locations, a “WFP-00986” error appeared for some of the managers. This issue prevented the edits from being saved. CENG-12241 If a user submitted a time off request for which the sub-type was configured with an "External Action" for a transition from “Draft” to “Submitted” status, and accrual validation generated a warning, the warning was not always visible to the user. This issue has been resolved so that the warning will be sent to the user’s Inbox or e-mail. CENG-12161 If employees submitted time off requests for dates that were after the latest date that had been populated with shifts by the Shift Builder, the following error message appeared: “The schedule data has not been populated for the selected range of dates; the schedule is read-only. If you need to edit the schedule for this range of dates, contact your system administrator." However, the requests were submitted and became idle. Managers could not approve or reject the requests. This issue has been resolved by preventing time off requests for dates beyond the latest date populated by the Shift Builder from being submitted. CENG-12086 Fatigue Management rule violations were triggered even if no violation occurred based on the defined work sets. CENG-12052 The IS Summary QuickNav did not show schedule group assignments for some employees if the HyperFind query that was used returned a large number of employees who belonged to multiple schedule groups.
CENG-11990 If a user updated the site.local.LONG_DATE setting to dd/M/yyyy format and then tried to access an open shift from Schedule Alerts, a Java error condition occurred. The error message was “Error. Click for details,” followed by detailed Java-related log information. CENG-11846 The RequestMgmt API did not ignore rule violations even if the setting called “global.WTKScheduler.notifyWarningRuleViolations” was set to “false.” Error messages were generated. This issue prevented users from using the API to cancel approvals for time off requests. Rule violations were correctly ignored if users cancelled approvals using the user interface. CENG-11760 In Schedule Planner, if multiple employees with the same start time were assigned a zero hours pay code to their shifts, hover text for the pay code in the By Job tab did not list all of the employees. Only the name of the last employee in the list appeared. CENG-11745 In Schedule Planner, inactive Skills and Certification profiles appeared in the drop-down list on the Coverage tabs. Inactive profiles should not appear as selections. CENG-11474 When a user who did not have access to the default Schedule Planner selected the Availability Quick Link from Work and Absence Summary calendar, the following error message appeared: “WFP-00805 a Generic Error was detected.” CENG-11465 The Person Details (Spreadsheet Export) report did not include an “Additional Information” column for information such as maiden name and contact information. This type of information should be included in this report. The solution included the creation of a new script called WTK070009001.sql. CENG-11308 In the Request Manager widget, managers could request time off for an employee for a period that was outside of the employee’s configured request period. If the employee requested time off using My Requests, the system correctly prevented requests outside of the request period. CENG-10837 If users entered a date with slashes when requesting time off but the date format was incorrect, an error message appeared. However, in the error message, Unicode characters appeared instead of the slashes in the date.
CENG-9167 If a user accessed the Open Shifts widget and then navigated to Schedule Planner using a Quick Link, the following message appeared: “WFP-00986 An unexpected error has occurred.” If the user clicked OK in the message and selected “All Home Locations,” data appeared in Schedule Planner. CENG-7569 When using the XML API to perform a schedule import, the shift label property was not exposed. “ShiftLabel” is now available in the API when “ShiftCodeName” is not used.
Budgeting (formerly “Operations Planner”) CENG-14236 Sometimes, when users ran a fiscal labor budget import, the following error message appeared even though all of the cells of information being imported contained values: “WTK-97843 You cannot edit a cell with a value N/A.” CENG-13371 Sometimes, when custom driver values were updated in Forecaster, the corresponding values were not automatically updated in Budgeting. This issue occurred even if the following system setting was set to “false”: “site.budgeting.BudgetEngines.useConsolidatedFiscalCustomDriverData” CENG-13364 When users ran a Budgeting Labor Plan, the following message appeared: “You cannot load a labor plan for until the system has finished generating the Labor forecast. Wait and try again when the Labor forecast is complete.” The plan remained in a running state and never completed. CENG-12619 Custom driver values in Forecaster did not match the corresponding results in Budgeting even if the following system setting was set to “false”: site.budgeting.BudgetEngines.useConsolidatedFiscalCustomDriverData Note: The system setting specifies the source for custom driver data.
Forecast Manager CENG-14959 The function access control point for the Restore Volume function did not make the function available for users whose function access profile had the feature turned on.
The solution included the creation of a new script called WTK070009032.sql. CENG-14957 In Forecast Planner, when a user selected a category and clicked Restore Volume, volume was restored for other categories. This issue has been resolved by controlling access to the “Restore Volume function in the function access profile. The access control point is called “Restore Volume” and is located in the following path in the function access profile: Time Manager-Department Manger - Forecasting - Forecast Planner If the setting is set to “Disallowed,” the user does not have access to this function. CENG-13818 CENG-12478 In Forecast Planner, when a user selected a category and clicked Restore Volume, volume was restored for other categories. This issue has been resolved by controlling access to the “Restore Volume function in the function access profile. The access control point is called “Restore Volume” and is located in the following path in the function access profile: Time Manager-Department Manger - Forecasting - Forecast Planner If the setting is set to “Disallowed,” the user does not have access to this function. CENG-12398 Labor forecasts that were run at the department level did not include volume-driven labor that came from a different department. Labor was generated only for the opening and closing labor standards that were associated specifically to the department. CENG-12257 Setup Data Manager (SDM) did not transfer any special events associated with a Forecaster node that were for a date that was before the effective date of the node. CENG-11676 In the user interface, the labor forecast totals for some stores did not always match the values in the LABFORECASTTOT database table. CENG-11640 n the Productivity Monitor the planned hours for Sunday through to Saturday were not displayed correctly. When the planned shift included hours worked over the day divide every day, Saturday hours from 0:00 to 3:30 were not being included in Sunday’s totals
Task Management CENG-13800 If a manager selected a project in Project Monitor, the following error message appeared:
“Unexpected Error Occurred. Please contact your administrator.”
Navigator CENG-14200 The Self Scheduling request sub-type allowed scheduling beyond the needed coverage even if the option “Allow overcoverage” is not selected in the sub-type configuration. CENG-14056 If an employee whose People record specified a “Reports To” manager submitted a time off request, the resulting alert appeared in the “Time Off Alert category” and the “Uncategorized” category. The alert should not appear in the “Uncategorized” category. CENG-12911 If an employee submitted a time off request with a duration or symbolic amount and specified multiple time periods, the Detail tab of the Request Manager widget showed conflicting information. For example, a time off request of 3.5 hours for 6/12/2015 and 6/13/2015 in multiple time periods was indicated in the Detail tab as “ - 3:00 Hours Training Start Time 8:00AM (Length3:30 Hours)” CENG-12846 In Navigator, employees could select transfer jobs that were not included in their job transfer sets as assigned in People Editor. CENG-12822 In Navigator, when a user selected employees and tried to access timecards from the Related Items list, the following message appeared: “WFP-83465 Invalid request. A valid Person Database Key must be provided in order to enter the Timecard.” CENG-12784 In Navigator, the “Back to” text of the link to return to a workspace from the QuickFind widget did not appear in the language of the Time & Attendance instance the user was logged in to. For example, if the user was logged on to a French instance, the “Back to” text appeared in English instead of French. CENG-12712 In the Timecard widget, when an employee selected and approved one day, the entire pay period was no longer editable (as if all days were approved). The employee could select another day in the pay period using the “Time Period” field, and the day was editable (not approved).
CENG-12665 In the Exceptions widget, managers could not add a pay code to a shift that already had a scheduled pay code. Managers could not add pay codes to override the scheduled pay code (for example, to excuse an absence). In this scenario, managers could add a pay code using the timecard. CENG-12409 Sometimes if users logged in to Navigator and their workspace contained the Timestamp widget as a secondary widget, the last timestamp did not appear. This issue was related to either the monitor resolution setting or using the browser in window mode. CENG-12394 In the Exceptions widget, when a user clicked View Details for selected employees and then clicked Show Schedule, schedules showed for some employees and not for others who also had schedules. CENG-12057 In Navigator, after a manager approved a time off request that contained notes entered by the employee, the employee ID associated with the notes was changed to the approving manager's ID. This issue did not occur if the time off request was approved using the classic user interface. CENG-11880 Accrual balances were not updated correctly when employees selected days to view in the Calendar widget. This issue allowed employees to request time off even if they had used up their accrued time. CENG-11698 In Navigator, when users with employee and manager licenses tried to schedule themselves using Employee Self Service, shifts associated with manager shift templates appeared instead of employee shifts. If the user tried to submit a shift, the following error message appeared: “WTK-97522 - The Selected Shift Template is not available for your login profile.” CENG-11591 If an employee cancelled a time off request that had been automatically approved, the employee’s manager received duplicate e-mail alert messages about the cancellation. CENG-11436 If a user selected employees in Schedule Planner and then used the GoTo navigation to navigate to the Schedule view, no employees appeared in the view. The number of employees selected did appear on the screen.
Device Manager CENG-13835 When users tried to access Device Manager Setup > Device Totals, a “system null” error message appeared. This issue occurred was related to combined pay codes not being fully supported.
CENG-12496 When using Setup Data Manager (SDM) to transfer device transaction settings from Device Manager, an error occurs if a short name was used for labor accounts. The name was valid, but the following error message appeared: “WFP-00950 The value is not valid for the property - Name: JOBDEFAULTVALIDACCOUNTNAME, Value: . CENG-12111 When navigating to the device page, if there were multiple pages of devices and a user selected a device on a page other than page 1, and then pressed the Back button, page 1 appeared. This issue has been resolved so that the Back button always takes users back to the page they were on. CENG-11925 If a user entered search criteria in a Search field and pressed Enter, the search did not execute because focus was not on the search icon. The user had to click the search icon. The field no longer cleared when the Enter key is pressed.
QuickGlance CENG-13991 If an employee tried to cancel a time off request at InTouch devices using Chinese, an error condition occurred after selecting the start and end dates of the request. The employee could not complete the transaction.
TeleTime IP CENG-14624 When employees used TeleTime IP to inquire about accrual balances, the balances were always reported in decimal format. If the employees’ timecards showed amounts in hours:minutes, it was difficult to quickly determine if the amounts matched. CENG-14053 The Communication Hub did not load labor level entries or sets to TeleTime IP. This issue prevented users from entering labor level transfers with TeleTime IP. CENG-13205 When users tried to download (manual or scheduled) information to TellIris through the communication hub, labor level entries under certain conditions were not included in the download.
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, Inc. Web page: http://www.adp.com