NP Retail Support

Search




Table of Contents
1 Touch Screen (Transcendence Client)
1.1 Protocol to switch between our different POS types
1.2 Major Tom Setup
1.3 Concept of Physical Device ID
2 Setup of our POS in Transcendence
2.1 POS Menus
2.2 Setting up the POS Menus buttons
2.3 Action Type
2.4 Action Codes Parameters
3 Sample of Action Codes & Parameters samples
3.1 Pictures in POS Menu Button
3.2 Trans. EDIT membership function
3.3 Trans. Accessory not displayed on Sale Line
3.4 Trans. Actioncode correction for Table Buzzer
3.5 Trans Action Code correction for Insert Comments
3.6 Filter on menu buttons for running pages and reports
3.7 Item Lookup on Stock Keeping Units
3.8 Item Lookup using Table Filters
3.9 ToolTips on the menu buttons
3.10 POS Inventory Overview
3.11 Negative Quantity
3.12 Edit/View Item Card
3.13 Sales Order (menu)
3.14 Hyperlink
3.15 POS Lock Action
3.16 Customer List Filter in Transcendence
3.17 Change Description on Item in Action Code ITEM
3.18 Changing of quantity by pressing a number and star
3.20 List of POS Menus Buttons with Security:
3.21 Setting Up a VAT Free Button in Shops
3.22 Export/Import in POS Menu Button
4 POS Setup
5 POS Actions
6 Recognition of data in the EAN Box in our POS
6.1 Unit Identifier Dissociation Type
6.2 Identifier Dissociation Action Dispenser
6.3 Unit Identifier Dissociation Type on Search Description
6.4 Scanning Exchange Label
7 Scanning Boarding Pass in Airports Duty Free Shops
7.1 Boarding Pass
7.2 Function
7.3 Setup of Boarding Pass Function
7.4 Use of functionality
8 NPR POS Menu Buttons/Actions
9 POS Views
9.1 How to use the POS Views
9.2 POS Default Views
9.3 POS Menus Views
10 Conversion of Touch Screen into Transcendence
10.1 Default Conversion
10.2 Why does the tool not convert all the buttons?
10.3 Practical Tips and Trick
10.3.1 Menu Level v/s Popup Menu
10.3.2 MORE_SALE_FUNC
10.3.3 Filters in POS Menu v/s Different Views
10.3.4 Appendix


Touch Screen (Transcendence Client)

Protocol to switch between our different POS types

From Standard to Transcendence:

  1. On the configuration page  , change Client Type from Standard to Transcendence
  2. Sign Out
  3. Exit Major Tom Client
  4. Start Major Tom Client

From Transcendence to Standard

  1. On the configuration page  , change Client Type from Transcendence to Standard
  2. Click  and confirm
  3. Sign out
  4. Exit Major Tom Client
  5. Start Major Tom Client
  6. Sync Stargate Assemblies – use the button in POS
  7. Exit Major Tom Client
  8. Start Major Tom Client

Note: We need to make sure that the POS for the clients have the "Sync. Stargate Assemblies" function / button in our "Standard" POS, and verify that it works. It is defined in Touch Screen Functions and the Button configured in Touch Screen Setup.

Major Tom Setup


On the configuration menu of Major Tom, change the Client Type to Transcendence. Then you will have access to Transcendence POS.

Concept of Physical Device ID

With Transcendence, we are introducing a new concept that the hardware device (a computer or Ipad) is directly associated with the POS Unit.
Hence we nominate the hardware as the POS Unit. Unlike currently, the Register is not fixed to a hardware.
A register is virtual and not physical.
Whereas the POS Unit will be attached to a physical device.

Whenever you use the POS on a hardware device for the first time, a POS Unit Identity record needs to be created.
You will hence have a pop up that comes up. The Device ID of the hardware will be detected and an identity initialization is done.
Our consultant in the store will need to establish with the project manager of the store which POS Unit will be associated with the device & does the setup on the Default POS Unit No.

Setup of our POS in Transcendence

POS Menus

The setup of POS Unit layout (equivalent to Touch Screen setup) is done in this menu. The concept consists of multiple menus. We do not have fixed pages like "Other Functions, Discounts, etc". There are possibilities of creating different menus to group set of buttons. Still the two main screens are the Sales POS Layout & Payment POS layout. Currently we have kept the same layout as the Java version. But we have provision to make even the layout flexible in the future, by coding it in the menu POS View List. (Refer to Section 1.9.5)
Menu: Retail > Sale > Administration > POS Menus

Code

Caption

CAFE-BOTTOM

Sale Cafe Bottom

CAFE-LEFT

Sale Cafe Left

CAFE-PAY-BOTTOM

Payment Bottom

CAFE-TOP

Sale Cafe Top

CUSTOMER

Customer Functions

DISCOUNT

Discount Functions

DISCOUNT_SCHEMES

Discount Schemes

ENT-BOTTOM

Sale Bottom

ENT-LEFT

Entertainment Left

FASH-LEFT

Fashion Sales Left

FASH-PAY-BOTTOM

Payment Bottom

FASH-SALE-BOTTOM

Sale Bottom

GIFTCARD_REDEEM

Redeem Gift Card

GIFTCARD_SALE

Gift Card Sales

HOSPGETFROM

Get sale from table

HOSPITALITY

Hospitality

HOSPMOVETO

Move sale to table

HYPERLINKS

Hyperlinks

ITEMS

Items Functions

LOGIN

Menu on Login Screen

MCANCEL/DELETE

Cancel/Delete

MCREDIT_VOUCHER

Credit Voucher

MCUSTOMER

Customer Functions

MDISCOUNT

Discount Functions

MDISCOUNT_SCHEMES

Discount Schemes

MGIFTCARD_REDEEM

Redeem Gift Card

MGIFTCARD_SALE

Gift Card Sales

MHYPERLINKS

Hyperlinks

MIMPORT_SALES

Import Sales Functions

MITEMS

Items Functions

MLOGIN

Menu on Login Screen

MMEMBERMGT

Member Management

MMORE_PAY_FUNC

Payment Funtions

MMORE_SALE_FUNC

Sales Functions

MORE_PAY_FUNC

Payment Funtions

MORE_SALE_FUNC

Sales Functions

MPAYMENT-BOTTOM

Payment Bottom

MPAYMENT-LEFT

Payment Left

MPAYMENT-TOP

Payment Top

MPINPAD

Pin Pad Functions

MPOS

MPOS Functions

MPRINTEXCLABEL

Print Exchange Label

MPRINTITEM

Print Item Price

MPRINTRECEIPT

Print Receipt

MPRINTS

Print Function

MRECEIVABLES

Customer Receivables

MREPORTSALES

Report Sales List

MRETURN

ReturnSales

MSALE-BOTTOM

Sale Bottom

MSALE-CTRL

Main Control

MSALE-LEFT

Sale Left

MSALES_ORDER

Sales Order Menu

MSALE-TOP

Sale Top

MSTATISTICS

Statistics

MSYSTEM_MENU_LEFT

System Menu

MSYSTEM_MENU_RIGHT

Function Menu

MTAXFREE

Tax Free Functions

MTICKETMGT

Ticket Management

PAYMENT-BOTTOM

Payment Bottom

PAYMENT-LEFT

Payment Left

PAYMENT-TOP

Payment Top

PINPAD

Pin Pad Functions

PRINTS

Print Function

REST-LEFT

Sale Cafe Left

REST-TOP

Sale Cafe Top

RETAIL_DOCUMENT

Retail Document

SALE-BOTTOM

Sale Bottom

SALE-CTRL

Main Control

SALE-LEFT

Sale Left

SALES_ORDER

Sales Order Menu

SALE-TOP

Sale Top

SIM-SALE-LEFT

Sale Left

SYSTEM_MENU_LEFT

System Menu

SYSTEM_MENU_RIGHT

Function Menu


The notion of Menus is that they give rise to sub-menus and sub-sub-menus etc. We are in an infinite world where we can go down menu levels. Of course everything is in the balance between our imagination & the practicality requires by a business.
The Touch Screen menus are created as follows:
1st Step:
Create a menu in the POS Menus screen on the RTC. Then under the menu, we need to create what buttons will be using in that menu. To do this, we go to the Home Ribbon, we select the "Button" shortcut.

2nd Step:
From the POS Menu Buttons, we will create touch screen "Button" that we need. These buttons will have an Action Code which will trigger an action.
The action has preset parameters which need to be modified if required.
From the Home Ribbon, we select the Parameters shortcut and list of values will be available to choose from.

In the above example, we created a set of buttons that is grouped under a POS Menu "SYSTEM_MENU_RIGHT". The latter is attached to a main menu known as Function Menu.
And it is used in the predefined System Menu LOGIN.
The System Setup & Function are Popup Menus where we can define specific buttons for each function we want to group under the menu.

We can even have sub-menus at this level. Hence visually, we have the login screen as below.
Fixed layouts:

  1. Login

