Making and Applying Language Changes in RedPrairie

Prepared for

Shell GSSP
Prepared by

Drew Arnold

RedPrairie Corporation
14 June 2012

Copyright © 2012. RedPrairie Corporation. All rights reserved.

This publication contains proprietary information of RedPrairie Corporation. No part of this publication may be reproduced, stored in a
retrieval system, or transmitted in any form by any means, electronic, mechanical, photocopying, recording or otherwise without the prior
written permission of RedPrairie Corporation
Contents
Document History ................................................................................................................................. 3
Introduction .......................................................................................................................................... 3
Changing, Downloading and Executing New Language Packs ............................................................... 4
An Example of How to Find the Correct Field in the OLTT from the UI ................................................. 5
Other Ways to find a Specific Phrase using the OLTT............................................................................ 8
Displaying Detailed Form Information and Messages for a Specific Page in RedPrairie ..................... 10
Applying Newly Generated Language Packs to Test and Pre Production ............................................ 11
Changing User Role Headings ............................................................................................................. 19
Metric Reports .................................................................................................................................... 20
Metric Headings .................................................................................................................................. 23
Workflow Schedule Setup ................................................................................................................... 24
Applying Language Packs during Test Cycles ...................................................................................... 26
Choosing POS Language ...................................................................................................................... 27
Validation Exercises – Internally and with Clients ............................................................................... 28
Difficulties and Visible English in RedPrairie ....................................................................................... 29

Page 2 of 29
Document History

Version Date Author Comment

1.0 05 June 2012 D. Arnold Draft – Initial Draft document completed.

2.0 12 June 2012 D. Arnold Draft - Initial Draft document completed.
Ready for review.
2.5 14 June 2012 D. Arnold Draft – Updates based on internal
review.

Introduction
This guide will assist in finding and amending language changes in RedPrairie, including User
Interface (UI), User Role and Metric Report changes.

Also detailed is how to apply newly created language packs and ‘Internal’ RedPrairie changes.

Page 3 of 29
Changing, Downloading and Executing New Language Packs
When a language change is saved through the Online Translation Tool (OLTT), a new language pack
will be generated. New language packs are generated every 6 hours (0900, 1500, 2100 and 0300) if a
change has been inputted and saved.

The address for the Online Translation Tool website is: http://translation.redprairie.com/login.asp

Login to the relevant language pack using details in language_logins.txt (supplied separately). Once
logged in, the following screen will be displayed.

Page 4 of 29
An Example of How to Find the Correct Field in the OLTT from the UI

When a change to a language has been requested and identified, the best way to ensure you select
the correct UI field in the OLTT is to hold ‘Ctrl’ and Right Click on the button or phrase in RedPrairie.
This will detail, if possible, the unique Database message name, which will ensure you change the
correct phrase in the OLTT. See below for more details.

Holding ‘Ctrl’ and Right Clicking this

field details information about this
phrase.

Page 5 of 29
Using the above detail ‘prtComposeMessage’, we can now search using the OLTT. Selecting ‘–ALL—‘
tables to ensure we find all instances (if multiples exist).

Page 6 of 29
 Here we can see the Primary Language phrase, Current Translation and New Translation (editable)
column. Enter the new translation into the “New Translation (Shell_*****)” field, next to the
Current Translation and Save.

You will notice that we have two fields for this Message Name, one is the description and the other
is the text itself. N.B When a new language pack is delivered to Shell, it is only the seen text that is
translated and this does not include descriptions, although we can still add or edit these if
requested.

Save and
Search
buttons

Existing Translation Box to Enter New Translation

Things to Notice:

 Table Name Rad_Sys_UI_Message - msg_desc versus Rad_Sys_UI_Message - msg_text, to

change the UI text, we need to amend the text instance.
 Ensure you select “Save” at least once to ensure the change is registered, there is no prompt
to highlight the change has been recorded, to return to the original search screen select
“Search”.
 To check your change is recorded we can search again for the phrase and if the change is
saved it will be displayed in the New Translation column. This new translation will move to
the Current translation when the next new language pack is generated.

Page 7 of 29
Other Ways to find a Specific Phrase using the OLTT

