Notification boxes allow you to dynamically display information in different parts of the application.
Currently supported places are:
- Logo Box
Tooltips allow you to show additional data when a user moves a mouse cursor over a drop-down input field.
|Data Service Tooltip|
In This Chapter
In this example the user can see a company logo and a phone line he is currently assigned to.
The user sees a stop-watch after starting a sequential workflow. He can pause/resume the stop-watch by pressing the action buttons for the current screen.
In this case the notification box is being refreshed every second so we could calculate how many seconds passed since starting the workflow (this information is written in a database so every time the logo refreshes we load the data, calculate the time and display it).
This tooltip will appear when the user moves over a lookup field in the UI:
Creating a Notification Box
In order to define content for the notification box you need two simple things:
- a Data Structure for data for the box
- a Transformation that will generate the content
1. Model–Notification Box
First you need to create a Notification Box element in User Interface > Notification Boxes:
You can specify the following attributes:
Type of the notification box. The only option is Logo. Future releases may support other notification box placements.
|RefreshInterval||The Number of seconds to wait before refreshing the box. When in the ORIGAM GUI, it will refresh the content after this interval.|
Now you can specify a tooltip element under the notification box by right-clicking on the notification box element and selecting New > Data Service Tooltip.
You can specify the following attributes:
The Name of the feature (or more, semicolon separated). When the feature is on, this tooltip be displayed. Otherwise the system will try another tooltip.
The Name of the application role (or more, semicolon separated). When the user is assigned to the role, this tooltip will be evaluated to be displayed. Otherwise the system will try another tooltip.
|Level||A sort order in which the system will evaluate possible lookup (beginning from the smallest).|
|TooltipDataStructure||A data structure for that will be a data source for the transformation.|
|TooltipLoadMethod||A method (typically a filter set) that will limit the data.|
|TooltipTransformation||A transformation that will generate data for the tooltip.|
The transformation for a tooltip needs to return a special structure for rendering rich formatted data.
Tooltip is the root element of the tooltip information.
|title||If you want the tooltip to be docked in a sidebar (for record level tooltips) you can specify a title that will be displayed in the header of the section.|
Cell defines a section inside the tooltip. A tooltip can contain one or more cells. Cells are of different types.
Type of the cell. Possible values are:
|height||Number of rows|
|width||Number of columns|
|verticalGap||Gap between columns|
|color||Background color of the cell|
|src||Url pointing to the image location in case that |
- HTML markup if
In case you need to put data into tabular format, you can create
<row> elements. The cell
type needs to be
Each grid row can be split into cells defined by the
Width of the column in pixels.
|percentWidth||Width of the column in percents.|
- HTML markup
ORIGAM supports a small subset of HTML. The following HTML tags are supported:
|Anchor tag||The |
|Bold tag||The |
|Break tag||The |
|Font tag||The |
|Image tag||The |
ORIGAM displays media embedded in a text field at full size. To specify the dimensions of the media you are embedding, use the
In general, an image embedded in a text field appears on the line following the
|Italic tag||The |
|List item tag||The |
|Paragraph tag||The |
|Text format tag|
|Underline tag||The |
ORIGAM supports the following HTML entities:
|<||< (less than)|
|>||> (greater than)|
|"||" (double quotes)|
|'||' (apostrophe, single quote)|
Links To Menu
You can create a link to execute your ORIGAM application menu items more easily. To do this you haver to make use of lookups which have existing menu bindings already. All you need to know is a lookup id and the value. The system will automatically launch the correct menu item when user clicks on the link.
In reality you would craft the following part of your transformation: