SharePoint Custom Task Forms

I have searched this all over and having an issue creating the solution. No solution addresses the issues below. Only shows how to create a custom content type.

Requirement:
1. Create a custom task list
2. Add custom fields
3. Carry ALL fields through the whole process. (ie. New Task, View Task, Edit Task) - All fields to show data
4. Selecting "View" task that has been assigned from email (Shows a form with ALL data from "New", not just a task with Start and Due dates with Approve / Reject) Don't want an additional link in the email that says "See Linked List Item".  I want the item data to show in the task.   This only makes sense.  Why would I want to select a separate list item to view the information I am trying to Approve / Reject?  If I'm going to Approve or Reject the Task, I want to see what I am Approving on the same form.
- I have created custom content type and it does create the Form in Edit and View that I need based on the Content Type, but no data follows it.  The Edit and View form sent to the email as a link sends them to a form with all the correct fields but no data.
LVL 1
Christopher GoreSolutions ArchitectAsked:
Who is Participating?
 
Keyboard CowboyConnect With a Mentor Commented:
Terrific -   Check out spEasyForms - a free download you can apply at the site level  - it allows very flexible customization of new/edit/display forms (which can be based on membership in SP perm groups or field values).  I use it heavily on selectively hiding  / displaying lists.  I used to use JS but spEasyForms has reducing my development time significantly.   It's a mature product  - couldn't live without it now.  
Glad you got a solution cheers
1
 
Keyboard CowboyCommented:
I can't quite understand what behavior you're seeing and exactly what you want.  You could write  a simple workflow perhaps to show exactly what you want in the email but I can't understand what exactly you want to accomplish.
0
 
Christopher GoreSolutions ArchitectAuthor Commented:
If I create a task in SharePoint, it will notify the person who is assigned with a task.  The user selects a link to view the task.  It takes them to a task page with about 5 fields, (Title, Due Date, Start Date, Description, ..). Also in the email is a link to the actual requested list item for the task.  this list item may have 30 fields.  If I am the person assigned a task and I open the link to the task, I don't know what I am approving without going to a totally separate list to see the request information.

I want to receive the task in my email with a link that shows me the entire request information in addition to approve / reject... That way I do not have to go to two separate areas to know the details about the task.  

I have been able to add the fields as a new content type but when I view the task from the link in the email, I get the task form as expected with all the fields, but no data.  So the information from the list requesting the task, does not pass the data to the task.  I know this is by design, but is it possible to combine the two.  Or perhaps just build a workflow for the list without a task is the only way.
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
Keyboard CowboyCommented:
I don't depend on the assignment automatic email as it's not very flexible and also it's not turned on automatically normally at the system level (it is for issues for not for tasks on SP 2013).  I would write a workflow and you can transmit all of the fields in the email or provide a link which brings up everything in the task.  Actually, I've found it more reliable to create a task list as a custom list and do all my work in a custom list with supporting workflow (s).  (normally I put everything in a single workflow - that is usually the best practice).
0
 
Christopher GoreSolutions ArchitectAuthor Commented:
I actually ended up creating a custom list with a workflow and omitted the tasks part.  I just sent email's as part of the workflow, waited for responses, hide fields when the current user was not the user required to approve/reject, and finally made all fields read only after it was originally submitted, except those fields that needed for the update.  It achieved the same goal and I was able to track the progress of the entire workflow with log comments and field changes.  As a side note, I was able to achieve the flexibility I needed with JavaScript for anything I could access in the DOM.  It worked out pretty well.
0
 
Keyboard CowboyCommented:
Thanks for the endorsement and selection - Happy Holidays!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.