In order to create a patch org, the user will have to click on the new button as shown below:

Patch Org view

On Click of New, following screen is displayed:

Create Patch Org View

Select the Version number, enter appropriate username for the patch org and make sure that the email address is correct for patch dev org.

Selected Patch Org created

1. Once the patch is created by retrieving all the latest code, the user will have to log into the patch org to make any code changes.
2. Once the changes are made within the patch org, the user can upload the package as he/she would do in the managed dev org.

Push Upgrade and Version view

The Version tab shows the version that was uploaded in the patch org, the admin can then click on the Push Upgrade button.

Push Upgrade Screen

On push upgrade screen, click on the Schedule Push Upgrade button:

Schedule Push Upgrade Screen

Within the Schedule Push Upgrade Screen, the admin can select the Patch Version, if there are any orgs that does not have the version of code uploaded it will show up in the Select Target Organizations grid.

The admin is able to schedule those selected organization and apply the patch version 1.2.2.

Upload result screen

Upload results will be displayed on the Push Upgrade Screen, the targets have a hyper link that shows more details about the scheduled tasks.

The first thing that people would discuss is to make use of SSO, this my colleague Vilas have blogged earlier. I on another hand have taken another approach that to make use of Oauth 2.0 on Force.com it involves making use of Remote Access functionality. I will go through the exact steps to establish the initial handshake and thereby have target application push data to Salesforce. The target application will be written in C#.

The first step here is to set up the Remote Access, I have covered the Consumer Key but an entry here will provide a Consumer Key and Consumer Secret.

Step 1

Navigate to
Setup -> App Setup -> Remote Access

Remote Access Setup

Step 2
I then went ahead and created a Visual Force page called Admin Screen:

Here I have created two different buttons, one that will open a separate window using javascript and another that will open a tab and make use of the PageReference, both performing similar functionality.

Visual Force Page for the Admin Screen

Step 3

Admin Screen Controller

The code reference above provides two links, one that calls VisitConcur, on Click of that button the url will include isNewUser=true and sessionId is passed to the target website.

I have inserted a breakpoint where the session id is captured, and if it is a newUser, the GetRefreshToken(); function is called, this will inadvertently ask the user to insert the Salesforce username/password:

Step 4

Target Web site

