I’m working for a client new to the world of software development and unencumbered by familiarity with development lifecycles and environments. (Not their fault; it just places the onus on us to teach them.) I’m not sure how long my company has been working with them; I just joined the project a couple of months ago.
Somewhere in the past, some percentage of the developers on the project acquiesced to doing development work in their production environment, probably because they were asked to do so to help them with some tight deadlines or urgent requirements. The short term effect was that it helped the client meet whatever deadlines or requirements they had; the long term effect is… disastrous.
Microsoft had originally expected to support the browser until the sundown of Windows Server 2012, scheduled for October 10, 2023, but it is now ending IE10 support over three and a half years earlier than anticipated.
I’m supporting an application that has a large number of rules inside the SmartForms. My task is to change some text. Instead of combing through all of the views and forms to find the text I need to change, I thought I’d try to work a little smarter.
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”→
I freaked out a little in my first look at K2 blackpearl 4.6.9 — I didn’t see the Environment Fields node in the Object Browser.
Oh no! Why would they take away the environment fields? I RAVE about these things, and for good reason — they allow for string values to be injected into a process at runtime. I use this magic in the form of e-mail text and other data the business might want to tweak at will, because it saves me from having to recompile and redeploy the solution — a workflow process will grab the value when it needs it.
Fortunately, one of my team members was able to talk me down from the ledge: Environment Fields are still very much a part of blackpearl — the folder just won’t exist until you create an environment field.
Here’s how: Open your blackpearl project, and navigate to the object browser. Right-click on any of the existing nodes, and click on Add new field… .
You should see the familiar Add New Field dialog appear. Here’s the key: Select Miscellaneous Field in the Item Type drop down list. Name your field and give it a value. Fill in the Field Description field for extra credit and click the black OK button in the dialog’s lower right corner.
The Object Browser should refresh. A wild Fields node appears!
It’s super effective!
By the way, if you remove the single Environment Field you just created, the Fields node will disappear again.