The core application's installation is executed with the following steps:

1 Installation

To install the core application, the device must be able to access the APK application. This access may be granted by means of an email previously sent to the device, where the application is sent. It can also be granted by direct connection to a computer. Once we select the APK file, the device will ask for permission to install the application.

1.1 Screenshots of the Device's Application Installation Process

Request Permissions Installation Process Installation Complete

1.2 Emulator Installation

Genymotion is an app player which allows users to run Android applications from Windows. The application supports the following operating systems: Windows XP with SP3 or higher, Windows Vista, Windows 7, Mac OS. To download it, click here: http://www.genymotion.com/ A video tutorial showing how to download, install, and configure the emulator is also available there.

2 Main Menu

The main menu is displayed on the Tablet device screen, with pending images.

Main Screen Meaning of Icons

3 Extended Options

In the Application Main Menu, users can access certain data and configuration menus.

3.1 Setup

With this menu we can access terminal configuration, settings which can be modified from the device itself. It provides access to data associated with the store and used for print document headers.


User Configuration Settings Terminal (Device) Settings
Settings Related to the Store Corresponding to the Terminal Printer Settings

3.2 Information

With this menu we can access terminal configuration, settings which can be modified from the device itself. It provides access to data associated with the store and used for print document headers.


Terminal logs. Takes into account the logging level set in connection parameters. Technical details of the terminal, such as network, GPS, filesystem, etc. Set of scripts and their code present in the terminal.

3.3 Menu

This button provides direct access to the Axional Core application.

3.4 Synchronization

The synchronize button provides access to the synchronization menu, where users can specify the module they wish to synchronize or press All to synchronize all modules.

4 System

4.1 Branches

Menu path:
System / Local offices / Local offices
Mobile / Local offices / Local offices
Mobile CRM / System / Local offices / Local offices
Mobile / System / Local offices / Local offices
Sistema / Local offices / Local offices

Main Mobile Entity

Lists branches/offices registered in the system.

apps_sys_delegations
Label Description
Branch code Local office ID code

  • Case: Upshift
Name Store/branch name

4.2 Users

4.2.1 User Roles

Menu path:
System / Users / Roles of user
Mobile / Users / Roles of user
Mobile CRM / System / Users / Roles of user
Mobile / System / Users / Roles of user
Sistema / Users / Roles of user

Definition of roles assigned to users.

These roles determine which functions (buttons, processes) can be performed on a device.

apps_sys_role_head
Label Description
Code User role code

  • Case: Upshift
Description Name and description of role
Actions
Button Title Notes
BUT_ADD_ALL Add all null

4.2.2 Widgets

Each APPS user can have an Android widget installed on their mobile device. This widget contains buttons which perform specific actions. Both the buttons and the actions they trigger are defined by each user in the ERP.

To access this configuration, the user interface contains a tab called Widget Buttons, as shown in the Access image in the table below.

apps_sys_widget_buttons
Label Description
User code User code
Order Order in which buttons will appear inside the widget.
Label Descriptive label which appears under the button.
Text color Sets default button text color if no icon is defined.

Background color Sets button's default background color if no icon is defined.

Icon Icon displayed to activate defined actions.
Action code Code of an action which a button will perform
Countdown

The countdown allows you to cancel the launch of an action. The bottom of this section contains information related to all actions the button will perform. This includes the type of action, the order of actions if more than one option is defined, the description of the action, and a field action URI in which information related to that action is defined.



  • Default: 0
  • Values:
    • 0: 0.
    • 10: 10.
    • 20: 20.
    • 30: 30.
    • 40: 40.
    • 50: 50.
    • 60: 60.
Countdown message Message shown during the countdown
User created User created

  • Default: USER
Date created Date created

  • Default: CURRENT
User updated User updated

  • Default: USER
Date updated Date updated

  • Default: CURRENT
Actions
Button Title Notes
BUT_COPIAR Copy null


On the widget screen, there are five areas with different information areas:

  1. User configuration-related information is found here. This may include information such as the user code, user branch code, and type of login, among others.
    • Role Code: Identifies the user's role, and which buttons they are therefore able to access.
    • Menu Code: Identifies the menus which the user is allowed to navigate.
  2. In this second section, you will find information related to each button which the widget contains. These are explained in the table above.
  3. Widget Control Data: Control data includes who created and modified the widget, and when.
  4. Information: Lists all button icons defined for this widget. It is a purely informative field.
  5. View: Summary of all buttons, defined with their respective information. All buttons can be viewed at a glance.

