How to configure the filter condition of RD to enable operators to see the cases created by the others
I created the report definition which enable operators to see the list of cases created by themselves.
The filter condition of the report is ".pxCreateOperator = pxRequestor.pyUserIdentifier"
I want to modify this report definition to enable operators to see the list of cases created by the other operator.
For example, OperatorA can see the list of cases created by OperatorB, and OperatorA can see the list of cases by himself.
How do I modify the filter conditions to meet this requirement?
I think that we can do that by using circumstances, but if threre are more and more combinations of operator, we cannot create the circumstance for one by one.
Best Regards,
***Updated by moderator: Lochan to update platform capability***
Accepted Solution
EY Advisory & Consulting Co., Ltd.
JP
Hi,
Thank you for your support.
I found that ApplicationProfileSetup can be customized.
Best Regards,
Areteans Tech
AU
if operator A wants to see only cases created by him ,
".pxCreateOperator == pxRequestor.pyUserIdentifier".
if operator A wants to see cases created by others but not by him/her then(OperatorB,OperatorC,..),
".pxCreateOperator != pxRequestor.pyUserIdentifier".
if operator wants cases created by him and also others, no need of this condition.
EY Advisory & Consulting Co., Ltd.
JP
Thank you for your reply.
I understand your comment, but it satisfies my requirement.
My requirements are as follows:
1. All operators uses the same report definition.
2. The list of cases created OperatorB can be seen by only OperatorA, the other operators cannot see it.
3. There are many combinations of operators like "2." For example, the list of cases created OperatorD can be seen by only OperatorC. The list of cases created OperatorF can be seen by only OperatorE, and so on.
Best Regards,
Pegasystems Inc.
IN
Hi,
Simply you can give ".pxCreateOperator != pxRequestor.pyUserIdentifier" right..? .It will display cases created by others except yours.
Please correct me if my understanding is wrong.
Regards,
Vinay Reddy :)
EY Advisory & Consulting Co., Ltd.
JP
Thank you for your reply.
I understand your comment, but it satisfies my requirement.
My requirements are as follows:
1. All operators uses the same report definition.
2. The list of cases created OperatorB can be seen by only OperatorA, the other operators cannot see it.
3. There are many combinations of operators like "2." For example, the list of cases created OperatorD can be seen by only OperatorC. The list of cases created OperatorF can be seen by only OperatorE, and so on.
Best Regards,
Coforge DPA
GB
HI,
Try the below steps:
1. Create a table which stores such combination
2. when the user logs in or before running report, get the list of operator's work he has access to.
3. Create a string with list of operators "Operator1","Operator2"..
4. Use the string created in Step 3 as a filter in RD.
You may have to customize the above steps based on your application.
Regards
Bhavya
EY Advisory & Consulting Co., Ltd.
JP
Hi Bhavya,
Thank you for your support.
Would you share the detailed information about the below?
>>1. Create a table which stores such combination
>>2. when the user logs in or before running report, get the list of operator's work he has access to.
>>3. Create a string with list of operators "Operator1","Operator2"..
For each steps, which rules do you customize?
Best Regards,
Coforge DPA
GB
HI,
Few more details to it:
1. Create a table which stores such combination
- I will create a Data type which can have columns like ParentOperator , ChildOperator etc. which stores the relationship between which operators can see whose work.
- You can delegate this if you need business to change it on the fly
>>2. when the user logs in or before running report, get the list of operator's work he has access to.
HI,
Few more details to it:
1. Create a table which stores such combination
- I will create a Data type which can have columns like ParentOperator , ChildOperator etc. which stores the relationship between which operators can see whose work.
- You can delegate this if you need business to change it on the fly
>>2. when the user logs in or before running report, get the list of operator's work he has access to.
- So you can have a Requestor level Data page of type "Page"/User level Page, which gets loaded when the user logins.
- This Data Page can be populated using the data type you created in Step 1. Depending on the level of logic, you can have source of D page as Activity or DT.
>>3. Create a string with list of operators "Operator1","Operator2"..
- In the page you created, have a property, which is concatenated based on the relationship of operator. Pass the current operator as Parameter to D page, and get the child operators and concatenate them to create a string.
Use this property in your report definition filter.
If by chance the D page does not work, then you can create a User level page and use that in the filter.
Hope this clarifies.
Regards
Bhavya
EY Advisory & Consulting Co., Ltd.
JP
Hi,
Thank you for your support.
I have another question.
>>- So you can have a Requestor level Data page of type "Page"/User level Page, which gets loaded when the user logins.
To load the Data page when the user logins, should I customize Data-Portal.ShowDesktop?
Best Regards,
Coforge DPA
GB
Hi
Can you check if an activity named "ApplicationProfileSetup" is there ? I guess you can customize this activity to populate the page.
Regards
Bhavya
Accepted Solution
EY Advisory & Consulting Co., Ltd.
JP
Hi,
Thank you for your support.
I found that ApplicationProfileSetup can be customized.
Best Regards,
virtusa
IN
Hi,
In report definition how to filter if work object is created date and time is greater than 24 hours could you please suggest me.
Thanks
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.