Nintex InspireX – Understanding Nintex’s Cloud Architecture

29 02 2016

Nintex InspireXFor most organisations, when it comes to the cloud, it is important to understand where their data is, where it goes and what is done with it. Also understanding how the services they use work aids them in developing current and further applications.

Mike Fitzmaurice (@mikefitz) and Patrick Hosch (@patrickhosch) from Nintex gave a high level overview of what Nintex’s Cloud Architecture consists of now, what it looked like in the past and what it will look like in the short to medium term.

For me the key thing to understand was where my customer’s data is held. In fact, very little data is held and when it is it generally it is held for short amounts of time. Most of the data that is held is held to facilitate Nintex Mobile.

The key thing that I took away from the session was that Nintex appear to be moving towards having their services closely aligned with the locations that Microsoft host Office 365.

Advertisements




Nintex InspireX – Nintex Workflow Platform Jumpstart

28 02 2016

Nintex InspireXIt was 8am in Las Vegas and instead of feeding the slot machines in the Aria hotel I was in the Nintex Workflow Platform Jumpstart pre-conferee workshop being run by TekDogs Jason Keller.

The workshop was a great way for me to kick of the conference. For me it reinforced what I already know about Nintex Workflow and Forms but also gave me a few tips and tricks that I could take back to the office to share with my team.

If you want to learn more about Nintex through training, there are various options listed below:

I have used all of these and are all very good.

The material covered in the training was copyrighted so I cannot share all of it however the following tip (with my own additions) and others that I already do, I’ll share over the coming months.

Tip – Use a Service Account

Create one or more service accounts for workflows. I like to use a dedicated workflow service account for each departments workflows and sometimes for specific workflows. Your IT department will have a naming convention for service accounts but here are some examples I would use:

  • WF-HR-LeaveRequest
  • WF-IT-NewHardware

Some will make sure that the service account password does not expired. I prefer to have a process to change the password periodically but have it expire once a year.
If you set the service accounts as “Constants” you can then limit access by using security groups.