Archiving project areas and deleteProjectAreaResource
- Apart from hiding PA from active PA list, what does archive PA function do? from functional point of view?
- What are the differences in between active PA and archive PA? In regards to resource management
(eg If there are 60 PAs and admin archive 30 of them. Will it lower overall resource usage?)
- How does archive PA function and deleteProjectAreaResource differ?
- What are the differences in between active PA and archive PA? In regards to resource management
(eg If there are 60 PAs and admin archive 30 of them. Will it lower overall resource usage?)
- How does archive PA function and deleteProjectAreaResource differ?
Accepted answer
- Apart from hiding PA from active PA list, what does archive PA function do? from functional point of view?
The archive feature does nothing other than hide the project area in the UI. It is purely a way to cut down on the visual clutter caused by unused project areas.
- What are the differences in between active PA and archive PA? In regards to resource management
(eg If there are 60 PAs and admin archive 30 of them. Will it lower overall resource usage?)
The archived project areas continue to exist, as do all of the artifacts associated with them. Archiving a group of projects will not make the database smaller. It will speed up some UI operations because the archived operations are not returned across the wire to be displayed.
- How does archive PA function and deleteProjectAreaResource differ?
deleteProjectAreaResource deletes the JFS storage items associated with the given project area. CM and QM do not use JFS storage items associated with project areas, so the command has no effect if used with CM or QM project areas. The command may be useful for RM project areas. As stated above, the archive function hides the project but does not delete any items.
The archive feature does nothing other than hide the project area in the UI. It is purely a way to cut down on the visual clutter caused by unused project areas.
- What are the differences in between active PA and archive PA? In regards to resource management
(eg If there are 60 PAs and admin archive 30 of them. Will it lower overall resource usage?)
The archived project areas continue to exist, as do all of the artifacts associated with them. Archiving a group of projects will not make the database smaller. It will speed up some UI operations because the archived operations are not returned across the wire to be displayed.
- How does archive PA function and deleteProjectAreaResource differ?
deleteProjectAreaResource deletes the JFS storage items associated with the given project area. CM and QM do not use JFS storage items associated with project areas, so the command has no effect if used with CM or QM project areas. The command may be useful for RM project areas. As stated above, the archive function hides the project but does not delete any items.