Visual Studio Team Services Extensions from the Rangers

http://blogs.msdn.com/b/visualstudioalmrangers/archive/2015/11/18/visual-studio-extensions-from-the-rangers.aspx


With the Extensions feature going live this week as per the announcement during Connect, the VS ALM Rangers have been busy creating extensions. We have a total of 11 extensions that made it into the Visual Studio Team Services Marketplace when it launched, of which 4 are published under Microsoft DevLabs and the rest as community extensions. Here’s a little bit about them…

A list of DevLabs extensions:

	Folder Management Create new folders from the code explorer within the Team Web Access. Team: Wouter de Kort & Abel Wang
	Print Cards Print cards from your backlog for use on a physical scrum board. Team: Gordon Beeming (@GordonBeeming) & Robert MacLean (@rmaclean)
	Test Case Explorer An extension to explore test cases. Team: Mattias Sköld & Mathias Olausson (@molausson + blog)
	Work Item Visualization Visualize relationships between work items from within the work item form. Team: Taavi Koosaar (@melborp + blog + GitHub + email: taavik@melborp.net)

Full list of features for Visual Studio Team Services | Visual Studio TFS 2015

Use this end-to-end feature index to learn about all the features available to help you plan and track your projects and code, build, test, and release your software applications.

https://msdn.microsoft.com/library/vs/alm/overview/alm-devops-feature-index  

Fun with SharePoint 2013 workflows and custom outcomes

It looks like a bug but it makes sense that the Custom Outcome buttons do not appear if the two fields, Percent complete and the Task Status fields are hidden or they have been set to 100% and the task status is set completed.

This is some basic logic that Microsoft put in to make things easier to the normal users.   But i think this is killing the power users who are very knowledgeable with the workflow and process from the previous versions of SharePoint.

they should just remove this basic box or restraints put on to assist the users which Microsoft typically allowed the public to find way to put in rules and such but why only allow the customization of the workflow task form for Visual Studio and not SharePoint designer if they are going the route of dumb-ing down of the users with these silly rules but only allowing more advanced users with development knowledge to customize the workflow task form.

Interesting....

Also there is a bug in the workflow where the outcome variable in the task process is ordinal value instead of the string value of the custom outcome.
for example:
Approved
Canceled
Rejected
Re-Assigned

the values are returned to the task process outcome variable is:
0 = Approved
1 = Canceled
2 = Rejected
3 = Re-Assigned

This needs to be fixed.