Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When dependent picklists added to the layout SF validation rules work incorrectly #4416

Closed
githubbob42 opened this issue Jan 12, 2017 · 1 comment

Comments

@githubbob42
Copy link
Owner

Mingle Card: 4754
Steps to Reproduce

| | |
|-|-|
|**Version #**|4.0.1.3550|
|**Hardware**| |
|**OS**|windows|
|**Browser**| |
|**Username**|[email protected]|
|**Password**|computer46|
|ORG ID| |
|User ID| |
|RayGun Error ID| |
  
 

  1. login to hunterpeak.herokuapp.com and search for T-B7B-7E8-6EF7 ticket, and go to ticket Details screen.
    This ticket was created in backoffice and has missing value in required field “Custom Text Field”.
  2. click any icon on the sidebar (“Logs” for example)

Expected Result

since there were no change made to the ticket , user should be allowed to go to another screen

Actual Result

_validation msg dialog box pops up stating 
”_Leaving this screen will result in losing your changes because of Validation errors”

Analysis

There is a bug in `salesforce-picklist.js` that causes the picker to try to clear dependent picklists when the controlling field is empty. The bug is that it sets the field to an empty string, even if the field is already blank (the field starts out with a null value).

Related Cards

Test Plan

selenium > srongervalidations.js > Test 7. Stronger validation on details pages test (Ticket page level required field)

Be sure to manually test clearing the value of a dependent picklist.

This has passed the 3 related selenium tests

@githubbob42
Copy link
Owner Author

Pull Request #2206

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant