For the last week now, Michael and I have been struggling with a very persistent workflow issue. An approval workflow that we have created, works fine when it’s started by an administrator, however when it started by a regular user, then the approval process won’t work. The workflow is activated with the permissions’ of the user that started it, not the permissions of the approver or the author. It isn’t currently an issue for the work we’re doing, but it will need to be fixed for use in a real world environment. Googling the problem didn’t seem to help, there were too many vague “fixes”, that required complicated multiple workflows that never seemed to work. There didn’t seam to be a solution to this problem anywhere on the internet. However, I then remembered that someone gave me a large SharePoint 2010 book as a “congratulations for getting the job”, so I decided to see if I could find a solution in there. The solution showed itself almost immediately.
The answer is: High-Privilege Workflows. I found this solution to be extremely easy carry out, and it solved our workflow problems 100%. A high-privilege workflow runs with the permissions’ of the person who created the workflow. While editing the workflow, you simply click in the area just below the first step, go to the “insert” section of the ribbon bar and click “Impersonation Step”. This adds a new step into the workflow that carries out the actions within it using the permissions of the workflow author.
I find it embarrassing that the solution was so simple, however I thought I might write a post about it, incase any others users were coming across the same issues.
I think i might have found the solution to the SharePoint issue
After asking around the office, I have discovered that SharePoint 2003 MAY be running service pack 2, if this is the case then the solution may be simply to upgrade to Service Pack 3 and install any hotfix’s that are available. It appeared that a handful of people have had a similar issues (not exactly the same but similar) and their issues have been fixed by upgrading.
It is clear from issues such as this that we NEED to upgrade to either SharePoint 2010/Online, it is a much easier platform to use and manipulate.
After some research around the SharePoint 2003 issue, I have come to believe that the problem with the RTE error is not the browser but the operating system. I know this might sound strange as it should not affect the operation of SharePoint on the browser. If this is the case, I have seen a number of fixes for this on the internet, they mostly involve a hack. I will test this theory more when I get to work tomorrow (I have been researching from home today)
I was wrong
Michael and I have been presented with a challenge involving SharePoint 2003, to attempt to resolve a very strange compatibility issue. A content editor is used to input text and images into a SharePoint site, it uses a Rich Text editor to format the text, for some reason the Rich Text Editor (RTE) will work perfectly fine using Internet Explorer 7, however it will not work in any newer versions of Internet Explorer or any other web browser. This is a very odd Error as it is assumed that Microsoft would try keep it compatible with future updates.
Along with the Microsoft SharePoint research, over the next few weeks we will be looking into this issue and will attempt to resolve it.
As you may have seen in some of our posts, we have been receiving and pretty consistent and pretty annoying error for the last month and a half . Microsoft have been on the case for the last 3 weeks and I finally got an email last night, the email gave me very simple instructions to a very simple problem, it took an entire 10 seconds to fix the site. The problem with the site was that the default master page was not set to v4 (something I may have accidentally done when fiddling with it) and all I had to do was right click and “set default”, I’m a little annoyed it has taken a month and a half for Microsoft to give me this solution, however, I am relieved that the site is now fully functional again.