cancel

Major operational flaw found in TRIM 7.*

Highlighted
JasonIMEX
Outstanding Contributor.

Major operational flaw found in TRIM 7.*

Not sure if this has been discovered yet but here goes...

 

Users use a profile which does NOT have the "can be assigned access control" rights.

When creating a record they assign access controls to thier position.

 

In TRIM 7 a dialogue is displayed as soon as the user goes to create a record (See attached)

 

In itself this is fine. But I have discovered that when this screen is presented it also breaks all functions following

 

Document queues 

Drag and drop 

Outlook linked files 

Right click and sendto

 

The break is a straight TRIM crash with a runtime error.

 

I have opened a case with HP and awaiting a resolution. But wondering if any of the TRIM community at large have faced a similar problem or to warn of this issue.

5 REPLIES
EWillsey
Acclaimed Contributor.

Re: Major operational flaw found in TRIM 7.*

Yeah it's been like that since they introduced that permission. 

 

Just don't do it! :)

---------
Erik
CMRamble.com
JasonIMEX
Outstanding Contributor.

Re: Major operational flaw found in TRIM 7.*

Two options:
Dont use those features or
Have that security option ticked for Specific users.

Both options are not desireable.

 

I dont think its the introduction of the permission but the introduction of the pop-up screen itself. The permission is present in 6.2 aswell but no pop-up warning of the absence of the permission.

 

I may have to go back and look at some of the past upgrades/installation we did and consult differently. We generally advocate the use of positions.

 

 

JasonIMEX
Outstanding Contributor.

Re: Major operational flaw found in TRIM 7.*

Shameless self bump

and il do it again i tells yah Muahahaha
JasonIMEX
Outstanding Contributor.

Re: Major operational flaw found in TRIM 7.*

No one else doing position based security out there?

 

 

Grundy
Acclaimed Contributor.

Re: Major operational flaw found in TRIM 7.*

Hi Jason, 

 

I saw this case come through and spoke to the support staff about it.

No one I know uses this permission unticked, it appears like it has some problems right now and I believe we've raised it with R&D now.

 

Using position based security/profiles is common enough, but just not unticking that specific permission!

 

Cheers

Jon



::::::::::::::::::::::
NOT A HP EMPLOYEE
::::::::::::::::::::::

INFORMOTION.com.au