You are currently reviewing an older revision of this page.
For stored jobs, the criteria used to determine whether a source document needs to be reprocessed during an incremental job run are now customizable with Bentley iCS for PDF CONNECT Edition Update 3.2 . The options below are available. By default, any recognized changes to the document or any of its references continue to cause reprocessing.
Different change criteria may be defined for the master document versus references. For example, if a new rendition is required whenever any aspect of the master document is changed, or the reference file contents are updated, but all reference attribute changes may be ignored, then set ‘Document Update Time’ and ‘Reference File Update Time’ to True and ‘Reference Update Time’ to False.
Some actions, such as changes to the logical set using ProjectWise Explorer’s Manage Reference Versions tool, continue to unconditionally force reprocessing of the affected documents. Disabling of these criteria is not allowed in order to assure proper product operation.
The ’Incremental Settings’ tab on the Job Builder dialog is only displayed if the ‘Enable Advanced Job Properties’ configuration property is set to True.
Document Update Time
If True, reprocessing is performed if the source document’s Update time has changed since the previous job run.
This criterion applies only to the master document.
The default is True.
Document File Update Time
If True, reprocessing is performed if the source document’s File Update time has changed since the previous job run.
If True, reprocessing is performed if the source document’s name or location has changed since the previous job run.
If defined, a semicolon-delimited list of ProjectWise environment attribute names for which to compare the current value against the value from the previous job run. If at least one of the specified attributes has changed value, the source document is reprocessed. Each attribute name may contain “*” or “?” wildcards. The attribute names are not case-sensitive.
This criterion makes sense only in conjunction with the “Document Update Time” criterion being False. Otherwise any document change, including attribute values, causes reprocessing.
Environment attributes not listed in the criterion are ignored and changes in their values do not cause reprocessing (assuming Document Update Time is False and no other changes are detected). Listed attributes that aren’t present in the document’s environment are also ignored, so the criterion may safely include attribute names across multiple environments.
The default is undefined.
Reference Update Time
Same as Document Update Time, but applies only to references.
Reference File Update Time
Same as Document File Update Time, but applies only to references.
Same as Document URL, but applies only to references.
Same as Document Attributes, but applies only to references.
Some of these criteria are not designed to be changed in between incremental job runs. Due to the nature of how the rendition and distribution times are calculated and persisted in the database and job working folder, altering the Update Time or File Update Time criteria without subsequently resetting the job or performing a full job run may result in source documents not being reprocessed as expected.