Unlike earlier versions, Lexacom uses cloud-hosted services to manage the system, including managing user accounts, teams, and their configuration, and to mediate the creation, retrieval, and progression of jobs through the system, and cloud storage to hold the jobs.
This allows users to log into Lexacom wherever it is installed, and access any of their teams and the corresponding jobs from any location. Installation of Lexacom does not require an on-site server or file storage, and users working from home do not require a VPN or special allowances for Lexacom to connect.
In order to be used effectively, Lexacom requires an internet connection to access these remote services. If the user has a steady internet connection and no other networking problems, Lexacom will be online, and all functions will work as described.
If the user does not have an internet connection, if there are networking problems preventing Lexacom from accessing necessary services, or in the unlikely event of temporary downtime to these services, Lexacom will go offline. The application will display the offline status in the window:
Additionally, certain controls (like the Job Notifications and Comments) may have an altered appearance.
Whilst offline, the following changes will be in effect:
Login
Users who were not logged into Lexacom before the device went offline will be unable to log in.
Users who were logged into Lexacom will remain logged in until they choose to log out. If the program is exited and restarted, the application will automatically open under their cached configuration, as if the '
Remember Me' option had been selected. The user may continue to use Lexacom whilst offline.
If the user is a member of multiple teams, they will not be able to switch teams whilst offline.
Creating new jobs
Users with a role that allows them to create jobs will continue to be able to create jobs whilst offline. The jobs that have been created whilst offline will be cached locally as
Pending Tasks and saved when Lexacom comes online. Whilst the jobs are pending the user will be able to reload and continue to work on these using the Load button in the
task queue.
Loading existing jobs
Users who had an existing job loaded before the device went offline will continue to be able to work on the job that they had loaded. Changes to the job will be cached locally as a Pending Task and saved when Lexacom comes online. Whilst the job is pending the user will be able to reload and continue to work on this using the Load button in the task queue.
Users will be unable to load other jobs (those not loaded before the device went offline, or created whilst offline) whilst Lexacom is offline.
