|
Obviously, many components are linked in some
way. Stages and Actions use Forms, for example. One very neat
addition to the user interface is a ‘Go
to’ menu item on the context menu. This allows
you to jump from one component to another. In other
components there are sub-items in the Explorer bar that lists
the instances where this item is used.
|
|
|
Go to menus exist for the following
items:
|
|
Action => Form used in the
Action
|
|
|
Linked Process Stage
=> Linked Processes in a sub-
menu
|
|
|
Sub-Process Stage => Sub-
Process
|
|
|
Linked Process => Parent Processes
in a sub-menu
|
Ones we would like to see
added:
| Flagged
Action
Stage
|
=> Flag for
Action
=> Forms used
in Stage
|
|
|
Sub-Item references exist for the following
items:
|
|
Role => Used
by Admin Forms
|
|
|
Process => Used by Process
(‘linked to’)
|
|
|
Sub-Process => Used by
Processes
|
|
|
Form Segment => Used by Forms (not
in referenced libraries)
|
Ones we would like to see
added:
| Flag
Visual Script
Connector
Business
Object
|
=> Used in Visual
Script
=> Used in Visual
Script
=> Used in Business
Object
=> Used on Forms
=> Used in
Field
|
|
There may well be others we have not discovered,
as they only appear when relevant.
|
|
|
|
It is not immediately obvious, but as you open
new components, the old ones are not closed. This means you
can easily switch back and forth between two or more
components. This is a great time saver for most developers.
Notice that unsaved components are marked with an
asterisk.
|
|
|
|
One potential problem, of course, is leaving too
many windows open. Fortunately you can right-click on a tab,
and not only can you close the tab, you can close all tabs
but the current one. We use this a lot, and we are sure it
will become very popular.
|
|
|
|
|
|
|
|
1. Designer User Interface
