 |
| |
EVOLUTION |
| |
|
|
| |
The
model view |
| |
In Evolution, forms
are managed in data models.
The model view is used to display and work
with the forms and relationships in an easy
to understand overview.
|
|
| |
|
| |
Forms
editor |
| |
In the form editor you work efficiently
with fields. Evolution makes it easy to add
and remove fields and set common field attributes.
With Evolution you can change datatypes on
fields, for instance change a character field
to an integer, renumber field-ids and change
field-entry-mode (required to display-only).
All changes can be done both on new and on already
created forms, functionality and data is retained.
Evolution keeps track of and synchronizes changes
when a field is copied to other forms.
Permissions can be set on one or several fields
at the same time.
|
|
| |
|
| |
Synchronize |
| |
Evolution creates and updates
forms, fields and functionality on AR System
Servers through the AR API. Updated forms retain
existing layout, functionality and data.
Evolution also have functions to keep models
synchronized to several servers.
|
|
| |
| |
| |
Maintenance |
| |
Evolution can fetch
forms from a AR Server to generate a model,
after changes, it can be re-synchronized back
to the AR Server. The model view as well as
difference checking functions makes it easy
to detect and correct inconsistencies in your
applications.
Evolution permits re-modelling to change the
back-end datamodel. Traditionally, development
on the remedy platform demands strict discipline
by the developers to maintain naming conventions
and field-id numbering. With Evolution you have
full freedom to change field-ids whenever you
wish. Evolution also gives automatic support
for naming conventions.
|
|
|
| |
Field
groups |
| |
A unique function is "field
groups"; groups of fields defined on one
form and then being used on other forms.
One example of field groups;
The Contact Information form keeps information
on contact persons. In the form editor you can
define the field group "Contact" and
fields in the form may be added to the group.
The field group can then be used in other forms.
Fields will automatically be created, with the
same attributes and permissions. If the field
group is changed, for instance, if a field is
added, it will automatically be added wherever
the field group is being used. |
|
| |
| |
| |
| |
Relationships |
|
| |
The concept of relationship
management has been taken from traditional datamodelling.
Evolution has support for 0:n, 1:n and m:n-relationships.
Adding a relationship between two forms automatically
creates fields for foreign keys.
Evolution can also generate functionality for
the relationships to automatically maintain
normalization, referential integrity and ripple
between the forms. Evolution also can generate
gui-functionality for searching in all fields
mapped in the relationship, examples are given
in the demo movie "relationships and
workflow".
|
|
|
| |
Manage |
| |
Evolution has many functions
to make it easy to maintain a Remedy application.
One example is Fields/Permisisions, which presents
permissions on the fields in a grid view, creating
good overview as well as allowing changes.
Other examples include groups merge/split functionality,
conversion of local applications to deployable
(which creates and sets roles from existing
groups.
|
|
| |
| |
