Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
11 replies
Subscribers
4 subscribers
Views
7553 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Reports
Business Data from Process Variable required in Process Report
kumaraveln
over 8 years ago
We have a process report in the context of a single process model. This process model has around 20 - 25 nested sub processes with human task(s) in it. Our requirement is to show a task report from where a group of users can view the status of various tasks (active, assigned and completed) and do reassignment if necessary.
Now we have no issue in showing the task related metrics like taskName, status, assignedTo, etc. But we also need few business process data (such as requestId, requestType, businessUnit) to be shown in the report (and option to use filters on them). All these process data are present in one particular CDT which flows across all the process models.
But here the issue is the name of process variable used in each sub process are different (since they were created by different people for various purpose and later integrated for this workf...
OriginalPostID-241727
Discussion posts and replies are publicly visible
Parents
0
kumaraveln
over 8 years ago
... cdt'. Doing so will work at least for new instances when we use index(pv!gblRequestDetails_cdt, "requestId", "") for column
Appreciate if anyone could give some better idea or throw some pointers. Our priority is to achieve this with minimal changes in process models as they are heavily nested. In worst case the process data should be available in report at least for the new instances if not for all instances. Any possible work around in the process report too would be great.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
kumaraveln
over 8 years ago
... cdt'. Doing so will work at least for new instances when we use index(pv!gblRequestDetails_cdt, "requestId", "") for column
Appreciate if anyone could give some better idea or throw some pointers. Our priority is to achieve this with minimal changes in process models as they are heavily nested. In worst case the process data should be available in report at least for the new instances if not for all instances. Any possible work around in the process report too would be great.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data