Inflectra Customer Forums: Automation filename edit (Thread)Hi, I have added automation values to some testcases, including a linked filename. Once saved, I don't seem able to edit this filename. As it is a typed field that must exactly match details from another system (SoapUI in this case), it is errorprone. I tried to delete the attachment (from the attachments tab), which seemed to succeed, but when I went back to the automation tab, the filename was still populated and unable to be edited. I also wonder what the affect of deleting this attachment will be? Thanks for any help, Charlie en-US(C) Copyright 2006-2024 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/remotelaunch/automation-engines/215.aspxthreadId=215Charlie Stott (cstott@tnsi.com)Automation filename editHi, I have added automation values to some testcases, including a linked filename. Once saved, I don't seem able to edit this filename. As it is a typed field that must exactly match details from another system (SoapUI in this case), it is errorprone. I tried to delete the attachment (from the attachments tab), which seemed to succeed, but when I went back to the automation tab, the filename was still populated and unable to be edited. I also wonder what the affect of deleting this attachment will be? Thanks for any help, Charlie Wed, 14 Dec 2011 04:09:49 -05002011-12-14T14:54:44-05:00/Support/Forum/remotelaunch/automation-engines/215.aspxmessageId=413David J (support1@inflectra.com) There is a minor bug in v3.1 (fixed in v3.2) that causes the field to become read-only. Simply chan There is a minor bug in v3.1 (fixed in v3.2) that causes the field to become read-only. Simply change the automation engine name to -None- and back to the engine name again and it will make the field editable. Wed, 14 Dec 2011 14:54:44 -05002011-12-14T14:54:44-05:00/Support/Forum/remotelaunch/automation-engines/215.aspx#reply413