If the UI phrase is made up of two instances, e.g. Next **, this could be 15, 25 or 50 depending on
the RP code for the particular page being viewed. We therefore need to ensure that only the “Next”
part of the phrase is changed.

If we searched for “Next 25” in the OLTT, the probability is that we will observe some hits but they
may not be the one specific to the change request, i.e. Next 25 for the below example, in the OLTT
is, “Next <<__arg1__>>”, or in Norwegian, “Neste <<__arg1__>>” and not “Next 25”.

This example highlights a field that is referenced in many places in RP; in this case we therefore hold
one translation for many fields.

Page 8 of 29
Highlighted below are different ways to search using the OLTT.

1. Search using the “Source Text”, with either =, starts with or contains if only part of the
phrase is known.
2. Using the “Current” target text, again with =, starts with or contains.
3. The exact message name.

Any one of these methods should highlight the required field and note to always use table name ‘–
All—‘.

Page 9 of 29
Displaying Detailed Form Information and Messages for a Specific Page in
RedPrairie
Using a similar method of holding “Ctrl” and right clicking the button or phrase to display Message
Information, we can highlight all the editable fields and their message data by holding “Ctrl” + “Alt”,
and selecting the ”Instructions” button (normally at the top of the page). This opens a new window
with a Screen Snapshot, Form Information and Form Messages.

Screen SnapShot:

Form Information

Form Title: Innboks

Form Moniker: portal.information.alerts.Browse

Current Form Mode: View

Other Form Modes:

Form Instruction:
This screen allows you to open all messages in your inbox, and compose new messages. You can also delete messages and move messages to other
folders from this screen.

No matter what screen you have open, you are never more than one click away from your Inbox. You can always click the mail icon button at the top of
your screen (it looks like two overlapping envelopes) to launch your Inbox.

When you receive new messages, the system lets you know to check your inbox by animating the mail icon button and changing its color to a flashing
yellow.

Click the Oppdater button to update your inbox with any messages that may have arrived since you launched the page.

Click the Styr innboks button to change your personal settings such as automatic delete and timezone preferences.

Form Messages

Name Text Description

ButtonShowAll [Vis alle] null
ButtonClose Lukk %label% the current screen.
prtRefresh Oppdater Refresh this screen.
Delete the selected alert message(s).

prtAlertDelete Slett
Note: If you click this button all selected (checked box) alerts will
be permanently deleted from the system.
prtAlertLinkError Kunne ikke åpne skift null
prtHeaderHighAlert Høy prioritet null
prtHeaderMedAlert Normal prioritet null
prtHeaderLowAlert Lav prioritet null
prtInbox Innboks null
prtSubjectContains Emne Inneholder The first few letters of the subject you want to find.
The %label% selection determines how information is displayed
prtAlertSortBy Sorter etter on the grid. You can sort the information on the grid according to
different grouping preferences.
Page 10 of 29
prtAlertDate Dato The date and time that each alert was sent.
Click here to manage folders, change the timezone, and
prtManageInbox Styr innboks
control email forwarding.
prtPublishedAfter Publisert etter The message or alert was created after this date.
prtPublishedBefore Offentliggjort: The message or alert was created before this date.
Applying Newly Generated Language Packs to Test and Pre Production
WinSCP is a file share program where the language packs are copied from RedPrairie, this program is
freely downloadable online.

 Run WinSCP and enter the following information followed by Login

o Host Name - SFTP.redprairielabs.net
o User name - Redprairielabs\release_master
o Password - 6.2isgold

 Open the ‘release_master’ Translations folder

o Copy compressed language pack to your desktop or defined language folder
o Add the date of generation to the folder name e.g.
Shell_Norwegian_Translations_dd_mm_yy, this helps to keep track of new and old
language packs.

Page 11 of 29
Once you have downloaded the language pack you can close WinSCP.

 Next we need to apply the new language pack to the relevant environments. To do this we
Remote Desktop Connect to the database server for the environment. Referring to the
Server Builds Tracking Sheet will indicate the IP address. E.g. for Norway Pre-Production, the
DB IP is: 145.59.237.247

o Navigate to -> E:\DATA\RedPrairie

