We would like to post a link to the workspace report for the process to which , for example, the InfoPath form currently belongs to.
This is similar to that "view process flow" capability, but since we're not using the K2 task pane we'd like the user to go to the report via a click of a button in InfoPath / link [as opposed to manually searching for it in the workspace environment]
Has anyone every done something similar or has ideas about where to start?
Thanks in advance,
+11
Would you like the link to take the user to the 'ViewFlow' of the process instance i.e. http://IISServer/K2V3/Workspace/K2MIS/ViewFlow.aspx?ProcInstID=SomeProcInstID OR the actual Workspace Report containing details down to Activity, Event and Data level i.e. http://IISServer/K2V3/Workspace/Report/ActivityInst.aspx?Link=Report&LinkReportName=AcitivityInstance ?
Regards,
Ockert
Regards,
Ockert
+5
It would be best to have a link to the Workspace Report. The links you provided are helpful, but how would I know where to get all the necessary IDs and such for the specific process?
+11
Hi,
The ViewFlow page should be fairly easy because it ONLY needs a ProcInstID - which you should be able to retrieve from the Serial Number of the client event.
The Workspace Report however will be much more difficult because you do not have access to all the required fields. In Workspace, most of these parameters are stored in session variables. Frankly, I don't know of anybody successfully doing this or if it even would be possible to do. For interest sake, the full URL for viewing Activity instances of a particular Process Instance, looks like this:
http://IISServer/K2V3/Workspace/Report/ActivityInst.aspx?Link=Report&LinkReportName=ActivityInstances&MainTemplID=299&LinkTemplName=All&Folio=ProcInstFolio&StartDate=10%2f21%2f2004+12%3a58%3a35+AM&FinDate=10%2f24%2f2004+11%3a05%3a00+PM&Duration=338785&ProcName=ExportedProcessName&Status=ProcStatus+&ExpDur=0&ProcInstID=73&ProcID=18&ParamStr=ProcInstID%3a73&Folder=K2StudioProjectName
As you can see, there's a lot of info you do not have direct access to.
Hope this shed some light on the difficulties you'll have to overcome if/when you attempt this.
Regards,
Ockert
The ViewFlow page should be fairly easy because it ONLY needs a ProcInstID - which you should be able to retrieve from the Serial Number of the client event.
The Workspace Report however will be much more difficult because you do not have access to all the required fields. In Workspace, most of these parameters are stored in session variables. Frankly, I don't know of anybody successfully doing this or if it even would be possible to do. For interest sake, the full URL for viewing Activity instances of a particular Process Instance, looks like this:
http://IISServer/K2V3/Workspace/Report/ActivityInst.aspx?Link=Report&LinkReportName=ActivityInstances&MainTemplID=299&LinkTemplName=All&Folio=ProcInstFolio&StartDate=10%2f21%2f2004+12%3a58%3a35+AM&FinDate=10%2f24%2f2004+11%3a05%3a00+PM&Duration=338785&ProcName=ExportedProcessName&Status=ProcStatus+&ExpDur=0&ProcInstID=73&ProcID=18&ParamStr=ProcInstID%3a73&Folder=K2StudioProjectName
As you can see, there's a lot of info you do not have direct access to.
Hope this shed some light on the difficulties you'll have to overcome if/when you attempt this.
Regards,
Ockert
+5
I was able to get to the ViewFlow page using the link you've samplified previously; however, when I try to use the native K2 task pane and click on the link there, it attempts to make a link out of my:ViewFlowURL which always produces
instead of the proper link to workspace you've specified.
Therefore, I could construct the link out of some constants and use the Serial number, but it appears this solution will break down upon deployment. Is there some way to check why our set-up is producing this link instead of the workspace one?
Funny enough, I've used the functionality on the sandbox K2 training VPC and have never attempted to use it previously on our real dev environment. It know seems like our set-up is different form what the default K2 task code expects?
http://IISServer/k2v3/infopathservice/K2ViewFlow.aspx
instead of the proper link to workspace you've specified.
Therefore, I could construct the link out of some constants and use the Serial number, but it appears this solution will break down upon deployment. Is there some way to check why our set-up is producing this link instead of the workspace one?
Funny enough, I've used the functionality on the sandbox K2 training VPC and have never attempted to use it previously on our real dev environment. It know seems like our set-up is different form what the default K2 task code expects?
+9
Hi,
Please have a look at the following KB article: http://kb.k2workflow.com/Articles/KB000023.aspx this explains in detail how you can reuse the ViewFlow component in a custom app. ViewFlow as part of workspace is dependant on currents state of Workspace and can cause issues if that state is not maintained.
Please have a look at the following KB article: http://kb.k2workflow.com/Articles/KB000023.aspx this explains in detail how you can reuse the ViewFlow component in a custom app. ViewFlow as part of workspace is dependant on currents state of Workspace and can cause issues if that state is not maintained.
Reply
View our Community Site Map
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.