Activity Stream and Work Notes not visible for custom my Project table in Workspace

jai281997
Tera Contributor

Hi Community,

I’m facing an issue with Activity Stream / Work Notes in a Configurable Workspace for a custom Project table.

Current behavior

For a Project record:

  • In Native UI, the Work Notes journal field and Activities formatter are displayed correctly.
  • I can add Work Notes successfully.
  • Existing activities/field changes are also displayed.
  • In Workspace, the Work Notes composer and Activity Stream are not displayed.

However, for the related Project Task / Project Task records, Work Notes and Activity Stream are displayed correctly in Workspace but for my project record Activity Stream / Work Notes are not displayed below screenshot is the example for project task the same way i want to view Activity Stream / Work Notes to my project in workspace

jai281997_1-1794839367846.png

Comparison

Scenario Work Notes Activity
Project - Native UIWorkingWorking
Project - WorkspaceNot visibleNot visible
Project Task - Native UIWorkingWorking
Project Task - WorkspaceWorkingWorking

Is there any table-level, dictionary, UX View Rule, Activity Formatter configuration, system property, ACL, table inheritance setting, or Workspace-specific configuration that determines whether Activity Stream Compose/Activity Stream is available for a particular table?

Since the same Workspace/UI Builder setup works for Project Task, I suspect there may be some configuration specific to the Project table that Workspace requires.

Has anyone encountered this behavior with a custom table?

Any suggestions on what records/properties I should compare between the working Project Task table and the Project table would be helpful.

Thanks!



1 REPLY 1

HasanM
Tera Guru

Hi @jai281997 ,

Going through your list, these are the places to compare between Project Task (working) and Project (not working):

  1. Workspace / UI Builder (most likely): open the Record page in UI Builder and check which variant each table resolves to, and the variant conditions. If Project lands on a different variant, or the Activity tab or Composer component has a visibility condition that excludes Project, that alone explains both being missing. Also check any declarative actions or tab configuration scoped to specific tables.

  2. Table inheritance: check what the Project table extends. Project Task extends Task, so it inherits work_notes, comments and the journal and activity behaviour the workspace expects. If your Project table doesn't extend Task, the workspace activity stream may not render for it even though the classic form works.

  3. Form view / view rules: check which view the workspace uses for each table (workspace, default or custom, and any view rules that switch it). Make sure the Activity formatter and Work notes field are on that view for Project.

  4. Dictionary: compare the work_notes and comments dictionary entries for both tables (type Journal Input, active, not read-only, no dictionary override that hides them).

  5. ACLs: compare field-level read and write ACLs for project.work_notes and project.comments with the Project Task ones. Workspace hides the composer if the user can't write to the journal fields, and hides activity if they can't read it. Debug Security will show this quickly.

  6. System properties: I'm not aware of a property that enables the workspace activity stream per table. I'd focus on points 1 to 5 first.

If the table extends Task and points 1, 3, 4 and 5 all match, check the browser console when the Project record loads in the workspace, because a component error there would explain it.

Hope this helps. If it does, please mark it as helpful or accept it as the solution.