1278332 - ITACS 3.8.2-2 p9 ICLv1 Scripted Command GUI Bug When Changing Processors

Status: RESOLVED INVALID

(Bugzilla :: Bugzilla-General, defect)

Description

[steve.koss]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E; InfoPath.3; rv:11.0) like Gecko

Steps to reproduce:

Changing Processors, Decoders, i.e. in the ICLv1 Scripted Command GUI can produce different results dependent on the way the User/Operator makes Processor, Decoder, i.e. selections.

Currently Option 1 works to ensure the right Processor, Decoder, i.e. goes to the correct item in question:

Option 1 - Perform this User/Operator sequence:

1. Change the Processor to Proc 1 (Alternate), Decoder, i.e. from the top of the GUI
2. Then select the line number with the command.

The above two steps will Load the commands correctly to the alternate processor.





Expected results:

Option 2 - In my observation there is a Bug with the ICLv1 Scripted Command GUI. If you perform this sequence of events the first command only gets loaded into the wrong Processor, Decoder, i.e.:

1. Select the command line first
2. Then select the Process, Decoder, i.e. from the Top of the ICLv1 Scripted Command GUI.

Current workaround the User/Operator must select the Processor, Decoder, i.e. first and second then select the command line you with to start commanding.  

Fix the ICLv1 Scripted Command GUI to behave consistently with both SOE & SCripted ICLv1 GUI processes in a future version or patch.

Comment 1

[Frédéric Buclin]

No idea which product you are talking about, but this is not the right bug tracker for this. :)