Looking back and ahead

At the end of a year I have the tendency to look back at the past year and set a vision of what lies in the twelve months to come.


When I look at the post history from this year I must admit that this blog was pretty silent in 2013. I published only three posts in January - which is eleven months ago. Then nothing has happened until this post. Wow, time flew by.

What has kept me from publishing new posts in this time? Frankly, I cannot attribute to a single cause. There were multiple reasons for this:
  • I have started a new job in February which provided new challenges.
  • In my prior job I was regularly involved in Nintex projects. In my new job my projects are most of the time around software architecture and quality assurance in SharePoint development projects. (SharePoint will never let you go ;-))
  • and many other reasons.
So with the new tasks in my daily job, I am going to shift the core topics of this blog more in the direction of software architecture and quality assurance. Nintex posts will still be published from time to time but the majority of posts will be around software architecture and quality assurance in the context of SharePoint.

Additionally, I have become a regular consumer of lifehack and personal effectiveness sites. So when an interesting topic from this area comes up, I am going to discuss this as well.

So stay tuned.

Comments

Post a Comment

Popular posts from this blog

How long does "Delay for..." really wait?

Image
First looking at the action "Pause for..." I was thinking think that I could configure the delay period precisely to the minute. However, when I used this activity I discovered that the activity did not behave as I as expected. This was especially true when I entered an interval shorter than five minutes. I always waited longer than configured. Looking deeper, I found out that the cause for this is the SPTimerJob job-workflow  which controls the triggers for " Pause for... ". This timer job runs with the standard configuration every five minutes. If you set " Pause for... " to a shorter interval, the trigger send by the timer job will be sent every five minutes anyway. The same applies when you set the action to pause the workflow for any period of time that lies between the configured schedule for job-workflow . Of course, an option to solve this issue is to reconfigure the timer job to run in shorter intervals. But ask yourself if this is really nece
Read more

How to Handle Environment Variables with Nintex Workflow

Image
A topic you sure will run across is how to handle environment variables when you deploy workflows designed with Nintex Workflow. The values are by definition just valid for one specific environment, and have to be changed in order to deploy the workflow into another environment. Example for environment variables are URLs of web services or service accounts, which are different between development, test and production system. Basically, there are three ways how you can handle this information: store the information within the workflow activity create a workflow variable create a workflow constant Most people start with alternative 1 . The environment specific information is directly configured on the workflow activities. This has one advantage: You are pretty fast when you configure the activities the first time. But in the long run the disadvantages outweigh. After deploying the workflow from environment to the next stage, you have to update all affected activities. Beside th
Read more

Run Now in Nintex Workflow 2010

Image
With version 2.3 Nintex introduced Run Now into Nintex Workflow 2010. Nintex promises that with Run Now the integration with other system will be easier, because workflow designers can test actions with Run Now support already during the design stage. It is not necessary to start and step through the workflow until you reach the actions. Can it keep up to the promise? Run Now can be accesed on all supported actions during the workflow design stage. Start with a new blank workflow and then drag an integration action into the design area. I will be using Query LDAP for the rest of this post. The other actions work alike. After you have configured the action select "Run Now" in the ribbon. A new window is displayed where you can test the configuration. If you are using workflow variables for the configuration you can replace them with actual values. And remember: As soon as you press execute the target system will behave as if you execute the action from the workfl
Read more