The Traka Asset Management plugin 3.1 includes the following known issues.
| Issue | First reported in | Description |
|---|---|---|
| 2298137 | 3.1 | If changes were made in the Events page of the plugin role
while the Traka monitoring task is open, the changes are not
dynamically updated. Workaround: To see the
updated list of events in the Events filter, close the Traka
monitoring task, and then reopen it.
|
| 2415413 | 3.1 | If a Traka service is restarted on the Traka Integration Engine server, you must deactivate, and then reactivate the Traka Asset Management plugin role on the Security Center server. |
| 2416456 | 3.0 | Federation™ is unsupported. On a federated host, you can receive Traka events, but the Traka entities (cabinets and iFobs) cannot be monitored. |
| 2434069 | 3.1 | In the Traka Asset Management plugin role's Events page,
if you re-select a custom event that was previously deleted, the history of events
for the original custom event are
deleted. Workaround: Avoid clearing the custom event check box.
|
| 2492240 | 3.1 | When access rules are assigned to assets (iFobs) in Security Center, the attached schedules are ignored
by the Traka system because schedules are not synchronized. Workaround: To control access to assets (iFobs) based upon day and time,
in Traka Web, create Access Schedules and assign them to
the user’s profile or an iFob attached to a key or an asset.
|