As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
We have an old WF 7.6.11 environment that we are migrating from to 8.1.05. My project lead has made known to me that as of like 2 weeks ago email attachments for various distributions aren't being sent if they are big. I wasn't given an actual size for these attachments as of yet. Where would an admin of 7.6.x go to troubleshoot such an issue? Where does the zip encoding get set for attachments, and where can one adjust the size of allowed attachments if at all?
Any help is much appreciated.
Thanks in advance!This message has been edited. Last edited by: CoolGuy,
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
Hope all is well. ReportCaster has a configuration setting to conditionally zip email attachments when the attachment exceeds a certain size. This setting is in releases including 7.6.x. In 8.1.05, it is documented on page 105 of the ReportCaster manual.
Please feel free to open up a case if this isn't adequate enough and reference the answer above.
We figured the issue out. We are currently migrating things to Office 365 and it ended up being a domain constraint issue. Thanks for your insights and suggestions though!
Until next time!
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015