Target Website (written in C#)

Step 5

Insertion of Salesforce Username/Password

On insertion of Salesforce username/password, the user will be prompted to the user to all the target application to be trusted:

Step 6

User prompted to trust the target website

Once the user clicks on Allow will send the control back to the Target website and this time the call back script that I have created will have the access and refresh token that will allow the target application to push data to Salesforce:

Step 8

Access / Refresh Token

Access / Refresh Token in Debug Mode

Target Website ASPX page

Call back script in code behind

Onload of the page, the javascript function CallServer is called passing in the url that contains the access and refresh token and its context (i.e. alert in this case).
Step 9

Now that we have the access and refresh token retrieved, we can make use of the access token to make API calls to Salesforce and retrieve or push data to Salesforce under the user’s credentials:

The URI here can be concatenated with token.instance_url + “/services/data/v20.0/query” and then we create a soql query to retrieve opportunities or any other object within Salesforce.

Post or Get information from Salesforce

Step 10

Refresh Token to retrieve access token

Finally there is one more point to note here, if the access token expires we can make use of the old refresh token to get a new access token without the user having to enter their username and password again. Instead of passing the access code we pass the refresh token, and pass the grant type as refreshToken instead of authorization_code. The function will return the new access token that we can make use of to communicate with Salesforce.

For more information visit:

http://wiki.developerforce.com/index.php/Digging_Deeper_into_OAuth_2.0_on_Force.com

Blog entry posted for: Ivan Melnikov

..

Overview

ExtJS javascript framework is becoming more and more popular among web site developers because of its simplicity and support of the most popular browsers in industry. Salesforce.com platform is not an exception. The newer 4^th version of ExtJS can be utilized to enrich standard VisualForce functionality with flexible UI components and make data representation a lot more customizable.

However there are some custom tricks and hacks that have to be used to integrate standard Salesforce.com with ExtJS framework. In this article I’ll try to briefly explain how to integrate lookup fields with Ext buttons and use standard Salesforce popup window for searching records and adding them to the UI components on the page.

Implementation steps

• You will need a lookup field on your page. This lookup field is going to be used to show the popup window only. It is not necessary to create any records using this field. Let’s create a custom object Lookup_Object__c and one lookup field to User object and name it User__c.
• Create a controller class for the page. This class has to have “global” access modifier and implement standard controller because we’ll need to use remote action methods for asynchronous calls on this page.
• Then define a remote action method which would return User record information by its Id in JSON format. For doing so we utilize new class available from the Winter’12 release for serialization of Salesforce.com objects into JSON format.

Here is what we should get:

global with sharing class UserManagerController

{

public UserManagerController(){}

public UserManagerController(ApexPages.StandardController controller){}

/* Object used to populate reference to user */

public Lookup_Object__c lookupObject

{

get;

set;

}

@RemoteAction

global static String getUserData(String recordId)

{

List<User> user = [select FirstName, LastName, Title, CompanyName from User where Id = : recordId];

// These methods are for serializing  Apex objects into JSON format available since Winter’12 release

// Find out more at http://www.salesforce.com/us/developer/docs/apexcode/Content/apex_methods_system_json.htm

String JSONString = JSON.serialize(user);

//Depends on your needs and way you want to format your result. Lets just hardcode the status value for now.

return ‘{“Records”:’ +JSONString+’, “error”: “null”, “status”:”SUCCESS”}’;

}

}

• Now create a VisualForce page. The lookup field should be hidden on the page. For doing that place it into the div under the form with style=”opacity:0; height:0;overflow:hidden;”. Please notice that we don’t use style=”display:none” in this case because it won’t work.
• So if you inspect this hidden field we created you may notice that in fact it is div which contains multiple fields ending with “_lkid”, “_lkold”, “_mod” to which we’ll need to get access to, read UserId from the “_lkid”  and reset all of them afterwards.  In order to open search window programmatically we’ll need to change window.location to the url stored at href property of hidden field.
• That is a basic concept. Please take a look at the code with comments inline. It is pretty straight forward and you can use it right away for you project needs.

VisualForce page code:

<apex:page controller=“UserManagerController”>

// Connects ExtJS library hosted at Sencha’s servers. However it can be stored locally as static resource.

<script type=“text/javascript” charset=“utf-8″ src=“http://cdn.sencha.io/ext-4.0.7-gpl/ext-all.js”></script>

<link rel=“stylesheet” type=“text/css“ href=“http://cdn.sencha.io/ext-4.0.7-gpl/resources/css/ext-all.css“ />

// Hidden form which contains lookup field to make standard salesforce lookup window work.

<apex:form >

<div style=“opacity:0;height:0;overflow:hidden;”>

<apex:inputField id=“userFieldId” value=“{!lookupObject.User__c}”/>

</div>

<div id=“pageView”></div>

</apex:form>

// Here is fun part begins…

<script type=“text/javascript”>

Ext.require([ 'Ext.form.*',

'Ext.grid.*',

'Ext.data.*'

]);

//Defines custom user model for the store

Ext.define(‘UserModel’, {

extend : ‘Ext.data.Model’,

fields: [{

name : 'LastName',

type : 'string'

}, {

name : 'FirstName',

type : 'string'

}, {

name : 'Title',

type : 'string'

}, {

name : 'CompanyName',

type : 'string'

}

]

});

// Defines custom user button which can be used multiple times

Ext.define(‘Ext.ux.UserButton’, {

alias : ‘widget.userButton’,

extend: ‘Ext.button.Button’,

// Handler function fires every time user clicks on the button.

handler : function() {

window.location = this.uA.getAttribute(“href”);

},

initComponent : function() {

var me = this;

var uField = Ext.get(Ext.DomQuery.selectNode(“input[id$=:userFieldId]“));

me.uId = uField.getAttribute(“id”);

me.uA = Ext.get(me.uId+‘_lkwgt’);

// Add on change event to the Salesforce user field.

uField.on(‘change’, function() {

// There is some delay required to let script set values to fields.

Ext.Function.defer(function(){

var nValue = me.getFieldValue();

if (nValue != ’000000000000000′)
{

me.addUserToStore(nValue);

}

}, 10, this);

});

this.callParent();

},

// Returns value from the Salesforce user field

getFieldValue: function() {

var v = Ext.get(this.uId+“_lkid”).getValue();

return v!=“000000000000000″?v:“”;

},

// Removes all values from hidden fields related to Salesforce user field

resetFieldValue: function() {

Ext.get(this.uId).dom.value = ”;

Ext.get(this.uId+“_lkid”).dom.value = ’000000000000000′;

Ext.get(this.uId+“_lkold”).dom.value = ‘null’;

Ext.get(this.uId+“_mod”).dom.value = 0;

},

// Adds user to the Grid store

addUserToStore : function(recordId) {

var grid = this.up(“grid”);

grid.setLoading(true);

// Get data from SalesForce

// Heres is apex remote action call, which allows user make request to APEX controller using Javascript.

UserManagerController.getUserData(recordId, function(result, er){

// Set loading mask on the grid.

grid.setLoading(false);

// Decode JSON string returned from the server.

var res = Ext.decode(result);

// If result field “status” contains word ”SUCCESS” then proceed with adding new user on the grid.

// Otherwise display popup with an error message.

if (res && res.status == “SUCCESS”)
{

// Take first and only record returned from the server. There might be multiple ones, depending on design requirements.

var userRec = res.Records[0];

// Add record to the grid store

grid.store.add(userRec);

} else {

// Display error message.

Ext.Msg.alert(“Error”,“An unexpected error occurred.”);

}

}, {

// This parameter is used to prevent auto escaping of special characters like &,@, quotes, double quotes etc.

escape: false

});

// Reset user field values for the next click.

this.resetFieldValue();

}

});

// Create an instance of grid.

var grid = Ext.create(‘Ext.grid.Panel’,
{

// tbar is toolbar element on the top of the grid.

tbar : Ext.create(‘Ext.toolbar.Toolbar’, {

// Creates one button in tbar

items: [{

xtype: 'userButton',

text: 'Add User'

}]

}),

// Creates store to keep user record for displaying on the grid.

store : Ext.create(‘Ext.data.Store’,
{

model: ‘UserModel’,

proxy : {

type : ‘memory’,

reader : {

type : ‘json’

}

},

data: []

}),

// Columns describe how records will be rendered on the grid.

columns: [{

text: "Title",
width: 100, dataIndex: 'Title', sortable: true

},{

text: "Name",
width: 200, dataIndex: 'Title', sortable: true,

renderer: function(value, p, record){

return record.data.LastName + ', ' + record.data.FirstName

}

},{

text: "Company", width: 100, dataIndex: 'CompanyName', sortable: true

}]

});

// Main panel contains grid panel and may potentially contain more panels in it. Renders to the ‘pageView’

// div tag, which we defined on the top of this page.

var mainPanel = new Ext.panel.Panel({

border: false,

renderTo : ‘pageView’,

width: 400,

items : [

// Only one panel, which is grid panel will be displayed on this parent panel.

grid

]

});

</script>

</apex:page>

What is good about it?

ExtJs can significantly extend any VisualForce functionality and add new features which Salesforce doesn’t have yet. All developers need is to customize and embed some standard functionality with custom JavaSript code.

Thank you for reading!

**

If you want to test out the sample from the post, please find below a link to the unmanaged package:

https://login.salesforce.com/packaging/installPackage.apexp?p0=04tU0000000DZd3

**

]]> http://comitydesigns.com/blog/integration-of-salesforce-com-lookup-field-functionality-with-extjs/feed/ 0 http://comitydesigns.com/blog/dreamforce-2011-a-spectacular-event/ http://comitydesigns.com/blog/dreamforce-2011-a-spectacular-event/#comments Sat, 03 Sep 2011 06:18:47 +0000 Rashi http://comitydesigns.com/?p=1010

