The deister proxSafe plugin 3.2.0 integration includes the following known issues.
| Issue | Description |
|---|---|
| 3012158 | For systems with a large number of entities, opening custom tasks related to deister, can result in Config Tool or Security Desk freezing |
| 3069765 | After you upgrade, assets might be missing from the plugin cache, which
prevents them from being assigned to cardholders. NOTE: Conduct a manual
synchronization to update the plugin cache.
|
| 3043977 | A key assignment can be pushed to cardholder when the plugin is showing a warning that indicates that the cardholder has been assigned multiple schedules. |
| 2586881 | A ghost camera can be assigned to a deister terminal or cabinet. This is not recommended, as ghost cameras do not provide video. |
| 2421809 | In the entity browser of a Federated system, all terminals, lockers, and assets
related to the deister proxSafe plugin have tile plugin icons ( ) |
| 742263 | If a cardholder is assigned multiple credentials, only the first card credential and the first PIN credential, or the first card and PIN credential, are valid on the proxSafe system. |
| 742138 | In the proxSafe Asset inventory report, if you have other plugins installed, you might see entities that are unrelated to the proxSafe system in the Entities filter list. |
| 697865 | There is no way to validate whether the proxSafe dataComm engine is running. You are only able to see if the proxSafe web service is online. |