Additional metadata desired for class definitions
There are many times that we, in a COE reviewing applications, wish to see a class-based view of an application.
That is, we'd like to understand all the classes supplied by applications, and understand things like how it's populated. This helps us effectively review the design.
It would be grand if this could all be captured within Pega, rather than maintained outside.
I'm open to evolving the terminology. "Foreign keys" is obviously a term out of RDB nomenclature, but the concept in general (of what things this relates to) applies to data architecture in general.
Through 7.1.5, the Custom Properties in a rule are still under-utiliized. We'd love to say for a given rule type, these additional fields are required to be filled out to go beyond the usage/description, (I suppose we could have a separate case to capture this, but that seems like overkill)
There are many times that we, in a COE reviewing applications, wish to see a class-based view of an application.
That is, we'd like to understand all the classes supplied by applications, and understand things like how it's populated. This helps us effectively review the design.
It would be grand if this could all be captured within Pega, rather than maintained outside.
I'm open to evolving the terminology. "Foreign keys" is obviously a term out of RDB nomenclature, but the concept in general (of what things this relates to) applies to data architecture in general.
Through 7.1.5, the Custom Properties in a rule are still under-utiliized. We'd love to say for a given rule type, these additional fields are required to be filled out to go beyond the usage/description, (I suppose we could have a separate case to capture this, but that seems like overkill)
| Description | Auto-generateable from Pega? | |
| Classname | Yes | |
| Table | associated table | Yes |
| Logical Key | Properties making up the key | Yes |
| Primary key | Primary key of the table. (pzInsKey for standard Pega tables) |
Mostly |
| Sample Key | What is it expected to look like? | No |
| Growth rate | Records added/month | No - could be calculated from prod |
| Avg Record Size | No - could be calculated from prod | |
| Who adds | Which part of the process adds a record here? | No |
| API for adding | What is the API/activity for adding records? | No |
| Work key property | Which property points to the work key | Yes |
| Foreign keys | What properties point to foreign tables? (IOW, is this associated to the case, or other objects?) | |
| Indexed columns | Which columns are indexed? | No |
| Confidential fields | Which columns contain confidential information? (could indicate which would be sanitized) | No |
***Updated by moderator: Marissa to close 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.