The layout of the login menu as shown in the above section is fixed.

The POS Menus consist of Pop-up Menus that users can define as they go along as well as Fixed Menus. When we say Fixed Menus, it the screen layout that is fixed but not the POS Menu Buttons.

  1. Sale Screen


The details of POS Menu Buttons within the POS Menus depend on the requirements of the client. But to keep a standard, the SALE-TOP & SALE-BOTTOM have a set of default buttons.
Nevertheless, they can be changed per client's requirements.

  1. Payment Screen


The details of POS Menu Buttons within the POS Menus depend on the requirements of the client. But to keep a standard, the PAYMENT-TOP & PAYMENT-BOTTOM have a set of default buttons. Nevertheless, they can be changed per client's requirements.

  1. Menu Screen Layout

The layout of POS Menu Buttons can be changed within a Popup Menu. To do this, go to the Action Type: Popup Menu and select the "Parameters" from Home Ribbon in the POS Menu Buttons screen. You can define the number of columns & rows you want in the menu.
!worddav8134fb37ab0d6043e30e7d10e8fd928b.png|height=350,width=531!h2. Setting up the POS Menus buttons

The POS Menu Button defines the Action codes that are used to trigger an action. Below is an example of how it is set up:

ID

Description

Caption

Identification of the button – It is what will appear on the button in the POS Screen

Tooltip

It is a text fields that can be defined to appear as a tooltip if the cursor is placed on the button

Action Type

The types of actions that are triggered by the button:

  • Popup Menu
  • Action
  • Workflow
  • Item
  • Item Group
  • Customer
  • Payment Type

Action Code

The Action Codes are the workflows that has been defined for each action as defined in the POS Action section above.

Block

This check-box is used to block any action if required

Background Color

The background color that is displayed on the button

Foreground Color

The foreground color that is displayed on the button

Icon Class

The logo that is used on the button

Custom Class Attribute


Bold

Font Appearance

Font Size

The size of the Font

Position X

The positioning of the button on the POS screen uses a logic of X-axis & Y-axis. The Combination of these two settings will allocate a position in the grid position on the POS.

Position Y


Enabled

Check-box to enable the function

Cash Register Type

The button can be allocated to a Cash Register Type

Cash Register No.

The button can be allocated to a Cash Register No.

Salesperson Code

The button can be allocated to a Salesperson

Available on Desktop

The button will be available when using the client type: Desktop to login

Available in App

The button will be available when using the client type: App to login


Grid Position

Action Type

There are different types of actions that are triggered by the button:

  • Popup Menu
  • Action
  • Workflow
  • Item
  • Item Group
  • Customer
  • Payment Type


But it must be noted that in case of creating a button for an item, we can use both the "ACTION" or "ITEM" as action type, but with the appropriate action code and parameters as shown in example below.

POS Menu

Action Type

Action Code

Parameter Name

Parameter Data Type

Parameter Values

Tommy Hilfiger Allen Jacket

Action

ITEM

itemIdentifyerType

Option

ItemNo


Action

ITEM

itemNo

Text

80010


Action

ITEM

itemQuantity

Decimal

1







Napapijri Anorak AW13

Item

80011

itemIdentifyerType

Option

Item


Item

80011

itemNo

Text

80011


Item

80011

itemQuantity

Decimal

1


Action Codes Parameters

In computer programming, a parameter or "argument" is a value that is passed into a function. We allow functions to have multiple parameters.
Hence based on the parameters, we can produce specific output(s) and therefore, a single function can be called multiple times within a program and produce different output each time.
In Transcendence, there are POS Actions that can be used in multiple ways, depending on the parameters associated with the buttons.
A simple example will be to call a list on the POS screen. We have an Action Code that does the function to run a page: RUNPAGE.
Then as parameter, we set the "PageId" paramater as the page that we want to select:

We can also use "parameter values" to change the output of the same action code. In the example below, when the quantity is positive, it will insert a positive line in the POS Sale Line whereas if we set the quantity to negative, we can do the reverse action, by insert a negative line in the POS Sale Line.

POS Menu

Action Type

Action Code

Parameter Name

Parameter Data Type

Parameter Values

Tickets






Adult Ticket

Action

ITEM

itemIdentifyerType

Option

ItemNo


Action

ITEM

itemNo

Text

31001


Action

ITEM

itemQuantity

Decimal

1







Adult Return Ticket

Action

ITEM

itemIdentifyerType

Option

ItemNo


Action

ITEM

itemNo

Text

31001


Action

ITEM

itemQuantity

Decimal

-1

Another example will be to have a set of parameters that can be used to do different action, but using the same Action Code.
The output of the based on the different or rather the combination effect of the parameters.

You will notice that there is a color coding on the parameters. This helps to identify which parameters have DEFAULT value and which ones have been modified.
Black = Default Value
Blue = Modified Value

Sample of Action Codes & Parameters samples

POS Menu

Action Type

Action Code

Parameter Name

Parameter Data Type

Parameter Values

CUSTOMER






Customer Info

Action

CUSTOMERINFO

CustomerType

Option

CustomerInfo

Debit Info

Action

CUSTOMERINFO

CustomerType

Option

DebitInfo

Select Contact

Action

CUSTOMERINFO

CustomerType

Option

CustomerCRM

Customer (Sales History)

Action

CUSTOMERINFO

CustomerType

Option

CustomerILE

Receivables (menu)

Popup Menu

RECEIVABLES




Select Customer

Action

RECEIVABLES

Type

Option

SelectCustomer

Invoice Customer

Action

RECEIVABLES

Type

Option

InvoiceCustomer

Clear Customer

Action

RECEIVABLES

Type

Option

ClearCustomer

Clear Contact

Action

RECEIVABLES

Type

Option

ClearCustomer

Customer List (Local)

Action

RUNOBJECT

MenuFilterCode

Text

CUSLOCAL


Action

RUNOBJECT

ObjectId

Integer

0


Action

RUNOBJECT

ObjectType

Option

Page

DISCOUNT






Line Amount

Action

DISCOUNT

DiscountType

Option

LineAmount


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Line Discount Amount

Action

DISCOUNT

DiscountType

Option

LineDiscountAmount


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Line Discount %

Action

DISCOUNT

DiscountType

Option

LineDiscountPercentABS


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Extra Line Discount %

Action

DISCOUNT

DiscountType

Option

LineDiscountPercentREL


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Total Amount

Action

DISCOUNT

DiscountType

Option

TotalAmount


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Total Discount Amount

Action

DISCOUNT

DiscountType

Option

TotalDiscountAmount


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Total Discount %

Action

DISCOUNT

DiscountType

Option

DiscountPercentABS


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Extra Total Discount %

Action

DISCOUNT

DiscountType

Option

DiscountPercentREL


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Fixed 10% Line Discount

Action

DISCOUNT

DiscountType

Option

LineDiscountPercentABS


Action

DISCOUNT

FixedDiscountNumber

Decimal

10

Fixed 20% Line Discount

Action

DISCOUNT

DiscountType

Option

LineDiscountPercentABS


Action

DISCOUNT

FixedDiscountNumber

Decimal

20

Fixed 50 kr Line Discount Amount

Action

DISCOUNT

DiscountType

Option

LineDiscountAmount


Action

DISCOUNT

FixedDiscountNumber

Decimal

50

Remove Line Discount

Action

DISCOUNT

DiscountType

Option

ClearLineDiscount


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Fixed 5.25 % Total Amount Discount

Action

DISCOUNT

DiscountType

Option

DiscountPercentABS


Action

DISCOUNT

FixedDiscountNumber

Decimal

5.25

Fixed 25 % Total Amount Discount

Action

DISCOUNT

DiscountType

Option

DiscountPercentABS


Action

DISCOUNT

FixedDiscountNumber

Decimal

25

Fixed 100 kr Total Discount Amount

Action

DISCOUNT

DiscountType

Option

TotalDiscountAmount


Action

DISCOUNT

FixedDiscountNumber

Decimal

100

Remove Total Discount

Action

DISCOUNT

DiscountType

Option

ClearTotalDiscount


Action

DISCOUNT

FixedDiscountNumber

Decimal

0

Fixed 70 kr Line Discount Amount

Action

DISCOUNT

DiscountType

Option

LineDiscountAmount


Action

DISCOUNT

FixedDiscountNumber

Decimal

70

Fixed 150 kr Total Discount Amount

Action

DISCOUNT

DiscountType

Option

TotalDiscountAmount


Action

DISCOUNT

FixedDiscountNumber

Decimal

150







DISCOUNT_SCHEMES






Period Discount List

Action

RUNPAGE

PageId

Integer

6014455


Action

RUNPAGE

RunModal

Boolean

false

Mix Discount List

Action

RUNPAGE

PageId

Integer

6014452


Action

RUNPAGE

RunModal

Boolean

false

GIFTCARD_REDEEM






Redeem Gift Card (G)

Payment Type

G




