Nintex State Machines and moving to Microsoft Power Automate

Budget and costs are always a concern especially when migrating or operating in the cloud.  We’ve recently helped clients convert Nintex Workflows to Microsoft Power Automate in order to help lower the subscription costs of Nintex.  

One of the larger challenges presented in these conversions is the state machine action offered by Nintex.  State Machines offer the client the ability to repeat actions or multiple parties dependent on an outcome. For example, a multiple party approval process that may move forward or backward through the process depends on whether the current party has approved the item or document.

Nintex workflow offered a pre-configured action to allow the users to create a state machine including the individual processes and statuses.

When migrating from Nintex to Microsoft Power Automate, there are a few things to consider, especially with a complicated workflow like a state machine.  The first is the fact that Power Automate does not have a matching action that duplicates a state machine. There are some other methods to achieve the same functionality such as a switch statement.  

Power Automate flows also time out after 30 days, this presents another potential issue if the process currently in place make take longer.  To avoid this issue in flow, we can split the Power Automate flow into separate smaller flows. One Power Automate flow will act as a controller, using an HTTP request action to call the needed Power Automate flow that will serve the actions for the current state of the machine.  Breaking up the Power Automate flows into smaller flows allows us to mitigate the 30-day timeout issue.

The ability to make an HTTP request and to start a flow via an HTTP request is a very powerful tool in Power Automate providing plenty of flexibility to fit the client’s needs.  If you have any questions or have encountered difficulty in your conversions, contact us at 724-423-9290.

SharePoint Meta Data Tags during Import

We’ve often discussed with client looking to utilize some of the features in SharePoint for document management the benefits of using meta data and tags to make finding document easier.  One of the challenges often faced with this approach is the migration of an existing file share or a large number of documents from another source.  Tagging such a large amount of files can prove problematic.

We have a current client facing such a situation.  There are 3rd party tools that can help with such a migration, but with recent changes and updates to the Microsoft Office 365 platform, those Office 365 customers can not benefit from a customized PowerShell script to tag files as they migrate.

We have a few options when tagging files as the script uploads them into their online SharePoint environment.  We could use the current folder structure to pull relevant tags, for example using a containing folder name to serve as a tag.  We could hard code the values for tags and perform multiple migrations, moving only folders we wish to take with a certain set of tags.  A more complicated migration may require an excel spreadsheet listing all the files to be migrated, their current location, and the tags for each file listed in cells on the same row as the file information.  The process can be catered to the needs of the customer thanks to the customization available in writing the script.

PowerShell provides us the flexibility and more importantly the efficiency needed to apply a large set of meta tag data to a large amount of documents in an automated fashion.  Combining the tags for documents with the new document library experience available in SharePoint allows any user to quickly find the documents via searching and filtering, and with PowerShell scripting – we can make the process of achieving a cleanly tagged document library a hassle free experience.

SharePoint / Office 365 serving as a Virtual Data Room

We recently had a request to set up a SharePoint environment to serve as a less featured version of a virtual data room so that an organization could make available documents to external users and organizations. SharePoint was chosen as the environment by the client because of the relative speed in which the needed components could be set up.

In this particular case, the client needed various other organizations to access certain files they would make available for a short amount of time. Rather than setting up a dropbox and going through the motions of inviting users to it and worrying about limitations imposed by drop box, the team asked us to spin up a SharePoint site for the purpose of sharing the files.

A single document library was created with the necessary folders for each outside organization. Access to each folder was granted to a corresponding group, so that each user into the system would only see their folder. The client could then drop the correct documents into each organization folder, and then simply invite those external users into the site and into the corresponding group.

This was set up in half a day and required minimal training to the client. External sharing in SharePoint and Office 365 is the driving force behind this particular solution. For this particular case, the invited users only needed a Microsoft account of some kind whether that be another Office 365 account, or an outlook account. More information on external sharing can be found here

SharePoint Branding and Customization

