Yesterday my client presented a problem he was experiencing in Chrome that I could not reproduce in IE 11. The issue, as it turned out, had to do with how SmartForms rules are executed through different browsers.
At some point, you might find yourself getting confused by fields with similar names or identical names from disparate sources. It happens.
In K2 SmartForms 4.6.11, there are no rule conditions specific to File Attachment Control events.
— But that doesn’t mean you can’t use them to detect those events.
According to a Computerworld article published 1/31/2019, Microsoft has opted to end support for Internet Explorer version 10 (IE10) next January.
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.
This was a really weird one. A client’s application suddenly suffered from this error in all environments simultaneously. The root cause had nothing at all to do with K2 blackpearl, but it affected the service keys of the instance of a service, which brought down the service and caused the exception.
This post is the sixth and final installment in the Build a Reporting Engine Using K2 SmartForms series.
In previous posts, I talked about some aspects of the T-SQL used to support the engine, and touched time and again on how the actual job of the interface is to build a SQL
WHERE clause to append to a
SELECT statement and execute to return data to a list.
Today I’ll talk a bit about the interface.
My client has an older version of K2 blackpearl/K2 SmartForms, and is preparing to upgrade to the latest minor upgrade in version 4.
Here are my tips for upgrade prep.
This post is the fifth installment in the Build a Reporting Engine Using K2 SmartForms series.
In the previous post I shared some thoughts about database functions that would make life easier when building your reporting engine. In this post, I thought I would wrap up the data layer discussion with a word or two about stored procedures.
This post is the fourth installment in the Build a Reporting Engine Using K2 SmartForms series.
In the previous post I shared some information you might consider when designing your data source and some of the database objects that will directly support the reporting engine — specifically, tables and views. In this installment I thought I’d offer some insight into functions I used when building my reporting engine.