Redeem (Electronic) Gift Card (GE)

Payment Type

GE




Redeem Foreign Gift Card (FG)

Payment Type

FG










GIFTCARD_SALE






(Electronic) Gift Card (Sales)

Action

SALE_GIFTVOUCHER

DiscountType

Option

Amount


Action

SALE_GIFTVOUCHER

PaymentType

Text

GE

Gift Card (Sales)

Action

SALE_GIFTVOUCHER

DiscountType

Option

Percentage


Action

SALE_GIFTVOUCHER

PaymentType

Text

G








For more details, see attachment which is an extract from RetailDemo2017_W1_EU:




Pictures in POS Menu Button

A picture can be used as a caption on the POS button. Navision will not store the picture but it is the link onto a picture on a website or web-shop that will be displayed.
For example, if our client has a web shop and we want to display as particular picture that is on it web shop on a button, then we must first identify the image address.

The next step is to copy the image address and use it in a java script on our POS Menu Buttons.
On the Caption, we define the https link, the size of the picture and description we want to display on the button which will be associated to the picture as follows:
<imgsrc=" https://static.homesandproperty.co.uk/s3fs-public/thumbnails/image/2016/10/17/16/applepie.jpg"height="70"> Apple Pie

Note:
The image address: https://static.homesandproperty.co.uk/s3fs- public/thumbnails/image/2016/10/17/16/applepie.jpg
The Height of the picture: height="70" (optimum is "85")
The Description on the button: Apple Pie
And then we will define the item we want to invoke, including the placement – same as the normal POS Menu Buttons.
Thus, we will have the picture displayed as the caption for the item 50006 on our POS:

Trans. EDIT membership function

The EDIT membership function was missing in membership management, it has been updated (case 289169) accordingly in NPR 5.36. Hence we have a full set of functions for membership:

  • Member Arrival
  • Select Membership
  • View Membership Entry
  • Regret Membership Entry
  • Renew Membership
  • Extend Membership
  • Upgrade Membership
  • Cancel Membership
  • Edit Membership


Trans. Accessory not displayed on Sale Line

Transcendence now support the function Accessories. We can attach an accessory to an item and it will displayed on the sales line when selling the item.

Trans. Actioncode correction for Table Buzzer

The INSERT_TABLE_BUZZER POS Action has been modified to cater for more than one type of input format. From now on, we have the possibility to add a parameter so that the users can select either a NUMPAD or a TEXT format for INPUT TYPE in the INSERT_TABLE_BUZZER POS Action.
The parameter for the DialogType is either Numpad or TextField.

Trans Action Code correction for Insert Comments

New changes has been brought on the function "Insert comment" to cover the following situations:

  • Editable Comment – We can set a Default Comment, but when the Pop-up opens, we can modify the comment.
  • Non-Editable Comment - We can set a Default Comment, but when the Pop-up opens, we are not able to modify the comment.
  • Free Text Comment – The comment field is blank, we will be able to type the comment


Output on POS:

Hence from now on, we can set the comment as we wish by using the parameters.

Filter on menu buttons for running pages and reports

The functionality implemented here gives the possibility to set static filter on pages or reports that are invoked by running POS actions from a button in the POS.
For running pages and reports from Transcendence POS there are two POS Actions 'RUNPAGE' and 'RUNREPORT'.
To set up a button in NAV that runs a page or report with a specified filter two things has to be done.
The first is to create a POS Menu Filter, which is a line or collection of lines describing a fixed filter on one or more tables that are to be sent to the page or report when they are opened.
A POS Menu Filter can be a static filter only pointing to a record and setting some constant filter on that.
It can also be a dynamic filter using the current sale and sale line from pos to set filter directly in report or page or on other tables.
POS Menu Filter are found under Retail/Sale/Administration.
To create a filter, we must give it a Filter Code and Description. Then select what kind of Object we want to run, be it a page or a report.
Then on what record should we put the filter – record meaning which table and lastly what fields from that table should we use to the filter.
In the example we are going to do a list of domestic customer. Hence we can identify a domestic customer with the posting group it is associated with.
In the POS Menu Filter, we will create a list called CUSLOCAL – Local Customer List.

After creating the POS Menus Filter, we need to set the "Table Filter". Then we do a test run and activate the POS Menu.
The second step is to setup a POS Menu button to desired POS Action and relate it to the POS Menu Filter that should be used. We go to the POS Menus, and choose where we want to create the button.

We use the action code: RUNOBJECT and set the parameter to the MenuFilterCode we created.

Item Lookup on Stock Keeping Units

We have defined a POS Menu for lookup on the Stock Keeping Unit instead of the Item. This function will display the list item, using the stock keeping units filtered by the location code.


The combination of the POS Menu for SKU (Stock Keeping Units is kept by Location) & the POS Store will give a list of items being sold in that store (we set the location on store) by associating the POS Store to the location and Stock Keeping Units is per location, we will have the list of items in that store.

The salesperson can select a line and the item will be set on the POS Line. As a company can have more than one store, but on the POS Store we are selling the items that are in the store, we do not want to have an Item Lookup for all items if we are only specific items in that store.

Item Lookup using Table Filters

We can now create Item Lookup and filter the list by any field on table 27. We can set filters using the Navision Filter Syntax. For example, we can do the following:

  • Item Lookup by Specific Item Group

SORTING(Description) ORDER(Ascending) WHERE(Item Group=FILTER(10..103))

  • Item Lookup by Unit Price of a Certain Value

SORTING(Description) ORDER(Ascending) WHERE(Unit Price=FILTER(>0&<25))

  • Item Lookup by Specific Inventory Posting Group

SORTING(Description) ORDER(Ascending) WHERE(Inventory Posting Group=FILTER(SHOP))

  • Item Lookup by Specific Description

SORTING(Description) ORDER(Ascending) WHERE(Description=FILTER(@Bag))

  • Item Lookup by Specific Item Group and Cost Price of Certain Value

SORTING(Description) ORDER(Ascending) WHERE(Item Group=FILTER(301),Unit Cost =FILTER(<50))

  • Item Lookup by Specific Vendor and Item Group

SORTING(Description) ORDER(Ascending) WHERE(Vendor No.=FILTER(CR000001),Item Group=FILTER(101))
The filetr can be built using teh right syntax in teh following POS Menus Parameters.


Some example of Filter Syntax and Values:

Symbol

Meaning

Sample Expression

Records Displayed

=

Equal to

777

Number 777



RED

Those with the RED code, for example, the RED warehouse code



12

A datetime: from 12-current month-current year 0:00:00 to 12-current month-current year 22:59:59



12 10

An exact datetime: 12-07-17 10:00:00

..

Interval

100..200

A range of numbers 100 through 200



..500

Up to and including 500



..310117

Dates up to and including 31/01/17



P2..

Information for accounting period 2 and thereafter

/

Vertical Bar

7/8

The vertical bar signifies either/or. It value is either 7 or 8.

@

Ignore case (either uppercase or lowercase allowed)

@green

Text such as GREEN, green or Green

***

Wildcard

Bag

any item containing the word "Bag" in any part of the name, filter with an asterisk (wildcard) before and after the word Corp: Corp

>

Greater

>100

A value greater than 100

<>

Note Equal to

<>100

A value not equal to 100. It can be smaller or greater

<=

Less than or equal to

<=100

A value Less than or equal to 100.

>=

Greater than or equal to

>=100

A value Greater than or equal to 100.

@ **

Wildcard, Case Insensitive

@bag

To find any item containing the word "Bag", "bag", "bAg", etc. (case-insensitive) in any part of the name, use the @ expression: @bag

@ ?**


@ba?

Text containing ba, BA, Ba, bA, such as bag, Bags and green bag.
ba, BA, Ba, bA must be present, followed by at least one character, but there can be an indefinite number of characters before and after these, and case is unimportant.

"

Blank


Value is blank. That is the field contains no value.

<>''

All not blank


The field contains a value.

Combination of Syntax






4444

5100..5490

Include any records with the number 4444 or a number from the interval 5100 through 5490



..1000

1200..

Include records with a number less than or equal to 1000 or a number equal to 1200 or greater (all numbers except 10001 through 1199)



>30&<100

Include records with numbers that are greater than 30 and less than 100 (numbers 31 through 99).



7*..8*

Result contains all records in which the field has values from (starting with digit 7) to (starting with digit 8), e.g. 7, 77, 717, 8, 81, 8123456 and so on.



7?..?11

Result contains all records in which the field has values from (two-digit numbers starting with digit 7) to (three-digit numbers ending with digit 11), e.g. 70, 71, 79, 111, 211, 911 and so on.



>B*

Result contains all records in which the field has text values that is greater than B*, where B* is any string that starts with "B". e.g Bag, Bags, Buggy, Boat etc..



>10?B*

Result contains all records in which the field has text values that is greater than 10?B*, where 10?B* is any string that starts with "10" then it has any random symbol, then goes "B" and than any number of any symbols.



