The SLICE_STATUS column of the PRTEAM table contains a value 4.
If Timeslice is processing a new assignment slice request and a blob is modified for the other assignment types, it is possible that Timeslice might miss the changes that occurred in the other assignment types.
This is because when Timeslice is processing a new assignment slice request all the assignment records are set to slice status of 1. But the new slice request data is re-sliced. Therefore changes made to the other assignment types will be missed as they will all be reset to NULL when the time slicing job has completed.
Because of this a new slice status (4) has be created in versions 8.1.1 and above. This status will be used to set the slice status of all unmodified object records to 4 so that any of the same type of object records already marked as changed (status 1) will not be affected.
Keywords: CLARITYKB, CLRT-8124, clarity8open.
Release: NCSVCS05900-8.1-Clarity-Service Connect-for MS-SQL