Change log - Revision history

Telcredstaff at 07:03, 31 May 2018

2018-05-31T07:03:48Z

@@ Line 1: / Line 1: @@
 === 2018-05-22 (Update #344) ===
@@ Line 7: / Line 19: @@
 '''Improvements and bug fixes'''
-* Presentation to the reader of a registered card with no user will now create event in the event log.
+* Presentation to the reader of a registered card with no user will now create events in the event log.
 * Under some circumstances there could be two offline events without an online event or the other way around. This has been fixed.
 * The controller could still be marked as healthy (“Online”) even if the responses were incorrect. This has been fixed.

Telcredstaff: /* 2018-05-22 (Update #344) */

2018-05-22T15:57:19Z

2018-05-22 (Update #344)

← Older revision		Revision as of 15:57, 22 May 2018
Line 11:		Line 11:
	* The controller could still be marked as healthy (“Online”) even if the responses were incorrect. This has been fixed.		* The controller could still be marked as healthy (“Online”) even if the responses were incorrect. This has been fixed.
	* In the web GUI, start dates now default to the previous day in GMT to make sure to be before the current time regardless of timezone.		* In the web GUI, start dates now default to the previous day in GMT to make sure to be before the current time regardless of timezone.
	* The difference between Restart and Reset has been clarified In the web GUI, and the feedback during the operations has been improved.		* The difference between Restart and Reset has been clarified in the web GUI, and the feedback during the operations has been improved.
	* An FW update will no longer automatically be triggered when an unsupported FW version is found running on an A1001.		* A FW update will no longer automatically be triggered when an unsupported FW version is found running on an A1001.
	* The feedback during FW update has been improved.		* The feedback during FW update has been improved.
	* The credential settings of policies can no longer be changed in conflict with the authorizations using the policy.		* The credential settings of policies can no longer be changed in conflict with the authorizations using the policy.

Telcredstaff: /* 2018-05-02 (Update #344) */

2018-05-22T15:08:01Z

2018-05-02 (Update #344)

← Older revision		Revision as of 15:08, 22 May 2018
Line 1:		Line 1:
	=== 2018-05-02 (Update #344) ===		=== 2018-05-22 (Update #344) ===

	'''New features'''		'''New features'''

	* None		None

	'''Improvements and bug fixes'''		'''Improvements and bug fixes'''

Telcredstaff at 15:06, 22 May 2018

2018-05-22T15:06:35Z

← Older revision		Revision as of 15:06, 22 May 2018
Line 1:		Line 1:
			=== 2018-05-02 (Update #344) ===

			'''New features'''

			* None

			'''Improvements and bug fixes'''

			* Presentation to the reader of a registered card with no user will now create event in the event log.
			* Under some circumstances there could be two offline events without an online event or the other way around. This has been fixed.
			* The controller could still be marked as healthy (“Online”) even if the responses were incorrect. This has been fixed.
			* In the web GUI, start dates now default to the previous day in GMT to make sure to be before the current time regardless of timezone.
			* The difference between Restart and Reset has been clarified In the web GUI, and the feedback during the operations has been improved.
			* An FW update will no longer automatically be triggered when an unsupported FW version is found running on an A1001.
			* The feedback during FW update has been improved.
			* The credential settings of policies can no longer be changed in conflict with the authorizations using the policy.
			* An event, single locked, could occur following a grant access event although no explicit locking had been performed. This has been fixed.
			* In the web GUI, the policy page will now include visits that use the policy.

			=== 2018-05-08 (Update #343) ===

			'''New features'''

			* The system now detects when an A1001s has been used elsewhere and needs to be reset before it will function properly. In the GUI the controller is marked “Offline” and the reason is displayed. The same information is available via the API.

			'''Improvements and bug fixes'''

			* Under some circumstances newly created system owners would not be usable. This has been fixed.

	=== 2018-03-26 (Update #341) ===		=== 2018-03-26 (Update #341) ===

Telcredstaff at 12:51, 29 March 2018

2018-03-29T12:51:16Z

← Older revision		Revision as of 12:51, 29 March 2018
Line 1:		Line 1:
	=== 2018-03-26 (Update #341 ===		=== 2018-03-26 (Update #341) ===

	'''New features'''		'''New features'''
Line 10:		Line 10:
	* The web server can be configured behind a load balancer to run without SSL.		* The web server can be configured behind a load balancer to run without SSL.
	* Contact Daemon start up is softer on the database.		* Contact Daemon start up is softer on the database.


	=== 2018-03-23 (Update #340) ===		=== 2018-03-23 (Update #340) ===
Line 25:		Line 24:
	* Controllers were being bothered for every update action even if there was no actual change, This will happen less often now.		* Controllers were being bothered for every update action even if there was no actual change, This will happen less often now.
	* Redundant schedule events will no longer trigger visits to Controllers. E.g. before this update, all controllers were visited at midnight every day.		* Redundant schedule events will no longer trigger visits to Controllers. E.g. before this update, all controllers were visited at midnight every day.


	=== 2018-03-20 (Update #335) ===		=== 2018-03-20 (Update #335) ===

Telcredstaff at 12:49, 29 March 2018

2018-03-29T12:49:56Z

← Older revision		Revision as of 12:49, 29 March 2018
Line 1:		Line 1:
			=== 2018-03-26 (Update #341 ===

			'''New features'''

			* The maximum PIN length can now be set per organization.

			'''Improvements and bug fixes'''

			* The lock status will no longer show Locked when passing between Double Locked and Unlocked.
			* The web server can be configured behind a load balancer to run without SSL.
			* Contact Daemon start up is softer on the database.


			=== 2018-03-23 (Update #340) ===

			'''New features'''

			None

			'''Improvements and bug fixes'''

			* An officer that only has access to one organization can now be deleted by the owner.
			* Filling up fields with with more data than the field can store now results in a more helpful error message in the GUI and the API.
			* Entering a non numeric value in a time field nw results in a more helpful error message.
			* Controllers were being bothered for every update action even if there was no actual change, This will happen less often now.
			* Redundant schedule events will no longer trigger visits to Controllers. E.g. before this update, all controllers were visited at midnight every day.


	=== 2018-03-20 (Update #335) ===		=== 2018-03-20 (Update #335) ===

Telcredstaff: Created page with "=== 2018-03-20 (Update #335) === '''New features''' None '''Improvements and bug fixes''' * Faster updates of lock state and door state when lock or door monitor configur..."

2018-03-27T11:41:54Z

Created page with "=== 2018-03-20 (Update #335) === '''New features''' None '''Improvements and bug fixes''' * Faster updates of lock state and door state when lock or door monitor configur..."

New page

=== 2018-03-20 (Update #335) ===

'''New features'''

None

'''Improvements and bug fixes'''

* Faster updates of lock state and door state when lock or door monitor configuration is changed.
* Added internal management capabilities for deleting and restoring systems.
* Fixed an issue with the process that fetches events from the A1001 where it could become hanging under certain circumstances.

=== 2018-03-14 (Update #334) ===

'''New features'''

None

'''Improvements and bug fixes'''

* Upgrade of internal frameworks.

=== 2018-03-13 (Update #333) ===

'''New features'''

None

'''Improvements and bug fixes'''

* A defect where clicking on a role on the web GUI role list page could yield an internal error message has been fixed.
* A defect that could cause the lock state of a door to be incorrectly reflected in the API and the GUI has been fixed.

=== 2018-03-07 (Update #332) ===

'''New features'''

None

'''Improvements and bug fixes'''

* Schedule override is now maintained over a controller reset.
* Controller restart is faster and the feedback in the web GUI and API is clearer.
* A door unlocked by schedule can no longer get into a state where it will not lock when the schedule becomes inactive.

=== 2018-03-01 (Update #331) ===

'''New features'''

None

'''Improvements and bug fixes'''

* Hacking the URL of a web GUI page with an unknown door id will no longer cause an internal error.
* Schedule override can now be entered and set to the state that the controller already is in.

=== 2018-02-23 (Update #330) ===

'''New features'''

None

'''Improvements and bug fixes'''

* Fixed synchronization which after build 328 would put the controller in a state where it would not function properly until restarted.

=== 2018-02-22 (Update #329) ===

'''New features'''

None

'''Improvements and bug fixes'''

* The restart and reset buttons on the Web GUI controller page will now attempt to contact the controller regardless of if it is considered to be online or not.

=== 2018-02-22 (Update #328) ===

'''New features'''

* The new section 'Status’ on the Web GUI door page shows the current lock state, door state, and controller connection state.
* In the new section 'Actions' on the Web GUI door page, there are now buttons to override the normal locking (Unlock, Lock, and Double lock) and a button to remove the override (Return to schedule). When any of the override buttons are pressed, the schedule, if any, is deactivated and the lock state is set. When 4 is pressed the schedule is reactivated and applied so that the lock state is set in accordance to it.
* In the new section 'Actions' on the Web GUI controller page, there are now buttons to restart and reset the connected controller.
* On the Web GUI controller page the controller connection status is now shown in the new section 'Status.

'''Improvements and bug fixes'''

* Firmware version on the web GUI controller page will now auto update if the page is left open.

=== 2018-02-19 (Update #326) ===

'''New features'''

None

'''Improvements and bug fixes'''

* When firmware updates are requested in tight succession, the controller is now given a 30 second rest in between that has been found to be beneficial.
* The free form info in the GUI and API regarding the state of the controller connection will now reflect on-going restart or firmware update more accurately.

=== 2018-02-13 (Update #325) ===

'''New features'''

None

'''Improvements and bug fixes'''

* The firmware update request is given a more liberal timeout setting.

=== 2018-02-12 (Update #324) ===

'''New features'''

None

'''Improvements and bug fixes'''

* The firmware version field, including the pending version, on the door page, is now auto updated.

=== 2018-02-09 (Update #323) ===

'''New features'''

None

'''Improvements and bug fixes'''

* In the web GUI, door status information (lock state and door state) will now always be displayed as unknown if the controller is not available.
* A controller in an erroneous state where certain requests succeeded but others failed, could cause its status in Access Manager to flip between online and offline. The likelihood of this happening has now been reduced.

=== 2018-02-07 (Update #322) ===

'''New features'''

None

'''Improvements and bug fixes'''

* A controller could incorrectly show the "Ready to connect" status in place of the "Offline" status.

=== 2018-02-07 (Update #321) ===

'''New features'''

* Access can now be granted by an officer on the door page in the web GUI.

'''Improvements and bug fixes'''

* It is now easier to undo a firmware update. You are no longer forced to wait for the first to finish before requesting a revert.
* On the web GUI event page, the method name API has been changed to Officer.

=== 2018-02-05 (Update #320) ===

'''New features'''

* The A1001 firmware upgrade feature is now available in O3C mode.
* A "Controller status" column has been added to the door list page.

'''Improvements and bug fixes'''

* The communication with the A1001 over O3C has been simplified and made faster.

=== 2018-02-01 (Update #319) ===

'''New features'''

None

'''Improvements and bug fixes'''

* Using the term firmware update instead of upgrade through out the GUI since it is possible to downgrade the version should one chose to.
* Improved handling of failed firmware updates.

=== 2018-02-01 (Update #318) ===

'''New features'''

None

'''Improvements and bug fixes'''

* A door’s door monitor state will change to Unknown if the monitor is removed from the controller reconfiguration.
* In the GUI, polices, that through their credential setting are unsuitable for a particular authorization (i.e. role, assignment, or visit), will no longer be displayed as an option when creating or updating the authorization.
* A controller’s firmware versions is now displayed in full regardless of it’s length.
* The filter fields on the list pages now always expand to the full with of their column.
* The mobile phone public key is no longer displayed on the device page.
* The default active period for a device is now one year.
* A door’s lock state will now be displayed also in the case where it is not on a schedule.

=== 2018-01-29 (Update #317) ===

'''New features'''

* This version features the direct connection (not O3C) edition of the capability to upgrade a controller’s firmware from the GUI.

'''Improvements and bug fixes'''

* Properties “internalIp” and “fwVersion” were added to the API Controller object.

=== 2018-01-22 (Update #316) ===

'''New features'''

None

'''Improvements and bug fixes'''

* The displayed online/offline state of a controller could become inconsistent with the detailed information regarding the connection if the connection mode (Direct/O3C/Shortcut) was changed. This has now been fixed.
* When responses from the A1001 contained a very large number of items, the log lines would become impracticably long. Requests to the A1001 are now limited to 500 items.
* We now not only set each controller to stand-alone mode but, per Axis recommendation to further improve stability, also disable global event distribution.
* Filtering by door state “Open” now includes "Forced open" and "Open too long”.
* The performance of the device list page for organizations with a large number of devices has been quite substantially improved.
* The controller list page now supports sorting by Internal IP or Firmware version.

=== 2018-01-17 (Update #315) ===

'''New features'''

None

'''Improvements and bug fixes'''

* PUT via the API, or Save via the GUI, that actually do not cause a change to the model, will no longer lead to A1001s being visited, which reduces unnecessary network traffic.
* Protocol adjustments to match the upcoming version of the Telcred Entry app.

=== 2018-01-12 (Update #314) ===

'''New features'''

None

'''Improvements and bug fixes'''

* Fixed bug where a user with access rights to a door (A) could incorrectly receive access rights to a door (B) if:
** Both A and B are controlled by the same controller
** Both A and B are in door groups.
** There is an active policy for each door group.
* Fixed bug preventing new controllers from connecting.

=== 2018-01-10 (Update #313) ===

'''New features'''

None

'''Improvements and bug fixes'''

* ContactDaemon stability.

=== 2018-01-10 (Update #312) ===

'''New features'''

None

'''Improvements and bug fixes'''

* ContactDaemon stability.

=== 2018-01-10 (Update #311) ===

'''New features'''

* We now display the A1001 firmware version in the GUI.
* We now display the internal IP address of the A1001 in the GUI.
* We now display “URL” as the method in log events where a URL was used as the credential.

'''Improvements and bug fixes'''

* API v1 has been taken out of commission.
* Device types are now consistently named through-out the GUI.
* The protocol between Telcred Entry and Access Manager has been updated to omit ACCESS_GRANTED from the door lock state property.