validfrom/validto
You can set a validity time for a job stream, which is a time frame within which the job stream is included in the preproduction plan. The validity time is set using the validfrom key in the job stream definition.
Syntax
validfrom date
Arguments
- validfrom date
- Defines from which date the job stream is active, that is it must be included in a production plan if the production plan duration includes that date. It also defines the first date the instances in the preproduction plan are included in the current plan.
Comments
Different versions of the same job stream can be defined by creating different job streams with the same name and workstation, but having different validity intervals. The concept of versions of the same job stream sharing the same jobstreamname and the same workstationname are key when managing dependency on that job stream. In fact when you define an external follows dependencies on a job stream you identify the predecessor job stream using its jobstreamname and workstationname. The job stream identified as the dependency is the one whose validity interval is during the period the dependency is active.
If you change the jobstreamname or the workstationname in one version of the job stream, the change is propagated in all its versions.
If you lock a version of the job stream, all versions of that job stream are locked.
If you change the name of a job defined in a job stream version then the new job name is propagated in all versions of the job stream. This means that, if you modify something, other than the jobstreamname or the workstationname, the internal and external job stream associations remain consistent.
The date specified as validto value is not included in the run cycle, therefore the job stream is not active on this date.