I would like to propose, and volunteer to participate in the development of, a general purpose Integration API for Tryton.
I’ve spent a few years deconstructing a proprietary any-to-any transformation application and have some ideas how to implement it in python and integrate it in Tryton.
At an overview level - I envision an interface that can accept any transaction-type/standard (X12, EDIFACT, UNCEFACT, UBL, cXML, customized XML, JSON, Flatfile Delimited and Fixed) for which a schema has been created and registered with the parser.
My experience has shown that when a generic document is able to be matched against such a schema, then it can be parsed and the data extracted or transformed into other formats or loaded directly into models/tables.
To perform a transformation, these key things are needed
What standard/document-type is it? (X12, EDIFACT, UBL)
That allows the document-type (ORDERS, INVOIC), from & to parties and version to be used to match the specific document instance to a specific transformation class.
I’d like to see a HTTP listener as a generic document startpoint and folder & sFTP pickups also available for getting these files into the parsing engine.
This is a rough draft and only the skeleton of a description - much more to follow from a specification standpoint - but hopefully this is a good starting point for community discussion.
I’ve used the timesheet module for a sample of basic user/key Bearer authorization and am beginning the process of creating the transformation_profile model & views for holding the schema/from/to/version requirements mentioned above. I’ll update the community as I work through each of my POC milestones.