Alertrow removes values when Priority is not column 2

[joost.lijster@siemens.com]

When configuring the alert row, I wanted the priority column to be column #7. In the alertrow configuration panel, I removed the columns that were not applicable for me, added a few extra and moved the Priority column to # 7.

When starting the alert row in a panel, it turns out that all values in column 2 had changed to "0".

A little research shows that the function aes_formatPriorityToInt() in the aes.ctl library is hard coded to update the alert priority to an integer, at column 2 (see code below).

In my opinion, this should be made more intelligent. Currently, this makes it impossible to shift the priority to any other column.

Code: Select all

aes_formatPriorityToInt(dyn_dyn_anytype &xtab)
{
  int ixtab;

  // read the result array
  for(ixtab=1;ixtab<=dynlen(xtab[2]);ixtab++)
  {
    dyn_anytype atValueOld, atValueNew;
    int iLen;

    // read the current value
    atValueOld = xtab[2][ixtab];
    //          ^^^^^^^ 
    //
    //  COMMENT: This column should be determined intelligently!
....

[leoknipp]

The problem is already known and we are working on a solution.
Possibly with the next patch the problem will be solved.

Best Regards
Leopold Knipp
Senior Support Specialist