Error: K2 SmartForms Content on SharePoint Page Cannot be Displayed

One of my client’s users came to me with an unusual situation — he could reach the SharePoint pages that host the SmartForms application, but none of the SmartForms would appear. Instead, this MacBook user saw messages that read, “The webpage at {URL} might be temporarily down or it may have moved permanently to a new web address.”

The user works in a remote office, and uses the application infrequently, as needed.

What gives?

Continue reading “Error: K2 SmartForms Content on SharePoint Page Cannot be Displayed”

Error: K2 SmartForms Content on SharePoint Page Cannot be Displayed

White Paper: The Impacts on Workflows When Migrating to SharePoint 2013

A new white paper released by Discover Technologies addresses the downstream effect a SharePoint environment upgrade can have on workflows.

Essentially, the upshot is really the difference between K2 blackpearl and other, SharePoint-based workflow solutions like Nintex Workflow: K2 blackpearl has its own workflow engine, and does not require SharePoint to operate. Other, SharePoint-dependent offerings (including Nintex) were faced with a major dilemma when Microsoft introduced Workflow Manager 1.0 (WM), because WM moves the workflow engine OUT of SharePoint, and there is no upgrade path to WM-based workflows. Microsoft did leave the legacy 2010 workflow engine in SharePoint 2013, allowing dependent workflows to run with upgraded content — albeit sans 2013 features. The only way Nintex and other workflow users will be able to take advantage of WM and its feature set (which is incomplete, by the way) is to rewrite their workflows. And if Microsoft doesn’t leave the 2010 engine in SharePoint 2016, those processes will have to be refactored sooner rather than later.
Continue reading “White Paper: The Impacts on Workflows When Migrating to SharePoint 2013”

White Paper: The Impacts on Workflows When Migrating to SharePoint 2013

Word Documents Event Wizard for SharePoint 2013?

K2 blackpearl 4.6.9 has an awful lot of features built in for SharePoint® 2013 support. There is a bevy of wizards for library, list, document set, and document manipulation — copying, moving, changing properties — but the K2 Word® Documents Event wasn’t invited to the party.

The 2007 and 2010 Word Documents Event is a glorious thing because it allows for manipulation of content controls in Word documents hosted in SharePoint via OpenXML. The secret in the sauce is the Word Automation Services (WAS), which is run through SharePoint. WAS also handles Word document conversions to Portable Document Format (PDF) and to earlier versions of Word.

For me the biggest feature of the Word Documents Event is in the content controls. Microsoft Word allows for special fields called content controls to be placed within Word templates. Consider a basic approval process scenario. Let’s say purchase orders have to be approved by people at three levels, and that an audit department requires a record of who signed off and when. A Word Documents Event is perfect for this (given the presence of SharePoint 2010). At the end of the process, these events can insert the names of signatories and the datetimes of their actions into a Word template. Together with other SharePoint events, the completed template can be placed in a specific library, and permissions restricted to ensure the data cannot be changed. One of my first K2 projects involved a scenario of this kind.

Microsoft changed the paradigm of SharePoint starting with its 2013 release. K2 connects very differently to SharePoint in the new, app oriented world than it did in previous versions.

As of today, K2 does not have a SharePoint 2013-based Word Documents Event (though it has been requested as a feature). Fortunately, not all is lost, though — you can use the Word Documents Event in a SharePoint 2013 environment in a limited capacity.

For example, I can use the Word Documents Event to populate a context control from text —

K2-Word-Document-Event (1)

In this case, I want to insert a client company name into a content control (called “client”). For this specific tag, I want to convert the client name to all upper case letters.
K2-Word-Document-Event (2)

The key to making this wizard work in a SharePoint 2013 environment is to use the library’s network location on the Document Location panel of the wizard. Here, I must specify the network path along with the file name and the name of the content control.

K2-Word-Document-Event (3)

Other features of the Word Document Event include inserting content from other Word documents located on SharePoint into the target document. Although we can get away with identifying the target documents through network shares, we can’t do the same for the source documents. Attempts to do so produce Invalid URI exceptions.

I’ll continue to look for workarounds until K2 announces a new and improved Word Documents Event Wizard.

Word Documents Event Wizard for SharePoint 2013?

It’s Way Bigger than Site Columns and Shoes

 

Technologies can mean so much more to the business than being just another “thing” put in by IT. Adoption will drive the return on the investment (ROI) — and we’ll get a far greater ROI by engaging everyone than we would by keeping it hushed up in Systems. So  it’s up to us (in Systems, as the implementors) to promote adoption across the enterprise by creating excitement and demand for the platform.  

Continue reading “It’s Way Bigger than Site Columns and Shoes”

It’s Way Bigger than Site Columns and Shoes