Perhaps I have been better organised with my project definitions since E.G. V2, but I haven't reordered tasks since I last used that version. So it wasn't until a colleague pointed out that she added a new task to a project, and it appeared last in the Explorer, and executed last in the process flow.
So she dragged it up in the process flow and it executed in the correct position in the sequence. But it meant the Explorer and the Flow were now in different sequences.
Is the lack of synchronisation recognised as an issue? (I don't see it on the SASWare ballot.) Has this any visibility to the design team?
Shameless plug: Go to support.sas.com, look for the item on the SASware ballot, open it and vote for the enhancements and fixes you want done. Even if you only do a handful of products, give the developers some feedback on the issues that concern you. You have until 4 January 2008 (U.S. time I think, but I have allowed for the international dateline and done mine already.)
Yes, it is possible for the process flow and project explorer to be out of sync. The process flow is the authority for determining the sequence that tasks will run. The process flow is a richer environment for showing dependencies. The project explorer shows organization by data used, types of content, etc.
We realize that the out-of-sync issue is a concern for some people, so we are researching ways to make these more tied together.
I spent some time last night creating projects with multiple process flows to remind me that there was not a one-to-one relationship between them.
I note that dragging and dropping objects is allowed on both the process flow window and the project window.
Our danger arose when a multi step project with a single process flow was completed, a data cleansing step was needed early on, was moved into the right position in the process flow but executed out of order when the project was run. I learned some things from this and now know to be even more careful about step sequencing.