You can continue to use C APIs to customize your application, but C APIs are not enhanced to support new capabilities provided by Java APIs and REST APIs.
Imports the indicated structure definitions to the specified server. Use this function to copy structure definitions from one BMC Remedy AR System server to another (see ARExport).
BMC Remedy AR System administrator.
#include "ar.h" #include "arerrno.h" #include "arextern.h" #include "arstruct.h" int ARImport( ARControlStruct *control, ARStructItemList *structItems, char *importBuf, unsigned int importOption, char *objectModificationLogLabel, ARStatusList *status)
The control record for the operation. It contains information about the user requesting the operation, where that operation is to be performed, and which session is used to perform it. The user and server fields are required.
The runtime group specified in the control record does not affect import operations. Instead, that function uses the overlay group specified in the object property list in the imported object definition file. For information about runtime groups and the overlay group setting, see ARSetSessionConfiguration.
A list of zero or more structure items to import (identified by type and name). Specify
for this parameter to import all structures in the import buffer.
Form (includes all associated views) (
Active link (
Character menu (
Distributed mapping (
Form data (
You must specify
AR_STRUCT_ITEM_SCHEMA to import a form. The three partial form types defined in ar.h (
AR_STRUCT_ITEM_SCHEMA_MAIL) do not contain complete form definitions and are used only for caching purposes.
When you import an overlay that has inherited properties, those properties are inherited from the copy of the origin object that is on the server. If you import the origin object with the overlay, then the overlay will inherit properties from the imported object. If not, then the overlay will inherit properties from the object already on the server.
A buffer that contains the definition text for the items specified for the
structItems parameter. This buffer can contain other structure definitions, but the system imports only the specified items.
A value that indicates whether to replace objects being imported if they already exist and how to replace them. There are two sets of import options. Always set one of the basic options to indicate whether to replace objects. Set zero or more advanced options to further configure how
ARImport handles inconsistencies between the objects on the server and the object definitions in the import buffer.
Create a new objects and generate an error if an object already exists. (
Overwrite an existing object. (
Advanced options (add the values to enable more than one option):
Check for conflicting data types and report an error. (
Check for conflicting data types and overwrite the existing object with the imported object. (
Check for conflicting data types and do not change the existing object if there is a conflict. (
Do not delete fields on the existing schema that are not in the imported schema. (
Check for duplicate entries and report an error. (
Generate a new ID for a duplicate entry. (
Overwrite existing entry with an imported duplicate. (
Merge an existing entry with an imported duplicate. (
Generate a new ID for each entry. (
Do not delete VUIs of the existing schema that are not in the imported schema. (
Preserve the permissions of existing objects. (
Preserve all existing workflow attributes except the form list, the list of forms the workflow is attached to. (
Add the forms in the imported workflow form list to the workflow form list of an existing schema instead of replacing the workflow form list of an existing schema with the imported one. (
Preserve the change history of an existing object instead of replacing it with the change history of the imported object. (
Overwrite all workflow attributes, but preserve the existing form list. (
Remove the forms included in the imported workflow form list from the workflow form list of the existing schema, but preserve the existing workflow attributes. (
Overwrite full text option on existing field. (
Overwrite field display properties with properties from definition. (
The version control label that the API function must apply to the object. If the label name does not exist on the server, the function creates it.
Rename and Delete operations typically change multiple objects in addition to their primary target object. The Rename or Delete function must apply the version control label to all the objects that it affects.
Multiple API calls for a single user action
Some user actions trigger a sequence of API calls. In that situation, the last API call in the sequence applies the version control label to the object. Thus, clients that create forms (like BMC Remedy Developer Studio does) should provide the label only to the last call. For example, when a form is created, a client might issue these calls:
In this case, the
objectModificationLogLabel value should be passed only to the last call,
ARSetSchema, even though the user provides the label during the
Operations on label-related forms
Version control labels cannot be applied to these forms:
- AR System Version Control: Label
- AR System Version Control: Labeled Object
- AR System Version Control: Object Modification Log
A list of zero or more notes, warnings, or errors generated from a call to this function. For a description of all possible values, see Error checking.