Tag Archive | DIY

Brad’s October Cumulative Update

As it turns out… everybody needs a CU, not just the ole SharePoint! 🙂

While I may not have posted on my personal blog in a little while, I have been a busy beaver putting out some thought provoking content in other places. So, feel free to peruse the links below to those items (ranging from how-to’s to an analyst webinar on using workflow to improve customer experiences (CX) and even thoughts on the explosion of the cloud scene).

 

xgility-video

Migrating Lotus Notes Databases to SharePoint [Video]

Still using Lotus Notes? Interested in Migrating to SharePoint? Watch (Dean Virag) interview Brad Orluk to learn more about why companies are wanting to migrate away from Lotus Notes, obstacles in migrating form Lotus Notes, tools to help migrate, and so much more..

 

crwueriwiaiqcqbLinkin’ Tasks or How to Get That Pesky Task Item URL [Blog Post]

In this post I cover how to grab task details and surface them on an item level form during the execution of a Nintex workflow. It’s a handy trick that opens myriad possibilities around task management.

 

cloud_computing

Cloud Computing: Past, Present and Future [Blog Post]

In this post I briefly cover the history of the , why it is so important and, interestingly, where’s it going.

 

d1a55b97ce524efbabb00df2236fe4f8

Process Automation Tools Fuel Your Digital Transformation [Webinar]

Enterprises today have a common problem: a platform that slows down processes and disconnects line-of-business operators from IT. “It’s a platform that will eventually burn up around you,” Brad Orluk, technical evangelist at Nintex. Orluk made his comments during a recent CMSWire webinar sponsored by Nintex, “How Intelligent Workflows Power

 

nintex_reg_small

Omni-Channel Customer Experience: How to Drive Best-in-Class Results [Webinar]

Customer experience is rapidly becoming the primary source of differentiation in today’s economy. Businesses that truly understand their buyers and address their needs across multiple channels outpace competitors by a significant margin.

 

Final thoughts…

I’m planning on writing up a post in a few weeks on my thoughts around Microsoft Ignite and where I can see workflow, SharePoint, Office 365 and collaboration going, through the Microsoft lens, over the next year or so. Stay tuned!

 

Advertisements

Let’s build a Nintex workflow that integrates with SalesForce.com!

Now that everyone has become acquainted with the new SFDC Connector for Nintex workflow we can discuss what you need to actually start building workflows that can tie it all together.

Keep in mind, the initial SFDC Connector actions revolve around CRUD operations with SFDC’s CRM and Social (Chatter) platform. That said, I won’t get into how you could leverage each individual action. Instead, I will give you some tips on what you’ll need to get started down the path of being a SFDC / Nintex integration guru by pointing you in the direction of some must have resources and then walking through how to create a basic workflow that will capture a individuals contact details (generated on an iPad via the Nintex Mobile App at a SharePoint event perhaps!), store it in a SharePoint list and then have Nintex Workflow create a Lead that your sales team can nurture into a sale using their favorite CRM, SalesForce.com.

Now, as my favorite PBS artist, Bob Ross, would say, let’s get crazy.

Prerequisites

  1. A SalesForce.com developer account – Since it’s not a good idea to experiment within your organizations production SFDC environment I would highly recommend signing up for a free dev account (by clicking here!) so that you can test the SFDC Connector without the fear of causing any issues with your live data. As this developer instance will be empty you may want to bring some records over to perform a more detailed test but that won’t be necessary at this point.
  2. The Salesforce Field Reference Guide – This document describes all of the SFDC objects and each of their corresponding fields. Click here to get it! This is very important as you will need to know which fields to map SharePoint columns to inside of SFDC.
  3. An Office 365 tenant with a site that has the Nintex Workflow for Office 365 app added to it. If you haven’t done this, log into your O365 tenant, click on the cog and Add an App, visit the SharePoint Store, search for Nintex and Add the Nintex Workflow app and trust it.
  4. Add the SalesForce.com Connector trial to the Nintex Workflow designer via the store. If you’re not sure how to do this, click here to watch a quick video made by my favorite Nintex Expert, Vadim Tabakman, that walks you through the process.

Now, let’s get to it!

Building the workflow: Step by Step

  • Go to your O365 tenant and navigate to the site where you’ve added the Nintex apps. Create a SharePoint Custom List with several columns;

FirstName – Single line of text
LastName – Single line of text
Email – Single line of text
Description – Multiple lines of text
RecordID – Single line of text
RecordURL – Single line of text

  • Now let’s open the Nintex Workflow designer.
  • Inside of the designer we’re going to place two actions on the canvas; Salesforce create record and Update item.

SFDC WF 2014-08-20_9-34-49

  • Now we can open the Salesforce create record action and begin configuring it.

