We love hearing from our users. Tell us what you want to see next and upvote ideas from the community. * Bugs and troubleshooting should as usual go through InterSystems support.
Automatic XML Formatting of XData in DTL, BPL and Rulesets
The basic idea is that when a DTL, BPL or ruleset is edited on the SMP, that is formats the XML in the XData block.
With large DTL, Rulesets and BPL, it is sometimes easier to open the class, collapse some sections of the XML and check the flow. Proper formatting will assist in this.
ADMIN RESPONSE
Jun 3, 2024
Thank you for submitting the idea. The status has been changed to "Needs review".
When a DTL, Ruleset or BPL is saved, the XML lines are all at the same level. We have DTLs that are 2000 lines long and it is easier to edit as XML than using the DTL editor. If the XML was formatted, it will be easier. We reformet these, but if the DTL editor is used at any point, it changes all the formatting again. The same applies to rulesets and BPL.
Example of requirement: Currently the XML looks like this after saving on the DTL editor.
Stefan, thank you so much for your idea. Could you please answer the questions from Product Manager to clarify this idea:
Visual Studio supports XML formatting, is that still insufficient? If so, how?
The interoperability editors are currently being reworked and the goal is to remove the need to drop back into the code for certain activities (like moving actions around)
Stefan, thanks for the clarification. I returned the status as "Needs review". I hope the product managers will provide feedback on your idea soon.
When a DTL, Ruleset or BPL is saved, the XML lines are all at the same level.
We have DTLs that are 2000 lines long and it is easier to edit as XML than using the DTL editor. If the XML was formatted, it will be easier. We reformet these, but if the DTL editor is used at any point, it changes all the formatting again. The same applies to rulesets and BPL.
Example of requirement:
Currently the XML looks like this after saving on the DTL editor.
What I would like it to look like:
Stefan, thank you so much for your idea. Could you please answer the questions from Product Manager to clarify this idea:
Visual Studio supports XML formatting, is that still insufficient? If so, how?
The interoperability editors are currently being reworked and the goal is to remove the need to drop back into the code for certain activities (like moving actions around)