cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Carry over the source file's check-in comment to generated design representations

Carry over the source file's check-in comment to generated design representations

When the Job Processor creates a design representation (e.g. DWF, PDF, or other derivative outputs) from a source file, the check-in or state change comment of that source file is currently lost. The generated representation either has no comment or only a generic, job-generated entry.

It would be very helpful if the comment entered during the check-in of the source file were automatically transferred to the newly created representation file — for all target file variants (DWF, PDF, and any other output format produced by the job).

This would preserve the context and intent that the author documented at check-in (e.g. revision notes, change reasons) right where it is most useful, without requiring a manual second step.

 

Preferred behavior: when a design representation is generated by the Job Processor, the check-in comment of the source file should be copied into the comment field of the created representation file. This should apply consistently across every target file type, so the original context travels with the derivative regardless of output format.

2 Comments
Markus.Koechl
Autodesk

I see various use cases and file versions as a source. E.g., if the current source's state is Work in Progress, a manually triggered design representation should copy the latest version's check-in comment. What if the source file is in a Released state? I guess you expect the comment from the initial version in the latest released state, rather than the latest version's comment generated by jobs or automation. @christian.hombach: Would you mind adding your view on this, please?

christian.hombach
Contributor

Hi @Markus.Koechl,

You're right, there are several use cases. I would always copy the comment from the latest version, including when it's in a released state. If the comment was written by a user, it's useful to have it attached to the design representation as well.

If it's a "system default" standard comment — one placed there automatically by a configured standard comment for a specific state — it might also be copied, since it isn't wrong to do so. However, the copying could also be skipped if the comment is equivalent to the configured standard comment of the current state.

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea