-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Cancelled
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Integrations
-
Labels:None
-
Bug Type:Functional
-
Level:Admin
-
Module:OnBoard - TSR
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
-
Issue Importance:Q2
-
Browser:Google Chrome
1] Suppose there are two tours T1 and T2 in application.
2] T1 is not eligible from system (having eligibility "Terminated") and T2 is eligible from system
2] Add employee and while adding assign T1 through TSR or Bullhorn API
3] Along with this tour, the system eligible tour is get assigned to employee.
4] Login as a partner and navigate to Manage Onboard Status page.
5] Observe the Tour status.
Actual Result:
Only tour system non eligible tour which is assigned through API is displaying, along with this tour if some system eligible tour also get assigned then status for these tour is not displaying. It is displaying only after employee started the tour.
Expected Result:
Non started system eligible tour status should be display on Manage Onboard page.
- relates to
-
NF-1062 Bullhorn Integration: Integration and Flow testing
-
- Closed
-
Hi Seema Gaikwad,
While fixing mentioned issue can you please take care of below scenarios too:
Suppose there are two tours (T1-Assigned through BH and T2-System eligible)
When we assign T1 to employee, T2 gets automatically assigned as it is eligible through system. After employee completes both tours and we try to assign T2 tour again from API then tour assignment successful message is displaying on UI and entry is made under "WTAPIStatusResponseLog" table with status as "Not Started" for T2 tour.