-
1. Re: Has anyone cloned the Change BO?
elysey May 14, 2016 6:23 PM (in response to tjordan)Hi Trichelle
There's no function to clone existing business objects at the moment however any reason why you odn't want to just utilise the same object with a different category? Or shouldn't you be utilising the release module for development requests in this case?
-
2. Re: Has anyone cloned the Change BO?
tjordan May 15, 2016 6:25 PM (in response to elysey)Hi Elyse,
Thank you for your reply. I am looking for a different module if you like, I getting a consultant out in a few weeks and will create a separate Object for any development request. I want it then to pass through the Change and Release phase separately.
Thank you again,
Trichelle
-
3. Re: Has anyone cloned the Change BO?
davidjohnson Aug 8, 2016 3:33 PM (in response to tjordan)Hi Trichelle;
Curious as to how you dealt with this. Can you stand up another environment? We're considering using UAT for our testers, while we develop the new workflows in the staging environment. We plan to use HEAT Cloud Support to promote from Staging to UAT. We will handle small promotions, such a few XML workflows.
Thanks,
David -
4. Re: Has anyone cloned the Change BO?
tjordan Aug 22, 2016 3:50 PM (in response to davidjohnson)Hi David,
I decided not to go ahead with that, rather made a new change form with different workflows etc to get around creating a new BO.
Good luck!
-
5. Re: Has anyone cloned the Change BO?
davidjohnson Dec 2, 2016 8:46 AM (in response to tjordan)Hi Trichelle;
HEAT created a quick action to clone a change for us - copies over Details tab (except the Start and End Dates which we requested be nulled out), CIs and the overall Risk Level. One caveat - HEAT could not clone the answers to the Risk Level questions.
Cheers,
David