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

1
Replies
328
Views
 Akash Sinha (AkashS1762) VirtusaPolaris
VirtusaPolaris
IN
AkashS1762 Member since 2016 28 posts
VirtusaPolaris
Posted: Mar 27, 2019
Last activity: Apr 4, 2019
Posted: 27 Mar 2019 6:53 EDT
Last activity: 4 Apr 2019 8:23 EDT
Closed
Solved

pySubjectType Property in pxInteractionHistory data set

Report

Hi,

In Pega 7.3 I see that there are two keys to query data set pySubjectID and pyGroupID. But in Pega 8.1.3 it has pySubjectID and pySubjectType. What could be the reason to change the property? What is the use of this new property?

Thanks,

Akash

***Edited by Moderator: Pallavi to update platform capability tags***

Pega Marketing Pega Platform Low-Code App Development

Accepted Solution

Posted: 4 years ago
Posted: 1 Apr 2019 3:18 EDT
Pawan Narain Singh (pawann) Swedbank AB
Swedbank AB
SE
Report

Hello Akash,

Pega® Platform 7.4 introduces the pySubjectType attribute that is used in interaction history aggregations. This attribute is populated for interaction history records that were created in release 7.4. For records that originated in earlier releases, the attribute must be set in the following scenarios:

  • Single-level decisioning frameworks that use interaction history.
  • Multi-level decisioning frameworks where interaction history is used by two or more levels of strategies that are defined on different classes.

 

You can find more about this property in this release note.

Let us know if that helps!

Show More

Hello Akash,

Pega® Platform 7.4 introduces the pySubjectType attribute that is used in interaction history aggregations. This attribute is populated for interaction history records that were created in release 7.4. For records that originated in earlier releases, the attribute must be set in the following scenarios:

  • Single-level decisioning frameworks that use interaction history.
  • Multi-level decisioning frameworks where interaction history is used by two or more levels of strategies that are defined on different classes.

 

You can find more about this property in this release note.

Let us know if that helps!

 

Thank you,

Pawan


Show Less

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