In this module, you can make fundamental business modifications, such as changing the map provider, importing GeoJSON data, or enabling or disabling features for field specialists.
1. In the Aranda FIELD SERVICE web console, in the heading menu select the “Profile” option.
2. From the main menu select the Global Settings. In the Info View, turn on the Enable Editing and in the detail view, complete the Global Settings and Map Settings information for the selected profile.

3. When you enable the editing of global settings fields, a confirmation message is displayed to warn you of the changes to be made to the tool.
4. In the Global Settings Detail View in the AFLS web console, select the Global Settings, where you can customize four operating parameters; The configuration of these parameters directly affects the operation and performance of the tool.
Application
In this option you can define the configuration parameters for the system in general:

Fields | Description |
---|---|
Update AFLS Base Route: | Enter the public URL of the AFLS instance here. |
Enable Log Map Consumption: | Enable or disable map consumption logging for your app. |
Default domain: | Select the domain that will be displayed by default in the login when entering the application. |
Hide Login Screen: | Allows you to enable or disable Login by domain for application login. |
Token Expiration Time in AssistMe (Days) | It allows you to configure the maximum time for the expiration of the client token when you log in to the AssistMe application. |
⚐ Note: After enabling or disabling the app’s map consumption log, you need to log out and log in again to view the change.
Specialist console
In this option, you can define the configuration parameters to enable or disable functional capabilities for field specialists.

Fields | Description |
---|---|
Edit or Create Customers and Create Orders: | Enable or disable the functional capabilities of creating, editing customers, or creating work orders to all field specialists. |
News URLs: | Enter the public news URL here so that field specialists can view the content in the mobile app. |
⚐ Note: After enabling or disabling any of the options in the Specialist Console, specialists need to log out and log in again before they can view the changes.
Assignment
Depending on the type of business, you can decide under what circumstances work orders are reassigned in the system. You can enable or disable the following options:
- Reassign orders due to availability change, inactivity, or license revocation.
- Maintain the assignment of manual orders, even if they have expired (otherwise they become automatic)
- Take the last location reported for work order assignment (otherwise the location associated with the specialist profile or facility location will be taken).
- Automatically assign tasks to the work order specialist. (When enabled, the option allows you to automatically assign the specialist, the date and time of the tasks associated with the work order.)

Integration
This parameter complements the integration with the ASDK tool by configuring the AFLS work order execution notification to ASDK field tasks. For newer versions of AFLS and ASDK, we recommend selecting the Direct integration type, which allows AFLS and ASDK to interact directly. To integrate via the WSO2 integration bus, select the ESB option. If you chose direct integration, you need to fill out the following fields:
Fields | Description |
---|---|
Username for connection | Integration username and password |
Additional User Name for ASDK Solution | If you are having field feed rule solution of a case in ASDK from an AFLS work order, you can place the system name of an additional AFLS field for this purpose. |
ASDK status approval: | This option allows you to make ASDK and AFLS state ID pairs when state changes are to be reported from AFLS to the ASDK. |
Homologation of AFLS states from ASDK: | This option allows you to make state ID pairs of AFLS and ASDKs when state changes are to be reported from ASDKs to AFLS. |

Storage
In this option you can define the configuration parameters either local, remote or external for the physical storage of the files that are uploaded to the application:

File: Allows you to perform local or remote file system configuration. When you select the Local file system, the following fields are enabled:
Fields | Description |
---|---|
Path: | It allows you to place the physical path where you want to save the files uploaded to the application. |
When you select the Remote file system, the following fields are enabled:
Fields | Description |
---|---|
Path: | It allows you to place the physical path where you want to save the files uploaded to the application. |
User: | It allows you to configure the user with whom the connection to the remote route is going to be made. |
Password: | It allows you to configure the password of the user with whom the connection to the remote route is going to be made. |
Domain | It allows you to place the domain of the user who is going to connect to the remote path. |

External: Allows you to configure the External file system in a storage account (Azure). When you select the External file system, the following fields are enabled:
Fields | Description |
---|---|
Supplier: | It allows you to select the external provider where the physical files uploaded to the application will be stored, at the moment only the Azure option is displayed. |
Connection String: | Allows you to configure the connection string of the storage account provided by the third-party provider to make the connection. |
Validate button | It is displayed in both options (File or External) and allows you to check that the configuration supplied in the module allows the correct connection to any of the file system options |
Save button | Allows you to save settings for the file system. |
5. When you finish configuring the global settings, click Save in the Detail View of the AFLS Configuration Console, to confirm the changes made.