Often times a client interested in SharePoint wants to do something, sometimes small and sometimes drastic, to change the look of the out of the box SharePoint site. The basic branding changes include a few color palette changes and a logo placement. Eventually though, a client will want to alter some of the layout, remove a menu, or wish to lay out a page that just is not possible with the page layouts offered in SharePoint.

The first place to start branding your site can be with the SharePoint’s master page. SharePoint’s most recent version offers two out of the box master page layouts, named Oslo and Seattle. Seattle is the layout that most people who have used SharePoint are accustomed to, and Oslo utilizes a top line of navigation as opposed to a left menu that Seattle employs. These master pages can be customized to fit the branding requirements of the client as needed.

Web Parts are a fairly popular option for adding content to a SharePoint site. When creating a page in SharePoint, the user can opt for certain layout options that provide positions to place Web Parts. In some cases a client may find these layout options limited and unsuited for their needs. Custom page layouts can fill the void and provide these clients with the customization that meets their requirements.

Microsoft recently released the SharePoint color pallette tool which will provide an easier method for customizing all the colors involved in a SharePoint layout. Previously, a custom css stylesheet was the method for making site wide color changes, but utilizing SharePoint color pallettes make this job a whole lot easier. Stylesheets and css can still be used in certain cases to make precision like changes to a layout, along with some client side javascript or jquery.

A client may want to match their SharePoint environment to their external facing web site, or may just want to provide their users with a fresh look as opposed to the default SharePoint experience. In either case, there are plenty of avenues to make things look just right when it comes to a SharePoint site to change the generic out of the box look.

What is the most cost effective way to convert complex Lotus Notes databases?

Lotus Notes was a very effective tool for its time.   The platform allowed for the effective deployment of applications that could range in size – from simple expansions of existing database templates to highly customized and complex applications.

Converting mail files and templates has been done.     Many partners have developed advanced tools and techniques that makes performing a Lotus Notes migration a very painless process for the consumer.    But what do you do about the more complex applications?

The McKula Inc solution

Our methodology with complex Lotus Notes migrations is to take a very detailed and specific look at the application.   We do not rely on tools to attempt to estimate the application based upon forms, views, and agents.    We rely on our team and their experience to give you the best estimates for effort to convert your applications.     We perform a detailed assessment that includes interviews with the business users and a detailed analysis of the application by our own Lotus Notes developers.     Once we have completed our interviews and assessment, we will present you with a path to moving the application to a possible technology (such as SharePoint) along with an estimate of effort to do so.

When it comes to actual database conversion, we again rely on our experience working with both Lotus Notes and Microsoft technologies to build a new solution.     We are also available to assist with any data migration and constructing tools (if necessary) to assist you in moving your Lotus Notes data.    Our team has experience with common Lotus Notes data migration tools – including DocAve, Dell Migrator, and SWING.

Our strategy has been successful in converting complex Lotus Notes applications for many large, enterprise clients.     Contact us today if you have a challenging Lotus Notes migration on your schedule or would just like to ask some questions regarding a potential Lotus Notes migration opportunity.

I can’t find files in our file share – You need SharePoint

The File Share Problem

We’ve got a current customer that is facing a common problem as their file share grows. Nobody follows a naming convention, versioning is done with random bits of information like the date or month mixed into the document name, and files that may belong in more than one place are impossible to find. This is one of the perfect situations to leverage SharePoint metadata for files and document libraries.

The SharePoint Solution

Tagging documents with metadata is similar to tagging your friends in a Facebook photo. SharePoint allows you to manage what data you would like to be tag-gable to an uploaded document or even a document library. Rather than organizing your files into folders, which could get layers deep with no easy way to determine where a document current exists or should exists – leveraging SharePoint metadata would allow you to store your documents with a more linear approach – utilizing search and filter features that would use the selected metadata to find the documents you are looking for.

Our current customer has a need for a document to belong to a few separate areas. In their current file storage solution, this document can only live in one of those areas, and whomever is looking for it either must know this location or search through multiple areas until they find it. SharePoint’s metadata allows them to tag this document with multiple tags – making this document far easier to find. This also solves a concurrency problem, the document only lives once on the site as well.

