Work Log FAQs

1. Impact of Log Objectification on Rich Text Field Capabilities

Currently, there are three types of rich text capabilities available, as shown below:

picture coming soon:
(Web) Non-objectified (not enrolled in log objectification beta or not in the expansion queue)

picture coming soon:
(Web) After objectification (but not enrolled in collaborative rich text 2.0 beta)

picture coming soon:
(Web) Objectified and enrolled in collaborative rich text 2.0 beta

Supported capabilities vary across scenarios, as summarized below:

picture coming soon:

Notes:
a. How to identify objectification status: Check for the presence of the [Save Draft] button.
b. After objectification, mobile devices lose location functionality. If still using rich text 1.0, topics, polls, and tables remain unsupported.
c. Current limitations after enrolling in collaborative rich text 2.0 beta (ongoing optimizations):
- Mobile: Emoji reactions, topic creation, and polls are temporarily unavailable.
- Web: Batch downloading attachments is unsupported.
- Tables currently don’t support templates or exportable queries.

2. Field Display Adjustment After Clicking [Show More] in Log List

On Web/PC platforms, logs initially appear in [Summary Layout] before clicking “Show More,” then switch to [Detail Layout]. These layouts have different field displays. Admins can adjust fields for each layout via Backend > Logs > Layout Settings.

3. The [Time] Field in Log Filters

The [Time Field] is a text field, allowing only exact-date searches (not date ranges). For range-based filtering, use time fields like [Log Start Date].

4. Log Data Export Options

Pre-objectification: Export via Backend > Log Query Statistics.
Post-objectification: Export directly from the object list page.

5. Multi-Person Feedback Fields in Objectified Logs

For logs with multi-person feedback:
- Feedback Status and Feedback Content fields don’t display or export due to non-unique data constraints.
- BI Reports cannot analyze feedback-related data (status, reviewer, score, content, or time).

6. New Record Types Not Displaying in Frontend

After admins create log Record Types in Preset Object Management > Logs and assign layouts, they must also configure applicable scopes and reporting cycles in Business Rules Management > Log Management for frontend synchronization.

7. Minimum Cc Scope vs. Log List Visibility

• Minimum Cc Scope (set in backend) only affects feed visibility in Feeds (workplace streams) and Follow-Up Activities on object detail pages.
• Log list visibility depends on user data permissions, unrelated to Cc scope.
  Refer to How to Use Logs for details.

8. Sub-object Components Not Displaying During Log Creation

a. Verify the employee has create/edit permissions for the Sub-object.
b. Confirm the Sub-object’s Record Type matches the Primary Object’s.

picture coming soon:
Functional Permissions > Log Details

picture coming soon:
Custom Object Management > Log Details > Record Type > Match Primary Object Record Type

9. Viewing Historical Logs of Deactivated (Former) Employees

Deactivated employees’ data remains accessible, even after reactivation:
1. In Feeds, filter by Created By and select [Deactivated Employees].
2. For objectified logs, use Reports and select [Deactivated Employees] in person filters.
3. Objectified logs also appear in lists based on data permissions.

10. Log Submission Targets (Virtual Objects)

These virtual objects (invisible in management) enable statistical reporting. When a Record Type enables logging statistics, submission rules generate Log Submission Data, producing reports on completion status (e.g., overdue submissions).

11. Disabling Log Types

• Non-objectified logs: Disable directly in Log Template Management.
• Objectified logs: Disable via Preset Object Management > Logs > Record Types.

picture coming soon:

12. Tracking Unsubmitted Logs

In BI Reports, create a metric: Unsubmitted Logs = Total Required Submissions - Total Submitted Logs.

13. Querying Deactivated Employees’ Logs

Log Query Statistics only includes active employees’ data.

14. Hiding Feedback Reminders

Feedback reminders (To-Do items) persist even when marked as read—solid notifications become hollow, but the task remains.

15. Manually Adding People to Weekly Logs’ [@-Frequent] Tab

No. The [Frequent] tab auto-populates with recently @-mentioned users.

16. Log Visibility Without Cc Scope

Yes. Logs are accessible via:
- Log Object Lists (depends on data permissions, e.g., read-only settings allow superiors to view).
- Object Detail Pages (Follow-Up Activities).
Feeds require Cc scope for visibility.

17. Restoring Deleted Logs

• Non-objectified logs: Irrecoverable.
• Objectified logs: Admins with [Recycle Bin] permissions can restore via Backend Management > Recycle Bin.

18. Enabling/Disabling Log Deletion Permissions

Configure in Backend > Role Permissions > Functional Permissions by toggling Create/Edit/Delete under the employee’s role.

19. Backend Changes and Historical Logs

Settings like default Cc recipients don’t affect existing logs.

20. Cc Scope Visibility Issues

Cc scope only governs Feeds visibility. Confirm you’re checking the correct entry point.

21. Viewing Log Cc Scope

Check the Data Source section at the top of the log detail page.