I am creating a very simple workflow on a (MOSS) document library list. The workflow creates a simple to-do task for me whenever a new document is added to the underlying library list. Periodically, I run a little program from my client that uses Sharepoint Web Services to query the WORKFLOW TASK LIST, looking for new tasks. When it finds a new task, it processes the underlying library list item, then posts some error messages to the workflow task item, and marks the workflow task item "Complete". But the original workflow doesn't seem to detect that action unless I use Sharepoint to "Complete" the task manually. What do I need to do to "complete" the workflow task using Sharepoint Web Services? I assumed if I marked the task item Complete, it would react accordingly.
I am limited to Sharepoint Web Services ONLY. I'm not allowed to create my own web parts.
The task list and the workflow are not really connected. As you have discovered changing the task list item has no effect on the workflow itself. You need to access the workflow associated with the original item and mark it as complete, this will trigger actions within the workflow that will update the task and other associated lists appropriately.
Do I mark the workflow complete, or the task? If I'm reading the docs (what there is of them...) correctly, I can (though I haven't tried yet...) link from the item to its active workflow(s), then to the Workflows' active workflow ToDos.
So my strategy should change, I think. I need to start at the library list member, filter for members with active workflows, then link over to the active ToDos (Tasks) for that workflow, and act on it, marking the (Task/Workflow) as "Completed?", so the workflow can "resume"....
A web part is on SharePoint That has a link to an ASPX page that opens in a new window.
If I login as System , it shows the page (I mean the popup window) but one I login as a user
it gives me Access Denied error.
Doesn't a popup become a part of the web part?
Or is there a way to inherit the permissions?
_____________________________________________________ Yea! I could be wrong...
I have a document library where my clients upload xlsx workbooks for import into an Access app. I developed a workflow that creates a task (assigned to me). I have a C# program, using Sharepoint Web Services (VS2005, MOSS 2007) that runs periodically, spots a new task, and imports the workbook. It then updates the TASK, setting its status to "Processed" or "Processed With Errors", along with a string containing any error messages.
Now, I want some device (workflow?) to see that the task has been set to "Processed" or "Processed With Errors" and notify the original document author that the workbook has been processed, and identify any errors. I can't seem to make that part work. What's the strategy here? I am particularly concerned that someone be notified if the task hasn't been "Processed" within a couple days, indicating something else is wrong....
I don't see the need for the C# app. You can create an event receiver for the task list that handles the processing when a new item is added, no need for the periodic polling. This same process can send an email to the document owner informing them of the status. For that matter the event receiver could be placed on the document library with no need for the task list unless you need it for logging or other types of reporting.
I neglected to tell you my client will not allow me to write Sharepoint code at all. I can't attach an event receiver. I am only allowed to use Sharepoint Web Services, and Sharepoint Designer. I'm not allowed to create web parts, etc.
LOL.... Who can bill that much? I've figured out I can send an email from the C# app, so I'll just skip the task entirely, and handle it all from the app. It's only 50 lines of code (probably would be 10 if I had ever written C# before... )
I am trying to write a custom web service that is in its own web application that also has its own application pool. When trying to open the site collection using SPSite site = new SPSite("https://www.abc.com"), I get the following error message: (System.IO.FileNotFoundException = The Web application at https://www.abc.com could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.). Now if I change the application pool to the SharePoint application pool everything works just great. There is a different identity on my new application pool, but I have verified that this identity has access to the site collection. Also, I am running the code within an SPSecurity.RunWithElevatedPrivileges block.
using (var site = new SPSite("https://www.abc.com"))
using (var web = site.OpenWeb("/Test"))
Does anyone have any suggestions? If this is not possible could you point me to an msdn article that states it is not possible?
This question is regarding the best practice to be followed while developing web parts. In developing web parts, the CreateChildControls method can be programmed in 2 ways,
Create all the required controls inside this method, set their properties and call 'this.Controls.Add(xxxx)' for each control created.
Create the controls to be rendered in web part as a web user control i.e., .ascx file and deploy this control in the 12 hive's Control Templates folder. In the 'CreateChildControl' method, load this web user control and call 'this.Controls.Add(xxxx)'.
When developing a web part with complex controls or rather huge number of controls in it, which one of the above is best in terms of performance and why?
Neither is better or worse in terms of performance. Performance is more related to how it was the coded and how it functions. In SharePoint 2010 a visual webpart, an ascx, can't be deployed as a sandboxed solution (there are ways, but ignore them for this discussion) so you would be limited to the CreateChild method.
I don't know wether it has an impact on performance, but I've read in several best practice documents, that whenever possible the CreateChildControl should only be used for the final polish.
Unlike ASP.NET Web controls, they are defined and rendered with templates.
Coded webparts and visual webparts are two separate animals. The point of a visual webpart is to not needing to use the CreateChildControls method yourself, it is handled in the background. You can't give a visual webpart a final polish and switch to using this method. You may as well have started there in the first place.
This is the first time I'm doing a deployment of a web part so please excuse me in case I'm making a silly mistake. My solution has about 3-4 webparts that I developed over the Win7 environment and now I need to deploy these to the remote server for testing which is Win Server 2008 R2. I made the wsp file which I moved over to the remote server, then I used the powerShell command Add-SPSolution and Install-SPSolution with -webapplication and -GacDeployment switches. The trouble is that the wsp gets installed, that I know because when I do stsadm -o -enumsolutions, it shows an XML output showing that wsp and its status as "Deployed". But when I open up the SharePoint administration website, go to a page, edit, add a webpart then it does not show the web part in the list of web parts.