Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Dev. Studio vs Report Assistant

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Dev. Studio vs Report Assistant
 Login/Join
 
<Dave>
posted
I have a client with some very reasonable requests as far as reporting requirements, web access, etc. The one unreasonable request is that this client insists that Report Assistant be the development and maintenance tool used. Developer Studio is "not an option". I have successfully met all reporting requirements with Studio, and deployed same. Now client wants the code re-done in RA so it can be maintained there. I have a few issues: 1.) Limited functionality (won't support multi-column joins, seems to treat all columns as Detail or Sum but can't mix the two, etc.)
2.) Bugs. Frequently when I develop and test a report with RA, then attempt to re-open it for mods, the window opens up with only the original master file. All report information, joins, etc. are gone. I know better than to text-edit these fex files, so that's not it.

I am ready to tell the client that Report Assistant is not a suitable tool for building and maintaining a production application. Fine for quick reports and throw-aways, but not for enterprise applications. Am I all wet? Anybody care to defend Report Assistant as an enterprise-wide development tool?
 
Report This Post
Jeffrey Friedman
Member
posted Hide Post
Dave,

I checked with the Product Manager for the HTML Report Assistant before replying to you and got the answer that I was going to send on my own. And that is:

The HTML RA should not be used as the enterprise report development tool and should not be marketed that way.
Dev studio is the tool to use. And yes, the RA does not have all the functionality of the painter, it wasn't meant to.

I know that this is probably not what you wanted to hear, but it is reality. We cannot give unrealistic expectations to our customers. By selling them an analytical reporting tool as a developers tool, we would be doing just that.
 
Posts: 3 | Location: Corporate | Registered: May 01, 2003Report This Post
<Laura Drezek>
posted
Dave,
The HTML RA is not as powerful as the Dev Studio Painter. That is true, and it is not meant to be. Dev Studio is the positioned app dev tool. There are limitations with the HTML RA and yes you may stumble across some bugs. If you do find bugs please open up a hottrack.

So yes, the HTML RA is not meant to be the main app dev tool. Developers Studio is much more powerful.
-Laura Drezek
 
Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Dev. Studio vs Report Assistant

Copyright © 1996-2020 Information Builders