SAP Knowledge Base Article - Public

2790061 - I edited a blog or event but my name does not show as the updater.

Symptom

User 'B' edits a blog post or event. However the blog or event creator is still displayed as the updater of the blog, not user 'B'

Environment

SAP Jam

Reproducing the Issue

  1. Go to 'content' section in an SAP Jam Group
  2. Edit an existing blog 

Resolution

This is by design.

  • Events and Blogs are both content types that are only ever editable by the author, group administrators, and in the case of Blogs the designated authors.
  • Because these types are not "collaborative" types, meaning despite the group's collaboration policy only the author and group admins can edit the type, SAP Jam will always will display the original author as both the creator and updater of the object.  

See Also

Related documentation:

Events: https://help.sap.com/viewer/user_help/10bc9713c5a040558c7a8614b1d1785c.html
"Only the event host can invite others, edit, delete, and restore their own events."

Blogs: https://help.sap.com/viewer/user_help/b1d039c67d4a1014ba05827eb0e91070.html
"When non-group administrators and non-blog post approver group members view a published blog post, the name of the group member that the blog post is written on behalf always displays as the author; the name of the ghost writer never displays to group members once the blog post is published."

Keywords

author, creator , KBA , LOD-SF-JAM-CNT , Content, File Sharing & Upload , Problem

Product

SAP Jam 1207 ; SAP Jam 1210 ; SAP Jam 1302 ; SAP Jam 1305 ; SAP Jam 1308 ; SAP Jam 1311 ; SAP Jam 1402 ; SAP Jam 1405 ; SAP Jam 1408 ; SAP Jam 1411 ; SAP Jam 1502 ; SAP Jam 1505 ; SAP Jam 1508 ; SAP Jam 1511 ; SAP Jam 1602 ; SAP Jam 1605 ; SAP Jam Collaboration 1608 ; SAP Jam Collaboration 1611 ; SAP Jam Collaboration 1702 ; SAP Jam Collaboration 1705 ; SAP Jam Collaboration 1708 ; SAP Jam Collaboration 1711 ; SAP Jam Collaboration 1802 ; SAP Jam Collaboration 1805 ; SAP Jam Collaboration 1808 ; SAP Jam Collaboration 1811 ; SAP Jam Collaboration 1902 ; SAP Jam Collaboration 1905