I developed an Microsoft Office Add-in for Outlook which forwards e-mails including some specific user-managed content. The add-in is hosted as a static website on GCP according to this Microsoft documentation. Everything works fine, but I need to know where data is transferred to and how I can prove it.
I need to prove that the Add-in only reads (GET) from GCP (the HTML, CSS & JavaScript files) and storages them locally (temporarily). This should be the case, because when I load the Add-in and then take down the GCP server, the Add-in including all functionalities still works for +/- 15 minutes.
How can I best prove that my Add-in reads the static files from GCP and stores them locally? I cannot find any Microsoft documentation on this.
Your add-in acts like a web site which is loaded locally and cached temporarily depending om the MIME header property values.
The Office cache folder is described in the Clear the Office cache article. Don't forget about the browser cache folder.
Related
I am new in Office 365 Add-ins. I want to know about caching. I am working on a Add-In using Office.js. I want to manage caching.
Scienario:
1- Add-In will get data from server once in a day. Data can be in MBs(i.e 5 MB).
2- It should store somewhere. So, user can use it even there is no internet connection.
Is there any internal caching mechanism provide by Office APIs?
I was also thinking to store in File. Is it possible to create and manage File using Office Add-ins in Windows and Mac?(I am just curious about File permission in Mac)
Please suggest
You need to read through the following resource: Persisting add-in state and settings. Depend on the Office application you are writing your add-in for you would need to use different objects or approaches (for example use HTML5 web storage, etc.)
I need to use a shared drive with SharePoint 2007 instead of document library/list, mainly due to space limitations.
My organization uses MOSS 2007. The Business Data Catalog can use a database or a web service as data source. So it appears I may not be able to use this feature to connect to the shared drive. Can I develop custom code in .NET and use it to integrate the shared drive with SharePoint site? If so, can you guide me to a relevant resource that can help me develop such functionality?
The functionalities I require are :
ability to upload/download files from the shared drive from the SharePoint site.
ability to detect when new files are created on the drive, or when existing ones are modified, and send relevant alerts.
workflows that can interact with the shared drive, just like they interact with a SharePoint list
I'm not exactly sure why you are using SharePoint for this because from my understanding you can simple create a web or windows application and link it to your shared drive. IF you still want to use SharePoint please see below.
from the top of my head this is the following approach than I can suggest for your requirements:
Create A Published folder and inside that create an unpublished folder.
Create a scheduled task calling a FileWatcher application which monitors the unpublished folder.
The FileWatcher application will move the files inside the unpublished folder to the published folder and use the SharePoint web services particularly the List service to update a specific list in the SharePoint and point it to the path from the Shared Drive.
You can use SharePoint workflows to check whether an item was modified to send proper notifications. This can be done via SharePoint designer and do not consume much space. This is more advisable instead of creating your own notification application.
We are going to develop a client-server application with web interface which will store office documents on server.
When we use browser as a client we need to perform these three steps to edit a document:
download document to the local machine;
open it in office program and edit;
upload document to the server.
It is very inconvenient. Sometimes it is hard to find where a document was downloaded to, when we need to upload it. Customers will also forget to upload document after editing.
Is there any way or technology to upload document automatically?
Or just any ideas how to make this process more convenient.
Thanks in advance!
I would, suggest, if applicable to store all documents as HTML then allowing editing in a web page powered by CKEditor or a similar tool.
If your documents must be in another format, like Office formats, you might start thinking at Office 365, or use ActiveX controls in your web application, something I believe should be deprecated but works in small (better restricted) enterprise environments.
These are just a couple of ideas.
At our company we offer a CRM platform for leasing companies and it includes task management. Some of our clients would like to sync those tasks with outlook so they do not have to switch between applications.
I do not have lots of experience with outlook, so I don't know about its extensibility features.
What options do we have?
Live syncing possible with some uri? (.ics, .xml?)
Writing some kind of extension?
What do you guys suggest is the most simple solution to this problem. Remember it's just syncing simple tasks, nothing more, nothing less.
Thanks!
I guess this depends on how your CRM system works. At my company we develop a webbased CRM system which means that the client can't really access the database outside of the web application. Our customers also wanted the ability to sync appointments with our activity calendar, so what I did was to write a simple web service from which data could be downloaded to the client. I then created an Outlook add-in using VSTO (Visual Studio Tools for Office) that took this data and created/updated Outlook appointments.
But as I said it all depends on how your system works.
We've developed a custom Outlook 2003 form based on ipmNote. I need a way to push this to all the other users in the organization. At the same time we'll also be installing a custom Add-in built with VSTO so we could do the form install as part of that.
Currently I can't use the Organizational Forms Library, because the exchange admins don't want to turn on public folders.
Why do you need it to appear in the user's Personal Form Library? If it's being published to everyone in the company, you would normally publish it to the Organisational Forms Library on the Exchange Server.
When your users opened the form for the first time, it would be pulled down to their local machine and stored in an application folder within their Documents and Settings.
Have a look at http://www.outlookcode.com/article.aspx?id=34 for some helpful information