Jump to content

Unable to delete redaction


Guest Daniel Hahnke
 Share

Recommended Posts

Hi Daniel,

 

I would check the user permissions. You will most likely need to be granted edit permissions in order to delete the redactions you created.

To delete the redactions of other users you will need to permission to modify/delete other users'.

You can view these options under Case Permissions > Security > Redactions

Link to comment
Share on other sites

  • 2 weeks later...
  • 11 months later...

I'm having the an issue where I set the permissions to allow delete redactions, but after saving, it reverts back to view, edit, create. Not just with a permission template but also at case Permissions. As soon as I hit save, and click to another group case permissions, and click back to the one I just saved, it's back not allowing delete. Eclipse version 17.3.2

[ATTACH=CONFIG]n2300[/ATTACH] [ATTACH=CONFIG]n2301[/ATTACH]

[ATTACH=CONFIG]n2298[/ATTACH]

Link to comment
Share on other sites

I'm having the an issue where I set the permissions to allow delete redactions, but after saving, it reverts back to view, edit, create. Not just with a permission template but also at case Permissions. As soon as I hit save, and click to another group case permissions, and click back to the one I just saved, it's back not allowing delete. Eclipse version 17.3.2

579267155_RedactionPermissionssettoDelete20170921.thumb.PNG.87c3fb366cef08a36de7bd4be2592a2c.PNG 196558454_RedactionPermissionsClickedanothergroup.PNG.640cfed68ad9adac9e4fc3bdfc4060c0.PNG

1372494614_BacktoRedactionPermissionssettoDelete20170921.thumb.PNG.0dc113be08e671f5178dc0f972f7db96.PNG

994977784_RedactionPermissionsClickedanothergroup.PNG.73de2c5e06b28b007b845877b6c54ac5.PNG

978901533_RedactionPermissionssettoDelete20170921.thumb.PNG.186bfa7f1eb54190a93d0f4d39aa6de5.PNG

Link to comment
Share on other sites

Even the modify/delete other users redactions being enabled, does not allow the deletion of another users redaction. Only as a Super User can I delete a redaction.

Hi there! In version (2016.3.0) there is a bug re redaction permissions.

I was given a SQL Script to fix this from tech support. After creating a new case, I run this query in SQL.

 

_________________________________________________________________________________________

use ADD database name

 

 

declare @caseName varchar(200),

@group varchar(200),

@CPEID int,

@groupId int;

 

 

set @caseName = 'enter case name here' --Provide exact name of case in question between single quotes

 

 

set @group = 'enter group here' --Provide exact name of group in question between single quotes

 

 

set @CPEID =

(select CaseProductEnvironmentId

from Enterprise.CaseProductEnvironment

where Name = @caseName)

 

 

set @groupId =

(select GroupId

from Membership.[Group]

where Name = @group)

 

 

if exists --Return case name, group name, and permission name if permission already exists

(select *

from Membership.CaseProductEnvironmentGroupPrivileges

where CaseProductEnvironmentId = @CPEID

and PrivilegeId =

(select PrivilegeId

from Membership.Privilege

where PrivilegeName = 'Redactions Delete'))

(select CPE.Name, G.Name, P.PrivilegeName

from Membership.CaseProductEnvironmentGroupPrivileges CPEGP

inner join Membership.Privilege P

on CPEGP.PrivilegeId = P.PrivilegeId

inner join Membership.[Group] G

on CPEGP.GroupId = G.GroupId

inner join Enterprise.CaseProductEnvironment CPE

on CPEGP.CaseProductEnvironmentId = CPE.CaseProductEnvironmentId

where P.PrivilegeName like 'Redactions Delete')

else --Insert the redaction privilege permission if it does not exist

insert into Membership.CaseProductEnvironmentGroupPrivileges

(GroupId,CaseProductEnvironmentId,PrivilegeId)

values (@groupId,@CPEID,47)

PRINT 'Added permission'

Link to comment
Share on other sites

Even the modify/delete other users redactions being enabled, does not allow the deletion of another users redaction. Only as a Super User can I delete a redaction.

Hi there! In version (2016.3.0) there is a bug re redaction permissions.

I was given a SQL Script to fix this from tech support. After creating a new case, I run this query in SQL.

 

_________________________________________________________________________________________

use ADD database name

 

 

declare @caseName varchar(200),

@group varchar(200),

@CPEID int,

@groupId int;

 

 

set @caseName = 'enter case name here' --Provide exact name of case in question between single quotes

 

 

set @group = 'enter group here' --Provide exact name of group in question between single quotes

 

 

set @CPEID =

(select CaseProductEnvironmentId

from Enterprise.CaseProductEnvironment

where Name = @caseName)

 

 

set @groupId =

(select GroupId

from Membership.[Group]

where Name = @group)

 

 

if exists --Return case name, group name, and permission name if permission already exists

(select *

from Membership.CaseProductEnvironmentGroupPrivileges

where CaseProductEnvironmentId = @CPEID

and PrivilegeId =

(select PrivilegeId

from Membership.Privilege

where PrivilegeName = 'Redactions Delete'))

(select CPE.Name, G.Name, P.PrivilegeName

from Membership.CaseProductEnvironmentGroupPrivileges CPEGP

inner join Membership.Privilege P

on CPEGP.PrivilegeId = P.PrivilegeId

inner join Membership.[Group] G

on CPEGP.GroupId = G.GroupId

inner join Enterprise.CaseProductEnvironment CPE

on CPEGP.CaseProductEnvironmentId = CPE.CaseProductEnvironmentId

where P.PrivilegeName like 'Redactions Delete')

else --Insert the redaction privilege permission if it does not exist

insert into Membership.CaseProductEnvironmentGroupPrivileges

(GroupId,CaseProductEnvironmentId,PrivilegeId)

values (@groupId,@CPEID,47)

PRINT 'Added permission'

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Stephen,

 

You're correct, the issue in question is resolved in a subsequent release.

 

For some additional information, you should actually be able to set this permission and have it operate as expected -- it just will appear to be incorrect if you go back to the permissions screen afterwards. That is to say, setting the permission saves properly in the database, but editing the existing permissions does not show this setting at the correct position later. This can be somewhat confusing, of course, so we recommend upgrading when possible in order to resolve this issue.

 

Thanks!

Link to comment
Share on other sites

  • S.W.A.T. Engineer

Hi Stephen,

 

You're correct, the issue in question is resolved in a subsequent release.

 

For some additional information, you should actually be able to set this permission and have it operate as expected -- it just will appear to be incorrect if you go back to the permissions screen afterwards. That is to say, setting the permission saves properly in the database, but editing the existing permissions does not show this setting at the correct position later. This can be somewhat confusing, of course, so we recommend upgrading when possible in order to resolve this issue.

 

Thanks!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...