We are using Webfocus 8.2.04Before we were using the file-system, making it also possible to search through my fexes using WIndows Explorer / Ulta Edit etc.Now everything is stored in the repository.The only thing I know about the repository is that it is just some kind of database. Now, we make fexes, reports etc etc. Also our users make reports using InfoAssist. Is al this stored in the repository??

If so, suppose we have developed a business view. Based on which users make reports.Now we want to change something in the business view. How can we easily check which reports, made by users, are affected?How can we do a search in the repository?

RegardsRon

This message has been edited. Last edited by: FP Mod Chuck, February 04, 2019 10:02 AM

It still confuses me. In AppStudio you have Domains and Applications folder. In the new Homepage Designer I also see Domains and Content.What exactly is the difference between the three?Domain contains the content, such as dashboards and infoapps, created for the end-user?Content contains the individual widgets/fexes created by for instance InfoAssist?But what exactly contains the Application folder in AppStudio then? I there also a Content folder in AppStudio?

RegardsRon

This message has been edited. Last edited by: Ronibi, February 01, 2019 01:20 PM

App Studio is a developer's IDE. Consequently, it exposes much more than what you see on the WebFOCUS homepage. As of now, all your assets with the exception of Metadata should be in the Domain which maintains an RDBMS repository. All reports/charts/portals et cetera are created and maintained in the Domains. Metadata is maintained in the Apps folder of your Reporting Server. In most situations, App Studio is configured to point to the same Domains as your WebFOCUS portal. Content created by either InfoAssist or App Studio can reside and be used in the Domain. In some cases, you may need to maintain reports on the Reporting Server. Most of those are utility jobs that aren't meant to be used on the WebFOCUS portals. Almost all objects your Portal users interact with should reside in a Domain where you can provision access based on roles and/or group membership.