by Derek Lu
Table of contents
31 March 2015
User level: All
Required Adobe products (retail)
Additional required other products (third-party/labs/open source)
Note: If you have questions about this article, use the DPS forum. Please don’t contact technical support with questions about Adobe Developer Connection articles.
Large companies ($100M+ revenue, 1000+ employees) have staff dispersed across geographies and time zones, making communication difficult. These companies need to engage employees to keep them on top of company news and strategy and to drive a sense of culture and unity. Employees are also increasingly using mobile devices that they are familiar with for their communication needs, so companies need to leverage those channels to convey a modern brand experience to both potential and current employees.
DPS can help these companies quickly develop multi-platform mobile apps with compelling, immersive and measurable content.
This article shows how you can create a single DPS app that can be both a public recruiting app as well as an internal employee communications app. This example includes integration with the WordPress CMS and shows how you display intranet-like company news and link news stories to rich DPS folios.
External Recruiting Apps
- Convey a modern brand experience to potential new employees via compelling mobile content
- Allow potential employees to more deeply engage in the company’s brand
- Equip company recruiters with interactive presentations that bring company culture to life
New Employee Onboarding
- Ease onboarding process and make the process faster (benefits, paperwork, etc.)
Employee Communication and Retention
- Company news, strategy, HR content, and employee newsletters/magazines
- Coordinate strategy and educate employees on complex lines of business
- Promote employee cohesion and drive sense of culture
This article describes how to create a custom view that allows external users to see one view and logged in users to see another. When a user logs in, they will be able to see a WordPress feed that allows posts to be associated with a folio. For example, a company might post an article about a new 401k offering and include a download link to the associated Summary Plan Description as a folio. Content is organized into tabs that are determined by the folio filter values.
This example is iOS-only since it requires the use of two custom tabs.
The logged out state of the viewer, for the fictitious healthcare company “we.HEALTHCARE.” This view is for non-employees. The viewer uses entitlement to login users. The folios displayed in this view can be set from the DPS Configurator with steps detailed below. Displaying folios in this view is not required.
The logged in state of the viewer with integrated WordPress RSS feed and tabs to organize content. Users can tap READ MORE to view the contents of a WordPress post.
The detail view for a WordPress post with a DOWNLOAD button for the associated folio. WordPress posts are associated with a folio by adding a custom field. Posts without this custom field do not have a download button.
The view for the Benefits tab. Tabs are derived from the filter value for a folio.
Library view that displays downloaded folios.
The steps to build the viewer are:
- Set up WordPress.
- Create template(s) from the DPS Configurator.
- Setup entitlement for internal users.
- Create the viewer in App Builder.
In order to associate a WordPress post with a folio you must associate it with a product id in a custom field. Since custom fields are not automatically included in the RSS feed, you must install a plugin that includes them. One of the plugins you can use is called Custom Fields in RSS by Frank Seidel.
When creating a post in WordPress, if you’d like it associated with a folio, you will need to add a custom field and name it product_id. In the Add New Post page, if you do not see a section for Custom Fields go to the top of the page and click Screen Options then select the Custom Fields checkbox.
The screen options to add the Custom Fields section.
Next in the Custom Fields section create a custom field and name it product_id then publish your post
The Custom Fields section to add the folio product id.
This example uses two custom tab templates which are available for you to configure using the DPS Configurator. The custom tab that displays the RSS feed and allows users to download folios is the template “Custom View with WordPress.” This template only functions if the user is online so you will need to either use the default library or replace the default library with a custom tab that has offline functionality. In this example, the custom tab that displays the library is the template Library.
To edit the Custom View with WordPress template, select it and click Next. If you’d like to view your own folios in the configurator, enter your DPS Adobe ID that you use for Folio Producer and then click next. This is not required and is only used in the configurator to display folios.
The edit view for the Custom View with WordPress template.
The edit view will allow you to update the UI with your own colors, fonts and images. To integrate your RSS feed, set the URL in the field WordPress RSS URL. This URL must link to the RSS 2 feed. If it is not valid, you will see an error message. To set the folios that are displayed in the logged out view, add your product IDs to the External Product IDs field, delimited by commas. If you do not want to display any folios, you can leave this field blank.
If you’d like to toggle the logged-in/logged-out state, click the View logged-in state check box. This setting has no bearing on the custom tab at runtime. It is only there to allow you to view the logged-in and logged-out states.
Once you are done modifying the template, click Download ZIP.
Modifying the Library template
To edit the Library template, select it and click Next.
The edit view for the library template.
Edit the template to your needs and then click Download ZIP.
In order to allow users to login, you need to use an entitlement server. If you do not have one set up, you can use the one Adobe has created for POCs and demos at http://dpsapps.adobe.com/entitlement_admin. For instructions on how to use it, see this article. This example uses entitlement in two ways. First, it authenticates a user to distinguish between a non-employee and an employee. This does not require any explicit folio permissions for a user because the folios, which are displayed for logged out users, are set in the configurator by specifying the External Product IDs above. Second, to entitle users or groups to a specific folio, you can use the entitlement admin to do so. Remember to set folios as retail/public so folios are only visible to entitled users.
From the entitlement admin, copy the Service URL, https://dpsapps.adobe.com/entitlement_admin/services/index.php, and Integrator ID, dps_entitlement_poc. You will need these for the next step.
App Builder is used to create your DPS viewer. For instructions on using App Builder view the help. For this example, create a Multi Folio with Entitlement Viewer. In the entitlement section, use the Service URL and Integrator ID from above. The Service URL and Service auth URL will use the same value.
Entitlement Details in App Builder
In the Navigation Toolbar screen, add the two zip files that you had downloaded. To replace the default library with your library zip, click Use custom app library and navigate to your zip.
Once you have downloaded your IPA from App Builder, install it on your device for testing.
If you have specified folios to display in the logged-out state but folios are not displaying, first verify that you have entered the correct product IDs in the configurator. The list of folios should be delimited by commas. These should match the exact product IDs that were entered in Folio Producer. Next, make sure the folios are not retail and public. Since these folios are supposed to be visible to non-employees, they should be free and public.
If you are unable to login, verify that you are using the same username and password from the entitlement admin.
If a folio is missing for a logged-in user, go back to the admin and verify that the user is entitled to the folio. If the user is entitled, make sure the folio has a filter value, otherwise it won’t display in a tab.
If posts are not displaying in the viewer, check the RSS feed to make sure it has the latest post. If it doesn’t, then your WordPress hosting provider is probably caching the RSS feed and is updating it on a schedule. You will need to either purge the cache or wait for the next update.
This article walked you through how to create a viewer that integrates WordPress and entitlement. For more information on creating apps check out Creating Proof of Concept Apps for DPS.
Comments are currently closed as we migrate to a new commenting system. In the interim, please provide any feedback using our feedback form. Thank you for your patience.