Question How To Assign Task Content Type To SharePoint Designer 2010 Workflow

  • vendredi 27 avril 2012 14:57
     
     

    Hi.

    I have created a custom content type of type task.  I have then created a workflow based on the "Collect Feedback" OOTB workflow in SharePoint Designer 2010. 

    In SharePoint Designer 2010 there does not seem to be an option to use my custom content type as the Task form content type for the workflow i.e. the list where tasks will be created.  I can add fields to the "Task Form Fields" section when I "Edit Workflow" but this creates a new form in my custom task list.

    Why does it not allow use of the Task content type that I have created?

Toutes les réponses

  • mardi 1 mai 2012 03:30
     
     

    You will have to crack open the .xoml file and the wfconfig.xml file.  Here is a link to instructions, you will start on Step 5:  http://www.rightpoint.com/community/blogs/viewpoint/archive/2012/02/21/assign-a-custom-content-type-to-task-process-in-a-sharepoint-designer-2010-workflow.aspx


    Kim Frehe

    • Marqué comme réponse motionpotion mardi 1 mai 2012 10:29
    • Non marqué comme réponse motionpotion mardi 1 mai 2012 12:02
    •  
  • mardi 1 mai 2012 08:56
     
     

    Hi,

    Also make sure that your Content type is based on Workflow task content type and not just task content type.

  • mardi 1 mai 2012 10:28
     
     

    Thanks for your reply.

    Unbelievable that Microsoft makes us jump through so many hoops to do the simplest of things.

    Couldn't they just allow us to select it from the Task Form Fields section to make life easier?

  • mardi 1 mai 2012 11:27
     
     
    SC Vinod, how can I base it on a Workflow Task when "workflow task" does not exist in my parent content types?
  • mardi 1 mai 2012 12:55
     
     

    After completing the steps above my workflow starts but no task is created.  I only get the option when creating a content type to create it based on "Task".  There is no option for "Workflow Task" in my list of parent content types.

  • mardi 1 mai 2012 14:35
     
     

    You can either create a content type and declare the parent with code, or through the UI by unhiding the "Workflow Task" from your list of available options:  

    • Add the following to your site URL:  _layouts/ManageContentType.aspx?ctype=0x010801  (if you click on your home page, replace default.aspx with this text)
    • This should have the Workflow Task open
    • Under Settings select Name Group and Description
    • Change the Group from _Hidden to something else (I usually have a custom group starting with an underline so that I can find it easily)
    • Now you can select it from the list of parent options when you are creating a new content type. 

    Do this carefully, you will not be able to return this to the _Hidden group through the UI once it is changed. 


    Kim Frehe


    • Modifié Kim Frehe mardi 1 mai 2012 14:36 spelling
    •  
  • mardi 1 mai 2012 14:53
     
     

    Ok.  Just for clarity and for future readers of this post -> how can I add it back to the _Hidden group after I have created my content type based on it?

    (Note: In 2007 I could just type in _Hidden to the group field and it would add it back, is it the same for 2010?)

    • Modifié motionpotion mardi 1 mai 2012 14:56 added note for clarity
    •  
  • mardi 1 mai 2012 18:53
     
     

    Another issue seems to be that even thought it says "Fields displayed on the task completion form." in the Task Form Fields section of the workflow editor in SharePoint designer - I see all the other fields on the task edit form that are on a Task item - i.e. Assigned To; Predecessors; Due Date; etc.

    I only want to see my fields on the edit form.  

    When I set the Content Type to only show my custom fields the task is created by the workflow but immediately the task "Outcome" field is set to "Canceled", the tasks status is set to Completed and the percentage complete for the tasks is set to 100%.  I am not setting this anywhere in my workflow.  There are no emails sent to the assignees of the tasks because they are immediately created and cancelled.

    The workflow stays "In Progress" but any tasks associated with it are "Completed" although their outcome is canceled.  So the workflow is in some sort of limbo immediately after it starts on an item.