Skip to main content
Hi everyone,

I am very new to K2 so perhaps this will not help you as much as it has me as I could be doing things the long way round, but I would like to share a solution to a problem that I had.

I am developing .aspx vb.net (2003) pages whereby I am querying a SQL database quite extensively and although debbuging the Plan page is fairly simple as this can be done directly in VS, the subsequent Client pages are not as easy to debug should one be accessing them from the K2 Web Workspace. The recommendations that I have seen on the forums is that the K2Rom should be used with a standard .aspx page rather than a SmartForm page should more complex solutions be needed.

Always wanting to take the shortest possible route, I added a simple worklist .aspx page that is my project start page, to my VS project, looped through the worklist items and populated a combobox with them specifying the serial no as the text value. When selecting an item from the combobox, I redirect the page with the serial number required for Client pages to the next Client page within my project and I can debug to my heart's content!

If there is an easier way of doing this - please let me know. In the meantime I can use a standard SmartForm with all the controls linked to my process without having to access the K2Rom.

Hope this helps someone, somewhere...
Thank you for the feedback Filia.

If you know the URL of the task item you want to open, you can also start debugging the solution with the plan page, then paste the URL of the client event into the browser window's address bar and hit enter/go - that will load the client page into the 'debug mode' IE instance and you can debug away.

Reply