The ongoing challenges of HR policy management at small to medium organizations (SMBs) are constantly changing and evolving, leaving HR managers overwhelmed and frustrated. Strict government regulations and an increase in employee legal disputes complicates policy development and automating the process of distributing and receiving employee acknowledgement.
Once a policy is developed and approved, what is the best way for organizations to communicate it and distribute it? Where and how can employees access it, especially if the policy is urgent and the employee is not in the office? Furthermore, how can HR managers receive confirmation that employees read, understood, and acknowledged the policy?
Recently Microsoft announced it would no longer support coded sandbox solutions and gave less than 30 days’ notice. Put in business power user terms, if you have developed business solutions such as an Intranet, help desk, employee self-service or other custom site on Office 365 SharePoint Online they may stop working soon if you did not build them using the correct methods. The impact could impact your ability to conduct business. This recent announcement may impact any web parts, forms, workflows or branding where code was used by the original developers. Many of these are probably are core to the operation of the application solution. There are a number of other solution development approaches that will become a problem as well. This article will look at business solution development and the “critical” mistakes internal developers and consultants can make and what you can do about it before August 28, 2016.