12.07.2015 Views

Database.com Metadata API Developer's Guide - Salesforce.com

Database.com Metadata API Developer's Guide - Salesforce.com

Database.com Metadata API Developer's Guide - Salesforce.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Metadata</strong> TypesSharingRecalculationrecord, and the sharing access is maintained across record owner changes. For more information, see “Overview of SharingSettings” in the <strong>Database</strong>.<strong>com</strong> online help.Use SharingReason to create, update, or delete sharing reason definitions for a custom object. It extends the <strong>Metadata</strong> metadatatype and inherits its fullName field.VersionSharing reasons are available in <strong>API</strong> version 14.0 and later.FieldsFieldfullNamelabelField TypestringstringDescriptionRequired. Sharing reason name. The __c suffix is appended tocustom sharing reasons.Inherited from <strong>Metadata</strong>, this field is not defined in the WSDL forthis metadata type. It must be specified when creating, updating,or deleting. See create() to see an example of this field specifiedfor a call.Required. Descriptive label for the sharing reason. Maximum of 40characters.Declarative <strong>Metadata</strong> Sample DefinitionThe definition of a sharing reason in a custom object:. . .recruiter__cRecruiter. . .SharingRecalculationRepresents Apex classes that recalculate the Apex managed sharing for a specific custom object. For more information, see“Recalculating Apex Managed Sharing” in the <strong>Database</strong>.<strong>com</strong> online help.VersionSharing recalculations are available in <strong>API</strong> version 14.0 and later.FieldsFieldclassNameField TypestringDescriptionRequired. The Apex class that recalculates the Apex sharing for acustom object. This class must implement the<strong>Database</strong>.Batchable interface.102

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!