Please weigh in, folks!
I always thought that it wasn't really recommended to use PIW files. If that goes pop then so does all of the embedded displays.
Well, Rhys, when PI ProcessBook was first released, PIW files were the only option and there certainly do appear to be customers that continue to use them. Of course, that was before you were born. :-)
I'm trying to assess how many of these customers are still are out there.
Although I've indicated no on the poll I will say that we do use PIW files; I wasn't aware that they weren't recommended (learn something new everyday). The reason for no is that we create a logical directory structure that is "imported" into Coresight which works well. However, we still use PIW files as it is an easy way of distributing multiple displays. Plus I have a small app that takes a PIW file, pdf's and emails it for those network challenged people.
Thanks for the information, Michael! We haven't exactly heard a hue and cry to support this, which is why I'm asking. I believe a number of customers use the PIW format for easy portability (as you describe), but we want the use of these files and their displays in PI Coresight to be as friction-less as possible.
I wouldn't say that PIWs aren't recommended. I would say that we've heard some issues with having multiple people edit them.
Like Rhys mentioned (hope I used the correct tagging here), I also believed that PIW is not really the preferred way, so never used it. Instead I have always preferred to build a nice looking Overview screen.
So if its a Petrochemica/Refining Plant for eg, all the important units like Atmospheric Distillation, Cracking Complex, Treating units and other detailed units etc are displayed on the overview screen with relevant flows between them, and the labels are formatted as standard blue hyperlinks. Then, buttons are placed on top of those labels and the buttons are made invisible (Visible property to "False"). This creates a " Home Page" to which the user can navigate if he wants to navigate to some other screen.
This works normally in coresight so I have preferred this way rather than use a PIW for listing out the screens. (They already have the list of displays in a shared folder normally).
Thanks for your input, Nikhil! This is helpful information.
In the older versions of Processbook is it possible to modify the buttons visibility property? My client is using ProcessBook Version 3.2.3 from 2010. Right clicking on the button does not give me the ability to open the property window so I can't access the visibility property. The only way to do this would be through VBA code which won't work when ported to coresight. Am I missing anything here? I'd prefer to make an overview screen similar to what you have described.
In my experience, few of our clients use PIW files any more. For those that do, it is easy enough to dump them into PDIs and then import those into CoreSight.
Thanks for your input, Steve. So, would you say that the structure in the Table of Contents isn't needed?
It isn't needed. Typically we build a menu display like Nikhil Kaul mentioned above and have "menu" buttons on other displays to come back to the main menu display. All of this works in CoreSight as is.
This is exactly the reason, why I officially signed up as member and not just as a viewer.
In general, most of our screens are processbook based and we have created an AF structure to move into Coresight, but recently we have made an acquisition which came with a very usefull *.piw file.
So my question is, how can you make these visible in Coresight?
Or can someone show me a post or link which explains these files(.piw), as I wasn't aware of these exisited.
Think of a PIW file like a zip file.
When you open the PIW file there is a kind of folder structure with embedded displays files. These embedded display files can still reference AF, PI etc but they are contained with the PIW and not as individual display files in your machine's file system.
Here is a link for more info: PI ProcessBook
Retrieving data ...