Add an option to disable/prevent cloning on specific forms

  • Profile Image
    sequencesafety
    Asked on January 08, 2018 at 05:54 PM

    I found a thread from 2014 that explains that there is no effective way to require permission before JotForms can be cloned, other than protecting all forms in settings -- why don't you add something simple like being able to create in Publish a "view form link" and "a share form link?"

    Or perhaps allowing protection to be controlled from the My Forms files -- a file for protected forms and a file for unprotected forms.

    Give this weakness I will not be able to recommend JotForm to any of my clients. I mean, let's face it, forms that can be cloned at will are not secure forms.

     

    .

  • Profile Image
    Jan
    Answered on January 08, 2018 at 08:24 PM

    You can enable the "Do not allow my forms to be cloned by other users." option under the Privacy section in the Account Settings so that they cannot clone your forms.

    Here's the link: https://www.jotform.com/myaccount/settings.

    151546072101-09-sniy1.png

    You will also see options here for the submissions and uploaded files.

    Are you looking for a function where you can do this only in a single form? If yes, then please let us know and we will forward it as a feature request to our developers.

    Thank you.


  • Profile Image
    FormLibrary
    Answered on January 08, 2018 at 08:43 PM

    Thank you for the reply.

    Yes, the ability to restrict cloning on specific forms -- not the current all or nothing -- would be a great addition.

  • Profile Image
    Jim_R
    Answered on January 09, 2018 at 02:36 AM

    I've elevated your thread as a feature request. Please keep in mind that there's no assurance whether this will be implemented. It will highly depend on the viability of the feature, the amount of similar requests we get, along with the workload of our Developers.

    We can't give you any timeframe but we'll keep you apprised on this same thread when there's an update.

  • Profile Image
    sequencesafety
    Answered on January 16, 2018 at 12:32 PM

    Thank you. Just an FYI (and I know any one client is small potatoes for JotForm) -- I am working on a project with a company that will be recommending form builder apps to their clients. Unless this functionality is added to JotForm sooner rather than later they will be recommending Cognito to all of their clients.

  • Profile Image
    liyam
    Answered on January 16, 2018 at 01:26 PM

    Thank you for your response, sequencesafety. For us, every user as just as important as to another. We will take note of this and we'll sure to inform you once we have updates.

    Thanks and warm regards.

  • Profile Image
    sequencesafety
    Answered on January 23, 2018 at 02:58 PM

    Thank you, updates are great. But timetables are better --- otherwise, we'll have to advise our clients to move from JotForm to Cognito.

  • Profile Image
    Jim_R
    Answered on January 23, 2018 at 03:54 PM

    I understand the urgency of this request for your client but we simply can't provide a turnaround time. What I can tell you is that feature requests are being reviewed and decided upon, based on the things I listed on an earlier post - the feasibility of the requested feature, the amount of similar requests we get, and the workload of our developers.

    Some requests get implemented immediately while some may take time, thus explaining why we can't provide a definitive timeframe. We'll ensure you will get updated here for any news about this. Thanks in advance for your patience and cooperation.

  • Profile Image
    sequencesafety
    Answered on January 23, 2018 at 04:46 PM

    Which makes this marketing blast a joke.

    I can help you with process/workflow management (that's what I do) -- which would enable you to efficiently provide real answers (no/yes/when) to your customers rather than smoke and mirrors (it's very complicated, Grasshopper, thus explaining why we can't provide a timeframe).

    I'll give you this for free. Train your support personnel to identify reasonable/doable requests. They will forward the reasonable/doable requests to someone in development to do triage -- providing a quick yes/no/when that can be communicated to the customer. Use JotForm to support this process.

    Maybe I'm alone, but I'm guessing your customers would be happier with truth than stall. Sure, tell me no and I'll take those clients needing that functionality to another app, but blow smoke and I'll never come back.

  • Profile Image
    Jim_R
    Answered on January 23, 2018 at 05:14 PM

    Thanks for sharing your thoughts on this matter, we truly appreciate it when a user voices out his/her opinion.

    Maybe I'm alone, but I'm guessing your customers would be happier with truth than stall.

    We're always telling our users the truth as nothing will be gained if we stall or make excuses. And no, you're definitely not alone - I'm totally with you on this. Most users prefer an actual timeframe (even a rough timeframe) so they know what to expect, especially for time-sensitive projects.

    I'll give you this for free. Train your support personnel to identify reasonable/doable requests.

    We already have something similar in place. A certain group of our Support Team categorizes each bugs, issues or feature requests we escalate and assign a priority, a status and a respective developer who will handle that case. That part was already done on this ticket that I escalated for you. Yours has a "NiceToDo" priority, an "Open" status and is currently assigned to a developer who will look into it.

    All that's left now is for us to wait for an update, so we're kind of in the same boat as you are (waiting for an update). To help you out, I will personally ask if we can at least give you a rough timeframe.

  • Profile Image
    sequencesafety
    Answered on January 23, 2018 at 05:30 PM

    A rough timeframe would help me considerably. Thank you.