| 1. | In most cases this is due to missing permissions. So please first check carefully if that user who is logged in and is missing an element has been granted roles and role extensions sufficient for this element, see section Workflow Start and Report or Special Widget and Table Editor. |
| 2. | If he or she should see the element or respective menu item judged from the configuration and the user's permissions, then an element can also be missing due to a non-matching configuration. |
Any non-matching configuration will not be signalled by an error message to the user. (This is a design decision.)
After having checked the permissions, make sure that
| • | in case of a workflow start: the Action Point Template referenced by name in the configuration does exist in the TrackingOne database and does belong to the same container as the user interface, |
| • | in case of a report call: the Report referenced by name in the configuration does exist in the TrackingOne database and does belong to the same container as the user interface, |
| • | in case of a table editor: the datasource configuration is correct, |
| • | in case of a special widget: the configured zul component (path / file name in textbox "Location") is available in the plug-in. |
This rule also applies to fields of a workflow start: Referenced but missing UDAs will be missing in the form.
| 3. | In case of a special widget, the missing can also be due to an intended restriction or additional authorisation check performed by the special widget's implementation (plug-in) or an error thrown on initialisation of the user interface. Please refer to the documentation delivered along with the relevant plug-in. |
Only if no clarification can be achieved this way, then it can be assumed that there is a bug.
|