There are many things to do in the IT World and finding new projects that are worthwhile can be difficult to do. To help, we’ve created a custom form and workflow to help you weed through the numerous project requests you receive. The form allows for any user to submit new projects to an IT Department’s Business Relationship Managers and IT Leadership team to determine if the project should be pursued. The associated workflow allows for IT Manager approval, Project Manager approval and assignment, the ability to notify users when a bug should be filed, and helps to streamline the process of finding new and worthwhile projects. Click to View and Download the new IT Project Request Form and Workflow today! • Top Contributors • • • • • • • • • • • Who's Online • Online now! • Online now! I would just use a list and alerts or approval workflows etc. Here's what I mean. You make a list called Task or Project Requests. ![]() Add the columns as 'fields' that you expect the user to fill out. Some examples could be 'Request Name (instead of title)', 'Reason for Request', 'Type of Request (which could be a choice field with the types available)' etc. Now when you click the 'New' Task or Project request it will display a form that allows users to fill out a request. You can take the URL from the top of your webbrowser and add this as a link to the left navigation or into a page for users to quickly 'submit' requests. Keep in mind the Source query string parameter is where it automatically redirects to upon completion. Add an approval to the SharePoint list that works the way you need it to and voila you have your solution. Be sure to use content types and play with the columns and if necessary create your own workflows using SharePoint designer to do some more complicated things that the basic approval does not do. All documents containing content for publications submitted to the Office of Marketing and Creative Services must be in Microsoft Word format. The office systems do not support WordPerfect, Adobe PageMaker or Microsoft Publisher. By submitting this request form, you agree to: complete any necessary copy; the Office of. The Project Request Form Template is a great tool to channel all those requests coming in with various content or simply not enough. The Project Request Form Template. (Such as assigning a task, or to do item as you suggest). Hope this helps get you started, Richard Harbridge. ![]() 4 Best Practices For Project Request Management. A project request form in. Information on the new BrightWork Project Request Manager template. Microsoft Office Project Server. Project Initiation with Windows Forms is an. If you do not use a project template, on the Project Initiation form you. ![]() I would just use a list and alerts or approval workflows etc. Here's what I mean. You make a list called Task or Project Requests. Add the columns as 'fields' that you expect the user to fill out. Some examples could be 'Request Name (instead of title)', 'Reason for Request', 'Type of Request (which could be a choice field with the types available)' etc. Now when you click the 'New' Task or Project request it will display a form that allows users to fill out a request. You can take the URL from the top of your webbrowser and add this as a link to the left navigation or into a page for users to quickly 'submit' requests. Keep in mind the Source query string parameter is where it automatically redirects to upon completion. Add an approval to the SharePoint list that works the way you need it to and voila you have your solution. Be sure to use content types and play with the columns and if necessary create your own workflows using SharePoint designer to do some more complicated things that the basic approval does not do. (Such as assigning a task, or to do item as you suggest). Hope this helps get you started, Richard Harbridge. It really depends on the complexity of the process and input of users. You can save a list/library as a template, create site definitions and lots of things that allow you to distribute the custom forms you make, however InfoPath is 'easier' to distribute forms. It is also relatively easier to teach a person how to use and create complex forms in InfoPath whereas teaching a person designer might be a little more difficult. The time it takes to implement a custom form (SharePoint) is very small, it's a good quick solution if you need one. But infopath can make it easier to adjust input based on the user (who their manager is, what groups they belong to). ![]() An example of this: If you have a requirement where a form is being pushed around to different users for different input, then it makes sense to go with infopath, since this would be harder with SharePoint designer. If you have multiple farms and lots of webs you want to distribute say, and expense reporting form, then it makes sense to go with infopath instead of playing with custom forms, site definitions and features. If you have enterprise SharePoint 2007 then you get Forms SErvices as well which allows both form types to display in a browser, so they are the same in that regard. An infopath form can also be much more secure, and can have added code to it much easier than a lists new or edit forms. My recommendation? Use SharePoint forms for Proof of Concepts, testing out workflows etc, because it allows rapid development and deployment (with designer) and can be created literally by just adding columns to a list. Use InfoPath for larger or important process deployments. Hope this helps clarify it a little bit, Richard Harbridge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
April 2018
Categories |