Question
BPM Company
BPM Company
NL
BPM Company
Posted: Jun 20, 2018
Last activity: Jul 9, 2018
Last activity: 9 Jul 2018 3:18 EDT
Closed
Solved
Why are there 9 non-used DB columns like pxCreateDateTime in an auto-generated declare index table?
If I run the optimize wizard for a page list, it will auto-generate a DB table. I noticed that 9 columns are created that are always empty, and it seems better to just drop these columns. Is there any reason not to drop those columns?
The 9 columns:
- pxcreatedatetime pxcreateoperator pxcreateopname pxcreatesystemid
- pxupdatedatetime pxupdateoperator pxupdateopname pxupdatesystemid
- pylabel
Accepted Solution
Posted: 6 years ago
Aaseya IT Solutions
Aaseya IT Solutions
IN
These are populated, if you copy them from source in Declare Index Rules.
I have use cases in one of the applications where i use these fields from Index tables in PR_INDEX_DATA_AGENTS or PR_INDEX_OPERATOR_WORKGROUPS for auditing purposes.
Guideline i follow us, if the columns are there on source table, i will retain them on Index table.
To see attachments, please log in.
Posted: 6 years ago
BPM Company
BPM Company
NL
Ok, sometimes it might be handy but to always populate that but in most situations not. In my use case, there is no added value of having these as the declare index is meant for reporting purposes on the page list. The pxCreate* and pxUpdate* properties would come from the case table.