Skip to main content

New Objects in API Version 29.0

Today, while working on Event object, I recognized that we can add more than one Lead/Contact to an event using 'Add to Invitees' link. My curiosity to understand how it is being stored in DB took me to 'EventRelation' & 'UndecidedEventRelation' objects. I suspected there are many more and it leads me to Winter'14 release doc and I found whole set of new objects in API Version 29.0

These objects are new in API version 29.0.

  • The AcceptedEventRelation object represents invitees with the status Accepted for a given event.
  • The AccountCleanInfo object stores the metadata Data.com Clean uses to determine an account record’s clean status.
  • The AllowedEmailDomain object represents an allowed email domain for users in your organization.
  • The AppMenuItem object represents an item in the app picker, exposing metadata for tab sets, service providers, and Connected Apps.
  • The AttachedContentDocument object contains all ContentDocument objects associated with an object.
  • The AuthSession object exposes session data and enables read and delete operations on that data.
  • The CombinedAttachment object contains all notes, attachments, Google Docs, documents uploaded to libraries in Salesforce CRM Content, and files added to Chatter that are associated with an object.
  • The ContactCleanInfo object stores the metadata Data.com Clean uses to determine a contact record’s clean status.
  • The CronJobDetail object provides the name and type of a scheduled job represented by a corresponding CronTrigger record.
  • The DeclinedEventRelation object represents invitees with the status Declined for a given event.
  • The EventWhoRelation object represents the relationship between an event and a lead or contacts. This derived object is a filtered version of the EventRelation object.
  • The FeedPoll Choice object represents a choice in a poll posted in a feed.
  • The FeedPollVote object represents a vote in a poll.
  • The FieldHistoryArchive object represents historical archived information about an object’s changed field values. The object is currently available through a pilot program.
  • The LeadCleanInfo object stores the metadata Data.com Clean uses to determine a lead record’s clean status.
  • The LiveChatTranscriptOwnerSharingRule object represents the rules for sharing a Live Agent chat transcript record with users other than the record owner.
  • The PermissionSetLicense object represents a license that enables a user to receive a specified permission without changing their profile or reassigning profiles.
  • The PermissionSetLicenseAssign object represents the association between a User and a PermissionSetLicense.
  • The TaskWhoRelation object represents the relationship between a task and a lead or contacts. This derived object is a filtered version of the TaskRelation object.
  • The UndecidedEventRelation object represents invitees with the status Not Responded for a given event.
  • The UserLogin object represents the settings that affect a user’s ability to log into an organization.
  • The UserProfile object represents a Chatter user profile.

Comments

Popular posts from this blog

Mashup Integration in Salesforce

During preparation for TA certification exam, I came across a word Mashup for integration a number of times. I explored about it and below is description:- Mashups, sometimes called “composites,” are hybrid applications created by bringing together several data sources and Web services to create a new application or to add value to an existing application. Behind the scenes, mashups may require different levels of integration, depending on whether the mashed-up data is only meant to be viewed, whether it can be edited, and whether data is actually transferred between systems. There are three types of mashup:- Client Presentation Mashup - In this type of mashup the integration takes place strictly at the visual level. It makes possible to view data from two or more applications in a browser,  without actually moving data between the applications. Example - Google Maps. Client Service Mashup - As mashups evolve, they are becoming more complex and sophisticated. Client ser

Grant Access Using Hierarchies

Problem There is a custom object say 'XYZ' and OWD for this is set to ' Private ', which means record of this can be seen by only owner and users above in role-hierarchy and territory. However, to share this with other user, we can manually share it. The problem is that I don't want other users, who are above in role-hierarchy and territory of the user with whom record has shared, can see it. Solution We can un-check ' Grant Access Using Hierarchies ' check box for object 'XYZ' on 'Sharing Settings' page. We can go to Setup >> Security Controls >> Sharing Settings and click on ' Edit ' button. On the edit page, we can un-check ' Grant Access Using Hierarchies ' for required object.  Major uses of 'Grant Access Using Hierarchies' are:- If you disable the Grant Access Using Hierarchies option, sharing with a role or territory and subordinates only shares with the users directly asso

ReadOnly Annotation

Use Case:- You want to show up to 10000 record on single VF page. Count of records based upon some business requirement where number of records could go up to 1 million. So far, it was not possible to achieve above in VF page because of following limitations:- The maximum number of items in a collection that can be iterated over using components such as <apex:dataTable> , <apex:dataList> , and <apex:repeat> is 1000. Normally, queries for a single Visualforce page request may not retrieve more than 50,000 rows. Solution:- But with API version 23.0 , salesforce has introduced ' ReadOnly ' annotation which has following functionality/restriction:- The @ReadOnly annotation allows you to perform unrestricted queries against the Force.comdatabase. All other limits still apply. It's important to note that this annotation, while removing the limit of the number of returned rows for a request, blocks you from performing the following operations