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
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

  • Default: USER
Date created

  • Default: CURRENT
User updated

  • Default: USER
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.