Exchange Server 2013
Posted on 2013-09-04
I have been doing some reading up on Exchange 2013 and am considering migrating from Exch 2010, but as most of you know there is always question of cost and justifying it to management.
Our company is rapidly growing and email plays a vital role in the way we do business. With that being said our company developed a piece of software that runs in conjunction with Outlook. The application was called a Mail Register and what it does is exactly that, registers any incoming and out going email. Basically when a new mail is received from a client relating to a certain project the mail is manually captured onto our Mail Register, it is giving an incoming number and a copy of that mail is then saved on another location. Any user can then go and access that mail from the Mail Register Client installed on their workstations, in a nut shell it is a "Document Management System" for emails.
The problem we have is that this application is only available locally to users, so users in our remote offices or mobile users are unable to make use of this app nor are they able to access the information stored in it.
Now I have seen that Exch 2013 supports "apps" which is available for use via OWA and it is said that you are able to code your own "apps" if you so wish to do so.
How possible would it be to write an "app" that works exactly the same as our Mail Register? I suppose that question is extremely broad. How customisable are the applications that you are able to code in Exchange 2013, are you limited in what you can achieve or is the world your oyster.. in a sense.