Question
Cox Communications
US
Last activity: 18 Oct 2022 12:52 EDT
'pr_index_operatorskills' table does not show up all Operator & Skill records
For few of the Operator profiles in our system, the corresponding Skills are not listed under the 'pr_index_operatorskills' table. Any reason why this could be and how to fix it?
***Edited by Moderator Marije to add Support Case Details***
Accepted Solution
Pegasystems Inc.
GB
@SaurabhA7126 I checked INC-234040 and can see this is now resolved.
The support team informed you that the issue came from Declare Index "Skills" which is an OOTB Declare Index causing reports generate incorrect data. Your current configuration would not work with this index in its default configuration.
Solution description: Enabled the indexing conditions option "Index even if source class is blank" allowed for the proper tables to be indexed and reports to generate the needed data from them. You were informed you had to modify the Application Ruleset for this change and implement for every operator, suggestion was to use an agent or a job scheduler to automate this change for all of your operators.
Please could you mark an Accept Solution reply to let other forum users see what was the final solution?
Pegasystems Inc.
IN
Have you tried resaving the operator record and checked if you are able to see the records?
Cox Communications
US
@SriHarsha Anika Yup tried that several times.
TATA Consultancy Services
IN
@SaurabhA7126 Hi Please check Index-OperatorSkills class record and pr_index_operatorskills table, It's holds the operator skill details
Cox Communications
US
@Nadimuthu T Hi yes that's where I am checking but don't see the records listed.
Pegasystems Inc.
GB
@SaurabhA7126 is this causing an actual functional impact?
If you require further help I would suggest that you log a support incident for this. Please provide the INC number here so that we can help track progress.
Cox Communications
US
@MarijeSchillern Hi Marije, here is the support ticket #: INC-234040
Lventur
IN
Pega will be having declare index to update operator skill values in Index-OperatorSkills table.
Declare Index Name = Skills
Class = Data-Admin-Operator-ID
This index is Available rule only, please enable "Index even if source class property is blank" checkbox and try. Maybe any of the source property might not have value inside operator profile, that's why this index is not getting fire and needed information is not getting populated in index table.
This check-box value update should help you in getting fix for this issue, by default this checkbox will not be enabled. Attached screen-shot for reference.
Cox Communications
US
@Gunasekaran Baskaran Thanks. This actually worked, only 1 challenge though. I have to save all the Operator profiles manually for the Index to kick-in so that the underlying table has the right data. Is there any way to automate that?
Lventur
IN
Yes you need to open all operator record and need to do deferred save and commit, then automatically index will get fired.
We are not having any pega OOTB process to save all operators automatically.
You can have activity and directly you can browse all data and then iterate the list and open and do deferred save and commit changes, that should be enough.
Accepted Solution
Pegasystems Inc.
GB
@SaurabhA7126 I checked INC-234040 and can see this is now resolved.
The support team informed you that the issue came from Declare Index "Skills" which is an OOTB Declare Index causing reports generate incorrect data. Your current configuration would not work with this index in its default configuration.
Solution description: Enabled the indexing conditions option "Index even if source class is blank" allowed for the proper tables to be indexed and reports to generate the needed data from them. You were informed you had to modify the Application Ruleset for this change and implement for every operator, suggestion was to use an agent or a job scheduler to automate this change for all of your operators.
Please could you mark an Accept Solution reply to let other forum users see what was the final solution?