DrawMGT - V11.4

Features

Description of end-user features, that we can explain to customers or put in our public web site.

Important New Features

1. New style work flow handling introduced on Task Detail/New

Other Changes

Database Model Changes

Database Model Changes Associated With New Features

1. New style work flow
   • New tables WF...
   • See Document SXS-T-000406-3

Other Database Model Changes

Migration Notes

• See app/schema/migrate/bin/migrate-db.sql.
• Task layout type migration

  • LayoutType determines if the following fields appear: abstract, priorityId, importanceId, probabilityId, hazardId, costImpactId, timeImpactId, technicalImpactId. These fields are independent from the work flow now.

  • The new layout types: SHORT-TASK, LONG-TASK, SHORT-RISK, LONG-RISK, SHORT, LONG

    • SHORT - field abstract doesn't appear

    • LONG - field abstract appears

    • TASK - fields priorityId, importanceId appear

    • RISK - fields probabilityId, hazardId, costImpactId, timeImpactId, technicalImpactId appear

  • The new layout type is determined by the old layout type (SHORT or LONG) and the old work flow type (TASK, RISK or NONE) as appropriate
• Task work flow migration into new style work flow

  • workFlowTypeId of Comments records are not cahnged but they refer to WFTypeRef now. (Table CommentWorkFlowTypeRef removed)

  • WFSteps record of the CommentIssuer step is set from fields issuerUserId, issueDate.

  • WFSteps record of the CommentDelegated step is optional and is set from fields delegatedToUserId, completePlanDate, completeDate, effortCompleted, statusId if delegatedToUserId is not null and assignedToUserId is not null.

  • Status of CommentDelegated step is ste as follows:

    • New (Unclassified) -> Pending

    • Informational -> Closed

    • Pending -> Pending

    • Hold -> Pending

    • Closed -> Closed

    • Reopened -> Pending

    • Obsolete -> Pending (Obsolete will be set in separate field as at Documents)

    • Answered -> Pending

    • Denied -> Closed

    • Duplicate -> Pending (???)

  • An inactive CommentDelegated WFSteps record is generated always for TASK and RISK work flows.

  • WFSteps record of the CommentAssigned step is mandatory and is set from fields completePlanDate, completeDate, effortCompleted, statusId. ResponsibleId is set from assignedToUserId, delegatedToUserId, issuerUserId (from the first not null one) if completeDate is set or from assignedToUserId, delegatedToUserId if completeDate is not set.

  • Status of CommentAssigned step is ste as follows:

    • New (Unclassified) -> Pending

    • Informational -> Closed

    • Pending -> Pending

    • Hold -> Hold

    • Closed -> Closed

    • Reopened -> Reopened

    • Obsolete -> Pending (Obsolete will be set in separate field as at Documents)

    • Answered -> Answered

    • Denied -> Denied

    • Duplicate -> Pending (???)

  • WFStepsCache table filled up as appropriate

Development Notes

New Style Work Flow

New Style Work Flow is imlemented and used currently on Comment New and Detail transaction ONLY through work flow wizard.

Advantages of the new work model:

1. Fully configurable
2. Work flow step can be optional
3. Unlimited number of parallel work flow steps can be used (by setting maxParallel to 0)

4. Task can be assigned to users with only CommentView permission (no CommentUpd) and he can set status and complete date on Comment Detail.

Disdvantages of the new work flow model:

1. A new table WFStepsCache is used to hold some information about the first, firs not comleted, last completed and last steps to allow to make lists easily.

Assumptions, conventions in the new work flow model:

1. The object (Comments record) and a full set of steps are initialized calling the New transaction. If the new obbject is not saved but cancelled the WFsteps records are also deleted.

2. A crontab job is necessary to remove objects not saved, together with all associated records (see. function CommentsSet::deleteNotSaved).

3. The first step of a work flow is always a step like Issuer.

4. All steps has field completeDate

5. Work flow is completed if the field completeDate of the last step is set

6. The work flow step where a new step can be added (maxParallel is not reached) an inactive WFSteps record (inactiveFlag is set) is used, necessary for the workflow wizard to display a line with the iaddi button.

7. The workflow wizard has 3 modes: user (no CommentUpd permission), admin (CommentUpd permission) and rooti (Admin permission) as described in document SXS-T-000358