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

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.

Bentley, like Margaret Thatcher, complacently thinks TINA - There Is No Alternative.
As many pointed out, and have been proved right, TESSA - There Exist Several Splendid Alternatives.
What are we waiting for?

It's never a good thing when Thatcher gets brought into an argument!!!

We the USERS, need to know what is going on. If we log a SR/TR, we should be automatically updated, the SR/TR has our details. Surely, if the SR/TR is closed it is simple to send the user an update. Check out https://www.zendesk.com. this does it.

However, we also use this site to view other users issues or comments and from time to time we may see an issue we haven't realised is also an issue for ourselves. Thus, it can be useful to counter act the issue before it is an active issue. (if that makes sense). Thus, a fix list would be very useful. I agree with Duncan, this site is faster at getting a reply than a SR.

OK I understand that Bentley don't really want to publish bugs or fixes, as it can be detrimental to the sale of their software. However, this is a user site, users use this to log issues, each users within this site has to have a user login, thus its not technically public. Bentley could request we sign a NDA or offer another closed site for SR/TR reviews.

Basically, we are trying to help make Bentley software better, we spend hours reporting issues (for Free), we want to get something back that actually means our time isn't wasted

Thank

Ian

Duncan... it can only mean one thing....... Bentley will be sold soon.

Spot on Ian

Spot on Ian

To Trimble - wouldn't that be great?
Could take the best (and there's lots of that), re-think and rationalise all the disconnected semi-finished incompatible bits, heavily prune the legacy ball-and-chain, modernise the UI e.g. merge with SketchUp?!!!, start rebuilding a user base from the bottom, keep selected super-techie bits in a cordonned-off area to keep the IT departments happy ...

Trimble? Merge with sketchup?? Noooooooo.... What we need is:

Fixes and updates for old stuff;

Proper merge with vue: CE u2 and beyond;

Update for luxology engine 10 (by the time we get that probably it's already out 11 or so...);

Refinement for UI;

And more.

Hi all,

To reiterate what Dan Eng has said above...we have recently reinstated the SR notification system, and he is looking into this and will post an update about it.

We are certainly appreciative of the software choices you make and the effort you all take to report your issues and as demonstrated by the list posted here are happy to post the issues fixed in each build.  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. 

Also, regarding Ian's effort to collect issues together in a list here.  It may be useful for you discuss and decide on the highest priority things if it reveals which issues help the largest number of you.  We will carefully review it and use it to guide our work in the coming updates.  However, as Andrew states, if you are indeed production-down or need specific fixes urgently, please raise a Service Request so that we can be sure to properly trace the issue.

-Makai

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!