andreysubbotin
commented
4 years ago Comments from Mario:
-
EditorPrintFormAction Constructor When using new EditorPrintFormAction(this, null) I have to pass in a null to express that I don’t want to define a output name. From an API usage perspective this is not very intuitive. Perhaps a builder would make sense here?
-
Connecting Button and EditorPrintFormAction Currently the glue code looks like this: Screen XML:
<button id="patientRecordBtn" caption="msg://patientRecord"/>Screen Controller:
@Inject protected Button patientRecordBtn; @Subscribe protected void onInit(InitEvent event) { patientRecordBtn.setAction(new EditorPrintFormAction(this, null)); }
natfirst
Description of the bug or enhancement
CUBA 7.0 introduced standard actions: http://cubadev:8181/manual/standard_actions.html
These actions can be simply added to a table by typing "type" attribute. Also Studio scans these actions and suggests them to user in a Screen Designer.
From first glance, at least TablePrintFormAction / ListPrintFormAction can work as a standard action.
Updates
Relates to #178. The
ExecutionHistoryAction,RunReportActionandListPrintFormActionare implemented as standard actions.ExecutionHistoryAction
ExecutionHistoryAction- standard action for displaying the report execution history. It should be defined on the screen that is associated withReport. It should be defined for aButtonor a list component (Table,DataGrid, etc.). To view the report execution history set app propertyreporting.executionHistory.enabled = true.Add
ExecutionHistoryActiontoButtonWhen the action is performed, a modal
ExecutionHistoryDialogwill open where reports related to the current screen will be displayed (to link the screen and the report, see the corresponding section below).ExecutionHistoryDialog
Execution Historybutton, the execution history for the selected reports will be displayed. If no reports have been selected, then a execution history will be displayed for all reports associated with the screen.ListPrintFormAction
ListPrintFormAction- for printing reports for a list of entity instances associated with a list component (Table,DataGrid, etc.). It should be defined for a list component in a screen XML descriptor. The action only selects reports having an external parameter of the Entity or the List of entities type and where the parameter entity type matches the entity type displayed by the list component. If only one report is available as a result of selection, it is invoked immediately. If several reports are available, their list is offered to the user for selection.When the action is performed, if no entities were selected from the list component, a confirmation window will be displayed.
After that, the modal
Run reportsdialog will open where reports related to the current screen will be displayed (to link the screen and the report, see the corresponding section below).Print reports dialog
RunReportAction
RunReportAction- standard action for displaying the list of all available reports. It should be defined on the screen that is associated withReport. It should be defined for aButtonor a list component (Table,DataGrid, etc.).Add
RunReportActiontoButtonWhen the action is performed, a modal
ReportRundialog will open where reports related to the current screen will be displayed (to link the screen and the report, see the corresponding section below).ReportRun dialog
How to link screen and report
To associate a screen with a report you need: 1) Open
Reporteditor 2) Go toRoles and Screenstab 3) Add a new screen to report.Test project
reports-standard-actions.zip
QA
1) Create
Customerentity 2) CreateReportforCustomerentity 3) AddCustomer.browsescreen to report