Three words, three values. These three words have been helping me set up and drive norm and culture of the teams I have been working with in the past ten years or so. I have to say, I started with a much bigger list of values. Caring, Teamwork, Agility, etc. were all on my list. Overtime, I set a goal and a challenge for myself to simplify the values to three words. I believed, this would it make simpler for everyone to understand, remember, and apply. ...

Browsing the web, today I came across the news that Drobbox is also ditching code sharing and moving to Native Development for their mobile apps. Looking at the recent trends of big companies, like Airbnb, move towards native mobile development, this was not a surprise at all. However, it made me have a flashback about our mobile development journey for Nintex Mobile. Back in late 2011/early 2012 when we started looking into which technology to use for Nintex Mobile, we POCed Native development, PhoneGap, C++ and Xamarin. However, the most important question we wanted to answer was not which technology was cheaper/quicker to develop on, but ...

Sure, Process Automation Life Cycle, i.e. PALC, is something I just made up, but why? Coming form Software Development background, Not long time ago, we have always been talking about Software Development Life Cycle, SDLC, methods and best practices (and a lot of people still do). We did that, because as software development was maturing, we needed best practices and guidelines to ensure the success of the projects. Since then SDLC has come a long way and we have got a lot better in delivering software systems. ...

We get this question a lot that why some Runtime Rules work on Android but no on iOS, Windows or Windows Phone. So if you have created a validation rule or formatting rule in Nintex Form which works on Android but not the other mobile devices, most probably the issue is that you have used a custom JavaScript syntax instead of Nintex Form functions somewhere in your rule. In most of the cases we have seen, users use == instead of equals(), > instead of greaterThan or < instead of smallerThan functions. ...

Yes, I truly believe that a product is pretty much reflects the team(s) working on it, their standard and their work culture. In the software industry we keep talking about getting closer to customers and hearing their feedback, validating features/products, market testing etc.. which are all very valid tasks and we should do them in most scenarios. I think we sometime miss the point that instead of blindly listening to user’s feedback, we need to listen to them and then start working on providing the best solution considering all possibilities and constraints and this is something which has to come from the team, not the team manger, not the UX and not the product manager but the team which includes all of the above plus engineers and testers. Fair enough I have always been saying that one person should have the final say and I still believe in that but the point is that you cannot/should not expect one person to cover all the possible requirements, quality measures and failure points. I dare saying that’s very, very unlikely that one person can cover everything and not miss one. If you are in a team which operates like that I bet yourself in situations where something has gone wrong and the engineers or QA would say “It was not part of acceptance criteria” and the product manager would say “We did not get that from the user testing UX team conducted” and the same sort of “excuses” from different people. This kind of team/culture would reflect in the product as either poor quality or missed deadlines. ...

It’s a pretty standard question, isn’t it? it’s kinda being asked in all job interviews. and also once in a while when having a drink with your friends. Up until a few years ago, normally my answer to this question was “my last project” and I was very proud of it. This was really my honest and genuine answer because most of the time each project I was involved was better than the previous one. Some projects however left me more proud and I kept mentioning them for a while. These were the project which would impact people’s life in a good way ex. makes it easier for people to do a job, make their life better or make them enjoy them their job/life much more. ...

Update 2016/06/23 Nintex Mobile has deprecated support of pre-populating sign in information using deep link. On the other hand you now can Launch the app, open a specific form and pre-populate it’s field using a deep link url. ———————————————————– Nintex Mobile is a great way to take your business process with you on the go anywhere; no matter you are online or offline. To use the app you need to download it from the store and sign in to a specific SharePoint URL using your credentials. ...

Once in a while you may end up having orphan Nintex Workflow tasks in your environment. Normally you wont end up in this situation in you production environment as this is normally as result of playing with the workflow or the list. But anyway we don’t live in the perfect world and things like this happen and when it happens it can be really annoying. Specially if you are using Nintex Mobile to respond to your tasks. One symptom is that you keep getting the tasks even though you delete local storage. So here I show you how to delete the orphan tasks for good ...

So first things first. You are asking if this is a marketing email? answer is yes. I am expanding my team and I am writing this post to convince smart developers like yourself to come and work with us at Nintex. It’s me writing this and these are my own view points. No one from the company has asked me to write this (in fact no one knows that I am writing this. not even HR). ...