... | ... | @@ -29,7 +29,7 @@ Custom Forms and Controls: |
|
|
* [My custom form does not work](#my-custom-form-does-not-work)
|
|
|
* [How to create a UB enum control](#how-to-create-a-ub-enum-control)
|
|
|
|
|
|
Reports
|
|
|
Reports:
|
|
|
* [Handle HTML report `onclick` event](#handle-html-report-onclick-event)
|
|
|
|
|
|
# Shell / Main Window
|
... | ... | @@ -518,9 +518,9 @@ Notice the `UB.i18n('bpm_ProcessDefinition.engineType')` syntax. That is a shor |
|
|
# Reports
|
|
|
|
|
|
## Handle HTML report onclick event
|
|
|
Starting from @unitybase/ubs>=4.1.19 report developer can define a `onclick` event for a `<a>` attributes. This feature is useful to open a form/grid/other report. There is some restriction for such cases:
|
|
|
- applicable only for HTML report
|
|
|
- `onclick` event can be defined only for `<a href="#" onclick="...">` html element - in all other html elements report editor/viewer will remove a `onclick` for security reason
|
|
|
Starting from @unitybase/ubs>=4.1.19 report developer can define `onclick` event for `<a>` attributes. This feature is useful to open a form/grid/other report. There are some restrictions for such cases:
|
|
|
- applicable for HTML report only
|
|
|
- `onclick` event can be defined for `<a href="#" onclick="...">` html element only - for all other html elements report editor/viewer will remove `onclick` for security reason
|
|
|
- report viewer display a HTML report in iFrame, so to call something from `adminUI` API `window.parent.yourFunction` syntax must be used
|
|
|
- because of iFrame, `event` parameter for `onclick` do not passed ho handler, so all function parameters must be in-lined into HTML template
|
|
|
|
... | ... | |