For modernization of green screen legacy applications, pattern recognition and transformation of host input fields can be achieved by HATS global rules, Global rules can work with customized and non-customized (default rendered) screens. They can be defined at project level and screen level both.
In a situation where project-level and a screen-level global rule are both defined for the same field, the screen-level rule has higher priority.
Project-level global rules are really global for the HATS application; they are effective in screens both transformed by the rendering set, and by custom transformations. This enables entire application to recognize a particular host screen pattern without modifying any of your screen level transformations.
A global rule contains a configured recognition pattern and a transformation fragment. The pattern configuration states what kind of content to look for on the host screen. It transforms specific fields or all fields of a certain size, or those adjacent to a string you specify.
More effective use of global rules is possible when host application has uniformity along the complete application, like all F4 Lookup fields have an identification symbol (e.g “ -> “) or word on host.
Following are few examples of global rules applied by the HATS, these can be applied once and users can witness the impact on all over the system.
We can create a rule in our HATS application to replace all appearances of “->” to an icon (e.g. ) on clicking this icon HATS will send some command or function key to host (e.g. F4). This can be used to open a lookup window like following.
Clicking one row from the popover lookup window fills the corresponding field on the parent page.
We can create a rule to put all fields with some identification for being a month (e.g. “M/Y”) to put an icon with them.
When user clicks a month it is auto inserted into the corresponding text field.
Date pickers can be applied to the complete application using global rules, but there has to be some identification on host application to let HATS know where it should generate a date picker icon.
A global rule can be created to display a yes/no drop down with every field with some identification (e.g.” y/n”)
We can apply a global theme with header, footer and background, this theme applies to all the screens of the application in one go.
Global rules using HATS default rendering can modernize the look and feel of the menu items across the application.
Sub files and tables,
Sub files and tables can also be modernized with improved look and feel by using global rules.
We can create global rules to modernize all function key indications to buttons styled with CSS, but there has to be a consistency among function key and its text or purpose. (i.e. F1 has to be used for help for the entire application and F4 has to be only used for prompt everywhere in the application)
If a green screen application fails to provide such consistency the HATS will have difficulty in applying the correct icon on the button.
Also the text associated with the Function key has to be of approximately an average length so that the modernized button can hold the text else the text may overflow from the button, as we can only make button of a fixed width using a global rule. A work around to handle this overflowing text is by chopping off some part of the lengthier text caption.
Global rules can globally apply table/grid themes and let us produce drop down input fields to perform actions on the table records.