I'm working on a Sharepoint 2010 project that uses a basic approval workflow. The issue I am facing now is that when I update an item in a list and set it to approved, the changes are not reflected on the website.
The only way I found is to recycle the app pool.... but since content update activities will be managed by a non-dev team, I would rather have another solution.
Any suggestion?
Related
I'm creating a sharepoint hosted app, two pages, default.aspx and admin.aspx.
When I update the list in the appweb thru a function in default.aspx, I want that a notify windows will popup to the client that are watching the admin.aspx page, that a new items is added to the list.
Is that possible in sharepoint 2013?
It is not exactly the same, but I think "AJAX automatic refresh can help". See this article: http://www.rdacorp.com/2010/01/sharepoint-2010-auto-refresh-web-parts-with-ajax-options/
I have a solution in VS2012 with a SharePoint 2013 sandboxed project. I have created some custom workflows in 2013.
What I really need to do is to have an approval workflow to publish content, and send out an email when a new document is approved.
My first thought was to use the OOB approval 2010 workflow and use an event receiver on the list. When an item becomes approved, I would send out an email, but I'm unable to send emails programmatically in SharePoint online.
My second thought was to recreate the workflow in 2013, since I know I can send emails out that way, but it looks like the activities related to content approval were removed for 2013 workflows. I can try and do the approvals via rest calls, but my concern was that my workflow will fire every time the item in the list changes (even if it's not a publish), so I will have to check (in the workflow) if the item is being published or not. This will cause the workflow history for the items to become pretty useless as it will be filled with mostly white noise. Also, as far as I can tell, the checkbox when you create an association for "Start this workflow to approve publishing a major version of an item." does not apply to 2013 workflows.
I believe my best answer at this time would be to create a custom 2010 workflow, but I don't see how I can do that from inside VS2012. Can anyone help me (or maybe suggestion another alternative to achieving my goal?)
You can just turn on the old (2007) approval workflows. It sounds like those might work for you.
This article references how to do that, but in short it is under
Site Settings -> Site Collection Administration -> Site Collection Features -> enable the feature 'SharePoint 2007 Workflows'
Configuring SharePoint 2013 to use legacy workflows
I ended up using an OOB 2010 Workflow and modifying it with SharePoint Designer. Not really the solution I wanted (which was to package ALL of my customizations into a single WSP), but I've spent more time than I should have trying to get it to work.
We use TFS integrated with Sharepoint for storing artefacts. Examples: end user documentation.
The artifacts are uploaded using Visual studio 2010 and not from web interface.
For each artefact preparation, there will be a task created in TFS.
Example:
Documentation preparation
The requirement is whenever a document is uploaded or modified in the sharepoint folder, can the user be alerted?
Example:
which TFS task he/she needs to update the completed hours
FOlder structure:
similar to the one shown in the 2nd answer to the below question
Share project documents in TFS different ways, what are your best practices?
It's not there by default, but one could build it oneself using a ListItemEventHandler (http://msdn.microsoft.com/en-us/library/ms437502.aspx) in sharepoint or a custom aproval workflow that activates from within sharepoint and creates workitems in TFS using the object model (http://msdn.microsoft.com/en-us/library/bb130322.aspx).
The requirement is whenever a document is uploaded or modified in the
sharepoint folder, can the user be alerted?
A simpler way to achieve only this requirement might be to put an sharepoint alert on the document list so one would recieve an e-mail when an item is created.
The SharePoint install is a SP2010 install on a 2008 R2 server. Everything is fully patched. I am running the SP Designer on the SharePoint Server directly.
I have a workflow which is intended to send an email when a new document is created in a custom list. I have deliberately kept the workflow very simple in order to illustrate this problem.
After creating this single step workflow in SP Designer, I click "Check for Errors" and SP Designer reports "The workflow contains no errors".
I then click "Publish" but the Workflow Error dialog is displayed with the message
Errors were found when compiling the workflow. The workflow files
were saved but cannot be run.
Clicking the advanced button reveals more information:
Could not publish the workflow because the workflow configuration file
contains errors
Any suggestions gratefully received
I'll share what fixed it for me - deactivating all workflow features at the site collection level (that is, Workflows, Three-state workflow, Publishing Approval Workflow) and then reactivating the features. I was then able to publish my workflow. This post helped, not sure whether this only works for 365 though, but it's sure worth trying first if you are considering a reinstall.
after googling for quite some time, i think it's an authentication issue. How is your SharePoint set up? Do you use HTTPS for authentication? If so check out this article.
I know this error message from sharepoint. I got this by dealing with multiple lookup fields refering to other lists. Even when I check the worfklow for errors SharePoint says that its all fine but i can't publish it at all.
Try to build a new Test-Site on your Site Collection. Build a Custom Document Library, leave it standard and then set up a new simple workflow just sending a mail.
Fill out the needed fields in mail only using simple values. Send to your mailadress, simple mail subject and simple mail body.
Set the workflow to run only manually.
Try to publish the workflow.
When this is working, then compair to your existing workflow and change your values by trail and error.
After doing a clean install of the OS and SharePoint, workflows are working flawlessly. I can only conclude that the problems were caused by left over registry settings from MOSS 2007. Thanks for the suggestions that people made.
This could also happens if you chage the URL of the web application, all you have do is click the Design button from the library itself.
when changinf the URL from http://server/Site to example: http://server.xx1.net/site, and you try to publish it tries the old url.
what helped in my situation is changing from start workflow automatically to manually.some times answers for critical situation is very easy. hope it helps, many thanks
I ran into this problem and after digging for days and folks suggesting to rebuild the servers, disabling and re-enabling site features, remove previous workflow versions, etc. and trying everything except rebuilding the servers (not practical for clients production environment). I decided to try some tests and found that this issue was only happening on one particular list no matter how simple or complex the workflow was... And when I would check the box for start automatically on item create (or when item changed) it would fail to publish and give the error above, but if I published it with just manually start worked fine. Finally after deleting views and some more testing, I discovered that there was over 240+ columns in this list (I did not create it...) and 50+ workflows set to run on create... Thankfully I have a test environment I built out for the client so I sync'd the Site Collection database back to test environment from Production re-ran my tests and got same error... So what resolved the problem and what was the ultimate cause of the problem, there was to many columns defined in the list and I had to delete several columns to publish the workflow in the test environment. This actually issue translates into the there is a limit in SQL Server on how much data the list can store each type of column takes up so much space read more about it here:
https://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#Column
So what I did in production was worked with my client to determine how to break up the list into multiple lists and have relationships between them, thus moving some of the columns and data to another list (Think database/list normalization)... I hope this solution helps someone.
Im designing a workflow in Sharepoint 2010 to run whenever users create itens or update itens... my question is how can i know if the item the fired the workflow was created or updated?
Test if (Created == Modified)
If it is true then it should be created, otherwise it is modified.
That is, as long as you are not doing anything fancy with SystemUpdates or timestamps etc.