Overview
ATTRIBUTES: SUMMARY \| DETAIL	RELATIONSHIP CLASSES: LOCAL \| INHERITED

Class BMC.CORE:BMC_RequestableOffering

BMC.CORE:BMC_BaseElement

  |
  +--BMC.CORE:BMC_LogicalEntity

        |
        +--BMC.CORE:BMC_Offering

              |
              +--BMC.CORE:BMC_RequestableOffering

Direct Known Subclasses:: None.

Specifies the offerings that are requestable, based on a technical or business service that is offeredFor example, for an ERP System business service offering, you might have requestable offerings for creating an account on the ERP System, closing an account on the ERP System, and increasing the database limit on the ERP System. This class is inherited from the BMC_Offering abstract class..

Properties

Name	Value	Scope	Options
`namespaceName`	BMC.CORE	None	None
`classId`	BMC_REQUESTABLEOFFERING	None	None
`FormName`	BMC.CORE:BMC_RequestableOffering	None	None
`Exposure`	usedVisible	TOSUBCLASS=false	OVERRIDABLE=false

Attributes Summary

Data type	Name and description
`enumeration`	`DeliveryRO` Specifies that this requestable offering (RO) is required to actualize the service offeringFor every service offering, you must set at least one requestable offering as a Delivery RO to actualize the service offering. You can create additional ROs that are of Transaction RO type. If set to True, the RO can be used to actualize or deploy the service offering. If set to False, the RO is a Transactional RO, which is used for making additional requests on an already actualized service offering. For example, think of setting up a bank account, which is equivalent to a Delivery RO. Once you set up the account, you can create multiple requests to deposit or withdraw cash. These additional bank transactions are equivalent to Transaction ROs.
`enumeration`	`IsAddOn` Indicates if the given instance of the RO represents an add-on service. If set to False, the service delivery is complete when the service request is closed. If set to True, the service delivery outlives the completion of the service request. For example, in case of a Blackberry Mobile Services requestable offering, the service request is closed as soon as the Blackberry device is sent to the user. The service delivery, however, is not considered complete until the Blackberry is functional and the user is able to send and receive messages on the device. Create a Contract AddOn Service Line during the execution of a RO with IsAddOn set to True to capture the service start and end dates, and to record that the user has the ongoing service.

Attributes inherited from class BMC.CORE:BMC_Offering

IsLocked, OfferingLifeCycle, OfferingType, WarrantyLevel

Attributes inherited from class BMC.CORE:BMC_BaseElement

AccountID, AssignedTo, AttributeDataSourceList, Availability, Category, CheckSumValue, CITag, ClassId, CMDBRowLevelSecurity, CMDBWriteSecurity, Confidentiality, CreateDate, DatasetId, Description, FailedAutomaticIdentification, History, ImpactComputationModel, InstanceId, Integrity, isCloud, Item, LastModifiedBy, LastScanDate, LicensingType, ManufacturerName, MarkAsDeleted, MarketVersion, Model, ModifiedDate, Name, NameFormat, Notes, OwnerContact, OwnerName, ParentCITag, Priority, ReconciliationIdentity, ReferenceInstance, RequestId, SerialNumber, ShortDescription, Submitter, Supported, SystemEnvironment, TokenFormat, TokenId, Type, VersionNumber

Attribute Detail

DeliveryRO

enumeration

DeliveryRO

Specifies that this requestable offering (RO) is required to actualize the service offeringFor every service offering, you must set at least one requestable offering as a Delivery RO to actualize the service offering. You can create additional ROs that are of Transaction RO type. If set to True, the RO can be used to actualize or deploy the service offering. If set to False, the RO is a Transactional RO, which is used for making additional requests on an already actualized service offering. For example, think of setting up a bank account, which is equivalent to a Delivery RO. Once you set up the account, you can create multiple requests to deposit or withdraw cash. These additional bank transactions are equivalent to Transaction ROs.

Name	Value	Scope	Options
FieldId	`530064200`	None	None
attributeId	`OS005056B5170DCFQhTA3TfKLQa1AA`	None	None
namespaceName	`BMC.CORE`	None	None
ValueMap	`0;1`	None	None
Values	`No; Yes`	None	TRANSLATABLE= true

IsAddOn

enumeration

IsAddOn

Indicates if the given instance of the RO represents an add-on service. If set to False, the service delivery is complete when the service request is closed. If set to True, the service delivery outlives the completion of the service request. For example, in case of a Blackberry Mobile Services requestable offering, the service request is closed as soon as the Blackberry device is sent to the user. The service delivery, however, is not considered complete until the Blackberry is functional and the user is able to send and receive messages on the device. Create a Contract AddOn Service Line during the execution of a RO with IsAddOn set to True to capture the service start and end dates, and to record that the user has the ongoing service.

Name	Value	Scope	Options
FieldId	`530064300`	None	None
attributeId	`CM005056B5170Di1UhTAah_QLQvlAA`	None	None
namespaceName	`BMC.CORE`	None	None
ValueMap	`0;1`	None	None
Values	`No; Yes`	None	TRANSLATABLE= true

Inherited Relationship Classes

Name Superclass Reference CI Class

Overview
ATTRIBUTES: SUMMARY \| DETAIL	RELATIONSHIP CLASSES: LOCAL \| INHERITED

BMC Atrium CMDB
Data Model