Best practices for objects with header/lines structure

Follow the recommendations below for objects with header/lines structure with a daily business flow usage:

• Use classic code rather than hybrid mode for documents with a potentially big number of lines to avoid a too long response time. Thus, the class will not be used through this X3 function.
• Write the control code in small separated chunks called by classic code so they can be transformed easily and reimplemented later in ETNA development.
• Create a class and a representation for read-only mode. This will help to transition later in ETNA and allow the benefit of potential indexation for Elasticsearch.