Hi David,
Thank you for your enquiry.
There are a number of factors to consider.
- Which Environment has the file with unwanted changes reach?
- Do you Deploy (or manage Datasets) that also need to be undone
- Do you have nested Releases? (Base / Delta)
- What should be presented to the auditors?
etc...
In general, our recommendation is to progress forward: i.e. undoing a change is really doing another change which reverts to the original state.
Hence, by checking out the file, Edit to undo the change, Compile and Promote, would:
- Reset the file to its original state
- Recompile all dependent objects over the new changes (over the original file)
- Correct any external Libraries (Deployment or Datasets)
- The Audit /Activity Log would reflect the true sequence of events.
Once the correction reaches the highest Environment that had been changed, (except IF PDN), then the File could be dropped from the Task
LMi Main Menu > 2. Work with objects by developer > 22=Remove task assignments
Then, if required, the file instance could also be deleted from the transitional Environment (ITG, QUA), since it should have the same Record Format as the next Environment up.
I hope you find this information useful.
Regards
------------------------------
Jay Mikaiel
Senior Technical Support Engineer
Rocket Software
UK
------------------------------
Original Message:
Sent: 01-25-2022 14:24
From: David Taylor
Subject: Delete a file from a task.
I added an existing file to a task and promoted it to our testing environment. The process correctly recompiled all the related objects. Now, we have decided not to change the file. What is the best course of action?
------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------