After reviewing with our beta testers, we found that many of the headlines and story leads were very repetitive, leading to a confused update, such as "Vatican doctors photo of Benedict's praise for Francis. The Vatican admitted Wednesday that it altered a photo sent to the media of a letter from retired Pope Benedict XVI about Pope Francis." So, we are using just the lead instead and usually it was much less weird.

That being said - I have gotten this request before as well and so perhaps we need to add some kind of toggle where you can control this. 

As a side note, we did recently release a new feature to get "min words" for an Alexa feed. The idea is that you can get the first 200 words (or whatever) instead of a much shorter amount. This may help some clarity as well.

https://help.bloxcms.com/knowledge-base/releases/software_releases/article_c4d392b9-e352-5682-8e65-fb50698e5b47.html 

Hey Brad!

I wanted to let you know that BLOX Go is a major initiative for us this year. In fact, we're totally re-doing it!

Coming soon, it will be re-released with an entirely new UI that is a lot more flexible.

In this first version, we are focusing on changing the UI elements and not adding a ton of new functionality. For our first version we're striving for feature parity with the existing interface. But in subsequent versions, we will add much more functionality, including having access to more fields, more asset types and eventually, more BLOX CMS applications.

Hi Scott! Sorry for the confusion... "reset to now" would be a feature request. So I was asking hypothetically if, assuming we built this "reset to now" command, it would work for you to create that workflow. I have already gone ahead and submitted this as a feature request, so at this point I'm just making sure it works in all of our user cases.

Yes, it is based on that. There may be some that don't work, but it is based on that.

Can you make a "breaking news" workflow that basically just has one or two steps, that does a publish and a "reset to now" command?

Okay, I spoke with our dev team, and it sounds like we agree with where you two ended up in the conversation... that this sounds like a great workflow step.

So, like Scott described, we would add a new workflow option that says something like, "Reset article start time to current time as part of this workflow transition." (Probably less wordy.) Then, when you hit the point in the workflow where you are putting the story live, you would have that feature trigger and it would then reset the start time.

The thing I like about this is that it does not rely upon editors or reporters to edit the asset to adjust it - rather, it just happens automatically with no extra work!

If you have a situation where you do not want something to be re-set to "now," you could create another workflow for that scenario and not include the "reset time to now" option. Or, in extreme cases, you could go back into the asset and back-date it.

What do you guys think?

When an article is created, the start time is always "now" - within a couple minutes.

But it sounds like you're saying that a reporter creates an article at 9 am (and the start date/time would be 9 am today). During this time it is set to "no publish" status, I assume. Then they start writing it, check with their sources, crunch data, file reports, fact check, talk on the phone while typing and other things reporters do! Then, 3 hours later, they want to publish the article, so they go in and remove the "no publish" status (or, maybe an editor does). But, the publish time says it was published at 9 am, when really it was 12 pm.

Is this an accurate (with some exaggerations about the reporting process perhaps) representation of the user story you are describing?

So, your idea is that, when the story is published, you want the reporter, or an editor, to go back into the story and hit a button that would then change the time to "now" to more accurately reflect the real publish time. But, then that is still relying upon the reporter to go change something, which is part of the problem.

Does all of this sound accurate so far? I have a few ideas about this, but I need to talk to my dev team about it...

Hey Nick! Awesome!!! Thanks so much!! =)