You are viewing limited content. For full access, please sign in.

Question

Question

Current User as Value for Data Filter on Report

asked on February 27, 2017

***Enhancement Request***

I'm in version 10.2 currently.

When creating a report, I want to be able to use the username of the currently logged in User as the value that is being checked.  

I have a process that is automatically kicked off by the system, and is routed through a couple user tasks before the "owner" of the task ever sees it.  The username of this "owner" is stored in the form variables throughout the entire process.

I want to make a report that is available to all the possible owners that shows them a quick summary of the status of all of their tasks, even the ones they haven't yet seen.

I know I can do this by creating an individual report for each user, and setting the data filter up as process_owner_variable is equal to UserName - but it's not ideal to set up several dozen, nearly identical reports, one for each user.  It'd be better to have a report that could check against the username of the currently logged-in user, with a data filter like: process_owner_variable is equal to @CurrentUserVariable.  Then that one report could be assigned to as many users as we needed.

Could something like this be added in a future update?

1 0

Replies

replied on February 28, 2017

Thanks for the request, I bring it back to the team.

1 0
replied on January 19, 2020

Hello,

Any update on this one ?

Thanks

Veronique

0 0
replied on February 1, 2020

This feature is not supported yet.

0 0
replied on February 3, 2020

It's extra set-up, but for our more business critical processes, I ended up making my own reports.

At the beginning of the process, it calls a workflow which does a database insert into a custom database table that I set up, it imports the specific vales we want to report on. At important stages of the flow, the process calls workflow and does a database update with new values (and "status").  Because it's all custom, you choose what gets tracked and reported.

Then set-up a stored procedure in the database to accept search criteria - stored procedure as opposed to a view, so that you can do more complex searches such as:

WHERE
(
  @SearchValue1 LIKE CONCAT('%', database_value1, '%')  --partial match
  OR
  @SearchValue1 = database_value1  --exact match
  OR
  @SearchValue1 = 'All'  --match everything
)
AND
(
  @SearchValue2 LIKE CONCAT('%', database_value2, '%')  --partial match
  OR
  @SearchValue2 = database_value2  --exact match
  OR
  @SearchValue2 = 'All'  --match everything
)

Then a separate business process works as a report.

I use Javascript to hide the submit button (I'll usually hide the autofill button too, and use a button created in a custom HTML element to click it, so that I have more control over appearance and positioning of the button).

Single line fields act as search criteria fields.

Then use the lookup functionality to populate a table (with the as new lines checkbox marked), and that's your report.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.