webMethods

 View Only
Expand all | Collapse all

In wM Runtime pipeline, DocumentList becomes Document even before loop over a segment

  • 1.  In wM Runtime pipeline, DocumentList becomes Document even before loop over a segment

    Posted Wed February 15, 2023 10:53 PM

    What product/components do you use and which version/fix level are you on?

    webMethods 10.7

    Is your question related to the free trial, or to a production (customer) instance?

    Production(Customer) Instance

    What are you trying to achieve? Please describe it in detail.

    Hi All,

    A segment has been created as DocumentList in IS DocType but when I debug the flow service used that IS DT,
    I could see the segment is coming as Document in the 1st step itself & even before loop over the segment

    imagehttps://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/01ded29a4bf5c62d22e8bd83617efdbf69a16f6c.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/01ded29a4bf5c62d22e8bd83617efdbf69a16f6c.png 2x" data-dominant-color="EDE8E4">
    image742×246 64.6 KB

    As the segment coming as DocumentList, I cannot loop over it and it will skip the loop step and proceed to execute following flow steps.

    What could have caused this issue ?
    Any idea on this?


    #Flow-and-Java-services
    #webMethods
    #edi
    #B2B-Integration
    #Integration-Server-and-ESB


  • 2.  RE: In wM Runtime pipeline, DocumentList becomes Document even before loop over a segment

    Posted Wed February 15, 2023 11:24 PM

    Please check step by step:

    1. check documentTypeName
      image

    2. check root tag of this documentType and your xmldata is the same one
      image


    #webMethods
    #Flow-and-Java-services
    #B2B-Integration
    #edi
    #Integration-Server-and-ESB


  • 3.  RE: In wM Runtime pipeline, DocumentList becomes Document even before loop over a segment

    Posted Thu February 16, 2023 12:16 AM

    kindly validate your document structure referenced to your service to me it looks like a document issue

    • Check the IDOC version which you referenced

    • Check if any of the step where you are converting and generating this IDOC structure is having issue


    #Integration-Server-and-ESB
    #webMethods
    #edi
    #B2B-Integration
    #Flow-and-Java-services