Release version: 6.19
Release date: 17th October 2023
Introduction
This page describes the enhancements in Lasernet FO Connector 6.19.
Click to view the Release Notes page.
Click to view the Lasernet FO Connector 6.19 New Features (part I) page.
Click to view the Lasernet FO Connector 6.19 New Features (part II) page.
Click to view the Lasernet FO Connector 6.19 New Features (part III) page.
Click to view the Lasernet FO Connector 6.19 New Features (part IV) page.
Click to view the Lasernet FO Connector 6.19 New Features (part V) page.
Click to view the Lasernet FO Connector 6.19 New Features (part VI) page.
Test & Performance Suite
Some extremely useful features have been added to the Test & Performance Suite (T&P).
Task recorder
Ignore usage data (task recorder)
New layout for printer dialog - “Tabbed form” (table of contents)
Support for XPath validation (XML file)
Ignore/reset personalization of Form(s)
Support for Filter in report overview and within structure/elements
Option to re-record from the UX Test
Filter when exporting and importing reports (to support playback)
Check points
Automatically compare PDF files
Option to ignore Jobinfos when comparing XML files
Task recorder
The following two new parameters have been introduced for the UX (User Experience) testing in Test & performance suite (T&P).
Lasernet > Test and performance suite > Parameters > General
Ignore usage data during test recording and playback | Will ignore the usage data when creating the recording(s) through the task-recorder. |
---|---|
Disable tabbed print settings form design | The tabbed print settings are disabled within the printer dialog. |
Ignore usage data during test recording and playback
Lasernet FO Connector saves much information as usage data (last values).
This could cause issue(s) in the playback of a recording and, therefore, issue(s) if the recordings are used for testing/automatic testing.
Example:
Print confirmation shown in the following image is saved within the usage data (last values) and could cause an issue if the recording does not contain the step for setting Print confirmation.
Playback of a recording for which the Print confirmation is not enabled, or for which the user running the playback does not have the Print confirmation enabled could get a block/stop in the recording.
Test & Performance Suite 6.19 contains the option Ignore usage data during test recording and playback.
Location: Lasernet > Test and performance suite > Parameters > General > UX Testing.
Enabling Ignore usage data during test recording and playback results in ignoring the usage data and, therefore, requires Print confirmation to be enabled as part of the recording. Otherwise, it is not possible to configure the destination.
Print confirmation gets disabled when preparing the recording even if it was previously enabled, as the usage data (last values) are ignored under the recording.
This ensures the recording is prepared from scratch (comparable to having no usage data (last values)).
Disable tabbed print settings form design
Enabling the option Disable tabbed print settings form design ensures the possibility to playback a recording containing a setting for the destination/printer dialog.
In Lasernet FO Connector, playing back a recording containing a setting for the fax, such as the one shown in the following image, can end up setting the wrong destination, causing to either stop the playback or throw an error.
Lasernet FO Connector 6.19 uses “tabbed form” (table of contents) by default for the settings of the destination/printer settings.
This is to ensure the playback of a recording in case it contains a setting for the destination/printer settings.
Having the Disable tabbed print settings form design disabled shows the setting for the destination/printer settings as follows, and ensures the right selection if the recording is used for playback/test:
Filter
The use of a filter in either the report list or within the structure/elements in Lasernet FO Connector was not properly recorded in previous versions of Lasernet FO Connector.
Being unable to have recordings that included the use of a filter could cause the playback of the recordings to stop.
This latest version ensures a complete recording, including the filter, is carried out, both in the report list and within the structure/elements. This recording can, therefore, be used for playback/test.
Validation of XPath
Another useful feature added as part of T&P is the option to validate a value within an XPath.
The option Set task recorder validation path appears when making a recording and when right-clicking the required XPath within the XML file.
Skip Validation of JobInfos
A new option to skip the validation of the information in the JobInfos section within the XML file has been introduced.
This is useful when data has been restored from PROD and information like connection is not the same. The following example illustrates how to avoid different destinations to cause failure:
Re-recording
A new option for re-recording has been introduced.
Re-recording existing task recordings simplifies the process of adjusting an existing recording.
Reset personalizations
Resets embedded form personalizations for the forms used in the recording
Filter for Copy, Export and Import configuration
A filter is introduced when Copying, Exporting or Importing reports.
This is added to assist the playback of a recording as wrong reports could get selected.
PDF comparison
It is possible to compare PDF files from the checkpoint in the Archive with the newly created PDF file.
This can be used as part of an upgrade in which checkpoints have been created prior to the upgrade and the PDF comparison is used to validate the documents (PDF files) before the upgrade with the documents after the upgrade.
There is a limitation when using checkpoints with some reports and Force re-run in Lasernet FO Connector.
Reports such as Sales invoices, Sales confirmations, Purchase orders have a journal/journal line, which ensures the possibility to use Force rerun when resending a document.
A report such as Cust account statement does not have any location besides the usage data (last values) and the report. Therefore, it needs the usage data (last values) for storing the required information.
Using this report for a checkpoint would always use the latest execution (usage data/last values) to find the required information needed to run the report from scratch.
Example
The following parameter was applied when preparing the checkpoint within the Lasernet Archive for the report Cust account statement:
When running the Test for this checkpoint, the system lets the user know the test is passed:
The test will show as failing if either the parameters are changed or another user is running the same checkpoint and they have other parameters set for the report (usage data/last values).
The usage data (last values) are saved per user. This can also cause different results when making a comparison.
Throw error
Throw error provides the option to simulate an exception/error. This is quite useful in relation to negative testing.
Location: Lasernet > Test and performance suite > Test > Tools > Throw error
368759@LAC365FO - SameLevel was producing just 1 and 1 record instead of fetching all. Layout generation had to be reviewed
For each table within the Query Wizard, it is possible to specify how data should be collected/fetched and added to the output (XML file).
Data is either “Nested” or added at same level as the parent data source (table).
In previous versions, using SameLevel only added one record from the parent data source/table and one record from the child data source/table.
In the following example the parent data source SalesTable was only added once.
In Lasernet FO Connector 6.19, parent data source is added once and child data sources are added as many times as records exist for the child data source.
Previous version of Lasernet FO Connector | Lasernet FO Connector 6.19 |
---|---|
Remember to enable Fetch/ Fetchmode if records for the child data source need to get sorted at same level as the parent data source.
In some situations, this requires the use of the Fetch/Fetch mode 1:1 for the Query within the Query Wizard.
It is not always enough having the records at Same Level as parent as the Layout is only the representation (XML file) and not the way the records should be fetched through the Query.
Add a comment
Please log in or register to submit a comment.