3,678 Views
8 Replies
Last post:
Jun 18, 2009 12:22 PM by
Curtis Gross 
Michael,
I believe what you are seeing with this document is the approval delay. Documents which have to go through approval will not show the initial publish time, they will show the time at which they are approved by the document approver.
This is something we have been talking about internally, because we have run into the exact same confusion. The UI / Notifications will be updated in the future to better notify users that this was the 'approval time.' Of course the danger at that point if you actually want normal users to know that the document had to be approved 
The server time is currently GMT-6, so 7 hours difference for the other timestamp is either showing the server time - or exactly when your approver got to work?
-Curtis
Michael,
This is exactly why we are trying to decide the best method to show these approvals. Here are the ways we could handle this, each has it's downside.
1) Current method: Display the approval date / time.
Plus: Your recently approved content will show up in the Recent Content / Activity / send our email notifications ASAP.
Minus: when the approval time looks totally off.
2) Display the user's original publish date
Plus: Consistent with the publisher's idea of what time it was created.
Minus: What if it takes 2 weeks to approve? The content will never be 'recent.' Search priority will be minimized, confusion from other users when they get an email notification for 2 week old content.
3) Display 'Approved @ this time'
Plus: Communication to all users that the time stated is the approval time
Minus: Maybe the CEO didn't want the rest of the company to know that his blog had to be approved
Make a vote - I can definitely push your thoughts through to our internal discussion.
Also, I am going to mess with the time on my machine / browser and see if I can get the approval time to be off.
Best,
Curtis
Hi Curtis,
I think there are two quite separate issues at play here. As for the question of what time to display against documents (or blog posts) that have been published following a collaboration phase, I think option 1 is just fine. Option 2 is clearly fraught with difficulty, and option 3 not only has the downside you point out, but also requires explanation to the vast majority of users who do not understand document collaboration so will not get what is being referred to anyway -- it may just confuse them.
My real concern, however, is about times being displayed in the wrong time zone. I just observed this happening again, this time on document comments. This is the document concerned, and here is a screenshot:
As you can see, my most recent comment shows as having been made at 05:01. In actual fact, it was made at 12:01pm BST, i.e. the time displayed is out by 7 hours.
Loading related product issues for this case
To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.