After a bucket load of theory I was pleasantly surprised when our lecturer gave us our overview for day 3. It was going to be basically just practical – #excite.
During the exercises I got a fairly decent overview of the API and realised that the product is super extensible (blackpearl off course). In our labs we built a custom work list, custom approval form, mini management interface (via ProcessSets) and more.
The support our lecturer gave us was brilliant and apart from the annoying HTML (which I started skipping after exercise 1) all our labs were good.
Here, in no particular order, are the K2 snacks I picked up on day 3:
K2 intends to move away from Kerberos.
The Server Event permission is required for long running processes
Action Rights allow for granular action management per task on each process
Reporting in K2 can assist business to plan resource using Activity reporting
ETL – Extract, transform and load (runs on schedule)
K2 does not support ETL out of the box
EII – Enterprise information integration (real-time data from multiple data sources)
K2 provides EII as part of SmartObjects
K2 surfaces their reports using SSRS and a K2 for SSRS component must be installed for it to work.
K2 ships with the 2 x Reporting Tools; K2 workspace and K2 Process Portal
Custom development tools such as .NET, Silverlight etc are all supported to surface the data
The K2 view flow is available for users to see the real-time look into the process. Take care of this when designing your process
View Flow component can be re-hosted as it simply requires the process id as a query string parameter
Reports may be build using Reporting Services and SmartObjects. To get to the queries, run the SmartObject Service Tester.exe (C:\Program Files\K2 blackpearl\Bin)
Example query: SELECT * FROM Activity_Instance.List inner join Process_Instance.List on Activity_Instance.List.ProcessInstanceID = Process_Instance.List.ProcessInstanceID
By default console logging is enabled
When versioning DLLs, try not to leave the DLL extension as K2 gets slightly confused. Rather use TFS for source control
K2 DLLs need to be GAC’ed on the reporting server if you wish to use the extended reports with K2 blackpoint. Once that is completed, register the extensions in the reporting services configuration XML files to ensure the SOURCECODE data source is available for selection.
I used the same trick on day 3 to warm up my food and enjoyed lunch thoroughly. After lunch, with some extra inspiration, I also added a link to the View Flow report into my custom work list which made me smile.