o Copy compressed language folder to this folder
o Unzip the folder in this location and open

Page 12 of 29
  The folder contains a number of files, however to execute the language pack we just need to
run the ScriptRunnerV2 package.

Once the ScriptRunner package opens we require the database instance taken from the Server
Builds Tracking Sheet for the environment.

For Norway RBA Pre-Production the database instance is AMS1-P-30053\INS01, this however needs
changing into the accepted ScriptRunner format (AMS1_P_30053_INS01 noting underscores).

Page 13 of 29
The User and Password information is detailed below.

o User = Deploy
o Password = Deploy#1

Next:

o Select Connect and we are then required to find the correct “Wave Database”
instance, i.e. for Norway RBA Pre-Production, this is “norba” (You can cross check
this with the initial RP login page, see below).

Page 14 of 29
o We can then select Run. This will relatively quickly display information relating to
whether the language exists in this environment, if all is correct there will be no
error messages. (These screen shots are from a Shell_Dutch application but are the
same for all deployments)

Page 15 of 29
o Next we can close the pop up window and are prompted to confirm we want to run
the package.

o A language package can take anywhere between 20 seconds and 2 minutes to

deploy.

Page 16 of 29
o Another pop up window will display any deployment errors. We can close this and
Exit the ScriptRunner package, however if we need to deploy the language pack to
other environments i.e. Norway DO and DO+ we can simply Re-Run the package by
selecting “nodo” and “nodop” without closing this program.

o Once completed you will observe an “Outfile” folder, this is for reference and
requires no action.
o Log Off the Database server

Page 17 of 29
  To complete the process we need to reset Internet Information Service (IIS) for the relevant
environment App Server/s. E.g. for Norway RBA Pre-Prod these are 145.30.70.30/29.

 Select the App Instance and select “Restart”, wait until IIS resets.

N.B. It is important that this step is completed at an appropriate time as to not impact any workflows
or automatic jobs being completed in the environment, as a rule restarting IIS should be completed
after 5pm GMT to avoid potential issues in the test and pre-production environments. It is also
important to note that a Production upgrade is completed by our hosting partners and all that is
required from RedPrairie is delivery of the latest language pack, no other action is needed.

Page 18 of 29
Changing User Role Headings
User Role Setup defines the text in the left hand pane of the UI. It is necessary to edit this if a
language pack change has been made and does not affect the User Role text automatically.
RedPrairie can hold multiple translations for user roles but is changed through the UI and changes
must be completed under the specific language being edited, below is the menu item ‘User Role
Setup’, in both English and Norwegian.

N.B. To find a menu item in an alternate language, search using the Menu bar first in English to
highlight exactly where the Menu item will be in the other language UI.

Page 19 of 29
Metric Reports
Metric reports are another example where changes to the UI are made in the UI. Metric report
changes are completed through Metric Report Editor (MRE), and again changes need to be entered
under the alternate language at Client Admin level.

For example, The user making metric report changes will need to have their user interface language
set to the language in which they need to make changes, accessed through ‘Edit My Profile -> User
Preferences (see below). Once the selected language is saved, RedPrairie will need to be re-opened
for alternate language to take effect.

Page 20 of 29
Some reports in RP are not immediately editable; the ones with the BlueCube symbol indicate that
no changes can be made to that report. However, if we do need to translate one of these BlueCube
owned reports we can ‘Copy’ the whole report within MRE.

BlueCube and Global RP

(editable report) Symbols

Example of copied report

Page 21 of 29
Inside the report we can change the title and metric headings. Below are notes on changing the
heading. N.B. Note alternate language user interface.

Report Title. N.B. – User Role Setup

(URS) will need to be updated to
align the heading on the left with
this Main Report Title, we may also
need to change which report is
referenced within URS (see below
image)

User Role Heading, possibly

independent of MRE.

To select which report is polled from MRE, we need

to be able to distinguish between the original and
copied report. To do this, rename the copied report
to differentiate between the two. Once the correct
report in URS is selected, we can revert any change
back from within MRE.

The report selection and name will need to be completed for the selected User Roles that are
observed in the alternate language i.e. Site Manager, Cluster/Territory, Cashier and Supervisor.

