Knowledge

Views, Filters & Print

Activity Feedback

TASKFDBK is resource comments on an activity; not TASKMEMO, not Discussion

P6 General tab. Activity Calendar, WBS, and Responsible Manager sit as fields.
These are General-tab fields. Activity Feedback is a notebook-style comment, not these fields.

What a planner means

Activity Feedback is activity-specific messages between a planner and the resources on that activity. Oracle: using Activity Details you collaborate by entering messages or feedback; all users who can access the activity can view your feedback and provide their own. The procedure is intended for project managers / planners and resources assigned to the activity.

The Feedback tab has two fields (not one):

  • Notes to Resources — comments about the activity aimed at the assigned resources. All of the activity's resources can view them. Enter text, then Add to move it into the Notes to Resources field.
  • Feedback from Resources — comments about the activity from the activity's resources.

New (rev_fdbk_flag): marked when a resource adds or revises notes / when new feedback appears in Feedback from Resources. Clear it after you review so you are notified of the next new feedback.

When Professional is connected to an EPPM database, Oracle: P6 Progress Reporter–enabled resources assigned to the activity can view those notes on the Activity Details General tab in Progress Reporter and respond. REST: Feedback is “the feedback from the resource”; NotesToResources is “the notes from the project manager to the timesheet resources”; IsNewFeedback is the flag that a resource has sent feedback notes that have not been reviewed yet. EPPM Timesheet Feedback columns: Feedback from Resource is the notes received from the resource as recorded in P6 Professional.

Oracle copy/paste: Activity Feedback is not copied.

This is not a notebook topic (TASKMEMO / MEMOTYPE / WBSMEMO). It is not a document (DOCUMENT / TASKDOC). It is not an issue (PROJISSU). It is not the Discussion tab (Comments / Unread Comments — REST UnreadCommentCount is Team Member Discussion comments, not this field). It is not primary resource or activity owner. It does not date the activity.

See Notebooks (MEMOTYPE / TASKMEMO / WBSMEMO) — Not Schedule Logic, Documents and Work Products Are Files, Not Notebooks, Issues and Thresholds — Not Schedule Logic, Primary Resource.

XER

TASKFDBK — (Activity Feedback)

ColumnOracle label
proj_idProject
task_fdbkFeedback from Resources (P6 EPPM) Feedback from Primary Resource (P6 Professional)
task_idActivity

Oracle listed only those three columns. Do not invent a unique-id column.

TASKNOTE — (Activity Notes to Resources). Separate table. Not TASKFDBK and not TASKMEMO.

ColumnOracle label
proj_idProject
task_idActivity
task_notesNotes to Resources

TASK.rev_fdbk_flag is New Feedback. It is on TASK, not on TASKFDBK.

TASK.review_end_date is Review Finish (P6 Professional only). TASK.review_type is Review Status (P6 Professional only). Those sit on the Timesheet Feedback column group; they are not the feedback text.

Microsoft Project

Desktop Project has a single Notes field: comments you enter about a task, resource, or assignment (RTF; Task Information → Notes). No Notes-to-Resources / Feedback-from-Resources pair, no New Feedback flag, no topic dictionary.

Notes ≠ Feedback. Do not map task_fdbk to MSP Notes and call them the same object. A converter may put one P6 text field into Notes; that is a product choice, not an identity. Do not claim MPXJ can write a real MPP.

Don't

  • Treat TASKFDBK as TASKMEMO / a notebook topic, a document, an issue, or Discussion comments.
  • Treat TASKNOTE.task_notes as TASKFDBK.task_fdbk, or collapse both into one field without saying which was lost.
  • Treat rev_fdbk_flag as the feedback text.
  • Invent TASKFDBK columns Oracle did not list (including a unique id).
  • Map Feedback to MSP Notes and call them the same object.
  • Claim MPXJ writes a real MPP.

Sources

Back to top