4.3 Logins

4.3.1 User Logins

Menu path:
System / Users / Logins / User Logins
Mobile / Users / Logins / User Logins
Mobile CRM / System / Users / Logins / User Logins
Mobile / System / Users / Logins / User Logins
Sistema / Users / Logins / User Logins

This form is used to register users. All information needed to assign tasks and track users is described below.

apps_sys_users_login_codes
Label Description
Login code Login code
Name Name
Password Password

Branch code Branch code
Image Image
Fast login Fast login via NFC or Barcode
Role code Role code
Menu code Menu code
WMS Menu WMS Menu
Document type Type of document
Status Status

  • Default: A
  • Values:
    • A: Active.
    • B: Drop.
Synchronization date Synchronization date

  • Default: CURRENT
Registry user User who first entered/created the registry

  • Default: USER
Registration date Log entry date

  • Default: CURRENT
Update user Last user who modified the registry

  • Default: USER
Update date Date of most recent record modification

  • Default: CURRENT

4.3.2 Types of Access Control

Menu path:
System / Users / Logins / Types of Access Control
Mobile / Users / Logins / Types of Access Control
Mobile CRM / System / Users / Logins / Types of Access Control
Mobile / System / Users / Logins / Types of Access Control
Sistema / Users / Logins / Types of Access Control
apps_sys_users_login_acc_type
Label Description
Language Language
Code Control code
Description Description
Synchronization date Synchronization date

  • Default: CURRENT

4.4 Reports

4.4.1 Device Information

Árbol de menú.
Screenshot
Detailed Information
Detailed Information on Battery and GPS Usage
Detailed Information on Data Usage and HDR Activity

4.4.2 User Location

Menu
Screenshot

4.4.3 User Geopositioning

Menu
Screenshot

4.4.4 User Routes per Day

Menu
Screenshot

4.5 Masters

4.5.1 Languages

Menu path:
System / Master / Languages
Mobile / Master / Languages
Mobile CRM / System / Master / Languages
Mobile / System / Master / Languages
Sistema / Master / Languages
apps_sys_languages
Label Description
Code Language code

  • Case: Downshift
Language Language description

4.5.2 Dictionary

Menu path:
System / Master / Dictionary
Mobile / Master / Dictionary
Mobile CRM / System / Master / Dictionary
Mobile / System / Master / Dictionary
Sistema / Master / Dictionary
apps_sys_dictionary
Label Description
Language Language
Code Code
Description Description
Modification Date Date of modification

  • Default: CURRENT

4.6 Menus

4.6.1 Menu Definition

Menu path:
System / Menus / Definiton of the menus
Mobile / Menus / Definiton of the menus
Mobile CRM / System / Menus / Definiton of the menus
Mobile / System / Menus / Definiton of the menus
Sistema / Menus / Definiton of the menus
This option grants access to the definition and parameters of radiofrequency (RF) menus, from which users can create, modify, and delete said definitions if they have the necessary permissions.

Below are some considerations about menu settings and definitions:

  • Menus can be defined in tree form, with submenus. These submenus, in turn, have options which call certain screen formats. In addition, users can define as many menus as needed. Menus are generally defined according to user profile. Each user is assigned the menu which corresponds to their profile in the RF operators master document.


  • Available types of menus may include:
    Menu
    A submenu, where a value corresponding to submenu to call must be entered.
    Function
    A form, where a RF form must be entered in the value corresponding to Command.


  • From a form, users can set parameters to call up to two different menus, using the function keys defined in the terminal type associated with the terminal in use.

A graphic interface utility is available to make the creation and modification of radiofrequency menus simpler and more intuitive for the user. This option is called the Menu Editor.
apps_sys_menus
Label Description
ID Menu ID
Menu Menu
Root menu Root menu code
Order View order
Next submenu Next submenu
Description Description
Type Option type (Menu, Function, External Program)

  • Default: M
  • Values:
    • M: Menu.
    • R: Report.
    • S: SQL.
