Beruflich Dokumente
Kultur Dokumente
Products
Version 2011.1
Release Notes
TABLE OF CONTENTS
Introduction..........................................................................................................................1
In this document......................................................................................................................... 1
Workforce Management Enhancements.......................................................................... 2
Introduction..........................................................................................................................2
In this section ............................................................................................................................. 2
040111
Page i
TABLE OF CONTENTS
Introduction........................................................................................................................11
In this section ........................................................................................................................... 11
Page ii
040111
RELEASE NOTES
Release Notes
Introduction
This document provides an overview of the enhancements available in the
RedPrairie supply chain execution workforce management products (WFM) for
the 2011.1 release.
In this
document
Section
Page
11
040111
Page 1
RELEASE NOTES
In this section
Page 2
Topic
Page
General Enhancements
10
040111
RELEASE NOTES
With the addition of the Consolidated User Report, Workforce Management lets you
view up to six standard reports for a user or for multiple users. (When you run this
report for more than one user, the resulting information is appended one after
another.) You can view these reports:
Summary Report
Quality Report
You can select which reports to generate in the final output. For example, you can
select to show only the Report Card Report and the User Milestone Report. For each
report that is selected, you can use selection criteria to refine what is generated in the
final output.
Purpose
Benefits
This feature lets you to view a single report that includes all of the productivity-related
information that exists for a user over a selected period of time.
These are the benefits of the Consolidated User Report feature:
040111
Page 3
RELEASE NOTES
Example:
Consolidated
User Report
Page 4
This image is an example of the first page of the Consolidated User Report. There
can be up to seven pages of the report for each user.
040111
RELEASE NOTES
Benefits
view the number of assignments that have been merged in the Audit Trail
Report.
040111
Page 5
RELEASE NOTES
The learning curve functionality in Workforce Management has been enhanced with
the ability to define more types of learning curves. You are now able to create a
learning curve based on effective days for a user and job code. You can define the
scale and assign users and job codes to base the learning curve calculation on the
effective date of the assigned users. You can still create learning curves based on
tenure for a user and on effective days for a job code or user.
Note
In order to separate core work from non-core work, you can group the report
output by learning curve in the Summary Report and User Daily Detail Report.
Purpose and
benefits
Page 6
The learning curve enhancements provide a relationship between users and jobs,
which lets you define more specific learning curves. You can now
create a learning curve for experienced users that are being cross-trained on
established job codes, and
040111
RELEASE NOTES
Purpose and
benefit
Example:
Metric Data
Report
Metrics are used to capture specific user information from the system or to hold
metric data from other systems. The new Metric Data Report provides a view of
metrics, such as excused absences and unexcused absences for users, user groups,
work teams or report groups.
This feature lets supervisors easily group and view metric data results.
This image is an example of the Metric Data Report.
040111
Page 7
RELEASE NOTES
Workforce Management now provides the ability to view the utilization percentage for
a user in the Summary Report. Utilization percentage is the percentage of paid time a
user spends on direct work (value-added activity). The calculation is Direct Hours
divided by Total Paid Hours.
Note
Direct hours are the total amount of time attributed to value-added activity,
regardless of whether that job code is measured or unmeasured. Direct work is
defined by the corresponding job code.
Purpose
This feature lets you view the amount of time a user spends on direct work as a
percentage of total paid time.
For example, you can sort and run the Summary Report by user to view the amount
of time each user has spent on direct work. If there are users with a low percentage
of direct work, you can identify the cause and, if necessary, take steps to rectify the
problem.
Note
Common searches include By User, By Job Code, By Supervisor and By Work
Category.
Benefits
Page 8
These are the benefits of the Utilization Percentage Column in the Summary Report
feature:
Ability to view a value for utilization percentage in the output for the Summary
Report.
Ability to view utilization percentage at the detail, subtotal and grand total
levels.
040111
RELEASE NOTES
Example:
Summary
Report
This image is an example of the Summary Report with the column for
Utilization % highlighted.
040111
Page 9
RELEASE NOTES
General Enhancements
Description
Copy language
entries
Unmeasured
time delete
transaction
Page 10
040111
RELEASE NOTES
In this section
Topic
Page
12
Controller Enhancements
14
16
19
General Functional
20
General Technical
21
040111
Page 11
0BRELEASE NOTES
Inbound and
outbound
communication methods
Page 12
General behavior
Inbound and outbound Integrator communication methods have been enhanced with
these changes:
Outbound XML communication methods are now based on the StAX XML
parser, which lets you produce larger XML documents. However, due to
resource restrictions, there are still limitations to the size of an XML
document. Due to this change, it is recommended you test each outbound
XML communication you are using. These are the communication methods
affected by this issue:
SL_REM_IFD_DATA_USING_XML
SL_XML_TO_EMAIL_2
SL_XML_TO_FILE_2
SL_XML_TO_FTP
040111
0BRELEASE NOTES
Obsolete
communication methods
Obsolete
environment
variables
General
behavior
SL_XML_TO_HTTP_2
SL_XML_TO_JMSMQ
SL_XML_TO_MOCA_2
SL_XML_TO_SAPJCO_IDOC
Area
Retrieval
methods
Enhancement
Data from algorithm-based retrieval methods will now represent null number
data types using a system-configured null indicator value rather than an
indicator value of 0.
Applications
Transaction
hooks
040111
Page 13
0BRELEASE NOTES
Controller Enhancements
Description
RedPrairie
Console
RedPrairie Console
MOCA_DMALLOC option
Several enhancements have been made to the RedPrairie Console, an interface that
lets you administer and monitor the Controller server from a browser. Specifically,
you can now
use the Resource Usage page to view additional resource usage information,
including the current, peak and maximum usage values for
memory
sessions
database connections.
The peak value is the highest value for the resource that has been recorded
since the Controller server was started, and the maximum usage value is a
specific value defined by a configurable registry file.
Shutdown of
process-based
tasks
Page 14
select multiple jobs and tasks from the Jobs and Tasks pages.
use the RedPrairie Console while tracing active and inactive sessions to
configure the
trace levels that you want to enable for use during tracing
(Command, Manager, Arguments, Flow, SQL, Server and/or
Performance).
is forcibly terminated.
040111
0BRELEASE NOTES
This feature ensures that process-based tasks are not orphaned when the Controller
server is shutdown. An orphaned task is a task whose parent process has finished or
terminated, though itself remains running.
Although process-based tasks that are manually stopped using the RedPrairie
Console are still forcibly terminated, you can now configure a new environment
variable (MOCA_CLEAN_SHUTDOWN) to force the Task Manager to use the
shutdown mechanism on a task-by-task basis.
MOCA_
DMALLOC
option
Compile
mbuild
warnings
Controller now issues mbuild warnings when compiling local syntax in order to
enforce best coding practices and expose unexpected behavior. Specifically, these
warnings are now available:
In addition, Controller now lets you use annotations on command calls inside of the
local syntax in order to suppress the warning for unresolved commands in code
where the invalid reference is normal and expected.
040111
Page 15
0BRELEASE NOTES
Purpose
specify the measurement unit types (such as inches, kilometers, grams and
Celsius) that you do not want the system to round in unit of measure fields.
For measurement unit types that are not rounded, the system displays and
processes the values exactly as entered.
configure the display precision for individual field variables that use a unit of
measure on specific application windows.
The display precision enhancement lets you retain precise measurements where
required. For example, if an inch measurement unit type is entered into the system
with 8 decimal places (7.48576934 inches) and you require that all 8 decimal places
be retained for further calculation, then you can specify that fields using the inch
measurement unit type not be rounded.
Additionally, because you can now specify display precision values on an individual
variable basis, you can also indicate that only the unit of measure for select variables
not be rounded, while all other variables retain the system-wide display precision
setting. For example, if the display precision setting for Variable XYZ on Application
Window A is set to 3, then all values for Variable XYZ on Application Window A will
round to the third decimal place (for example, 3.456 inches), regardless of how the
system-wide display precision settings are configured in Measurement Unit
Maintenance.
Benefits
Page 16
result in more precise and exact measurements within your database, and
increase the flexibility with which you can view and process unit of measure
data within the system.
040111
0BRELEASE NOTES
Example:
Display
precision
settings in
Measurement
Unit
Maintenance
This image displays the Display Precision field on Measurement Unit Maintenance, where you
can enter a setting of -1 to ensure that RedPrairie products do not round the values in unit of
measure fields with the selected measurement unit type.
040111
Page 17
0BRELEASE NOTES
Example:
Display
precision
setting in MCS
Variable Setup
window
Page 18
This image displays the MCS Variable Setup window that appears when you press
Ctrl+Shift+F5 while in a RedPrairie application window. You can select a variable with a unit of
measure field type, and then use the Control Properties field to define the display precision
with which you want to round values in that field. In this example, the system will not round
values entered in the Height field on the Item Footprint Maintenance window since the control
properties (dsp_prec) are set to -1.
040111
0BRELEASE NOTES
The RedPrairie configuration of measurement unit types was enhanced. You can
now configure policies to set the system default units of measure for area, distance,
linear measurement, temperature, volume and weight. These policies, for example,
let you change US units (the distributed data values) to metric units. Once the values
are changed, then all new values entered in the system are stored in the database as
the new units.
IMPORTANT
After these policies are set, then all values entered using those measurement unit
types are stored as the new value (for example, US units or metric units). Values
entered prior to the policy update remain stored as the previous unit value. To
retain the integrity of your data, it is recommended that these policies be set prior
to system startup, and not modified after data exists in the database.
Purpose and
benefits
Example:
Measurement
unit type
policies in
Policy
Maintenance
The measurement unit type policies simplify the process of converting system units
from US to metric, or metric to US. The ability to set the value once and affect all
system unit values throughout the database reduces the time required to configure
the system, especially systems in non-US locales.
This image illustrates how you can configure Policy Maintenance to change the
measurement unit types used by your RedPrairie products.
040111
Page 19
0BRELEASE NOTES
General Functional
Description
DDA profile
and criteria
bar expand
and collapse
button
Job
Maintenance
test
The profile and criteria bar that appears in data driven application (DDA) windows
has been enhanced to let you show or hide the query fields. This enhancement gives
you more control on how you view the query fields on DDA windows. You click the
collapse button
to hide the query fields and expose more of the grid view and
application window. You click the expand button
to view the query fields.
The Job Maintenance window, which lets you create and schedule jobs, was
enhanced. You can now test a configured job to determine whether the job will
succeed or fail before you run that job.
When you test a job, the system validates the job configuration and alerts you to
potential problems. If an error message appears indicating that the job has failed,
then you can troubleshoot, resolve and retest that job before you schedule it to run.
Password
reset
permission for
non-super
users
Warehouse
identification
during login
Refresh
Navigation
Menu option
Server file
browsing
support
Page 20
The Role Maintenance window in Authorization Maintenance, which lets you maintain
the roles in your facility (such as assigning menu options, users, and permissions to
roles) was enhanced. You can now use this window to give non-Super users the
ability to reset a password for another user. This feature decreases the workload for
Super users by allowing non-Super users to assume responsibility for changing and
resetting passwords for users.
To help users in multiple warehouse environments select the correct warehouse
during login, the RedPrairie client login window has been enhanced to include the
warehouse identifier and warehouse description in the Warehouse ID selection list.
The Tools menu on the RedPrairie menu bar has been enhanced to include a
Refresh Navigation Menu option that lets users for whom permissions have been
changed to view the menu options associated with their new permission level without
logging out of the system. Once users select the Refresh Navigation Menu option,
they have instant access to menu items currently assigned to their role.
When using Load File Operations to load data into a database from external .csv
files, you can now view and select files located on a designated application server.
040111
0BRELEASE NOTES
General Technical
Description
Special
character
numeric input
mask
Local syntax
command
extensions
Tracing
support for
asynchronous
calls
Proxy server
setting
configuration
RedPrairie products now include an Any Character field input mask on the MCS
Variable Setup window to let you configure fields that require the use of special
characters as input variables. The Alpha/Numeric field input mask that was
previously capable of accepting special characters now accepts only letters or
numbers.
When using WinSQL to create a local syntax Controller command, you can now save
the command as an .mcmd file. Previously, when creating a local syntax Controller
command using WinMSQL, you were required to save the command as a .txt file,
and then manually add the XML tags required for .mcmd files before saving it to that
file extension. Now, when you save the command as an .mcmd file, the necessary
tags are added, and the file is automatically saved in the appropriate format for use
with Controller.
RedPrairie products now support the tracing of asynchronous calls. Asynchronous
calls permit parallel processing to continue while performing their call. Previously,
when you performed a trace in RedPrairie products, the tracing function would not
include asynchronous calls in the output. Now, when you perform a trace, the system
generates the standard trace file, as well as a trace file for any asynchronous calls
that were performed during the trace period.
The use of Internet Explorer (IE) proxy settings has now been disabled by default in
RedPrairie products to improve system performance. Customers that use corporate
proxy servers in their system configuration can now configure the system to
040111
Page 21
0BRELEASE NOTES
Page 22
040111