I'm looking to create a workflow app on Sharepoint. Basically at the top level there's a list of projects. When you click on a project, a list of states is displayed (dev/qa/staging/prod) etc...when a developer finishes their task, they will change the state to QA, and the QA team needs to get a notification.
Is this possible to accomplish in Sharepoint 2007 without any custom webparts? If not, what's the best way to approach this?
Thanks.
SharePoint 2007 supports creation of workflows out of the box MOSS 2007 adds more features on top of basic functionality provided and 2010 versions provide more inprovments.
Check out http://msdn.microsoft.com/en-us/library/bb386168(v=VS.90).aspx or http://msdn.microsoft.com/en-us/library/bb386211.aspx to get statred.
Search for "SharePoint workflow" on your favorite search engine for more information.
I was able to do what I wanted to do using SharePoint Designer which is a free download.
Related
I just saw in a video about sharepoint (https://www.youtube.com/watch?v=jhVWtlItL6k Minute 6:50) that in sharepoint there is a Check In Button. Now my question is is this also possible with ItHit WebDav too? Or is this a button from the Sharepoint Plugin and can only be rebuild with an own plugin?
The Video is from Office 2013, I have Office 2016 maybe thats why the Button is not there.
Otherwise the CheckIn can also be done by closing and saving. But preferably I would like to have an option to Make a Checkin and Signal my Application it should make the Safe a New Version (Optionally with a description input).
Also I saw there is the property AllowOffice12Versioning (which said here was experimental:
Show Versions within the document (IT Hit WebDav) )
The Versioning Support for DeltaV cannot be reused for word right?
https://www.webdavsystem.com/server/documentation/creating_deltav/
Is there any progress on it since 2014 or how is this acutally realized in Office? Does it use any of the WebDav Extenions by Microsoft which I could extend myself if no progres yet? (MS-WDVSE, MS-WDVME, MS-WDV, MS_WDVME...)
Unfortunately, unlike other operations, versioning in MS Office is not using WebDAV, as this post describes: Show Versions within the document (IT Hit WebDav). MS Office is using its own proprietary protocol to display versions.
One possible solution is implementing check-in/check-out commands and versions list in the IT Hit WebDAVDrive sample based on IT Hit Virtual File System product. This sample works similar to OneDrive (it using the same Windows API) and can automatically lock/unlock documents on the virtual drive, which is very close to check-out/check-in. You potentially can add check-out/check-in/list versions commands to the Windows File Manager context menu as well as attach a hook to file open/close or lock/unlock events in sample code to show a custom user interface.
I see lot of solution c# for Sharepoint but i have sharepoint online 2013 with microsoft server.
How can i install solution to my sharepoint online ?
For example: https://code.msdn.microsoft.com/Convert-from-HTML-to-PDF-09ce2a1d#content
Normally I use jquery for Sharepoint but i need convert Htlm to pdf and save this to Document Library.
For Information : I use visual studio to develop xamarin applcation and plumsail forms designer to develop sharepoint forms.
Can you help me ?
Thanks.
please explain what kind of Solution it is. You cant install a custom Solution with server side code in sharepoint Online.
You might use a Sharepoint Add in. If you need Server side code you can develop a provider hosted app instead.
Ok, so what you need is a Sharepoint Add In.
You are in the good road looking at some JavaScript solution. Keep looking for a suitable one.
I would like to use Excel functionality from a browser. I currently have an excel based Microsoft office application. It adds an icon to the ribbon and does C# based custom application logic to communicate to a database server.
Since it requires application releases for any changes in the schema I am curious if I can convert this into an web application and still benefit from Excel's built in functionality.
I am expecting this to be possible since Microsoft Excel Online is run inside a browser. My question is, is it possible to add plugin to such online excel document? If yes, any example would be much appreciated.
You absolutely can, and depending on approach you can do so with nothing more than a VSTO project template. This is little more than a ClickOnce application. This can launch a browser within a window to perform the logic.
You may use the Office Interop assemblies to decouple your application from Office apps, yet still communicate easily. Make sure you set Embed Interop Assemblies to true once added as a reference.
For those using Office in the browser, it seems as though Microsoft is shifting into CSOM/JSON/REST, meaning this solution is coded entirely differently than COM. This should help you get started:
https://msdn.microsoft.com/EN-US/library/office/dn268594.aspx.
What are my options for editing Word documents? We have a hosted business web application (written in C# using javascript libraries and webapi2) and our users would like some basic document management functionality. From within our application they would like to complete documentation which currently resides as Word 2013 documents.
Is there something that would allow us to upload a docx file, convert to some web friendly XML format that would allow online editing or can Office Web Apps be used directly within the browser for Word edits if the client has a valid Word license? Is SharePoint online integration an option? Or, is there an option out there that I am not aware of? Any direction would be greatly appreciated!
To complete your task, you can use the DevExpress ASPxRichEdit and ASPxSpreadSheet controls. They support the most popular rich text and spreadsheet formats (including MS Office documents).
Both controls are web-based (ActiveX isn't required), standalone (you don't need to integrate external services in your application) and work in all modern browsers. Also, they have the built-in filemanager, so you can use them with minimum coding.
Moreover, both controls are distributed as a part of the ASP.NET controls suite, which includes a lot of other web components.
If you're client have the correct licenses and that you already have a solution develop that have the basic document management features like upload documents, download, etc. Then I would opt for the Office Web Apps. This solution requires some reading and a certain architecture (it's own server for instance). But it is probably one of the best Word Document editor currently out there. You can find the basic information of the Office Web App server 2013 here
These approach will let you either use a sharepoint integration or a custom WOPI-Host. I've analysed and searched for different tools and other the Google Docs, this would be the best option currently out there.
If you actually take the Office Web App server approach with a custom WOPI-Host you can find several WOPI-Host samples on the internet:
MVC6 WopiHost based on marx-yu's WOPI host
Building an Office Web Apps (OWA) WOPI Host
As I know, Google Docs can help you on your issues, but you just cannot build it in your web Apps. And aceoffix can be an alternative too, which can enable your web project edit Ms Office documents full functionally.
I am in the estimating phase of a project, and one requirement is that my application will create draft emails (with attachments) in MS-Outlook, which the user can then review and send. The app is written in WPF.
The clients will have either Outlook 2003 or Outlook 2007. The files that need to be attached will already exist on the file system when the drafts are generated.
I have done some initial research, but would like to get some opinions from people who have first-hand experience.
Questions:
What tool would you use to
accomplish this?
Will there need to be separate code for Outlook 2003 vs. 2007?
In general, using whatever tools are recommended, is this a relatively straightforward problem to solve?
Thanks for any insight.
a c# wpf application should be able to do the job just fine, you just need to add the outlook libraries in your references and you can work with outlook directly from your WPF app.
I only write for 2003, but I do know that 2003 and 2007 use different libraries. There's probably a clever way check what version of outlook is being and use the methods from the correct library, but it will take some work to figure out.
It's relatively straight forward except for the security prompt you'll get if you send the email. But I suppose if they are going to have them review it first, you should be able to generate the email, open it in an outlook window for them to review, and have them click the send button.
Would you be able to use WebDAV and then simply create the message and drop it in the users' Drafts folder?
Basically, you'll end up using something like this product (or you can roll your own) to create and save the message. You might be able to find an open source solution.
I think there are a couple tools you could use here:
Visual Studio Tools for Office (VSTO)
total control over Outlook
version of Outlook may matter
Assuming you have Exchange, you could use WebDAV, Exchange's XML methodology
version of Outlook wouldn't matter here
Use the built in mailto: functionality
lots of results for using this to include attachments - Google Results
would work for email apps other than Outlook
this probably would be quickest solution, but the least control over the output
An Outlook Add-in is probably a good way to go for this application. The tool set you need is Visual Studio Tools for Office (VSTO). With the possible exception of the WPF requirement, this is pretty straightforward.
Be aware that the API's and the VSTO tools evolved between 2003 and 2007. You can potentially have a single code base but you will need to write for the least common denominator, 2003.
2003 and 2007 also have different Primary Interop Assemblies, the components that bridge the gap between your .NET code and the native code COM interfaces that Outlook has. This can be a challenge when it comes to building and installer for your add-in. If you want your add-in to install the PIA's, you need to detect the version of Office and install the appropriate version, or, more commonly, just build two different installers.
I've never tried to do WPF inside Outlook 2003. There may be some issues with it but I don't know.