The futUre Importance of GNOSIS Transactions
27 August 2003
Here are some of our reasons why we believe you need
to know about Gnosis Transactions.
Gnosis Transactions offer the capability for the database
transaction integrity to be synchronised with the business
transaction (process), resulting in
reduced business process error and
rework.
Gnosis Transactions, offer workflow capabilities such as
passing transactions from one user to another and multi-user
update, which enable
flexible business operations and greater business efficiency.
Gnosis Transactions offer the capability
to manage critical business data in one unit with significantly
reduced risk of error and timing issues. For example, multiple
product pricing changes, and associated marketing data are
managed as one Gnosis Transaction.
The Gnosis Architecture is in the database,
it does not add complexity, whereas other architectures are
outside of the database and require considerable additional
engineering to manage work-in-progress, ironically these systems
require additional databases to control workflow!.
Most systems today perform short transactions. What usually
happens is that short transactions are entered after the business
process is completed, because the business process may take
a while to assemble the appropriate data, ask the appropriate
questions and fill out the appropriate forms. For example,
recently one of our staff made an insurance claim for a stolen
car, but the forms filled out were not entered into the computer,
until all the required data had been assembled, which tool
over 24 hours. Unfortunately a short transaction enforces
integrity on the whole data set and thus will reject work
that is not fully correct and complete, so in the case of
the insurance claim the documents remained on paper in a desk
for 24 hours!.
With a Gnosis Transaction the documents could have been managed
on the computer as the information for the claim became available,
and not on paper, and the Gnosis Transaction could have guided
the integrity of the claim information, ensuring less error
and rework in this business process.
In most of today's database systems, the business integrity
processes are separate from the database integrity process,
and usually the database transaction integrity is made when
the business process is completed. This is exactly what happened
with the insurance claim made by one of our staff. Thus there
is a higher likelihood of business process error and rework.
Unfortunately today, in the prevalent architectures, we are
trying to build work flow systems outside the database, which
is resulting in technically highly complex systems. Gnosis
Transactions occur in the database and thus require significantly
less technical engineering.
|
