Any lessons learned from Lifecycle changes?

[sdrzewiczewski]

we are about to do some legacy data cleanup.

• One project is to remove some states from our current lifecycle.


• One project is to reassign lifecycles for objects not using the incorrect lifecycle.

If you have done this a couple of questions:

1. If you've removed states from your workflow, did you change legacy object to some mapped state or did you leave the old versions as is?


2. If you did change the states, did you do this just for the latest, or all objects?


3. If you reassigned lifecycles, what was the best approach to do this in mass?


4. Did you reassign just the latest or all objects?

Were there any issues you or things to be aware of that would be helpful to know so we can plan for this?

Thanks,

Steve D.

[AL_ANDERSON]

I'm not sure if this is exactly what you are looking for, but every time
we update a lifecycle template to add a state or change an ad hoc access
control rule, we have to run this script where the main object table
(underlined in red text, below), and the lifecycle template name changes
(underlined in blue text, below) in order to make sure that the latest
iteration of all objects using that template point to the latest iteration
of the lifecycle template. This is so common that there really should be
a "Publish" button in the Lifecycle Administrator, but until then, here is
the SQL.

update wtchangeactivity2 set ida3a2state = (
select ida2a2 from lifecycletemplate where ida3masterreference
IN ( select ida2a2 from lifecycletemplateMaster where name
= 'My Life Cycle Template Name')
and latestiterationinfo = 1
);

Al Anderson