SharePoint developer task allocation template

Project Name

Module Name

Task Information
Task Title

Task Description

Task Type
[ ] Normal Task (Only SharePoint Related)
[ ] Normal + DB (SharePoint + SQL)
[ ] DB Only
[ ] Requires R&D
What does this task contain  (Check all that applies)
[ ] Has View
[ ] Has Save
[ ] Has Edit
[ ] Has Grid
[ ] Has Modal Dialogs
[ ] Has Server Object Model
[ ] Has Client Object Model
[ ] Has Web Services, WCF Services or REST Services
[ ] Has Javascript / JQuery / SPServices
[ ] Has External Database Interaction
[ ] Is a Report
[ ] Is a Background Timer Job
[ ] Is a SQL Work (Table, View, Stored Procedure, Function)
Technical Details
Technical Approach (WebPart, Appl Page, Modal Dialog etc.)

Solution Name, WebPart / Appl Page Name

List Names

Table Names

Which machine this task should be done in?

What Web Application URL?

Best Practices to be followed

UI Details
To be made Responsive
 Yes / No
Master Page

CSS to refer to

Other Relevant Information

Timeline Information
By when this has to be started and ended
Start Date: ____
End Date: _____
When next review will be done by TL
Date ______
Time ______
Related Tasks, References
Which task this is related to? (Done by this developer or any other developer)
Related meaning, only if the other task is done, this developer can do this task OR this developer’s work picks some data from that task, or this developer’s work sends some data that is used by another developer’s task

Reference Internal Links (within iGrid)

Reference External Links (Internet Links)

Any reference code (either paste the code in the next column or attach the notepad or .cs file)

Any other TL or Colleague name to whom help can be sought

Final acceptance criteria
Mention the different things you expect before you can accept saying, this is done

After checking does it need to be deployed in another machine / URL, if so, specify that and also specify who has to be contacted to do this deployment, if this user does not have direct permissions

Comments

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

Image
You must have tried External Content Types - the exciting new feature in SharePoint 2010 to connect to an external SQL table and provide a list where it lists, creates, updates data straight into the SQL table. People always wonder, how do you get a ECT to work with a Stored Procedure, one that has input parameters. You could do it this way... Step 1: In your SharePoint Designer 2010, create a new external content type Step 2: Connect to your SQL Server and then make sure you see the Routines (your stored procedures must be listed here) Step 3: Rt Click on the Stored Procedure name and create operations for "Read Item" and "Read List" - both are required for the External Content Type's SharePoint list to be created. During both these wizards, in the Input Parameters, your SP's Input Parameter will be listed. Here, you need to create a filter, which sends out it's value to the SP's filter. For example, if your SP's Input Parameter is @Emp
Read more

NAV 2009 Issues in Role Tailored Client

Image
Role tailored client issue Changing stored procedure to 64 bit in NAV 2009 Did install Dynamics NAV 2009 on windows 2008 64 bit / Windows 7 65 bit. When trying to connect to the database in classic client I got this error. The following SQL server error or errors occurred: 17750,“42000”,[Microsoft][ODBC SQL Server Driver][SQL Server]Could not load the DLL C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database\xp_ndo.dll, or one of the DLLs it references. Reason: 193(failed to retrieve text for this error. Reason: 15100). SQL: INSERT INTO [#$ndo$groups] {CALL [master]..[xp_ndo_enumusergroups](?,?)} The reason for this error is that the installed xp_ndo.dll is 32 bit and not 64 bit. My solution was simple to replace xp_ndo.dll with the 64 bit version. 1. Stop SQL server 2. Copy \\vedfssrv01\DynamicsNAV2009\W1\DVD\Sql_esp\x64\ xp_ndo_x64.dll to C:\Program Files (x86)\Microsoft Dynamics NAV\60\Database 3. Rename existing xp_ndo.dll to xp_ndo_x32.dll 4. Rename xp
Read more