Delson

Processing old LOTUS NOTES bases (.NSF) is a painfull task because in many cases we need to install LOTUS NOTES 9 client many timens in order to Intella detect it correctly. Even worse if the base needs .ID file to open. It will be great if Intella Connect has the libs needed to open NSF built-in.

I woul like to suggest the creation in Report Area TAB a "Reviewer Performance Report", verry similar to "Volume" option but using the user names and dates as filtrers. The mais goal is to quickly see (grafh and sheet) the users that coded, or tagged more itens in a determinet time period, and compare the review performance between the users.

Dear, I'd like to suggest that audio and media files were supported in preview item and batch coding. As many investigations use smartphone data, tis fairly commons to and item (chat) bring WhatsApp audio and video file (.ogg and .mp4). Today we need to download the files and play using VLC or media player. The problem is that not all reviewers has Download permission, restricting the people that can review CHATS. Thanks Delson Gonçalves

Hi, There are a few tasks, like Hreading and AI Coding that are very machine memory consuming. As those are background tasks, they use the current Intella Connect server memory and processor to ran. It will be verry nice if we could use another machine to perform this kind of tasks, like a NODE machine instead the current Connect Server. TKS Delson

Dear, I'm working in a case that the reviewers are not allowed to print or dolwnload a file. So I ser the premission according those premisses, allowing the reviewers to only access a case in the "review" batch view. The problem is that the plugin used to load the "preview" in batch has the option to print the file. Is there a way to overcome this problem? Delson

In this case i'm using an homologatiom machine/system that use Microsoft Defender as AV. I will try to disable it before instalation. Meanwhile, do you know if there is any problem in using Connect/NODE 2.3 with the HASP drivers embedding in 2.2.2 version?

Hello There, Last night I started to update my NODE from Connect 2.2.2 to 2.3 version. Immediately after the instalation I received the error 33 - Unable to Access HASP KEY and I notice that the LED from the USB key was off. In order to fix that I used the commands >haspdinst -r then >haspdinst –purge and finally >haspdinst –I from the Version 2.2.2 in order to restore hasp drivers. After that the USB key led trun on again. Because of that I'm still currently using the 2.2.2 version, and I'm not sure if it's a good idea using the new version with old drivers. Anyone has the same problem? Delson