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.