Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
There actually is a way to do it today, although it may not work for you because it requires some additional conditions to happen. Let me elaborate.
There are two types of Locks in Fusion Lifecycle. The first is the one you are referring to which is also known as 'Explicit Locking'. Explicit locking is done by declaring an item locked. At that point, the item is locked for all users. The second type of locking is known as 'Implicit Locking' and that happens for each user independently when that user does not have the ability to perform any workflow transitions on the item.
So one way to achieve what you are looking to do is to remove the ability of Person A to perform any transition out of the new state. If that happens, the item will be locked for user A and any other user that cannot perform a transition.
One other thing to note is that user A in the above example will still be able to edit any data that is not subject to workflow locking. To mark a section of Item Details data as subject to workflow locking, please open the settings for that section (in the admin page for the Item Details tab) and mark the section as subject to workflow locking. A section that is marked as subject to workflow locking will be locked in both Implicit and Explicit locked states.
@dvirh I think the issue may be the section for Person A has advanced permissions applied so only the group they are in can edit, Person B has advanced permissions applied so only the group they are in can edit. I think preventing each other from editing each others sections also bypasses the workflow locking by state. Make sense? It needs to be best of both worlds, not one or the other.
Advanced permissions should not trump workflow locking. If that is happening, I would recommend opening a bug as this is unintended. Have you tried it out in Modern UI to see if the problem appears there as well?
