I’m going through the rules in a SmartForm and associated views to squash a bug, when I came upon an Execute a Form method action in the When the Form is Initializing rule.
Trouble is, the method to call is the Initialized method.
Would that even work?
K2 SmartForms controls are validated in two ways: One is immediate, and the other is rule-based. But the rule-based validation applies to an entire form, not to a specific control.
But does it have to be that way?
My client has just completed upgrading their K2 blackpearl and K2 SmartForms software from version 4.6.11 to 4.7. Here’s something I learned about how SmartForms behavior has changed in version 4’s final minor release.
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.
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 second installment in the Build a Reporting Engine Using K2 SmartForms series.
The concept behind the reporting engine is simple: put the querying power of Transact-SQL (T-SQL) into the hands of business users through a simplified and intuitive interface.
I can’t recall the last time I’d been this excited about building a new feature.
My client has a high-touch, high-visibility application — and I mean “high-touch” more in the sense that a lot of people use it, rather than it gets used often (quantity as opposed to duration, I guess). At the top of my clients’ Christmas list this year was a new feature for building and persisting reports that can be used to monitor the progress of work items through their process.
I wanted to build them a reporting engine that was flexible enough to provide insight from multiple data sources, and with an interface that was as familiar and intuitive as possible.