PDP Prod Issue: Error 500 displayed when exporting conversations in Employee Record page

[telusdcinco]

After implementing #1379 to Production Error 500 displayed when exporting conversations in Employee Record page for select employees like EE 061623.

[telusdcinco]

The employee demographics record for EE 061623 has a dept ID 100-3507. The employee demo department ID is mapped to an Org ID by the nightly process for pulling the employee demographics from ODS.

PDP retrieves department information from PDP thru another nightly process for generating department tree. 100-3507 is no longer available in the currently generated tree. This may happen due to re-orgs within BC Gov.

In Employee Record page, Org ID is used to retrieve the 4-level departments, and is currently required to retrieve the necessary details displayed in the PDF file. The open and closed conversations does not display the 4-level departments. The 4-level department details seems to be not required or may be optional for the generated PDF.

The export displays the error 500 when the 4-level dept details is not found, due to missing Org ID. The issue may not be limited to EE 061623. This issue could potentially happen to other employees with mismatching dept ID to 4-level depts.

The 500 Server Error is NOT a result of the #1379 change.

The simplest fix is to make the 4-level dept optional (or not required) in the Export PDF.

[telusdcinco]

@jessicahjwu

Issue replicated in Test, after syncing employee demo details.

[telusdcinco]

@jessicahjwu I've deployed the fix in Test. The export button is working again.

[telusdcinco]

@jessicahjwu Training data for 061623 is now setup like in Prod. Training is setup with a higher debug setting. Does not show Error 500, but shows the actual error in the PHP code.

[jessicahjwu]

@telusdcinco Not sure why the error shows for PHP code but can we have it fixed? I'd also like to see if we can manually do the following in Test and Training so I can validate the function (as 061623 did not have any completed conversations in Test/Training):

Scenario 1 - Past Employee with a department ID that's no longer existing

1. Put 163102 (Travis Clark) back to dept 100-3507 (in both Test and Training)
2. Manually add a date_deleted for 163102 (In both Test and Training)
3. After testing is completed and confirmed working as expected, revert the changes and link 163102 back to his current department 100-3547

Scenario 2 - Past Employee with a valid department ID

1. Manually add a date_deleted for EE ID 062149 (Zehra Leroy)
2. After testing is completed and confirmed working as expected, revert the changes and link 163102 back to her current department 100-3527

[telusdcinco]

@jessicahjwu

Updates in Test and Training:

EE 163102 updated to dept 100-3507 and date deleted of Jan 1 2024.
EE 062149 updated with date deleted of Jan 1, 2024.

The following processes ran manually for above changes to reflect across pages.

• php artisan command:SyncUserProfile;
• php artisan command:UpdateGUIDByEmployeeId;
• php artisan command:AutoRemoveAccess;
• php artisan command:PopulateAuthUsers;
• php artisan command:PopulateAuthOrgs;
• php artisan command:SetNextLevelManager;
• php artisan command:BuildAdminOrgUsers;
• php artisan command:CalcNextConversationDate;
• php artisan command:BuildEmployeeDemoTree;
• php artisan command:PopulateEmployeeManagersTable;
• php artisan command:PopulateUsersAnnexTable;
• php artisan command:PopulateOrganizationStatistics;
• php artisan command:CleanShareProfile;
• php artisan command:MaintainLogs;

Checking with Warren on why Training is displaying debug page when this error occurs, instead of the generic Error 500 page. This issue is limited to Training only. Test and Prod are following the correct behavior as defined in the config file.

[jessicahjwu]

If the PHP coding error doesn't affect Prod nor our testing to this specific item, let's not dig deeper for now.

[jessicahjwu]

Just a thought - since there are also possibilities to different levels of re-orgs, and since the PDFs are not displaying any departmental information other than the two participant names - I'm wondering if it's possible to make pulling all levels of work unit information optional for past employees to avoid similar issues from happening?
This is how it looks like when pulling a past employee records in MyPerformance:

[telusdcinco]

@jessicahjwu The 4-level dept pulling is now optional for Employee Records export function.

[telusdcinco]

@jessicahjwu Deployed to Training. Ready for your validation.

[jessicahjwu]

Confirmed function working properly as expected, error message did not appear in Training for both scenarios: past employee with an non-existing department ID and past employee with a valid department ID.

[telusdcinco]

MIGRATION NOTES:

Code change only.

[telusdcinco]

@jessicahjwu Deployed to Prod. App pods restarted.