Wovex is a cloud-based solution and so will run on any browser on Mac or PC or mobile. Chrome is our recommended browser.

It can be hosted in a Wovex-managed Azure Cloud environment or hosted behind your firewall when you have extremely high-security requirements.

If you have any questions on your configuration then do contact us at [email protected].

If you want to extend your licence and you do not have an agreement in place then please raise a ticket here or contact your Wovex representative.

Yes. Wovex provides user and role-based permissions management. Our cloud platform is hosted on Microsoft Azure and has access to the Azure Active Directory services, including AD Identify Protection.

Wovex Cloud supports multiple, simultaneous users in many ways.

Multiple users can log in as they all have separate logins and are allocated permissions based on roles. Queries can all be done simultaneously. When updating data then the records are locked to a user when updating and other users accessing are warned. The editing user and other details can also be seen if required. If a user comes out by e.g. closing the browser, then the lock is timed out after a certain period.

When mapping Wovex lets you know when someone else is editing the same map view as you and if they change anything alerts you to refresh your screen so as not to overwrite their work. This supports teamwork with mapping and group workshops.

There are different settings available to enable Wovex to support you in how you want to work. If you don't have access to something get in touch with your Administrator or Wovex support.

All Wovex products are accessed on the cloud or internally hosted by customers.

Wovex was originally a Microsoft Windows-based desktop Mapping and Tracking application and the move to a fully http-browser-based version is now complete.

Today, Wovex Mapping, Data management, Tracking, Reporting (including Dashboards, Tracking Agreements, etc.) and administration are all in the cloud.

Overview

A user is anyone who accesses the system. Each needs a user account and licence.

To create a user account a unique company email address is needed.

The Super-User of the system will set them up and send them a username and password.

Why is a unique user account needed?

1. This allows the user to connect and use the system.

2. Wovex can ensure that the organisation has and is using valid licenses.

3. The organisation needs to ensure that each user can access only appropriate areas, functions and data.

4. Any audit and change logs are also connected to the appropriate user account.

User accounts are easy to set up and manage.

Sharing of a single licence is not permitted

Under the Wovex software licence agreement accepted when accessing the software, each person must have a unique named user licence.

In addition, the hardware or software you use to pool connections or reduce the number of devices or users that directly access or use the software (sometimes referred to as "multiplexing" or "pooling") does not reduce the number of licences you need.

In such case, one software licence per assigned user is required (named user licence). The Wovex software may not be shared, installed or used concurrently on different computers. Wovex monitors the access behaviour and identifiers of devices used through our license management system.

To check your licence availability get in touch with your SuperUser or send us a message on Messenger.

There is a rare issue with Google Chrome browsers that is easily solved.
It relates only to one pop-up message: when you exit a form without saving changes.

The situation:

If you don't save changes on a form and look to exit the form, the Wovex system will warn you.

If this message freezes up your browser then there is an issue with your browser.

The resolution:

These are the troubleshooting options provided by Google:

1. Introduction

Wovex can be implemented either in the cloud (default) or on a server hosted by your organisation (on-premise).

On-premise hosting involves Wovex providing an update package for installation.

More information is below. This requires the Enterprise features addition to your Plan.

2. Start with a cloud environment

Many customers choose first to have onboarding and training in a cloud environment. Then, have this transferred to an internal server when ready.

This has the advantage of Wovex having access to the environment for set-up and configuration. Also, this means that access to and experience of Wovex can be quickly gained without waiting for your server to be made ready. A Wovex-hosted cloud environment can be typically set up within 24 hours.

This is the recommended first step - create a temporary cloud environment.

3. Moving to on-premise

Wovex will be packaged into a zip file and shared with your technical team in a file location/method they prefer.

This will include all the settings, items, data etc., that were set up and used in the cloud.

This typically takes Wovex 3-5 days to complete but can be completed faster if required.

Your technical team can then install the following components onto an internal server.

Typically, the server selected is a virtual Windows server with approximately:

- 32Gb of RAM

- 4 Cores

- 100 GB of storage

Dependencies include:

The App, Database and Storage can all be on the same server.

SendGrid is used to manage the sending of emails. For example:

Alternative email services, like Mandrill, can also be used.

4. Updates

App code updates are typically sent every three months. More frequent updates can be provided for critical changes or when new functions are urgently needed. Zip files are shared in the agreed location.

On-premise customers can have multiple separate environments, for example, for Production, Test and Training.

Each can have its own App Code and Database.

A standard process is to install each update on the Test environment and then update Production after any required tests have been performed.

5. Additional information

It is recommended that your server is regularly backed up to disk.

You need to decide the retention schedule, so how long to keep backups, for example, for three years.

There is no standard requirement for constant synchronisation between databases.

Wovex does not need a separate licensing server.