Skip to Main Content
AVEVA Product Feedback


Status No status
Categories Notifications
Created by Guest
Created on Aug 20, 2022

Web Service Configuration - Dynamic "Path" for the JSON Body

Allow free-form JSON construction. Maybe not replace the simple JSON guide that is the only entry form now, but free-form would allow the kind of flexibility that would empower the user. This would allow a single template to be used, rather than the workaround to manually override the template for every individual sensor configured, resulting in hundreds of template copies in which only the "Path" field is edited
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    How would you enter the free form JSON? By hand?
  • Guest
    Reply
    |
    Aug 20, 2022
    Having seen how the current configuration seems to work, it would look like it could be a rewrite. If a JSON format text file were used as the base, then any text editor could be used. Possibly like the UFL interface where the ICU reads in an INI file, then provides guidance as how to proceed. This could be a utility tool that reads in a JSON text, allows further editing, then imports into AF, or just leaves the file to be read by the channel when it starts up. Maybe similar to StringBuilder in the current client? That allows substitution parameters wherever.