Sidebar
en:prozessdefinition:repositorien:analysator:typen
Table of Contents
Analysator Typen
eBiss.Api.ITypedEntityAnalyzer
eBiss.ClassLib.Analyzers.AnsiX12EntityAnalyzer
eBiss.ClassLib.Analyzers.AnsiX12EntityAnalyzerEx
eBiss.ClassLib.Analyzers.ediBoxInhouseEntityAnalyzer
eBiss.ClassLib.Analyzers.EdifactEntityAnalyzer
eBiss.ClassLib.Analyzers.FlatFileAnalyzer
eBiss.ClassLib.Analyzers.IDataBoundEntityAnalyzer
eBiss.ClassLib.Analyzers.InternalXmlEntityAnalyzer
eBiss.ClassLib.Analyzers.JsonTypeAnalyzer
eBiss.ClassLib.Analyzers.RepositoryTypeAnalyzer
eBiss.ClassLib.Analyzers.SoapXMLTypeAnalyzer
eBiss.ClassLib.Analyzers.VDAFlatFileAnalyzer
eBiss.ClassLib.Analyzers.XMLTypeAnalyzer
eBiss.ClassLib.Analyzers.XMLTypeAnalyzerEx
Compared to the regular XMLTypeAnalyzer, XMLTypeAnalyzerEx allows you to mark and recognize elements in the XML hierarchy as documents. This requires that an element within the XML structure is marked as an envelope (interchange) of the document using the MapInterchangeRecord attribute. Afterwards, an element that is located as deep as you like in the XML structure can be marked as a document using MapTrigger attribute. All higher-level elements of the trigger up to the root of the structure must then be provided with a MapTriggerParent attribute to mark the path to the trigger.
sample structure:
<root>
<header>[MapInterchangeRecord] (Hinzugefügt in der Definition des Map-Objekts)
...
</header>
<body> [MapTriggerParent]
...
<documentparent> [MapTriggerParent]
<document> [MapTrigger]
...
</document>
</documentparent>
</body>
</root>
eBiss.Sap.SapIDocAnalyzer
Evaluates the segment EDI_DC40 and enables, for example, partner recognition based on the information in a Custom Interchange Communication Address.
The following data elements are evaluated in the EDI_DC40 segment by the SapIDocAnalyzer.
eBiss.Tradacoms.TradacomsEntityAnalyzer
en/prozessdefinition/repositorien/analysator/typen.txt · Last modified: 2024/02/20 08:15 by 127.0.0.1