Provide your input on the next-generation Annotation Modeler 

Developers that create SAP Fiori elements apps know that using annotations makes the standard SAP Fiori elements page types look and behave like the apps your end users request. SAP Fiori tools includes an XML language server protocol that provides code completion when editing XML annotations. We are exploring what the next generation Annotation Modeler should look like.  

• Is a code editor sufficient for annotation modeling?  
• Do we need a graphical editor too?  
• When would you need both?  

These are some of the questions we are exploring by means of a survey and some individual phone interviews.  

If you have created SAP Fiori elements apps and used the Annotation Modeler in Web IDE, we invite you to take our survey.

If you have used the LSP functionality in SAP Fiori tools, we also welcome your feedback through the survey.  

The latest tools for annotation modeling are part of the XML LSP in SAP Fiori tools. SAP Fiori tools is a set of extensions that runs in SAP Business Application Studio or Visual Studio Code. The XML annotation language server accelerates how you define annotations in the xml code editor, reducing the effort and improving consistency in your code. It provides suggestions for which annotations and properties can be used, based on the context, and checks your annotation files against OData vocabularies and metadata to identify any syntax errors. 

Unlike the Annotation Modeler in the Web IDE, the current annotation tools are code-based only and do not have a graphical editor. For our next generation annotation modeler, we are exploring what capabilities it should have.  

While the survey will provide quantitative feedback, we also would like to have some in-depth conversations to better understand how you use the annotation modeler and what you would like to see in the next generation.  

Please email me using the standard firstname.lastname at sap.com format. 

You can also include your feedback about the annotation modeler in the comments below.  

For the SAP UX product team, Mariana Naboka.