| # Secondary Status of Objects To define tThe secondary status of objects, the user can use the available system defined status. The system-defined status is the status assigned to the ODM objects. ODM objects include: CR CH CP_VER DOCS DOC_REV FILE FLDR HARD COPY QUERY LIBR TASK TG For example, a Change (CH) has the following system-defined status: Created Under Review Approved Rejected Cancelled Frozen Completed The sequence of status determines the order of the status assigned to the object. Example, if the user is at a particular system-defined status in a lifecycle, the secondary status, if defined, appears for that object instance during the lifecycle. The purpose of a user-defined status is to create status conditions customized to the needs of a particular company. Example, a company might need a change process status called Financial Approval that precedes the actual system defined Approval status. |