| Darryl,
SM CSZ MET (manage element types)
Select STANDARD and then the element type you want and finally
Read it - oh and about the 14th field down is
"Delete Develop version when moved to live"
This is set to N for all the STANDARD elements except FRM since I
think it's obvious that you need to delete the development version
of that so that the users can see the live version.
So setting this field to Y would cause another element type to be
deleted when an element of that type is made live but to anticipate the
questions from the experts...
"Which element types ... and why?"
Regards,
Andrew.D.Wicks
|
|
Darryl,
In ALL-IN-1 V2.* the FRM was deleted from the development area once it
had been moved to live, while the BLP, DO, COM and SCP elements stayed
in the development area. One of the reason was that the DEVELOP.FLB would
grow bigger and bigger all the time unless some action was taken to
reduce the size. A replacement of a form in a form library doesn't
re-use the original space, just adds to it.
The decision for this was made in the code.
In V3.0 we made the option 'to delete the development version after
move to live' optional, as Andy indicated. To be backwards compatible,
the only element type who has this field set to 'Y' by default is the
'FRM' element type (and the 4 exception elements). But you're free to
change it. That's why it has been made optional.
Andrew,
> This is set to N for all the STANDARD elements except FRM since I
> think it's obvious that you need to delete the development version
> of that so that the users can see the live version.
Deleting a development version for the user to see the live version has
nothing in common. The development version is for the CM User Society,
the live version for the users to be used. They can live next to
eachother quite happily.
> Which element types ... and why?
No specific reason. The user can now decide whether or not the
development version should be deleted. The main reason will be 'to save
valuable disk-space'.
Ciao,
Simon
|