Академический Документы
Профессиональный Документы
Культура Документы
User’s Guide
B006-6038-M000
Issue 1
January 2013
The products described in this document are copyrighted works of NCR Corporation.
IBM and OS/2 are either registered trademarks or trademarks of International Business Machines Corporation in the
United States and/or other countries.
Sybase and PowerBuilder are either registered trademarks or trademarks of Sybase Inc. or its affiliates in the United
States and/or other countries.
Adobe, Acrobat and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United
States and/or other countries.
All other trademarks are the property of their respective owners.
Disclaimer:
It is the policy of NCR Corporation to improve products as technology, components, software and firmware become
available. NCR therefore reserves the right to change specifications without prior notice.
All features, functions and operations described herein may not be marketed by NCR in all parts of the world. In some
instances, photographs are of equipment prototypes. Therefore, before using this document, consult with your NCR
representative or NCR office for information that is applicable and current.
To maintain the quality of our publications, we need your comments on the accuracy, clarity, organisation and value of
this book.
© 1998 - 2013
By NCR Corporation
Duluth Georgia, USA
All Rights Reserved
Federal Communications
Commission (FCC) Radio Frequency
Interference Statement
Note: This equipment has been tested and found to comply with
the limits for a Class A digital device, pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is
operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual,
may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause
harmful interference in which case the user will be required to
correct the interference at his own expense.
This digital apparatus does not exceed the Class A limits for radio
Canadian Class A Device noise emissions from digital apparatus set out in the Radio
Declaration Interference Regulations of the Canadian Department of
Communications.
Le présent appareil numérique n’émet pas de bruits
radioélectriques dépassant les limites applicables aux appareils
numériques de la classe A prescrites dans le Réglement sur le
brouillage radioélectrique édicté par le ministère des
Communications du Canada.
Revision Record
B-2 Added new worker list for Advance NDC 3.02 and
reordered headings for new workers provided in
previous releases
5-6 Added note that only EXE files can be built, not
OCX.
Contents
Preface
Chapter 1
APTRA Author Basics
Overview ................................................................................................1-1
Introducing the APTRA Author..........................................................1-2
Life Cycle Support ..........................................................................1-2
APTRA Author................................................................................1-2
Authoring System..................................................................................1-4
Runtime Components ...........................................................................1-5
Authoring Components Provided................................................1-5
Using Your Own Authoring Components..................................1-5
Chapter 2
APTRA Author Setup
Overview ................................................................................................2-1
Working Directory ................................................................................2-2
User IDs ..................................................................................................2-3
User ID Format................................................................................2-3
Using the User ID Utility ...............................................................2-4
PC Directory Structure .........................................................................2-6
Global Directory Structure ............................................................2-6
Directory Types...............................................................................2-7
Installing the ActiveX Sample Application .......................................2-9
Chapter 3
The APTRA Author Methodology
Overview ................................................................................................3-1
Graphical Programming Environment ..............................................3-2
Communication Between Workers .....................................................3-5
Types of Workers...................................................................................3-6
Using Workers to Extend Advance NDC....................................3-6
Chapter 4
First Steps in Building an Application
Overview ................................................................................................4-1
“Hello World” Tutorial.........................................................................4-2
Finding the Correct Component...................................................4-4
Setting the Properties of Components .........................................4-6
Starting the Simulator ....................................................................4-7
Running the Application ...............................................................4-7
Creating an Attractor Sequence...........................................................4-9
Top Worker ......................................................................................4-9
Co-ordinator ....................................................................................4-9
Director.............................................................................................4-9
Creating an Application...............................................................4-10
Using a Director Worker..............................................................4-10
Creating a Director Worker .........................................................4-10
Adding the Hello World Worker................................................4-12
Modifying Attributes Dynamically ............................................4-12
The Attractor Sequence ................................................................4-13
Adding a New Top Worker.........................................................4-14
Adding a Timer and Editing its Attributes ...............................4-14
Creating Screen Text.....................................................................4-15
Sharing a Timer Worker...............................................................4-15
Copying the Text Worker ............................................................4-16
Signals Available from a Worker................................................4-17
How Workers Communicate .............................................................4-18
Connecting the Flow.....................................................................4-18
Running a Completeness Check........................................................4-20
Running the Test Application............................................................4-21
Test Window Menu Options .......................................................4-23
Conclusions ..........................................................................................4-25
Chapter 5
ActiveX Controls and APTRA Author
Overview ................................................................................................5-1
APTRA Author and ActiveX ...............................................................5-2
ActiveX Controls .............................................................................5-2
ActiveX scripting.............................................................................5-3
Generating ActiveX Controls ........................................................5-3
APTRA Author Workers and Utilities ...............................................5-4
Workers ............................................................................................5-4
Using a Web Page Interface...........................................................5-6
Software Utilities.............................................................................5-9
The Barcode Scanner Sample Application.......................................5-11
ActiveX Sample Application .......................................................5-13
Barcode Sample Application .......................................................5-13
Advanced Functionality...............................................................5-18
Hints and Tips......................................................................................5-19
Active Script Host .........................................................................5-19
Screen Displaying With Script Hosts .........................................5-19
Multiple Result Work Groups.....................................................5-19
Enumerated Types........................................................................5-20
Chapter 6
Managing Modules
Overview ................................................................................................6-1
Access to Components You Do Not Own..........................................6-2
Creating a New Module .......................................................................6-6
Default Module ...............................................................................6-7
Using Catalogs and Creating Workers...............................................6-9
Transferring the Worker to Another Module..................................6-12
Transferring the Worker to a Module You Do Not Own........6-13
Changing the Owner of a Module ....................................................6-15
Move a Module ....................................................................................6-17
Module Move Based on Ownership ..........................................6-17
Move to the Default Module .......................................................6-18
Summary on Modules ........................................................................6-19
Chapter 7
Team Development
Overview ................................................................................................7-1
Planning for Project Development......................................................7-2
Approaches to Team Development..............................................7-2
Team Development.........................................................................7-5
Owning More Than One Module .................................................7-6
Receiving Ownership of a Module...............................................7-6
Project Management Features..............................................................7-8
Project Comparison ........................................................................7-8
Read Only and Shared Components............................................7-8
Component Status...........................................................................7-9
Module Information .......................................................................7-9
Module Highlighting......................................................................7-9
Merging Projects ..................................................................................7-11
Creating Project Reports.....................................................................7-13
Producing a Workers Report.......................................................7-13
Catalogs Report Option ...............................................................7-14
Components Report......................................................................7-15
Module Ownership Report..........................................................7-16
Printing Reports and Language Support...................................7-17
Appendix A
Troubleshooting
Overview ...............................................................................................A-1
Dealing with Exceptions......................................................................A-2
Advance NDC Exceptions ............................................................A-2
Questions and Answers.......................................................................A-4
Getting Help and Information .....................................................A-4
User IDs ...........................................................................................A-5
Working with Screens ...................................................................A-6
Developing and Testing an Application.....................................A-6
Building an Application................................................................A-7
Appendix B
Advance NDC Worker Support
Appendix C
Extending the APTRA Author Runtime
Appendix D
Guidelines for Developing Applications
Overview ...............................................................................................D-1
PCI DSS/PA-DSS Considerations ................................................D-1
Appendix E
Reserved User IDs
Appendix F
Display Considerations
Overview ................................................................................................F-1
Understanding Grey Scale Monitor Burn-In .....................................F-2
What is Monitor Burn-In?..............................................................F-2
Example of Monitor Burn-In .........................................................F-2
How Do I Prevent Monitor Burn-In? ...........................................F-3
Implementing Screen Maintenance Techniques.........................F-3
Guidelines for Using Monochrome STN LCDs ................................F-4
Colour Depth ...................................................................................F-4
Contrast ............................................................................................F-4
Animation ........................................................................................F-4
Optical Effects..................................................................................F-4
Display Burn-In...............................................................................F-5
Appendix G
Related Documentation
Overview ...............................................................................................G-1
APTRA Author Documentation.........................................................G-2
Other NCR Documentation ................................................................G-4
Appendix H
APTRA Author GUI Reference
Glossary
Glossary .................................................................................... Glossary-1
Index
Index ................................................................................................Index-1
List of Figures
Chapter 2
APTRA Author Setup
Chapter 3
The APTRA Author Methodology
Chapter 4
First Steps in Building an Application
Chapter 5
ActiveX Controls and APTRA Author
Chapter 6
Managing Modules
Chapter 7
Team Development
Appendix A
Troubleshooting
Appendix D
Guidelines for Developing Applications
Appendix F
Display Considerations
Appendix H
APTRA Author GUI Reference
List of Tables
Preface
Chapter 2
APTRA Author Setup
Chapter 4
First Steps in Building an Application
Chapter 7
Team Development
Appendix B
Advance NDC Worker Support
Table B-1 Workers Modified for Advance NDC 4.02 .............. B-14
Table B-2 Workers Modified for Advance NDC 4.00 .............. B-15
Table B-3 Workers Modified for Advance NDC 3.04 .............. B-16
Table B-4 Workers Modified for Advance NDC 3.03 .............. B-16
Table B-5 Workers Modified for Advance NDC 3.02 .............. B-18
Table B-6 Workers Modified for Advance NDC 3.00 .............. B-18
Table B-7 Passbook Printer Differences..................................... B-21
Table B-8 Runtime Errors Mapping to Signals......................... B-22
Appendix C
Extending the APTRA Author Runtime
Appendix E
Reserved User IDs
Appendix G
Related Documentation
Appendix H
APTRA Author GUI Reference
Table of Contents Lists the first two heading levels in page order with
page references.
Table of Contents Lists the first three heading levels in page order
for chapter or with page references.
appendix
Element Description
Multi-Vendor Implementations
If you intend to implement Advance NDC on other vendors’ SSTs,
refer to the APTRA Advance NDC, Multi-Vendor Support Reference
Manual.
PCI DSS/PA-DSS
For an Advance NDC end solution that is compliant with the
Payment Card Industry Data Security Standards, (PCI DSS),
Authored modifications may fall within the scope of the Payment
Application Data Security Standard (PA-DSS). For more
information refer to the following:
APTRA Advance NDC, Payment Application Data Security Standard
Implementation Guide
APTRA Advance NDC, Developer's Guide
Appendix E, “PCI DSS & PA-DSS Compliance in Advance
NDC”
PCI Security Standards website.
Copy Hold down the MB1 and the Control key and drag item.
(Copy will take a copy of the current Authoring
component. Note that the two components are now
unique, any changes to one will not be made to the
other).
Share Hold down MB1 and the Shift key and drag item. The
component will now be referenced from two places.
If you have a problem using the Author software, try the following
Support Information to resolve it:
1 For exception handling in Advance NDC and Self-Service
Support, see Appendix A, “Troubleshooting”
Chapter 1
APTRA Author Basics
Overview 1-1
Overview
Overview 1
With the APTRA Simulator, the Author provides support for the
Life Cycle Support 1
Authoring system
Runtime components.
Authoring System 1
Runtime Components 1
For details of the name and location of the Worker Factory file that
you distribute, see the section “What is a Worker Factory and when
do I need to build one?” on page A-7.
Chapter 2
APTRA Author Setup
Overview 2-1
Overview
Overview 2
Working Directory 2
Before you start using the Author, you must create a directory
\<working>, in which <working> can be any directory name of your
choice.
The working directory is the place where you save your Author
projects and it provides a base directory. This directory is also
where your Advance NDC applications must be built. For details of
building a final application, see “How Do I Perform a Build Final”
on page A-8.
User IDs 2
A unique User ID is required for each user that will be using the
Author to create an application or to create authoring components
for other users. A separate User ID utility is provided, which allows
you to manage the Author User IDs. User IDs must be set up before
using the Author for the first time.
Each component that is created in the Author has a unique
component identifier. It is very important that each user has a
unique User ID, even when using separate development PCs, as
components will be copied and shared between projects. Errors will
be caused when components are created with a User ID that is
present on more than one PC at any one time.
A User ID is a file that can be moved, not copied, from one
development PC to another by copying the file to another disk and
then deleting it from the original PC. The User ID file is installed
into your <global> directory.
<user-id>.USR
Figure 2-1
User ID Utility
2
Note: If you run the utility from the check box, do not select the
Increment All Install Counts button. If you do this, the install counts will
be incremented twice.
If you run the utility from the Start menu for the first time since
installation, you can increment all counts by selecting the Increment All
Install Counts button.
To change the installation count for an individual User ID, select the
ID from the list, enter the number of installations in the Install No text
box, and select the Update Install Count button.
For more information about the installation counts, see “Why is the
Install Number so important?” on page A-5.
2 Select the Create New User ID button. Accept the prompt to create
the User ID with an install count of 1.
3 If you need to change the install count for the User ID, enter the
required count in the Install No text box, and select the Update Install
Count button.
PC Directory Structure 2
Table 2-1
Development PC Directory Structure
Directory Contents
<drive>:\<global>\AUTHOR\dll DLL files supplied with the Author for Windows NT.
<drive>:\<global>\AUTHOR\XPDll DLL files supplied with the Author for Windows XP.
Directory Contents
Chapter 3
The APTRA Author Methodology
Overview 3-1
Overview
Overview 3
Graphical Programming
Environment 3
Figure 3-1
Advance NDC workers
Figure 3-2
Worker Hierarchy
Workers
Work Group
Figure 3-3
Work Flows Between Work Groups
Director
Work Flow
Work Group
Types of Workers 3
Chapter 4
First Steps in Building an
Application
Overview 4-1
Conclusions 4-25
Overview
Overview 4
Note: In the tutorials that follow references to the left and right
mouse buttons are given as MB1 and MB2.
Figure 4-1
User ID Dialog Box
2 Select your name from the list and then OK to display the main
author screen.
Status Bar
5 Select the Open button to open the project for the Customisation
Layer components.
The first thing you must do is save this project with another
name (do not overwrite the originally supplied .mpj project file).
Note: Ensure that you save the new project in your working
directory and not the global directory.
Now you need to create a new module and assign it as your default
module, then a new catalog and finally a new application. The
module gives you ownership, and the catalog allows you to group
the components you create in an organised manner. Complete the
following steps.
1 Open your project and on the Modules menu, select Create and
type in Tutorial as the name.
Figure 4-3
Creating the “Hello World” Application
Catalog Window
Now that you have created a component in your catalog you can
use it in the workspace to start developing your application.
Figure 4-4
“Hello World” Application in the Workspace
Workspace
Window
For this “Hello World” simple application, you are going to use a
Finding the Correct worker which will display a text message. You will find the worker
Component 4
in the Displays catalog.
You can add a worker to the work group in one of three ways,
described on the next page.
Method 1 4
2 Select Displays from the list. A catalog with the Displays workers
is shown. You may need to select Window | Tile from the menu to
ensure that the catalogs are all visible (and not one on top of
another).
3 Copy the Fixed Front Text worker into the Top Worker of the
application. (Hold down MB1 on the worker, press the Control key
(Control for Copy) and drag the icon to its destination.)
Method 2 4
1 Select MB2 anywhere inside the work group of the Top Worker.
Method 3 4
Figure 4-5
Adding a Text Worker
You now need to define the actual text you want the Fixed Front
Setting the Properties of Text worker to display, as well as some of its other properties, such
Components 4
as colour and position.
1 Select the Fixed Front Text icon with MB2 and open the Settings
dialog box by selecting Worker Settings from the pop-up menu
(you can also double-click MB1 on the icon).
Figure 4-6
Worker Settings Dialog Box
Work group
Work flow.
You can display or hide the Settings dialog box by selecting the
Open Settings option in the View menu. A check mark to the left of
the Open Settings menu option indicates that the Settings dialog is
visible.
For more information on the Settings dialog box, see the on-line
help.
You now have a complete application. If you have the APTRA XFS
Simulator (Simulator) installed, you can test the application outside
the Author, in the PC environment to see its effect. You must ensure
that you have started the Simulator before running the Author Test
Application.
NCR recommends that you test your application frequently when
creating and adding new components. This will allow you to correct
problems at each stage in the development.
Save the project now before testing the application (Select File |
Save).
It is good practice to save your work regularly.
1 Select the application icon (on the blue background) with MB2.
On the Application pop-up menu, select Start.
The application will start executing. You should see a new
window appear with the name of the application on the title bar.
This is the Test Application window and it represents the screen
of the SST.
Figure 4-7
Displaying the Test Application Window
2 Select Stop from the Application pop-up menu. Now change the
Text String in the Fixed Front Text worker to “World Hello“.
Re-start the application by selecting the application icon with
MB2, then Start from the pop-up menu. The text changes on the
screen.
Sharing the “Hello World” Fixed Operator Text worker into your
own Catalog lets you use it again later. This is another benefit of
using the Author: re-use of components.
1 Select the Hello World worker with MB1.
2 Holding down the Shift key (Shift for Share) and MB1, drag the
worker into your catalog.
A Director contains work groups and each work group can contain
a number of workers. Using one of the Director’s work groups as an
example, the Director activates each worker in the work group in
turn, with the worker at the far left of the first row being activated
first. The workers are activated in turn very rapidly and it appears
as though they are activated simultaneously.
All workers in a Director will be started, regardless of whether the
first worker generates a response before any other worker has been
activated. The co-ordinator will not look for any signals during this
‘start-up’ phase. When all the workers have been activated, the
(Director) co-ordinator will be in a position to recognise when a
signal is raised. All the workers will then be de-activated before the
co-ordinator responds to the signal.
follows:
1 Select your Tutorial - part 1 catalog. Create a new application by
selecting Components | New | Application from the menus.
3 To define the name of the new worker, you can select the icon
with MB2, then select Worker Settings from the pop-up menu. Enter
the name IDLE SEQUENCE. Alternatively, use one of the other
methods described in “Finding the Correct Component” on
page 4-4.
5 Share the IDLE SEQUENCE icon (select the icon in your catalog
with MB1, then pressing the Shift key and MB1, drag the icon) into
the Top Worker of the application.
Figure 4-8
Idle Sequence Director in the Workspace
Director
Work
Group
You will notice that the first work group has a START label attached
to it. This label indicates the work group that will be activated first.
When the Director itself is activated it will activate all workers
within this work group.
The top worker will become activated under one of two conditions,
as follows:
Started from within the Author (to test it on the development
PC)
Installed on an SST and the SST is powered on (the application
will automatically start executing).
The first method will be used in this tutorial to test the application
as it is being developed.
You are now going to add the Hello World worker you created
Adding the Hello World earlier to the START work group. The difference here is that you
Worker 4
will encapsulate a specific worker in the worker structure, allowing
you to add more workers, for example to display more text to the
screen. The first example of Hello World would not allow you to
add more workers.
1 Share the “Hello World” Fixed Front Text worker into the
START work group.
2 To change the text colour, double-click MB1 on the text and select
the Colour Editor from the dialog box.
Figure 4-9
Selecting the Colour Editor
4 When you select OK, notice that the colour of the ‘Hello World’
text changes to the colour you selected in the palette editor.
5 If you wish, you can also dynamically change the font of the text
using the Font Editor.
6 When you are satisfied with the colour and font of the text, stop
the application running and close the Test Application window.
Each type of worker has a different behaviour (as do all the workers
The Attractor Sequence 4
Here you will remove the IDLE SEQUENCE Director from the
Adding a New Top Attractor application and then add a new top worker.
Worker 4
1 Select the Director with MB2 and select Remove. Then select Yes
when prompted with the confirmation message.
2 Select the Application with MB2, select Add Top Worker and select
Director. Name the new worker Attractor Sequence. Show its
view by double-clicking its icon.
Here you will add a ten-second timer to the START work group:
Adding a Timer and
Editing its Attributes 4
1 In the workspace view of the Attractor application, select the
Start work group with MB2.
2 Select Add Worker to show the pop-up menu. Select Timer from the
list.
3 Open the Worker Settings dialog for the Timer, and change its
name to 10 SECONDS.
Figure 4-10
“10 SECONDS” Timer in the Workspace
2 From the list, select Fixed Front Text. Name the worker IDLE 1 and
set its attributes as follows:
For the moment you can leave all other attributes at their default
value.
3 To share the new worker to your catalog, select the icon, then
press the Shift key and MB1 to drag the icon into your catalog.
2 Hold down the Shift key and MB1 to drag the icon into the empty
work group.
Satisfy yourself that the two Timers are actually the same. For
example, select one Timer and using the Settings dialog move to the
Description tab and enter the description 'attractor timer'. Select the
other Timer and observe that the same description appears.
Note: You have shared the same Timer worker between two work
groups.
If you change the Time Delay attribute to 5 seconds for one of the
Timers, it will be changed across all the shared workers.
Copy the IDLE 1 worker from the first work group to the second
Copying the Text Worker 4
one.
1 Select the IDLE 1 icon in the START work group
2 Hold down the Control key and MB1 to drag the icon into the
second work group.
3 Name the new worker IDLE 2 and set its attributes as follows:
Note: The Text String remains the same when you copy a
worker and hence you did not need to re-enter it here (as we
want the same text string).
Figure 4-11
Copying the Text Worker
To find out what signals are available from a worker, look at the
Signals Available from a on-line help, as follows:
Worker 4
Figure 4-12
Signals from the Timer Worker
signal at the end of the Timer period. In this example, after the
time-out of each Timer the other worker should activate (to display
the alternative attractor screen).
1 Select the START (Place 1) work group with MB2, then select
Create Workflow from the pop-up menu.
2 Select the other (Place 2) work group. A work flow has now
been added between the work groups.
3 Now add a work flow from the Place 2 work group to the Place 1
work group.
This indicates that when a signal occurs the source work group will
be de-activated and control will pass to the destination work group
pointed to by the arrow on the work flow. Note that we have not yet
specified which signals cause the control to change. This will be
done when you select a signal.
1 Select one of the work flows (click MB2 and select Workflow
Settings). A dialog box appears allowing you to name the flow
and to allocate a signal generated by a worker. (There may be
more than one signal generated by a worker so ensure that you
select the correct one.)
Note: The Depth drop-down list box allows you to limit the search
and selection of available signals to assign to a work flow. This is
especially useful for performance reasons when an application
contains a deep worker hierarchy and you want to assign a signal
which is generated near the top of the hierarchy. Since this manual
only involves you developing relatively simple applications, you
can leave the Depth at its default value of ‘Full’ when assigning
signals to work flows. For more information about this feature, refer
to the Author on-line help.
Figure 4-13
Assigning Signals to Work Flows
2 Select Completeness Check to check that you have completed all the
appropriate settings for each worker.
Figure 4-14
Completeness Check Dialog Box
Figure 4-15
Successful Completeness Check
Figure 4-16
Completeness Check with Errors
The errors shown on the above screen are only warnings. This
means that you can still test the application on the development PC.
You will not be able to perform a build final on a Final Application
for execution on the SST until the causes of all such warnings are
resolved.
Figure 4-17
Active Work Group
2 Modify the Time Delay attribute in the Timer worker (it does
not matter which Timer you select as it is the same worker
shared in two places) to two (2.0) seconds.
2 Change the Text String attribute for the IDLE 1 text worker to
“We would like you to enter a card”.
If you select the test window’s title-bar icon, this reveals the title-bar
Test Window Menu drop-down menu. This menu contains two significant Author menu
Options 4
items:
SST Screen Size
ScreenDisplayer Mode.
This menu item sets the size of the test window on the development
PC. This allows you to preview how an application will look when
run on an SST with a different screen resolution from that of your
PC. The size options are as follows:
640 x 480
800 x 600
1024 x 768
1152 x 864
1280 x 1024.
Conclusions 4
In this chapter you have built your first application. It was a simple
application using the basic concepts. The application was tested in
the Author on the development PC. You did not need to run it on
the SST.
By this stage you should be familiar with the concepts of using the
Author, how to use existing workers and define the unique
properties for your application.
In the next chapter we will look at more powerful objects that let
you add more powerful types of workers. These workers provide an
interface to the devices on an SST, for example, the Card
Reader/Writer, Journal Printer and FDK keypad.
Chapter 5
ActiveX Controls and APTRA
Author
Overview 5-1
Overview
Overview 5
controls:
Active Control
Active Script Host
Automation Object
COM Initialiser
Integer Signaller
Variant Store
Web Event Monitor
Web Page Loader.
An introduction to each of these workers is provided in the
following pages; further details of all of these workers (except the
generic Integer Signaller) are available in the ActiveX Worker Class
Help.
Active Control 5
Automation Object 5
COM Initialiser 5
This worker creates and initialises a COM object associated with the
subworker object.
The COM Initialiser is useful if you are using an Active Control
class to wrap a complex Active Control object which has a long
initialisation time. You can make sure that any delay due to the time
taken to create the COM object is handled before the COM objects
are used, by dropping the Active Control class into the Data Objects
work group. This prevents the delay occurring during customer
transactions.
Integer Signaller 5
This worker was originally for use within an SSDS Flow, which is
not supported. However, it can still be used as a Passthru worker.
Variant Store 5
Note: The Integer, String and Real Data Store workers have been
enhanced to support COM. They can be used to share data as in a
The Web Event Monitor and Web Page Loader workers assist in the
Using a Web Page development of consumer flows within the Author where the aim is
Interface 5
to provide a web-page-driven graphical interface to the cardholder.
Figure 5-1
Interaction of Workers and Controls
Withdrawal
“Welcome2”
Enquiry
Each Web Page Loader worker loads the initial page Welcome1.htm
or Welcome2.htm. The example VBScript shown below ensures that a
failed navigation results in activation of the Failed work group,
which in this case contains a Passthru worker:
Sub WebBrowser_BeforeNavigate2(pDisp,URL,Flags,
TargetFrameName,PostData,Headers,Cancel)
' The following code is provided to catch Navigation
errors
' Add to this code to catch other Navigation exceptions
If InStr(1, URL, "dnserror", vbTextCompare) > 0 Then
Cancel = True
ActiveWorkGroup.Failed=True
End If
End Sub
This allows the consumer flow to continue to the next stage, shown
as ‘Card Entry’ in the extract from the sample application,
Figure 5-1 “Interaction of Workers and Controls”.
The web pages are loaded through Web Page Loader workers, and
any user-generated COM events are handled through the buttons
and the Web Event Broker object, passing control back to the Author
to continue the consumer flow.
The advantage of these workers and objects is that they enable you
to use the benefits of both the Author and web-page technology for
the user interface.
Control Browser
Control Builder
Script Editor.
Control Browser 5
The Control Browser, a Literal Type Editor for the Class Identifier
attribute in the Active Control worker, displays a list of all the
ActiveX controls installed on your development PC. It is invoked
when editing the Class Identifier attribute in an Active Control
worker. The Control Browser enables an ActiveX control to be
selected from those installed on your PC.
Control Builder 5
Script Editor 5
The Script Editor is a Literal Type Editor for the Script attribute in
the Active Script Host worker, and enables the entry of VBScript
associated with the Active Script Host worker.
The Script Editor provides empty template functions to which script
can be entered, and to associate script with events generated from
Active Control workers in the Data Objects work group (that is,
‘Event Handlers’).
It also enables you to view the Methods, Properties and Events of
ActiveX controls included in the Data Objects work group.
Figure 5-3
Opening the Customisation Layer Project
Figure 5-4
Module Copy Procedure
Figure 5-5
Confirmation Message
Figure 5-6
Menu Bar Message
You will now be able to view the components in the ActiveX sample
application.
Ensure the Author is running, open the project you have just named
ActiveX Sample (during the module copy process), and then open the ActiveX(TM)
Application 5
Sample Application catalog to see the ActiveX sample application (File
| Open Catalog and select ActiveX(TM) Sample Application).
Figure 5-7
ActiveX(TM) Sample Application Catalog
Figure 5-8
Viewing the Barcode Sample Application
Figure 5-9
Barcode Sample Host (Active Script Host
Worker)
Figure 5-10
Launching the Control Browser
Figure 5-11
Launching the VBScript Editor
End Sub
The code shown above enables the Barcode Scanner Control, using
the variable defined within the Active Script Host worker, and
initialises the Variant Store associated with the Active Script Host.
The Enable method, Enable (m), of the Barcode Control can be
found in the Object Viewer window as shown below.
Accessing Methods and Properties The Object Viewer window of 5
Figure 5-12
VBScipt Editor - Object Viewer Window
Figure 5-13
VBscript Editor - Viewing Associated
Events
ActiveWorkGroup.Index = 2
end if
End Sub
Figure 5-14
VBscript Editor - Viewing a User Procedure
BarcodeTest = True
else
BarcodeTest = False
end if
else
BarcodeTest = False
end if
End Function
inactive. This could lead to events being lost if the Active Script
Host is being used to manage an ActiveX control which can receive
events at any time, such as a TCP/IP Control.
You can avoid this by placing the Active Script Hosts in the
application such that they are always active, using either of the
following methods:
Ensure that the Active Script Hosts are concurrent with the
transaction processing application
Develop a separate application to run concurrently with the
transaction processing application, to which it passes
information using shared stores.
You can debug the script used by the Active Script Host worker by
selecting Start | Run and entering
<drive:>\<global>\test\xfs\dll\axscripthostoptions.exe at the
command line. This will display the following dialog window:
Figure 5-15
Debugging Scripts
Chapter 6
Managing Modules
Overview 6-1
Overview
Overview 6
This tutorial shows you what happens when you try to access
components in a module that you do not own.
Figure 6-1
Opening the Customisation Layer Project
Figure 6-2
Saving the Project with a New Name
Figure 6-3
Opening the Flow Control Catalog
Figure 6-6
Viewing the New Module
Note: If you try to delete a module, you will only be offered the
choice of deleting one of the modules you own. You cannot delete
modules you do not own.
The default module is always the current module in use, and the
Default Module 6
Figure 6-7
Creating a New Worker
With the Flow Control
Catalog selected, create a
new worker.
When you try and modify a component, the Author looks at the
component to see which module is associated with that component.
the Author then checks the module’s details for ownership. If you
are not the current owner, you will not be allowed to change the
component.
So far, you have opened the Customisation Layer project, saved it
with a different name and created a module. You do not own any
other components in the current project, as you have not created
any.
You will now create a catalog. This will be assigned to your default
module.
Once you have created the catalog, you can create a worker, as
follows:
Figure 6-8
Creating and Naming a Catalog
Select Timer in
this window.
Figure 6-12
Transferring the Timer Worker to a
Temporary Module
Select the Advanced tab.
Transfer the Timer Worker to the Temporary
Module and select Close.
Figure 6-13
Changing the Timer Name
Again, open the worker’s dialog box, and change the name
of the Timer worker to Delay. Select Close.
You are now going to transfer the Timer Worker to a module you do
Transferring the Worker to not own.
a Module You Do Not
Own 6
As in the previous section, open the Timer Worker’s dialog and select
the Advanced tab.
Figure 6-14
Transferring the Timer Worker to a Module
You Do Not Own
Figure 6-16
Viewing Project Modules and Settings
6
Figure 6-17
Changing the Module Owner Change the owner of the Temporary
Module to a name in the Owner list
and select OK.
Repeat the above steps, but this time try to transfer ownership of the
Temporary module to a different name.
You will discover this time that you cannot transfer ownership of
the module. This is because you no longer own the module.
Move a Module 6
In this tutorial, you will move the contents of one module to another
module using two methods, as follows:
Move based on ownership, which means you can only move
modules that you own
Move to the default module, which moves a catalog’s contents,
owned by you or another user, to the default module
This type of move lets you move all of the components in any
Module Move Based on module that you own into another module you own, which is not
Ownership 6
set as your default module. This function is useful when you need to
incorporate work from one module into another module you are
working on.
The Move To Default Module function lets you move the contents of a
Move to the Default catalog directly into the module that you have set as your default
Module 6
module. This function allows you to incorporate another person’s
work, or your own, into your default module.
Figure 6-19
Using the Move To Default Module Select the ‘Move to Default
Function Module’ menu item from the
Catalog menu.
Note: The Tools menu has a Module Copy option, which also lets you
copy a module to the default module. If a default module does not
exist, the copied module is named “Copy of...”
Summary on Modules 6
Chapter 7
Team Development
Overview 7-1
Overview
Overview 7
Figure 7-1
Concurrent Team Development
Figure 7-2
Un-networked Team Development
Inter-Team Transfer 7
Figure 7-3
Inter-Team Transfer Development
For large developments, the project team can contain the following:
Team Development 7
Lead developer
Developers
Other non-technical experts such as graphics specialists.
In the development process it is a good idea to split a development
into separate areas. An effective model is to develop a top layer
from which other areas are called. The top layer would be
developed first using stubs to represent the areas which had not yet
Figure 7-4
Changing the Default Module
To modify a component that you do not own, you must ask the
Receiving Ownership of a current owner of the module containing the component to transfer
Module 7
the component to one of your modules.
If you are a new developer, you cannot receive ownership of a
component or module until you are added to the project and your
name appears on the list of names available for module transfer.
For your name to appear in a project, you must have worked on the
project at some time. This can be as simple as creating and deleting a
catalog. Two methods for doing this are outlined below.
With this method you take the given project, for example,
CoreSelfService.mpj, and add your name to it, as follows:
1 Open the project and create a module, assigning the module a
meaningful name. Your name is now present in the project.
3 On the lead developer’s PC, the project can be imported into the
lead developer’s project. The only difference in the imported
project is the new developer’s ownership details.
This method takes a little longer than the first but has the advantage
that the new developer does not need to go to the lead developer’s
PC. This may be of advantage where geographical locations make
the first method difficult.
This method can also be achieved more easily by saving the project
file to a shared network drive and making the changes to it before
importing from the network.
Read only components are displayed with their label font in italic
Read Only and Shared and light grey (see Figure 7-5). A darker shade of grey indicates that
Components 7
the component is also shared.
Also notice that the component ID of the worker is displayed in the
line below the worker name. This helps when documenting any
work that requires the context of the change to be indicated in a
worker hierarchy.
Figure 7-5
Read Only and Shared Component
Display
Figure 7-6
Status Bar - Component Status
dialog box (see Figure 7-7), the owner of the module is indicated
and the number of components contained within the module is
shown. This makes it easier to identify ownership of the work
within a team and also shows how the authored work is partitioned.
It is also possible to identify empty modules that are no longer
associated with the project. These empty modules can be deleted
using the Delete Empty option on the Modules menu.
Figure 7-7
Module Selection Dialog Box
Selecting Highlight | Off on the Modules menu returns the label colours
back to the original state, based on the edit and share status of the
components.
Figure 7-8
Module Highlight Status
Merging Projects 7
You merge two projects by importing one into another. You will not
lose any changes when importing a project, as the ownership
feature of the Author ensures that all components associated with
modules are protected. After the project is imported, you can select
any of the workers provided in the newly imported project.
To merge two projects, complete the following steps:
1 In the Author open you project, and select File | Import.
Figure 7-9
Selecting All Catalogs in the Imported
Project
The merge process is started and you are offered the option to view
a report of the merge. If you select No, the merge proceeds to
completion. Select Yes to see the effects of the merge and decide
whether to continue or cancel the merge.
If you choose to continue with the merge, you can view discarded
components in the Trash window when the operation is complete. If
you wish to retrieve components from the Trash window, you can
move them to another location.
If a component is not associated with a module and exists in both
projects, the one with the latest timestamp is retained and the other
discarded.
Every component has a timestamp containing the data and time a
component was last modified. The timestamp is used to identify the
latest version of a component when merging projects.
Producing a Workers Select the Workers option to produce a report based on all the
Report 7
5 Select Data | Import External Data | Import Data and select the report file
from the directory in which it was saved.
The following example shows the worker report data imported into
a spreadsheet:
Figure 7-10
Worker Report Data
Figure 7-11
Catalog Report Data
Figure 7-12
Component Report Data
This option reports the name of the module, who owns the module
Module Ownership Report 7
(along with User ID), and how many components are associated
with the module.
This can be useful for tracking team development work carried out
over a period of time. It is especially useful if the Project Module
structure has been created based on functionality rather than
developer. In this way, a different area of functionality can be
assigned to team members by transferring ownership of the Module
based on the User ID of the developer.
As the report file is a CSV file, it can be opened directly in a
spreadsheet, without importing it first.
To generate a Module Ownership report, complete the following:
1 If the project is not already open in the Author, open it now, and
select Modules | Ownership Report.
Figure 7-13
Module Ownership Report Data
Appendix A
Troubleshooting
Overview A-1
Overview
Overview A
Figure A-1
Error Message Help
manipulation.
To avoid this, do not use ASCII control characters in text strings that
are to be displayed.
Figure A-2
Performing a Final Build
Figure A-3
Running a Completeness Check
4 When you are prompted for a build name, provide a name, for
example myapp, without an extension. The default file type to
save as is exe. The default location for the compiled build is your
<working> directory, but you can create another directory at
this point if you prefer.
Figure A-4
Specifying a Build Name and Location
Appendix B
Advance NDC Worker Support
Overview B-1
Overview
Overview B
New Workers B
Passbook Printer B
Barcode Resource ID *
Cheque Acceptor
Cheque Capture
Cheque Ejector
Coin Dispenser (replaces Coin Dispense)
CPM Initialise
CPM Tamper Indicator (TI)
CPM Resource ID *
Extended Cash Stacker
First Cash Handler Resource ID *
Integer Array Element
NDC Delete RSA Key
NDC Print Coupon
Receipt Control
Resource Status Checker
Resource Initialiser
RSA Key
Second Cash Handler Resource ID *
XML Config File Loader
* Resource ID workers are used solely for Advance NDC functions
(Device Variant Getter and Fitness Getter) as the Advance NDC
application does not need to perform resource negotiation.
Supported Workers B
Cancel Collector
Operator Key
Supervisor Data Collector.
Envelope Depositor
Envelope Depository T.I.
Envelope Presenter
Fitness Getter
Resource Initialiser
Terminal Suspend
reader/writer (MCRW):
Card Acceptor
Card Answer To Reset (ATR) Reader
Card Capture
Card Ejector
Card Track Reader
Card Track Status Getter (Track 3 only)
Card Track Writer
MCRW TI
Track 1 Decomposer
Comms Opener
Comms Closer
Message Sender
Message Receiver
NDC Message Sender
NDC Message Receiver
Status Activator
Status Getter
customisation data:
Configuration Data Saver
Customisation Data Decomposer
Customisation Data Initialiser
Customisation Data Saver
Date
Handle Computer
Handle Store
Integer Computer
Integer Store
Real Computer
Real Store
Setter
String Computer
String Store
Handle Computer
Tester
Time
XML Config File
Deformatter
Formatter
Structure
Fixed Length Field
Open Length Field
Separator Field
Supplies Data Formatter
Table.
Persistence Wiper
Persistent Integer Store
Persistent Real Store
Persistent String Store
Sharable Integer Store
Sharable Real Store
Sharable String Store
Director
Integer Signaller
Caller
Listener
Pass-thru
Selector
Synchroniser
Timer
Variable Timer
Active Control
Active Script Host
Automation Object
COM Initialiser
Integer Signaller
Variant Store
Web Event Monitor
Web Page Loader
Statement Capture
Statement Ejector
Statement Page
Alarm
Modified Workers B
IFD Alarm The IFD Alarm worker class and its help have been
removed from the APTRA Author as the intelligent
fraud device (IFD) is no longer supported
Picture Now used to support BMP, JPG, TIF, PNG, GIF and
Displayer PCX/DCX image file formats; dependency on
LEADTOOLS removed
Table B-3 lists workers that were modified for Advance NDC 3.04.
Worker Change
Night Safe This previously waited for the time specified in the
Closer Door Close Time attribute before signalling for both
basic and enhanced night safes.
For basic night safe, this worker signals if a bag is
dropped while the worker is active. If no bag is
dropped, the worker signals as in previous releases.
For enhanced night safe, this worker signals if the
door is closed while the worker is active. If the door
is not closed, the worker signals as in previous
releases.
NDC Processing This worker now handles the execution of one state
State Executor only and then signals. Therefore, the Transaction
Request signal and Close State signal are no longer
supported
SSDS DLL This worker can now link DLLs indirectly through
Interface the registry using a new attribute of Application
Link
Table B-5 lists workers that were modified for Advance NDC 3.02.
NDC Export Changed name from NDC EPP RSA Export Key and
Encryptor Data modified for enhanced RKM. Now supports
retrieval of encryptor capabilities and status and
retrieval of the ATM random number.
NDC Import Changed name from NDC EPP RSA Import HSM
RSA Key Public Key and modified for enhanced RKM. Now
supports loading of any type of RSA key into the
encryptor in the EPP.
NDC RSA Changed name from NDC EPP RSA Import DES
Import DES Key Key.
Table B-6 lists workers that have been modified for Advance NDC
3.00.
Worker Change
Supervisor Data Now works only in two basic modes: numeric and
Collector hexadecimal; new signal introduced for Cancel
operation, due to CEN-XFS limitations.
Card Track Now used to retrieve the track data previously read
Reader by the Card Acceptor.
New signal on read failure.
Worker Change
Table B-8
Runtime Errors Mapping to Signals
9 The page number specified is outside the Passbook Page Turner Bad
range defined for the current passbook
10 The line number specified is outside the Passbook Printer Line number 0 is selected
range defined for the current passbook
Unsupported Workers B
The following workers exist in the authored flow for worker factory
Stubbed Workers B
Consumer Token B
This worker has been replaced by the XFS Front FDK worker, which
requires the NDC Data Collector to be active during key entry.
This worker has been replaced by the XFS Front Key worker, which
requires the NDC Data Collector to be active during key entry.
The beeping of both the front and rear keyboards can be configured
at the service provider (SP) level.
Logo Setter B
This worker class is no longer supported but you can set a logo by
updating the K09 screen definition in resrvd.def with the appropriate
printer controls for downloading the logo file to the printer.
As Advance NDC does not support the BOP, there is no support for
Basic Operator Panel the following workers:
(BOP) Workers B
The following Security workers are not used and are not supported
Unsupported Security in Advance NDC:
Workers B
BSC 3
FBSS Passthru
Hayes Modem
HoneyWell
S4 Message Sender
SNA 3624
SNA X.25 QLLC
X.25 LAPb
XModem
As linked FITs are not supported in Advance NDC, the Linked FIT
FIT Workers B
Advance NDC:
Cash Accessibility Checker
Extended Cassette Type Enabler
Note Initialiser
Note Mixer
Advance NDC:
Offline
Offline Status
Note Mixer
Session Requester
Appendix C
Extending the APTRA Author
Runtime
Overview C-1
Overview
Overview C
Note: If you previously used the ASC() function with the OS/2
version of SSDS, you should be aware that the ASC() function
returns different values with Microsoft Windows than with OS/2. In
both OS/2 and Windows, the ASC() function returns an integer
ASCII/EBCDIC Functions C
between the host and the SST application developers. Messages may
be Character Based or Character/Binary Based.
Character Based Messages consist entirely of character fields, that is
all of the message fields contain character (String) data.
Character/Binary Based Messages consist of a combination of
character fields and binary (Integer) fields, that is some of the
message fields contain character data and some contain binary data.
Typically, the entire content of Character Based Messages should be
translated, whereas only character fields of Character/Binary Based
Messages should be translated.
message.
corresponding decimal value using the Alt key and the numeric
keypad.
For example, if the Message Identifier characters are '02' EBCDIC,
this is equivalent to F0H F2H, which converts to 240 242 decimal.
Use the numeric keypad to enter <Alt>240 <Alt>242.
When the Message Receiver worker signals, transfer control to a
work group which contains an Assigner worker, with the attributes
Expression EBCDICToASCII$(InMsg$) and Parameter List
InMsg$.
conversion, the source code for these functions has been made
available should you want to change their behaviour. The character
conversion table used in the default implementation of the functions
is provided in the following pages.
For details of how to change the default tables, refer to the APTRA
Advance ADE, Programmer's Guide.
The following table specifies the default ASCII to EBCDIC
conversion used by the ASCIIToEBCDIC function:
Appendix D
Guidelines for Developing
Applications
Overview D-1
PCI DSS/PA-DSS Considerations D-1
Overview
Overview D
Recommended Guidelines D
These guidelines assume you are familiar with using the Author,
and you have read the Author documentation, and/or attended an
Author course. As such, they are not step-by-step instructions but
stages to follow when you are modifying or extending an Author
application.
Before and during these guidelines, it is good practice to back up the
provided projects, and the projects you are working on.
NCR recommends that you adhere to the following guidelines
when preparing to modify or extend any application:
1 With the required project file open, create a new module for
your development. Change the default module name you are
prompted with to an appropriate and meaningful (recognisable)
name.
8 Replace the top worker and any other Director workers you
wish to change, down to the required level. Make changes at the
Director level wherever possible, to enable easier re-use of your
own changes, and for subsequent releases.
9 Ensure all the signals associated with the workers you have
changed are reconnected to the required workers.
12 Share the top workers from the catalogs into the main work
flow.
separate project files (instead of storing them all in one large project)
are as follows:
The application will take less time to initialise in the test
environment
The responsiveness of the Author will improve when running
an application in this way
The project merge time is reduced.
4 Open the original project again and repeat steps 2 and 3 to create
another project containing only the components for the other
application.
5 Where the applications use Sharable Stores, ensure that the Store
Name attributes have identical values.
We will now assume that you have two projects named app1_prj.mpj
and app2_prj.mpj which contain application top workers ‘App1’ and
‘App2’ respectively.
2 Set the DLL Name attribute of the SSDS DLL Interface worker to
refer to the DLL generated for App2 as part of the Final
Application. The full pathname is required (that is,
c:\working\app2.dll).
3 You can now start this application and App2 will run.
The above is an outline of the approach and can be adapted
depending on how many applications you have, how many you
wish to run on your PC at the same time, and how many projects
you have.
Note: All of the above are achieved because the Author does
not have to do any checking of the contents of the sub-DLLs.
3 Find all the Data Stores that are shared between the controlling
application and the intended sub-application. If some of the
Stores do not need to be shared, then replace them with other
workers. If there are some Stores which need to be shared,
replace them with Sharable or Persistent Stores.
7 Open the original project again and repeat steps 5 and 6 to create
another project containing only the components for the
controlling application.
8 Where the applications use Sharable Stores, ensure that the Store
Name attributes have identical values.
We will now assume that you have two projects named main_prj.mpj
and sub_prj.mpj which contain application top workers ‘MainApp’
and ‘SubApp’ respectively.
11 Set the DLL Name attribute of the SSDS DLL Interface worker to
refer to the DLL generated for the sub-application as part of the
Final Application. The full path name is required (for example,
c:\working\sub_app.dll).
Note: The SSDS DLL Interface worker has only one signal
which is triggered whenever the top worker in the
sub-application (it refers to) produces a signal. However, the
sub-application may return more than one signal. So that the
controlling application can handle all the signals returned, you
need to adapt its flow. This is described, later in this appendix,
in the section “SSDS DLL Interface Signal”.
The SSDS DLL Interface worker has only one signal which is
triggered whenever the top worker in the sub-application (it refers
to) produces a signal. However, the sub-application may return
more than one signal. So that the controlling application can handle
all the signals, you will need to adapt its flow. We describe this in
the following steps.
Step 1
In this example, Transaction is the top worker of the
sub-application. We will assume that the sub-application’s top
worker can generate two different signals, ‘good’ or ‘bad’.
In order for the controlling application to know which signal has
been generated by the sub-application (good or bad), a Shared Store
will be used.
First of all, you need to add work groups to the sub-application and
place workers in them which set a Shared Store to one of two values.
Each value identifies either the good or bad signal generated.
The following diagram shows how to do this.
Note that the SSDS DLL Interface worker (Sub App) can only
generate one signal. Therefore, when the sub-application signals,
the Sub App worker signals.
By adding a Selector worker to the application, we can use this to
determine what signal was generated by the sub-application (good
or bad).
The same Sharable Store used in the sub-application (see Step 1) can
be added to the Selector worker. Depending on the value in the
Shared Store (either 1 or 2), the Selector will generate a signal to
force the correct path through the application.
Appendix E
Reserved User IDs
Overview E-1
Overview
Overview E
This appendix lists the reserved user IDs that are used in the
Advance NDC authored projects. These user IDs must not be
assigned to anyone else, otherwise duplicate component IDs could
be created.
The following list gives all the reserved user IDs in Advance NDC,
alphabetically by row. For details of the format requried for new
users IDs, see section “User IDs” on page 2-3.
bm bna cb cm db
dc df dha di dma
HC185040 hg im ja513225 js
jv kv kn laptop laya
lb lg ly ly250014 MBYI
mk ms murthy mw ncr
pa pad pc pd pk
VKA vm yc ziy yy
Appendix F
Display Considerations
Overview
Overview F
Figure F-1
Effects of Monitor Burn-in
1 2 3
scale. Gradations between black and white for any one pixel are
achieved by strobing the pixel on and off. Some grey scale
representations of colours appear to have moving interference
patterns. This can be avoided by creating a shaded area by means of
turning on every other pixel fully, rather than strobing all pixels
within a given area.
The following diagram shows two groups of four pixels. All four
pixels in the left-hand group are strobed at 50% duty cycle. The
right-hand group shows how a similar grey scale can be achieved
with a lower risk of unwanted optical effects. In both cases, the eye
perceives the same amount of grey over the area.
Figure F-2
Reducing Optical Effects
Key:
Pixel on
Pixel strobed
Pixel off
Appendix G
Related Documentation
Overview G-1
Overview
Overview G
Table G-1
APTRA Author Documentation
APTRA Author Help Windows Context-sensitive help for the Author and runtime
Help errors.
Runtime Core Help Windows Context-sensitive help for the Runtime Core
Help Authoring components and runtime errors
Self-Service Core Help Windows Context-sensitive help for the Self-Service Core
Help Authoring components
Basic Self-Service Help Windows Context-sensitive help for the Basic Self-Service
Help Authoring components
Special Self-Service Help Windows Context-sensitive help for the Special Self-Service
Help Authoring components and runtime errors
Statement Printer Help Windows Context-sensitive help for the Statement Printer
Help Authoring components and runtime errors
Advance NDC Worker Class Help Windows Context-sensitive help for the Worker Classes
Help provided in the Advance NDC Customisation Layer
and NDC Core catalogs. Also includes
context-sensitive help for additional Advance NDC
Worker Classes which are provided for inheritance
purposes.
Advance NDC Passbook Printer Worker Class Windows Context-sensitive help for the Worker Classes
Help Help provided in the Advance NDC Passbook catalog.
These worker classes are provided to allow users to
develop their own passbook printer application.
Advance NDC Voice Guidance Worker Class Windows Context-sensitive help for the Worker Classes
Help Help provided in the Advance NDC Voice Guidance
Workers catalog.
Advance NDC Application Core Worker Class Windows Context-sensitive help for the Worker Classes
Help Help provided in the Advance NDC Application Core
catalog.
Table G-2
Other NCR Documentation
APTRA Advance NDC, Introduces Advance NDC and gives full details of
Overview the Advance NDC and related documentation.
B006-6597
APTRA Advance NDC, PDF Provides application programmers with reference
Reference Manual information for Advance NDC: States, Screens,
B006-6180 and the message formats between Central and the
SST.
APTRA Advance NDC, PDF Describes the differences between Advance NDC
Multi-Vendor Support on NCR SSTs and Advance NDC on other
Reference Manual vendors’ SSTs, and how to implement Advance
B006-6344 NDC in a multi-vendor environment.
APTRA Advance NDC, PDF Describes how to install and configure Advance
Developer’s Guide NDC>. It also describes how to migrate or
B006-6046 upgrade to Advance NDC.
XFS Simulator for APTRA Microsoft HTML Help (CHM) Context-sensitive help for the XFS Simulator.
Appendix H
APTRA Author GUI Reference
Overview H-1
Menus H-2
Overview
Overview H
Menus H
Table H-1
Author Menus
Menu Functions
Menu Functions
Open Picture - creates a new workspace and displays the picture of the selected Application or
Coordinator in it
Open Co-ordinator - creates a new workspace and displays the picture of the selected worker’s
coordinator in it
Open Settings - displays the properties of the selected Authoring component
Show - shows the selected worker’s picture
Hide - hides the selected worker’s picture
Test Start - starts the test application running from the selected Authoring component (the
APTRA Simulator needs to be installed to run test applications)
Test Stop - stops the test application running
Check Completeness - checks the completeness of the selected component
Build Factory - builds the Worker Factory for this project
Build Final - builds the Final Application for the selected application
Build Application Links - builds links for selected state types, reply functions and application
DLLs
Edit User Name - allows you to change the name associated with your User ID
Module Copy - copies the components in a Module and deletes the old components
Defragment Project - defragments the currently open project
Print Report - generates a Worker Report or Author Forms for the currently open project
Tile - arranges all open windows side by side so that they are all visible
Cascade - arranges all open windows in an overlapping pattern so that their title bars are
visible
Tool Bars H
Figure H-1
Tool Bar Icons
Move the cursor across the icons on the tool bar. Tool tips are
displayed for each active icon. Information is also provided for each
icon on the status bar at the bottom of the Author window
The tool bar offers the following functions:
File, Save
Edit, Cut
Edit, Copy
Edit, Paste
Edit, Share
Edit, Find
View, Show
View, Hide
Zoom, Zoom In
Zoom, World
On-line help is available for the Author and each of the Runtime
components.
In the following sections, we describe how to obtain help for the
Author and the Runtime components.
We also describe how to obtain help for error messages that can be
displayed when developing and testing an Author application.
pull-down menus)
Dialogs - describes the dialogs provided for entering various
types of information
Objects - describes the various components of the Author.
Concepts - describes the concepts and terminology used in the
Author.
The following table gives details of the help for the Author.
Menus either Place the cursor over a menu item, and press <F1>.
Dialog either With a dialog box selected, select the Help button.
boxes This gives you help on the dialog.
Note: If the dialog box is a Settings dialog and an
Authoring component is selected in the Author,
then the help for the component is displayed, not
the help for the dialog.
Note: In addition to the above methods for getting help, each of the
above help topics can be found in the Contents and Index windows
of the Author on-line help. There are also links throughout the
on-line help system to various help panels, as appropriate.
Catalogs 1. Select the Title Bar icon in the top left of the catalog
window.
2. Select Help.
Note: In addition to the above methods for getting help, each of the
above components can be found in the Contents and Index
windows of the Author on-line help. There are also links
throughout the on-line help system to various help panels.
Authoring errors
Runtime errors
Simulator errors—refer to the documentation accompanying the
APTRA Simulator for more information.
Authoring Errors H
Figure H-2
Error Message Box
To obtain help for the error, select the Help button. Additionally,
help for all authoring error messages can be obtained by selecting
Author Error Messages from the Contents or Index windows in the
Author on-line help.
Figure H-3
Runtime Error Dialog Box
Figure H-4
Menu Item Help
When you require help on a specific worker, you can select Help from
the worker’s pop-up menu.
Figure H-5
Timer Worker Help
For help on the worker class help layout, select Help, Author Help Topics,
and open the Overview help for any runtime item (for example,
Advance NDC Worker Classes). Select the worker class help layout
link.
For other topics, select the Contents or Index tabs.
For general Windows help guidelines, select Help, General Help, and
then Help On Using Help.
Glossary 0
Index 0
timestamp 7-11
user ID 6-10
Passbook printer
P modified worker classes B-21
Pass-thru worker B-10
PC directory structure 2-6
directory types 2-7
PCI DSS/PA-DSS xxxi, D-1
Performing a module copy 5-11
Persistence wiper worker B-9
Persistent and sharable stores workers B-9
Persistent integer store worker B-9
Persistent real store worker B-9
Persistent string store worker B-9
Picture displayer worker B-11
PIN block encryptor worker B-12
PIN collector worker (unsupported) B-24
PIN length adjuster worker B-18
PIN retries updater worker B-12
Print paragraph worker B-6
Printer code page definer worker (unsupported) B-27
Printer workers B-6
Printer workers (unsupported) B-27
Project administrator 7-3
Project Compare 7-8
project coordinator 7-3
Project directory 2-8
Project reports
catalogs report 7-14
components report 7-15
module ownership report 7-16
workers report 7-13
Projects
development planning 7-2
owning more than one module 7-6
receiving ownership of a module 7-6
team development 7-5
importing 7-13
management features 7-1
saving 6-3
NCR welcomes your feedback on this publication. Your comments can be of great value in helping us improve
our information products.
Cut
You may send your comments to us electronically. See over for details.
Circle the numbers below that best represent your opinion of this publication.
Cut
Fold
If we may contact you concerning your comments, please fill in the information below:
Name:
Organisation:
Company:
Address:
Phone: Fax:
Thank you for your evaluation of this publication. Fold the form where indicated, tape (please do not staple),
and drop in the mail.
F 8763-0695
Fold
Affix
Postage
Stamp
Here