Worklflow 2013 should have MORE functionality than WF 2010
8pproval Workflow functionality is limited. A ItemModertorStusChanged event reciver is missing. WF 2010 has more functionality and hence used instead of WF2013. Even with WF2010 it is tricky to get appovers names and dates into library columns. SharePoint Designer 2013 is unstable and may corrupt the system!
Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now. In SharePoint Online we are gradually moving towards Flow from the classic workflow scenarios. In on-premises workflow is absolutely supported and there should not be any corrupt issues. If that would be the case, it would be rather a bug than a new feature. We do understand the importance of the business processes support and are looking to further invest in this area also in future, but not using the classic concepts.