Invoking a JADE Report Writer Application from a User Application

The JADE Report Writer Configuration and Designer applications should be integrated into the user system. The JADE Report Writer Designer application print, extract data, and preview options are not enabled unless the report designer is run from the user system.

For initial evaluation of the JADE Report Writer, you can do this from JadeScript methods, as shown in the following examples.

startConfiguration();
vars
    rwManager : JadeReportWriterManager;
begin
    create rwManager transient;
    rwManager.startReportWriterConfiguration("a user name", null);
epilog
    delete rwManager;
end;
startDesigner();
vars
    rwManager : JadeReportWriterManager;
begin
    create rwManager transient;
    rwManager.startReportWriterDesigner("a user name", null);
epilog
    delete rwManager;
end;

For full integration into the user system, use the same JadeReportWriterManager methods but with the first method parameter being the name of the currently signed-on user and the second method parameter being the subclass of JadeReportWriterSecurity in the user schema.

It is recommended that you run your JADE Report Writer applications as separate applications from the one in which you are working and on the same schema level as the schema on which you are reporting. Attempting to run your JADE Report Writer reports in the same session as your working application causes locking issues that can result in impaired performance.

The JadeReportWriterManager class provides two methods, startReportWriterConfiguration and startReportWriterDesigner, to start the JADE Report Writer Configuration application and the JADE Report Writer Designer application, respectively.

The JADE Report Writer keeps a reference to the security object reference set when the setSecurityObject method of the JadeReportWriterManager class is called. The security object is used whenever the JADE Report Writer needs to check security access to something. This reference is held in the internal equivalent of the user app object, so needs to be valid for the life of the application.

Instead of deleting it after calling the report writer startReportWriterConfiguration or startReportWriterDesigner methods, it would be best to create it once and hold a reference in the user app object or equivalent, and reuse this instance so it stays valid. It can be deleted at the end of the application.

For details, see "Dynamically Configuring JADE Reports at Run Time" under "Run Time Considerations", in Chapter 6. For full details, see the JADE Encyclopaedia of Classes.

For details about configuring or designing reports, see Chapter 3 or Chapter 4, respectively.

Depending on your security class access, you could have read-only or full access to your JADE Report Writer application. If you are limited to read-only access, the title bar will display [Read-only] along with the usual information. With read-only access, you cannot save or apply any changes to a report layout or reporting view.

 

VERSION 2018.0.01  |  Copyright © 2018  Jade Software Corporation Limited.  All rights reserved.