We Take Great Pride In Our Work.
Recent and notable case studies
project details
Incident Tracker is a flexible reporting software with a rich set of features such as workflows, digital dynamic forms, analytics and trending used by industries ranging from healthcare, security firms, libraries, education, businesses, and government agencies. It allows users to customize categories, locations, and digitize paper forms. Also integrates with third-party active directory. Integrates with other systems using API’s and integration authentication. Incident Tracker automates alerts and workflows to create an easy to use and efficient system that shares, tracks, and secures information.
Technologies Utilized
Xamarin, JavaScript, .Net, C#, Azure, SQL, Integration Services, .Net Core, SendGrid
Platforms
project details
Nintex Workflow and Form Conversion to PowerApps Forms and PowerAutomate
Third-party license costs are often a necessary evil when it comes to enterprise-level organizations. These licensed applications often enhance an existing product with a layer of extra functionality or usability. In this particular case, Westinghouse was migrating their existing on-premise SharePoint environment to the Office 365 cloud environment. Numerous Nintex workflows and forms had existed on the on-premise environment, and Westinghouse planned to use the opportunity to convert these Nintex workflows and forms to Microsoft PowerAutomate and Forms. Microsoft products are included in their cloud environment, so Westinghouse could reduce the needed license costs on Nintex.
The plan was simple, convert larger and more complex Nintex Workflows to PowerAutomate, starting with all Nintex workflows with more than 5 actions. These larger workflows would begin to reduce the licensing cost for Westinghouse, and offered an opportunity to rework or update any workflows to the benefit of the customer.
In some cases, improvements were available by converting to PowerAutomate whether that be a deeper integration with other Microsoft products such as teams, or automated scheduling to run a PowerAutomate flow at a scheduled time.
The result of the conversion work was cost savings based on less usage of Nintex flows and forms, and a collection of updated PowerAutomate flows and closely integrated Forms for many newly migrated SharePoint sites
Technologies Utilized
Platforms
SharePoint
project details
Building a custom membership provider for an on-premise SharePoint environment
A unique challenge to be sure, our client SAE International brought us into a problem where their current membership provider had stopped authenticating. They attempted to rebuild the on-premise SharePoint sites but had no success.
An oracle database was used to contain not just the account credentials, but also the numerous SharePoint site forums available to each account.
Solving this issue means not just building a membership provider for authentication, but also building a custom web part to display the accessible forum sites available to the logged-in user.
The custom provider was built in .NET and installed into the SharePoint environment. The first step was to ensure the SharePoint site was correctly using the new provider, and then to build the claims provided by the provider in a way that would be accepted in the SharePoint environment.
Once this was completed, a custom web part, again built in .NET, was written and installed onto the SharePoint site. This web part built the menu which displayed all the forums the specific logged-in user would have access to.
Technologies Utilized
Platforms
project details
Westinghouse Nuclear Ticket Tracking Portal
Technologies Utilized
O365, PowerAutomate, PowerApps
Platforms
Browser
