The ITX mapper needs to be capable of supporting Sterling B2Bi Envelope/Control Number management is a similar manner to how it support ITXA in order to fully leverage ITX maps within the Sterling B2Bi product

This ask effectively is to expand the Sterling Data Harness called within ITX maps to support more than just delimited from the Sterling Envelope but allow for a get & increment control number(s) as well as all sender/receiver/qualifer/version etc calls from the Sterling Envelope in the same manner as the Sterling Envelope process do behind the scenes today. This way we can run an ITX map with full envelope generation within the ITX Map service. Why? Well this actually seems to be the way ITX is designed to work only with ITXA as the envelope manager but if we already have Sterling doing this we don't really need or want to run two envelope management systems especially if we are going to have Sterling and ITX maps being called for a single partner facing output from parallel internal job runs. Additionally, this would allow us to actually use the ITX Map service within the Sterling BP flow with multiple file inputs and outputs, fully able to leverage ITX's mapping capabilities as calling an ITX map within a Sterling Map call restrict the file input and output to one same as a Sterling Map. This 'IDEA' acompanies another that deals with pain point with using JSON Data with an ITX map within the Sterling 'canned processes' of Document Extraction Service and X12/EDIFACT Envelope Service(s) that are not designed and can not handle JSON data having a single root tag in the same way that XML has and is supported.