**Before we get into the fields and data to map, you’ll notice is that you will need to specify an email address of an authorizing user. This will allow the action to communicate with your SFDC instance. Be aware that this will send this user an email from Nintex Live requesting access to the SFDC tenant (in a similar way of how one would authorize a 3rd party app to access a Twitter or Facebook account) the first time you run the workflow. If the user has the appropriate permissions in SFDC (this should be your account in the developer environment) they can ahead and select allow the app to access SFDC as seen in the figures below.

Fig. 1

Fig. 1

Fig. 2

Fig. 2

Fig. 3

Fig. 3

  • In the Salesforce create record action we’re going to configure it as follows:

Environment – Production
Authorizing User – Email address of our SFDC dev account
Create – This is the type of SFDC object we would like to create (refer to the Salesforce Field Reference Guide for a complete list). In this example we’ll create a Lead
Fields – 
These are the SFDC fields we would like to populate with metadata from SharePoint. Add all of the fields we mentioned earlier:

SFDC Field

SharePoint Column

LastName {Current Item:Last Name}
‌FirstName‌ {Current Item:First Name}
Email {Current Item:Email}
Description {Current Item:Description}
Company {Current Item:Company}

Lastly, we want to capture the ID and URL of the new SFDC record so that we can refer to it later, perhaps to access it directly or to integrate with via another workflow later.

So next to Record ID let’s add a text variable called ‘RecordID’ and next to Record URL let’s create another text variable called ‘RecordURL’

SFDC create 2014-08-20_11-09-36

Now go ahead and save the action.

  • Open the Update List item action and configure it as follows:

Target List – Current Item
List Item Properties – Select both the RecordID and RecordURL columns
RecordID – On the insert reference bar on the right hand panel, expand Workflow Variables and select RecordID
RecordID – Select the RecordURL variable

SFDC Update Item 2014-08-20_11-07-19

Go ahead and save the action.

  • Open the workflow settings, give your new workflow a name and then configure the workflow to start automatically when a new item is created.
  • Now publish the workflow!

Now let’s run the workflow!

Go ahead and create a new item on the list. Populate the fields and save it. The workflow will run and in a short amount of time you will have a new lead inside of your SFDC instance and the SharePoint item will have the SFDC record’s ID and URL added to it.

SFDC SP Item 2014-08-20_11-16-21

Our record in SharePoint Online

Our new lead in SFDC

Our new lead in SFDC

That’s it! You’ve created your first workflow that integrates SharePoint Online with Salesforce.com thanks to the magic of Nintex! In the future I’ll work on visiting the other SFDC actions that can pull data and tie into the social aspects (Chatter) of the platform.

I hope this post helps get you started on your journey of integrating SharePoint and SFDC. Feel free to let me know what you think and go ahead and share your experiences in the comments below!

 

Iterate through documents in a Document Set

So, I’m a big fan of working with metadata (SharePoint views FTW!) instead of logical hierarchies (folders = boo!) and, on several occasions, I have found myself needing to run an action (a review task or approval perhaps) against all of the documents inside of a SharePoint Document Set.   But when I navigate to the Document Set I encounter a long and somewhat ugly URL for the set itself and begin the tedious work of recording the URL’s for each document.

DocSet324143

So how can I quickly retrieve all of the document URL’s?    Enter Nintex Workflow, a few action configurations and voilà!

Setup

Our Document Library (Doc Lib A in this case), which has been configured with a Document Set content type, and our first Document Set (Test Document Set A).  For realism, I’ve sprinkled it with a few Word documents, with fascinating names (such as the timeless, Test Doc 1-4!).

Then we open the Nintex Workflow Designer and create a new workflow…

For this exercise I will simply be recording each items URL in the workflow history. But, you could use your imagination here… Another scenario with the URL’s would be populating an email notification where users would need to review a document based on its metadata. Another could be that each document in the set would need to be copied to another location for a publishing or retention process, so we would need to collect its location for additional workflow actions.

Building the Workflow

First, we need to create some variables to store our data:

  • textDocSetRaw – A text variable to store each documents Context Item URL.
  • textDocSetName – A text variable to store the isolated and cleaned up Document Set name.
  • colDocument – A collection to store the list of all of the documents inside of the set.
  • textDocumentUrl – A text variable to store each documents URL.

Then we build out the workflow to perform the following tasks:

  1. Extract the Document Set Name
  2. Remove the %20’s in the name and replace them with spaces
  3. Remove the open in browser string
  4. Query our library for all of the documents in the particular set
  5. Record the URL for each document in the workflow history of the Document Set

DocSet32414

Outcome

We can now run this workflow against a specific Document Set and it will return the URL for each document inside. This is a handy tool for my SP bag. Maybe yours now?

DocSet324142

Download an exported version of this Workflow now

Process_DocSet_Workflow.nwf