Dreamforce 2011 was a phenomenal event for Comity Designs, partners and clients! The event is always jam packed with conversations, building relationships, networking, and not to forget – having a little bit of fun in the mix of it all (as can be seen in the picture above).

I also want to congratulate Comity Team members that once again this year have WON an award at the Dreamforce 2011 Hackathon!!!

**CHEERS**

And for all you visitors that are reading our blog, please check out the links below to read all about our announced victory.

Hackathon Entry: “Enterprise Mood Monitor”

Link 1 - Dreamforce ’11 Hackathon Winners Announced (Developer Force Blog)

Link 2 - Social Media “Mood” App Wins Big at Dreamforce ’11 Hackathon (Developer Force Blog)

Link 3 - Dreamforce Hackathon Winner: Enterprise Mood Monitor (GNIP Blog)

…

We will be sharing additional information about the hackathon and adding more pictures to our blog , so stay tuned and visit us again soon.

*****************************

Pictures:

*****************************

Comity winning at the Dreamforce 2011 Hackathon

Participants: Shamil Arsunukayev, Ivan Melnikov, Gaziz Tazhenov

Salesforce.com provides Translation Workbench, a feature that can be turned on only by calling in Customer Support or logging a Case through your Org. When the translation workbench feature is available, you have to login to your org and enable the feature, add new languages that you want to support and then provide translations for the areas of your application that you control.

Steps to enable Translation Workbench

1. Call Salesforce.com support or enter a case to activate a feature [this feature is non-reversible after it is turned on].
2. When the customer support turns it on, login to your org and Enable the feature by going to Setup -> Translation Workbench
3. Add languages that you want to support for you application
4. Provide translation
5. Update your code to use the translations if you haven’t already done designed for globalization

