Active Profiles reporting in Control Panel is available to all Adobe Campaign Customers (Classic or Standard) whose instances are fully hosted on AWS. This feature is available as beta. Any Campaign customer (AWS hosted) can use this functionality by accepting beta consent
This feature provides :
Consolidated view of active profiles of all the instances of an IMS Org at a single and easy to view place experiencecloud.adobe.com
Data is provided on a day level granularity (instead of monthly view as of now)
Historical view of usage evolution of Active Profiles over a period of an year
All the Adobe Campaign customers that are hosted on Public Cloud (all versions of ACC and ACS) can now subscribe to email alerts to get notified about some important metrics related to health of their system with recommended user actions
When admin users log on to Campaign Control Panel via Experience Cloud login they can view a card to subscribe to email alerts.
Control Panel would send notifications and alerts to subscribed admin users when one or more of the instances exceed SFTP usage above 80% or DB usage exceeds 80% or SSL certificates are near expiry or have already expired
For over 12 years, this competition has been a unique analytics-focused business case competition where university students are given the opportunity to use Adobe’s industry-leading analytics products and access to real-world data from leading organizations such as Starwood, Lenovo, Condé Nast, Comcast, Overstock.com, Backcountry.com, Sony PlayStation, and MGM Resort International.
Through this program, Adobe has exposed thousands of students to the high-demand fields of digital marketing and analytics. Selected individuals from the Adobe Analytics Challenge will be given the opportunity to interview for internships and full-time positions at Adobe and our sponsor company. Over the years, Adobe has hired more than 50 students from this program, and it has been a valuable recruiting pool for other companies and agencies looking for data-driven talent
Digital Marketing organizations have access to a plethora of data which is growing at a faster rate than ever before. Digital Marketers have tools to segment their customers or visitors based on their geography , demography, and behavior etc., but it is still a challenging task to easily compare the performance of one segment of customers with another.
Adobe Analytics introduced a new powerful Segment Comparison tool in Analysis Workspace in Summer 2016 release (i.e on June 16, 2016) for Analysis Workspace users to easily compare the performance of one segment of customers with another. This functionality was made available to all Analytics Standard and above licensed customers.
In recent past, there have been an increasing number of requests from customers to provide a way so that they can restrict non-admin users to just use Analysis Workspace and they do not have to go through the complexity of searching for hundreds of pre-canned reports provided in Reports section.
We have introduced a new group Reports & Analytics Access in Summer 2016 release. Any non-admin user who is part of this group can access Reports section and all the pre-canned reports available under it. Admin users can remove a specific user from this group in order to restrict that user to just Analysis Workspace.
admin user Alice would like to restrict non-admin user Bob to not have access to Reports section
A capability to add a Blank Panel in the workspace is introduced in Summer 2016 release. Analysts who start off many new projects during their exploration process might want to start everything from scratch and a clean state, now they can Go to Panels panel and drag n drop new blank panel on to Workspace canvas area.
Any visualization out of the seventeen visualizations that we support in Analysis workspace as of now can be dragged and dropped onto the blank panel.
When any visualization other than Freeform Table , Cohort Table, Text, and Venn are dragged and dropped onto Blank Panel a Freeform Table visualization is automatically added because those visualizations need data from a linked Freeform table in order to display graphs and charts on visualization pod
An increasing number of features are getting added to Adobe Analytics Analysis workspace at a rapid pace. It was appropriate for us to update the current Analysis workspace user interactions metaphor of using actions toolbar on the top of Analysis Workspace to a smart pull-down navigation menu metaphor which is a representative of most of the popular applications that computer users interact with.
In Summer 2016 release , there are three noticeable UI changes in Analysis Workspace :
Action buttons on top area of Analysis workspace are now made available as smart pull down menu items
Components panel and Visualizations panel on the top are now available on left-hand rail
A new panels panel has been introduced. An analysis workspace user can drag and drop one of the panels (blank , freeform & Segment Comparison) on to a new project or existing project.
For Analysis workspace power users who spend most of their time in the workspace and are more comfortable using short cuts, we have ensured that there is no change in the functionality of shortcut keys and all the shortcuts before Summer 2016 release would continue to work with same behavior after Summer 2016 release.
Full list of shortcuts before summer release and after summer release are listed in the screenshot below :
Analysis Workspace shortcuts
Analysis Workspace UI before and after Summer 2016 release are depicted in screenshots below :
One of the key features of AEM 6.0 Forms is integration with EchoSign service. Any XFA based adaptive form can be configured to be digitally signed using EchoSign service.
During development time you may want create an XFA based adaptive form to see the end-to-end signing workflow. For that one of the pre-requisites is to have an EchoSign API key. You may want to obtain a developer key during development phase before going to production.
I am listing down the steps to obtain an EchoSign Developer API key
You will receive an automated registration email from EchoSign to your registered email account, check your Inbox (spam folder if necessary) and activate the account by clicking the URL provided in the mail
Log on to EchoSign
Navigate to “Account tab” and click “EchoSign API” panel on left hand side tabbed panel items
Copy the API key which needs to be provided when creating a cloud service configuration for EchoSign service in AEM 6.0
The below image shows where to look for API key when logged on to EchoSign
If you happen to see the following error while starting AEM 6.0 quickstart after installing AEM Forms add-on package (adobe-aemfd–pkg-1.0.78.zip)
*ERROR* [FelixDispatchQueue] adobe-aemfd-signatures FrameworkEvent ERROR (org.osgi.framework.BundleException: Activator start error in bundle adobe-aemfd-signatures .) org.osgi.framework.BundleException: Activator start error in bundle adobe-aemfd-signatures . at org.apache.felix.framework.Felix.activateBundle(Felix.java:2202) at org.apache.felix.framework.Felix.startBundle(Felix.java:2070) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1297) at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoClassDefFoundError: com/rsa/asn1/ASN_Exception at com.adobe.fd.signatures.activator.Activator.start(Activator.java:36) at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645) at org.apache.felix.framework.Felix.activateBundle(Felix.java:2152) … 4 common frames omitted Caused by: java.lang.ClassNotFoundException: com.rsa.asn1.ASN_Exception not found by adobe-aemfd-signatures  at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1550) at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:77) at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1973) at java.lang.ClassLoader.loadClass(Unknown Source) … 7 common frames omitted
It is because couple of boot delegation properties not being included in sling.properties file.
To resolve these errors , follow the steps mentioned :
Stop AEM server
Add these two properties in sling.properties file under /conf folder