############################################################################ PRONTO-4GL Release Notes ############################################################################ NOTE: ===== - The official XI release is version 6.2. See release62.txt for further release notes. Pending developments for 6.1 ---------------------------- - Basic dumb terminal (and X-Windows) support. ** Release 6.1v20 ** ==================== Miscellaneous ------------- - Added Field Copy mode to the Edit menu (allows you to click on any field to copy it to the clipboard). Note: this is not available for tree or pop-up menu items. Unix versions require Proclient 4.0v10 for this feature. - Fixed problem where last inserted record was not shown on exit of Entry mode. - Fixed truncation of subscript number of XML tag within XML file for long field names (e.g. 27+ characters). - Fixed incorrect page_header end tag in basic XML reports where a page contains a page header but no detail section. - Fixed problem where default values were ignored for a Find operation. - Fixed Red Hat Linux 7.3 SEGV crash. - Program initiated updates without a locked record will now fail if any field changed by the program has been altered by another application (even if it is to the same value). - Added Text/XML/HTML options to Send to Proclient option in PROPRINT (Unix version only). DRILL-BACK clause on FIELD definition ------------------------------------- - Fields defined within a program (i.e. non dictionary fields) can use the DRILL-BACK clause to define the drill back/down command to use for it's data. e.g. field my-spool-file-name pic x(20) drillback is "proprint" - NOTE: LIKE fields do not (currently) inherit locally defined drill back commands. HTML mail support (Unix only) ----------------------------- - The MAIL-ATTACH command now supports attaching reports in HTML format as the body of the mail. - The PROBATCH utility can send the output of batch jobs in HTML format to enable spool file names to be drilled back to the PROPRINT utility. This will currently only be done if the PROBATCHHTML environment is set to 'Y'. - NOTE: Most mail clients (e.g. outlook) by default disable the scripting and ActiveX controls required to perform drill back (due to security reasons). To enable drill back from Outlook, you may need to change the security settings for scripting and ActiveX in the Internet zone of IE. These changes will affect both Outlook and Internet Explorer security. It is advised that you set them to Prompt rather than Enable so that you are aware when an ActiveX control is being initiated. Contact your system administrator for your company's policy on IE security settings before making any changes. - If you click on a drill back field and nothing happens, it is likely that scripting is not enabled. If you encounter an error, it is likely that ActiveX is not enabled. - Windows implementations of PRONTO do not currently support the generation of HTML mail. ** Release 6.1v19 ** ==================== XMLSPOOL clause in $PRONTO/lib/printers file -------------------------------------------- - A Windows based XML print server is now available. This allows Unix based implementations to spool jobs to the print server, which will render the output and direct it to the nominated Windows print queue. - This method of printing has the following advantages: 1) It removes the overhead of rendering the output from the Unix host. 2) Only basic rendering is currently available for Unix based printers, so many customised style sheets would need to be rendered on a Windows system. 3) Output can be spooled to the print server via batched jobs. - A clause called XMLSPOOL is available for PRONTO printers defined in the $PRONTO/lib/printers file. This specifies that printing is to be spooled to the XML print server specified by the XMLSPOOL value (host name or IP address). The SYSNAME clause, if present, specifies the name of the Windows print queue to ultimately send the output to, otherwise it goes to the default defined for the XML print server. For example, my_printer, sysname=\\server1\lp0, xmlspool=172.1.2.3, - This is only valid for XML/XSL format reports on Unix based systems. The XMLSPOOL clause is ignored on Windows implementations of PRONTO. - The "type=" clause is not required, and will be ignored if specified. - The current implementation does not support the printing of multiple copies, or a from/to page range (i.e. it always prints the full report). These options will be added at a later release. SYSNAME in printers file (Unix only) ------------------------------------ - A SYSNAME clause that contains the name of a Windows based print queue (defined with leading \\ characters, e.g. \\server\printer) will be assumed to be a Windows based printer. If the XMLSPOOL or PROCLIENT clauses are not present for the printer, then the PROCLIENT clause will be assumed. This will cause print requests to be routed to the user's proclient session for processing. This only applies to XML/XSL reports. MAIL-ATTACH function added -------------------------- - This function attaches the specified file to the mail message being generated (using the existing PRONTO mail functions). - It's format is: MAIL-ATTACH (, , , , ) - It returns 1 for success and 0 for failure - The parameters are: Name of file to attach. This can be the name of a PRONTO report file (#P or .xml). Name of file to send in mail message. Currently ignored. 1 if file is to be sent in the body of the message. 0 if a separate attachment. Report conversion flag (for #P or .xml files). 1 means convert to HTML. 2 means convert to text. 0 means no conversion. 1 if file/s are to be removed after they are attached. 0 if they are to be left. - HTML format is not currently supported for attachments with the flag set. Miscellaneous ------------- - Multi-field (column) clipboard paste re-implemented. This is available only from the Paste button and pop-up menu. Single field paste is only available using CTRL-V. Unix implementations require Proclient 4.0v07. - Proclient Terminal mode copy/paste re-implemented. Requires Proclient 4.0v08. - XSL generation changed for non-full XML reports to overcome problem where first line of header printed on previous page on some reports. - PROPRINT now supports XML/XSL files for mailing, text conversion and batched printing. - Added -r option for PROPRINT to restrict access to the specified report. The user is able to view and print the report, but cannot remove it. - PROXMLPRINTSIZE and PROXMLDISPLAYSIZE environment variables are available to set the default print/display font sizes when generating a report (when a customized style sheet is not used). - The default font size for printing is 10pt instead of 6.7pt for reports declared as 80 columns or less. - The enable/disable status of the tool bar and status bar are retained. ** Release 6.1v18 ** ==================== XML/XSL Report Colors --------------------- - All XML/XSL reports generated will now have separate colors specified for the page header section. The page header section is deemed to contain all lines printed from within the routine specified in the HEADER clause of the REPORT statement. - The following environment variables can be set to alter the default colors used with generating a report (that is not using a customized style sheet). PROXMLHEADERFG - Foreground color for the page header PROXMLHEADERBG - Background color for the page header PROXMLDETAILFG - Foreground color for the detail/body of the report PROXMLDETAILBG - Background color for the detail/body of the report PROPRINT -------- - A -v command line option has been added to PROPRINT. This specifies that the report viewer should be invoked for the spool file specified. - The command line syntax is: proprint -v spool-file Unix ---- - External application launch requests (e.g. drill back) supported within the runtime. This requires Proclient 4.0v06 (and associated components). SQL Server ---------- - Fixed problem with procopy when copying alpha key fields which have been enlarged, on systems with the old null padding (fill char) option set. Miscellaneous ------------- - Fixed problem with direct print for non-XML reports. - Fixed refresh of records after entry into an empty review screen where the application re-read the inserted record (RDBMS versions only). - No longer automatically get current record when entering a screen if there is an INITIAL-MODE specified that does not require a current record. ** Release 6.1v17 ** ==================== XML/XSL Printing ---------------- - Changed default XSL style sheet generated for basic (non FULL-XML) reports to overcome additional blank lines at start of pages when printing. - Unix proxmlprint utility changed to support new style sheet format. Miscellaneous ------------- - Fixed problem with suppressing modes via screen customization. ** Release 6.1v16 ** ==================== Miscellaneous ------------- - Changed data-grid/review screen refresh after entry to be consistent with previous versions. - A screen invoked with no valid modes (e.g. search without a primary) will pause at exit (as per previous runtimes). - Limited dumb terminal support (e.g. no data-grids etc.) enabled for use with RF units. - Default behaviour of F1 key changed. F1 will not invoke program generated help. It will only show dictionary field help and context sensitive help from the user manuals. The F2 key will work as it traditionally has. It will show program generated help if present, as well as dictionary field help and context sensitive user manual help. - Keyboard macros have been re-implemented. - Automatically widen a non data-grid parent window to allow for a scroll bar if a child screen using the parent window contains a data-grid. - Fixed crash when processing a full-page XML report. SQL Server ---------- - An automatic CLOSE operation on all database tables will be performed by the runtime after an application creates (or truncates) a SQL Server table that is not contained in the current data area (e.g. sysinfo tables). This is due to SQL Server automatically closing all "cursors" (connection points) as a result of the operations required to grant table access permissions. NOTE: this is not an issue for TEMPORARY tables, only PERMANENT database tables. Record positioning will be maintained (where possible), however, locked records will not be maintained. C-ISAM ------ - The transaction log format (for rollforward operations) has changed to allow for 4GB+ log files. Only 32bit AIX implementations, and platforms running full 64bit PRONTO implementations currently support log files over 2GB in size. This only applies to permanent transaction logs used to enable roll forward recovery of a data area. NOTE: This log file format is incompatible with the previous format. Any existing log files should be reset (truncated) before using this runtime. Log files must not be shared between data areas using this and older runtimes. Roll forward operations using the proroll utility provided with this runtime will not be successful on existing (old format) log files. ** Release 6.1v15 ** ==================== Miscellaneous ------------- - Multiple page print requested via the XML viewer at report generation fixed (Unix only). - New XML viewer included with release. - Worked around Windows XP problem on program exit. - Internal changes to PCS file (screen customising) processing. - Updated Unix XML print program (proxmlprint). - Only permit a single XML viewer to be launched if multiple reports generated. - The ODBC server/daemon distributed is no longer the release 5 version. PRONTO SQL/LST/RPT ------------------ - The PRONTO SQL module and report generators now support basic XML/XSL format reports. PROCLIENT clause in $PRONTO/lib/printers file --------------------------------------------- - A clause called PROCLIENT is available for PRONTO printers defined in the $PRONTO/lib/printers file. This specifies that printing is to go to a workstation defined printer via the user's Proclient session. e.g. my_printer, sysname=\\server1\lp0, proclient, - This is only valid for XML/XSL format reports on Unix based systems. The print request can only be made for interactive sessions (i.e. not batched). - The "type=" clause is not required, and will be ignored if specified. - Printers defined in this way can be used to implement direct printing from PRONTO applications, as well as printing directly from Proprint (without the viewer being active). RDBMS ----- - Views named after the original PRONTO object are automatically created (and updated) to access the physical database table associated with it, whenever a new table (or new version of the table) is created. e.g. a view called "deb_master" will be created to access table "def5mfl", and will be automatically updated to reflect the correct table name if the version of the table changes. ** Release 6.1v14 ** ==================== Miscellaneous ------------- - Fixed problem with communication between proclient and the XML Viewer for non FULL-XML reports. - Ensure help line for input fields whose WHEN clause was initially invalid is set. ** Release 6.1v13 ** ==================== Proclient --------- - Re-implemented Slave Printer control. - F6 (screen print) logic added. Miscellaneous ------------- - Direct XML printing when report is generated is now supported. - XML printing is on by default if licensed (without PROXMLREPORTS set). - Aggregates option for data-grid columns implemented. - Fixed problem with debug window remaining hidden. - Fixed help line of data entry fields for old (pre 6.1) apps. - Default value (and trigger) processed for fields in modes defined with both entry and correct (i.e. entry and correct both defined in same mode). - Added -s option to proenq to be compatible with proman. ** Release 6.1v12 ** ==================== NO-XML clause on REPORT statement --------------------------------- - The NO-XML clause can be used to disable XML/XSL reporting for a report. The report will be generated in the traditional (older style) report format (i.e. #P format). SET-HELP-CONTEXT function ------------------------- - The SET-HELP-CONTEXT (, ) allows an application to specify the help file name and optional context ID within the help file to use if the help key is pressed. - The parameter is a text string containing the name of the help file to invoke. If a full path is not specified the runtime will use the default location for PRONTO help. If no extension is specified then an extension of .chm (compiled HTML) is used. - The is a number representing the marker within the help file for the current help context. If this number is zero then no help context is used. This number is only valid with Windows .chm or .hlp format files. - The return value from this function should be ignored. Additional Folder Icons ----------------------- - The following folder icons are now available: BLUE-FOLDER-ICON, RED-FOLDER-ICON, GREEN-FOLDER-ICON, and ENQUIRY-FOLDER-ICON. Viewing/Printing XML reports ---------------------------- - Unix implementations can now view XML reports when running with Proclient. The view is launched by default when the report is being generated. It is also available via PROPRINT. NOTE: data item drill back is not yet available for Unix generated reports. - Printing of XML reports can now be selected via PROPRINT. Only the default printer defined on the workstation is currently available. Miscellaneous ------------- - Re-implementation of cursor/caret functions for screen/report painters. - Set Next-scr/Prev-scr modes instead of Next/Prev when processing intermediate rows when moving to the row clicked by the user in a data-grid. - A right justified ACCEPT with a PIC smaller than the field now correctly stores the value entered as right justified within the full field's size. - Fixed fault where incorrect center, or left/right justify could occur for a data-grid column. - Changed tag name for subscripted fields in full XML reports. ** Release 6.1v11 ** ==================== SPOOL-ONLY clause ----------------- - The SPOOL-ONLY clause on a REPORT statment specifies that the XML viewer should not be automatically invoked to view the report. TREE-MENU clause ---------------- - The TREE-MENU clause on a MENU can be used to indicate to the runtime that this menu should be displayed as a tree style menu instead of a popup menu. - If a valid tree menu is active (without child screens invoked), then the menu will form part of this tree menu. Otherwise a new tree menu will be created. - If the MENU contains the NO-HIDE clause then the TREE-MENU clause has no effect. If the MENU routine does not define it's own window, then a NO-HIDE clause on the routine that defined the window will also override the TREE-MENU clause. Unix/Proclient -------------- - Internal communications protocol changes (affecting data-grid row selection). Proclient 4.0v2 (and later) is required! - Fixed proclient crash if incorrect username/password entered. - Fixed problem on Windows 95/98 when incorrect menu selection character entered for a popup menu. Miscellaneous ------------- - Change to default field values on a Find. Fields will default to their current values unless a specific default is specified in the ACCEPT statement. This is intended to benefit multi field Find operations. - Multiple tree menus now supported. - Internal changes to support data-grid screen customisation. - Fixed fault with REFRESH REVIEW when issued while in CORRECT mode. - Fixed segmentation violation via the F9 key if user defined sorting specified for certain screens. ** Release 6.1v10 ** ==================== Unix/Proclient -------------- - Initial Unix/Proclient version. Requires Proclient version 4.0 (and later). - Dumb terminal (and X-Windows) support is not available in this release. - Interaction with the XML report viewer is not implemented in this release. - Proclient 4.0 will support older (pre 6.1) version PRONTO runtimes. Due to differences in implementation of the message help text, older runtimes will show an additional message/help window. This will generally be obscured by the application's window unless input is required from it. - The .INI file is only supported for passing communications information to Proclient. All other user configurable settings are stored in the Windows registry, and are ignored if found within the .INI file. If no .INI file is found, the registry will also be used for communications information. - All user configurable settings that occur in both Proclient and the standard Windows version of PRONTO are shared. For example, changing the fonts within Proclient will result in the fonts for the Windows version of PRONTO also being changed. Miscellaneous ------------- - Environment, Color, Font and General dialogs are now implemented. - The size of the main PRONTO window (frame) and initial tree menu are now saved in the registry when their size changes. This size (including maximised state) is restored when a new PRONTO session (Windows and Proclient) is started. NOTE: In Windows (non Proclient) versions, this only applies to programs which invoke an initial tree style menu (e.g. bmsmenu). - The PRINT statement now supports the LEFT, RIGHT and CENTER clauses to control the justification of text. This only has effect in full XML reports. Data Area (Company) Colors -------------------------- - You are now able to define a specific set of colors on a per data area (company) basis. - This, in conjunction with a per data area logo (background image), allows users to easily visually distinguish between data areas (e.g. testing versus live). ** Release 6.1v09 ** ==================== Miscellaneous ------------- - Fixed 6.1v08 bug where modes were not hidden when Entry/Correct selected. - Sort/Filter options available to datagrid screens that inherit a window. - Changes to default XSL generation. - Terminate (non-zero) fonts correctly in XML reports. ** Release 6.1v08 ** ==================== HELP Files ---------- - PRONTO now searches for .chm (compiled HTML) format help files, rather than .hlp format files. SET-BACKGROUND-IMAGE Function ----------------------------- - This function allows a background image to be specified. This will be displayed beneath the PRONTO logo. - e.g. if set-background-image ("c:\bitmap\logo.jpg") endif - To turn off the background image, pass a blank (spaces) image path. - NOTE: The image will not be scaled down to fit. If there is insufficient room to fit both the standard PRONTO logo and the specified background image, then the background image will not be displayed. Miscellaneous ------------- - Fixed bug causing fields to be blanked when scrolling a review screen (not a data-grid) where the application CLEARed then DISPLAYed/ACCEPTed the field. ** Release 6.1v07 ** ==================== FULL-XML clause on REPORT statement ----------------------------------- - The FULL-XML clause on a REPORT statement indicates that the report will be generated as a fully compliant XML/XSL report. This requires all XML sections to be identified within the report by use of the REPORT SECTION statement, and the SECTION clause on the PRINT statement. REPORT SECTION statement ------------------------ - This statement marks the start (or finish) of an XML section within the report. - The syntax to start a section is: REPORT SECTION [IS]
[ HIDDEN | CAN-HIDE ] [ COLOR [IS] ON ] [ ON ] -
can be any valid alpha expression or string. This is used to generate a path list within the XML file. If the section string does not start with a / or \, it will be added to the current XML path. A section named .. refers to the parent section. By default, the section string should not contain /, \, or .. characters. - A section once closed cannot be reopened (i.e. continued). A closed section can only be started again. - The HIDDEN clause indicates that the contents of this section will not be shown by default. The previous line in the report (contained in the parent section) will show a button to allow this section to be expanded. You are advised to allow 3-4 characters at the start of the previous line for the button. - The CAN-HIDE clause indicates that the contents of this section will be shown by default, but can also be closed/hidden. The previous line in the report will show a button to allow this section to be closed. - The COLOR/COLOUR statement is used to specify the default foreground and background colors to use within this section. - The syntax to finish the current section is: REPORT SECTION FINISHED - The FINISHED clause has the same effect as specifying: REPORT SECTION IS ".." SECTION clause on PRINT statement --------------------------------- - The SECTION clause on the PRINT statement is a shorthand way of defining a single line section. - For example: PRINT "xyz" in col 1 SECTION IS "xyz-sect" is equivalent to: REPORT SECTION IS "xyz-sect" PRINT "xyz" in col 1 REPORT SECTION FINISHED TAG clause on PRINT statement ----------------------------- - The TAG clause can be used to override the default XML tag for an item being printed. The default XML tag for a single field is it's name. Default tags for text and expressions/functions are internally generated. - For example: PRINT "xyz" TAG IS "xyz-tag" SECTION IS "xyz-sect" STATIC clause on PRINT statement -------------------------------- - The STATIC clause is associated with the previous item (field, text or expression) in the PRINT statement. It indicates that this item will always contain the same contents within this line of the current section. Generally, only text items should be specified as static. - Static items are not written to the .xml file, but are defined within the .xls file (style sheet). COLOR clause on PRINT statement ------------------------------- - The COLOR/COLOUR clause allows the specification of foreground and background colors for individual items within a PRINT line. - Due to the conflict with the use of the ON keyword in the COLOR clause and it's use within the PRINT statement to specify a named report, care must be taken if both these clauses are used. Either ensure that a background color is always specified, or do not place the COLOR clause directly before the ON clause for the report's name. OK/Cancel buttons ----------------- - A screen in correct mode that does not have a PRIMARY defined is no longer initally positioned on the OK button. - The POSITION-ON-OK clause for a screen indicates that the OK button should be positioned on initially (i.e. gain focus) when the screen is in correct mode. - If the screen requires confirmation based on the CONFIRM statement, the Cancel button will be the default instead of OK if the default for the CONFIRM is NO. PROXMLREPORTS environment ------------------------- - This environment now supports the following values: NO or FALSE - Use old (non-XML) format reports SPOOL or SPOOL-ONLY - Don't pass XML thru viewer VIEW or VIEW-ONLY - Pass XML thru viewer and remove spooled XML report when finished. - Any other non-null value will currently be interpreted as requiring reports in XML format which will be spooled and viewed. - If the environment is not set, then old (non-XML) format reports are generated. F6 Key ------ - The F6 key now invokes a process that adds the screen's image to the clipboard, and allows the image to be printed. - The image processed is that of the full PRONTO controlling window. Customised XML Style Sheets (XSL) --------------------------------- - Customised style sheets can be used in place of the default generated .xsl file for an XML format report. - The customised style sheet must be named based on the form type of the report (as defined in the FORM clause of the REPORT statement), with a .xsl extension (e.g "Invoices.xsl"). - Customised style sheets will be searched for in the following locations: 1) Current data directory 2) Current report directory (if different from data directory) 3) In the $PRONTO/custom_xsl directory (or $NETPRONTO if Windows C/S) 4) In the $BMS/custom_xsl directory MESSAGE Statement ----------------- - Messages without the NO-BELL clause are no longer displayed on the bottom help line. Instead, they are always displayed in a message box/window, which will require the OK button to be pressed to acknowledge the message. - A MESSAGE statement with a NO-BELL clause that is immediately followed by the PAUSE statement will also be displayed in a message box/window. - If the PAUSE statement immediately follows a MESSAGE statement without the NO-BELL clause, the PAUSE will be ignored (to avoid an additional unwanted user interaction). ** Release 6.1v06 ** ==================== IF-THEN-ELSE() function ----------------------- - The if-then-else (, , ) function has been added. - It can be used anywhere that a function/expression can be normally used. - This function implements an in-line IF THEN ELSE test within an expression. The function returns the value of the THEN expression if the IF condition is true (or non-zero), otherwise the vaue of the ELSE expressions is returned. - The results of the THEN and ELSE expressions must be compatible (i.e. both numeric, or both alpha). The result of the if-then-else function will be the same type as the results of the THEN/ELSE expressions. - The IF condition can contain any valid conditional/logical expression. e.g. set x = if-then-else ((i < 0 or i > 10) and x != spaces, "A", "B") - It is different from a normal function in that only the required THEN or ELSE expression (parameter) will be evaluated, depending upon the result of the IF condition. This is partly to optimise the function, but also to allow the IF condition to test for valid subscript values etc. e.g. set x = if-then-else (i > 0, a[i], spaces) In this example, the THEN expression (a[i]) will only be evaluated if the IF condition (i > 0) is true, so a subscripting error will not occur when i is less than or equal to zero. - The THEN and ELSE parameters are expressions, and can therefore contain other if-then-else functions nested within them. e.g. select *, desc = if-then-else (sol-line-type = "CR", "Credit", if-then-else (sol-line-type = "IN", "Invoice", if-then-else (sol-line-type = "JE", "Journal", "Other"))) Initial XML/XSL report support ------------------------------ - Reports can be generated in a basic XML/XSL format. This is currently controlled by the PROXMLREPORTS environment. If this environment is set to a non-null value the reports will be generated in XML/XSL format. This environment is temporary, and is intended only for the transition period for full XML/XSL support. - A pair of files are created for each report. The format is a unique random number, followed by the file type extension ("xml" and "xsl"). The XML file contains the data for the report. The XSL file contains the default style sheet to be used to format the XML data of the report for printing or viewing. ** Release 6.1v05 ** ==================== OK/Cancel buttons ----------------- - The runtime will automatically display OK/Cancel buttons when in entry or correct mode of a screen. They are not shown for entry within a procedure. - When entry/correct is selected for a screen, the screen's modes are hidden and the OK/Cancel buttons are displayed in the center of the line used by the modes. - Clicking on or pressing the OK button has the same effect as pressing the F4 (Finish) key. Clicking on or pressing the Cancel button has the same effect as pressing the Home (Cancel) key. - The OK/Cancel buttons will only gain focus for keyboard entry if the screen would normally ask for confirmation for entry/correct. The OK/Cancel buttons replace the confirmation question in this situation. - A screen in correct mode that does not have a PRIMARY defined is assumed to be an options/defaults screen. In this situation the OK button will initially have the keyboard focus, rather than the first ACCEPT. - Only the screen that defines the current window can gain keyboard focus on the OK/Cancel buttons. Sub-screens that inherit the window of the calling routine will not give focus to the OK/Cancel buttons. They can still be clicked on when a sub-screen is being processed. - The OK/Cancel buttons are not shown on a window that is less than 4 lines deep. - The NO-OK-CANCEL clause can be used on a screen to disable this functionality. PRODEFDATAGRID environment -------------------------- - An environment variable called PRODEFDATAGRID has been added. This environment is intended specificially for software developers and testers. - If set to a non-null value, it indicates that the default view of a datagrid will not be shown with user modified column sizes or positions. It has no effect on named views for a data grid. - This environment allows developers and testers to run applications with their default data grid settings, eliminating confusion caused by user changes to them. Export of Data Grid Columns --------------------------- - The Export button is now implemented. This allows the export of all valid columns for the data grid in it's current view. - Only columns that are the direct result of the SELECT for the data grid will be exported. - This generates a temporary XML file which is passed to a script on the workstation called "xml_export.vbs". The standard version of this script is contained in $PRONTO/bin. User specific versions can reside in the $PRONTO/lbin directory on either the workstation or the server. ** Release 6.1v04 ** ==================== User specified column filters ----------------------------- - The user can now click on a column and specify a filter criteria and value. User specified sort ------------------- - Multiple columns can now be specified for sorting. User Views ---------- - The Views menu allows a user to save and invoke named views of the data grid. - The views allow the user to save specific column sorting and filters, as well as the size and positioning of the columns within a data grid screen. ALWAYS-SHOW clause added to MODE statement ------------------------------------------ - This clause only has effect if a WHEN clause is present for a MODE. - If the WHEN clause is invalid when the modes for a screen are initially shown, by default the mode will be ommitted. A mode with the ALWAYS-SHOW clause will always be added to the screen regardless of the initial state of the WHEN condition. - NOTE: The ALWAYS-SHOW keyword is interchangeable with the NO-HIDE keyword. New Menu Icons added -------------------- - An icon for the favourites folder (FAVOURITES-FOLDER-ICON) has been added. - An icon for a locked folder (LOCKED-FOLDER-ICON) has been added. PRODEFDATAGRID environment -------------------------- - Application developers can set the PRODEFDATAGRID environment to indicate to the runtime that the default view of a data grid should initially always show the application's default column size and position. Any non-null setting of the environment will turn on this feature. ** Release 6.1v03 ** ==================== - Interim internal release. ** Release 6.1v02 ** ==================== PRIMARY converted to SELECT where possible ------------------------------------------ - All PRIMARY clauses on a SCREEN will be converted to their equivalent SELECT operation by the compiler. - The existing PRIMARY logic within the runtime is intended to be phased out in favour of SELECTs. - The operation of the SELECT for a screen has been enhanced to remove some of the existing limitations. The REVIEW-FROM-CURRENT and the START-ON-CURRENT-RECORD clauses are now supported for a SELECT. - If the DIFFERENT clause has been used, only those fields nominated will be returned to the screen. REFRESH DATA/REVIEW changed --------------------------- - A REFRESH DATA (on a non data-grid/review screen) or a REFRESH REVIEW will cause a repositioning of the current record within the SELECT for the screen. - The application must issue one of these statements if it wants to force the SELECT for the screen to reflect any change it has made to the current record location of the object/s associated with the SELECT. DISPLAY of field converted to ACCEPT READ-ONLY ---------------------------------------------- - A DISPLAY of a single field in a SCREEN that is defined with a SELECT and a DATA-GRID, is converted to a READ-ONLY ACCEPT. This is to enable the Find operation to work on this field if the user has specified a different sort order. User specified sorting added ---------------------------- - A user is now able to click on the column in a data-grid and nominate to sort the contents of the data-grid by that column. - Currently, sorting can only be specified on a single column. Multiple column sorting (and filtering) will be added in a future release. - Only columns that are the direct result of the SELECT for the screen may be sorted. This excludes any fields/values calculated within the DETAIL of the SCREEN, as this occurs after the sorting of the rows has been processed. ** Release 6.1v01 ** ==================== - Interim internal release. ** Release 6.1v00 ** ==================== Hidden Windows for PROCEDUREs ----------------------------- - The window for any PROCEDURE will remain hidden until input is requested from it via an ACCEPT statement. - This is mainly to overcome problems with existing applications that create dummy windows. It is also to remove non-input windows prior to the initial tree view being shown. These dummy windows are now noticable (if not hidden) as all windows will be created with title bars and borders. - Any window that does not contain input, but is required to be shown, must have the NO-HIDE clause specified. - This behaviour may be changed in future to show windows as long as they issue a DISPLAY statement. This will depend upon a review of the application software. Tree View Menu -------------- - A tree view menu system is now available to navigate through the application's menu instead of the traditional button based menus. - A menu invoked while there are no visible windows (excluding the tree view) will be shown within the main tree view menu by default. - The NO-HIDE option on the MENU will cause the menu to be displayed in the traditional way rather than via the tree view. - Menus are defined within a program in the traditional way. A menu shown as a tree view (or pop-up) ignores any DISPLAY statements that may be present. - When running on a character based device, the traditional menu is used. Pop-up Menus ------------ - Any menu invoked while there are visible windows (excluding the tree view) will be shown as a pop-up menu by default. - The NO-HIDE option on the MENU will cause the menu to be displayed in the traditional way rather than via a pop-up (or tree view). - Currently, a pop-up menu is restricted to a maximum of 25 menu items. - When running on a character based device, the traditional menu is used. - The position of the pop-up will be based on the top/left coordinates of the last input field or menu option used. - Any pop-up menu should exit once the option has been performed. e.g. the CONFIRMED section of the CONFIRM should finish with an unconditional EXIT. The positioning of the pop-up menu after the user selects an option is not guaranteed. ICON clause on OPTION and MODE ------------------------------ - The icon used in the tree view can be specified by the use of the ICON clause on both the OPTION statement and MODE declaration. - Only the following predefined icon types are currently available: FOLDER-ICON ADMIN-FOLDER-ICON REPORT-FOLDER-ICON ADMIN-ICON REPORT-ICON SCREEN-ICON TRANSACTION-ICON PERIOD-END-ICON QUESTION-ICON BLANK-ICON - The syntax of the clause is: ICON IS e.g. OPTION "TESTING" @10,10 ICON IS SCREEN-ICON - The OPTION statement will allow the to be a numeric expression (or field name) to allow for variable options. The MODE declaration does not allow expressions. For example: SET OPTION-TITLE = "TESTING" SET ICON-NUMBER = SCREEN-ICON ... OPTION OPTION-TITLE @10,10 ICON IS ICON-NUMBER Data Grid Review Screens ------------------------ - A variation of the traditional review screen is available. A review screen defined as being a data grid provides moveable button style column headings, allowing columns to be resized and repositioned. - A data grid review screen is defined in the same manner as a traditional review screen except the keyword DATA-GRID is used. e.g. DATA-GRID OCCURS 14 - The column headings used are defined by the TITLE keyword associated with each ACCEPT or DISPLAY in the DETAIL section of the screen. e.g ACCEPT accountcode @4,10 TITLE IS "Acccountcode" DISPLAY shortname @4,25 TITLE IS "Short Name" - NOTE: the TITLE clause on an ACCEPT/DISPLAY is valid outside of DATA-GRID screens. It can be used in standard screens. - The buttons for the column headings will be displayed at the line specified as the starting coordinated for the data grid screen. Boxes may now have a title/heading ---------------------------------- - The TITLE clause is available for the BOX statement. If a title is given for a box, the title will be displayed left justified on the top line of the box. e.g. BOX @5,1 to @10,40 TITLE is "Details" Help/List button for input fields --------------------------------- - A help/list button will be shown beside an input field if there is a screen or menu available to provide assistence with the valid values. The button is only available while the field has the input focus. - Any ACCEPT that has an ON HELP-KEY section will automatically have the help/list button shown. Pressing the button will invoke the ON HELP-KEY section. - Any ACCEPT of a date field will also have the help/list button shown. If pressed the Windows Date/Calendar control will be invoked for the field. Window Titles ------------- - The TITLE clause is available for any menu/screen/procedure with a window. - This will set the title on the title bar of the window. - It is processed once only upon entry to the routine. BOLD/UNDERLINE -------------- - The DISPLAY attributes BOLD and UNDERLINE are now purely font characteristics. - BOLD indicates that the font selected should be bold (thick). - UNDERLINE indicates that the text should be underlined. - The foreground/background color selections for these attributes are now ignored.