Document versioning is another sore spot that SharePoint solves for this current customer. Rather than having users making versioned copies of files and inevitably failing to adhere to a naming convention, SharePoint takes care of all versioning issues – providing a clean way to retrieve older versions of the documents in the library.

For this customer – SharePoint’s document library functionality and metadata solution was a perfect solution to their needs.

Office 365 Who To Call List with JSLink Customization

Office 365 JSLink

The Problem

This past week we had a request from a client to display a list of employees to call based on a selected department.  They asked that the menu specifically be displayed on the left side of the screen with the department users displayed in two columns in a box like display.  They also needed to be able to manage not only the users and their information, but the departments as well.

The Solution

We needed some custom lists to allow the client to update their own departments and call lists.  We provided a person link field to help with photographs, along with some custom fields that the client could use to better explain why that particular user should be called.

The challenge came in both the menu and the custom display.  For the menu – we utilized a content editor web part that linked to a custom html page.  This custom page grabbed the department list and structure from the SharePoint API for lists and formatted it utilizing some custom css and javascript.

Clicking on a department would push that selected department into the query string – which would give us a way to determine which users to show.  We used a Query String Filter Web Part on the page to facilitate sending the values to our display web part area which was linked to our Who To Call list view.

To achieve a customized look of this list, we took advantage of a JSLink setup which allowed us to customize the list view to suit the customers needs.

Bootstrap provided us some layout options to achieve the look the client desired. Adding the javascript file under Master Page Gallery then Display Templates as a Javascript Display Template allowed us to then use it as a JSLink file for our view.

Nintex Forms and Workflows

The main tools to utilize in SharePoint development of forms and workflows have been InfoPath and SharePoint Designer.  However, with Microsoft’s latest updates in 2016, new versions of InfoPath and SharePoint Designer were missing from the list.  Microsoft has stated that there won’t be new versions of InfoPath, and it seems to be the case with Designer as well.  Both will be supported by Microsoft for years to come, but existing versions aren’t very intuitive.  Without future improvements, it may be time for businesses to look at other options.  One such option that stands out from the rest is Nintex Workflows and Forms

Nintex extends SharePoint’s functionality, giving a user-friendly way to create what would normally take extensive programming to achieve.  The two products they offer are Nintex Forms and Nintex Workflows.  They can be purchased and utilized separately if needed.  Nintex is also compatible with both SharePoint on-premise and Office 365.

Workflows are key in automating processes that would normally require a manual effort.  Workflows can be either scheduled to run or can be triggered by an event.  Nintex Workflows accomplishes this simply by point-and-click.  Nintex Workflows provides an interface with drag and drop actions that can be specifically configured to users’ needs.  In the workflow designer, you are given a flowchart view of the actions within the workflow.  A menu of draggable actions are shown to the left of this section.  Email notifications, setting SharePoint fields, assigning a task to users, and triggering another workflow are all standard options in the menu.  In addition, actions normally reserved for programming can be employed, such as setting variables, loops, and if-statements.

Forms are critical for easily capturing information and setting fields in SharePoint.  Similar to Nintex Workflows, forms can be built through Nintex using drag and drop.  A variety of form controls are available in the menu that can be placed on the form’s canvas.  These include all the basic form fields like labels, textboxes, checkboxes, and radio lists.  Once placed on the canvas, the fields can be connected to SharePoint fields.  However, there is also a tab containing all the fields in the associated SharePoint list.  These can be dragged onto the canvas as well, looking to column type to determine which form control is necessary.  For more advanced users, there is a section in the settings to add CSS and JavaScript to extend Nintex out of the box functionality.  The configuration options for each field allows for CSS classes and JavaScript IDs to be set.

Nintex will be an additional cost to SharePoint’s out of the box fees, but will allow for more extensive forms and workflows to be created with far less development time.  An additional advantage to Nintex is that a programming background is not required when setting up basic workflows and forms.  However, when working on more intricate solutions, programming experience certainly helps.