to make an application role work. Enable the application role with the first checkbox then, give the application a name. This will be a basic label in the analytics but doesn't show up in the app anywhere. Then, scroll to the bottom of the page. The last section of this page is where you set-up where analytics data for the application will go. What you enter here will depend on your DPS subscription and whether you are also an Adobe Analytics Subscriber. If you're a SiteCatalyst or Adobe Analytics customer, you should check with your company's analytics team to learn the company name for analytics. They may offer to set-up a Report Suite for you but ask them not to do this. You will set-up the Report Suite for your app through the DPS Dashboard right here. If you're a SiteCatalyst or Adobe Analytics customer, enter the company name and then, enter a Report Suite name to identify your data. I typically use a Report Suite name inspired by a reverse DNS pattern, this helps me find my reports more easily. DPS Enterprise accounts which do not have Adobe Analytics should leave the company name field blank. Then, enter a report suite name to identify your data. Click Check Availability to make sure you have a unique Report Suite name. DPS Professional Edition users who do not have a Adobe Analytics, should not enter information for Report Suites. With these three options set for the application role, click Submit at the bottom of the page. The application role now works and the content can be built and published for an app. Eventually, you'll want to come back through these role options to add more information or to allow certain types of features to work for the content that appears in the app. You'll want to add shared secrets for any application stores your app will appear in. The shared secret will create a connection in the store between apps that you release. Once you set up your store accounts for each platform, enter the shared secrets in the corresponding field for the application role. You also want to add iTunes app URL once you prepared information through iTunes Connect about this app. And you should review and determine how you want to set up other options for the application role in each app. The Device Viewer options let you control how content is available on devices without purchase. The Content Viewer for Web area controls whether and how your content is available through web-based viewers. Primarily, on desktop or laptop systems. And the last section will enable Secure Content workflows. Primarily, of interest for internal or corporate apps where the content is sensitive. Anytime you make changes to these settings, click Submit at the bottom of the application role page and then click Back to Users to leave the role configuration area and close the browser window for DPS Account Administration. So, there you are, a quick video about setting up the application role for an Adobe ID so that you can create and publish content for an app.
Granting the Application Role
Share this Episode
Adjust your embed size below, then copy and paste the embed code above.
442 x 256
515 x 296
640 x 367
Width: px Height: px
About This Episode
To build content for an application you use an Adobe ID with the application role. In a DPS Pro or Enterprise account the application role is granted to an Adobe ID by a master or admin account. This video shows how to grant the application role to a delegate Adobe ID and settings for this role.
Runtime : 00:06:01 Added : 07/10/2014
About this show
Learn Digital Publishing Suite: Enterprise Edition
Stay on top of the latest developments for Enterprise Edition customers. Learn tips and tricks to make your publishing workflow more efficient and effective.
Next episode in this show
Other Suggested Episodes