Forum / Remote Desktop Manager - Feature Request

Add customizable field length for Comment Log and add configurable subconnection types

  • Create an Issue
  • Cancel

We want to be able to store change history for Cisco devices and such in log comments when disconnecting from our devices.
Currently if insert a log comment the Notes field has a maximum character length of 500 lines.
The field in the database is stored as nvarchar(max) by default, so this is a constraint in the application not the database design.
Can you please either remove this constraint, or preferably, add an option in the administration section to change the maximum length of this field.
That way default installations can have their same limit, but it allows for flexibility for people who wish it.
This shouldn't cause too much of a speed issue, but could do with a note that adding large comments would likley mean needing to run the log cleanup tool more often.


Secondly,
It would be good if we can set what entry types are valid to be used for subconnections somewhere in the administration section.
We have passwords that are only valid for a single application on a single server, so we store them as a Username/Password credential entry, then use the refactoring options to parent it to the specific device (think Windows server with a specific piece of client software that gets used no where else on their network)
We cannot add the credential as an entry directly, we can only do it via refactoring where we set the parent.
But this does not work for all entry types.
We have Cisco devices that we would like to add a Document Entry as a subconnection to store their last known good working configuration.
But we cannot set a parent on a Document Entry.
And if we could get the Credential Entries listed in there, as we can already use them as sub connections, just not directly.

Clock2 yrs

Hi,
For the first request, it can easily be done. The other one is more complicated. We tried to remove the sub connection usage because it could cause a lot of performance problems. I will add a feature request to change the way it's implemented and this could allow some types like the document.

Regards

David Hervieux

signaturesignature

Clock2 yrs

By the way, you could use an attachment entry to store the document.

Regards

David Hervieux

signaturesignature

Clock2 yrs

Great to hear that the first request can be easily done.

Didn't even think of using an attachment to handle that. that will work nicely for our purposes.
Even just allowing credential entries would be nice for now, as we are able to Parent them through refactoring, so it would take out the double handling for the odd time we need to do it.

Clock2 yrs

I can see that you implemented this in the latest update, however it is bugged.
When adding one, it never appears.
It offers it in the sub-connection entry screen, you can select it, input all details, but when you click ok, it doesn't appear to save it to the database.

Clock2 yrs

I will assign this to Hubert.

David Hervieux

signaturesignature

Clock2 yrs

Hello,

Thanks for letting us know, we made the change internally and it will be available in the next minor update.

Regards,

Hubert Mireault

signaturesignature

Clock2 yrs

Thank you both for your prompt response and rapid patching, as per usual. smile

Clock2 yrs