When customizing symbol scale range, only top and bottom values can be specified. It would also be useful to set increment or step value to avoid unnecessary clutter on a display.

When ProcessBook files are viewed through PI Vision it should be able to render user created bitmap symbols.

Using the AF limits, show the 'bands' or limits for the PI value. You can put a multi state which will change the colour of pointer, however you cannot tell by how much it is within the limits. See attached for a mocked up symbol built in PI Vision.

Have the ability to hide PI Vision Bar Chart scale.

Have the possibility to change Bar Chart color for each individual value bar.

Allow formatting of numerical values used in the scale to be configurable.
E.g. use display digits set on attribute or be able to specify number of decimal places.

Currently number formatting only affects the values that appear in the tooltip.

Fill the area between the trend line and 0 (or a configurable value) with color (otherwise known as an area chart). This makes deviations from a desired value much easier to see.

Currently only the Target limit attribute is able to be added as a column in Table symbols. It would be nice to be able to add the other limit attributes (e.g. HiHi, LoLo, etc) to be added as columns too.

For example, a display containing two value symbols that display data for a tag. One value symbol shows the value for the tag at a specified time yesterday and the other one shows the value if the tag at a specified time today.

In PI Vision, the hyperlink can be enable/disable based on different AF attribute values

Ability to control the font size of a text symbol based on a data item's value using the multistate functionality of PI Vision.

Currently, the font size is directly related to symbol size. This is problematic when migrating button symbols from PI ProcessBook to PI Vision, since they will not retain their width. This leads to manual work being required to adjust the display layout after displays are migrated.

An alternative solution would be to add a button symbol to PI Vision that can be sized independently of the symbol's font size.

To be able to have event tables within Collection (this is mandatory)
Event tables are feed with events matching the collection asset.

It is different than the idea https://feedback.osisoft.com/forums/320517/suggestions/35062504

Would be great to be able to:
- have cursor(s) on XY plots

Data that is outside of the range of the Min and Max set in AF show up as 'bad data' in a multi-state display. This means instead of the display on the screen flashing red they turn blank (how our multi-state is setup)

I think this shouldn't behave this way. If my temperature drops below the min I want it to be shown out of spec, not bad.

I also can't just change the min and max as it drives the scale on the gauges.

Not all users like synchronized trend cursors (placing a cursor on one trend causes it to appear on other trends at the same time), some find it very distracting. There should be an option to disable this functionality.

Allow selection of multiple Traces in the Trace Options, and allow modification of the Legend Label for all of them at the same time so they all have the same Legend Label configuration

I have summarized energy data for kWh consumption by day for buildings and plant that is written at specific end of shift day week points.

I'd like to be able to have this display as a stacked bar where the various plant consumption components are shown as a proportion of the bar and the height of the bar is the sum of the components.

Classic stacked bar chart.

Select values from collections using Ctr to ad hoc trends.

Right now we will get whole collection to ad hoc trend and need to remove unwanted values/atributes, we would like to get only selected values using CTL to ad hoc trends.

Currently, some AF attributes' value is multi-line string. We hope pi vision can also display them in multi-line way .

PI Vision 2021 introduces the ability to wrap text within the Table symbol.
But it's for long text, if the AF attribute value is multi-line string, it will not wrap line according to line breaks.