A&B

Text containing both A and B.



SE

SO

LE..WE

Values SE, SO, LE, PE, WE

Date Formula






20D

20 days



6W

6 weeks



CM+2D

Current Month plus 2 days



CM+1M

Current month plus one month



CQ+1M+20D

Current quarter plus one month plus 20 days



CW+1W

Current week plus one week



D15

On the 15th of each month



-CY+10M

November 1st



CY

Current year



CM

Current month



CQ

Current quarter


ToolTips on the menu buttons

This facility is an aid to users. We can put "message" or "tips" to be displayed on a specific button.
The tip is displayed when the user has his cursor on the button.
This tip is configured using the POS Menu Buttons.

POS Inventory Overview

In the Standard version of POS, we have two triggers for Availability of Items = ITEM_INVENTORY_ALL and ITEM_INVENTORY.
The ITEM_INVENTORY, gives us a visibility on how many inventories we have for an item by location and the ITEM_INVENTORY_ALL gives us a page on Availability By Location for all items. But we do not have a view of what is the availability by variant and location. Navision does not have such report.
Given that Transcendence is flexible, we have developed a page to give us the inventories of an item by both Location & Variety. The idea is to have a simple report that can be used on both Desktop & Apps.

The POS Menu developed for POS Inventory Overview is known as ITEMINVOV and it does not require any parameters.

Negative Quantity

Please note the principle of returning an item requires that the item was bought and it has a sales ticket. As such, if we which to return an item, we should use the POS Menus

In exceptional cases, we have to do a negative line, and as such, we have provided a POS Menus with an Action Code called QUANTITY and the set parameters for it is "No Constraint" and if the NegativeInput is set to True, then the quantity entered will automatically be a negative in the POS sales line.

There is an additional feature that has been added in Transcendence whereby a consultant can define a POS Menu to do a Negative Line for a specific item on the POS Sale line. The Action Code is ITEM. The parameters are used to specified the item & quantity to be inserted on the POS Sale Line. (Note: The quantity can be Negative or Positive).

Edit/View Item Card

The Action Code ITEMCARD is used to call the Item Card from the POS. We can set the button to allow modifications in the item card or just to view. These two functions are based on the parameters associated with the Action Code.

Sales Order (menu)

We have developed new logic that permit us to create Sales Orders in Navision from the POS. The flexibility is based on the parameters we set for each Action Code.

  • Create Order (Open Status)

This Action Code allows us to create a Sale Order in Navision without shipping the item. Hence it has an "Open Status". Given that the Sale Order is open, it can be recalled on the POS line at a later stage to be converted into a Cash or Credit Sale. Or alternatively, we can process the Sale Order in Navision into a posted invoice.

  • Create Order (Release Status)

Unlike the above, we can create a Sale Order, but the items are shipped from the POS itself. Hence it will have an "Release Status" in Navision. We cannot recall this type of Sale Order on the POS, as the items have already been shipped. The sale Order will need to be posted in Navision only.

  • Retrieve Order (Open Sales Order)

This Action Code allows us to recall on the POS line at a later stage to be converted into a Cash or Credit Sale.

  • Create Order with Reservation

We have now the possibility to create a Sale Order with not only an Open Status Code allows us to create a Sale Order in Navision without shipping the item, but at the same time set a reservation on the item. The Sale Order will then need to be processed in Navision.
Note: The detailed configurations are found in "List of Action Codes & Parameters samples" section above.


From now on, we support Hyperlinks in Transcendence. An Action Code "HYPERLINK" has been created and we can set the link in the parameter as shown above.

POS Lock Action

We have introduced an automatic Loack Screen Action that can be setup if required.
The first step is to activate the Lock POS Action Code in the POS Setup menu. To do this, we need to go to Department > Retail > Sale > Administration > POS Setup.

Then go to Department > Retail > Setup > Administration > POS Unit. Select the POS Unit that we need to set a time out and choose from the options availiable which one we will use.

Alternatively, a button can be set on the POS for the user to manually lock the register.

To unlock a register, the Salesperson will use his password to unlock it.

Or a master password can be set on the Retail Setup card.

Customer List Filter in Transcendence

We can use any field in Customer Card to do a filtered list. In teh POS Action RECEIVABLES, we have added a parameter to create a customer view using a particular criteria. For example, if we define Staff as Customer and assign them a specfic STAFF Discount, we can use the Customer Disc. Group as a criteria to have a list of Staff on using a button to select the latter on the POS. Hence, in this case, we set the view, using a filter for Cust. Disc. Grp = SORTING(Name) ORDER(Ascending) WHERE(Customer Disc. Group=FILTER(STAFFDISC)). The list displayed will be only those who has STAFFDISC as Customer Disc. Group.

Change Description on Item in Action Code ITEM

As from NPR 5.38, we support the modification of description on Item Action Code. On the POS Menus, we can set the description to be editable. This is used in Item Groups Sales where we want to cahnge the description to indicate the product sold.

For example, the description of the Item Group can be Soft Drinks, but on the point of doing the Sale, we can change it to Coca Cola etc..

Changing of quantity by pressing a number and star

There is an old functionality which is to change the quantity by pressing a number and star, for example 4*. It needs some setup in the Id. Dispencer to work.
A new action dispenser must be added with id type "EANPATTERN  / QTYSTAR" has been developed and it shall go to POS Action Quantity. On the parameters Constraints can be set to what you like and the new ChangeToQuantity should be set to 'Use Code As Value'.

Also, when changing the POS Action Quantity, we need to update POS Menu buttons where it us used by pressing refresh if it does not do it by itself with versions.



Setting Up Security Options on POS Menus

We can set security password levels on any POS Action. The security is set at group levels and not at individual level such as users. A user or salesperson will then belong to a group of security level.    

The parameter which is referred as Security has the following Options to define the access levels:

  1. Blank - anybody is able to use the function without any access control. (No Security Restrictions)
  2. ANY-SALESP (AnySalespersonPassword) - any salesperson with a Register Password and Supervisor Password will be able to use the function.
  3. CUR-SALESP (CurrentSalespersonPassword) - only the salesperson who has logged on the POS at that time can use his password and Supervisor Password to use the function.
  4. SUPERVISOR (SupervisorPassword) - only password for salesperson marked as supervisor will open the item card.
  5. ADMIN-PWD (RetailSetupAdminPassword) – This level is the highest level. Hence if set on a POS Action, only that person with teh Admin Password will be able to execute the POS Action.

In additional to the above, we have a password that can be set for the opening of Cash Register = REGIST-PWD (Retail Setup Open Register Pas).

To activate the password security on the POS Action, you will need to go to the POS Menus. There is a field called Secure Methode Code.


 

Setting Up the Salesperson & Supervisor Password:

In the Salespeople Card, there is a Register Password that is used by the saleperson to login on the POS. And it is this password that is used at the security level of AnySalespersonPassword or CurrentSalespersonPassword. Hence he will use the register password to execute the  POS Action.

A Salespeople can be an ordinary Salesperson or he can be a Supervisor. If, he has the status of Supervisor, we  activate the flag for Supervisor POS in the Salespeople Card as shown in the above printscreen. In this context, we can define more than one supervisor and with their respective password can use the POS Action.

Setting Up the Admin Password & Open Register Password:

These two passwords are not directly related to the salesperson as above but rather to the postion of the user in the organisation. Hence, it can be set and given to any user.

Menus: Departments/Retail/Setup/Retail Setup

Using Password Security on POS

 

Hence, On the POS, if we select the button where security has been set, we will get a Numpad where the user is asked for a password, based on the level set in the parameters.

Without the correct, the user will not be able to excute the function and he will get an Invalid Password  message. It is only when he input the right password that he will be able to move further in the process.


Setting Up a VAT Free Button in Shops

There are two ways of doing Tax Free.

  1. If the shop is Tax Free, meaning all sales are Tax free, then we can set a VAT posting group (VAT=0) at the POS Store level


 


      2. If we want a button for the sale, we create a customer with VAT posting group (VAT=0), then create a button with POS menus receivables + parameter customer no & insert customer. Note: in this case the default POS posting setup = Customer


Export/Import in POS Menu Button

Once the POS Menus has been defined, they can be exported from a company and imported into another using "Jason" format. The shortcut is found in the Action Ribbon of POS Menus.

We can export selected menu or all the menus.

POS Setup

In Transcendence, we have a new set-up where-by we can change the predefine type of action we have in our POS menu button.

For time being, we have reflected what we currently have in our classic version. Nevertheless, we add on new types in the future.

POS Actions

These are sets of workflows that trigger specific actions (functions) on the POS. It is equivalent to the "Triggers" in the standard version of NP Retail. These workflows are developed and the setup and parameters are part of the objects.
Menu: Retail > Sale > Administration > POS Actions

Code

Description

Version

Blocked

Type

Workflow Defined

Data Source Name

Codeunit ID

BALANCE_V1

