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  Performance Management Framework (PMF)    PMF Developer Series – Forward Looking with Dashboard Gadget Parameters

Read-Only Read-Only Topic
Go
Search
Notify
Tools
PMF Developer Series – Forward Looking with Dashboard Gadget Parameters
 Login/Join
 
Gold member
posted
In the last post I discussed the PMF Gadget Parameters and how you can access these values inside custom gadgets. In the future the handling of gadget parameters will be fundamentally changing. Here I’ll give you a sneak peak on some of our plans to improve this process.

We are changing the internals to handle dimensional parameters with a generic nomenclature. This means that a previous parameter of LOCATION would be called DIM02 instead. Similarly, looking at dimensional level parameters which might have been LOCATION_LEVEL01_VALUE=’EAST’ will now need to be accessed by doing DIM02_LEVEL01_VALUE=’EAST’. Those with database design backgrounds can think of this naming as a surrogate number to the proper dimension name.

You might be wondering – what are they thinking? Well, this actually is very powerful as it allows much more flexibility to allow dimension re-naming and not to mention better handling with other languages (such as with UTF8).

The good news is that this should affect very little if any of your custom gadgets. A specialized include will be provided that will convert back and forth the naming conventions that will allow older reports to function as is. At the very least you may need to add this one call to the beginning of your custom report. One noticeable difference will be when doing a view source of reports that it will show the surrogate number instead of the dimension name as it is currently done.

This is a heads up to some of the internal changes we have coming down the pipe. These changes will be discussed in more depth in the future.

Best regards,
Michael Paul
Senior Software Developer
WebFOCUS Performance Management
 
Posts: 57 | Registered: December 03, 2007Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  Performance Management Framework (PMF)    PMF Developer Series – Forward Looking with Dashboard Gadget Parameters

Copyright © 1996-2020 Information Builders