![]() | ![]() |
|
HTML is automatically rendered in grids*. It would be nice to be able to specify whether or not HTML is interpreted or rendered as plain text in grids. I believe it would be OK (and probably much easier) to manage this per grid rather than per column.
(*although there appears to be some in some versions that do not, although ours seem to work)
FYI, in V9.1.1 grids no longer interpret at all, but all of the tags show making HTML fields (such as RTFs) practically unreadable to "normal" users.
I logged this with the Helpdesk and it has been given defect number DEF19072.
Oh Great!
This is what I meant in one of my earlier posts here - one persons feature is another persons constraint.
I logged this as an issue because it was interpreting (presumably now fixed in 9.1.1)
I have an application where I cannot use grids because I don't want the grids to interpret the data, I want it displayed verbatim so I am less pleased that the defect that has been fixed has now become a defect itself!
This is what Jerome (and I) was getting at - let's have the option.
I agree with the option; I wasn't trying to dispute that. As long as there is a decent way to either display the encoding or easily remove the encoding in a BO so it can be used in a grid.
My concern is that Metastorm may implement a change in behaviour becasue it is seen by some users as a benefit without understanding that it may actually be the opposite to another group of users.
We expect a text and memo field on a form to display the full text of the bound data and I would expect that a text based grid cell would do the same. IMO the fact that a text grid cell does not is a defect.
I accept that it would be useful for grid cells to be able to render html and other formats maybe but this must be controllable at design time. So maybe the best route for Metastorm would be to have a column option for HTML
Agreed an option would be great.
I would also be great to extend this option to reporting.
If a field that has html in it is reported on, then you see the HTML code.
You must be a registered user to add a comment here. If you've already registered, please log in. If you haven't registered yet, please register and log in.
How to Be Notified of New Releases
How to Suggest Product Enhancements
Metastorm BPM 7.6.4 Hotfix 2 (7.6.4.2) is now available for download in the 'Patches' section of the Knowledge Center here.
Metastorm BPM Widgets Release 2 for OpenText Smart Business Workspace Version 9.1 and Metastorm BPM 9.1.3 is now available for download in the 'Patches' section of the Knowledge Center here. For more information see this post.
Metastorm BPM 9.1 SR3 (9.1.3) is now available for download in the 'Patches' section of the Knowledge Center here. For more information see this post.
Metastorm BPM 9.1.2 Hotfix 2 (9.1.2.2) is now available for download in the 'Patches' section of the Knowledge Center here.
Note: Software and documentation are now in the Knowledge Center (KC) located here.
Have a question about the Community Site? Contact Us
![]() |
![]() |
![]() |
|
|
![]() |
![]() |
![]() |
