This is the built in function to perform balancing of the register (Version 1)

1

No

Generic

Yes


0

BLOCK_DISCOUNT

This action toggles the state of "Custom Disc Block" field.

1

No

Generic

Yes


0

BOARDINGPASS

POS Action for boarding pass scan

1

No

Generic

Yes


0

CANCEL_POS_SALE

Cancel Sale

1

No

Generic

Yes


0

CHANGE_VIEW

Changes the current view.

1.1

No

Generic

Yes


0

CONV_TOUCH2TRANS

Warning: This Action will convert the old Touch screen POS buttons to Transcendence

1

No

Generic

Yes


0

CREDIT_GIFTVOUCHER

This is a built in function for handling return sales with Gift Vouchers

1

No

Generic

Yes


0

CUST_DEBITSALE

Customer - Debit Sale (Proof of Concept)

1

No

Generic

Yes


0

CUST_LOCATION

This is a built-in action for moving sale lines to/from a customer location and starting related prints.

1.3

No

Button

Yes


0

CUSTOMER

This is a built-in action for setting a customer on the current transaction

1

No

Generic

Yes


6151590

CUSTOMERINFO

This is a built-in action for handling Customer Info

1

No

Generic

Yes


0

CUSTSALEDOCEXP

This is a built in function for handling sales document export

1.1

No

Generic

Yes


6150826

CUSTSALEDOCIMP

This is a built in function for handling sales document import to POS

1

No

Generic

Yes


6150826

DELETE_POS_LINE

This built in function deletes sales or payment line from the POS

1

No

Generic

Yes


6151590

DEMO-DELETE

This is a test action that accomplishes nothing in particular, but is here to confuse the crap out of you.

1

No

Generic

Yes


0

DEMO-DELETELOC

This is a test action that accomplishes nothing in particular, but is here to confuse the crap out of you.

1

No

Generic

Yes


0

DEMO-MENU

This is a test action that accomplishes nothing in particular, but is here to confuse the crap out of you.

1

No

Generic

Yes


0

DEMO-QUANTITY

This is a test action that accomplishes nothing in particular, but is here to confuse the crap out of you.

1

No

Generic

Yes


0

DEMO-SAVERETRIEVE

This is a test action that accomplishes nothing in particular, but is here to confuse the crap out of you.

1

No

Generic

Yes


0

DISCOUNT

This is a built-in action for handling discount

1.1

No

Generic

Yes


0

EXCHANGELABEL

This is a build in function to handle exchange labels.

1

No

Generic

Yes


0

GS1FREEITEM

POS Action to handle GS1 Free Item Barcodes

1

No

Generic

Yes


0

GS1FREEITEMSE

POS Action to handle GS1 Free Item Barcodes

1.1

No

Generic

Yes


0

HC_EXTERNALPRICE

This action makes remote call to aquire item price information

1

No

Generic

Yes


0

HC_INVMESSAGE

This action makes remote call to aquire item price information

1

No

Generic

Yes


0

HYPERLINK

This is a built-in action for inserting an item line into the current transaction

1

No

Generic

Yes


0

IMPORTSALESDOC

This is a built-in action for handling Customer Info

1

No

Generic

Yes


0

INSERT_COMMENT

Insert a sales line comment.

1.1

No

Generic

Yes


6151590

INSERT_TABLE_BUZZER

Insert a table buzzer number

1.1

No

Generic

Yes


6151590

ISSUE_RETURN_VOUCHER

This action Issues Return Retail Vouchers.

1

No

Generic

Yes


6151590

ISSUE_VOUCHER

This action Issues Retail Vouchers.

1

No

Generic

Yes


6151590

ITEM

This is a built-in action for inserting an item line into the current transaction

1.5

No

Generic

Yes


6151590

ITEMCARD

This built in function opens the item card page for a selected sales line in the POS

1

No

Generic

Yes


0

ITEMINVOV

This built in function opens a page displaying the item inventory per location and variant.

1

No

Generic

Yes


0

LOCK_POS

This built in function locks the POS

1

No

Generic

Yes


6150835

LOGIN

This is a built-in action for completing the loign request passed on from the front end.

1

No

BackEnd

No


0

LOOKUP

This is a built in function for handling lookup

1.1

No

Generic

Yes


0

MM_MEMBER_ARRIVAL

This action handles member arrival functions.

1.1

No

Generic

Yes


0

MM_MEMBER_LOYALTY

This action is capable of redeeming member points and applying them as a coupon.

1

No

Generic

Yes


0

MM_MEMBERMGT

This action handles member management functions.

1.1

No

Generic

Yes


0

MPOSNATIVE

This is a built-in action for running a report

1

No

Generic

Yes


6150825

NOTIFICATIONCARD

This built in function opens the notification card page

1

No

Generic

Yes


0

NOTIFICATIONLIST

This built in function opens the notification list page

1

No

Generic

Yes


0

OPEN_CASH_DRAWER

This is a built-in action for opening the cash drawer

1.1

No

Generic

Yes


0

PARK_SALE

This built-in function handles parking and retreiving sales

1.1

No

Generic

Yes


6150811

PAYIN_PAYOUT

This built in function handles cash deposit / withdrawls from the till

1

No

Generic

Yes


0

PAYMENT

This is a built-in action for inserting a payment line into the current transaction

1.2

No

Generic

Yes


6151590

PEPPER_TERMINAL

This command sends different commands to the Pin Pad. Specify command using the Parameters.

1

No

Generic

Yes


0

POSINFO

This built in function opens a page displaying the POS Information.

1

No

Generic

Yes


0

PRINT_EXCH_LABEL

This is a built-in action for printing exchange labels.

1.3

No

Button

Yes


0

PRINT_ITEM

Print item-based prints.

1.2

No

Button

Yes


0

PRINT_RECEIPT

This is a built-in action for printing a receipt for the current or selected transaction.

1.1

No

Generic

Yes


0

PRINT_TEMPLATE

This is a built-in action for running a report

1

No

Generic

Yes


0

QUANTITY

This is a build in function to change quantity.

1.2

No

Generic

Yes


6151590

RECEIVABLES

This built in function handles customer receivables from the POS.

1.3

No

Generic

Yes


6151590

RECOMM

This is a built-in action for selecting and inserting a recommended item into the current transaction

1

No

Generic

Yes


0

REVERSE_CREDIT_SALE

Refund / Reverse Sale. This action will prompt for a receipt no and recreate the sales with reversed quantity.

1

No

Generic

Yes


0

REVERSE_SALE

Refund / Reverse Sale. This action will prompt for a receipt no and recreate the sales with reversed quantity.

1

No

Generic

Yes


0

RUNOBJECT

This is a built-in action for running a page

1

No

Generic

Yes


6151590

RUNPAGE

This is a built-in action for running a page

1

No

Generic

Yes


0

RUNREPORT

This is a built-in action for running a report

1

No

Generic

Yes


0

SALE_DIMENSION

This Action updates the POS Sale Dimension with either a fixed value or provides a list of valid value

1

No

Generic

Yes


0

SALE_GIFTVOUCHER

This is a built in function for handling sales of Gift Vouchers

1

No

Generic

Yes


0

SALEANNULL

This action will prompt for a receipt no and annul the sale.

1.1

No

Generic

Yes


6150821

SALES_STATISTICS

This built in function reports on various turnover statistics

1

No

Generic

Yes


0

SCAN_COUPON

This action handles Scan Discount Coupon.

1

No

Generic

Yes


6151590

SCAN_VOUCHER

This action handles Scan Retail Vouchers (Payment).

1

No

Generic

Yes


6151014

SETTAXAREACODE

Set Tax Area Code

1

No

Generic

Yes


0

SETTAXLIABLE

Set Tax Liable

1

No

Generic

Yes


0

SETVATBPGRP

Set VAT Bus. Posting Group

1

No

Generic

Yes


0

STERIA_TERMINAL

This command sends different commands to the Pin Pad. Specify command using the Parameters.

1

No

Generic

Yes


0

SWITCH_REGISTER

Switch to a different register

1

No

Generic

Yes


0

TAX_FREE

This is a built-in action for toggling tax free before completing sale

1.1

No

Generic

Yes


0

TEXT_ENTER

This is a built-in action for completing the TextEnter request passed from the front end (when user presses enter in a supported text box)

1

No

BackEnd

No


0

TM_TICKETMGMT

This action handles ticket management functions.

1.1

No

Generic

Yes


0

UNLOCK_POS

This built in function unlocks the POS

1

No

Generic

Yes


6150836

VATREFUSION

This is a built in function for handling VAT refussion

1

No

Generic

Yes


0

WAITERPAD

This is a built in function for handling move between pos and waiter pad.

1

No

Generic

Yes

NPH_WAITERPAD

6151590

ZOOM

Zoom a sales line.

1

No

Generic

Yes


0


Recognition of data in the EAN Box in our POS

Unit Identifier Dissociation Type

