The default implementation of offline processing uses the report engine to generate special Excel documents during the download or to import them during the upload. This procedure is based on specific report definitions stored in default report XML files called reports_offlineprocessing_<component name>.xml. These report definitions must adhere to additional conventions:
Their ID must always be specified in upper-case letters. Example: <ID of object type>_<ID of editor role>.
The default implementation uses Excel reports only, which means that the required format must be Excel.
Excel cells that offline editors can edit must be marked with the renderer offlineProcessingInputReferenceRenderer or, optionally, with the style offlineinputcell.
The auto component offlineinfo must be part of the report definition.
When adapting editable cells in the report definition, you must ensure that these cells are marked as editable by the rule engine for the selected editor role. Otherwise, all attempts to upload documents are canceled. The following example shows how to incorporate the test case attributes Walkthrough name and Walkthrough counter into offline processing for the tester.
Location
XML file in the xml folder
DRL file in the rules folder.
Procedure
Copy the TESTCASE_TESTER report definition of the form to a separate custom.xml file and use the offlineProcessingInputReferenceRenderer report renderer for the cells of the Walkthrough name and Walkthrough counter attributes.
Copy the rules of the test case form to a separate testcase.drl file.
Adapt the rules so that the tester is allowed to edit the two attributes in the form.
Documents
reports_offlineprocessing_testmanagement.xml as a template
testcase.drl as a template
Example
OfflineProcessing_CustomizeDocument\WEB-INF\config\custom\xml\custom.xml: Enable offline processing for the two attributes in the offline document
OfflineProcessing_CustomizeDocument\WEB-INF\config\custom\rules\testcase.drl: Mark the two attributes as editable for testers