Looking for very specific features to be developed (Spell check and property character counter)

Good morning,

I am looking for very specific features to be developed and looking to see if any M-Files Partner can offer a solution (so far, it seems M-Files is not offering/considering these functionalities).

  • Spell Check: for text fields we want to have a spellchecker as part of M-Files.

  • Property Character Counter: so we have some text properties where we have enforced a maximum length, e.g. there is one "text (multi-line)" field where we set-up a 1,000 character limit. The enforcement is set-up and functioning correctly. However, when users are typing their text, they never know when they are close or have reached the limit. If they exceed the limit and try to create/save then they get an error message. They then have to adjust their text accordingly. As you can imagine, if you are doing this day-in-day-out it becomes a bit of an inconvenience.
  • We would like to have a counter that shows the 'characters remaining' to the text limit. So as a user is typing, the counter is instantly following, so at a glance the user can see how many more characters they can type (as per the attached pic).

Parents
  • Hi Patrick,

    For your first request I have found an existing improvement request: 164775.  I have added your company to the list of people requesting it.

    For your second one I can't find an existing tracker item, but can I ask how you've implemented the restriction?  Is it through a custom vault application (e.g. an event handler), or some other approach?

    Regards,

    Craig.

  • Hi Craig, yes this was implemented through a "Custom Vault Application" by our M-Files consultant.

  • Okay.  In that case the restriction isn't really "known about" by the system itself; it's simply a piece of code that's run when the object is checked.  If this code throws an exception then the system displays it.

    The only way to achieve this would be either for M-Files to have a concept of "maximum characters" on a text field (I know single-line text already has a limit, but that's a hard limit) which it could then use to create the countdown, or for you to be able to react as the information is entered into the metadata card.  Both of those are options, but significant changes.  I will see whether I can find any improvement requests that I can upvote for you.

    There is one other option involving a custom dashboard and a custom metadata card, but that would probably be very significant work unless the metadata you're collecting is really simplistic.

Reply
  • Okay.  In that case the restriction isn't really "known about" by the system itself; it's simply a piece of code that's run when the object is checked.  If this code throws an exception then the system displays it.

    The only way to achieve this would be either for M-Files to have a concept of "maximum characters" on a text field (I know single-line text already has a limit, but that's a hard limit) which it could then use to create the countdown, or for you to be able to react as the information is entered into the metadata card.  Both of those are options, but significant changes.  I will see whether I can find any improvement requests that I can upvote for you.

    There is one other option involving a custom dashboard and a custom metadata card, but that would probably be very significant work unless the metadata you're collecting is really simplistic.

Children