In this section, we have provided options to the what type of data can be recognized in the EAN Box in our POS Unit.
The options are as follows:

#

Check Module

Dissociation Code

1

CUSTOMER

CUSTOMERNO

2

DISCOUNT_COUPON

REFERENCE_NO

3

EANPATTERN

QTYSTAR

4

EXCHLABEL

EXCHLABEL

5

ITEM

ITEMCROSSREFERENCENO

6

ITEM

ITEMNO

7

MEMBER_MANAGEMENT

EXTERNALMEMBERCARDNO

8

MEMBER_MANAGEMENT

EXTERNALMEMBERNO

9

MEMBER_MANAGEMENT

EXTERNALMEMBERSHIPNO

10

SALES

POSTEDSALSEINV

11

SALES

SALESBLANKET

12

SALES

SALESCREDITMEMO

13

SALES

SALESINVOICE

14

SALES

SALESORDER

15

SALES

SALESQUOTE

16

SALES

SALESRETURNORDER

17

TICKET_MANAGEMENT

EXTERNALTICKETNO

18

TICKET_MANAGEMENT

TICKETNO


By default, we are setting the Items, Tickets & Membership to be scanned in the EAN Box on the POS.

Identifier Dissociation Action Dispenser

Once, we have identified which action we want to be recognised in the EAN box, we need to enable it. To do this, we should create the "Identifier Dissociation Action Dispenser".
We access the menu with the said name and add an ID Dis. Type.

When we select "Add id. Dis. Type", we will be presented with the "Unit Identifier Dissociation Type" page which we have previously defined.
Description of Issue with Module Priority
The issue is that there is no priority settings done when the number is validating against ITEM NO & ITEM CROSSSREFERNCE NO. we have a pop-up message to manually select which value we need to choose for validation.
Given that the Item No and the Cross Reference No may be the same in certain cases, we need to a set a priority for the system to do the validation and identify if item exist.
Solution of Issue with Module Priority
The solution is to set a priority. Hence the system will automatically validate against first the ITEM CROSSSREFERNCE NO, if found, it will insert the item on the Sale Line.
If not found in ITEM CROSSSREFERNCE NO, it will continue to look in the ITEM NO and then insert the item on sale line.
If both numbers are the same, it will stop on the first search automatically without asking a question to choose which number to check.
If it not found in both ITEM CROSSSREFERNCE NO &  ITEM NO , it will give an indication that the item does not exist.
Setup is done in menus:  Departments/Retail/Sale/Administration/Identifier Dissociation/Identifier Dissociation Type
The next step is that we need to select which code we want to be recognised in the EAN Box. Then the next step is to "Add the Action Parameters" for it to work.

In the above example, we set the Item Cross Reference barcode to be recognized in the EAN Box. It is imperative that we set it to use code as a value. Hence when it scans the code, the EAN box will pick it up.

Unit Identifier Dissociation Type on Search Description

Apart the code, we have added the Search Description on ITEM & CUSTOMER in the EAN Box. As form NPR 5.37, we can type the description in the EAN Box, and it will pick up the item or customer. The only limitation is that it takes a minimum 4 characters. The search facility is not proactive as if when you are typing a letter, it will start the search. It is only when you do enter on a minimum 4 characters, that the search engine start the search by doing an enter. This is so as we are not in a List Page (like Item List or Customer List), we are in a field.




Now if you write parts or full text of an item description it will be added as item to sale. If text written in EAN box matches more than one item a look up list is shown. It will only searches for non-blocked and non-blocked for POS items.
The same principle applies to Customer. A minimum four (4) characters are needed to be entered in EAN-box. And when doing enter, it will only searches for non-blocked customer. If text written in EAN box matches more than one customer, a look up list is shown. On selecting, it will attach the customer to the transaction which is the equivalent to Insert Customer.

Scanning Exchange Label

A new POS Action called EXCHANGELABLE has been created to cater for the scanning of the exchange label code in the EAN Box or having a pop-up menu.

And a new Id Type called EXCHLABEL:

The POS Action are used to take a barcode value from an exchange label and run the functions for handling exchange.
The Id Type lets the Id Type Dispencer understand that a value scanned in the EAN box is a exchange label barcode and send it to the POS action.
This can be set up in two ways or a combination of them.

  • The first is a button where you press and get a new window to enter an Exchange Label barcode in (and then the exchange functions runs). This is set up in POS Menu.
  • The second is you just scan the barcode in the EAN box (and the the exchange function runs). This is setup in the Id Diss . Dispenser.

They can both be setup at the same time or just one of them.

Pressing the button gives a box to enter a exchange label barcode.

Id. Dispenser:
Is setup by adding a new dispenser line for sale-view with Id. Type 'EXCHLABEL' and Action Code EXCHANGELABEL and for the action parameters ExchLabelBarcode is set to 'Use Code As Default' and PromtForBarCode to false.

With this setup, no pressing of button is needed, only to scan label.

Scanning Boarding Pass in Airports Duty Free Shops

New function to handle scan of boarding pass in POS for validity check and to register in POS Info. What is saved is airport codes and flight date. The function includes a identifier to identify a scanned boarding pass (scan in POS text box), a POS Action to be initiated after identification for doing validity check and save to POS Info.

Boarding Pass

An IATA boarding pass can be represented I various format (ex. PDF 147 printed on boarding pass or QR/Aztec on mobile devices). They all holds a string with data from the boarding pass. This data can be one flight-leg or many flight-legs and there can also be data that is different depending on carrier.
The Boarding Pass Scan function decodes the flight-legs in the boardingpass and reads flight dates and from and to airports. Example of an boarding pass string:
M2ENGSTRAND/ANTON EOJCV9F CPHCDGAF 1063 314Y035A0071 348>5180 B1A 2A05714050072410 AF 1147455642 NOJCV9F CDGMRUAF 0460 314M049H0059 32C2A05714050072410 AF 1147455642 N

Function

A new id type [BOARDINGPASS] [IATA-M] has been added that identifies a scanned boardingpass string.
A new POS Action [BOARDINGPASS] has also been added to handle decoding and registration.
The POS Action has five parameters for settings.

  1. BoardingPassString is used for transfer the scanned boarding pass from Id Action Dispenser to POS Action.
  2. InfoCode is setting for what POS Info code to register trip on.
  3. RequiredLegAirPortCode is setting for an airport code that have to be on boarding pass. This is to avoid the use of not valid boarding pass. For example, in a POS on Kastrup airport this setting should be CPH. The function will the check that from-airport-code on one of the flight-legs on the boarding pass is CPH. If nothing is set here all airport codes are valid.
  4. RequiredTravelToday is a setting to check that the scanned boarding pass is for travel on the POS workdate. If RequiredLegAirPortCode is set then the date for that flight-leg will be used, otherwise all travel dates on boarding pass are checked.
  5. ShowTripMesasge is a setting to control if a message should be shown on POS when a succesfull scan is done.

Setup of Boarding Pass Function

Before setting up the Id Action Dispenser a POS Info must be added. It should be 'Once per Transaction', 'Input Mandatory', Type=Request Data and 'Input Type' = Text.
An Id Action Dispenser should be set up to connect Identifier to the POS Action.
And parameters for POS Action must be set up on the dispenser. When setting them up the BoardingPassString should have 'Use Code As Default' marked.

Use of functionality

Scan of boarding pass can be done on a sale anytime in the sale view and is done by scanning the boarding pass with a device that writes to the POS text box.
If setting is done not to show message after scan the trip will be saved to POS Info with no notice or action needed by user is scan is successful.
If setting to show message is done a message is shown to user on successful scan.

Now POS Info is also registered and when sale is paid and posted it can be seen in POS Info Audit Roll.
If boarding pass is not valid according to settings message is shown to user telling what is wrong.

NPR POS Menu Buttons/Actions

We have a report that gives us all the menu buttons and associated parameters that has been defined on a company. This report can be printed and kept in the client's file by the project manager for records. It helps to verify if along the way, parameters have been modified and so on. The report can be filtered by Menu Buttons if required. It can be printed with or without parameters depending on the level of details required. Report is found in following menu:
!worddav33b34d915ba7939aeef4eca2e0812476.png|height=466,width=869!h1. POS Views

The POS View is not configured UNLESS you want to change the Default view. This menu should be empty for default setup for both Desktop version of the layout and the MPOS version for the mobile.
You only need to define POS Default Views if you are overriding standard layouts, or if you are defining different registers for different salespeople which need any specific view layout. The set filters can be by salesperson or Register.
Otherwise if you are happy with default built-in layout (either desktop or mobile) then you don't need to modify either POS Views or POS Default Views
But before doing any new views, make sure you have a good backup as these codes are sensitive. There are a few steps to follow to set it up new POS Views.
Menu: Retail > Sale > Administration > POS View List

  1. In POS View List – create the new view for example "ENTRE"
  2. Paste the POS layout (attached)
  3. In the code, all the names you usually refer (SALE-LEFT, SALE-TOP, etc) are defined. You can changed SALE-LEFT to ENTRE-LEFT.
  4. Register the view (from step a.) as type Sale
  5. Select who should use this view (register or sales person)
  6. The last step is to define the POS Menus Buttons that is under the POS Menu ENTRE-LEFT.



