User Story:
I have broadcast engineers with no coding experience, They need to be able to define new parameters for use in a protocol according to a limited set of preconfigured variables in an existing protocol without using DIS or an XML editor.
I want to build a protocol that could generate additional standalone protocol parameter xml code sections to be included in itself, create a new protocol version with the additional parameters, change the version number of the protocol xml code, import the modified protocol.xml into dataminer, reassign the protocol version of the element to the new version, and restart the element so that it begins to use the new version of the protocol code.
Basically, the goal is to have a mini DIS parameter generation capability built into a protocol, and an automated means of putting that new code into production.
Is there any conceivable method by which a protocol could be designed to edit its own protocol xml code and update its element with that new version?
Is the .dll that facilitates the "Publish" feature of DIS available to be used in a QA of a protocol?
Is the .dll that facilitates the Protocols and Features "Import" feature of cube available to be used in a QA of a protocol?
Hi Michael,
It should be possible to automatically generate parameter xml and insert it in an existing protocol xml. However, you'll then just end up with empty parameters and I fail to understand how the expected value would then end up in that parameter.
Let's have a sync to better understand the exact use case with a practical example.