Yeah, that can work in some situations. But requires binaries deployed to the server, so really more of a 2010 thing, and not viable for office 365". In Spd 2013 workflow there is a new action to call a web service so that could be really useful instead of custom actions.
Mark On 23/04/2013, at 7:46 PM, "Nigel Witherdin" <nigel_wither...@hotmail.com<mailto:nigel_wither...@hotmail.com>> wrote: Is developing custom workflow actions for SPD Workflows a viable/good option? Haven't done much at all, but this like the way to add more complex but reusable options to SPD wf's Sent from my iPhone On Apr 23, 2013, at 3:49 PM, "Mark Daunt" <mda...@datacogs.com<mailto:mda...@datacogs.com>> wrote: Yeah, I hear you. SPD is only viable for really simple workflows. As soon as there is any level of complexity I have found it almost unworkable and pretty much a waste of time. In SPD 2010 it was not even easy to do a string comparison that was not case sensitive! There seems to always be little brick walls like that. Why is Visual Studio not an option for you? Mark From: Web Admin <web.ad...@syd.catholic.edu.au<mailto:web.ad...@syd.catholic.edu.au>> Reply-To: ozMOSS <ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>> Date: Tuesday, 23 April 2013 3:32 PM To: ozMOSS <ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>> Subject: Re: SP Designer 2013 Workflows I wish I had that option. :) I'm having a world of trouble trying to publish them as the complexity builds with Email and Task and actions. Only solution is to strip them back and delete associated xsn before re-publishing. On 23 April 2013 15:25, Mark Daunt <mda...@datacogs.com<mailto:mda...@datacogs.com>> wrote: A bit. Enough to still avoid them like the plague. No debugging is a real show stopper for me. I find time spent troubleshooting those suckers is better spent doing it properly in Visual Studio. I like the new ability to create workflow in stand alone apps in VS2012 and deploy without having to add code to the server (no dlls in GAC etc, its all declarative like SPD but you can debug). That's where I'll be spending most of my workflow development time. From: Web Admin <web.ad...@syd.catholic.edu.au<mailto:web.ad...@syd.catholic.edu.au>> Reply-To: ozMOSS <ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>> Date: Tuesday, 23 April 2013 3:15 PM To: ozMOSS <ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>> Subject: SP Designer 2013 Workflows Anyone else had a chance to tinker with workflows in SPD 2013? Regards, Paul _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
