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.
When a user goes into InfoAssist, for some reason they can see Applications even though we're setting the list of applications in the security properties for each content folder (similar to how we did for Domains in 7.X).
8.1.0.5 seems to be picking up ALL content folders using a "*" or fuzzy search.
Example: We only grant access to application "test" but users will see all apps in InfoAssist with related names such as "test_a" or "test1" or "testB".
Has anyone seen this behavior before, and knows whether this is some sort of configuration that we can change/disable either in SC or at the Reporting Server level?
We need to restrict what our users can view in IA, but we cannot rename all of our applications since that would be a large effort.
Thanks in advance.This message has been edited. Last edited by: <Emily McAllister>,
What they are allowed to create from depends on the role permissions of the security group they are tied to. You can edit role permissions to only allow those users to work from reporting objects; or you can edit them to allow them to work from master file descriptions. When doing so, they will only be able to see the master file descriptions that are in the app path for the domain security group they belong to.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
I'm working with bldkfs98 to troubleshoot this and I'm hoping a little more detail might spark an idea from someone more knowledgable...
In our WF instance, each Content Folder is associated with one application via the Server Properties tab (right-click on the Content Folder, select Properties and then Server Properties).
The expectation is that when report writers open InfoAssist to create a new report they will only see the masters from the one application listed on the Server Properties tab. In our production system (WF 7.7.03), as well as an earlier test environment (WF 8.0.10), that is exactly what happens.
However, in WF 8.1.05, when report writers open InfoAssist they can see the masterfiles from all applications that begin with the same name as the application listed under Server Properties.
Applications listed under Applications visible WF Environment Domain/Content Folder Server Properties to InfoAssist 8.1.05 ABC test test, test_a, test1, testB 8.0.10 ABC test test 7.7.03 ABC test test
This causes a huge issue for us because we group application names by subject area (e.g. fin_payable, fin_receivable) and some applications contain sensitive information that should only be accessed by specific groups.
We are trying to determine if this new behavior is controlled by a configuration item that we can change or if it is a bug with 8.1.05.
Note - even though I referred to a report writer the behavior is consistent across all user types (Developer, User, Admin).
CoolGuy - We have main 3 roles - User, Developer and Group Admin. We do not use Reporting Objects and all roles have the ability to create reports directly from masters. We control what masters they can see via the applications that are associated with each Content Folder.
BabakNYC - We set up Access Control rules on the Reporting Server but that did not affect what applications were visible via InfoAssist. We then tried setting rules on the Application folders that permitted only certain groups to list the contents of each Application but that had no affect on the behavior either.
Posts: 2 | Location: Storrs, CT, USA | Registered: May 16, 2014
This is a known issue which has been fixed in an upcoming maintenance release. I will PM you with details on how to obtain the fix for your environment.
Emily McAllister Focal Point ModeratorThis message has been edited. Last edited by: <Emily McAllister>,