Discussion
VIRTUSA
IN
Last activity: 4 Oct 2018 13:54 EDT
Properites: Page List Vs Page Group
How we can decide that, which property type (ex: Page, Pale List, Page Group) we can use.
I mean to say when we want create a property how can we decide that, weather its a page or page list and page group?
Can any one please provide answer to this question with an example.
Thanks in advance!!!
**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.
Square BPM Inc.
CA
Both are lists, one is keyed other one is not. I don't think there is general guideline one when to one vs the other. It very much depends on your design and preference.
I try to use Page Group as much as I can since it allows keyed access.
United Guaranty Corporation
US
Page group can be used only when you can define a key for the list of pages. For example, items in a shopping cart is just an enumerated list, you cannot define a unique key to each item. Whereas, when you talk about a list of employee profiles, you could use either page list or page group, but I prefer to use a page group as you can directly access profile of "Employee X", rather than iterating the list of profiles and finding the profile of an employee.
Hope that makes sense and the determination of whether to use page group vs page list is primarily use case driven.
Telstra
AU
To answer your question in a simple way,
Page - When you want to get data of something which doesn't repeat. Eg. .EmployeeData (Property of type Page) - One employee has only one record in database
Page List - When you have number of items for something which cannot be grouped by some property. Eg. .EmployeeAccounts (Property of type Page List) - One employee can have multiple accounts.
.EmployeeAccounts(1).Type= LAN
.EmployeeAccounts(2).Type= Sharepoint,
.Domain=External,
.EmployeeAccounts(3).Type= Sharepoint
.Domain=Internal
Here, you can see even though type is same, domain is different, so, it cannot be grouped by type
Page Group- When you have number of items for something which can be grouped by some property which is only text without special characters Eg. .EmployeeAccounts (Property of type Page Group) - One employee can have multiple accounts.
.EmployeeAccounts(LAN).ID= a123456
.EmployeeAccounts(Sharepoint).ID= a123456,
.EmployeeAccounts(Outlook).ID= Proprietary information hidden
Here, you can see it's easy to group.
VISPL
IN
Hi,
Can anyone please tell me how to add page group property in section in pega 7.2 and also how add property in page group?
Requirement:
want to create single page for address containing these three properties and want to access same fields for Office and Home Address
Address
- Street
- City
- Postal Code
Pegasystems Inc.
US
Hi Ashwini,
1. You can create ABC-Address class with those 3 properties in it.
2. Create a Data Page D_Address with Object type ABC-Address class.
3. Now in your Office class, create a single page property with Page Definition ABC-Address. Here data access can be done manually or refer to a data page D_Address based on your requirement.
4. Similarly in the HomeAddress class.
Hope this helps you.
Regards
Mahesh
VISPL
IN
Hi Mahesh,
Thank you for your reply.
I want to create an address property of type page group and inside that i want to add Street, City, etc. and can you please tell me how to create Street, City property in a page.
And want to display it in same UI form as Home Address and Office Address using same Address page.
Thanks.
Pegasystems Inc.
US
Hi Ashwini,
You can create a property of type Page Group in your class and specify the Page Definition with your Address class then you can see all the properties of Address in your newly created Page Group as shown in my attachment.
Regards
Mahesh
NCS Pte Ltd
SG
Hi Ashwini,
I believe I have the same issue as yours and I found out the answer myself so there might be another way to accomplish this.
Once you created the Page Group property with Page definition of "Address" (or whatever your original data class is),
- Create a Section (User Interface -> Section) in either your work class or data class (data class is preferred since it can be reused across multiple work classes)
- In the Section's Design tab, put all the input you need
- Double click on the input
- In the Property box, in case of "street" text input, type --> .Address(home).street
- Do step 3 and 4 for all the Address property
In this case, 1 section can only be dedicated to 1 address type e.g. home,office.
I guess it's not really "reusable". But at least you can customize each address type.
Note that I am still new to Pega and hence this might not be the most efficient way to do it.