Perforce (P4V) allows you to configure your favourite connections, aliasing ips/ports/workspaces to a more memorable name. However after visiting each favourite it will then be added to the "recent connections" list, thus the dialog has 2 entries for the same connection:
Ideally it would not add an existing Favourite to recent-connections, but failing that, is it possible to turn off recent-connections entirely?
(Similar to but not a duplicate of "How can I clear the list of recent connections from Perforce P4V?").
Related
I am trying to create a Mail-In database for a new workflow application,
internal and external mail to arrive into a view which can be accessed by any member of the team, assigned reassigned, etc etc.
Attempt 1
I started with a blank canvas created a memo form, view, frame with preview etc, embedded another team calendar in the frame etc no problem until I started to try to implement basic functionality like forward and reply - with history. Forwarding my memo/mail with the history results in a copy of what becomes the ugly header in the new form. I needed it to be formatted like it is in a reply or forward of a Notes email ie like this.
Many hours later I could not figure out how the above has been achieved in Notes.
Attempt 2
Use the standard Notes 11 mail template and using the Notes message/memo form, add my bespoke view and frameset with preview etc. Nearly works, I get the neat history on Forward, however, on previewing the mail in my frameset the preview is pushed outside of my frame covering half of the other frames, it is unuseable. It seems like there is one form on top of another, ie this is apparent when opening the mail, adding a green background to the form is only visible on Edit. Again after hours and hours of searching through code and subforms, I cannot find the cause of it. I have established though if I open my client in basic mode, ie. nlnotes then it works perfectly.
So several questions all related, am I going about it the right way. I would like to use the mail template as a lot of what I need is built in, but I need to view that database in basic mode whilst in a standard eclipse notes client, ie stop it trying to open whatever it is trying to open in the eclipse version.
Or is there a better way, ie to generate the neat From: To: history in Forwarded and Replied to emails.
I will also want any replies to be from the group email address rather then the individual user, I haven't got to that yet so I am not sure if it is a problem.
I have seen the Open NTF Team Mail project, but that is 10 years out of date, so I felt there would be more advantage in trying to use the existing mail template.
Hope that makes sense.
Any help would be greatly appreciated.
Thanks
I suggest to create a new mail-in database and give it the right mail-template. Sometimes an application gets a hick-up and the application can't implement the template correctly. Or because of your previous tries there are design parts which shouldn't be there.
Is this the first time you create a mail-in database? Are all template elements signed correctly? Did you check the ACL, too?
We have a (super)user who has been using VBA in an Excel spreadsheet to create and manipulate documents in a Domino database application.
The user has 'Editor' access to the application, and should normally be able to create/edit the document contents.
They have been, however, creating documents using VBA. That logic doesn't consider such important document fields as Readers, Authors, etc. .
We would like to restrict access to all Domino data so that it can only be created/modified using an IBM Notes client.
I have tried looking through the ECL, but that only restricts what 'others' do.
Since he has his Notes client available, the external logic is using his normal Notes credentials.
I have tried setting a hidden field with the Notes client and looking for that in the QuerySave event of the form design.
Unfortunately, the external code pays no attention to the form events and the save is executed despite the missing field.
Similarly, the Database Script has no bearing on the execution of external logic.
I was going to inspect the client version upon database open and restrict activity based on a variance in the version (I was hoping!).
I have de-selected the 'Don't prompt for a password...' option in the user security preferences, but that has no effect at all (suspected as much!).
The ONLY thing I have been able to suggest is to hide the database design... That's really only designed to thwart a user's efforts to understand the underlying design.
It won't prevent them from creating hundreds of thousands of documents with a fictitious form and throwing the app into disarray.
I'm hoping that there is a solution out there that I'm missing.
The user has been instructed not to undertake such activity in the future.
We were lucky that there really wasn't any malicious intent - "Just trying to be more efficient" we're told.
The effects of the activity have been remedied, and the user has been warned.
What I want to know is... how can I prevent this from ever happening again?
The circumstances are rare I know, but I would've thought there'd be a means of restricting the platforms used to manage Notes/Domino data.
Is there a way to ensure no external applications are able to access, create or modify Notes database documents?
I am currently focussing on access to Notes via COM.
I thought that, if I unregistered 'nlsxbe.dll' from the registry, that would prevent such activity - It has not.
I also tried removing the .TLB files from the Notes executable folder - removal of 'notes32.tlb' and 'domobj.tlb' have no effect at all. Removal of 'ltsci3.tlb' screws everything up (as expected!).
I'm really having no luck at all - Any/all suggestions would be most appreciated!
I'm not aware of any way to detect that a connection has been made by standalone code instead of by the Notes client, but you do have two paths available to you:
A Domino server add-in that prevents documents from being saved in that particular database if certain criteria aren't met.
An agent that is triggered to run shortly after documents are saved or modified in that particular database. The agent code can delete (or modify, if you prefer) the documents that don't conform to the required criteria.
The server add-in route would normally require coding in C, but thanks to the Open NTF Trigger Happy project, the hard part is done for you, and the rest can be filled in with either LotusScript or Java agent code that is "triggered" by the pre-written C code. You will need to have some basic knowledge of how the Notes Extension Manager interface works, but once you get past that and write your agent code to enforce your data consistency/integrity requirements, the only real hurdle is your willingness to host open source code on your server.
There may be two other possibilities, but I can't say if either will solve or deal with the issue...
In the ECL you can disable 'COM' access for the user (also known as OLE or ActiveX) automation since VBA access is usually via COM. This has stopped Notes using external COM access for me, but I don't know if also prevents VBA using Notes. Additional steps may be needed to enforce the ECL and apply to the specific users.
There is an (old) notes.ini 'DisableExternalApps' (or something similar) that disables some external access. This can affect many things (DDE/Prompts/#dblookups) but again I don't know if this will disable VBA/COM and its not user specific, but server wide.
I would have thought that removing the nlsxbe.dll or restricting access to execute it might work, but the ECL may be the best bet.
Alternatively, rather than add hidden flags to your design (and the documents), and then delete the offending documents, your agent could apply the correct author/reader fields to the documents instead.
Very tricky. Did you find a better solution?
I recently made changes and created two forms in a database residing in a production server. When I sent out the link, the users are getting this error:
Unable to create document, database does not contain design.
I suspect that the database residing in their Workspace is not getting the latest design elements (not in-sync). I tried asking one user to remove the database from her Workspace, sent the link to the database to open it again, and click on another link which I provided to open up the two forms and she was able to access the forms.
May I ask if there's any other way I can do for them to not delete it from their Workspace and re open it again so it will get the latest design elements? Should I request the Notes Administrator to perform some codes in the console?
Form designs are cached by the Notes client, presumably to aid performance. As far as I know, it's not possible to disable the caching.
If users have a database open when you modify or add forms, it's usually necessary for them to close and reopen the database to see the design changes, but they shouldn't ever have to remove the database from the workspace and re-add it. I don't think there's any way to avoid having to reopen the database.
I have seen a problem affecting several users at one customer where Notes wouldn't update its design cache, no matter what they did inside the client. The only solution I found in that case was to close Notes, delete a file named "cache.ndk" from the root of the Notes data directory, then restart Notes. It's been 2 or more years since this last occurred, so it might have been fixed in some version of Notes.
We have quite a lot of duplicates in our CRM 2011 system. We are looking at implementing a few duplicate detection rules that we be triggered when a user attempts to save their account or contact.
However, we do not allow standard users to deactivate accounts or contacts but the duplicate detected frame that pops up when a user attempts to save a duplicate allows them to do so (via More Actions).
I have checked permissions but they only have read access for the duplicate detection rule (which they need in order to view the potential duplicates).
Does anybody have any ideas about how I can remove the deactivate option?
Many thanks.
There is no way to change the UI for how the Dup Rules work. If you truly want that functionality, You could make a rest call to perform the save, inside of the onSave handler, then check for the Dup Detection error response, and present your own error dialog that allows the user to create anyways.
I have directories in TFS (server is 2010, users are using VS 2012 and 2013), which I want to prevent anyone from working in. I still want them to be there, so users can read the files and view history, but I don't want to let them check anything out or in.
The reason is that we have a bunch of outdated branches which people have created all willy-nilly with terrible names over the years, and we're hoping to not have to move/reorganize them all right now - but I don't want anyone new to accidentally work on one of the old branches without realizing it.
I can lock the directories, but then they show up indefinitely in my on personal changes as locked - I don't want this junking up my workspace, and if I ever leave, I'm sure my locks will be removed anyway.
Is there any "disable" command or anything else I can do to stop checkouts/checkins on directories?
if you right click on the branch you should get security options. in TFS 2013 its Advanced > Security (sorry not got 2010 instance in front of me)
you can then set permissions on the branch, set read for your normal users and disable Check in / check out for them