Portfolio

SharePoint Policy Management System

Boosted performance thanks to SharePoint policy management

This client is global insurance provider with a long history of notable clients. Backed by one of the highest rated insurers in the Gulf region with a rating of “A” from Standard and Poor’s and “A” from A.M. Best.

Executive brief

Minimising downtime, maximising success

Our client, a global insurance provider, reached out to us looking for assistance updating their policy management system, running on an aged version of SharePoint and constructed with complex custom code.

The key requirements of the underwriting management system included management of user permissions, tracking user actions, and sharing amendments in live documents. We were able to simplify the code, modernise the UI, streamline workflows, and future-proof their solution.

The Challenge

Enhancing a defunct system

The client needed to update their policy management system with minimal downtime and limited change to the user experience. They knew their current solution could no longer be managed or supported effectively.

 

By keeping their current SharePoint operation, they were risking:

  • Compliance violations by using end-of-life software
  • No vendor support
  • A slower system, wasting man hours
  • Reduced data security
  • Missing out on a variety of new updates

The Solution

A polished system with enhanced UI

After meeting with them and hearing their challenge, we proposed a solution in line with their goals, and was more than capable of meeting their needs. The end solution was an improved policy management system which had the exact same features as the previous version…but better.

 

After removing redundant documents and code from the backend of the site, we were able to dramatically simplify the migration process. To make long-term maintenance of the software easier we decided to implement source control, upgrade the base code to C# a more widely used language.

 

In terms of functionality the application appeared unchanged, but the modern SharePoint UI and underlying solution was dramatically modernised compared to the original.

 

In short it was simplified, streamlined, and modern.

The Results

End-user and technical improvements

By the end of this project, the client saw several key benefits that affected the end-user and overall technical improvements that benefited the company, these included:

 

End-user improvements:

  • improved UI
  • improved performance
  • improved workflow

 

Technical improvements

  • Simplified code- making maintenance easier in the long-run
  • Improved custom software
  • Removed unnecessary tools that were causing huge expense
  • Source code moved to the cloud, making updates much easier

Looking to upgrade your current solution?

Need help building a new SharePoint solution? Our team is skilled in SharePoint development, meaning you get exactly what you want, and when you want it.

Contact us today

Info

26th January 2023

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by egforit.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress,
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
-id-[app_id],-session-[add-id]

×