Skip to Content
author's profile photo Rahul Thunoli
0
Rahul Thunoli

RNIF Angled brackets in the Content Id in the attachment

Posted on Apr 29, 2011 at 05:19 PM 16 Views

Hello All,

I'm working on an RNIF interface with a PIDX message and an attachment . Everything is working fine until this new requirement came up . The partner that we are communicating with needs the content-id of the attachment to be enclosed in angled brackets <>. I know that this issue has been resolved in PI 7.1 EHP1 , but we are on PI 7.0 .

Please let me know if there is a support pack in 7.0 for this and if so which one . Thanks.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Mark Smyth
    Mark Smyth
    Posted on May 04, 2011 at 03:53 PM
    0

    Hello

    Check the SAP note #1554216 RNIF Adapter doesn't use angled brackets(<>) for Content-ID.

    Regards

    Mark

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Mark Smyth
    Mark Smyth
    Posted on May 04, 2011 at 04:42 PM
    0

    Hi

    Yes, this is a module parameter for the RNIFModuleListener module.

    Regards

    Mark

    Add a comment
    10|10000 characters needed characters exceeded

    • Rahul Thunoli
      May 04, 2011 at 04:57 PM

      That note talks about Support packs and patches that supports this attribute . In the listing there is SP12 for AF and AFC . So we were under the impression that this attribute is available on SP12 and above .

      Right now we are on PI 7.0 SP 14 stack and i have set the attribute to 'true' for the RNIFLISTENER module , but the content-id is not coming enclosed in <> . So does that mean that the Add-Angled-Brackets-To-Content-ID is not available in SP14 which is above sp12 .

      Thanks again for your reply .

  • author's profile photo Mark Smyth
    Mark Smyth
    Posted on May 04, 2011 at 05:09 PM
    0

    Hi

    The parameter is not available for SP14. Note #1554216 is a relatively new note. SAP will generally provide fixes for the previous 3 SP releases (e.g. SP24, SP23 and SP22 in this case).

    It looks like this specific fix was provided for a customer on SP12. I guess you will need to request they do the same for your SP14 release (if upgrading is not an option for you).

    Regards

    Mark

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.