Hi, Steven!
Thanks for the reply!
I figured it out!
You were right about the encryption. The message length is the size of a train, and sometimes at least ten files need to be transferred.
So, we decided to transfer a web URL.
I added the following code to the xsl file, and everything started transferring.
<ns0:DOCLINKSs>
<xsl:for-each select="max:DOCLINKS">
<ns0:DOCLINKS>
<ns0:WEBURL>
<xsl:value-of select="max:WEBURL"/>
</ns0:WEBURL>
<ns0:description>
<xsl:value-of select="max:DESCRIPTION"/>
</ns0:description>
</ns0:DOCLINKS>
</xsl:for-each>
</ns0:DOCLINKSs>
------------------------------
Sergey Melnikov
RusNet
------------------------------
Original Message:
Sent: 01-07-2026 10:19
From: Steven Shull
Subject: Export attached doclinks documents to an external system.
I apologize because this is an older post I missed somehow. Hopefully you figured it out but in case you haven't or in case someone else stumbles on this post, I wanted to add a response.
Based on the formatting of the message, it looks like you have a XSL file (defined in the XSL Map section of the publish channel) transforming the message from the Maximo format into the format you need for your external system. These XSL files control the entire processing of the message and if not configured properly, will ignore additional content in the message, so you need to review the XSLT to ensure it is bringing in this data.
In addition, specific to certain versions of 7.6.1.3 (up until IFIX 022 in July 2024), there is a bug if your attachments are stored in a S3 bucket where documentdata will not be populated. IJ51407: DOCLINKS.DOCUMENTDATA IS EMPTY WHEN THE ATTACHMENT IS IN AN S3 BUCKET
------------------------------
Steven Shull
Naviam
Original Message:
Sent: 11-27-2025 07:48
From: Sergey Melnikov
Subject: Export attached doclinks documents to an external system.
Hello, experts.
I need to send attached DOCLINKS documents along with a PR procurement order.
I found the X1CPR object structure, added the original DOCLINKS object, and enabled the non-persistent DOCUMENTDATA attribute. I regenerated the object structure XML, and also regenerated the publication channel XML.
In these XML files, I see (<max:DOCUMENTDATA changed="true">YW5pbW9z</max:DOCUMENTDATA>)
But the DOCUMENTDATA field doesn't appear in the outgoing XML message. Please help me: what did I do wrong?
Should I add documentdata field to the sync_pr_mx21c.xsl structure of the publish channel?
#Administration
#Architecture
#EverythingMaximo
#Integrations
------------------------------
Sergey Melnikov
RusNet
------------------------------