Lifecycle and Environment Cleanup

No-Code Platform
1

Hi there, please can you give some guidance on how we can clean up 25.1RPDevPartner before we start developing in there full time, if possible.

  1. We currently have lifecycles which were copied over from 24.2 and even before those versions. Those lifecycles have objects in them and they are still active. Would it be OK for us to run a data transform to mark those workbenches as inactive although there are objects in those LCs that are branched/copied/created/customised, etc? If not, what would the best option be to reduce the number of lifecycles that is preferably not manual?
  2. In xxxx_test, we have a bunch of customisations from testing in different LCs. Some of those LCs may not exist. What would be the best approach for us to clean out lifecycles with the customisations in xxxx_test? Will a DT allow us to delete customisations?

Any suggestions on this would be appreciated. Thank you.

2

@claire.minnaar

  1. You cannot mark a lifecycle as inactive, unless all the objects have been unlocked or merged. Do some of your lifecycles still have checked out objects? Lifecycles is Platform family so not sure if you can run DT on those objects. Checking to see if there any other options.
  2. No a DT will not allow you delete customizations. So you are seeing customized records, let’s say in app builder, tied to lifecycles that do not exist or were inactivated?
3

@viviana.s Answers to your questions below - thank you for getting back to me:

  1. Yes, when the 25.1RPDevPartner was created, it took a snapshot of 24.2RPDevPartner and there are a workbenches in those snapshots. Those are still active and have objects checked out as a result. This would have happened when moving from 24.1 to 24.2 and potentially versions before, so those workbenches will be sitting in 25.1RPDevPartner potentially as well.
  2. Some lifecycles are inactive in xxx_auto, but the customisations are there. I am not entirely sure if customisations exist for lifecycles that don’t exist - not sure if a script or something could be created to know that answer for sure.

Thank you.

4

Unfortunately you will need to manually clean these up. We will enter an idea in the backlog to make this easier/smoother in the future for our Partners who develop and deliver solutions on our platform.

  1. You will need to unlock the objects from the lifecycle before you can inactivate the lifecycle. I would suggest you also delete those objects from the lifecycle before you inactivate
  2. For your _test environment, you will need to activate the lifecycle to delete the customization and then deactivate the lifecycle.