Skip to main content

Things that ROCK in Salesforce Winter 11'

Force.com Labs never cease to surprise and please you during every new release. After creating a lot of buzz with their new chatter this time, they are now back with the Winter 11.

Things that ROCK in winter 11'

1. System Log console

If you have not seen the awesomeness yet, check out the brand new System Console. I know this feature is quite old in other languages and their sophisticated IDE's but for a force.com developer, this will be a amazing feature to debug languages.
Have only seen the screen shot, so will need to confirm what exactly it shows.
Check out this blog post for a sneak peek, which includes this amazing screenshot:

2. Visualforce Chatter Components:
The power of Force.com comes with simple tools for complex business processes. The Chatter components for Visualforce will help embed chatter feed into the Visualforce page. With simple tags like.
<Chatter: FeedWithFollowers entityId={!RecordId}/>

3. Language Translation for Force.com
This feature would be really interesting, while developing custom apps for Multi-lingual support. By default as announced, Serbian, Slovak, Georgian and a number of English variants are supported.

4. #Hashtagging is enabled in Chatter
How many of us simply love the Twitter #HashTag? Now the #Hashtagging is supported in Chatter, we can actually predict the trends like Twitter into chatter.
Looking at the chatter updates, you can feel that the corporate wall is slowly getting thinner and thinner and people are liking the new medium of communication and collaboration.

5. OAuth 2.0 Support
Usefull for authorizing external websites with Salesforce. To know more click here.


6. Visualforce View State Inspector
In a separate tab of the Visual Page editor, you can now see the view state of the page running. You can use this to fine tune the visualforce page and no need for debugging. Not good if you are using Eclipse IDE for development.



7. Global Search
Searching on Content can help reduce a lot of time hunting for the record you forgot.

Global Search gives you instant results and suggests terms using auto-complete for records that you’ve recently viewed, edited, or looked up. You can drill down to specific items, including articles, content, products, solutions, Chatter feeds, files, groups, and people.

8. Set up UI update
Finally the setup sheds its old skin and jumps up in the cloud. No actually use here, but I kinda love the new skin, its clean.

9. Default Values in Visualforce Input Fields
A little more help in the Input Field fields. Also, the recordtype also affects the inputfield properties.


10. Revised Governor Limits
I was pretty excited on seeing this enhancement, but the excitement died down when no changes in the DML limits was seen.


For Winter '11. tests no longer have specific limits. Instead, they've been included with triggers, anonymous blocks, Visualforce controllers, and WSDL methods.

Good news is many of the Limits are now reduced.

Some of the limits affected from the change:

Removed limits:
• Total request time for one callout (HTTP request or Web services call) has been removed.
• Maximum size for a callout (HTTP request or Web services call) has been removed.
Increases to existing limits:
• General heap size has been raised from 2 MB to 3 MB, with no scaling. In addition, batch Apex heap size is 6 MB.
• Apex classes and triggers have been raised from 100,000 characters and 32,000 characters, respectively, and can now be 1 million characters long, not counting comments, test methods, and classes defined with @isTest.
• Maximum amount of Apex code allowed in an organization has been raised from 1 MB to 2 MB.
• Total number of ChildRelationship, RecordTypeInfo and PicklistEntry objects allowed and total number of fields calls allowed has been raised from 10 to 100.

Thats all in it from me today, you can check the full features of the release on Salesforce.
The release notes are available here.

Comments

Popular posts from this blog

Video: Top ten tips on how not to ruin Salesforce implementation

Another presentation for the London Salesforce Developer Group using mobile app. 
When it comes to Salesforce development, we all know what it takes to deliver stuff. Having a certified professional helps you gain a knowledgeable partner but what about the things such as common sense?  We all know how to deliver things on client requirements but what about things that are not mentioned by the client. We will be discussing in details things that will enhance the user experience, focus on tips to read your customers mind and have a bit of perspective on the user experience.

Cache me if you can: What you should know before daring to set URL parameter on visualforce

If someone gave me a pence for every time there was an SOQL query in an APEX Class without using Limit or a condition during a code review, I could afford a Lamborgini this month. Sigh. If only. We make it a habit of going digging for data, at the very moment we need it. The crux of this problem happens when you have chain classes which are independent of each other. Each class needs the reference from a single record and we have to query for that record every single time.

While we don't see it, every SOQL query has a cost to it, and it does not go in my Lamborghini fund, however, it should. In a recent project, we had to construct an Account 360 page that could fetch information from different integration points. The page was also called using a live telephony integration, which could pass the phone number for the account. This required an ability to keep in context the Account that was on call.

Passing the Account id in URL parameter was a valid option, however, any manipulatio…

Four secrets to improve the usability of your visualforce/Lightning pages on Salesforce

In the immortal words of a certain machine returning back in time, I am back. For now. After procrastinating for over a year and drafting a lot of rants- I am back with a very important coding lesson for you. For now.

When we are designing a Visualforce page or an app or a lightning component (added that only to trick google) or any web page for that matter, we often tend to wrap up things quickly. Ask anyone on the team, how to design a good User Experience? and the person will immediately throw buzz words like Bootstrap, angular and other useless libraries (did someone squint?)

Ok, Bootstrap, Angular-Js, and all the libraries are really cool and are useful in designing a fabulous UI. They are helpful in creating responsive pages that will work on all the devices but this post is not about those. Nope. For the purpose of this post, all the external libraries and buzzwords you use to decorate your resume are useless. (Adding Angular JS in your resume for a Salesforce consultant posit…