We have section named Caseinformation in Work- class in that section we are embedding a section named as “pyCaseInformation” with page context as “Use Current page context”. But when i try going to the section in the portal and live UI it i found out it is calling a section which has same but in different class which is WKTAApp-RMS-Work-ICM-Subject-Initiate.
I know i am wrong but through rule resolution the section should be picked from class hirearchy of Work- class right???
@AbhishekB16577181 As you have selected “Current page context” , assuming that at runtime that section is being invoked at work object context , so the primary context for that section would be your work object class (Not the Work-) & as per your current application inheritance most likely for your work object class the right candidate would be the section from WKTAApp-RMS-Work-ICM-Subject-Initiate class.
No, as per rule resolution the system will first check the rule availability in your application defined classes before moving to Pega’s Work- class. In your case it found the section is your application defined class WKTAApp-RMS-Work-ICM-Subject-Initiate first. If this section withdrawn then it would have referred the Work- class provided there was nothing else present in the inheritance path.
