You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In X12 versions 003060 and earlier, segments can be declared mandatory, optional, or floating. Floating segments can appear anywhere in the transaction set between the ST and SE segments.
This is not supported in stupidedi. There no "floating" SegmentReq, and there is no obvious way to add support for this. It's not clear what an Instruction would look like for this situation. Also, because floating segments can occur anywhere, the find method would need to do a linear search through the segments after the current position, which it doesn't currently do.
I don't have any documentation on floating segments, nor any idea of how prevalent they are in practice. This issue is just to document the lack of support in case someone is looking for it, and to gauge if there is interest in supporting it.
The text was updated successfully, but these errors were encountered:
I found some documentation that indicated NTE segments usually have this designation. I guess the intention was to let people insert annotations (NTE is note) anywhere in the X12 document? I don't have the URL handy anymore, but if I find it again I'll post it.
In X12 versions 003060 and earlier, segments can be declared mandatory, optional, or floating. Floating segments can appear anywhere in the transaction set between the
ST
andSE
segments.This is not supported in stupidedi. There no "floating"
SegmentReq
, and there is no obvious way to add support for this. It's not clear what anInstruction
would look like for this situation. Also, because floating segments can occur anywhere, thefind
method would need to do a linear search through the segments after the current position, which it doesn't currently do.I don't have any documentation on floating segments, nor any idea of how prevalent they are in practice. This issue is just to document the lack of support in case someone is looking for it, and to gauge if there is interest in supporting it.
The text was updated successfully, but these errors were encountered: