Camms.Project MQU – My Issue Decisions
This article contains: |
1. Overview |
By default, this section will display issue decisions:
Which are linked to Open projects.
For which you are the responsible officer for.
For which you have view permission for the respective Issue Register object.
Which have not been resolved.
In order to edit issue decisions, the relevant project should be opened.
Inline Quick Update will display the below given information for each issue decision:
Decision No – Displays the Decision No for the issue decision. Non-editable.
Decision Title – Displays the Decision Title for the issue decision. Non-editable.
Date Logged – Displays the Log Date for the issue decision. Non-editable.
Date Resolved – Displays the Resolved Date for the issue decision. Date Resolved will be enabled when the ‘Decision Status’ is ‘Resolved’. Otherwise, it will be blank.
Status – Displays the Decision Status for the issue decision.
Comment – Displays the comment for the issue decision.
2. Issue Register Object and Groupings |
The Issue Register Object can be added multiple times within one workflow. Further, the Issue Register Object will be either common to the workflow OR unique for the phase OR unique or incremental based on the organisation’s configurations.
If the Issue Register object is common to the project workflow:
My Quick Update will display all issue decisions which you are responsible for in the current editable Issue Register object in the project workflow.
Issue decisions should be grouped by:
The ‘project’ which the issue decisions are linked to [Projects will be ordered by the Project Code].
The ‘issue’ which the issue decision is linked to [Issues will be ordered by the Issue No].
Notes:
If an issue decision is not linked to an issue, then that issue decision should be shown under the group ‘Issue: Not linked’. The ‘Issue: Not Linked’ group should be shown after all issue decisions linked to any issue are displayed under the project.
Under the ‘Issue: Not Linked’ grouping, there can be issue decisions which are linked to an issue action OR issue decisions which are not linked to any issue action.
iii. The ‘issue action’ which the issue decision is linked to [Issue actions will be ordered by the Action No].
Notes:
If an issue decision is not linked to an issue action, then that issue decision should be shown under the group ‘Action: Not linked’. The ‘Action: Not Linked' group should be shown after issue decisions linked to any issue action are displayed under the project.
Example for groupings:
|
2. If the Issue Register Object is unique for the phase:
a. My Quick Update will display all issue decisions which the user is responsible for in the current editable Issue Register object. Further, if there are any issue decisions which you are responsible for in any other Issue Register object which is editable in the project workflow, those will also be displayed.
b. Issue decisions should be grouped by:
i. The ‘project’ which the issue decisions are linked to [Projects will be ordered by the project code]
ii. The ‘phase’ which the corresponding issue register object is available in the workflow [Phases will be ordered according to the order in the project workflow].
ii. The ‘issue’ which the issue decision is linked to [Issues will be ordered by the Issue No].
Notes:
If an issue decision is not linked to an issue, then that issue decision should be shown under the group ‘Issue: Not linked’. The ‘Issue: Not Linked’ group should be shown after all issue decisions linked to any issue are displayed under the project.
Under the ‘Issue: Not Linked’ grouping, there can be issue decisions which are linked to an issue action OR issue decisions which are not linked to any issue action.
iv. The ‘issue action’ which the issue decision is linked to [Issue actions will be ordered by the Action No].
Example for Groupings:
|
3. If the Issue Register object is unique and incremental:
a. My Quick Update will display all issue decisions which you are responsible for in the current editable Issue Register object. Further, if there are any issue decisions which the user is responsible for in any other Issue Register object which is editable in the project workflow, those will also be displayed.
b. Issue decisions should be grouped by:
i. The ‘project’ which the issue decisions are linked to [Projects will be ordered by the project code].
ii. The ‘phase’ which the corresponding issue register object is available in the workflow [Phases will be ordered according to the order in the project workflow].
iii. The ‘issue’ which the issue decision is linked to [Issues will be ordered by the Issue No].
iv. The ‘issue action’ which the issue decision is linked to [Issue actions will be ordered by the Action No].
Example for Groupings:
|
View other articles under this section: |
