Completed
Last Updated: 28 Aug 2014 12:54 by ADMIN
ADMIN
Cody
Created on: 26 Feb 2014 21:42
Type: Bug Report
1
Changes to FrameInfo may not be saved
When you close a project, then reopen and make changes to the FrameInfo of a frame in Elements Explorer, then close the project again, those changes will be discarded.

Because element definitions (and their frames) are actually contained in test files, doing anything to the test itself which uses that element will mark the test "dirty" (it will be in bold in the Project view), then the changes will be saved. Simply unchecking and rechecking the step enabled checkbox is sufficient. The trick is that you must do this on the test in which the element is actually used by. Doing this on just any random test will not be enough.
5 comments
ADMIN
Shtilianov
Posted on: 14 Apr 2014 10:43
It is included with the latest release. 2014.1.410
Tushar
Posted on: 14 Apr 2014 06:30
Can you please let me know on what version do we have this fix available?
Srinivas Maheedhar
Posted on: 05 Mar 2014 08:23
Thank you for fixing this on priority
ADMIN
Shtilianov
Posted on: 05 Mar 2014 08:00
Problem is fixed. Fix will be available with the upcoming service pack.
Tushar
Posted on: 27 Feb 2014 07:01
The workaround works fine. But if the element is being used by multiple steps accross different tests in a project, Do we have to do the unchecking-rechecking for all the steps which are using the element?