ITSM uses hidden data fields and tables for references
to other tables' records.
Workflow and display tables rely on these hidden data.
For valid ITSM data,
these references must be looked up and assigned values correctly.
|
|
This sheet shows the hidden reference fields in a table that associates support staff to support groups and companies.
Click the image for more details.
BMC Migrator, Panacea, Export/Import copy records as is -
with all columns' data unchanged.
The only way to automate these value changes, is either through staging forms and workflow,
or, through the BMC API. Both are expensive to develop, maintain, own.
With Meta-Update, your ARS Administrators - not programmers - script
reliable, auditable, repeatable, ARS Data operations, in record time, without
knowing the API or programming at all!
|
These tables and references are completely undocumented.
ITSM 7 is more rigid with respect to data validation than previous releases.
In previous ITSM releases, type-in fields specified an Asset's or Ticket Requester's
address. These were not validated and because of the human entries, much data had
errors.
To migrate this data, these values must be corrected.
Until now, this was very difficult to automate.
- Extracting trees of related Foundation data across
- Transferring and merging Foundation data across server environments
- Migrating data from earlier versions of ITSM
- Importing foundation data with your own spreadsheets
- Filling in the Data Management spreadsheets
- Extracting subset trees of foundation or other data
- Handling ITSM Customizations' data
- Running Foundation data consistency and comparison reports
|