Re-use library: preventing other projects from modifying items

Basit Sheikh
Basit Sheikh Member Posts: 8
edited March 13 in Peer-to-Peer Support Forum

I have a centralized library project. I want to reuse one item from it so that it is included in two other projects. How can I ensure that the content can not be modified by the two other projects, thus maintaining future changes from a centralized location (e.g. make it so that the only way to update the item would be through the centralized library project)?

Additionally, would it be possible to make it so that anytime a change is made from the centralized library project, it is automatically propagated to the other two projects (as opposed to being forced to sync the changes)?



------------------------------
Basit
------------------------------

Comments

  • [Deleted User]
    [Deleted User] Posts: 103
    edited July 2023

    To lock a single item, you can use a system lock based on workflow status.   You will have to unlock it in order to update it.

    The only way to trigger the change automatically would be to do so via a script (which you schedule to run periodically) or to use JCI.

    ------------------------------
    Geoffrey Clemm
    Jama Software
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 07-19-2023 10:09
    From: Basit Sheikh
    Subject: Re-use library: preventing other projects from modifying items

    I have a centralized library project. I want to reuse one item from it so that it is included in two other projects. How can I ensure that the content can not be modified by the two other projects, thus maintaining future changes from a centralized location (e.g. make it so that the only way to update the item would be through the centralized library project)?

    Additionally, would it be possible to make it so that anytime a change is made from the centralized library project, it is automatically propagated to the other two projects (as opposed to being forced to sync the changes)?



    ------------------------------
    Basit
    ------------------------------

  • Basit Sheikh
    Basit Sheikh Member Posts: 8
    edited July 2023

    If I needed to prevent other projects modifying all of the items within a folder (rather than just one item), would a system lock still be the best option?



    ------------------------------
    Basit Sheikh
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 07-19-2023 21:18
    From: Geoffrey Clemm
    Subject: Re-use library: preventing other projects from modifying items

    To lock a single item, you can use a system lock based on workflow status.   You will have to unlock it in order to update it.

    The only way to trigger the change automatically would be to do so via a script (which you schedule to run periodically) or to use JCI.



    ------------------------------
    Geoffrey Clemm
    Jama Software
    ------------------------------

    Original Message:
    Sent: 07-19-2023 10:09
    From: Basit Sheikh
    Subject: Re-use library: preventing other projects from modifying items

    I have a centralized library project. I want to reuse one item from it so that it is included in two other projects. How can I ensure that the content can not be modified by the two other projects, thus maintaining future changes from a centralized location (e.g. make it so that the only way to update the item would be through the centralized library project)?

    Additionally, would it be possible to make it so that anytime a change is made from the centralized library project, it is automatically propagated to the other two projects (as opposed to being forced to sync the changes)?



    ------------------------------
    Basit
    ------------------------------

  • [Deleted User]
    [Deleted User] Posts: 103
    edited July 2023

    If it is an entire Component or Set that you want to make read-only, then Project Permissions would be the way to go (a Project Admin would set those).    But at the folder level, you would need to use System Locks on each of the items in the folder.

    ------------------------------
    Geoffrey Clemm
    Jama Software
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 07-20-2023 10:46
    From: Basit Sheikh
    Subject: Re-use library: preventing other projects from modifying items

    If I needed to prevent other projects modifying all of the items within a folder (rather than just one item), would a system lock still be the best option?



    ------------------------------
    Basit Sheikh
    ------------------------------

    Original Message:
    Sent: 07-19-2023 21:18
    From: Geoffrey Clemm
    Subject: Re-use library: preventing other projects from modifying items

    To lock a single item, you can use a system lock based on workflow status.   You will have to unlock it in order to update it.

    The only way to trigger the change automatically would be to do so via a script (which you schedule to run periodically) or to use JCI.



    ------------------------------
    Geoffrey Clemm
    Jama Software

    Original Message:
    Sent: 07-19-2023 10:09
    From: Basit Sheikh
    Subject: Re-use library: preventing other projects from modifying items

    I have a centralized library project. I want to reuse one item from it so that it is included in two other projects. How can I ensure that the content can not be modified by the two other projects, thus maintaining future changes from a centralized location (e.g. make it so that the only way to update the item would be through the centralized library project)?

    Additionally, would it be possible to make it so that anytime a change is made from the centralized library project, it is automatically propagated to the other two projects (as opposed to being forced to sync the changes)?



    ------------------------------
    Basit
    ------------------------------

Categories