eSignature Report
This program lets you generate a report of audit log information relating to transactions that form part of the Electronic Signatures system.
Exploring
You can configure the Electronic Signatures system to maintain a detailed transaction log for auditing purposes (which can be archived for later retrieval).
A computer-generated time-stamp records the date and time of operator entry (including creation, modification, or deletion of records). This lets you generate a secure audit trail of completed transactions, indicating who performed a transaction and when it occurred.
Functionality:
-
The eSignature Query program provides an audit log of information relating to transactions controlled by eSignatures.
-
The eSignature Report program lets you generate a report of audit log information relating to transactions requiring eSignatures.
-
The eSignature Purge program lets you remove audit log entries held on file (based on the age of the entries) to reduce the number of entries in the log table (the table can consume excessive disk space after you have used the Electronic Signatures system for some time).
This purge system is controlled using the Global Configuration options where you can enable or disable purging and maintain run time selections.
This program is accessed from various locations in SYSPRO:
-
Program List > Administration > Electronic Signatures
Electronic Signatures (or eSignatures) let you increase control over your system changes by providing security access, transaction logging and event triggering.
This is achieved through the authentication and tracking of system activities against key business processes and sensitive data.
Starting
You restrict operator access to activities within a program using the Operator Maintenance program.
Controls whether an operator can create or maintain a report form.
Controls whether an operator can create or maintain report themes.
Controls whether an operator can purge archived SRS reports.
This activity, together with the activity SRS View all archived items, controls whether an operator can view archived reports.
-
If neither of these two activities is enabled, then the operator can only view archived reports that they have created.
-
If this activity is enabled and the activity SRS View all archived items is disabled, then the operator can only view archived reports generated by members of the operator group to which the operator belongs.
-
If this activity is disabled and the activity SRS View all archived items is enabled, then this activity has no effect and the operator can view all archived reports.
Controls whether an operator can view archived reports, regardless of whether the SRS View operator group archived items activity is enabled.
Controls whether an operator can create, edit and delete report schedules.
Controls whether an operator can change the priority of reports in the queue (server-side printing).
Controls whether an operator can delete a report in the report queue (server-side printing).
Only reports run by the logged in operator can be deleted.
Controls whether an operator can view the reports of all operators, in the report queue of a company (server-side printing).
Controls whether an operator can purge reports from the report queue of a company (server-side printing).
This enables the Purge Manager button on the report queue toolbar, from where an operator can purge reports by date, operator or report status.
You can restrict operator access to programs by assigning them to groups and applying access control against the group (configured using the Operator Groups program).
-
The date printed in the footer of each report refers to the system date when the report was generated (i.e. the company or temporary company date is ignored). In a client/server environment, the client system date is used.
Solving
This message appears when you can't connect to an instance of the SQL Server Database Engine on a single server. There could be a number of reasons for this:
- Incorrect SQL server name
- Incorrect default settings
- Incorrect firewall settings
- The SQL Server Database Engine does not have permission to allow remote connections
Ensure that your SQL Server name is configured to match the name of the server instance under the Object Explorer pane of Microsoft SQL Server Management Studio.
- Press the Win+R keys to launch the Run dialog.
- Type services.msc.
-
Select OK.
This launches the Services window.
- In the right-hand pane, select the SQL Server (MSSQLSERVER) service from the list (MSSQLSERVER being the name of the SQL Server instance).
- Right-click the service and ensure that Start has been selected. The option won't be available if already selected.
To run Services, you need to run this program as an Administrator.
-
Launch Microsoft SQL Server Configuration Manager.
Select Yes when prompted with the User Account Control window. This opens the Microsoft SQL Server Configuration Manager window.
- In the left-hand pane, select the SQL Native Client 11.0 Configuration (32bit) drop-down.
- Select Client Protocols from the dropdown.
-
Right-click the TCP/IP option and click Enable.
If already selected, the status of this option displays Enabled.
-
Select Properties for the TCP/IP option.
-
Change the value in the Default Port field to 1433.
-
Select OK.
SQL Server instances use port 1433 by default. Ensure that the Windows Firewall exception on the server for TCP ports 1433 is added so that SQL Server will run.
- Open Control Panel.
- Select Windows Defender Firewall.
-
Select Allow an app or feature through Windows Defender Firewall.
This launches the Allowed apps window.
- From the Monitoring drop-down, select Firewall.
- Check the list for Microsoft SQL Server Management Studio. If it is not listed, select Allow another app.
- Navigate to the location where Microsoft SQL Server Management Studio is stored and select OK.
- Select OK to close the Allowed apps window.
This message appears when you try to print a report, but haven't yet configured a printer for SYSPRO Reporting Services.
You need to configure your printer requirements:
-
From the Print Setup screen (SYSPRO Ribbon bar > Setup > Print Setup) select the printer to which you want to print reports.
-
Optionally, specify any preferences.
-
Select Apply and exit.
The name of the selected printer is then displayed in the status bar next to the print icon.
The eSignature Report program lets you generate a report of audit log information relating to transactions requiring eSignatures:
-
Open the eSignature Report program (Program List > Administration > Electronic Signatures).
-
Indicate if you want to generate a Detail or Summary report at the Report type field.
-
(Optional) Indicate your criteria preferences for which you want to generate the report.
-
Transaction selection
-
Transaction date selection
-
Transaction time selection
-
Operator selection
-
Program selection
-
Key selection
-
Variable selection
-
-
(Optional) Use the Include options to define which transaction statuses you want to include in the report.
-
(Optional) Define any additional report options you require within the Output Options pane.
-
Select the Process function.
-
Exit the eSignature Report program.
Using this lets you produce a report of the audit entries displayed in the eSignature Query program according specific report criteria and report options.
You would typically follow this procedure to generate a more detailed log per transaction, apart from the audit log which is generated by default when you set a transaction's access control to eSignatures or Log only.
In addition, you can add variables to provide insight into transactions performed or initiated by your SYSPRO operators:
-
Load the Electronic Signature Transaction Setup program:
-
Open the Electronic Signature Configuration Setup program (Program List > Administration > Electronic Signatures).
-
Select the Maintain hyperlink (in the Transactions column) against the configuration level for which you want to define conditions. This loads the Electronic Signature Transaction Setup program.
This only applies if the Transaction Type for the configuration is defined as Define by Transaction.
-
-
Select the Edit hyperlink against the relevant transaction within the Transactions list view. Alternatively, select the Add condition hyperlink to add an additional condition. This enables the Configure pane.
-
Define the Access level as eSignature or Log only.
-
Enable the Detail log required option under the Logging and trigger options section.
-
Optionally select the Configure details hyperlink to load the Configure Detail Log window:
-
Indicate the variables that you want to include in the detailed log for the transaction by using the checkbox within the Select column.
For example:
You may want to know the name of the supplier and banking details associated with the supplier that was added by an operator for the AP Supplier added transaction.
You'd therefore add the %Key, %Bank, %BankAccount and %BankBranch variables.
Adding a large number of variables to the detail log can increase the size of the audit log table. Therefore, you should consider only including the required variables.
-
Select Ok to save your selections.
-
-
Select the Save function of the Electronic Signature Transaction Setup program to save your condition's configuration.
-
Close the Electronic Signature Transaction Setup program.
-
Exit the Electronic Signature Configuration Setup program and restart SYSPRO for your changes to take effect.
You can now view the audit logs for eSignature transactions using the eSignature Query program (Program List > Administration > Electronic Signatures).
To view the audit log of eSignature transactions processed, proceed as follows:
-
Open the eSignature Query program (Program List > Administration > Electronic Signatures).
-
Indicate the relevant Time filter.
-
Enable the Show detail option from the toolbar.
-
Optionally define any criteria you require within the Filter Options pane and select the Apply Custom Filter function.
-
Select the Refresh View function.
After defining your preferences for purging log records, you can use the eSignature Purge program to remove audit log entries held on file, based on the age of the entries:
-
Open the Electronic Signature Configuration Setup program (Program List > Administration > Electronic Signatures).
-
Select the Global Configuration function to load the Global Configuration window.
-
From the Purge options section, select the Allow purge option to enable purging audit logs for eSignatures.
-
Optionally enable the Allow run time selection option so that you can indicate the relevant number of months or years against the Purge log records older than drop-down.
-
Select the Save function.
You are returned to the Electronic Signature Configuration Setup program.
-
Exit the Electronic Signature Configuration Setup program and restart SYSPRO for your changes to take effect.
-
-
Open the eSignature Purge program (Program List > Administration > Electronic Signatures).
-
At the Purge field, indicate if you want to remove all audit log information or only the details log.
-
Use the slider to indicate the Months to retain records.
-
Select the Start purge function and accept the confirmation message that is displayed.
The program automatically closes and an informational message is displayed indicating how many records were removed.
-
This helps reduce the number of entries in the AdmSignatureLog and AdmSignatureLogDet tables as the number of entries can grow substantially after you have used the Electronic Signatures system for some time.
Using
The following process outlines how to implement the Electronic Signatures system for a single company. However, this is only a basic guide and you can configure the system differently according to your requirements:
-
Enable the Electronic Signatures system:
-
Open the Electronic Signature Configuration Setup program (Program List > Administration > Electronic Signatures).
-
Select the Global Configuration function to launch the Global Configuration window.
-
Enable the Electronic signatures required option.
-
(Optional) Disable the Secure by default option to ensure that any new eSignature transactions added to the system are automatically defined as Allowed by default.
If you leave this option as enabled, then the access control of all new eSignature transactions added to the system are automatically set to Denied by default.
-
At the Authentication by field, indicate which password must be used for the authentication process when you configure eSignatures that require a password to be entered before certain transactions can be processed.
-
At the Configuration level field, indicate the level at which you want to configure eSignatures:
-
System-wide (if you want to apply access control and any advanced settings to all operators and groups across the system (i.e. in all companies)
-
Company, group, operator or role (if you want to configure eSignatures for a specific company, group, operator or role)
-
-
(Optional) Enable the Specify company for operator/group/role option if you want to configure Electronic Signatures separately for different companies. Otherwise the configurations defined for each group will apply to those groups in all companies.
-
(Optional) Indicate your preferences for purging log records against the Purge options.
-
Select the Save function to return to the Electronic Signature Configuration Setup program.
-
Exit the Electronic Signature Configuration Setup program and restart SYSPRO for your changes to take effect.
-
-
Define your configuration level(s) at Operator, Group, Company or Role level:
- Open the Electronic Signature Configuration Setup program (Program List > Administration > Electronic Signatures).
-
Select the Add a new configuration toolbar function.
A new blank record is added to the list view.
-
Indicate the Security level you require as Company, Operator, Group or Role.
-
Depending on your selection against the Security level, indicate the associated code within the following columns:
-
Company
-
Operator
-
Operator Group
-
Role
-
-
Indicate the access control you require for this configuration level within the Transaction type column:
-
eSignature
-
Allowed
-
Denied
-
Log only
-
Excluded
-
Define by transaction
-
-
Select the Save function.
-
(Optional) If you defined the Transaction type as Define by transaction:
-
Select the Maintain hyperlink within the Transactions column.
This loads the Electronic Signature Transaction Setup program from where you can define the transactions associated with the configuration, as well as the trigger and audit log details.
-
Locate the transaction you want to configure the eSignature against and select one of the following depending on your requirements:
-
To maintain the existing condition for the transaction:
Select the Edit hyperlink within the Edit column of the Transactions list view.
-
To add an additional condition to the transaction:
Select the Add condition hyperlink within the Add condition column of the Transactions list view.
-
-
Within Configure pane, define the condition as you require it, along with the effective period, logging and trigger requirements.
-
Select the Save function to return to the Electronic Signature Configuration Setup program.
-
-
Exit the Electronic Signature Configuration Setup program and restart SYSPRO for your changes to take effect.
-
Once the Electronic Signatures system is in place and operators have begun processing transactions that form part of your configuration level(s), you can view the audit log:
-
Open the eSignature Query program (Program List > Administration > Electronic Signatures).
-
Indicate the relevant Time filter.
-
Enable the Show detail option from the toolbar.
-
Optionally define any criteria you require within the Filter Options pane and select the Apply Custom Filter function.
-
Select the Refresh View function.
-
-
Generate a report of audit log information relating to transactions that form part of the Electronic Signatures system:
-
Open the eSignature Report program (Program List > Administration > Electronic Signatures).
-
Indicate if you want to generate a Detail or Summary report at the Report type field.
-
(Optional) Indicate your criteria preferences for which you want to generate the report.
-
Transaction selection
-
Transaction date selection
-
Transaction time selection
-
Operator selection
-
Program selection
-
Key selection
-
Variable selection
-
-
(Optional) Use the Include options to define which transaction statuses you want to include in the report.
-
(Optional) Define any additional report options you require within the Output Options pane.
-
Select the Process function.
-
Exit the eSignature Report program.
-
-
If required, you can purge the audit log entries held on file to reduce the size of the log files:
-
Open the Electronic Signature Configuration Setup program (Program List > Administration > Electronic Signatures).
-
Select the Global Configuration function to load the Global Configuration window.
-
From the Purge options section, select the Allow purge option to enable purging audit logs for eSignatures.
-
Optionally enable the Allow run time selection option so that you can indicate the relevant number of months or years against the Purge log records older than drop-down.
-
Select the Save function.
You are returned to the Electronic Signature Configuration Setup program.
-
Exit the Electronic Signature Configuration Setup program and restart SYSPRO for your changes to take effect.
-
-
Open the eSignature Purge program (Program List > Administration > Electronic Signatures).
-
At the Purge field, indicate if you want to remove all audit log information or only the details log.
-
Use the slider to indicate the Months to retain records.
-
Select the Start purge function and accept the confirmation message that is displayed.
The program automatically closes and an informational message is displayed indicating how many records were removed.
-
-
Within the Electronic Signatures system, you can define access control either at configuration or transaction level. Therefore, the following table summarizes the access control levels available.
-
The access levels you define against an individual operator take precedence over the access levels defined at company level.
-
Each transaction condition can have a different access control level.
Similarly, each operator group can be assigned a different access level.
-
If you select the eSignature or All Secured by eSignature access level, then a password must be defined against each operator who has access to the transaction.
This is either an operator password or an alternate password, depending on your selection at the Authentication by option within the Global Configurations.
-
Where transactions are configured against a specific operator, the access level defined against the operator applies (except if this access level is set to Excluded from definition), regardless of the configuration against any groups to which the operator belongs.
If the access method for a transaction configured against an operator is defined as Excluded from definition, then the access level defined against the operator's group(s) applies.
If the access level against the group(s) is also set to Excluded from definition, then the access level defined against the company applies.
Access Control | Impact |
---|---|
eSignature (Configuration level) or eSignature (Transaction level) |
This sets the current transaction or configuration level to be subject to the Electronic Signatures system. Configuration level
Transactions are subject to Electronic Signatures and therefore operators must enter a password before a transaction can be processed. Transaction level
The transaction is subject to Electronic Signatures and you therefore need to indicate one of the following against the transaction:
Auditing capabilities
An audit log is generated for each transaction when this access control is defined at either level. |
Allowed (Configuration level) or Allowed (Transaction level) |
When selected at either Configuration or Transaction level: Operators can process transactions without having to enter a password (i.e. transactions are ignored by the Electronic Signatures system). Auditing capabilities
No audit log is generated for the transaction. |
Denied (Configuration level) or Denied (Transaction level) |
When selected at either Configuration or Transaction level: Operators are prevented from processing any SYSPRO transaction that forms part of the Electronic Signatures system. Auditing capabilities
No audit log is generated for the transaction. |
Log Only (Configuration level) or Log only (Transaction level) |
When selected at either Configuration or Transaction level: Operators can process transactions, but an audit log is generated for every transaction. In other words, this is the same access control as Allowed, except an audit log is generated. Auditing capabilities
An audit log is generated for each transaction when this access control is defined at either level. |
Excluded (Configuration level) or Excluded from definition (Transaction level) |
When selected at either Configuration or Transaction level: Transactions are ignored by the Electronic Signatures system. You would typically select this option at Configuration level if you wanted to configure only a few transactions for Electronic Signatures. Configuration level considerations
The access control to all transactions are set to Excluded. You can then select the Define by Transaction option to configure the transactions you want to secure individually. If you select this option but do not configure any transactions individually, then this is equivalent to selecting the Allowed option for the selected configuration level. Therefore, the purpose of this option at Configuration level is to cascade the access level up to the next level defined, except when using role-based eSignature definitions, as there are no higher-up levels. For example: If the transaction is excluded for an operator, then the access level defined against the group applies. If this is defined as Excluded from definition, then the access level defined against the company applies. This access control is an advanced option and should therefore only be used with sophisticated conditional logic. Auditing capabilities
No audit log is generated for the transaction. |
Define by Transaction (Configuration level) |
When selected at Configuration level: This lets you configure each SYSPRO transaction that forms part of the Electronic Signatures system individually. You can then select the Edit or Add condition option from the Transactions list view of the Electronic Signature Transaction Setup program to define additional configuration options for each transaction. In addition, you can deselect individual transactions in the Transactions list view, thereby setting that transaction to Denied for the selected configuration level. |
The following indicates the different statuses which may apply at some point to each transaction that forms part of the Electronic Signatures system.
You can view the current status of an eSignature transaction using the eSignature Query program or the eSignature Report.
Status | Description |
---|---|
0 - Authorized but not yet complete Successfully passed Electronic Signature verification (but transaction not yet completed) |
This status indicates that the transaction has been authorized but not yet completed. For example: If the AP Month-end performed transaction is configured within the Electronic Signatures system to require a password before proceeding, and an operator enters the correct password but has not yet completed the full process, then the transaction resides in this status until complete. |
1 - Function canceled Operator canceled from Electronic Signature function |
This status indicates that the operator canceled the particular function before the eSignature verification could complete. For example: The Access Control against the against the AP Delete payment run transaction was defined as Allowed, but the operator canceled the process while performing a payment run. |
2 - Password verification failed Failed to enter password x number of times |
This status indicates that the password verification failed due to the operator entering the incorrect password x number of times. |
3 - Denied access Operator was denied access to the function |
This status indicates that the operator was denied access to the particular function or transaction. For example: The operator couldn't perform the month-end as the Access control defined against the CB Month-end performed transaction was defined as Denied. |
4 - Transaction canceled Operator canceled the transaction |
This status indicates that the operator canceled the transaction before it completed. |
Transaction was authorized completed successfully |
This status indicates that the transaction has been successfully authorized and completed. For example: If the Access control against the AP Post invoice transaction for a particular operator is defined as Allowed and that operator then processes an invoice, the transaction is successfully authorized and completed. |
Referencing
Field | Description |
---|---|
Report type |
Summary
This lets you print a report listing a summary of logged information for all transactions requiring Electronic Signatures. Detail
This lets you generate a detailed audit log report containing additional information relating to all variables applicable to each transaction logged. |
Transaction selection |
Indicate the transaction id(s) for which you want to generate the report. |
Transaction date selection |
Indicate the transaction date(s) for which you want to generate the report. |
Transaction time selection |
Indicate the transaction time(s) for which you want to generate the report. |
Operator selection |
Indicate the operator(s) for which you want to generate the report. |
Program selection |
Indicate the program code(s) for which you want to generate the report. |
Key selection |
Indicate the key(s) for which you want to generate the report. This is the key for the table in which the transaction occurred (e.g. supplier code, stock code, customer code, etc.). |
Variable selection |
Indicate the transaction variables (as defined within the Electronic Signature Configuration Setup program) for which you want to generate the report. |
Include |
This lets you indicate the eSignature statuses according to which you want to generate your report. This is based on the Status description associated with each particular transaction as displayed in the eSignature Query program. Transaction completed successfully
This includes all transactions that have been authorized and completed successfully (i.e. transactions with a current status of ).Transaction authorized but incomplete
This includes all transactions that have been authorized but not yet completed (i.e. transactions with a current status of 0 - Authorized but not yet complete). Operator canceled from function
This includes all transactions where the operator canceled the particular function before the eSignature verification could complete (i.e. transactions with a current status of 1 - Function canceled). Operator denied access to function
This includes all transactions where the operator was denied access to a particular function (i.e. transactions with a current status of 3 - Denied access). |
Select a standard or user-defined theme you want to apply to the report.
You can't define a report theme if the Disable theme selection option is ticked ().
This enables the Email Options function which lets you define the parameters required for emailing the report.
The Office Automation and Messaging module is not required for emailing documents from SYSPRO Reporting Services.
Selecting this option enables the Export Options function which lets you output the report to a specific format and save it to a specific location.
You can also export the report from the Report Preview screen.
Export formats can be page-based and record-based. Page-based formats typically preserve these properties as closely as possible, while record-based formats prioritize data rather than layout and formatting. Some record-based formats are only data-exchange formats (e.g. Adobe Acrobat PDF).
Depending on the format you select, the layout (e.g. object position, object size and relationships between these attributes and other objects) and formatting (e.g. font style, text color, text alignment, background color, etc) may not be perfectly preserved.
This exports (saves) your report with the current data without modifying the original report.
[Page-based]. The exported documents are intended for printing and redistribution. Acrobat format will export both layout and formatting in a manner that is consistent with how the report looks on the Preview tab.
Acrobat format embeds the TrueType fonts that appear in the document. (Non-TrueType fonts are not supported.)
This export format does not support Microsoft font-linking technology, which is used to provide support for some extended character sets such as Chinese HKCS. Therefore, the fonts used in the report must contain all of the required glyphs.
The following URL types are supported for hyperlinks: http:, https: and mailto:.
[Page-based]. You would typically select this if you wanted to create a report that wanted to publish on a website or email to a recipient. An HTML page containing the entire report is generated in the directory you specify. Once published or emailed, the report can be viewed without requiring SYSPRO programs.
This format preserves the layout and formatting of the report by using DHTML.
All the images in the report are saved externally and a hyperlink is inserted in the exported HTML output. Therefore, this export format can generate more than one file in the output.
[Page-based]. This converts your report contents into Excel cells on a page-by-page basis. Contents from multiple pages are exported to the same Excel worksheet.
The export program creates multiple worksheets to accommodate data if a worksheet becomes full and there is more data to export.
If a report object covers more than one cell, then the export program merges cells to represent a report object.
Microsoft Excel has a limit of 256 columns in a worksheet, so any report object (or part thereof) that is added to cells beyond 256 columns is not exported.
This export format retains most of the formatting, but it doesn't export line and box objects from your report.
The Export page header and page footers option lets you include the header and page footer information when exporting the report. Options include: None, Once per report or On each page.
The exported file contains text and drawing objects to represent report objects. Individual objects are placed in text frames.
This format is intended for use in applications such as fill-out forms, where the space for entering text is reserved as empty text objects.
Almost all of the formatting is retained in this export format. However, text objects can't be placed outside the left edge of the page (e.g. if you have text objects in your report that are placed before the left edge of the printable area, they will be pushed right - most noticeable in reports with wide pages).
This exports the report to a plain text file. For client-side reporting, you can specify the characters per inch and number of lines per page.
This is the location (full path and file name) to which you want to save the report.
The file name can't contain characters that are reserved in XML (e.g. ' : & ' > <).
This lets you define parameters for printing the report to a specific printer or PDF printer.
You can define the default paper size to use for your specific reports using the Default printing paper size option ().
This displays the report on the screen after processing all output options selected.
This option is selected by default if the Report Preview option is enabled from the (SYSPRO Ribbon bar > Setup > Report Preview).
This option has no effect when using server side printing. Once the report is requested by the client, it is sent directly to the server for processing which enables the client to continue working or even to shut down. When a report has been processed, it must be opened from the SRS Report Queue.
Saves your selections for future runs of the report.
This field can be controlled using the Always archive report and Disable archive report options ().
Archiving reports lets you identify which reports were run, when they were run and by whom. This is also useful for customized SRS reports. In addition, reports are readily available for printing, reprinting or emailing.
This resets all the options on all the tab pages to the SYSPRO default selections.
This generates the report according to your selections.
At least one output method must be selected on the Output Options tab before you can select to process the report.
This exports the report to an Excel spreadsheet.
Option | Description |
---|---|
Export to Excel options | |
Constant column width |
This fixes the width for all exported columns. If selected, enter the required value into the Constant column width field. |
Column width based on objects in the |
Select the part of the report on which you want to base the column width. |
Export page header and page footers |
This lets you include the header and page footer information when exporting the report. Options include: None, Once per report or On each page. This effectively lets you include details of the operator who created the report. |
Create page breaks for each page |
This adds the page breaks as designed in Crystal Reports. Don't select this option to add page breaks automatically in Excel. |
Convert date values to string |
This keeps the date formatting of the report in Excel. |
Show gridlines |
This adds grid lines to the report in Excel. |
Page range |
Select the pages you want to export. |
Option | Description |
---|---|
Export to Excel options | |
Constant column width |
This fixes the width for all exported columns. If selected, enter the required value into the Constant column width field. |
Column width based on objects in the |
Select the part of the report on which you want to base the column width. |
Options |
|
Export object formatting |
This exports the report formatting to Excel (i.e. ensuring that the data types are maintained). |
Export images |
This exports images in the report to Excel. |
Use worksheet functions for summaries |
This converts report summaries to Excel functions (i.e. numbers with formulas). |
Maintain relative object position |
This keeps the objects in the report in the same position when exported to Excel. |
Maintain column alignment |
This keeps the alignment the same as the report. |
Export page header and footer |
This lets you include the header and page footer information when exporting the report. This effectively lets you include details of the operator who created the report. |
Simplify page headers |
This exports only the last row of the page header section. |
Show group outlines |
This adds the lines that separate the report groups in Excel. |
This exports the contents of the report as a text file. When you select this option, the report contents are displayed in a Notepad editor.
This applies a selection formula to the report to filter the data without re-running the report, making the report easier to read by only displaying certain records.
This option is not available for archived and scheduled reports.
Option | Description |
---|---|
Record |
Specify criteria for displaying records in the report. |
Group |
Specify criteria for displaying group data in the report. |
Saved Data |
This displays the report with the saved data. This applies to reports previously exported or reports which you designed and against which data was saved using the Save data report option. Any changes made to the database after the report is saved doesn't affect the report (i.e. the program does not refer to the database when generating the report). |
Clear all selection formulas |
This clears any previously specified selection formulas (using the Select Expert option) for the current run of the program. |
This queries the database to redisplay the report on the screen at the selected page.
This only applies when generating a report that extracts data directly from a database (i.e. not when using a business object to extract the data).
This exports the report (as well as sub-reports) to a comma-separated-values (CSV) file.
Each record in the file is typically a single line and each field in the record is delimited by a specific delimiter (e.g. a comma).
Option | Description |
---|---|
CSV export options |
|
Delimiter |
Indicate the character you want to use to wrap around each field in the record. This defaults to " (double quotes). |
Separator |
Indicate the character you want to use to separate the fields or columns in a record. This defaults to , (comma). |
Tab |
Select this to use a Tab as the delimiter for separating the fields in each record. When you select this option, the Separator field is disabled. |
Mode |
Standard mode
Indicates what to do with the page and group sections of the report when exported. Legacy mode
Exports the report to the file to resemble the rpt format of the report. |
Path |
Indicate the location to which you want to export the report. |
Report sections |
|
Report and page sections |
Select whether you want to write all report headers and footers and page headers and footers to the export file. |
Isolate report or page sections |
This writes all report headers and footers and page headers and footers to the export file, but isolates them in the file. This creates a bigger file which resembles the rpt version of the report where everything is more spaced out and easier to read. Otherwise the report and page headers and footers are included in each record of the file. |
Group sections |
|
Group sections |
Select whether you want to write all group headers and footers to the export file. |
Isolate group sections |
This writes all group headers and footers to the export file, but isolates them in the file. This creates a bigger file which resembles the rpt version of the report where everything is more spaced out and easier to read. Otherwise the group headers and footers are included in each record of the file. |
This exports the report to a specific format, location and enables you to specify the page ranges to export where applicable.
This saves the report to a specific location. This defaults to Crystal Reports (*.rpt).
When you export a single document, the default file name is created using the document type and the key field (e.g. customer number, invoice number, quotation number, purchase order number, etc). When you export a batch of documents, the last document number or key field is used as a reference in the file name.
This option lets you export reports individually (i.e. only the main report, or any of the sub-reports you are current displaying).
This lets you view the parameters and parameter values entered for the report using the Crystal Report Designer.
This displays the values of the primary key sequence used in grouped reports (e.g. Inventory Valuation) in a tree view.
Copyright © 2022 SYSPRO PTY Ltd.