smorinjr

The "Collect Data from User" action has been causing problems... When I collect task data, the task doesnt store the values that selected.

For instance:

Step 1)

Collect Data from user task (choice menu selected with "Approved" and "Declined" as the choices)

Step 2)

Email those values to a user.

The works great for most users, but some users receive an email with " " as the value selected.

NOTE: I am correctly assigning the values to a variable named "List Item ID" and correctly referencing it in the email.

Any ideas



Re: SharePoint - Design and Customization Sharepoint Designer error with "Collect Data From User" Action

Paul Galvin

This would happen if the user didn't select one of those values. I think that SPD will allow you to configure the collect data from user part such that there is no default answer. Maybe you did that






Re: SharePoint - Design and Customization Sharepoint Designer error with "Collect Data From User" Action

smorinjr

Thank you for the response Paul,

Actually I provide three choices "Approved, Declined, and Pending" I set "Pending" as the default selection (radio buttons so there is always at least one choice).

When a user is assigned a task they will open up the task, click on "edit Item", then they will select "Approved" and then click on "Complete Task".

I then wanted to email those results to myself (my solution for the lack of debugging), so I can see what values are being selected. 9 times out of 10, I receive valid results (see fig 1) but then I receive results from the same individuals completing other tasks that look like fig 2.

I was curious that since the "Collect Data from User" action does pause the workflow, if there could be an issue "rehydrating" the workflow after the task is completed

(Source: http://blogs.3sharp.com/Blog/davidg/archive/2007/10/18/3785.aspx and http://www.microsoft.com/downloads/details.aspx displaylang=en&FamilyID=6096ce0f-d21e-47ac-afe2-d4e1c2fce670)

NOTE:

"Task Value" is equal to the value of completed task

"Column Value" is "Pending" by default and changes to value of the "Task Value"

"VAR Sup Choice" is a workflow variable set up to equal the value, as a string, of the "Task Value"

"Task ID" This is the "List Item ID"

Fig 1)

Task Value:::Approved

Column Value:::Approved

Task ID:::1120

VAR Sup Choice:::Approved

Link:::http://iss1200/adm/Out%20of%20Town%20Travel/TEST2007-10-24T14_46_57.xml

Task Assigned TO:::esc_lan\BLANK

Fig 2)

Task Value:::


Column Value::: Pending


Task ID:::1106

VAR Sup Choice:::


Link:::http://iss1200/adm/Local%20Travel%20Reimbursement/LTR-Maria%202007-10-24T09_12_23.xml


Task Assigned TO:::esc_lan\BLANK

Regards!!!

-Sam





Re: SharePoint - Design and Customization Sharepoint Designer error with "Collect Data From User" Action

halopunker

The ' ' typically mean that the value that was returned was null or it just couldn't find the item it was looking for.

My question would be does this happen when the Column Value = Pending

Because that would make sense, because the 'Task Value' would remain blank, and so Would 'VAR Sup Choice' because they are both effected by whether or not the item is completed. Since the item isn't completed in pending it would just be copying over the null value which would result in your ' '. But than again it just depends on when you actually do the copying from Task Value to Column Value.





Re: SharePoint - Design and Customization Sharepoint Designer error with "Collect Data From User" Action

smorinjr

The "Column Value" is set to Pending by default. After a task a completed, the value of that task is then copied to the "Column Value.

Sample,

Step 1) Assign Task with (Pending, Approved and Declined) as choices. (Pending is set by default)

Step 2) Complete the Task by choosing one of the choices above.

Step 3) Read the "Task Value"

Step 4) Copy the "Task Value" to a workflow Variable called "VAR Sup Choice" as string

Step 5) Copy the "Task Value" to the "Column Value"

Step 6) Email myself the values of "Task Value", "VAR Sup Choice", and "Column Value" to verify that they are properly being assigned.


This works 70% - 90% of the time. When it doesn't work, I receive the values " " for "Task Value" and obviously the "VAR Sup Choice" since it copies the value of "Task Choice"

This workflow, by the way, is used as an approval for a travel requisitions of a staff of over 250 people. The tasks are assigned to various individuals, and these results seem to happen at random.

Thanks!!





Re: SharePoint - Design and Customization Sharepoint Designer error with "Collect Data From User" Action

halopunker

Two Questions:

-When it fails 10-30% of the time, is the task actually completed in the list Check the workflow history to make sure there isn't any errors. I say this because you stated that it is suppose to email you after the user has submitted a form (Approve/Declined)

If the Column Value is pending by default and changes to value of the task value, then the Column Value should read: as well, not Pending.

-Also when you get the in your email, does it always say pending in the Column Value Are the fields that the user is filling in required

The state that it can't find a value for the item. Otherwise it would return at least something (if it returns multiple values snags the first one), double check your Workflow Lookup Field, to make sure they are looking up the exact item you want (the item created in task rather than current)





Re: SharePoint - Design and Customization Sharepoint Designer error with "Collect Data From User" Action

smorinjr

Actually you are right, the email I receive gives me the default value of the column task as "Pending" but when I go to view the "Column Value" inside of my forms library, the value change from "Pending" to "NULL" or blank.

This anomally is what made me believe that there is a timing issue with the workflow in which the email is fired to me before a "Task Value" is received. Because of this, I also created a "Pause for Duration of 1 minute" to see if this could "sync" the receiving of the task value with the initiation of the next workflow step, but I still receive the same null values for the "Task Value" even with this pause.

In the emails I receive, the value for "Column Value" is always "Pending" when the "Task Value" is " " (See timing hypothesis above"

The "Pending, Approved, and Declined" choices are set up as radio buttons with "Pending" set up as default and is a required field. I also disabled the "allow blank/fill in values"

The workflow lookup is correct: (at least 80% of the time...)

Action from Step 1)

collect Supervisor Choice from domain\user (Output to Supervisor Choice - List Item ID)

Action from Step 2 to retrieve Workflow Lookup

set Column Value to TASK VALUE*

*Lookup Details: Source: TASKS ; Field: Supervisor Choice

Find the List Item: Field: TASK ID; Value: WorkflowDataTongue Tiedupervisor Choice - List Item ID

Similar to this: http://office.microsoft.com/en-us/sharepointdesigner/HA102098081033.aspx

THANKS!!!





Re: SharePoint - Design and Customization Sharepoint Designer error with "Collect Data From User" Action

halopunker

Hmmm, I have no Idea then.

Try using a Drop Down List rather than radio buttons.

Try storing the 'Task Value' in a variable and then setting the Column Value to the Variable.

SPD seems a bit touchy sometimes with Sharepoint and not everything works correctly. I ran into that issue when I thought I had the latest version but I didn't. I was so thrilled things were working a bit more smoother. But regardless, I hope someone else will come along and help ya ^.^





Re: SharePoint - Design and Customization Sharepoint Designer error with "Collect Data From User" Action

smorinjr

Well here is the answer:

After speaking with the boys in Redmond. They told me that the issue I have is related to the owstimer.exe not restarting, (or rehydrating as they call it) after a user has completed their task. Furthermore, the Redmond guys, told me that they didn't know if and when they would EVER fix this issue because it also affects workflows with the "Delay Until Date" function.

In addition to that, I was told that if workflows create more than 2000 tasks in the task list (in my case its 4 tasks per travel request form submitted, or max of 500 travel forms submitted), that THIS will cause workflows to be ignored all together.

Very disapointing.