Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

If you have GEODI Pro module, you can prepare and present 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 Settings/Reports or %appdata%App/Geodi/Settings/Reports .



What can be done with jSettings definition files

Customizations can be made by dropping a jSettings file next to all report types. Report display name, icon, working condition can be specified. The query can be changed.

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 field.

MyReport.jSettings
{
    ID:"MyReport",
	DisplayName:"[$.en:My Report;tr:Benim Raporum]",
    __type: "Factory.ActionFactory:HTMLReporter",
	ActionTargets:"*",
	ConditionMacro:'c.HasPermission("DECE.SYSTEMMANAGER")',
}

Changing the Query

With jSettings file you can add to the query. The definition of "AndQuery" that you add under "GenericSettings" will be added to the query that was executed when the report was received.

MyReport.jSettings
{
    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"
		}
}
  • No labels