We just upgraded to 19.2 and I'm trying to switch a round a few things so they conform to the new version of Appian. However I've come across a problem, I'm having issues adding a link to a task report on one of the columns.
This is what the column in the old grid looked like. Note that the variable local!tasks is the task report
a!gridTextColumn( label: "Name", field: "c0", data: a!forEach(items: index( local!tasks.data, "c0", null ), expression: fv!item & " " &fv!index+100 ), links: a!forEach( items: local!tasks.data, expression: a!processTaskLink( task: local!tasks.identifiers[fv!index] ) ) ),
The new version of the grid doesn't have the concept of index anymore so I don't know how to add the task inside the processTaskLink. But when I click on the link on the grid it doesn't do anything. I looked at the recipes on the site and found this one but I don't seem to understand why they are doing it this way. They are creating columns based on an array instead of having set columns with the data for each. This is what I tried to build the column with the new grid. I also tried adding the same foreach inside the dynamic link the way I did in the old grid but that didn't work
a!gridColumn( label: "Name", value: a!linkField( links: { a!dynamicLink( label: index( fv!row, "c0", null ) & " " & fv!identifier, value: a!processTaskLink( task: fv!identifier ) ) } ) )
Discussion posts and replies are publicly visible
As far as the recipe you linked (which i only just looked at) -- that's an example of a grid with columns dynamically generated per the ColumnConfigs return of the queryProcessAnalytics call. This might be useful in certain cases but if you have an established grid with pre-set columns, I assume you wouldn't need or want to do it this way.