Move your mouse round the image for details:
Meta-Update allows you to load up ARS records from different forms and update or
create an entry in a target form using any of the above data.
You can also iterate through a query's results, or ASCII file's records,
building or updating an equal number of target forms.
Meta-Update can be used manually, on Unix or NT at the command
prompt, fired through workflow, or executed in a script.
Meta-Update allows you to load up ARS records from different forms
and update or create an entry in a target form using
any of the above data.
You can also iterate through a query's results, or ASCII file's records,
building or updating an equal number of target forms.
Meta-Update can be used manually, on Unix or NT at the command
prompt, fired through workflow, or executed in a script.
All required schema definitions are automatically loaded when
a Load is processed.
Schema definitions allow automatic type conversions and
checks.
For example it is possible to assign a character
string to an enumerated type if the string matches
the name of a value:
Status = "Assigned"
As many different ARS records from as many different forms as you want
can be loaded and tagged for use in assignments.
The keys for these records can come from any source: previously loaded
ARS records, program parameters, environment variables, constants, file
contents.
Schema definitions allow automatic type conversions and checks.
When a Query is being processed, one record at a time is loaded and can be referenced.
As many program parameters as allowed by the OS are accepted. These can be used in both
assignments and loads.
In assignments as literals:
Status = $001
In loads as keys:
Load = PplRequester, "SHR:People", $001
The keys for these records can come from any source: previously loaded
ARS records, program parameters, environment variables, constants, file
contents.
A Query can be done when creating or updating records.
Meta-Update will iterate through the results of the query and will
create one new target record, or update one and only one target
record, for every query result record.
The query record may be referenced in assignments, be the update record,
or, be referenced to query for and load the update record.
This is a simple approach to parent / child relationships.
The Remedy ARS server can be located on either UNIX or NT system, either the
same system as Meta-Update, or another system.
Meta-Update is itself available on either system.
Meta-Update can be incorporated into workflow to perform hard or impossible
to implement functions, reduce workflow complexity, reduce the need for hidden fields.
Meta-Update can be called from scripts which themselves can be incorporated into workflow.
Meta-Update can be also called from scripts which can implement "batch" updates.
Meta-Update is available for both NT and Unix Servers and can be run on the
server itself or on any other machine that can connect to the server.
Meta-Update can be incorporated into workflow to perform hard or impossible to implement functions,
to reduce workflow complexity, and to allow configurable changes to workflow.
Meta-Update can be called from scripts which themselves
can be incorporated into workflow.
Meta-Update can be also called from scripts which can implement "batch" updates.
Meta-Update uses the Software Tool House Meta-Layer over the Remedy API.
No direct database reads or updates are performed.
Because of the ARS API, the machine executing the update does not need to be same as the ARS server.
All ARS rights are adhered to. All Server workflow fires.
The target record can be a new record (submit) or an update (modify).
As the Remedy API is used, all workflow is fired, all field requirements are adhered to, and
normal ARS field security is checked.
Only those fields specified receive updates. All other fields retain their original or default values.
Attachments can be updated and can retain their original names.
If a Query is used, a target record is created for each record in the query result.
If updating, a further query is used to load the update record.
Meta-Update<'s script file is the key to the Meta-Layer's flexibility.
Load statements cause the retrieving and tagging of other records.
These records are retrieved through keys passed on the command line,
fields in ARS records already loaded, and environment variables.
These can then be referenced in the Remedy ARS assignments.
Assignment statements assign fields in the target schema.
A Query can be used to cause Meta-Update to loop and create many target records.
The set of fields assigned is used to update or create the target Remedy ARS record.
Load statements tell Meta-Update to load and identify other records for use in
assignment references or other load references.
The IDs of these records may be passed from the program parameters, environment
variables, file contents, or previously loaded records' data.
This provides for a conveniant method of updating target records.
The results of a query are loaded one at a time.
Each record returned in the query is used to create a new target record, is
the record to update, is used to query for a single record to update.
The query record may be referenced in assignments, more loads, and the query
for the update record.
The result of a query is that as many records as returned by the query are
updated or created.
This is a simple approach to parent / child relationships.
The target record can be a new record (submit) or an update (modify).
On an update, the record is read.
On both an update or create, only those fields specified receive updates.
All other fields retain their original or default values.
Attachments can be updated and can retain their original names.
Meta-Update can also be made to create as many records as returned by a query.
The record being updated is itself loaded through a query.
Click for a full-text, printer-friendly version.
|
