New Applicant registration fails when registering through IScript_NewApplicant

The problem happens when the applicant tries to register from the link sent as a notification, when a back office user link the applicant to a JOB. The link directs to an Iscript and through the IScript the details are prepoulated for registration. An error occurs when you register where by the applicant is not allowed to register.

The issue is due to a code reference to CLASSIC being executed for FLUID CG. This issue will occur when CG is FLUID only.

Solution: Force the peoplecode to execute only for CLASSIC.

After installing patch 10 and starting servers I was getting JVM not started issue with some iscript issue in it

To fix that you need to reconfigure app servers and process scheduler server domains.

Later Navigate to :

Enterprise Components > Page Composer Administrator > Installation Administration > Synchronize with Installation button 

click the button "Synchronize with Installation button"

Data Integrity Issue on Internal Candidate Gateway

To fix the data integrity issue generally we need to clear app/web server caches, if required run the Version Application engine. But here this issue is more related to particular page only so we followed below document to fix it. As we found this document after checking error in appserver log.

Data integrity issue while applying job.

Data Integrity error

The data structure from the page does not match the data structure in database.This can be caused by a change in record definition while you were viewing the page.This is a non-recoverable error and current transaction will be aborted.

Getting 'Data Integrity Error' After Attaching Resume In Candidate Gateway (Doc ID 2393677.1)

Cause:

It was determined that the cause was due to PeopleCode program version changed in component HRS_CG_APPLY_FL.

Fix :

To resolve this issue, please perform the following:

1. Manually update HRS_CG_APPLY_FL.GLB.HRS_UPDNMFL_DVW.SECOND_LAST_NAME.FieldChange so its version updates from 1 to 129.
2. Re-test applying for a job
3. Verify that adding a cover letter doesn't log out the applicant and no errors occur

Unauthorized Token has been detected by the System. Please signon with your Userid and Password

Fix:

Please follow the document E-PORTAL: "Unauthorized Token has been detected by the System. Please signon with your Userid and Password" when clicking on pagelet links after upgrade to PT 8.56 (Doc ID 2423420.1)

Delete/empty all the hardcoded URIs from all Node definition under the Portal page and retest the functionality.

         Note there is no real Pcode or standalone application setup need to set these URIs, except the case one             wants to set a portal cluster and/or the developer wanted to fix/hardcode the link PCode generation                   towards a single site.

         However the same coding effect can be achieved in PCode without setting the URI's in such standalone               (non clustered) PS database implementation

Cause of the issue:

New security of PT 8.56 will not allow the site to be switched if this is not part of a portal cluster due to the new PT 8.56 node CheckToken being not validated by such site switch.

Setting the URI's for nodes definitions in such non clustered implementation is not expected.

Oppositely, the URIs are expected to be populated in a clustered PS setup, but in such the new node check token value is expected to be set for all the Default local nodes in the cluster

As far the URI for CRM node is pointed (hardcoded) to the Internet site URI, the PeopleCode Generate: PortalURL and ContentURL PCode functions used in the custom pagelet links are always pointed at run-time to the external site.

All this as far the first place that Pcode looks for at runtime, is to the node URI being set or not, and for a standalone PS app these URIs are not expected to be set..

As far here is not a about a portal cluster (PIH <> CRM) but just a standalone/single PS CRM application (with two sites)  there is no real need to set the node URI!

However, be aware that when using the new ACM templates for setting the IB, could pre-populate the node / portal and content URI's with some, values and this is not expected by the portal and security code if you do not really implement a Portal cluster.