Chain All is, for each contract listed in the list view of Contract Maintenance, creating a copy of that contract so that the originating contract (the one being copied from) has a ‘next contract’ value of the contract being created and thus the newly copied/chained contract has the originating contract as its ‘previous contract.’ This uses existing copy functionality where, if the contract being copied is a ‘priority contract’ or if the contract is already approved then that priority value will be reset (and the user alerted) as well as creating the copy as ‘not approved’ (all other values are copied exactly – except for: any last used date, any quote origination number, any existing ‘next-chain’ of the copy-from contract). If a contract already has a ‘next contract’ listed then it is not allowed to be copied/chained using this procedure – that contract is skipped.
Field Descriptions
Use the following fields to chain contracts:
1. New Contract Effective
This field is for the new chained contract’s effective date. It may optionally be set using the buttons to the field’s right (one for ‘Today’ and one for ‘None’). The default is for ‘Today’ though any date may be entered.
If a contract that is being copied from has its expiration date as ‘Never’ then that expiration date will be changed to be one day before the date entered here.
If a contract that is being copied from has its expiration date a date that is not one day before the date entered here then it will be changed to be 1 day before this entered date.
If there is no entry here (if the none button is selected) then the new contract’s effective date will be one day after the originating contract’s expiration date – if the originating contract’s expiration date is ‘Never’ then the originating contract’s expiration date will be changed to be ‘Today’ and the new contract’s effective date will be 1 day greater.
2. New Contract Expiration
This field is for the new chained contract’s expiration date. It may optionally be set using the buttons to the field’s right (one for ‘Never’ and one for ‘None’). The default is for ‘Never’ though any date may be entered. Any entry made here will be the expiration date entered for every contract being created/chained. If this field is ‘None’ then there must be a numeric entry in the following field.
3. Offset Expiration Dates By
This field, and its companion field beside it, is optionally used if the ‘New Contract Expiration’ field is “None” (if the ‘New Contract Expiration’ has a value other than “None” this field is disabled, and will not be used to calculate the chained contracts expiration date). The value entered here, along with the companion field’s selection of Day or Week or Month, will be used to calculate, from the newly created/chained contract’s effective date that contract’s expiration date.
4. Collection
This selection allows you to add this newly created/chained contract(s) to the collection they are working with in contract maintenance, to replace the collection they are working with in contract maintenance, or neither (to chain/create the contract only and then return to contract maintenance without any change to the collection being worked with).
See Also