[KULRICE-14272] Fix DocSearchAft and WorkFlowDocTypeAFT Created: 04/Aug/15  Updated: 30/Mar/16

Status: Open
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: 2.6
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Major
Reporter: Claus Niesen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: LongTerm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:

AFT Step: By.xpath: //input[@name='methodToCall.performLookup.(!!org.kuali.rice.kew.doctype.bo.DocumentType!!).(((name:document.newMaintainableObject.parentDocType.name,documentTypeId:document.newMaintainableObject.docTypeParentId,))).((`document.newMaintainableObject.parentDocType.name:name,`)).((<>)).(([])).((**)).((^^)).((&&)).((//)).((~~)).(::::;http://env2.rice.kuali.org/kr/lookup.do;::::).anchor4'] no such element
  (Session info: chrome=43.0.2357.130)
  (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 30.03 seconds
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html

This error is caused by the Java 8 upgrade which causes the order of the property map to be different.

Generated at Wed Oct 21 00:12:15 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.