Adding a working hours configuration in the K2 Workspace is trickier than you’d think.
You wouldn’t think this would be a thing.
I’ve a new client running K2 4.7 who has changed the URL for the K2 Workspace. The person I took the client over from could only guess at the correct URL.
How did I find it?
I have a new VM with blackpearl 4.6.9 and Internet Explorer (IE) 11 loaded on it. I’ve never been able to get the built-in reports inside K2 Workspace to display correctly — if they’d display at all, it’d just be for a quick moment — like a flicker — and then, nothing.
I was assuming the issue was something with the display resolution inside the VM. But this morning I got a tip from a coworker that proved otherwise. He told me that IE 11 has a known “flickering” issue. His recommendation — which worked like a charm — was to add the domain to the browser’s Compatibility View Settings list.
Open IE 11 and go to your K2 Workspace. Click on Process Overview to observe the default state — if your display was like mine, you’ll pretty much see a blank white screen. Now for the fix: go to Tools (in the upper right corner of the browser; the gear icon) and select Compatibility View Settings.
In the Compatibility View Settings dialog, add your workspace to the list of sites.
IE 11 should refresh, and your Process Overview report should now be visible!
At this early date there seems to be conflicting information out regarding the new blackpearl’s support for Microsoft Internet Explorer (IE) 11.
As of yesterday, the Compatibility Matrix shows IE 11 as unsupported. Yet the New Features List for blackpearl 4.6.9 says it IS supported, and offers this KB article with instructions for a workaround to allow the K2 Workspace and other portals to render correctly in the browser.
Had this happen today: The business contacted me because they had a worklist item they couldn’t release.
I had a question today about how to determine which action was taken in a specific Process Instance.
As I was walking our business users through the role management features of the K2 Workspace, they lamented that they K2 didn’t give them visibility inside of the Active Directory groups which are assigned to various roles. My quick solution was to provide them with a PowerShell script which would give them the insight they were looking for.