Did you know that there’s a database operation that occurs with each activity in a K2 blackpearl workflow process?

In short, the more activities you have in a process, the more database writes occur within each running instance of the process.

For better performing process instances, try to limit the number of activities you have within them.

I have a particular client who requires me to develop their solution by remote desktop connection to a server. A recent failure on that server forced the removal and recreation of accounts. When I was able to RDP back in, I found that I had no shortcuts of any kind on my taskbar — not even to Windows Explorer. With no access to Windows Explorer or a desktop Start menu, I couldn’t get to anything else in the OS. So my first order of business was to get to Windows Explorer.

Continue reading

K2 has released a statement announcing the immediate end to security updates or technical support for Microsoft Internet Explorer versions earlier than IE 11.

On Tuesday, January 12th, Microsoft ends support for Internet Explorer 8, 9, and 10. The end of support means that these older versions of Internet Explorer will no longer receive security updates or technical support.

As such, K2 will also no longer release fixes or patches for these older versions of Internet Explorer. You may continue using the older browser versions with K2 products, but if any issues arise K2 will not release fixes or patches for unsupported browser versions. You will be required to upgrade to a supported version or use a different supported browser.

Endgaget reports that these older versions still have an estimated 20% market share.

I’m working on a little home project right now that does some examination of the current day of the week against a database table containing events by year and week number.

Curious to know if my event for this week would run as scheduled, I did some checking. Microsoft SQL Server thinks that we’re currently week 53 of 2015, instead of week 1 of 2016.

But Outlook is telling me we’re in week 1 of 2016, because January 1st is on Friday! How can this be?

My workaround was to duplicate the event for week 1 of 2016 in a new record for week 53 of 2015, but the reason seems worth exploring.

Based on various articles I’ve read, including this post I found on Stack Overflow, I’m led to believe that SQL Server is smart enough to know the difference between the last days of the current year and the first days of the new in the context of the week that bridges the two years.

Any days in the current year that extend beyond week 52 (starting on Sunday) are called week 53, and any days in the coming year in the same calendar week (up through Saturday) are considered week 1. The next Sunday starts week 2.

Example: This year, December 27th fell on Sunday, and January 1st is on Friday. So, from a SQL Server perspective, Sunday, December 27th through Thursday, December 31st are week 53; Friday, January 1st and Saturday, January 2nd are week 1, and Sunday, January 3rd through 9th are a full week 2.

So my week 53 workaround should work as long as the event day is before January 1st.

SQL Server also has the concept of the ISO WEEK datepart. Ask your doctor if it’s right for you.

K2 has released a second coldfix for its latest version of K2 blackpearl. The fix corrects an issue concerning workflow deletion in the Management Console. This second fix follows one released on July 7th related to how item references work.

• If you have downloaded but not yet installed K2 4.6.10, please download the latest software which contains the fix, dated 16 July. You can find it on the K2 Partner and Customer portal.
• If you have already installed K2 4.6.10, please download the coldfix and follow the instructions at KB001710 (Known Issue: Delete workflow coldfix for K2 4.6.10).

The KB article steps you through the replacement of several DLL’s in the original 4.6.10 package, and the execution of a couple of SQL scripts. If you’ve downloaded that package but not installed it, a more recent package already contains the fix.

K2 has released a coldfix for its latest version of K2 blackpearl. The fix corrects an issue concerning how item references work.

According to the technical bulletin,

• If you have downloaded but not yet installed K2 4.6.10, please download the latest software which contains the fix, dated 6 July. You can find it on the K2 Partner and Customer portal.
• If you have already installed K2 4.6.10, please download the coldfix and follow the instructions at KB001708 (Known Issue: Item References coldfix for K2 4.6.10).

The KB article steps you through the replacement of two DLL’s in the original 4.6.10 package. If you’ve downloaded that package but not installed it, a more recent package already contains the fix.

K2 blackpearl 4.6.10 has been released.

The blackpearl 4.6 compatibility matrix shows no change in compatibility from 4.6.9.

blackpearl 4.6.10 includes support for DocuSign eSignature integration, and the ability to see comments and attachments directly in a process’ view flow, and, for SmartForms, the ability to designate specific views on a form as anonymous — allowing anyone to execute it. SmartForms 4.6.10 includes ListBox controls and a location-based services control that can retrieve a user’s current location. See the release notes for additional details, important considerations, and applicable prerequisites.

According to the 4.6.10 developer reference, an OData service broker was added to the available service brokers, paging and sorting has been added to custom service brokers, and the Folder Breadcrumb and the Date-time Picker controls have been added to the smartwizards.

K2 now offers two ways to update your environment. For 4.6.9 environments, download the new update installer (248 MB). Updating older environments will require the combined installer (a hefty 758 MB).

Each package contains:

  • K2 blackpearl 4.6.10
  • K2 SmartForms 4.6.10
  • K2 Smartforms Control Pack 4.6.10
  • K2 for SharePoint 4.6.10

Finally, K2 was very careful to note that Google has deprecated support for Microsoft Silverlight in its Chrome browser (versions 42 and above), which affects a user’s ability to consume View Flow and K2 for SharePoint 2010. A workaround is offered which discusses how to re-enable the browser’s NPAPI setting.