Yes, All are available in the on Premise or Adobe managed hosting AEM
instance you get when you license AEM Mobile. It's the exact same list
of capabilities you get if you bought the product that used to be known
as AEM apps. Depending on what additional AEM products you license you
would have even more capability in this instance.
1) I can still do with Indesign? - YES2) Can I use the folio file and
convert the same system for the digital version of the catalog? - YES3)
AEM just about publishing and content management, etc. Customers? - No,
AEM is used by a wide variety of customers. job requirements:1) in the
catalog need of product research, by code, for narca, by category, etc.
you can do it? - YES, if you put in the correct metadata2) updates are
possible catalog? - YES3) you can create a shrine with all the sections
It's the number of files being referenced. It's not the page size. I'm
going to assume that this is an HTML article that references a lot of
other files. I think the limit is set pretty high (1k files). The limit
was set to avoid having someone initiate a DOS attack through the
ingestion service by creating articles with lots of little 1 byte files
thus overwhelming the service. We just look at the number of files and
refuse the upload if there are too many. If you are seeing this and this
So, you really don't want to show different content. You want different
entitlement on device vs web viewer. Is asking a user to sign in on a
mobile device that onerous that you'd go through the maintenance issues
of multiple content hierarchies just to avoid signing in?
Can you provide more detail? I've been able to sign multiple apps today
using the DPS App signing tool. All of them load onto my devices just
fine and run. I'm not submitting them to any app store however.
Having a greyed out sign up box there usually means that you already
have an analytics essentials account or your account is linked to an
Adobe Analytics account. Maybe the master admin already went through the
process of setting this up? I'd contact tech support and they can verify
and get that info...
If what you are trying to do is remove the project from the drop down
menu or from other parts of the dashboard, you can achieve almost the
same thing by simply removing the users from that project. Those users
will no longer see the project anywhere in the UI. The only caveat is
that the admin can not remove themselves from the project.
My highly placed sources say that this never should have worked on a
preview app. The share icon should not show up in the preview app. If it
did previously and it doesn't now then the previous behavior was a bug.
We do have a work item on the backlog to enable social sharing for
preview apps but the ETA is still TBD.
I'm not quite sure what you are trying to accomplish here Vamshi. It's
unlikely that your flow of logging into a web site is going to buy you
anything in the context of a DPS app because the entitlement for your
content is handled by the app. You can't use a login token or key from
logging into a web site and use it in the DPS app to control access to
content, it would be very weird to navigate to a DPS article that the
app thinks you are entitled to, only to have the article itself make
If I read the question correctly, you are asking if parts of the older
DPS platform will continue to be supported when if and when Adobe
decides to terminate the old platform? The answer is no. When we shut
down the old platform, which will only happen when customers have moved
over to DPS 2015, it will be shut down to a point where there will be no
methods to access the folio producer and publish new content to the old
You should be looking at the Content Producer APIs to solve this
problem. You are describing a very common workflow which should be
automated instead of being performed as a manual process. The DPS
dashboard isn't really set up to automate these sorts of tasks, even the
improvements under way aren't going to solve the use case of updating
several hundred pieces of article content in a streamlined fashion. I
guess one question is; Why isn't the content being updated in DPS by
your colleagues? You...
You can select multiple items in the content dashboard for deletion as
long as they are unpublished and of the same type. I just did it. The
shift select functionality is a little wonky. Select the first item,
then shift select on the label for the last item. If you shift select on
the checkbox, you'll only see that item selected. Shift select instead
on the label and all the items will get selected.
Migrate the folios individually, take the time to add keywords and
metadata and use the filter functionality to reduce the article list
down to manageable chunks. We are working on some UI additions to help
in the organizational areas, they include adding the article name to the
list of columns in the UI, letting the user choose what columns they
want to see, building a visual representation of your content hierarchy
but all will take time to build, test and release. Right now I advise
yes, this is on our list. We are working on building an interface that
makes it clear that when you "open" and article from within a collection
that you are actually editing the article as it appears in every
collection, not just the one in your current collection. Collections are
really lists of "references" to articles, not a container of the actual
articles themselves. Its a subtle difference but very important as we do
not want users editing from within a collection and getitng confused as