CC Tutorials Gets Connected

Creative Cloud Tutorials is a mobile app our team built that delivers training content to our customers. CC Tutorials was built after talking with the Adobe Primetime team about use cases for their new Primetime Player SDK.

The product team wanted to provide a full featured player to developers to help them get started. We wrote the video player inside CC Tutorials as that code that the product team could provide to our external customers.

Along the way our CC Tutorials App now has over 165,000 downloads.

Continue reading…

Personalized Customer Experience

The Adobe@Adobe team have been working on early builds of AEM Screens to deliver a personalized customer experience in San Jose’s new Customer Experience Center. The center opened in mid-September with a variety of next generation digital experiences. Working with the Brand, CEC and AEM Screens teams we built an internet of things (IoT) enabled experience.

“A@A brings personalized information screens on a new level; a perfect, 1st reference for AEM Screens.”

– Martin Buergi, Product Manager

Continue reading…

Build single page applications using AngularJS on AEM

Larger presentation can be found here

Code repo is here

More detailed video sessions will be posted here the second week of July

Creative Cloud for enterprise Customer Success Package

Through the Adobe@Adobe program our company is customer zero. We deploy unreleased versions of our software within our enterprise so we can provide real world testing before releasing our software to the public.

Late in 2014, our team, along with the Creative Cloud for enterprise team, embarked on a program to deliver Creative Cloud for our employees using not the ubiquitous AdobeID but rather a Federated ID – our employee’s network ID – similar to how any other large organization would.

The following article is our lessons learned along with tips to help customers make the most of their experiences deploying Creative Cloud for enterprise.

Continue reading…

Adobe Enterprise Dashboard

With the advent of Creative Cloud for Enterprise (CCE) a key new resource for IT administrators has become available: the Adobe Enterprise Dashboard. The dashboard empowers an IT administrator to handle numerous organizational tasks, from account management and app provision to group management and access levels. While these and other myriad features of the dashboard assist an IT administrator, perhaps the best known feature of the dashboard is its option to explicitly manage enterprise identity providers. With this feature the IT administrator can now configure multiple identity providers by first claiming domains and then configuring enterprise identity schemes of either Enterprise ID type or Federated ID type.

Continue reading…

Meet the Adobe@Adobe team

CQ Tips and Tricks #4 – Switching SiteCatalyst Reporting Suite at runtime based on host

Recently I was configuring a new CQ install and we needed to switch SiteCatalyst reporting suites based on the host the application was running on.

The way we ended up doing this was by adding some custom javascript in the General SiteCatalyst Settings section of the framework.

//check for communities.dev|qa|stage.adobe.com or prod
s.dynamicAccountSelection=true;
s.dynamicAccountList="adbecush=communities.adobe.com;adbecush=communities.adobe.com;adbecush=cush-author.corp.adobe.com";

Here is a screen shot for reference.
sitecatlyst_settings

CQ Tips and Tricks #3 – Getting a service from JSP

This is just a quick little example of my two favorite ways to grab a service in a JSP page.

adaptTo is super handy

<%@taglib prefix="sling" uri="http://sling.apache.org/taglibs/sling/1.0"%>
<sling:defineObjects />

<%@ page session="false" import="com.day.cq.security.UserManager"%>

<%
    UserManager userManager = resource.adaptTo(UserManager.class);
%>

see this page for more details on Adaptors make sure what your trying to adaptTo is mapped correctly. For example in this case I went from Resource to UserManager not all classes support AdaptTo.

Another simple way it to get a service is using the slingScriptHelper

<%@taglib prefix="sling" uri="http://sling.apache.org/taglibs/sling/1.0"%>
<sling:defineObjects />
<%@ page session="false" import="com.day.cq.contentsync.handler.util.RequestResponseFactory"%>

<%
    RequestResponseFactory requestResponseFactory = sling.getService(RequestResponseFactory.class);
%>

Adobe Saves Thousands Using Adobe EchoSign

Some of the happiest surprises here at Adobe are the results we realize from using our own products.

Our team members want performance, value, engagement, and experiences that make their jobs productive and rewarding, just like our customers. To make that happen, we’ve been encouraging teams throughout Adobe—such as sales, procurement, and people resources—to integrate Adobe EchoSign into their e-signature workflows.

So far, the results have been spectacular:

·         Procurement has slashed $250,000 from its operating overhead

·         Vendor contract completion is three times faster

·         People resources has cut printing costs 80% and shipping costs by $35,000

Many of my colleagues are impressed at how well automating signature processes improves productivity while it cuts costs.  We also had a really easy time integrating EchoSign with our existing technology. The Adobe EchoSign API integrated with our legacy system in only three weeks, using only one analyst, one developer, and a few software QA people.

Our sales department uses Apttus enterprise contract management system (ECM), powered by Salesforce.com to manage nondisclosure agreements. The sales team can leverage EchoSign e-sign workflows within the ECM, generating clear audit trails to expedite workflows and verify the legality of agreements. The forthcoming companywide rollout and integration of ECM with Adobe EchoSign will make contracting even faster and more reliable.

Learn more about Adobe and the benefits we yield from Adobe EchoSign by clicking here

CQ Tips and Tricks #2 – Handy Urls

This is by no means an exhaustive list of all the handy URL’s found in the CQ 5.5 – 5.6 platform.  This is my short list of clipboard handy URLS.

URLS

/crx/explorer/index.jsp  – CRX explorer

/crx/de/index.jsp – CRXDE Lite url

/libs/cq/search/content/querydebug.html – Query debug tool

/libs/granite/security/content/admin.html – New user manager standalone ui  [5.6 only?]

/libs/cq/contentsync/content/console.html – Content sync console

/system/console/bundles – Felix web admin console

/system/console/jmx/com.adobe.granite.workflow%3Atype%3DMaintenance – Felix web admin console JMX / Workflow maintenance tasks

/system/console/jmx/com.adobe.granite%3Atype%3DRepository – Felix web admin console JMX / Repository maintenance tasks

/system/console/depfinder – This new 5.6 tool will help you figure out what package exports a class and also prints a Maven Dependency for the class.

/libs/granite/ui/content/dumplibs.rebuild.html?rebuild=true – Helpful link for debugging caching problems. Wipes the clientlibs and designs and forces it to rebuild it. Thanks to Mark Ellis for this link.

/system/console/adapters – This link shows you the Adapters are registered in the system. This helps you figure out what you can adaptTo() from resource to resource.

/libs/cq/compat/components/ntupgrade.html – This link allows you to update Node Types in the system. Thanks Tamer.

https://www.adobeaemcloud.com/content/packageshare.html – Link to the external interface for the CQ Package Share.

http://localhost:4502/crx/explorer/diagnostic/prof.jsp – Shows you the built in profiler

http://localhost:4502/system/console/profiler – Shows you the built in profiler

Params

wcmmode=DISABLED – This handy publisher parameter turns off CQ authoring features so you can preview a page cleanly
debugClientLibs=true – This will help to debug clientLibs includes

If you have more handy URL’s and or parameters that you think others should know about please comment on this blog entry and I will add them to the list.