These forums were permanently set to read-only mode on July 20, 2022. From that day onwards, no new posting or comment is allowed on the site, but the historical content remains intact and searchable.

A new location for posting questions about PlanetPress Suite is now available:

OL Learn - PlanetPress Classic (opens in new tab)

Topic Options
#50639 - 01/21/15 06:31 AM Worflow Requests - compare workflows/find varibles
Kap Offline
OL User

Registered: 10/20/10
Posts: 80
Hi I've got two unrelated Workflow requests:

1. To be able to compare workflow files - so if two workflows have been developed and we now want to merge them it would be useful to see both on the screen at once to see exactly what has changed between the two. I know we can merge workflows but you need to already know which parts have changed to do it properly.

2. Find where local/global variables are being used. If I want to rename or delete a variable then I need to go through the entire workflow to find it. In Design it tells me where the variables are in use already or updates the names automatically which is a really nice feature.


#50642 - 01/21/15 10:41 AM Re: Worflow Requests - compare workflows/find varibles [Re: Kap]
Raphael Lalonde Lefebvre Offline
OL Expert

Registered: 10/14/05
Posts: 4956
Loc: Objectif Lune Montreal
Hi Kap,

Here's my comments on your two requests:

1. Although opening two configs simultaneously would be useful, this isn't really possible with the way Workflow is made. Workflow is designed to only allow one active configuration at a time, and in order to implement that, we'd have to put heavy restrictions on a second opened config, such as not allowing to send it, not allowing debugging, etc... A lot of trouble for something that although cool, isn't really needed in most situations, and hasn't been requested much in several years.

This problem can be worked around by keeping a changelog updated with the changes. Or, instead of having multiples copies of your configs, have multiple inactive copies of your processes, so that this way, you keep an history of the work that has been done to processes. (this suggestion may not be that good if you have a lot of processes though...)

2. There is a limit to just how much we could implement this. Unlike Design, Workflow can include external or custom resources, such as scripts, or custom plugins, that can make use of the variables, but because they're not really part of the software, we wouldn't be able to affect them. (and since it's generally more advanced stuff, we wouldn't necessarely WANT to have the application automatically change the code to "help" us, then end up breaking something in the process...)

There is also an easy workaround: Workflow configs are really XML files, and you can open them with a Text editor. Meaning that you can do a Search and Replace for the old variable name, and replace it by the new one if you want to. But as I've mentionned above, there might still be stuff that won't have been affected, or affected the wrong way, so I would still recommend double-checking the result.

Raphaël Lalonde Lefebvre