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 firstname.lastname@example.org for further assistance. Reference the community FAQ to learn more about the community.
Doing custom development in PMF and utilizing Gadget Preferences or Broadcast functionality you will need to learn the background on gadget parameters. In the past we have recommended that users leverage the GADG_DIM_PARMS_MULT include. What this function does is split up the parameter you want into a usable split level format.
Eg. The Gadget Parameters of the below is setup in the gadget preferences: &LOCATION=EAST~Bos
The include GADG_DIM_PARMS_MULT converts this into the useable format of: &LOCATION_LEVEL01_VALUE=’EAST’ &LOCATION_LEVEL02_VALUE=’Bos’
What many people still may not know is that we do this now for you within the gadget Today Page layer. All dimensional parameters passed from the Today page have already been split up for you so this include is not needed in most situations. You can now just use the split amper variables such as &LOCATION_LEVEL01_VALUE within your custom pmf gadget. This is how in WF77 InfoAssist interfaces with PMF so well.
It would be worth noting a difference in handling inside PMF with InfoAssist and other gadget types. For InfoAssist, PMF passes a _FOC_NULL for every dimensional level where a value is not explicitly passed. This was done so these variables do not need to be –DEFAULTH in the final reports in case they are referenced in the report but not explicitly set and passed. We did not implement this _FOC_NULL for other gadget types because of the possibility whereas there is a 16 dimension with 16 levels which could potentially exceed the 2K limit imposed by some browsers. If anyone feels like this limit would not be a problem for them and they would like to know how to turn this on for other gadget types, I’d be happy to let you know how.
Note: Those of you who are unsure what _FOC_NULL is –> It is new in WF77 and is used as a replacement for the FOC_NONE used in prior WF releases. Note: The include of GADG_DIM_PARMS_MULT is still a viable option with pertinent value especially regarding Operational report drill downs. This can calculate the drill down values from the passed report and including the proper time information and split that up into a usable format.
As always, if you have any feedback please let me know.
Best regards, Michael Paul Senior Software Developer WebFOCUS Performance Management