Had a request to be able to duplicate a change. Meaning, if/when a change is closed having an option to create a new change with all the information from the closed change propagated to a new change. A practical example would a patching change that just requires updating what new patches are being implemented. This could be a template design, but we fear going down this road as it could create a long list of templates for all the unique changes. Wouldn't it be easier to give the option to duplicate a change, capture all the old information and create a new change/lifecycle? I don't want a parent-child type relationship. I'm looking for a way to create a new change lifecycle from an change whose lifecycle status is closed.
first thought would be to use the "Create Child Change" action and Value types to copy the information you want to preserve from the original change.
If you do not wish to mark this as a Child, you can add a new collection of change on change and name it to anything you like. Then you can create new changes out of the existing one with the "Create Related" Object action of this collection.
See https://help.ivanti.com/ld/help/en_US/LDSD/11.0/Default.htm#003 Designer/Object Designer/Actions.htm#kanchor926
Thank you. I'll try this out in my lab.