Check in comments on Workflow template

[TorstenG]

The Check in comment on a workflow template are not part of the dataset if you export the workflow to ZIP or JAR file.

In our example we have a chain of 3 systems in order to test and verify if a workflow change is OK.

First we manually create/change the workflow template in our TEST system, during check in of the template we refer to our change management system and issue the change number in the check in comment.

If the change is OK, we export to ZIP and import to PrePROD system for a end user verification. Already on this first export/import the change management number is lost during import.

Last import is done on PROD system, no comment at all since its lost.

It is hard to track changes if this information is not persistent.

Please make the comment part of the export data set and please consider to import a template into checked out status, then maybe a comment can be made manually as last step

[BjoernRueegg]

Absolutely, and not only for the Workflow, rather also for lifecycle, oir, and all other possible templates. The history is so important when working with three different systems dev, test, prod!

[STEVEG]

This is incredibly important.

[gobada]

Comment field critical for imported workflow process template and lifecycle template

[UM_9960668]

It is hard to track changes if this information is not persistent.

Perhaps the best thing would be the ability to edit the comment at object import as a last step.

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.