A benefit of active reports is the ability to run these reports offline. You can export an HTML form as a FOCUS procedure (.fex) to provide the ability to schedule and distribute active dashboards, so these too can be run offline.
Export As Procedure converts the HTML page and embeds the code into a FOCUS procedure. The layout is no longer a webpage or HTML file, but a FOCUS procedure with embedded HTML code. The procedure (.fex) is added to the Procedures folder (in your local projects) or in your Standard Reports group folder (Managed Reporting environment).
Once the HTML form is saved as a procedure, it cannot be converted back to HTML Composer.
The Export as procedure is recommended for saving active dashboards only, as many layout controls and report formats are not supported.
Once the HTML form is exported as a procedure, it cannot be converted back to HTML Composer.
The New Procedure File dialog box opens.
If the layout contains any parameter controls other than an active control, the Export as procedure option is unavailable.
Export As Procedure converts the HTML page and embeds the code into a FOCUS procedure. The layout is no longer a webpage or HTML file, but a FOCUS procedure with embedded HTML code. This conversion requires conversion of each object on the HTML page.
The purpose of creating a procedure from an HTML form is to provide the ability to run these forms offline. Because you may not be connected to a WebFOCUS environment, the new procedure removes all referenced objects and adds them to the procedure. Layouts with controls that require multiple requests to the server are not supported.
The following conversions occur when exporting as a procedure:
The active reports (AHTML) format is preserved.
This code can become very long and it is recommended that only small images be used in layouts that will be exported as procedures.
Note the following limitations when applying the Export As Procedure in HTML Composer: