From my consulting experience, I have noticed one core issue that many IT administrators and power users face in their implementation towards integration of Outlook/Exchange and SharePoint – the ‘incompleteness’ of the captured Outlook data in SharePoint. And this happens when there is a lack of metadata available to describe the published item in SharePoint. Because of this, user adoption of SharePoint could suffer in the organization.
For instance, emails can be saved as Outlook Message Format (.MSG extension) from Outlook > File > Save As, and then can be uploaded directly through the native SharePoint UI. And when one clicks the MSG file from SharePoint, it will open up in Outlook (if installed) which the user can then reply/forward. This provides for a basic integration of storing Outlook emails to SharePoint. However for non-Outlook users, the MSG file is not as useful because SharePoint can’t display the MSG file and its content such as attachments natively.
There are other important limitations with as such! The upload of the MSG file of the email to SharePoint does not bring along any additional attributes or metadata information (To, From, Subject, Sender etc.) to the SharePoint columns. So, one need to manually feed additional metadata information to describe it in the SharePoint columns to give a meaning to the uploaded email MSG file. Not only, it is time consuming and laborious to save, upload the email file and enter metadata to describe it, one has to repeat the same step for each email. And it can be quite a daunting task if you have thousands of emails in your Inbox. This limitation can significantly handicap the usefulness and usability of such data in SharePoint.
Email enabling a SharePoint list or library could be another option (that is, one can include the email address of the SharePoint list as one of the recipients to have that email stored in the SharePoint). But again, the actual email is stored in .EML format in SharePoint, which only recent versions of Microsoft Outlook supports. Moreover, this process does not populate useful email metadata to the SharePoint columns. Other limitation with this approach is the administration overhead to setup SharePoint with unique email addresses and broadcast it to the users. This approach does not work on your existing emails and other Outlook items such as appointments, tasks or contacts and hence, cannot account as a cumulative solution for your Outlook/Exchange data.
If the solution discussed above is exactly your requirement, then you are in for luck and need not read further of this blog. But if you find yourself needing for a seamless way to bring Outlook emails and data to SharePoint along with useful metadata information of the email to corresponding SharePoint columns, then read on as I am going to discuss how this can be achieved fairly simple with one of my application ‘DataPublisher for Outlook & SharePoint’.
DataPublisher exists as an add-in application in your Microsoft Outlook. In this application, the first step you (or the administrator in Team Edition) would do is to specify any number of destination SharePoint lists that will store the published emails or other items from Outlook. This is followed by simple mapping of attributes or fields between the Outlook mail (or other item types) and SharePoint columns. This is done so that the add-in can extract the relevant metadata information (such as To, From, Categories, Subject, Body etc.) from the email and populate it automatically to the published item on the SharePoint side.
And storing emails from Outlook to SharePoint is just a matter of a click (or two, if you had linked multiple SharePoint lists to Outlook). To be even more productive, you can select multiple emails and publish them to SharePoint.
Once published, the SharePoint item will contain the email (OutlookItem.msg) as well as relevant metadata information that were mapped. Attachments of the email are available as clickable links.
For that matter, you can publish all the items of an Outlook folder to a particular SharePoint list in a click. This will publish all the items in that Outlook/Exchange folder to the chosen SharePoint lists in batch. As the transfer is done in the background outside the Outlook.exe process, you can continue working in Outlook without being interrupted.
No matter what technique you use, DataPublisher add-in pushes the emails to your SharePoint along with attachments of the email and the metadata information (chosen when performing mapping of fields) to the SharePoint columns. In fact, to view the content of the email, you don’t even need to open the MSG file from SharePoint as the metadata information contains the email body too. Attachments of the email can be directly accessed and viewed natively from the SharePoint item without opening the MSG file in Outlook or other email client application.
Outlook items with custom fields – if you use a custom form on an Outlook folder, most likely you might have added custom fields to collect additional data from users. With DataPublisher, you can map those custom fields to SharePoint columns too to bring the custom data to the corresponding custom fields to SharePoint.
Outlook/Exchange to SharePoint publishing is not limited to emails. In fact, with DataPublisher, you can implement the same technique to push appointments, tasks, journals or contacts to your chosen SharePoint destination, while preserving the metadata information and attachments.
You can also set DataPublisher to automatically push incoming emails in your Inbox to SharePoint without requiring you to do it. That is, as soon as new emails are received or new appointments are added, the add-in would export those items to SharePoint with the same logic. This is ideal if you want to maintain a live copy of your Outlook folder items (e.g. Inbox, Calendar) in SharePoint.
DataPublisher application works in your Exchange Public folders or PST just as fine as it does in your Inbox. And if your organization still uses Public folders to store data and documents, you could make use of DataPublisher add-in to export and migrate all of it to SharePoint repositories without worrying about the integrity or loss of information on the SharePoint side.
In a nutshell, you can just concentrate on deciding which emails to store in SharePoint and leave the question on ‘how’ and other technical complexities to DataPublisher application. So go ahead and adapt our content management solution from Outlook to SharePoint for your varied requirements such as filling caller and problem metadata information from emails to trouble tickets in your SharePoint Issue Tracking lists, submitting meetings and schedules from Outlook Calendars to SharePoint calendars, Exchange Public Folders migration to SharePoint, email retention and archival from Outlook to SharePoint repositories as part of company’s legal policy etc.
Remark: In the Enterprise Team edition of DataPublisher application, choosing the destination SharePoint lists and the mapping of fields is done once by the administrator and deployed to all other users automatically. This makes it very easy for workgroup users to file and publish emails, attachments, appointments, tasks or contacts along with the mapped metadata to the administrator’s specified SharePoint list and columns from within their Outlook. Streamlining these processes for all users of the organization, brings about a bridging solution for content publishing and management from Microsoft Outlook to SharePoint.
It is almost 3 years ago AssistMyTeam was conceived and founded and it has come a long way since. The journey and experience has been worthwhile in-spite of all the challenges, stumbling blocks and failures that are associated with a start-up. Today, I am proud to say, it is a pioneer in providing IT business and CRM solutions on three of Microsoft Core platforms – Microsoft Office, Microsoft Exchange and Microsoft SharePoint. Our clienteles include some big names in the fortune 500 companies such as Microsoft Corporation, Samsung, Goodrich, Cybercom, Fujitsu, Capital Finance Company etc. (see the complete list). This is a testimony to the high quality standards we have set in all our products and solutions. Reliable, highly scalable and cost effective solutions are what drives our applications in helping businesses and teams become more information-driven, even more dynamic.
Our foremost task at this point is to make all our products compatible with the new Microsoft Office 2013. With every new Office release, there are changes in workflows and user interface and this is where the time consuming tasks are. We have to make a middle path where the new features in the new Office version is supported without breaking the existing compatibility with older versions of Office. Because quite often many IT departments feel comfortable with their existing versions of Office and seldom rush to adopt new versions. Another challenge we are tackling currently is supporting both 32 bit and 64 bit native versions of Microsoft Office applications. The queries and pressure from prospective and existing users for 64 bit compatibility has lead us to prioritize our short term goals and push back new product development and release. Moreover, who would want to lose a half of Office 64 bit users!
I am very excited about 2013 as what we design and build these moments will steer the direction of AssistMyTeam for the next 5 years – which is exploiting the cloud computing services that Microsoft is focusing on for their office applications. Microsoft Office 365 Exchange and SharePoint Online are such offerings and we have seen in the last year alone, one-third of our clienteles were already using these cloud based services. So, we had been investing heavily in term of funds and development to support Office 365 on all our products. And we are glad that we made the right move.
I also want to reflect on our commitment for giving back to the community. But before that, let me emphasis on an old saying – success is just not merely a reward, rather it is a responsibility. I believe any business, no matter how small or big, can give back to improve the lives of others. And I truly value the exposure and goodwill generated by such acts of kindness. Since its founding, I offer free licenses to use my products to educational institutions and universities around the world. And that tradition is still continued today and I am happy that more than 80 institutions and renowned universities have implemented one or more of my products and solutions in their workstations and departments. Notable among them are in the top ten world ranking including University of Cambridge, University College London (UCL), University of Oxford, University of California, Berkeley (UCB), Columbia University, Stanford University, Australian National University, Canberra. (see the complete list)
So, if you represent an educational institution/university/non-profit organization and would like to use one or more of my software solutions, don’t miss this opportunity. Simply write to us (or refer to this page) to participate in our academic license programs.
It’s simple! Computers are so much engraved in today’s businesses, but in the end, the ultimate goal is all about maximizing knowledge wealth and enhancing human intelligence. And for any company, this acquired intelligence is the single most valuable asset. When such intelligence is utilized, shared and factored in, innovation and inventions take precedent, spiraling the business and profit level of the company. Therefore, in today’s competitive world, companies take a great deal of efforts to implement an effective knowledge retention and management policy, to prepare and compete for the future. This is where, a knowledge management system or what we popularly refer to as ‘knowledge base’ can make all the differences in aiding productivity and operational skills of the people of the company.
Besides, enabling knowledge retention for future, a knowledge base system can be effectively used for addressing recurring issues reported by your end-users. Consider a scenario, where you and your support team frequently find trying to solve the same issue over and over. Your end-users send you emails on similar issues repeatedly. And if you are already aware of the solution, typically, you will try to compose the solution or if you have vague recollection of it, you would try to navigate to your existing document libraries, past email conversations etc. Just consider how much time and effort you had wasted in trying to find the right information at the moment of need, not to mention the delayed response to the support request. If there was a knowledge base system at place in the organization, you could have shared your knowledge with other team members so that everyone has the same understanding and are communicating the same message when asked about specific issues.
There are many ways of implementing knowledge management systems. One of them is using Microsoft SharePoint repositories. In most cases, you might already have a SharePoint based site already running in your company’s network, or may be using one of the hosted SharePoint services, such Microsoft Office 365, which is becoming quite popular for small businesses. And we already know, one of the great capabilities of SharePoint is its collaborative and sharing feature. This makes it very versatile for storing knowledge base articles, which can be shared among the staffs and personals, especially those involve in customer service.
However, there is one crippling limitation of SharePoint based knowledge base, which is its isolation state and lack of integration with email clients such as Microsoft Outlook. This is at disadvantage for customer support team that relies on email as the primary mode of communication. Because when a support request email is received, support staff would need to refer to the SharePoint site and search for the relevant knowledge base article, and if they manage to find it, there is no direct and effective way of using that article along with its associated documents and files in the email reply. One can copy the content from the KB article to the email, however, that is time consuming and cumbersome, and often not all information and files make it to the email. So, after putting much effort and time, you still didn’t get the complete KB article inserted into the email reply. Moreover, the frequent switching back and forth between the email client and SharePoint site tends to loosen the focus of the support staff, leaving him/her frustrated. Evidently, organizations and teams that leverage SharePoint as knowledge base would need to reinvent the wheel and implement an efficient way of importing SharePoint based article or document, to outgoing email reply.
Because of such limitation in SharePoint based knowledge base system, it made me thinking on how to bridge this gap and come up with a solution that offers a seamless integration of the SharePoint based KB articles in Microsoft Outlook. The effort of this work leads to the development of an Microsoft Outlook add-in, called ‘Team KnowledgeBase for Outlook & SharePoint‘. Currently available as a beta offering, with Team KnowledgeBase installed, one can effortlessly locate a KB article (stored on SharePoint) relevant to an issue from within Outlook itself, and insert it into an outgoing email reply in a single click. All these and more making sure, the outgoing email retains all the actual files and the original formatting of the selected KB article. No more frequent switching between Outlook and SharePoint, no more copy-paste job etc. In fact, you don’t even need to type in anything into the email reply. Team KnowledgeBase add-in does that for you on the fly.
There are two portions of Team KnowledgeBase – an admin install and a user install. The former is for managers and administrators, who would perform the global configuration of the knowledge base, choose and setup SharePoint KB lists, and map fields between Outlook and SharePoint, whereas the later is for individual support staff that will be making use of the KB articles stored in one or more of the administrator chosen SharePoint lists, from Outlook. Even though KB articles are stored on your SharePoint list, every user can make use of it in Microsoft Outlook to reply to emails in a snap.
A pop-up dialog box allows you to browse through the existing knowledge base articles, and select the relevant article to be embedded either as attachment, inline or as URL into the email reply.
You can make use of a filter, to refine your search. For example, you can display the KB articles listing by specifying a problem category and/or a type. Alternative, you can also specify keywords for a full text search such that matching KB articles that meet the criteria are only displayed, for selection. Selected KB article can be applied or inserted into the replied email in varied format.
You can choose to insert as attachment in the form of a word document (*.doc), Adobe PDF (*.pdf), Microsoft XPS (*.xps) or as single file MHTML (*.mht).
You can also embed the selected KB article directly into the body of the email reply. Any inline images and formatting are preserved in its original state in the reply also.
Alternatively, if your SharePoint site is opened (i.e., accessible via the web), then you can also insert the hyperlink or URL of the selected KB article into the reply, so that the recipient can simply click the hyperlink to open the relevant article in their web browser.
The good thing about a SharePoint based knowledge base system is the accessibility, not only for the staffs, but also for the end users. Over time, the knowledge base repository would have enough solutions on common problems and issues. You can exploit this wealth of knowledge, by allowing your SharePoint knowledge base site accessible on the web. Such that your end-users and customers experiencing technical challenges can self-service the answer to their problem by accessing this web-based knowledge base. They can even make use of the SharePoint inbuilt search functionality to query KB articles by keywords. This can eliminate unnecessary phone calls and allows your customers to quickly get answers to questions and maximize the use of your knowledge base.
On the cost front, as Team KnowledgeBase leverages your existing Outlook and SharePoint resources, there is no extra hardware/software cost that you will have to incur in implementing an enterprise-wide knowledge base for your team. As your team members are already familiar with Outlook, there is no requirement for any elaborate training, further lowering the cost. As you have network and SharePoint administrators in place, you don’t require dedicated personnel for maintenance. And the bigger advantage, in long-term, is the reduced number of inbound customer support questions, which will reduce the amount of time it takes to respond to support issues. This can reduce the number of support engineers needed, thereby reducing costs to your support desk at the long run.
(This is the second part of the previously published blog ‘Overcoming the limitation of SharePoint based Issue Tracking system – Part I’. You can find the first part here)
I wonder how a support team can work together and collaborate on issues without some form of tracking and ticketing mechanism put in place in the organization. And lately, with SharePoint becoming as a preferred repository for sharing documents and enabling collaboration among staffs and workers from within or outside the organization’s network, I am seeing a trend for IT managers to make good use of the inbuilt Issue Tracking template in their SharePoint list, to meet their basic ticket recording and tracking requirements. Well, no doubt, Microsoft SharePoint is very powerful and popular. Just like a sculptor producing a piece of art-work from a raw wood, in the hand of a creative designer, SharePoint can be molded into doing anything they want it to do or, sort of. However, to be that something useful, it requires a good level of customization. And that’s where the problem and its potential pitfall lie. Because, without extensive experience and skills, there is no way one can build the logic of their helpdesk application and integrate their in-house workflows such as importing tickets from Outlook emails into SharePoint. In fact, SharePoint development is a huge business with hundreds of consultants or ‘third parties’ delivering web-parts, add-ons and other SharePoint customizations. And yes, it is certainly an expensive investment.
Well, a SharePoint based issue tracking system is useless if there is no easy way of sourcing and tracking ticket information from emails stored on your Outlook. Further, most trouble tickets cannot be resolved within a single e-mail and response. Feedback from the end-user and suggestions from other technicians or stakeholders often occur and lead to multiple request-response emails in Microsoft Outlook. Moreover, different members from the support teams may provide resolutions during the course of the request. So, in practical scenario, a trouble ticket might have various e-mail versions of the resolution steps, and the ticket should reflect the compete snapshot of these responses and resolutions. The question is, how will these emails from Outlook get updated to the ticket item in your SharePoint list? This is where our expertise and solutions comes into the picture to fill this glaring void! With our Outlook add-in (Issue Tracker for Outlook & SharePoint), you can establish and maintain a live connection between your email clients (Microsoft Outlook) to your SharePoint lists, such that, you are able to simply press a button to raise and log a trouble ticket from the selected email to your Issue Tracking SharePoint list. The generated ticket item in SharePoint will inherit metadata information from the email or sender, such as name, email address, phone number, address, problem description, attachments, and any number of custom fields, your administrator might have deployed.
You may think, just clicking a button to raise a ticket from an email to a destination SharePoint list is a big leap in the efficiency of the helpdesk. However, in a typical service desk environment, where the email is the main medium of correspondence, there is a feel of a ‘disconnect’ between the technicians and the ticket tracking system. The reason being a technician has to manually create and log in new trouble ticket from email and this can be a major drawback if there is considerable emails traffic. Moreover, during off hours, weekends or holidays, support emails will remain unattended in your mailbox, increasing the anxiety and frustration of curious callers. It can increase response time affecting the overall performance of the help desk. So, an ideal issue tracker system should provide a way to automatically log a trouble ticket from an email and assign the appropriate technician who has the relevant skill to resolve it.
This is precisely why our Issue Tracker add-in is designed to operate in automation mode based on administrator defined ticketing workflow. When certain mailboxes or mail-enabled public folders are configured for automation, Issue Tracker will intercept incoming emails and automatically raise trouble tickets to the specified SharePoint list. Contact information is automatically extracted and populated from the emails along with the problem description into the tickets. The generated tickets will also inherit the default problem category, type, status or technician defined for that mailbox/folder in the workflow. As a consequence, automated emails of assignment will also be sent out to the technician. So, no longer you need to manually monitor your mailbox for support requests. Issue Tracker does that all for you in a blink, enabling you to focus and concentrate on resolving the ticket rather than spending on the technicalities of ticketing process. This helps to improve the efficiency, and response time of your helpdesk team.
You’ll be wrong to think that the functionality of an Issue Tracker system ends with the capture and logging of trouble tickets. In fact, the real purpose of an Issue tracker system is to enable tracking of a ticket over several communication loops and responses. But when you and other technicians start working on resolving to your assigned trouble tickets stored in SharePoint lists, unless you have managed to create some specialized web parts and workflows, most likely you would be unable to respond to the caller or other stakeholder from within SharePoint, or set SharePoint to send out notification alerts to the caller or the technician on the ticket progress and escalation. So, what do you do? Open up Outlook and get back to the caller, and when caller replies back, you again update that information into the ticket in SharePoint. Well, just imagine how laborious and manual procedure it is, switching back and forth between Outlook and SharePoint! And not to mention, the risk of making erroneous entry. Our Issue Tracker add-in in Microsoft Outlook overcomes this limitation, by monitoring and tracking incoming or outgoing emails associated with a trouble ticket and accordingly updates the corresponding ticket on the fly.
Talking about the Outlook and SharePoint integration, when the time arises to edit or re-assign to another technician, or add a comment to a ticket, normally, you would do that directly from the SharePoint site. Another way of doing this is from the comfort of your Outlook itself. You can simply select or open the email from which a ticket was raised previously, and press the ‘Edit Ticket’ button and that would allow you to easily edit or update the data into the ticket or add new comment without using your web browser and searching for the particular ticket list item amongst the lot. You can add comments, hours of work done, reschedule the due date and update the status, mark it resolved, in just a single click. If the ticket had been resolved already, and if the caller contacts the helpdesk to inform about the problem resurfacing again, you will have to reopen the ticket. In such a case, you can un-check the ‘Mark As Resolved’ option and update the ticket. Doing so, it will trigger a case reopening notification alert, which Issue Tracker add-in will send out to the assigned technician.
Would not it be nice, if you were to be able to see all the tickets that were assigned to you, from Outlook, and even work and update the ticket from within? From the ‘My Tickets’ panel, the tickets assigned to you are listed in tabular form with detail information on other columns. When you select a ticket from the list, based on the state of the ticket (ongoing or resolved), the actions and tasks that can be performed on the ticket are enabled. From within your Outlook, you can quickly reply to the caller, choose a relevant KB article to embed to the reply, forward to a third person or stakeholder, edit and comment to the ticket, mark as resolved or reopen or delete the ticket and more.
If you are the manager, and are assigning the ticket to a technician, Issue Tracker will automatically send out notification alert on the ticket assignment to the technician, and insert due date appointment to the technician’s default calendar as well. Optionally, Issue Tracker will also add or update the due date information of the ticket into an administrator specified dedicated SharePoint calendar.
Your end-users may send you emails on similar issues repeatedly. It is typical of any support team to frequently find themselves trying to solve the same issue time and again. And if you are already aware of the solution, typically, you will try to compose the solution or if you have vague recollection of it, you would try to navigate to your existing document libraries, past emails etc. Just imagine how much time and effort you had wasted in trying to find the right information at the moment of need, not to mention the delayed response to the support request. You wish you could share your knowledge on a centralized information system with other team members so that everyone has the same understanding and are communicating the same message when asked about specific issues! One of the important goals of implementing an issue tracking system in an organization is to minimize the occurrence of recurring issues from their end-users. Our Issue Tracker system includes an integrated Knowledge Base system that allows your helpdesk team to document best practices and solutions to common problems, in the form of KB articles stored on a dedicated SharePoint list. A Question and Answer format is used to intuitively display KB articles. Each article may have any number of file attachments associated, rich-text elements, and hyperlinks to other web pages. All articles are tagged with a related problem category and problem type, so it is easy to find a particular resolution at time of needs.
So, the question is how can technician make use these knowledge base articles in replying to emails? Well, individual technician even need not go back and forth between the email (Outlook) and the KB articles (SharePoint). In the Issue Tracker toolbar or ribbon in Outlook, there are KB buttons, which the technician can use to choose one of this relevant KB article directly for replying to tickets or emails.
A dialog window allows the technicians to browse through the existing knowledge base articles, and select the relevant article to be embedded either as attachment, inline or as URL into the email reply.
Selected KB article can be applied or inserted into the replied email in varied format. You can choose to insert as attachment in the form of a word document (*.doc), Adobe PDF (*.pdf), Microsoft XPS (*.xps) or as single file MHTML (*.mht). You can also embed the selected KB article directly into the body of the email reply. Any inline images and formatting are preserved in its original state in the reply also. Alternatively, if your SharePoint site is opened (i.e., accessible via the web), then you can also insert the hyperlink or URL of the selected KB article into the reply, so that the recipient can simply click the hyperlink to open the relevant article in their web browser.
As these knowledge base articles reside in your SharePoint server, you can allow your end-users access to the KB website so that end-users and customers experiencing technical challenges can self-service the answer to their problem by accessing this web-based knowledge base. Once on the Knowledge Base web interface, end-users may click through the tiered problem categories and type to find articles they are looking for. They can even make use of the SharePoint inbuilt search functionality to query KB articles by keywords. A knowledge base repository acts as an effective knowledge sharing medium, boosting support productivity by leveraging collective knowledge and providing invaluable KB Articles to support technicians in a snap! It also helps in improving the average “First Call Resolution” timing significantly, as technicians find resolution to problems quickly.
Another long term expectation or goal of implementing an issue tracking system in the organization is to be able to re-engineer business processes, reinforce resources and forecast problem areas and exploit all these factors for competitive advantage. Senior managers should be able to perform information mining to seek out trends and other hidden measures such as response and resolution durations. Analyzing these mathematical values for cues are critical to devise an effective strategy for helpdesk best practices. In a nutshell, an ideal issue tracking system should aid in extracting mission critical information and intelligence that will enable better decision- in the team and organization. In our Issue Tracking system, we have implemented two kind of reporting tools – Summary Reports generator and OLAP Statistics and Reporting.
With the Summary Report tool, managers can generate summarized reports on support tickets based on different time interval. It appraises on the current happenings on the helpdesk and enables tracking the progress of tickets. It provides an overview about when tickets are logged, due, worked and resolved over a period of time. Any fields can be selected for inclusion into the reports which can then be exported to Excel, Text, XML or HTML web page or printed for sharing and easy distribution.
The OLAP tool on the other hand, provides statistics on trouble tickets from the SharePoint lists. It supports displaying multidimensional data structures in grids, charts and graphs and support most common operations such as pivoting, drill down/slice and dice, filtering etc. This gives managers a unique opportunity to analyze their helpdesk data – slice and dice performance data to seek opportunity, drill down into trouble spots to reinforce and strengthen policies. It also provides various inbuilt reports specific to Issue Tracker tickets. Helpdesk managers can also easily create and save their user-defined reports for future references. Any report, chart, grid or graph can be saved to PDF, images, web pages or printed.
Therefore, in addition to providing a mechanism to resolve customer problems, our Issue Tracker system provides senior IT managers with statistical information and understanding that aid in the decision-making process concerning the whole of help desk, and the organization as a whole.
I know, I have gone a bit lengthy on writing this particular blog, but I believe it was necessary, as we have put considerable amount of time and efforts in the development of this application (Issue Tracker for Outlook & SharePoint). The fact is, there are whole lots of other features which I have not covered in this blog, doing which would have turned this blog into a journal of some sort. Anyway, if you want to get first insights and learn more on our issue tracking system, watch out the video demonstrations.
Product Summary: Title: Issue Tracker for Outlook & SharePoint (Team Edition) Website:http://www.assistmyteam.net/IssueTrackerSP/ SharePoint: WSS 2.0, WSS 3.0, MOSS 2007, SharePoint 2010 (Foundation and Enterprise), Office 365 SharePoint Online and any other cloud based SharePoints Outlook: Outlook 2003, Outlook 2007 and Outlook 2010 (32 bit Office 2010 only).
By now, most of you might be aware of latest Microsoft’s Cloud based Office collaboration and services – Office 365. The offering consists of Office Professional Plus, Exchange Online, SharePoint Online and Lync Online.
In the last few months, Office 365 has grown tremendously and widely adopted by small and medium businesses. Add to that, many of our existing customers keep nagging me when the support for Office 365 is planned. Reluctantly, it was decided that the time has come to finally do it. But wait, there is no blueprints or easier way to achieved it. One aspect of Office 365 is the claimed-based authentication which is quite different from the usual NTLM or form authentication, that are quite common in in-housed Microsoft software environment such as SharePoint 2010. So, spent 2 days learning about the new claim-based authentication implementation in Office 365 and another day for finally coming out with a working prototype. The journey was painful, but the end it was worth it, because now, I can proudly display ‘works on Office 365‘ for our products. Moreover, I would be scanning less emails on Office 365 support from now onwards – a relief actually!
The following products are now updated to support Office 365, especially the SharePoint Online service.
The update does not add any new UI or options to go along, only the logic that drives connection to the Office 365 SharePoint Online site is piggyback into existing module. So, there is no new steps to get accustom to and you can keep on using the product the way you had been doing before. What is new is now, you can specify your Office 365 SharePoint site to interface and work with our product, by simply keying in the office 365 team site URL and you will be prompted to provide the credential to log on to the site.
For example, below, the Office 365 team site URL is http://amt100.sharepoint.com/TeamSite
And in the credential dialog prompt, you will enter your Microsoft Online Services ID, as the user name. In this context, it is john@AMT100.onmicrosoft.com and the password characters.
Note that, Microsoft Online Service ID is the same that you use when signing in to Office 365 site in your web browser.
If the credential provided is correct, it should load up all the lists and sub-sites as shown below.
Edited (30th November 2011): Please note that you need the following requirements to be able to integrate Office 365 SharePoint Online with our products:
Operating System – Vista SP2 or above. Windows XP and 2003 won’t work with Office 365 SharePoints. .NET Framework – 3.5 or above Windows Identity Foundation – This component is required to be installed on the system so that our product can work with Office 365 SharePoint lists.
You can download and install this component from below:
bahrurBlog is written by Bahrur Rahman, founder and CEO of AssistMyTeam SMB Solutions. It contains information and insights on the products offering from AssistMyTeam SMB Solutions. You can also learn more about the founder's perspectives and ideas on efficient CRM, ERP and collaborative solutions based on Microsoft Office, Exchange and SharePoint platforms, to help drive the success of Small & Medium Businesses.