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.
Deletes the escalation with the indicated name from the specified server and deletes any container references to the escalation. The escalation is deleted from the server immediately and is not returned to users who request information about escalations.
BMC Remedy AR System administrator.
#include "ar.h" #include "arerrno.h" #include "arextern.h" #include "arstruct.h" int ARDeleteEscalation( ARControlStruct *control, ARNameType name, unsigned int deleteOption, 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.
If a valid overlay group is specified in the control record, the
ARDelete* function operates on the object that belongs to that group. If no group is specified, the function operates on the origin object. To specify whether to use an object's real or resolved name in an operation and whether to perform the operation only on objects in a specified overlay group, use the
AR_SESS_CONTROL_PROP_DESIGN_OVERLAYGROUP variable of the
ARSetSessionConfiguration function (see ARGetSessionConfiguration).
The name of the escalation to delete.
A bitmask that indicates the action to take.
Server object default delete option. For locked objects, fails the delete attempt (
Delete escalation and all objects in the block (
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.