Arguments Arguments
Creator User who first entered/created the registry

  • Default: USER
Registration date Log entry date

  • Default: CURRENT
Updater Last user to modify the registry

  • Default: USER
Update date Date of most recent registry modification

  • Default: CURRENT

4.7 Scripts

4.7.1 Conceptual Map of Scripts

4.7.2 Script Structure

Menu path:
System / Scripts / Scripts
Mobile / Scripts / Scripts
Mobile CRM / System / Scripts / Scripts
Mobile / System / Scripts / Scripts
Sistema / Scripts / Scripts

The APPS system takes advantage of JavaScript to customize application actions and forms. At various points, each installation will require its own customizations, so as to be able to perform actions online with the application. These points may include loading, assignment validation, document editing, new customer registration, document line editing, payment verification, or printing. The apps_scripts table contains all Java programs synchronized to the device, which are interpreted by the application.

apps_sys_scripts
Label Description
Code Script code

  • Values:
    • ticketh.print: ticketh.print.
    • apps_pos_ticketh_open.edit: apps_pos_ticketh_open.edit.
    • apps_pos_ticketh_open.save: apps_pos_ticketh_open.save.
    • ticketh.validate: ticketh.validate.
    • ticketh.close: ticketh.close.
    • apps_customers_new.commit: apps_customers_new.commit.
    • apps_customers_new.edit: apps_customers_new.edit.
    • ticketl.validate: ticketl.validate.
    • apps_pos_ticketl_open.edit: apps_pos_ticketl_open.edit.
    • apps_pos_ticketl_open.save: apps_pos_ticketl_open.save.
    • main: main.
    • apps_sfa_task_assign.save: apps_sfa_task_assign.save.
    • apps_sfa_task_assign.commit: apps_sfa_task_assign.commit.
    • apps_sfa_task_assign.validate: apps_sfa_task_assign.validate.
    • apps_sfa_task_assign.edit: .
    • apps_pos_moveh.commit: apps_pos_moveh.commit.
    • apps_pos_cash.print: apps_pos_cash.print.
    • apps_pos_movement.print: apps_pos_movement.print.
    • apps_pos_moveh.validate: .
    • apps_pos_moveh.edit: apps_pos_moveh.edit.
    • apps_pos_moveh.save: apps_pos_moveh.save.
    • apps_pos_movel.edit: apps_pos_movel.edit.
    • assign_from_action.validate: assign_from_action.validate.
Description Script information
Script Script

Status Status

  • Default: A
  • Case: Upshift
  • Values:
    • A: Valid.
    • B: Drop.
Creator User who first entered/created the record

  • Default: USER
Registration date Log entry date

  • Default: CURRENT
Updater Last user to modify the record

  • Default: USER
Update date Date of most recent registry modification

  • Default: CURRENT

4.7.3 Main Script

The script with the main code will be executed when APPS is initiated. The program must return a [true/false] boolean value. The actions which can be performed include, for example:

*Verify, update, or delete data from the device database.

*Create triggers in the device database.

Example
Copy
// ******************************************************
//
// [main]
//
// Event launched upon loading POS apps
// 
// * Creation of the trigger apps_clientes_new_ins
// During client registration, a rate is assigned to the new client,
// to be used immediately. Both the client and their rate
// must be registered in apps_clientes_tarpre. 
//
//
// ******************************************************
 
    private boolean __create_trigger()
        throws Exception 
    {
 
        String statement = "@NATIVESQL.CREATE TRIGGER IF NOT EXISTS apps_clientes_new_ins AFTER INSERT ON apps_clientes_new BEGIN INSERT INTO apps_clientes_tarpre (codcli,tarpre,event_sync,date_sync)VALUES(new.codcli,new.tarpre,'A', CURRENT_TIMESTAMP); END;";
 
        Cursor c = context.getContentResolver().query(
            Constants.tableUri(sentencia),
            new String[] { "*" },
            "1 = 1 ",
            new String[] {},
            null
        );
 
        return true;   
 
    }
 
return __create_trigger();

4.8 Printers

4.8.1 Printer Schema



4.8.2 Printers

Menu path:
System / Printers / Printers
Mobile / Printers / Printers
Mobile CRM / System / Printers / Printers
Mobile / System / Printers / Printers
Sistema / Printers / Printers

