You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 13, 2025. It is now read-only.
The general idea of the fix, we should not post to Zapier to update status, if status was not really updated. Added the next unit tests which verify this logic:
should post to Zapier if status is changed to “rejected”
should post to Zapier if status is changed to “shortlist”
should not post to Zapier if status was already “rejected” and updated to “rejected”
should not post to Zapier if status was already “shortlist” and updated to “shortlist”
should not post to Zapier if status is changed to “interview” or another one (not “rejected” or “shortlist”)
should not post to Zapier if status is changed to "topcoder-rejected" (not "rejected" or "shortlist")
Though it appears that there was a second part of issue:
when rejecting JC from RCRM we want the JC status to be Topcoder Rejected (topcoder-rejected)
while when rejecting JS from TaaS we want the JS status to be Client Rejected (rejected)
For this purpose, we added support for a new status topcoder-rejected to Job Candidates.
Verified the status updates between RCRM and TaaS App after the addition of the new status. The syncing of the statuses between the apps is working fine on Dev.
Verified the status updates between RCRM and TaaS App after the addition of the new status. The syncing of the statuses between the apps is working fine on Prod.
Activity
maxceem commentedon Apr 8, 2021
References:
shortlisted
status RCRM Job Candidate Shortlist Status Integration Loop #114Suggested fix:
As have been discussed on Slack we would add a new status
topcoder-rejected
to indicate that candidate has been rejected in RCRM.maxceem commentedon Apr 9, 2021
We found out the root cause of looping and fixed it via topcoder-platform/taas-es-processor#33.
The general idea of the fix, we should not post to Zapier to update status, if status was not really updated. Added the next unit tests which verify this logic:
Though it appears that there was a second part of issue:
topcoder-rejected
)rejected
)For this purpose, we added support for a new status
topcoder-rejected
to Job Candidates.DEV PRs
PROD PRs
SathyaJayabal commentedon Apr 9, 2021
Verified the status updates between RCRM and TaaS App after the addition of the new status. The syncing of the statuses between the apps is working fine on Dev.
SathyaJayabal commentedon Apr 9, 2021
Verified the status updates between RCRM and TaaS App after the addition of the new status. The syncing of the statuses between the apps is working fine on Prod.