Connect Update 1 - Whats New/Fixed? Help only mentions a a change for "Checking for Product Updates"

Is this all that was pushed out in this update?

Parents
  • If it took 6 months to get just that fixed, then something must have gone horribly wrong...

    AZERTY support is in, the pop-up bottom row icons aren't cut off, there is undoubtedly more, but it would have been nice if they mentioned what they've been working on and what's supposed to be fixed in this update.

    Now we'd have to try everything all over again.

    Parametric cells are still placed on the active level, labels without leader still broken, wrong terminators on DWG dimensions still there.

    Better not get our hopes up too high.

  • I can't believe they released a version with a .13 at the end. That is going to freak out a lot of superstitious users, especially if they have to use it on Fridays.

    Rod Wing
    Senior Systems Analyst

  • Unknown said:
    This should save you the time it takes to re-verify your defects at each release; especially important since releases will now come far more frequently

    Sorry but it really doesn't.  On the user side there is no cross reference between and SR and a Defect number.  There is no way to run a defect number against my SR's

    The SR Database does have a field the shows status but they don't seem to get updated went the issue gets fixed.

    The SR filing is unnecessarily complex.  

    With connect I can open right to my SR's but....

    I have select my product for a Picklist of over 100.  Who in their right mind creates a pick list with over 100 entries?

    I have to give it a version number. & language... remember I'm launching for the product itself.

    Why can't any of this be auto populated? At least remember the last settings.

    Fortunately there are some extremely helpful BSI personal here in the form who will take defects logged here and file the SR for us.  This saves me a lot of time having to file everything twice and eliminates BSI having two different people chasing down the same problem.

  • Filing a SR can take a whole lot of time. Really a whole lot.
    Say you're aware of a bug, you read about it on the forum, tried it on your install and you think "Darn, that doesn't work. We'll need to wait for that to be fixed before we can do this or that. You find the Defect Number somewhere.
    Now you reproduce the issue, make an example, document, file an SR.

    Standard blah response, analyst does or doesn't know what you're talking about even with the Defect # in the SR. Analyst follows the standard routine, proposes the usual blah, no that's not a solution because there's a Defect # for it. Mails back and forth. Explain why this is important, blah, blah, more blah. Until finally you can get a response that your SR has been attached to the Defect# (or the other way around, whatever).

    If on a particularly "productive" day you stumble upon a dozen or so things that will really need fixing for you to move forward with CE.
    The time it can take before you get those tickets attached to their corresponding Defect numbers can easily mean a day or two of close to zero productivity (money made). One or two days without pay or anything to show for your efforts other than that you're supposed to now be notified when that issue is resolved, and even that doesn't work!

    Is anyone really surprised that customers more often than not can't be bothered to even file an SR anymore? Support is bogged down by this process, costing money, and the customers are bogged down by this because they can't make money while going through the same old motions of explaining everything while the analysts have to follow their scenario. Have you tried this? Did you read that? Blah, blah, blah,...

    Like the Ideas section, there should be a Bugs (Defects) section where you only need to vote for a Defect and be done with it instead of wasting hours and hours of precious time for something that should really only take a few seconds.

    Of course Bentley appreciates the time people take to file SR's. They get paid for their time by the customer, who instead has to pay yet again by seeing time go down the drain that could have been spent making money. The whole SR process is a huge money-drain and Bentley needs to set up something that's at least 100 times more efficient. That Defect#, Oh, someone already filed it, great! Click, vote done!
  • Fortunately there are some extremely helpful BSI personal here in the form who will take defects logged here and file the SR for us.  This saves me a lot of time having to file everything twice and eliminates BSI having two different people chasing down the same problem.

     

    Why aren't there more Bentley Support/Developers active in here.!!!!!

  • Case in point how this wonderful system works...NOT!

    Defect 323991 which is reported as fixed.

    This was a result of SR 7000416380 which is still showing me its an Open Defect.

    And the only way for me to find the link between the two was to read thru all Descriptions and look for similarities.

  • Hi Ian,

    Just to follow up on the notification process, there is a delay from when the notifications will be sent out from the time a product has been released to the time they are sent out. There will be notifications sent out informing you of the resolved issues that have been linked to a service request.

    Thanks,
    Daniel Eng

Reply Children
No Data