Enhancing Harvest Forms
By embedding the
Trilogy Scripting Client
in a Harvest Custom Form,
the form can now launch and exchange data with jobs on remote servers. It can
do this whenever the form is created, displayed or amended. This powerful
feature allows Harvest Forms to be much more tightly integrated with external
systems in your IT infrastructure.
You can use this technique to disable form components to users outside of
a specific user group, to populate form data from external systems or to
create or amend records in external systems on request from the form.
Example
Bill is a long-suffering Harvest Administrator. Internal Audit are insisting
that packages should not reach the production environment unless a change
record has been raised in the company's change management system "Antidote".
Because Harvest and Antidote are not integrated, there is no mechanism to
enforce this.
There is already a custom form attached to each change package and the users
do not want that altered. Instead, they want to be able to add a new Harvest
"change" form to packages that are about to reach production. They want the
act of simply adding this new change form to the package to automatically
raise the change record in Antidote and for the allocated change number (and
other details) to be inserted on the Harvest Change Form.
Fortunately, Bill's site uses Trilogy. He simply uses the Trilogy
Scripting Client to run a job on the Antidote server when the Harvest
Change Form is created. Now, the Antidote change record can be created
automatically and the details populated into the Harvest Form as soon as the
form is created. Changes to the form contents in Harvest can be
automatically reflected in Antidote and vice-versa.
Now, the users can raise and view change records within Harvest without having to launch Antidote or attempt to keep the two systems in sync manually.
|
|
 |
|
