Allow individual customization for FTP mailboxes

Thank you for your response, it was helpful in understanding your use cases.

IBM has evaluated the request and has determined that it cannot be implemented at this time or does not align with our current strategy or roadmap. However, there are ways to implement this with current functionality. There are a few options:

• Create a custom user exit that calls an XAPI from your Java code to change the message attributes, which would include extractability. This would require some Java skills or engage services to assist in creating this custom user exit

  • https://www.ibm.com/docs/en/b2b-integrator/6.2.0?topic=work-configuring-mailbox-user-exits

  • see the install folder for examples on user exits

• Use a BP to dynamically change a message's extraction attributes based on the condition like file name/size/type. BPs would execute after the file is uploaded as a post-processing step that would be slower than a custom user exit

Thank you for taking the time to provide your ideas to IBM. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.

Hello Mark,

Thank you. This request was created after submitting case TS014433539. What I could find is that all of our mailboxes are controlled under the same properties. We had a client request that when they submit a file, that the extract remain “Always Extractable” or extract count = yes.

• Are you asking for the capability to flag files based on some condition like file name/size or type? Yes, when a client submits a file and it meets a criteria, we would want to update the flag to “Always Extractable/Yes” or perhaps a new flag “Extractable Until = yyyy/mm/dd.”

• These flags could be a restriction such as setting an extraction rule or throw an error? The flags themselves would be the enhancement request.

• Are you suggesting a feature that allows you to control the extraction count based on some properties of a file? Yes.

• Is this a set of rules that prevent file upload? Not necessarily. We want to have more capability of controlling each mailbox’s messages individually.

• Are these flags just an indicator to highlight these files? I am specifically referring to the extract count flag.

I apologize for the delay in my response. I hope to be more poignant in future responses. Thank you for your time!

-Kyle

Thank you for taking the time to provide your ideas to IBM. I truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations and ideas.

I need a little more information to understand your idea.

• Are you asking for the capability to flag files based on some condition like file name/size or type?

• These flags could be a restriction such as setting an extraction rule or throw an error?

• Are you suggesting a feature that allows you to control the extraction count based on some properties of a file?

• Is this a set of rules that prevent file upload?

• Are these flags just an indicator to highlight these files?

It would be helpful if you could provide some concrete examples/use cases so we can understand the request better. Today in SFG, the routing rules can specify some of these restrictions based on things like file name, which might be worth exploring but cannot prevent uploads based on size, etc. The product already has a custom user exit on mailboxes, which might be another alternative to look into.