At what level the translations can be turned on?

1. Org level by going into Setup -> Company Information -> Edit [Default Language]
2. User level by going into Setup -> Manage Users -> Edit User [Language]

However, keep in mind changing the Default Language at org level doesn’t change every user’s default language. In order for user to start seeing the content in different language, either of two things need to happen:

• Admin has to set the language at user level
• User should use a browser with the locale for the language they want to see in Salesforce.com

What gets translated?

Salesforce.com documentation mentions three main areas that get translated or need to be addressed either by Salesforce.com or by yourself in your own customizations [code or admin changes]

1. Main salesforce.com application content [this is your standard look and feel of salesforce.com, standard objects and their labels]
2. Online help provided by Salesforce.com
3. Your own customizations – things like labels for your custom objects/fields properties, Visualforce page content that you control, picklist values you control.

Very Simple Example to illustrate the implementation

Let’s make sure we have performed following steps before we start:

1. The feature has been activated by Salesforce.com customer support
2. You have logged in to the Salesforce.com org and Enabled the feature [even though customer service activates the feature you still have to turn it on by going to Setup -> Translation Workbench
3. Add Spanish language as the new language we are going to support in our Salesforce.com Org and make sure you have checked the Active check box.









4. Create a new Custom label named Field1Label to use in our Visualforce page. Set the value for it as “Value”. Also, add a spanish language translation for this custom label and set its value to to be “Valor”

At this point we are ready to get started on creating a very simple Visualforce page that will allow us to support two languages English and Spanish.

Here is our Sample page:

Save the following in a new Visualforce page named TestCustomLabelPage

<apex:page controller="TestTranslationController">

<apex:form >

<apex:pageBlock >

<apex:pageBlockSection >

<apex:pageBlockSectionItem >

<apex:outputLabel value="{!$Label.Field1Label}"></apex:outputLabel>

<apex:inputText />

</apex:pageBlockSectionItem>

</apex:pageBlockSection>

</apex:pageBlock>

</apex:form>

</apex:page>

Assuming that your Salesforce.com user has the default language set to be English, let’s see how the Visualforce page will look like this at present.

Let’s go to Edit the user and set the Language to be Espanol.

Go back and refresh the Visualforce page and we should see following page [see the label is changed to Valor [Spanish for Value as we have entered in the translation for the custom label].

What is good about the translation workbench?

• Fairly straight forward implementation as long as you are supporting the language out of the languages that Salesforce.com supports
• Ability to add new languages over time and leverage the same code infrastructure you have setup when you supported two languages
• Earlier it was pretty tedious to enter all the values manually, but recently Salesforce.com has added support for translation import/export from both Apex Data loader as well as Force.com Eclipse IDE

What is not so good about it?

• Salesforce.com supports fairly good number of languages out of the box but the number is still pretty small so if you are supporting a language that is not part of their list you are out of luck and the only option you have at that point is to build your own code infrastructure in apex to support it
• Limit on maximum number of custom labels. This could be critical given that salesforce.com supports maximum 5000 for the whole org. I am interpreting this as all the code within the Salesforce.com org and the all the AppExchange packages installed in that org, all of them have to share that pool of 5000 custom labels. In my opinion, this is pretty sparse. In a fairly complex AppExchange application you will come pretty close to using at least a few thousand custom labels and if you have an Org where you have 4-5 of those AppExchange apps installed then you are going to run into this problem. Having said that, there is a possibility that Salesforce.com may not count the custom labels included in the AppExchange apps with Aloha status but not sure about this.

Further Reading

https://na9.salesforce.com/help/doc/en/customize_wbench.htm

https://na9.salesforce.com/help/doc/en/salesforce_ide_localization.pdf

https://na9.salesforce.com/help/doc/en/entering_translated_terms_in_packages.htm

https://na9.salesforce.com/help/doc/en/salesforce_workbench_cheatsheet.pdf

..

One of the limitations of the Salesforce.com platform is that it does not allow developers to inject their own logic into an Approval Process, especially when using standard VisualForce tags. With standard related lists (not custom components) columns cannot be customized to display custom information.

One common way of working around this limitation is to replicate the relatedList as a custom component where you duplicate the look and feel utilizing the pageBlockTable VF tag, thereby having the ability to add any custom logic. This approach is more rewarding but far more time consuming and not always necessary.

Another quicker mechanism to bypass this limitation is to use a combination of CSS and HTML tags and attributes on a page in addition to APEX code that replicates the needed standard functionality.

As an example, let us take a look at a use case that requires us to perform a check and display an error message on a VF page upon clicking the Approve/Reject Link from the ProcessSteps relatedList i.e. the Approval History.

One way to approach this, as highlighted in this post is to use CSS to hide the actionColumn on the standard relatedList, then provide commandButtons or commandLinks above or below the relatedList allowing the user to run custom pre-defined APEX logic.

In the event that the business does not require a heavily customized solution, modifying a standard related list can be the faster and more reasonable approach. However, its functionality is also limited, in the sense that using this method only allows the hiding of pre-existing columns that would otherwise be shown in the relatedList implementation. The addition of new columns is not possible and in this case one must revert to the complete custom solution.

For hiding the Action column:

Insert the following code on the Custom  VF Page in the correct place as specified by the tags:

<style>

/* === Hides Action Column for Approval History === */

[class$='actionColumn']

{display:none}

/* === END === */

</style>

NOTE: This will cause all columns of the name actionColumn to be hidden on the page, so only use this implementation if you are sure that nothing else has the same name or else it will disappear as well.

A better way would be to find the columnID because this is guaranteed to be unique at least within the page, but this is not always possible, as it was in this case.

So you could use this method to hide a column from a custom element in a similar manner.

To add commandButtons that do the same thing:

Informational Headers should provide the reader (author or another developer) with at least the following :

• Artifact name
• Associated artifacts
• Spawned artifacts
• Purpose (summarized description) and context
• Change log

This basic set of information allows yourself or anyone else a quick background of what you are going to view, review, edit, or deploy, including any information about dependancies if you choose to include this additional detail.

Well structured and commented code goes a long way, and speeds up development. Poorly structured and non-commented code makes it hard for the person that did not write it to understand and potentially delay development or even create further problems by modifying the wrong data, etc.

In addition a properly maintained change log allows one to track changes or updates that were made within the header, providing a quick facility to then reference the right individual for help in the event of code failure or malperformance.

I can list another 101 reasons in this entry, and trust me when I say that I’ve seen a lot of dirty code – it makes it very hard to move forward at a good and fast pace. SO, I urge all Technical Architects, developers (Sr. and Jr.), and to be developers to make it a practice to add ‘Informational Headers’ to your code artifacts, it will not only save you time but also for others that inherit your code.

Well, you can!

All you have to do is pass an additional URL parameter to your report with the new criteria for testing:

• bool_filter=1+AND+2+AND+(+3+OR+4+)
• Example: https://cs1.salesforce.com/00OM0000000FAUH?bool_filter=1+AND+2+AND+(+3+OR+4+)

So lets say that your original advanced filter criteria was: 1 AND 2 AND 3 AND 4, by passing the above URL parameter your report should now show 1 AND 2 AND ( 3 OR 4 ) as part of the advanced filter criteria. Additionally, your report data should reflect accordingly.

..

Disclaimer:

Any of these features could be changed by Salesforce.com in a future release.

This effect can be mimicked on standard pages by using the url parameter: isdtp=mn or lt .

• isdtp=mn will retain the old SFDC styling and retain the page header (not the SFDC header with all the tabs)
• isdtp=lt will retain the old SFDC styling and will remove the page header as well

You can use this trick on standard page layouts as such:

• For example: https://cs1.salesforce.com/001C000000oaDWl?isdtp=mn

or on other native salesforce pages, such as reports. This trick allows you to you embed standard pages without the header and side bar within VF pages successfully.

Of course you do need to keep in mind that there are limitations to what all you can do, but nonetheless ‘isdtp’ is a very useful URL parameter to know of.

..

Disclaimer:

The new SFDC styling/UI Theme has not been made available to this URL parameter, and may not work on some of the native SFDC pages.

If you closely observe the URL, you may notice two query string parameters: saveURL and retURL, and by modifying one or the other or both you can control the users navigational behavior.

1. retURL : allows you to redirect the user to any location** within Salesforce.com as allowed by permissions when they hit ‘Cancel’
2. saveURL : allows you to redirect the user to any location** within Salesforce.com as allowed by permissions when they hit ‘Save’

**any location : other salesforce records (detail or edit view), native and custom pages (VF), native tabs and custom tabs, etc.

Example – upon cancel the user is navigated to another record’s detail page, and upon save the user is sent to a custom VF page

• https://cs1.salesforce.com/a06M0000000I3dq/e?retURL=%2Fa06M0000000I5ab&saveURL=/apex/VF_PAGE_NAME

By modifying your custom links or buttons you can control the user navigation and tailor it to your business’ specific needs.