-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Integrations
-
Labels:None
-
Module:TSR
-
Reported by:Harbinger
-
Item State:Production Complete - Closed
-
Issue Importance:Q1
1. Launch the Postman app.
2. Select “Post” request from dropdwon.
3. Select authorization type as “Basic Auth”.
4. Enter valid User ID and Password.
5. Enter below URL:
http://10.0.2.120/api/employee/addEmployeeTour
6. Pass the require parameter using body.
7. Click on Send button.
8. Employee get added and success message also get display.
9. Search newly added employee using Search Employee page.
Actual Result:
Success message is displaying and employee get added in DB, but it is not listed in Search Employee page.
- relates to
-
NF-180 TSR: API: Add Employee- generate & assign defaults
-
- Closed
-
Kunal Kedari (Inactive)
created issue -
Kunal Kedari (Inactive)
made changes -
| Component/s | Integrations [ 10907 ] | |
| Component/s | TSR [ 11001 ] |
| Status | Open [ 1 ] | In Development [ 10007 ] |
| Status | In Development [ 10007 ] | Local Testing [ 10200 ] |
| Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) |
| Assignee | Saurabh Sablaka [ saurabh.sablaka ] | Kunal Kedari [ kunal.kedari ] |
On Stage for "TSR Demo Company" Security Plolicy configuration is done using First Name, Last Name and Email.
Working as expected on Stage with this configuration only.
| Status | Local Testing [ 10200 ] | Stage Testing [ 10201 ] |
| Item State | Parent values: Stage QA(10202)Level 1 values: Stage Deployed(11602) | Parent values: Stage QA(10202)Level 1 values: Production Deployment on Hold(10224) |
| Item State | Parent values: Stage QA(10202)Level 1 values: Production Deployment on Hold(10224) | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) |
| Item State | Parent values: Stage QA(10202)Level 1 values: Ready for Production(10217) | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) |
Kunal Kedari (Inactive)
made changes -
| Item State | Parent values: Production QA(10203)Level 1 values: Production Deployed(10221) | Parent values: Production QA(10203)Level 1 values: In Testing(10218) |
This issue is related to configuration. The configuration done for Password security should consists of the parameter passed through API.
As per dev comments in NF-508:
*This issue is now fixed. Error was occurring due to company level customization for UserName generation policy. For candidates we accept only email, firstname & last name. So, username & password generation policies should be configured using these fields only.
We need to consider these policies after deployment of enhancement to Stage and Production, setting should be made in advance to avoid the issue. *
Kunal Kedari (Inactive)
added a comment - This issue is related to configuration. The configuration done for Password security should consists of the parameter passed through API.
As per dev comments in NF-508 :
*This issue is now fixed. Error was occurring due to company level customization for UserName generation policy. For candidates we accept only email, firstname & last name. So, username & password generation policies should be configured using these fields only.
We need to consider these policies after deployment of enhancement to Stage and Production, setting should be made in advance to avoid the issue. * Kunal Kedari (Inactive)
made changes -
| Item State | Parent values: Production QA(10203)Level 1 values: In Testing(10218) | Parent values: Production Complete(10222)Level 1 values: Closed(10223) |
Kunal Kedari (Inactive)
made changes -
| Status | Stage Testing [ 10201 ] | Production Testing [ 10202 ] |
Kunal Kedari (Inactive)
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Production Testing [ 10202 ] | Production Complete [ 10028 ] |
Kunal Kedari (Inactive)
made changes -
| Status | Production Complete [ 10028 ] | Closed [ 6 ] |
| Transition | Time In Source Status | Execution Times |
|---|
|
7d 4h 22m | 1 |
|
2s | 1 |
|
23m 16s | 1 |
Kunal Kedari (Inactive)
made transition
-
|
32d 22h 5m | 1 |
Kunal Kedari (Inactive)
made transition
-
|
8s | 1 |
Kunal Kedari (Inactive)
made transition
-
|
2s | 1 |
This issue is related to configuration. The configuration done for Password security should consists of the parameter passed through API.
As per dev comments in
NF-508:*This issue is now fixed. Error was occurring due to company level customization for UserName generation policy. For candidates we accept only email, firstname & last name. So, username & password generation policies should be configured using these fields only.
We need to consider these policies after deployment of enhancement to Stage and Production, setting should be made in advance to avoid the issue. *