Appirio Cloud Sync - July 2012 Release Notes

Summary:

Appirio Cloud Sync is a multi-tenant cloud-based application that synchronizes Salesforce and Google Calendars and Contacts helping to improve the value derived from both applications by allowing users to see a consistent set of information in both.  Appirio periodically delivers new features and fixes via updates to the application which, when released to production, are automatically available to all Cloud Sync tenants.  Note that some features require admin or user action to enable, and the details are covered below.

In this release there is a major platform improvement, a new Contact Sync feature, and a couple fixes.

Details:

• Platform improvements
• SUMMARY: Cloud Sync now supports OAuth authentication protocol with Google and Salesforce.  Users will authorize (and revoke access) without Cloud Sync storing password credentials.  This will support the following behaviors:
• Users can authorize connections to Google domains other than the primary one used by their Salesforce organization.  This can include sub-domains, standard gmail.com domain, etc.
• After a user configures OAuth, Cloud Sync will no longer store their Google or Salesforce passwords and will no longer fail to sync when a Google or Salesforce password changes.
• USAGE - Salesforce: Users will see a difference in the My Setup page versus the previous behavior.  Instead of needing to provide their Salesforce username and password, users will click the Authorize link (or Reauthorize link in the case that they previously provided username and password) and complete the dialogs to allow Cloud Sync to connect to their account.

New user will see:

User that previously authenticated (including with username and password parameters in Cloud Sync) will see:

• Note - when multiple Salesforce sessions are open this process will typically recognize the last one so users should confirm the user being authenticated is the expected one.
• Users that want to revoke Salesforce access later can do that via the Cloud Sync My Setup page, and/or can do that from within Salesforce by going to Setup > My Personal Information > Personal Information and Revoke the Cloud Sync application in the Remote Access list.
• USAGE - Google: Similarly, a user will authorize Cloud Sync to connect to his/her Google account.  Note that Cloud Sync will default to the open Gmail session or if multiple Gmail sessions are open it will prompt the user to confirm which one to use.  Make sure to login to the Gmail account you plan to use with Cloud Sync prior to starting the Authorization process.
• Users that want to revoke Google access later can do that via the same page, and/or can do that from within Google by going to Account > Security > Authorizing applications and sites.  Find the CloudSync entry and click the Revoke button.

• Contact Sync improvements
• SUMMARY: Users can now configure Cloud Sync to synchronize contact records from Google to Salesforce even if they don't have an email address.  This use case is prevalent when creating emails on a mobile device.
• This feature only applies in the Google to Salesforce direction.  Salesforce contacts currently must have an email address to sync to Google.
• To successfully sync to Salesforce, the Google contact must have a Name and a Work Phone specified.  Contacts with a Name and Mobile or Name and Home Phone will not sync successfully with Salesforce.
• USAGE: Users can enable this feature by using the Google to Salesforce Custom option and deselect the Exclude Contacts without email addresses option.

• I-27530: Changing the visibility filter no longer allows Google contacts that should otherwise be filtered to sync to Salesforce.

• Calendar Sync improvements
• I-26829: Recurring All Day meetings now sync to Salesforce from Google with the correct number of days.

CloudFactor Release Notes - July 2012

Standard Apps

SFDC Contact App

• SUMMARY: When receiving an email from a sender that doesn't match an existing Contact or Lead in Salesforce, in addition to the Create a Contact and Create a Lead buttons, the user will see all the other standard action buttons e.g. Record Email, Log a Call, and Create Task.
• TO CONFIGURE: n/a, the buttons now appear by default.
• TO USE: click to activate buttons as in other CloudFactor contexts.

Business Actions Sidebar App

• SUMMARY: Business Actions sidebar now includes a Go button to activate the choice in the picklist.  This change is being made to support the use case where a user selects a Business Action, returns to his/her Inbox and then wants to activate the same Business Action again.
• TO CONFIGURE: n/a, the Go button now appears by default.
• TO USE: to activate a Business Action, click the Go button.

Platform

Add CloudFactor apps as custom buttons on Case and Contact app header bars

• SUMMARY: to make it easier to surface CloudFactor apps such as Create Account or Create Contact, it is now possible for administrators to configure buttons that call CloudFactor apps.
• TO CONFIGURE: in the CloudFactor admin console, the Administrator can add custom bottons to the Case, Contact, and Contact (No Contact Found), and Sent Email.  To do this:
• Navigate to the Applications tab and select the App Buttons page on the left navigation bar.
• Select an application to configure buttons for.

• Select an application to expose as a button.  Note: this must be an application that requires no email context e.g. Create XXX applications or custom apps that do not require any email context are candidates for this feature.
• Optionally, override the default Button Label which is the same as the application name.
• Save the changes.

Note: there are a few configuration limitations to be aware of:

• You cannot disable standard action buttons currently.
• You should not choose any application that requires email context to function correctly e.g. Case, Contact, and Reply to Chatter for instance, all require the email sender email address or some element in the email subject or body to work correctly.
• Applications copied from standard CloudFactor apps will inherit the buttons on the original app.
• CloudFactor will automatically add buttons until the width of the app is filled and then add a row below the action buttons and include more buttons as needed until all buttons are added.  Recommended approach is to add no more buttons than will fill one row.

• TO USE: users will see and be able to interact with the buttons as other buttons.  This provides a good alternative to having the application configured under the Fixed Applications list in the CloudFactor more options menu.

Dependent Picklists

• SUMMARY: CloudFactor page layouts may now include dependent picklist fields.
• TO CONFIGURE: in the CloudFactor admin console, the Administrator can add picklist fields to the application page layouts.  To do this:
• Navigate to the Applications tab and select the Applications page.
• Click the green gear on any standard app to configure the page layout for the application e.g. click the green gear on the Case application.
• Select the controlling picklist field and the dependent picklist field and add both to the page layout.  Important - the controlling field must be placed above the dependent field in the page layout.
• Save the changes.

• TO USE: users will be able to use these picklists like any other field in CloudFactor apps when creating or editing records.  The controlling field will determine what is selectable in the dependent field.