Files marked/ready for Edition - Job-Workflow Configuration

orlando_CR

I'm having issues trying to setup a new Job-workflow that will let the files marked as edited and ready for Editions.

 

Old Jobs works fine, once a file is edited it remains with the flag as an edited file and it is included within the files once an Editions is generated for a PROD release.

 

I created a new Job-workflow based on the originals, but files edietd with that workflow are not marked as edited and as consequence will not be included in the editions.

 

I'm strugling trying to find the setting/flag that will allow to let the files marked as edited for an edition.

 

In the attached file, test_pic2.png was edited and deployed using the old Job-workflow and it remained marked for Edition as it should be ( pencil icon ). But test_pic1.png was edited and deployed using the NEW Job-workflow and after it completes it was reseted and removed the edited icon meaning it won't be include in a future edition.

 

Need help trying to find out what configuration setting is required to have the same behaviour as the original Job.

 

I already compared configurations settings and haven't found a clear specific setting. 

 

Thanks.

 

 

Adam Stoller

I think there is some confusion here.

Files marked as edited in the workarea are generally an indication of modifications to files that have not yet been submitted to the staging area.

Editions are based on the latest version of files in the staging area - not the workarea - at a particular point in time (a "snapshot" if you prefer)

 

If a workflow runs with files that are edited and the files are no longer listed as edited after the workflow completes - it is an indication that the workflow submitted the files from the workarea to staging, such that the files in the workarea are now in sync with those in staging.

 

If the files remain marked as edited (more correctly, as "modified") after the workflow completes - it is either an indication that the workflow did not submit the files to the staging area (as in a 'development' run of the PLC workflow), or that someone designed the workflow to submit the files and then "touch" them so that they remain marked as "modified" (there are reasons why one might do this, though it can cause a bit of confusion).

 

I suggest you spend a bit more time understanding the product and what you are trying to do with it, and then spend a bit more time looking over the workflow and what it is doing (or not doing as the case may be).