Posted: 1 Jun 2015 15:48 EDT Last activity: 17 Nov 2015 12:00 EST
Changes are not getting reflected in HR application
I have perform below activity each time whenver i am making any change in application like adding new field, its not getting reflected at front if i dont perform this activity, is there any alternative for this?
1)In First stage of Candidate case - First step - Collect Personal Info - I mistakenly add Position Applied For and ReffredByEmployee field on Embeded Candidate Page instead of single value property on screen.
2)To clear this mess, i removed both fields from sections and also deleted properties from database and saved changes proeprlly many times.
3) When i am clicking on Create Candidate case, both deleted fields should not be there, but i am able to see them on screen.
So i came to know about this activity - old:pzassemblepreprocess . After running this activity, both fields are not visible on screen which is as expected.
But i have to run this activity each time whenever i am making changes in sections to get it reflected in Candidate case. So is there any alternative for this?
OK, this scenario helps me understand - thank you.
For sure, you should not have to run and activity to clean up the system after making simple changes such as these.
Can I assume you are making changes in the section: SAE-HRServices-Work-Candidate-CollectPersonalInfo?
When you create the UI screens that use page-type properties (as detailed in SAE1), Peag 7 creates a container section in SAE-HRServices-Work-Candidate. And, this container section references (includes) a section from SAE-HRServices-Data-Candidate. It is this section where the fields and associated properties are located.
Next time you want to make a change to a UI section, switch to the App Explorer and navigate to SAE-HRServices-Data-Candidate. Then expand Candidate > User Interface > Section > CollectPersonalInfo_Candidate
Make the change there directly, then report back your results.
The only thing that comes to mind is the system is not refreshing as it should; this could be a stale/dirty cache issue. Also, while you are in SAE-HRServices-Data-Candidate, expand Candidate > Data Model > Property and confirm the properties you deleted are in fact deleted.
But when we are making change in Candidate > User Interface > Section > CollectPersonalInfo_Candidate of SAE-HRServices-Data-Candidate, isn't it same as makinng change in sections by locating them through UI Inspector or through process outline.
And, again, you should not have to use an activity to effect any changes you may make this way.
There could be any number of reasons why this is not working for you. Out of curiosity, I tested this scenario on one of my VMs and it works as expected. Your experience could have something to do with the online exercise environment - not sure.
Would you be OK to set this aside for now and plan on confirming this expected behavior when you get to using a real development environment?
I got struck in the "Conditional Processing " step in the SAE1 part. I have created the Candidate Case type as said in the previous exercises but I am unable to retrieve it from the Application Explorer part in the exercise. When I searched for class " SAE-HRServices-Data-Candidate" it is returning Class not found . This is the class where I previously created properties in for the previous exercises.
P.S: I tried to check through UI Inspector by creating a case, I could find the properties I created before like .FisrtName . The problem started when I tried to create a property for RefferedByEmployee property for this particular exercise.
The Properties you Created should be in the SAE-HRServices-Work-Candidate class and visible in the Application Explorer. Try refreshing the Application Explorer (Right-Click on the Class Group "SAE-HRServices-Work" and select "Refresh All" from the Pop-Up menu). The Application Explorer does NOT automatically refresh whenever you create new Property Records (Rule Instances) in Pega 7. Remember to expand the class that represents the Candidate Class in the Application Explorer, then expand the "Data Model" Category of Records and then expand the "Properties" Records (Rule Type Instances) node to view the Properties created.