Page 22 of 29
Metric Headings
N.B. Note the “Kopi” button on the right hand side (regarding copying reports).

1 5

2
4

To change the metric headings from within MRE and the selected report:

1. Select the detail tab in the copied metric report.

2. Select the metric you wish to edit.
3. Edit the ‘Header’ field (Topptekst in Norwegian).
4. Save and Close.
5. To validate the change(s), go to the options tab and run the report (Alternativer in
Norwegian).

Page 23 of 29
Workflow Schedule Setup
Much like MRE, to change the workflow names, seen on the dashboard of Site Manager and Cluster
for example, we use Workflow Schedule Setup.

Workflow Schedule Setup - English

Page 24 of 29
Example - Norwegian

Select the workflow you wish to change and edit the name field. This also must be done at Client
Admin level.

Page 25 of 29
Applying Language Packs during Test Cycles
During a test cycle you may be requested to complete and change some UI fields, this task may be
raised as a defect within QC or directly via email. It is important to follow this process as closely as
possible to apply, test and validate language changes. As we run many environments simultaneously,
if we complete changes in test and not mirror these into Gold environments we will lose any manual
and language pack changes that have been completed when Gold is copied into test during break
weeks.

Therefore,

 After applying language packs into test, confirm that the changes have been applied, and all
edited fields have been addressed.
 If this passes our own validation, apply the language pack immediately into Gold, again
confirm that these changes have been applied.
 Repeat this process with any manual changes made into test, as detailed in this guide, and
validate once more in Gold.
 If language validation is to be mirrored in all test environments, apply to test 2 and 4 for
example, otherwise it must be stressed to all involved that language validation is to be
completed in only one of the test environments.
 These steps will ensure no changes are lost or erased between test cycles.

Page 26 of 29
Choosing POS Language
For Austria and Switzerland markets (and potentially new upcoming markets) we are using an
amalgamation approach to inventory and fuel data whereby RedPrairie will define what language is
downloaded to the POS, Customer Receipts, SEL’s and Display.

This is defined through Business Unit Setup (for a selected BU) -> Related Links -> POS Management
Setup.

Selecting a ‘Default Language’ will poll data from that language specific to Items and Fuels, the UI
language will not be altered, just what is downloaded to the POS.

Page 27 of 29
This alternate language data is configured and imported by Shell through Item Setup -> Related Links
-> Item Translation Setup (Similar process for Fuels).

Validation Exercises – Internally and with Clients

It is highly advisable to perform an Internal Quality Check once any new language pack is applied and
ready for client delivery, ensure all language pack deliverables (workflows and reports), and ‘seen’
user interface is translated. English that is observed that is not in an alternate language, and which is
editable via the OLTT, may indicate language pack issues and should be followed up with your line
manager.

In the past we have used the format ‘A Day in the Life’, whereby we attempt to demonstrate the
language within the environment from a Site Managers perspective. This includes an End of Day
walkthrough (with sales and fuel data if possible), and an execution of as many reports as possible
(data dependant).

To achieve this requires a linked test rig to pass sales data through. If this is not possible we have in
the past requested a live ‘End of Day’ from our test partners in the IDC, enabling us to record the
EOD at a suitable time.

Page 28 of 29
Difficulties and Visible English in RedPrairie
With RedPrairie being a very complex and layered system, it is inevitable that some of the
functionality and fields are not multiple language compatible (as they may be referenced by a
background job and need to remain in English). This can present issues in one market but not
another, for example, there are some words in the UI in English that do not exist in the Norwegian
vocabulary, in these cases we will need to explain the context and meaning to help define a
translation.

An example where the UI will always display the English is the Global Hierarchy, a decision made by
the GSSP project team to keep in English across all markets.

You may also discover fields in RedPrairie that were not originally coded to support multiple
languages, in these cases it is a Change Request from our point of view unless we can prove it as a
defect.

It is also important to convey that even when we receive a new language pack that new or recently
added functionality may not have been translated. This is also true of CR’s and enhancements, these
may need to be translated after delivery.

Similarly with Metric Reports, these will need translations inputted at an early stage of an
environment creation as these are manually addressed and not included in a delivered language
pack.

Page 29 of 29