If you have GEODI Pro module, you can prepare and present It is possible to prepare custom reports in HTML, Text, Excel, Zip , CSV formats, and submit the reports in Text format as XML / JSON.
Even if reports use different definition languages and environments, they all have Macro and Localize support.
It can be accessed from the Export menu of the GEODI Pro module. E-mail content definitions in the notification mechanism are also prepared with reports.
You can use your report definitions by copying them to the appropriate folder under or CSV formats with GEODI.
You will need a GEODI Pro license for reporting.
Reports have Macro and Localization support.
A Notification E-mail Body definitions are also a report. You may utilize reporting feature in many places.
Reports need a jSettings and other file depending on the type. The settings must reside in Settings/Reports or %appdata%App/Geodi/Settings/Reports.
Child pages (Children Display) |
---|
What can be done with jSettings definition files
...
Report jSettings
Report display name, icon, working condition can be specified. The query can be changed. Table of Contents
Conditionally Displaying
Using the macro in the ConditionMacro field in the jSettings definition file, the plug-in can be installed when the desired conditions are met. The project name can be entered in the ActionTargets fieldConditionMacro defines the report’s visibility. If the report is specific to a WorkSpace use ActionTarget. The MAcro page may have more samples.
Code Block | ||||
---|---|---|---|---|
| ||||
{ ID:"MyReport", DisplayName:"[$.en:My Report;tr:Benim Raporum]", __type: "Factory.ActionFactory:HTMLReporter", ActionTargets:"*", ConditionMacro:'c.HasPermission("DECE.SYSTEMMANAGER")', } |
Changing the Query
...
Pre Query
If your report should only contain PDF files then "AndQuery in GenericSettings" will limit the report rows. The following sample limits report to erroneous files only.
Code Block | ||||
---|---|---|---|---|
| ||||
{
ID:"MyReport",
DisplayName:"[$.en:My Report;tr:Benim Raporum]",
IconName:"Layer/newspaper",
__type: "Factory.ActionFactory:HTMLReporter",
ActionTargets:"*",
ConditionMacro:'c.HasPermission("DECE.SYSTEMMANAGER")',
GenericSettings: {
"AndQuery": " status:HasCanError"
}
} |
Each Row is a Content
By default, each row in a GEODI report is a GeodEntry, which is a word discovered. Every date or IBAN discovered will be a row in the report. With the following settings, each row will be content.
Code Block |
---|
{ .. GenericSettings: { "OneSummaryPerRecord":true } } |
Init
Runs before the report. The following samples how to change data objects so that each row will be a layer. You may try different distinct criteria and look at other methods of the context object.
Code Block |
---|
{ .. "Init":['=c.Data=c.Distinct(c.Data,"=string.Concat(context.Data.OutputGeodiContent.SystemContentID,context.Data.RecognizerBackRef.Recognizer.DisplayName )")'] } |