I did a little testing and have found there are number of fields that do not reflect the values supplied in the JSON payload. When the alarm comes through and is in the nas, these fields have values that are supplied by the robot/probe running the uimapi. Among those that I attempted to supply customized values for are userTag1, userTag2, robot, probe, timeOrigin, and subsystem. The probe always comes in as wasp and the robot is the robot running the wasp/uimapi. The time origin is always when the alarm was actually created (I'll assume the other timestamp fields will behave the same). The subsystem is always "1.1 Alarm" and the user tag values are whatever the robot has. The custom 1 - 5 fields do take the values as supplied. The assignedTo and assignedBy also have no affect.
------------------------------
[Designation]
[City]
------------------------------
Original Message:
Sent: 07-31-2020 09:37 AM
From: David MICHEL
Subject: UIMAPI Create alarm
Was just looking at the swagger and it does have the fields for usertag.
my best guess based on the info provided there are fields missing which are required for usertag to work.
Based on Gene's comment that would probably robot, and likely more.
------------------------------
Support Engineer
Broadcom
Original Message:
Sent: 07-31-2020 08:02 AM
From: Oswaldo Muñoz Matos
Subject: UIMAPI Create alarm
Hi,
I have created an alarm using UIMAPI, but i can't modify the parameters userTag1 and userTag2. Can i do that?
I have used the following:
But, the alarm was created with the userTag1 and userTag2 fields empty.
Thanks for your help.