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
------------------------------

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
------------------------------

---

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
------------------------------

Thanks, Jay. That was my first instinct, but I wanted to check.

------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------

---

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
------------------------------

We would usually just check the file out to Development, change it, and promote it back to Testing.


Thanks,

Kevin Monahan (he/him/his)
Systems Analyst

[SIgnature2]

555 Turnpike Street
Canton, MA 02021
781.828.9300 x2785
kmonahan@dxlg.com
dxl.com

Find us at:
[cid:image002.png@01D7B139.161EF9E0] [cid:image003.png@01D7B139.161EF9E0] [cid:image004.png@01D7B139.161EF9E0] [cid:image005.png@01D7B139.161EF9E0]

Upcoming out of office - 01/17/2022 and all Fridays through January 2022

Confidentiality Note: This e-mail, and any attachment to it, contains privileged and confidential information intended only for the use of the individual(s) or entity named on the e-mail. If the reader of this e-mail is not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that reading it is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.

---

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
------------------------------

While that worked, we still needed to do a lot of manual clean up to clear the related files from the integration level.  Was that needed?

------------------------------
David Taylor
Senior Developer
Range Resources Corporation
Fort Worth TX US
------------------------------

---