Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Suggestions

Discussion in 'CRM / Helpdesk / App Integration' started by SWSDEV, Sep 20, 2009.

Thread Status:
Not open for further replies.
  1. SWSDEV

    SWSDEV Member

    Joined:
    Feb 23, 2008
    Messages:
    256
    Likes Received:
    0
    These might help some company's avoid some initial frustrations when evaluating the voice application designer, therefore help increase the number of company's who decide to take on the platform.

    1. In the designer, in any location where the user creating the voice application has to put single quotes around a string, it might be a good idea to validate their string at design time.

    If they put a value in and you can tell it contains non-numeric characters, then throw a warning immediately. It seems the ecmascript error is a common thing until you get used to it.

    2. A "test connection" button would be great, like Visual Studio has. I can tell you guys have already gone to a good amount of detail to make the environment familiar to Visual Studio developers.

    3. When deploying a project, check the web.config file of the IVR for the <httpRuntime> tag so you can throw an immediate warning if you know the size of the project is greater than the value of "maxRequestLength"

    The more errors that can be determined at design time, even if they're just warnings, the better. You've done a great job thus far in general.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. SWSDEV

    SWSDEV Member

    Joined:
    Feb 23, 2008
    Messages:
    256
    Likes Received:
    0
    Here's #4

    I just learned after a bit of going around in circles that in your database name, when using a non-standard instance, you have to make sure you escape your backslashes.

    Hence 'TFS2\\SQLEXPRESS' and not 'TFS2\SQLEXPRESS'

    This would be another great thing to tell at design time.


    this would frustrate traditional Visual Studio developers, since escaping characters in strings is always at the code level and you'll never find that in a design time database connection window.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. SWSDEV

    SWSDEV Member

    Joined:
    Feb 23, 2008
    Messages:
    256
    Likes Received:
    0
    Incrementing version numbers with each build would be great too.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. VAD_Support

    VAD_Support Active Member

    Joined:
    Aug 6, 2009
    Messages:
    690
    Likes Received:
    0
    Thanks for your suggestions, they're much appreciated!
    We'll consider them for future releases.

    In regards to build number, it is currently being incremented in each build. Did you notice any problem with this?
     
  5. SWSDEV

    SWSDEV Member

    Joined:
    Feb 23, 2008
    Messages:
    256
    Likes Received:
    0
    ok, sorry I missed that obvious one.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.