01
Define the contact workflow
Shinetech analysed the requirements with the client and designed a custom Web Part using the SharePoint SDK to retrieve and display contacts.
← Back to all case studies
Case study
Connecting contact records and email actions with SharePoint
A US software company extended contact management with an ASP.NET application, synchronised records and a SharePoint Web Part for emailing selected contacts.
- Client context
- A US provider of custom business solutions
- Architecture
- 3 layers
- Data
- Access and SharePoint contacts
- Action
- Email selected contacts
The situation
The business need
The client delivered document management, portals, workflow and related business solutions. It needed contact additions, changes and deletions to be saved both to an Access database and a SharePoint contact list.
Users also needed to retrieve the contact list, choose recipients and send email without a separate manual workflow.
The approach
How the team delivered
02
Separate presentation and business logic
The ASP.NET presentation layer used UserControls. C# components handled business logic and called the data-access layer and SharePoint web services.
03
Implement shared data access
The data layer used iBatis.NET DAO and SqlMapper for persistence. The application supported record changes alongside SharePoint contact-list updates.
Project context
Technology and delivery
Technologies and working practices used in this engagement.
ASP.NETC#SharePointiBatis.NET
The result
What the engagement delivered
Connected contact records
The application addressed updates across the database and SharePoint list.
An integrated email action
Users could select contacts in the Web Part and send email to the chosen recipients.
Clear application boundaries
Presentation, business logic and persistence were separated within the implementation.
Need to connect SharePoint with an existing business application?
Tell us about your software, workflows and delivery requirements.
Discuss your project