Automated test framework : set field value not possible on Work notes field

thomas_langlade
Mega Contributor

Hi everyone,

It seems that the configuration step "Set field values" do not work at all with fields typed as journal. (tested on our customer code version + an out of the box code version => same results)

For a new incident for there is no issue, but for an existing incident, I'm not able to set a work note value I have the log below :

FAILURE: Unable to set field 'work_notes' to value 'test'. Field 'work_notes' is not editable. See screenshot

And there is no issue on the Screenshot.

Is there any workaround/fix to manage this field from the automated tests ?

It's important because our customer set the work notes mandatory in some use cases on the incident form, then I can't finish the test properly.

Thanks by advance,

Thomas

13 REPLIES 13

brian_degroot
ServiceNow Employee
ServiceNow Employee

Hi Thomas



Unfortunately, there currently is no workaround to this behavior. There is an open problem for this however (PRB752835), so I would recommend opening an incident in HI. Your incident will be associated to this PRB, and you'll be notified once it's addressed.



I apologize I don't have a better answer to give you, but hopefully some more information becomes available in the near future.



Best regards,



Brian


Thank you Brian,



I will open a Hi ticket for our customer.


I can manage this as workaround (assuming you just want to validate a scenario not based on the work notes field behaviour) :


- 1st step of the test : Update record action => I temporary deactivate the client script that activate the mandatory option on the worknotes field



This is working fine (the related client script is reactivated automatically at the end of the test), the Worknotes remains optional then I can submit the form to the server.



Kind regards,



Thomas


Any updates on this issue?



I've worked around this and updated the ticket through a record update action instead but would be nice to wholly work through the UI.


The workaround worked - thank you!