Properly support Project Management within locked Integrity Servers

[cdoyle]

Project management within a PTC Integrity Lifecycle Manager server chain (i.e. a set of servers that are locked via Admin Staging) is currently much more manual and cumbersome than it needs to  be, because creation of Projects and editing of Dynamic Groups on locked servers is not officially supported by PTC.  If these capabilities were officially supported, project management could be automated to a  large extent; without such support, much of the work must be manually done by a full administrator of the system, and migrated up the chain of servers.

The functionality to support these features is already available within PTC Integrity, and has been there for several releases; at least since Integrity 10.6.  Specifically, the following hidden, undocumented, and officially unsupported properties allow the necessary operations on a locked server to allow streamlined, automated project management on a locked Integrity Server:

        mksis.im.allowDynamicGroupModificationOnLockedServer

        mksis.im.allowProjectModificationOnLockedServer

This request is for those two properties to be officially supported by PTC.

[mrump]

This would really help a lot

@cdoyle Thank for mentioning the properties.

I was looking for that for years.

Now I can finally reactivate my initial script setup from 8 years ago (basically filling dynamic groups based on user fields in the project's backing item)

This used to work perfectly till we switched to a prod-stage server setup.

[GauravPhadtare]

This feature is delivered with Integrity Lifecycle Manager 12.2.0.0 release.