Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 nagavenkata naveen (nagavenkatan1807)
igate global solutions

igate global solutions
IN
nagavenkatan1807 Member since 2015 15 posts
igate global solutions
Posted: Oct 14, 2015
Last activity: Feb 4, 2019
Posted: 14 Oct 2015 9:58 EDT
Last activity: 4 Feb 2019 14:17 EST
Closed
Solved

Declare Pages, The scope of a declarative page (PRPC 5.1-6.3 SP1) can be either Node or Thread?

https://pdn.pega.com/data-management/data-pages-may-have-node-thread-or-requestor-scope#declarepage

In the above link, it is stated that The scope of a declarative page (PRPC 5.1-6.3 SP1) can be either Node or Thread.

I understood that there is no scope called Requestor of a declare page in PRPC 5.1-6.3 SP1 version But I can see the Requestor scope in a declare page rule.

If Requestor Scope is really existing, why it is mentioned in the article like that. What does the article actually meant?

Please clarify me.

and also can some one provide me example when we will go for requestor scope declare page.

***Updated by Moderator: Marissa to add Doc Bug group tag***

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Case Management

Accepted Solution

Posted: 9 years ago
Posted: 15 Oct 2015 11:27 EDT
Mary Carbonara (MaryCarbonara) Principal Knowledge Management Specialist
Pegasystems Inc.
US

Submitted to Pega internal tracking system (PMFe)

BUG-220498 (Doc BUG: PDN Article NID 1145, Data pages may have Node, Thread, or Requestor scope

Section Declare page (PRPC 5.1-6.3 SP1)

Bug report links to this discussion thread.

To see attachments, please log in.
Posted: 9 years ago
Posted: 15 Oct 2015 10:22 EDT
Brendan Horan (BrendanHoran)
PEGA
Director, GCS Knowledge Management
Pegasystems Inc.
US

I didn't go through every version, but I confirmed that Requestor shows up as an option from at least 6.2 SP2 on. So, on the surface, it looks like an in-congruency in the documentation. Mary Carbonara, I'm not sure what our policy is for addressing documentation issues going this far back, but raising to your attention.

Lastly, I'll see if I can find a good example of the use of Requestor level. If anyone in the community has one off the top of their head, please chime in.

Thanks.

B.

To see attachments, please log in.

Accepted Solution

Posted: 9 years ago
Posted: 15 Oct 2015 11:27 EDT
Mary Carbonara (MaryCarbonara) Principal Knowledge Management Specialist
Pegasystems Inc.
US

Submitted to Pega internal tracking system (PMFe)

BUG-220498 (Doc BUG: PDN Article NID 1145, Data pages may have Node, Thread, or Requestor scope

Section Declare page (PRPC 5.1-6.3 SP1)

Bug report links to this discussion thread.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice