Skip navigation
All Places > Getting Started > Blog > 2018 > January
2018

I have some details to share about big changes coming to the Nintex Connect community!

 

You may have seen my previous announcement about it: New Year, Renewed Community. The quick version of that post is that since the software underpinning our community is facing the end of its useful life, we're moving to a new platform -- very soon. In fact, we plan to launch the new community in the next few weeks.  First, we'll show the plans to attendees at the Nintex xchange conference, Feb. 26-28 in San Diego. You're registered, right?  We'd hoped to launch by then, but in trying to deliver the best experience, we thought it best not to rush things.

 

Here's a preview of what to expect.

 

What's happening when?

In order to launch the new community by our target date, we need to shut down this site and fire up the other one.  We'll put up a notification here in the community to let people know when that's happening, but now you know.

 

Between now and then, expect to see some areas of the community blocked to new content. I'll try not to do that until the last minute, as I don't want to prevent you from getting answers. However, we have to decide at some point that we're moving what's here to the new location, and we need to pick a stopping point so we don't leave stuff behind.

 

What will our new community be like?

 

For starters, It's going to be organized a little differently. 

 

Instead of somewhat vague titles like "Getting Started," with a few product areas thrown in, we're planning to organize the Q&A categories by what you're trying to do.  So, when you log in, you will see areas like "Workflow," "Forms," "Document Generation," "Analytics," etc.  Beneath those categories, you'll find a list of platforms you are likely using. 

 

So, if you have a question about building a workflow in Nintex Workflow Cloud, you'll go to "workflow" and then Nintex Workflow Cloud.  We haven't built the interface yet, but this picture gives you an idea how we're approaching it:

lithiumstructurepic

Some of our members report having a hard time figuring out where to put their questions, and with the new structure, they should be able to find things more easily. Sure, there might be some overlap, but this should cut down on confusion. Plus, at Nintex, we look at our array of capabilities as a platform, not individual products. This is a step in moving the community in that direction, too.

 

What this means for your existing content:

 

Q&A: We're bringing our questions and answers over to the new platform.  If you asked it here, you should see it there.

 

Blogs: I'm still working on where, or even whether, we will permit members to share blog posts. I'll give you an update when I have one.

 

The Nintex Product Blog content is going to merge with our corporate blog.  So, look for a product channel in the corporate blog in the very near future. Same writers, same content about the value of our platform and its new features and capabilities. Just a new location.

 

Documents/Downloads:  To streamline processes for our customers, we'll no longer have duplicate links to product downloads, Release Notes, or knowledge base content which are in the Customer Portal.  Support cases will still be opened at the Support site. Areas that don't get much traffic (like the Nintex Gallery) will be archived.

 

How points and badges will work:

 

Some of you love earning badges and points and showing up on our leaderboard. Truth is, I love how much you love it, so we will have what's called "gamification" in the new community, too. It will work a little differently there, and I'll post a blog on that later. But the main thing to know is that in our new community, you'll have an opportunity to earn a "rank," not just a bunch of points. You earn rank by providing content of value, not just doing a lot of activity that may or may not be of value.  Here's a look at how rank, badges and the like appear in my profile on the Lithium community for community managers:

lithiumprofile

 

The community score is a number that represents influence based on feedback to the content you post.  You rank up when other members value your contributions.  The more value you provide, the higher you'll rank.  And it's not a game with only one winner.  Many people can be "valued contributors," or even "experts."  Just like real life.  This allows newcomers to raise their rank without worrying that they can never "catch up" to people who are seasoned Nintex veterans just because they've earned more points. But there will also be more and more ways to raise your community score, so highly-active users will always have something to strive for. See those badges above? More on those later, but those are earned, and can be put together to earn "trophies."  It's going to be much more involving and interesting than our current leaderboard.

 

Some things to know as we get closer to launch:

 

  • I'm going to start closing off areas of our community to new content to simplify the move.  For example, the Dev Talk is closed to new questions so I can move them to a better place in this community before we move the lot to the new platform.

 

  • Your inbox messages won't be transferred to the new platform. Nor will status updates. If there's something in your inbox you want to keep, copy/paste it somewhere now. I can't access your inbox now, and won't be able to after the move, either.

 

