AutoClose property in Alarm Definition not saving via SDK

MIP
, ,
1

If you setup an Alarm Definition via the SDK, the AutoClose property does not get saved. You can reproduce this with the ConfigAPI application.

Add an alarm definition (Screenshot attached of my setup). Tick the AutoClose property. Click on save. Refresh the ConfigAPI application, browse to Alarm Definitions and notice that the AutoClose property is reset to “False”.

If I tick the AutoClose property in the Management Client on the same alarm definition, the property is saved correctly.

2

I was able to make the same observation on my test server. I will report this observation. I will update here on feedback on this issue..

3

Question: What XProtect product and version are you using?

4

Hi Bo,

I am using 2018 R2 for both VMS and SDK,

5

We have developed a fix for 2018R2. We would like your confirmation before making it an official fix with knowledge base article etc.

Please download apply the two executable fixes to the Management Server (2018R2).

Note that the fix is a cumulative patch installer and other known issues will be fixed alongside this issue.

Please provide feedback whether the fix works.

http://download.milestonesys.com/MTScases/MSC353000/

6

Do you have feedback for us?

7

Hi Bo,

Yes, I can confirm that the hotfix is working as expected.

Thank you,

Kind Regards,

Jaco de Meillon