The staging framework uses more factors to identify what's going to be published.
In case of the web content the date range is being used to look for contents. Let's say you have a web content article which is new, the framework will look for the createDate and modifiedDate to see if it needs to be published. The isNew() method is way too low level for this operation, it's more used in the persistence layer.
Generally speaking the numbers are coming from the data handlers, in this case the JournalPortletDataHandler. The actual method being called for the number is the doPrepareManifestSummary(). This method will count the number of entities for the given portlet to be published.
For the actual logic however we will need to dig deeper, the export actionable dynamic query has the addCriteria method will assemble the actual criteria which will be used to determine the number back on the UI.
So just to add more clarification this is the call chain (in s simplified form):
UI asking for the manifest summary which contains the numbers ->
JournalPortletDataHandler.doPrepareManifestSummary() calling the export actionable dynamic queries for each relevant asset (article, folder, etc) ->
JournalArticleExportActionableDynamicQuery will take the parameter settings from the UI and adds extra filtering such as the date range settings ->
a query ends up in the DB determining the number of the items we want to publish.
So back to your original question that you need more information on the items you will be publishing. Unfortunately the framework does not have built in for that, but using the very similar approach I think it would be fairly easy to implement your own.
The ExportActionableDynamicQuery is specifically used to execute a certain action (hence the Actionable part of the name) but the concept is the same for DynamicQueries.
You would simple need to implement a DynamicQuery which queries articles from the DB and add the same logic from the ExportActionableDynamicQuery:
@Override
public void addCriteria(DynamicQuery dynamicQuery) {
super.addCriteria(dynamicQuery);
if (portletDataContext.getBooleanParameter(
NAMESPACE, "version-history")) {
return;
}
DynamicQuery articleVersionDynamicQuery =
DynamicQueryFactoryUtil.forClass(
JournalArticle.class, "articleVersion",
PortalClassLoaderUtil.getClassLoader());
articleVersionDynamicQuery.setProjection(
ProjectionFactoryUtil.alias(
ProjectionFactoryUtil.max("articleVersion.version"),
"articleVersion.version"));
// We need to use the "this" default alias to make sure the
// database engine handles this subquery as a correlated
// subquery
articleVersionDynamicQuery.add(
RestrictionsFactoryUtil.eqProperty(
"this.resourcePrimKey",
"articleVersion.resourcePrimKey"));
Property versionProperty = PropertyFactoryUtil.forName(
"version");
dynamicQuery.add(
versionProperty.eq(articleVersionDynamicQuery));
}
This piece is copied from the JournalPortletDataHandler. So executing a DynamicQuery having this criteria, will give you the result of the entities selected for publication.
Hope this helps. It's a lot of info, so let me know if you need more clarification.
Thanks,
Máté
Juan Miguel García:
Hi, I'd like to achieve the same goal. I mean I'd like to retrieve more information of the web content and documents and media about to publish from staging to live.
I attach an image where you can see the amount of content or documents and media it will publish. Well I'd like to get as much information of it, let's say the title, description, modifed date...
I know that 'new approved content' will be published, I can get that information using JournalArticle.isNew(); But if the content has published already but we perform a modification, how can we know if this one is ready to publish from staging to live?
Many thanks in advance.
