SharePoint 2010 was chosen due to their current usage of the Microsoft technology stack, anticipated high adoption rate, and the many capabilities and features SharePoint provides. In order to maximize the benefits of their investment in SharePoint, the company selected TDK to create and carry out a SharePoint implementation plan.
ESCO felt that their corporate HR department would benefit most from SharePoint. However, they wanted to also assess the benefits of implementing SharePoint for all corporate departments and subsidiaries. Phase 1 therefore consisted of interfacing with the CFO and corporate HR stakeholders to define the requirements for the HR SharePoint site. Additionally, TDK worked with ESCO to define high level requirements for all corporate departments and subsidiaries. As a result of this process they decided that including their Finance department in the Phase 1 development effort would be beneficial. TDK defined the user roles, groups, and security for the system. TDK then began designing and developing the SharePoint sites for both the corporate HR and Finance departments.
SharePoint 2010 was to be installed and configured to provide all of the enterprise features. The first task was to modify the SharePoint Portal to follow the company's corporate branding strategy. This was accomplished using a custom masterpage, CSS, and jQuery. The second task was to create a custom stock ticker to display up to date stock information for all subsidiary companies. Since there were no web parts available that provided this functionality, a custom web part was developed. The custom web part used XSLT Data Views, CSS, and the Google Stock API. Each time the page was refreshed, the stock information would be updated. The final task was to create a reusable InfoPath form for gathering information related to ongoing tax reviews. The form retrieved data from multiple SharePoint lists, and when submitted the form updated SharePoint lists based on the content being submitted. The form relied on qRules for InfoPath to allow for dynamic generation of fields based on the content that was being entered. The qRules tool assisted in generating the code behind files, which is normally a time consuming and error prone process. The InfoPath forms were deployed as a template file to allow the form to be reused on multiple SharePoint sites.