Represents the category that Life Sciences configuration records are
organized into. This object is available in API version 65.0 and later.
Important
Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
Supported SOAP API Calls
create(), delete(), describeSObjects(), query(), retrieve(), update(), upsert()
Supported REST API Methods
DELETE, GET, HEAD, PATCH, POST, Query
Fields
Category
- Type: picklist
- Properties: Create, Filter, Group, Restricted picklist, Sort, Update
-
Description: Required. The category used to organize the Life Sciences
configuration records.
Possible values are:
- AccountProviderVisitRecordTypeMapping
- AccountSearchSettings
- ActivityHistoryAdministration
- ActivityHistoryRelatedLabel
- ActivityPlanConfiguration
- ActivityPlanSettings
- AddressSettings
- AffiliationReverseRoleMapping
- AffiliationSettings
- ApplicationSettings
- BestTimeSettings
- BulkUpdateRestrictedEntity
- BusinessHoursHolidayMapping
- CalendarEvent
- CallCustomDiscussionRecordType
- CallDiscussionRecordType
- ConcurOrgLevelConfig
- CustomAction
- CustomerMergeSettings
- DEASettings
- DTVComponentConfig
- DTVObjectConfig
- DbSchema
- EnablementCoachingOrgLevelSettings
- ExternalSearchPreferences
- ExternalSearchUserSettings
- FieldSetMapping
- InventoryManagementSettings
- KAM
- KAMSettings
- LogSettings
- ManagedEventRecordTypeMapping
- NavigationIcons
- OptAdministration
- PlannerAdministration
- ProductAdminSettings
- ProfileBasedAppSettings
- ProviderSummarization
- QuickAction
- ReportsAndDashboardsSync
- SearchBeforeCreate
- SprintSettings
- StateDistributorLicenseSettings
- StateLicenseNumberSettings
- SyncProcessorConfiguration
- SyncTransactionAdminView
- SyncTransactionConfig
- SyncTransactionFieldBehaviour
- TerritoryManagement
- TimeOffTerritoryDynamicRule
- TimeOffTerritoryRule
- TimeOffTerritoryOrgLevelSettings
- TimeOffTerritorySettings
- TimeOffTerritorySlots
- TimeOffTerritoryWorkingDaySettings
- TimelineActivitySetting
- UISchema
- VideoCallPhoneNumber
- VideoCallSettings
- WorkingDaysConfig
CategoryLabel
- Type: string
- Properties: Create, Filter, Group, Nillable, Sort, Update
- Description: The custom label for the category.
DeveloperName
- Type: string
- Properties: Create, Filter, Group, Sort, Update
- Description: The unique name of the object in the API. This name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores. In managed packages, this field prevents naming conflicts on package installations. With this field, a developer can change the object’s name in a managed package and the changes are reflected in a subscriber’s organization. Label is Record Type Name. This field is automatically generated, but you can supply your own value if you create the record using the API.
Language
- Type: picklist
- Properties: Create, Defaulted on create, Filter, Group, Nillable, Restricted picklist, Sort, Update
- Description: The language of the LifeSciConfigCategory.
ManageableState
- Type: picklist
- Properties: Filter, Group, Nillable, Restricted picklist, Sort
- Description: Indicates the manageable state of the specified component that is contained in a package.
-
Possible values:
- beta—Managed-Beta
- deleted—Managed-Proposed-Deleted
- deprecated—Managed-Proposed-Deprecated
- deprecatedEditable—SecondGen-Installed-Deprecated
- installed—Managed-Installed
- installedEditable—SecondGen-Installed-Editable
- released—Managed-Released
- unmanaged—Unmanaged
MasterLabel
- Type: string
- Properties: Create, Filter, Group, Sort, Update
- Description: The label for the configuration category. In the UI, this field is Label.
NamespacePrefix
- Type: string
- Properties: Filter, Group, Nillable, Sort
- Description: The namespace prefix associated with this object. Each Developer Edition organization that creates a managed package has a unique namespace prefix. The prefix is limited to a maximum of 15 characters. You can refer to a component in a managed package by using the NAMESPACE_PREFIX__COMPONENT_NAME notation. Replace NAMESPACE_PREFIX with the namespace prefix, and replace COMPONENT_NAME with the component name.