4.14.0001 (Service release 2)

- Updating must be carried out by an installer with knowledge of the particular VAKA system.

- Updates must be made on site.

- Before updating to a new VAKA version, it is important to ensure compatibility with integrated third-party solutions * . Examples of such solutions are Renz mail boxes and Amido Alliera. To avoid operational disturbances, check with respective party that applicable versions are compatible.- Before updating, ensure that system security is set to the default level (Settings->System->Security).

- After updating, it can take up to 45 minutes before the system is fully operational.

What is new?

Booking

• Added the possibility to abort an on-going booking.
• Re-introduced possibility to request new password via e-mail.
• Faster page loading at login and a page loading icon when page loading is in progress.
• Introduced activation of all/parallel bookings behind common end node.
• Fixed issue with activation of booking object behind door leading to more than one booking object.
• Fixed assignment of default booking object in settings for C200-C205.
• Removed display of name for logged in user in the booking panel (C200-C205).
• Fixed an issue where iOS displayed a corrupt view of the booking schedule when the number of intervals was not the same for all days of the week.

VAKA Admin (Needs a B60)

• Fixed issue with activation of Save button.
• Added confirmation request when removing users with admin rights.
• Fixed conflict between card types.
• Fixed problem with reset of private PIN.
• Changed field names in door view.
• Added access group to event Group code used.
• Fixed problem when downloading backup when the system name contained special characters.
• Added limitation to remove logged in user.
• Fixed problem when previewing PDF documents in Information Center
• Fixed problem with removal of time schedule from access group

Java/PC-Klient

• Fixed problem with upper/lower case user names
• Fixed problem when user list got stucked in Not possible to leave while loading data.
• Changed process at deployment and registration.
• Added limitation to remove logged in user.

General improvements

• Added event for Smart-Call number conflicts
• Fixed problem with locking of bistable unlocked doors at log in or saving of back-up.
• Support for B27-R from serial number 108001.

Alarm related improvements

• Changed behaviour for automatically setting the alarm. After unset, attempt to set is performed after the configured time to automatically set the alarm. This is provided that the system is configured to set automatically at this time. Previous behavior was to try to arm at fixed times, regardless of when disconnection was made.
• Fixed problem with alarm menu was presented at the wrong time.
• Implemented check to not allow access to alarm zone when waiting for ASF.

Update information

Before updating to 4 SR2, the system must be at least version 3.86, 3.87 or 3.88. In case the system is in older version, follow previous update instructions to upgrade to any of the 3.8 versions.

For questions and for help with updating, please contact technical support, +46 (0)8-722 34 40, button selection 2 or [email protected].

After upgrade, the following versions apply

Update inside VAKA generation 4

Follow the instructions for Manual update with the package vaka-mini-4.14.0001.vfp).

Uppdate from 3.86, 3.87 eller 3.88

To do before updating

Configure system security

Ensure that the system security is set to the default level (Settings->System->Security).

Create a backup of system data

Back up system data by following the instructions, in the JAVA/PC client, at Settings -> Backup .

Back up relevant events

In the JAVA client, filter out relevant events and export them to a CSV file.

Open port 443

After the update, some communication will take place via HTTPS. Therefore port 443 must be open where system parts communicate between network segments and where connection for remote administration is needed.

If there is at least one B60 in the system

Restart all B60s by:

1. From Main Menu in B60, navigate to Tools and press return.
2. Navigate to Restart Device and press return.

Update

System without B60

Follow the instructions for Manual update with the package vaka-mini-4.14.0001.vfp).

System with B60

Follow the instructions for Manual update with the package vaka-maxi-4.14.0001.vfp).

To do after update

Set country- and area code

To prepare for future features, the Country Code and Area Code for the intercom need to be entered upon first login after update. This is done in the dialog that is presented.

Associate email address with migrated administrators and installers

When updating to VAKA 4, or later, previous administrators and installers are migrated to users/persons with roles (and rights) to interact with VAKA. Theese users should be given valid e-mail addresses. Please note that, when an e-mail address is specified, this is used as the username when logging into VAKA.

Change playlists from HTTP to HTTPS

If there are playlists where HTTP is used, these must be changed to HTTPS.