I’d recently been plugged into a new project and asked to determine what specific tables or views were needed to move into a new environment. Apart from being unfamiliar with all of the data layer clockwork, I also didn’t have access to the RDBMS.
My first stop was to the SmartForm, to identify the SmartObjects involved. I could find the calls within the rules.
My next stop is the SmartObjects Service Tester. I found each of the SmO’s and right-clicked to view their XML. To get the code out of the form window, I selected all and copied it into a blank text file, then started going through the XML to find the objects they were predicated on.
The XML gave me the names of table or view objects the SmO was built upon. If the SmO was derived from a stored procedure in a package, the XML gave me the name of the package and the name of the procedure, which I could then pass along in a request to the DBA’s.
The format of a SmartObject based on a database object resembles this:
* if you have a SmartObject with a single method, the tag will read
The information under the
<serviceinstances> node will name the service instance and identify the GUID and type (e.g., type=”SourceCode.SmartObjects.Services.SQL.SqlServerService”).
The information under the
<objects> node will identify the objects the SmartObject is based on (e.g., “<object name=’usp_getShoeColors’ type=’StoredProc’ active=’true’ version=”>”).
So in that text file you dumped all that XML into, do a search on “<serviceinstances>” or “<objects>” to get to the information you need fast.
We have a demo instance and a production instance of a particular workflow. I got a frantic call from one of the business people telling me that she didn’t have access to all of the roles in the demo instance that she does in production.
I verified this and attempted to correct it by assigning her to the various additional roles. When I asked her to close her browser, then re-open it and navigate back to her worklist, no change had been made.
This is an enhancement I’ve really wanted to see: SmartForms Rules in version 4.6.9 now have name and description properties. Much like comments in code, these should be immensely helpful for developers new to a project who have to figure out what rules do what.
Commensurate with its release of K2 blackpearl version 4.6.9, K2 also released an upgraded SmartForms platform version 4.6.9.
The prior version of K2 SmartForms was 1.0.7.
Confusing for now, but I’m glad they tied the two together — it seems to make complete sense.
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.
Let’s say a person actions a Process Instance in your workflow, but the item seems to “disappear” unexpectedly — routed to a special queue for workflow administrators because of an error condition. It would certainly be nice if the “actioner” was notified about the problem too, right?
I had a question today about how to determine which action was taken in a specific Process Instance.