Example of Code for DEFAULT SALE Screen View:
{
tag: "sale",
flow: "horizontal",
content: [
{
alignment: "left",
flow: "vertical",
content: [
{
type: "grid",
id: "salesLines",
fontSize: "normal",
dataSource: "BUILTIN_SALELINE",
totals: [
{
caption: "l$.Sale_SubTotal",
total: "TotalAmount"
}
],
control: "dataGrid"
},
{
type: "menu",
source: "SALE-LEFT",
columns: 5,
rows: 5,
base: "55%",
"margin-top": 0,
dataSource: "BUILTIN_SALELINE"
}
]
},
{
flow: "vertical",
base: "40%",
content: [
{
type: "text",
caption: "l$.Sale_EANHeader",
id: "EanBoxText",
showErase: false,
base: "4em",
control: "eanBox",
bigCaption: true,
inputFilter: true
},
{
type: "menu",
source: "SALE-TOP",
columns: 3,
rows: 2,
id: "buttongrid-functions-top",
dataSource: "BUILTIN_SALELINE"
},
{
type: "captionbox",
fontSize: "medium",
binding: {
dataSource: "BUILTIN_SALELINE",
captionSet: {
title: { field: "10" },
rows: [
{ field: "6" },
{ field: "15" }
]
},
fallback: {
dataSource: "BUILTIN_SALE",
captionSet: {
title: { caption: "l$.Sale_LastSale" },
rows: [
{ caption: "l$.LastSale_Total", field: "LastSaleTotal" },
{ caption: "l$.LastSale_Paid", field: "LastSalePaid" },
{ caption: "l$.LastSale_Change", field: "LastSaleChange" }
]
}
}
}
},
{
type: "menu",
base: "44%",
source: "SALE-BOTTOM",
columns: 3,
rows: [1, 1, 2],
id: "buttongrid-functions-bottom",
dataSource: "BUILTIN_SALELINE"
}
]
}
],
statusBar: {
dataSource: "BUILTIN_SALE",
sections: [
{ field: "CompanyName", width: "20%" },
{ field: "4", width: "15%" },
{
type: "group",
width: "5%",
sections: [
{ caption: "l$.Sale_RegisterNo", "class": "strong" },
{ field: "1" }
]
},
{ field: "7", width: "10%" },
{
type: "group",
"class": "group right",
sections: [
{ caption: "l$.Sale_ReceiptNo", "class": "strong" },
{ field: "2" }
]
},
{
type: "group",
"class": "group right",
sections: [
{ caption: "l$.Sale_LastSale", "class": "strong" },
{ field: "LastSaleNo" }
]
},
{ id: "walkthrough" }
]
}
}
If we have a closer look at the POS View for the Sale Screen about, we can identify the different subsections in the Sale Screen. Let's do a closer analysis on the above.
We start from the top of the codes:

Code Extract

Screen Layout View – The demarcation of the section is indicated in RED

