Version 4.4 October 2020

What's New in the Apty Admin Portal?

Configurable number of application environments supported by Apty

PATH:  Admin Console > on the left side panel select application > at the top of the application menu click the Gear   icon > Environment Setup tab

Previous versions of Apty supported 2 fixed environments per application: production and pre-production. 

In a new version this limitation has been removed: each application can now support multiple environments upon request. This upgrade adds more freedom for setting up Apty within defined spaces and provides the following benefits:  

  • supporting multiple environments of the hosting application allows testing Apty content in lower environments without interfering with higher environments like Production or Staging that might be used for other purposes at the given time,
  • an ability to enable / disable Apty widget for each environment allows regulating where users can see Apty within one click (covered further in the article), 
  • new publishing process that supports different versions of the element for different environments (covered further in the article).

A new publishing process supporting multiple environments

PATH: Admin Portal > select an application on the left side bar > Publish

A new functionality allowing Apty to support multiple environments opened a way to a more secure content version control and publishing procedure. Introduction of a new publishing process implies that the content can now be published in all environments gradually, starting with the lowest environment of the given application and moving up to the Production.

For the purpose of this example let's assume that your application has 3 active environments supported by Apty: UAT, Staging, and Production. After you created a piece of content, you can only directly publish it in UAT and after that it may be published in Staging and Production. This new procedure benefits your content quality in the following ways:

  • Multiple layers of publishing saves the mistakes represented by the "human factor" (accident clicks),
  • Eliminates bypassing of the content testing,
  • If the content published on production needs to be updated, it can be done without visible interruptions for the end users: while the older version is still published and available on production, you can update the content in the lower environments.

Enabling / Disabling Apty Widget in different environments in one click

PATH:  Admin Console > on the left side panel select application > at the top of the application menu click the Gear   icon > Environment Setup tab

With introduction of multiple environments, Apty also offers more flexibility with enabling a widget selectively.
A new setting has been added to the Environment Setup tab on the Manage Current Application page: Enable Apty Widget checkbox. This function allows gradually implementing Apty starting with lower environments or enabling a widget for a quick demo or testing sessions on higher environments with an ability to further disable a widget with on click (if needed).

3rd Party Analytics Integration

PATH:  Admin Console > on the left side panel select application > at the top of the application menu click the Gear    icon >Third Party Analytics

When it comes to data analysis, each company has its own best practices, favorite tools and methods; therefore, we at Apty wanted to give our customers freedom and flexibility of viewing and visualizing analytics data in the dashboards of their choice. In a new release we are adding functionality that gives provision for users to migrate analytics data to their own apps. In order to do that, Application Administrator needs to get to the Manage Current Application screen > Third Party Analytics integration options, define request type, URL connecting to the third party, event key, and choose events that they choose to receive. Detailed instructions on how to setup Third Part Analytics can be found by following the link below.

For more details refer to: Third Party Analytics Integration

What's New in the Apty Studio?

Publishing content directly from Apty Studio

In previous versions of Apty all the content procedures related to changing publishing states of the items were performed solely in the Apty Admin Portal.

With the 4.4 release and further all types of content which are currently created using the Apty Studio, namely Workflows, Validations, Tooltips, Launchers, and Announcements can now be published directly from the Studio. This improvement saves time by allowing authors to perform all content manipulation procedures (creating, editing, publishing) in a single place in the system.

NOTE: Publishing functionality is duplicated in the Admin panel which allows users to control publishing states of the items in multiple environments without the need to install Apty Studio.

Expanded functionality in Studio's Rich Text Editor

To introduce more flexibility when it comes to customization of the content we provide through Apty Assist. This level of flexibility has been and ask from prospects and customers, such features are all supported by our main competitors

The following functions were added / upgraded:

Allow admins to insert HTML code snippets in all content types.

Allow admins to underline text in all content types.

Allow admins to upload an image. In previous Apty versions images were supposed to be hosted in another resource and only the link to the image was accepted. Currently, you can drag and drop an image and it will be hosted by Apty. 

Allow admins to insert videos in all content types (from URL).

Allow admins to add numbered lists in all content types.

Allow admins to add bullet lists in all content types.

An ability to copy content within the same application

In one of the previous releases Apty introduced an ability to copy Workflows from one application to another within the context of the same Admin Panel. This feature is helpful in an event when your applications share identical or similar UI but represent different countries; therefore, you might want to use the same Workflows with different translations. 

Similarly, within the context of the same application you may have use cases where several Workflows share a number of similar subsequent steps. Instead of having to recreate each step manually, a new feature has been introduced: it allows duplicating content for the same application in the Apty Studio.

  • The copied version of the Workflow is saved in a Draft status. It can be edited and published manually.
  • When the Workflow is copied, all the export files are copied with it.  

Ability to Identify a Page Using Label Comparison

One of the first steps for creating any kind of Apty content (Workflows, Tooltips, Announcements, etc.) is to define what web page they belong to. This can be typically done by defining URL hash of the page, defining specific anchor points or writing a custom script (for example, by checking the class of the HTML <body> tag or other custom solutions). In a new release we are adding a simplified option for page identification: Label Comparison. This logic will help Apty to define whether it is a correct page to display content based on the unique element labels.
This new function identifies the correct page in the following way:
1.   When setting up a condition, you define a label unique to the page and the value it should be equal to (for example, a label of the "Supplier #" input field on the product order form).

2.   Once the page is loaded, Apty scans through the DOM structure.

3.   If the label with a correct text is found, the page is considered to be a correct one.

4.   Apty attaches pre-defined content to it.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.