Create Clickable Interface from Process Report

Question

I would like to create a landing page for an app which displays data from a process report in a grid format. Clicking on a grid row will allow a user to complete remaining user input tasks for that process model instance. This page also needs a button that initiates a new instance of the process model. 
 I currently have an interface that correctly displays the process report data in a grid. However, I cannot figure out how to make this interface clickable to complete an active process instance. I also don't know how to create a button for this page that initiates a new instance of the process model. 
 Do I need to create a report or record type that references the process report, rather than an interface? Any resources for how to do this? 
 Please let me know any ideas or possible solutions.

Mike Schmitt · Accepted Answer

lukevg said: errorMessage=Empty context passed in for report My Upload Process Report 
 This tells you pretty much what you need to know. If you edit the portal report you will see an associated Context, but you're not passing anything into your QPA call. QPA expects either contextGroups , contextProcessIds , contextProcessModels , or contextUsers to be passed in as required depending on the type of portal report. You might need to check the value of cons! 
 Edit: I just noticed that in your older pasted code, you had a contextProcessModels value: 
 whereas in your newer code, you don't have this parameter at all: 
 I'm assuming this is probably the root of your current issue.

Mike Schmitt · Answer

What exactly do you mean by "complete an active process instance"? AFAIK you should be able to grab task IDs from any active instance your report returns and formulate task links to those. I'm unclear what else you might be wanting to do since all of this sounds plausible on SAIL forms.

Mike Schmitt · Answer

I suggest you manually define your columns, instead of looping over local!report.columnConfigs and trying to define a "universal" gridColumn definition that'll handle all columns. I realize the recipe probably suggested that method, but I find it far more cumbersome and confusing than it's worth. 
 Also (and sort of a side note), I don't use a!linkField any more and I tell everyone else that they should avoid it too. It has been more than sufficiently replaced by a!richTextDisplayField, and with far greater flexibility. I don't think that's related to the error you were seeing, though, just a note.

Mike Schmitt · Answer

To clarify, do you see any data if you directly open the process report referenced by cons!Constant1? The data you see there will be the direct source of your a!queryProcessAnalytics call, so if that's now blank then your SAIL grid would be, also. You might want to make sure you didn't change the data source / filtering there to something unintentional.

Mike Schmitt · Answer

Add a read-only Paragraph Field to your form (i.e. right above the grid), set its value to the value of local!report. That'll tell you whether you're getting any queried data locally. You could also copy and paste the queryProcessAnalytics call itself into a blank/unsaved Expression Rule editor and see what happens when you run it there.

Mike Schmitt · Answer

In general that sounds about right -- a!processTaskLink() accepts the ID of an existing task instance and allows a user (with sufficient permission) to open, accept and complete that task. And as you said, a!startProcessLink() allows a user to chain directly into a brand new instance of a processs.

Create Clickable Interface from Process Report

Top Replies