I am curious as to users experience with WorkFlow Designer. I don't see many questions or comments re this software.
Do people use it as a development tool, learning tool, teaching tool, documentation? Or is the consensus it is just cute but anyone worth their salt will generate scheduling script in directly in Macro Scheduler?
Look forward to a healthy discussion...
k
WorkFlow Designer
Moderators: JRL, Dorian (MJT support)
-
Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
People do use it - I helped out a user recently who had a workflow diagram containing over 1000 code blocks. I think why you would use it over just writing a script in Macro Scheduler will depend on a number of things. The obvious benefit to me is that it bridges the gap between design, documentation and implementation. It is effectively a CASE tool. In organisations where a process needs to be mapped out and documented, it's a great way to build, visualise and document that process and then attach code to it to make it work. If a step later needs to be inserted or moved, that is easily done.
I've used it before to refine requirements with a client and agree on the process in flow chart form before even thinking about code. A non-technical user understands flowcharts. So defining a process in flowchart form first can be useful. Then, after agreeing the process and adding the code the user also benefits from being able to see progress of the run visually.
But it could also come down to personal preference and the type of script/process you are building.
I expect the main reason we don't see discussion here is that most discussion here centers around the code itself. Code attached to Workflow Designer is still Macro Scheduler code built using Macro Scheduler. But it is also true that the number of people using only Macro Scheduler outnumbers those who also have Workflow Designer.
I've used it before to refine requirements with a client and agree on the process in flow chart form before even thinking about code. A non-technical user understands flowcharts. So defining a process in flowchart form first can be useful. Then, after agreeing the process and adding the code the user also benefits from being able to see progress of the run visually.
But it could also come down to personal preference and the type of script/process you are building.
I expect the main reason we don't see discussion here is that most discussion here centers around the code itself. Code attached to Workflow Designer is still Macro Scheduler code built using Macro Scheduler. But it is also true that the number of people using only Macro Scheduler outnumbers those who also have Workflow Designer.
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
Hi Marcus,
Any idea which use prevails?
- Using WorkFlow Designer as a front-end for both designing and launching Macro Scheduler scripts.
- Using WorkFlow Designer to design Macro Scheduler scripts that ultimately will run without the WorkFlow Designer.
- Using WorkFlow Designer to visualize and test manual processes having nothing to do with Macro Scheduler.
-Other.
I do not see WorkFlow Designer offered standalone, it is bundled with Macro Scheduler Enterprise. Can it be purchased standalone by those with Standard or Pro versions of Macro Scheduler?
Or by those who only have access to or compiled Macro Scheduler scripts?
Once you have created your WorkFlow for manual process verification you need an audience for your creation. In this scenario most of your audience would not be Macro Scheduler developers but non-technical business analysts. The only practical way to present the workflow to them is via a show and tell meeting. Can the WorkFlow GUI work with a compiled Macro Scheduler so the business analysts can try out your WorkFlow with with various inputs?
Thanks,
Gale
Any idea which use prevails?
- Using WorkFlow Designer as a front-end for both designing and launching Macro Scheduler scripts.
- Using WorkFlow Designer to design Macro Scheduler scripts that ultimately will run without the WorkFlow Designer.
- Using WorkFlow Designer to visualize and test manual processes having nothing to do with Macro Scheduler.
-Other.
I do not see WorkFlow Designer offered standalone, it is bundled with Macro Scheduler Enterprise. Can it be purchased standalone by those with Standard or Pro versions of Macro Scheduler?
Or by those who only have access to or compiled Macro Scheduler scripts?
Once you have created your WorkFlow for manual process verification you need an audience for your creation. In this scenario most of your audience would not be Macro Scheduler developers but non-technical business analysts. The only practical way to present the workflow to them is via a show and tell meeting. Can the WorkFlow GUI work with a compiled Macro Scheduler so the business analysts can try out your WorkFlow with with various inputs?
Thanks,
Gale
