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.
So, I've built a portal with several pages. A few of these pages display AHTML-based reports inside various iframes sitting in parent div containers. (used the RDF Templates add-on templating) When we go to run some of them in mobile browsers (Safari, Chrome), the Active reports will only partially render completely. We get huge widths for each column of data (usually its just populating the BY fields), but then it never finishes rendering the rest of the report. I've had it happen to me on my laptop as well before from time to time. In order for us to get it to render completely, we have to click a column title to get the drop down menu and select View Full Screen. Then it finally renders the whole report like it should have originally.
Has anyone else had these types of issues with their AHTML reports before, and have figured out why it fails to render completely??
Any guidance, insights, suggestions in relation to this issue is greatly 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
- Modified the RDFTemplates CSS and Js to add an AHTML button option for the panel buttons feature. This allows the user to open the report in a new window as AHTML output without the issues. - Reports showcased within templates in use in our portal will be set to HTML output instead while utilizing both the tablesaw.js and dataTables.js libraries to add features, make responsive, etc. It took me around 2 days to find a Js library that would work with both IBI generated HTML, and the tablesaw.js library. DataTables.js is the best! Our reports now have sorting, pagination, responsive column hiding/showing, search, # records/page shown drop-downs, etc.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015