The APPS system allows multiple alternative document printing methods. Printing can be performed through wifi, Bluetooth, or network/LAN. The system may also have an external APK for printing. For more information on printer configuration, see below.

apps_sys_printers
Label Description
Printer code Printer device code
Description Printer description
External printing External printing

  • Default: 0
  • Values:
    • 0: No.
    • 1: Citizen.
    • 2: Zebra.
    • 10: OTHER.
Print columns Columns for printing

  • Default: 80
  • Values:
    • 40: 40.
    • 80: 80.
Function start Function start
End comand End comand
Jump line Jump of line
Space white Space on white
Paper type Paper size, cut, etc.
Open cash box Open cash box
Fuente texto Font of the text
Bold text Bold text
Logo Logo
Horizontal space Horizontal space
Vertical space Vertical space
Vertical line Vertical line
Horizontal line Horizontal line
Top-left Top-left position
Top-center Top-center position
Top-right Top-right position
Bottom-left Bottom-left position
Bottom-center Bottom-center position
Bottom-right Bottom-right position
Mid-left Mid-left position
Center Center position
Mid-right Mid-right position
User created User created

  • Default: USER
Date created Date created

  • Default: CURRENT
User updated User updated

  • Default: USER
Date updated Date updated

  • Default: CURRENT

4.9 Customers

4.9.1 Customers

Menu path:
Mobile / Tasks / Customers / Customers
Mobile CRM / Tasks / Customers / Customers
Tasks / Customers / Customers
Point of sales (POS) / Customers / Customers
Mobile / Point of sales / Customers / Customers
Point of sales / Customers / Customers
This form will be filled in with all customer information, then used as a reference to help users correctly perform tasks.
apps_customers
Label Description
Customer code Customer code
Name Customer name

  • Case: Upshift
Group Group to which customer belongs
Name Customer name

  • Case: Upshift
CIF CIF (VAT identification number) of customer

Mobile number Customer's mobile phone number
Phone number Customer's secondary phone number
Contact Contact person
Address Customer address
City Customer city
Postal code Postal code
Province Customer province
Email Customer email address

  • Format: EMAIL
Price rate Price rate
Loyalty card Customer's loyalty card(s)
Payment status Status of customer's payments

  • Default: 0
  • Values:
    • 0: Valid.
    • 1: Pending payments.
    • 2: Defaulter.
Longitude Longitude
Latitude Latitude
Syncing event Event triggering synchronization

  • Default: A
  • Values:
    • A: Load.
    • B: Drop.
Modification date Date of modification

  • Default: CURRENT
since

4.9.2 New Customers

Menu path:
Mobile / Tasks / Customers / New clients
Mobile CRM / Tasks / Customers / New clients
Tasks / Customers / New clients
Point of sales (POS) / Customers / New customers
Mobile / Point of sales / Customers / New customers
Point of sales / Customers / New customers

This form contains a viewable list of users in the system (app customers), with all their corresponding information.

apps_customers_new
Label Description
User code User code
Terminal Terminal ID
Customer code Customer code
Name Name of customer
CIF Customer's CIF (VAT identification number)
Mobile number Customer's mobile phone number
Phone number Customer's secondary phone number
Postal code Customer postal code
Contact Contact person
Address Customer address
City Customer city
Email Customer email address
State Customer state

  • Default: P

4.9.3 Excel Customer Data Load

Menu path:
Mobile / Tasks / Customers / Download costumers' Excel
Mobile CRM / Tasks / Customers / Download costumers' Excel
Tasks / Customers / Download costumers' Excel
Point of sales (POS) / Customers / Download costumers' Excel files
Mobile / Point of sales / Customers / Download costumers' Excel files
Point of sales / Customers / Download costumers' Excel files
apps_excel_customer_load_head
Label Description
Identifier Identifier
Name File name
File File
Size File size

  • Default: size(file_data)
file_info
Status File status

  • Default: 0
  • Values:
    • 0: Pending.
    • 1: Processed.
User created User created

  • Default: USER
Date created Date created

  • Default: CURRENT
Actions
Button Title Notes
BUT_EXECUTE Execute Button used to execute the process to turn over the data from the Excel file to the system.