Preset API REST have change the documentation is old

1

Hello Community,

I have couple of questions about the Preset API and how i should implemented it,

We use the API to add/edit/show the preset to our environment in older version, but we change to new latest version now and there are some strange behaviors.

  1. The Data we send is like as its on documentation for preset preconditions:
    API Reference — GenieACS Documentation 1.2.13 documentation

example
[precondition] => {“Device.DeviceInfo.SerialNumber”:“AAA”,“Device.DeviceInfo.SoftwareVersion”:{“$ne”:“BBB”}}

The new GenieACS version UI transform it like this:
Device.DeviceInfo.SerialNumber = “AAA” AND (Device.DeviceInfo.SoftwareVersion <> “BBB” OR Device.DeviceInfo.SoftwareVersion IS NULL)

if we try to edit this preset now from GenieACS UI and save it the return over the API is:

[precondition] => Device.DeviceInfo.SerialNumber = “AAA” AND (Device.DeviceInfo.SoftwareVersion <> “BBB” OR Device.DeviceInfo.SoftwareVersion IS NULL)

nothing like the old structure this is normal behavior?

After that i have change the API calls to send back lines like
[precondition] => Device.DeviceInfo.SerialNumber = “AAA” AND (Device.DeviceInfo.SoftwareVersion <> “BBB” OR Device.DeviceInfo.SoftwareVersion IS NULL)
And it works, but if the SQL is wrong, etc typo error and save it, the genieACS UI breaks cant open the presets any more.
Over the UI if you try to edit it with wrong SQL syntax show “Precondition must be valid expression”
is there a mechanism to validate this syntax over the API?

  1. On documentation about the Preset Configurations
    [configurations] =>
    Array (
    [0] => Array (
    [type] => provision
    [name] => TEEST
    )
    [1] => Array (
    [type] => add_tag
    [name] => TEEST
    [tag] => NEW TAG
    )
    )
    if we send the data like this, it save it but in new GenieACS UI says: “This UI only supports presets with a single ‘provision’ configuration. If this preset was originally created from the old UI (genieacs-gui), you must edit it there.”
    So maybe you mast change something on API documentation for that.