GraphQL - Wildcard * sometimes not working for Recources Label and Identification

• Related Articles

• GraphQL Interface reports "Unexpected end of JSON input"

  Summary The GraphQL Interface sometimes terminates data queries with an error. This has been fixed. Description The GraphQL Interface sometimes terminates data queries prematurely with the error message "Unexpected end of JSON input". The error seems ...

• New keyword in ALARM.FRM and BTB.FRM file for "Resource label"

  Summary In formatting files ALARM.FRM and BTB.FRM the possibility to use keyword for "Resource label" is missing. Thus this variable property cannot be printed the Alarm and Chronologic Event List. The Resource label property is used in projects ...

• GraphQL interface editor only works with internet access

  Description The GraphQL Interface Editor requires an active internet connection. If this is not available or the file has been removed from the CDN, the editor will not work. This has been changed. The GraphQL Interface Editor no longer requires an ...

• GraphQL - Filters only search in original strings, not on translations

  Description For GraphQL statements, the language can be set as a parameter. Return values are translated accordingly. However, filters are applied only to the original expression, translations are ignored. Only the texts in the source language are ...

• XML export and (re)import of command groups removes wildcard-based interlocking variable entries.

  Summary In Command Processing for all variables – response, command and interlocking – the wildcard '*' is allowed (and recommended). During XML-export and (re)import the entries about interlocking variables are removed if had the wildcard. ...