列出事件处理程序版本控制/批准/签入/签出
我们看到的问题是，如果您取消文档签出并且更改了部门（具有不同的安全性），则文档权限不会更新/更改回之前发布的版本权限。发生的情况是，如果您取消签出，事件处理程序不会触发，并且我们认为在您执行此操作时（目前）没有办法让它触发。一旦我们更改部门，事件处理程序就会更改已发布的版本，即文档 v1.0 的安全性，而它应该只更改文档 v1.1（现在处于草稿模式）的安全性，然后当我们取消签出时安全性是正确的，但 EH2 正在改变两个版本的安全性
编辑
我们使用的是 2010。我意识到安全性和签入/签出是两个独立的功能，但我们遇到的问题是当我们编辑时强制签出的文档（版本控制已打开）。当进行编辑时，我们有一个事件处理程序，它会根据文档的元数据列触发并更改文档权限。
整个过程如下： 上传新文档 分配元数据（一列指示分配文档的权限） 现在以编程方式将文档权限设置为唯一 - 现在，根据上述列选择，文档具有唯一权限 然后是用户可以通过更改元数据列来更改文档权限。如果版本控制/签入/签出未打开，则在签入/签出和版本控制打开的情况下可以正常工作；所有版本的文档权限发生变化，包括发布版本和草稿版本。然后，如果他们取消签出，文档元数据将返回到正确的版本，但权限不会更改回来，因为没有任何内容可以触发用于更改权限的 itemupdate 事件。
我们正在寻找一种方法，让它在发生这种情况时根据当前发布的版本重新应用权限，或者保持每个版本的权限唯一，因为 SharePoint 将它们视为单独的文档。
例如，在草稿获得批准之前，文档可以具有具有一组权限的草稿版本和具有另一组权限的发布版本。
The issue we see is that if you cancel a document check-out and you had changed a department (which has different security) the document permissions are not updated/changed back to the previous published version permissions. What is happening is that if you cancel a check-out the event handler does not fire and we see no way to make it fire when you do this (yet) . The event handler is changing the published version i.e. document v1.0 security as soon as we change the department when it should only change the security on document v1.1 (which is now in draft mode) then when we cancel a check-out the security would be correct, but EH2 is changing security on both versions
Edit
We are using 2010. I realize that security and check in/out are two separate functions, but the problem we are having is when we edit a document it forces a check out (versioning turned on). When that edit happens we have an event handler that fires and changes the document permissions based on a metadata column for the document.
Here is the whole process: Upload a new document Assign metadata (one column indicates what permissions to assign the document) The document permissions now programmatically are set to be unique - Now the document has unique permissions based on the column choice noted above Then a user can change the document permissions by changing the metadata column. If versioning/checkin/checkout is not on this works fine With the checkin/checkout and versioning on; all versions of the document permissions change including the published version and the draft version. Then if they cancel the checkout the document metadata goes back to the correct version, but the permissions do not get changed back as there is nothing to fire off the itemupdate event that was used to change the permissions.
We are looking for a way to have it reapply the permissions based on the current published version when this happens or to keep the permissions unique to each version since SharePoint sees them as separate documents.
So for example a document could have a draft version with one set of permissions and a published version with another set of permissions until the draft gets approved.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
SharePoint 支持的最低安全级别是列表项级别。如果您修改列表项（或文档）的安全性，它将始终应用于该项的所有版本。取消结账并不会真正改变它仍然是同一个列表项的事实。取消签出也不会回滚您在事件处理程序中执行的所有代码。
The lowest level of security that SharePoint supports is at the listitem level. If you modify the security of a listitem (or document), it is always applied to all versions of that item. Cancelling the checkout doesn't really change the fact that it's still the same listitem. Cancelling the checkout also doesn't roll back all the code that you executed in an event handler.