LEFT Section
content: [
{
alignment: "left",
flow: "vertical",
content: [

SALE LINE Sub-section
{
type: "grid",
id: "salesLines",
fontSize: "normal",
dataSource: "BUILTIN_SALELINE",

totals: [
{
caption: "l$.Sale_SubTotal",
total: "TotalAmount"
}
],

control: "dataGrid"
},

SALE-LEFT Sub-section
{
type: "menu",
source: "SALE-LEFT",
columns: 5,
rows: 5,
base: "55%",
"margin-top": 0,
dataSource: "BUILTIN_SALELINE"
}




RIGHT Section
{
flow: "vertical",
base: "40%",
content: [




Note:
The 40% means that the right section is 40% of the whole screen. Hence the left section takes 60% of the whole screen.


EAN BOX Sub-section
{
type: "text",
caption: "l$.Sale_EANHeader",
id: "EanBoxText",
showErase: false,
base: "4em",
control: "eanBox",
bigCaption: true,
inputFilter: true
},



SALE-TOP Sub-section
{
type: "menu",
source: "SALE-TOP",
columns: 3,
rows: 2,
id: "buttongrid-functions-top",
dataSource: "BUILTIN_SALELINE"
},





SUMMARY Sub-section
{
type: "captionbox",
fontSize: "medium",
binding: {
dataSource: "BUILTIN_SALELINE",
captionSet: {
title: { field: "10" },
rows: [
{ field: "6" },
{ field: "15" }
]
},

fallback: {
dataSource: "BUILTIN_SALE",
captionSet: {
title: { caption: "l$.Sale_LastSale" },
rows: [
{ caption: "l$.LastSale_Total", field:
"LastSaleTotal" },
{ caption: "l$.LastSale_Paid", field:
"LastSalePaid" },
{ caption: "l$.LastSale_Change", field:
"LastSaleChange" }
]
}
}
}

SALE-BOTTOM Sub-section
{
type: "menu",
base: "44%",
source: "SALE-BOTTOM",
columns: 3,
rows: [1, 1, 2],
id: "buttongrid-functions-bottom",
dataSource: "BUILTIN_SALELINE"
}




STATUS BAR Section
statusBar: {
dataSource: "BUILTIN_SALE",
sections: [
{ field: "CompanyName", width: "20%" },
{ field: "4", width: "15%" },
{
type: "group",
width: "5%",
sections: [
{ caption: "l$.Sale_RegisterNo", "class":
"strong" },
{ field: "1" }
]
},
{ field: "7", width: "10%" },
{
type: "group",
"class": "group right",
sections: [
{ caption: "l$.Sale_ReceiptNo", "class":
"strong" },
{ field: "2" }
]
},
{
type: "group",
"class": "group right",
sections: [
{ caption: "l$.Sale_LastSale", "class": "strong"
},
{ field: "LastSaleNo" }
]
},
{ id: "walkthrough" }
]


Now that you understand how different sections and sub-sections are set, let's have a look at the contents. For example, in SALE-LEFT Sub-section, we have the following:

Sections of Code

Explanation

type: "menu",

It is a POS Menu

source: "SALE-LEFT",

The ID of the POS Menu. The buttons are defined in the POS Menu.

columns: 5,

The number of columns in the section

rows: 5,

The number of rows in the section

base: "55%",

The space occupied by this sub-section when compare to the section

"margin-top": 0,

It means that the delimit has minimum space in between the grids

dataSource: "BUILTIN_SALELINE"

BUILTIN_SALELINE is a datasource. In this case the default datasource for SALE_TOP (the picture you show). Datasources are basically data available for display on the POS.


The same logic applies for the Code for DEFAULT PAYMENT Screen View:
{
tag: "payment",
flow: "horizontal",
content: [
{
alignment: "left",
flow: "vertical",
content: [
{
type: "grid",
id: "paymentLines",
fontSize: "normal",
dataSource: "BUILTIN_PAYMENTLINE",
totals: [
{
caption: "l$.Sale_SubTotal",
total: "Subtotal"
}
],
control: "dataGrid"
},
{
type: "menu",
source: "PAYMENT-LEFT",
columns: 5,
rows: 5,
base: "55%",
"margin-top": 0,
dataSource: "BUILTIN_PAYMENTLINE"
}
]
},
{
flow: "vertical",
base: "40%",
content: [
{
type: "text",
caption: "l$.Sale_PaymentAmount",
id: "TotalText",
showErase: false,
base: "4em",
control: "totalBox",
bigCaption: true,
inputFilter: true
},
{
type: "menu",
source: "PAYMENT-TOP",
columns: 3,
rows: 2,
id: "buttongrid-functions-top",
dataSource: "BUILTIN_PAYMENTLINE"
},
{
type: "captionbox",
fontSize: "medium",
binding: {
dataSource: "BUILTIN_PAYMENTLINE",
captionSet: {
title: { caption: "l$.Payment_PaymentInfo" },
rows: [
{ caption: "l$.LastSale_Total", total: "SaleAmount" },
{ caption: "l$.LastSale_Paid", total: "PaidAmount" },
{ caption: "l$.LastSale_Change", total: "ReturnAmount" }
]
}
}
},
{
type: "menu",
base: "44%",
source: "PAYMENT-BOTTOM",
columns: 3,
rows: [1, 1, 2],
id: "buttongrid-functions-bottom",
dataSource: "BUILTIN_PAYMENTLINE"
}
]
}
],
statusBar: {
dataSource: "BUILTIN_SALE",
sections: [
{ field: "CompanyName", width: "20%" },
{ field: "4", width: "15%" },
{
type: "group",
width: "5%",
sections: [
{ caption: "l$.Sale_RegisterNo", "class": "strong" },
{ field: "1" }
]
},
{ field: "7", width: "10%" },
{
type: "group",
"class": "group right",
sections: [
{ caption: "l$.Sale_ReceiptNo", "class": "strong" },
{ field: "2" }
]
},
{
type: "group",
"class": "group right",
sections: [
{ caption: "l$.Sale_LastSale", "class": "strong" },
{ field: "LastSaleNo" }
]
},
{ id: "walkthrough" }
]
}
};
To close this section, we are providing a few samples of how we can configure the Views and the output of the layouts to illustrate the flexibility of the Views.

POS View Code

POS View Description

POS View File

Sale Screen Layout

SALE-FULL






Default Sale View

Blank – no file

SALE-INV






Invert Default View

SALE-ENT






Entertainment View

SALE-FASH





Fashion View

SALE-CAFÉ






Cafe View

SALE-REST





Restaurant View


How to use the POS Views

There are 3 ways of getting access to the view that has been created. In the menu POS Default Views, we can set defaults based on certain conditions or we can create a POS Menu Button using the CHANGE_VIEW action code.

POS Default Views

Menu: Retail > Sale > Administration > POS Default Views

In the POS Default Views, we can set the default view on two criteria.

  • A view can be set per Salesperson. Meaning a Salesperson can have a specific POS Screen defined for him.
  • A view can be set per Register. Hence, we have different POS Screen per register. For example, in Entertainment Environment, we can have a Register for Ticketing (ENTRE) and the other for Shop (BUTIK).

If the POS Default View does not contain filter, then it is set for all. Hence, we always leave it blank as a start. As mentioned, we do not need to touch this configuration, unless we have created a specific view for a specific purpose.

POS Menus Views

Menu: Retail > Sale > Administration > POS Menus

In the "CHANGE_VIEW" POS Action Code, we can set parameters to open which View we want. There are two criteria that we need to set:

  • ViewCode – The ID for the POS View
  • ViewType – The ID for the type of view

Hence as shown above, when we use the button, it will go to the SALE View defined for Entertainment. But if we leave the ViewCode empty, it will go to the Default View as shown below:

Please note that if we define a set of POS View & we use the "CHANGE_VIEW" POS Action Code to move from one view to another, then we need to set the button to move to where we want or it will jump to the Default View.
In case we are using "CHANGE_VIEW" POS Action Code and not POS Default View, and we do a SALE-View, we will need a corresponding PAYMENT-View and the button "Go To Payment / Back to Sale" which are "CHANGE_VIEW" POS Action Code has to have the right POS View code as POS Parameter Values for them to work properly.

Conversion of Touch Screen into Transcendence

Most of the setups concerning Transcendence is found in the following menu:
Menu: Departments > Retail > Sale > Administration

Default Conversion

On the POS Menus, there is a function to convert the Touch Screen Setups (buttons) into Transcendence POS Menus (buttons).

The function will convert nearly 95% of the button.
When using the function to convert, it will ask you stepwise,

  1. Do you want to delete ALL POS Menus and POS Menu Lines. If it is a first time, you can says YES or else if you are re-doing a partial coversion, you will need to say NO.
  2. Then it will start by converting the following

    Touch Screen Setup

    POS Menus

    Login

    LOGIN

    Sub-menu Discount

    DISCOUNT

    Sub-menu Print

    PRINTS

    Sub-menu Sales Funtions

    MORE_SALE_FUNC

    Sub-menu Payment Functions

    MORE_PAY_FUNC

    Sub-menu Customer

    CUSTOMER

    Sub-menu Item

    FUNCTIONS_ITEM

    Sale menu (Left – Bottom Center)

    SALE-LEFT

    Sale menu (Right)

    SALE-TOP + SALE-BOTTOM

    Payment menu (Left – Bottom Center)

    PAYMENT-LEFT

    Payment menu (Right)

    PAYMENT-TOP + PAYMENT-BOTTOM


    Note: You can re-do partial conversion if need be. As it is done stepwise, just run the "Convert to Transcendence" function and say NO to the menus you do not want to reconvert & YES to the menu you want to reconvert. For example, if we want to reconvert Sales Function into MORE_SALE_FUNC when asked for Convert Submenu – Sales Function , we say YES.

    It will then give a warning that it has a trace on the MORE_SALE_FUNC. You will need to YES to delete it.
    Note: If you want to reconvert a section, please delete manually the POS Menu, before reconverting.

    Why does the tool not convert all the buttons?

When we did the move to transcendence, we took that oportunity to improve on the existing functions as well creating new functions.
There are a few reasons why not all the buttons are converted:

  1. The Touch Screen button contains a bug and we have made it redundant.
  2. If the tool does not find a correspondig Transcendence equivalent, it will insert the button, but will block it and display the description of the button in the Tooltip field to indicate that we need to look into it & replace it with a new POS Menu.

  1. The Touch Screen button was customised specifically for the customer and we do not have an equivalent in our Transcendence repository. Hence a case will need to be created for the developer to do the POS Menu & Action Button.


Practical Tips and Trick

Menu Level v/s Popup Menu

The principle of Popup menu is the same as in Touch Screen where we used to have Sub-menus. The advantage of Popup Menu is that it is not fixed as in the past we had only: Discounts, Prints, Other Functions, Item Functions etc..

We define any PopMenu if we want to re-group a set of functions under one button. Fot example, instead of ahving only one button for lookup, we can defien variuos buttons for lookup based on different criteria and group them under a Popup Menu.

Output:

The logic of Levels is the same as in Touch Screen. You can define indefinite levels and the details move from 1st button to the last button.

How to choose between levels or Popup Menues? The answers lies in what our customer requires.
The main practical difference if when you move back from the last level to the first level, you will need to do back stepwise. And in a Popup Menu, each time you use a button, it will jump back to your main screen after executing the Action.

MORE_SALE_FUNC

The grouping logic of the display of the Sales Function has changed. In the touch screen, we used to mix modules and groups teh button depending if the function is Input(Create) or Output(Get). Whereas in the MORE_SALE_FUNC, we have grouped the functions modular.

English POS Menus: \\npkcenter.local\desktopicons_NPRetail_Release\NPRetail100_W1_Release (Company: __Demo_Template_Master)
Danish POS Menus: \\npkcenter.local\desktopicons\_NPRetail_Release\NPRetail90_DK_Release (file://npkcenter.local/desktopicons/_NPRetail_Release/NPRetail90_DK_Release) (Company: __Live_Template)
The way forward whenever we do a conversion is to delete the MORE_SALE_FUNC and import the POS menu for MORE_SALE_FUNC from the above database. Then modify manually the POS Menu to fit the client's requriements. By doing so, we will maintain a uniformity in the the POS Menus.

Filters in POS Menu v/s Different Views

As we have the facilities of doing different views as well as using filters in the POS Menus, we are a bit confused as when to use what?
Filters:

We can put filters on Cash Register Type, Cash Regiter No. & Salesperson. Hence jsut like in touch screen, if we put filters on the button, the button will be visible for that particular filter only.
Hence we use filters when the layout of the POS Screen is the SAME for all registers. There is no need to create a different view for each register. The safest way is to regroup the cash register under a specfic Cash Register Type and do the filters on that Cash Register Type.
When we use the conversion tool, it will convert the Touch Screen filters into the POS Menu filters. BUT there is a limitation in the POS Menus is that it accepts only one element in the filter fields.
For example, in touch screen, we could put Cash Register 1,2,3 as filters thus the button will be seen by the 3 registers whereas in POS Menus you can put only ONE filter. For that particular button, you will need to create it 3 times & then put the individual filter to it. The most common way will be to use Cash Register Type inseatd of Cash Register No. Then in the setup of the Cash Register, we attach it to the Cash Regsister type.
Another solution for the limitation of the filters, will be to create a different vies and attach teh Cash Register to that view in Default Views setup.
Views:
The main reason to create views is that if the layouts of the Cash Registers are different. In the Cash Register, we were able to create different layouts (number of boxes or button) for the register, whereas with Transcendence, we can move the sections of the screen to look different, hence it more flexible and at the same time more complicated to create and setup. Nevertherless, we have this facilty. In teh Demo Database, we ahve examples of different layouts of Cash Registers.
When we use the conversion tool, it will look at the Cash Register layout and if it is different, it will create a different view. Of course, we need to verify it and do manual corrections where required. For details on how to do view, refer to the section on view in this document.
Conclusion:
If we have different layout for different Cash Registers, then we use VIEWS or else we use FILTERS.

Appendix

As we are moving fast in Trancendence, the new functions are tested in company : Transcendence Test Company & TRANSCENDENCE Advance Post Company in \\npkcenter.local\desktopicons\_NPRetail_PreRelease (file://npkcenter.local/desktopicons/_NPRetail_PreRelease) .
If you are looking for a function, please check in the repository in the above company or in our Retail Demo in \\npkcenter.local\desktopicons\_Demo\RetailDemo2017 (file://npkcenter.local/desktopicons/_Demo/RetailDemo2017).