Sharepoint Workflow Strategy
-
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 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 know the language. I've read a book. - _Madmatt
-
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 know the language. I've read a book. - _Madmatt
Mark, 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.
-
Mark, 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.
To do this properly you will need, at the very least, to write a custom workflow action. Then tell your client to jump off. Or charge them a fee equal to their ridiculousness + 10%.
I know the language. I've read a book. - _Madmatt
-
To do this properly you will need, at the very least, to write a custom workflow action. Then tell your client to jump off. Or charge them a fee equal to their ridiculousness + 10%.
I know the language. I've read a book. - _Madmatt
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... ;P ) Thanks.