Organizing project transformation scenarios

[Patrik]

Hi,

I have some projects with a growing number of transformation scenarios. So it's becoming uncomfortable to find the right one.
Maybe some kind of folder mechanism would be nice so you can organize them.
This might also enable you to easily select a set of transformation scenarios - e.g. for publishing all variants to all formats.

Regards,
Patrik

[adrian]

Hi,

We already have a feature request for this. I have added your vote. For future reference it is issue EXM-28506. We will notify this thread when it is implemented.

Currently it is possible to group scenarios together with the help of a prefix in the scenario name. Use digits if you want them in a specific order.
e.g.
[MyGroup1] 1 Some scenario
[MyGroup1] 2 Another scenario

Regards,
Adrian

[Patrik]

Ok, Thanks.

Patrik

[rmcilvride]

Has any support for this kind of organizing project transformation scenarios been implemented since this original post? We are trying to follow the guidance here by naming our scenarios in a sequential order, and it isn't working very well. For example, we have scenarios named as follows:

01Skkynet-PDF-Set
02Skkynet-PDF-Set
03Skkynet-PDF-Set
04DocBookWebHelp
05DocBookWebHelp-Final

Recently it started with 04DocBookWebHelp, then went to 05, then 01, 02, and 03. In previous attempts, with other names, it went through groups in reverse sequence from, for example, 3 to 2 to 1. Stopping and restarting the transformation didn't change it.

Is there any way we can ensure the order of implementation of transformation scenarios?

[adrian]

Hi,

The organizing mentioned here is not for running the scenarios, but for grouping them together under categories, so you can locate them faster.
Running the scenarios in a specific order is a completely different matter. Please see my answer from this topic, Sequence of transformations.
In short, the association with multiple scenarios does not ensure the scenarios will be executed in a specific order. Especially after restarting Oxygen.
I would say that the normal order of execution (within the same Oxygen session) is the order in which they were associated. However, since this is not something by design, it can vary from one version of Oxygen to another and restarting Oxygen will probably change the order (associations get sorted at some point).

We do have a feature request for "Batch/Chained transformation scenarios" (implies that they are run in a specific order). I've added your vote.

Regards,
Adrian