I want to thank you for taking the time to read this update. There's more to come. Be sure to "follow" me (hover over my name above and click "follow" on the pop-up card) so you can get notifications when I create new content. And follow me on Twitter, where I'll post updates like this.

 

I'm looking forward to the new community rolling out, and your participation in it!

So I made a rooky mistake and thought I would share so that you can all see that I am only human too, and sometimes, no matter what experience you have working with certain technologies, oversights can be made...

I had a very old solution (not mine) that used an InfoPath form and a workflow that run on all updates with a Run if action at the very beginning checking if the email flag was checked.  This had been working fine for a long time but the customer reported that they wanted the form slightly changed.

In good old fashioned InfoPath style, it informed me changes had been made in the list that needed to be reflected in the form (and rather unhelpfully didn't elaborate on the changes).  I needed to add this change for the customer so I accepted and published.  User was happy for a day or so until they realised that one of the dropdown controls had become unbound...!

I won't bore you with the details, but here is what I did.

  • the column was missing for whatever reason in InfoPath
  • time was limited so I created an additional column in my list, and used that in the InfoPath form
  • Using quick edit, copied the data from old column to new column

 

All perfectly reasonable right?  But what did I forget...?  Oh yeah, that workflow that run on modify of every single item.  That particular workflow emailed about 50 important people in my organisation...  and I sent 65 of them!  (shudder).

So after 24 hours of sobbing and panic, I calmed down and realised that this mistake was a simple one; one anyone could have made.  No process in place would have prevented it as I simply overlooked it.

 

Feel free to make me feel better with your rooky mistakes in the comments below... 

Many thanks to the people who hit the top 25 on our community leaderboard in 2017!

 

The top members of the leaderboard get there because of their contributions to the community. We reset the points to zero every year and see who bubbles up to the top.  Every few thousand points, you earn a new reputation level, the top one being "Rock Star."

 

Well, we had FOUR Rock Stars this year!  Congratulations to Marian Hatala, Cassy Freeman, Tomasz Poszytek and Rhia Wieclawek!

 

The contributions of all our members are valuable because they contribute to what makes this community so great: people coming together to ask questions, find answers and share knowledge. Here are the rest of the top 25:

Fernando HunthChris Ben, Jesse McHargue, Mike Matsako, Enrico Knapp, Andrew Glasser, Ryan Greenaway, Paul Crawford, Brendan Murphy, Giacomo Gelosi, Courtney Vargo, Lachlan Ainley, Eric Harris, Dan Barker, Sam Sysum, Aaron Labiosa, Chris Ellis, Manfred Lauer, Joshua Tan, Lakshmi C, and Brad Orluk.  Their point totals are in the images below.

 

Following our annual reset of points last January, I set our highest reputation level at a lower level - 20,000 points. It used to be a virtually impossible 80,000 points. My rationale was that I wanted to see how many members would reach the highest level in our community if we only made it a teensy bit more attainable.

 

Nobody had ever accumulated even 20,000 points, so I thought perhaps we'd have one person. Winding up with four is pretty amazing.

 

Points are accumulated for the contributions made in the community. From a couple of points for receiving a "like" to a couple dozen or so for receiving an answer marked correct.  The top contributors provided a great deal of value to the community, not to mention personal time, to help mark hundreds of answers in 2017.

 

It's worth noting that the mix of people says a lot about Nintex Connect. A lot of communities are dominated by one type of member. We have a nice mix of customers, Nintex Partners and Nintex employees in Connect.  And they all contribute to a helpful atmosphere that makes this place great. 

 

xchange banner

 

I hope you'll take the opportunity to make our connections personal by registering for our Nintex xchange conference.

 

 

 

As you may have already noticed, we have reset our points scheme for 2018. You can read about that annual event here.  I'm not going to set a new ladder for 2018 because we're going to have a new way to earn community cred in a new community! You can read more about that here: New Year, Renewed Community.

 

I wish you all a great 2018!

 

leadersleaders2

Filter Blog

By date: By tag: