A special end-user property of text fields is that if they enter a URL into the field, then when the field is rendered on a report, or the field is rendered in a read-only mode, the URL becomes a hyperlink to the URL. For example, if you enter http://www.mycompany.com or www.mycompany.com into a text field, then it will appear as http://www.mycompany.com or www.mycompany.com on a report, and if you click the text, a new window will open at the address of the URL. This behavior is extended one step further. Assuming that the title for the ID field in your instance is ID #, then entering ID # 12345 into a text field, will provide a link on reports and read-only versions of the field, to the detailed report view of the issue with the ID of 12345. If the title to the ID field is Report Number, then the end user would enter Report Number 12345 for the same effect.
It is possible to render HTML within a field on a report which has a display type of either text area, print text or log area. This is separate from the capability offered with fields with a display type of HTML Area, which is the recommended way of handling fields that will routinely hold HTML. The normal behavior with text area, print text and log area fields is that ExtraView will “escape” the sent being sent to the report in the browser. For example, HTML being sent to a field of these types will be shown as HTML and not rendered within the browser. This is the normal mode of working, as ExtraView is often used to track defects or bugs that refer to HTML code. There are some circumstances when you may want to actually view the code rendered as HTML within the text field. In order to do this, place the following text within the text field as you create –
<!-- generated valid html - don't escape! -->
All code following this, until the end of the field will be rendered in the browser. It is the user’s responsibility to ensure the code placed following the above text is valid HTML and will render appropriately. One interesting side effect of this feature is that you can legitimately place a complete program, along with buttons, forms and JavaScript within a field!
The field can be populated with code within user custom routines. For example, a field on an add or edit screen can contain the complete results of a query in report format.
This convention can also be used to decorate field titles and default values in the data dictionary.
