- An Attribute range could be updated upon creation of an object. For
example, when a Vendor object is created, its name is added to the "Provider"
Attribute range.
- When an Attribute is modified, a connection could occur. For example,
when the Provider Attribute field of a Purchase Order object is entered,
the P.O. could be connected to the Vendor object.
- Relationships could be given a lifecycle. For example, three relationships
could exist called "Proposed", "Planned" and "Complete." A Project object
could be connected to various Tasks with the Proposed relationship. When
the Task has been worked out, the two objects are connected with the
Planned relationship, which triggers a disconnect of the Proposed relationship.
Likewise, when the Complete connection is created, the Planned connection
is removed automatically.
- The changename event could trigger the name of a related object to
be changed. For example, if a Product name is changed, the Manual object
which will document it could be automatically changed, and notification
sent.
- The checkout event could trigger a program that would check to see
if the object is locked and prompt the user to lock if they want to check
the file back into the object.
- The checkin event could trigger the object to be unlocked.
- When objects are deleted, if files exist, they can programmatically
be copied to a specified location or externally be emailed to the System
Administrator.
- When one state is scheduled, each successive state could be scheduled
automatically by a specified offset value.
- Objects could be added or removed from sets when an event occurs.
For example, the set called "Pending Projects" could be modified as objects
reach the "Complete" state.
|