Leverage Cloud and Bring Efficiency to Your Business

salesforce-cloud-serviceIt’s important for businesses to understand how cloud computing works before leveraging it fully. Having a cloud app gives them a whole lot of freedom where they can open a browser, log and it and get going with the work. Continue reading



The Salesforce1 World Tour comes to the London ExCel on May 21st and with so much to see, do (and drink) it is vital you plan your day so you get the most out of it! With stalls as far as the eye can see and a multitude of pens, key rings and furry toys being handed out by company representatives the question stands; what companies should I visit come the big day (that’s May 21st if you’d forgotten!) First things first though make sure you have signed up for the event here (registration is free!) – https://www.salesforce.com/uk/events/details/london/register/

Who To Visit (In No Particular Order)?

1. NewVoiceMedia

NewVoiceMediaThere are many reasons to go and visit NewVoiceMedia other than the fact that last year they were handing out fresh coffee to guests. Although that is a good reason lets take a look at some of the others… NewVoiceMedia announced last year that the solution is now compatible with the Salesforce1 Mobile App – meaning that sales and service representatives can now stay connected with prospects and customers from any location, safe in the knowledge that their calls are being recorded and logged in Salesforce. Check out the video here – http://www.newvoicemedia.com/referral/press/salesforce1/index.html

The guys and girls at NewVoiceMedia also know how to throw a good party come the evening so make sure you visit in them in the day and make some friends!

2. Conga

congaA quick read through Conga’s reviews on the Appexchange should provide enough reason for a visit to the ‘Conganeers’ at Salesforce1 World Tour.

Conga is probably the app we not only see installed the most in our customer’s orgs but also utilised the most. The reason for this? Well Conga provides you with the ability to, at the click of a button to generate proposal, quotes, account plans, invoices, receipts and the list goes on. These documents can be presented in a number of different formats (Excel, Word, PDF, PowerPoint and Html Email templates).

With Salesforce1 capability, users can generate any document or report from either their browser or their mobile. The documents themselves can then be emailed directly to whomever, automatically downloaded, sent for e-signature or stored in Salesforce, Google Drive or Spring CM.

Why should you have to draw up a proposal after you have already entered all of the necessary information in to Salesforce already? Well with Conga, at a click of a button you will no longer have to. Conga is as popular as it is for a very good reason, so they are well worth a visit! Take a look at some of their customer stories for some ideas on how Conga can help you create efficiencies in document and report generation – http://www.congamerge.com/customers/case-studies

3. DocuSign


So what is Docusign and how does it work? It’s pretty easy! Firstly send your document to those recipients who need to sign, date and initial the document. The recipient(s) can click on the link in the email and follow the tags on the document which will tell them what they need to do and where! You can then manage your documents that are out for signature! You will have visibility of where each of your documents are in the process and can send out reminders and get notifications at each and every step of the way! Your documents are then saved and stored as required… So if you send out documents for signature I suggest you drop a visit to the DocuSign team!

Most importantly though, if you see one of the CloudSocius team wondering around the event then come and say “hi”, we are a friendly bunch (in the most part!)

Resource : CloudSocius

Salesforce – What Records Can I See?

Salesforce-What-Records-Can-I-SeeWhen working with what people can see within Salesforce there are four key considerations and in this blog we will work through each one of these four, exploring how they control what users can see within Salesforce (not what they can do – this is controlled by user profiles and permission sets)! The four key features controlling what people can see are as follows; Organisation Wide Defaults (OWDs), Record Ownership, Role Hierarchy and Sharing Rules.

Organisation Wide Defaults
So let’s start at the top with OWDs. OWDs can be found under Setup – Security Controls – Sharing Settings and with OWDs you have four options; Private, Public Read Only, Public Read / Write, and Public Read / Write / Transfer. The best advice here is to lock these down so they are as restrictive as possible – but of course still let people do their jobs! So if we take a look at an example of a Case record within Salesforce. The question you need to ask yourself when setting up OWDs is do you want users to have the ability to see and edit all case records (Public Read/ Write), see all records (Public Read) or just have the ability to modify cases that they own (Private).

Record Owner
Why is record ownership so important? Every record within Salesforce has an owner (either a user or a queue) and this impacts on who can see the record! If a system admin was to import a number of accounts in to Salesforce and set themselves as the owner of all of the imported accounts and your OWD is set to private then none of the true owners of the account records will be able to see these records due to a combination of the record ownership and the OWD.

Role HierarchySalesforce Role Hierachy Salesforce – What Records Can I See?
The role hierarchy is similar to a company org chart (but please remember that these two do not always match!) The role hierarchy will show you within Salesforce how your users relate to each other when assigned a role. A role within Salesforce can have one or multiple users. In the example to we have here two users at the same level, for example the director, channel sales and the director, direct sales would not be able to see each other’s records if the OWD was set to private. However staff higher up in the hierarchy would be able to see records owned by users beneath them in the hierarchy.

Sharing Rules
There may be occasions where the OWDs need to be extended. This is where sharing rules can help! For example members of the services team may need to be able to view all case records when they are closed. Therefore if your OWD for cases is private they would currently only be able to see their own records. A sharing rule can be based on criteria and state that any case with a status of closed can be viewed by any member of services team role. When using sharing rules your only option is to open up access further and not to restrict access! So there you have it. The four key considerations and features to use when setting up your Salesforce instance to ensure that your users can see the right records at the right time! Understanding not only these four in isolation but also how they relate to each other is key in having a secure


Loop through an auto launched flow without using the loop element

In this example I will be cloning an Opportunity with all related products in an auto launched flow without using the loop element!

You can trigger the flow you are about to create in one of three ways:
1) URL button
2) Lightning Process builder
3) Embed flow in a VisualForce page and trigger via a button

First, you will need to create a checkbox on the Opportunity Product (Default False). We will use this as our loop criteria if you like and will allow us to update this checkbox and process all Opportunity Products.

1) Record Lookup – If you are choosing options 2 or 3, you can skip this step and assign variables in your flow certain values. If you are using method 1, you will need to look up the current Opportunity you wish to clone you can then obtain all info needed to create your new Opportunity. Store each field you wish to use as a separate variables.

2) Record Create – You will then need to create the new Opportunity. For this, you simply insert your variable values from step 1 into these fields on your new opportunity. Ensure you give this Opportunity a unique Variable to reference later on in your flow. Like this:
salesforce CRM





3) Record Lookup – This is where you need to look-up any Opportunity products from your initial Opportunity which is going to be cloned. You will need to add the criteria of the checkbox you created earlier to equal false. This is so that we can update this field to True after we have created the clone of this Opp Product for your new Opportunity.



4) Record Create – Create the New Opportunity Products. Insert your new Opportunity ID variable in to the OpportunityID lookup field on the Opportunity record. This will create the relationship between your new Opportunity and this new Opportunity Products.

5) Record Update – Update the old Opportunity Product with a check box equalling true. This will then eliminate this Opp Product from the cycle as we have already just created the clone of this Opp product.

6) Record Lookup – Repeat step 3. Lookup the Opportunity Products with the following criteria. Checkbox equals false. This will only look for opportunity products which have not been already updated. Assign this new Opp Product a new unique variable for the ID.

Salesforce auto launched





7) Decision – Create a decision which will determine if there are any more Opportunity Products to be created and added to your new Opportunity. The Decision will look at your step 7 variable ({!id}) and determine if it is true or false. If it is false, you want this to then go on to step 3 and repeat the whole process again. Your Decision does not need another branch. If the criteria is not met then your flow will simply end!

Your flow should look something like this – Enjoy!salesforce launched decision






CloudSocius – Salesforce Consulting Services