In this article, we are going to look at the Anonymous Page feature which will be made available starting AgilePoint NX V9.
Few years back, we introduced Anonymous Forms feature that quickly became very popular. This feature enabled enterprises to engage with their customers, partners, vendors and other people outside their organization boundaries without needing to login using company issued credentials but still making sure security policies are being enforced.
Later, we introduced Page Builder module which helped companies totally rebrand their AgilePoint portal experience but that took effect only once the user logged into the portal. The requirement was to provide experience builder for internal user to match their company intranet site’s look and feel. External users still go through public facing sites to access link to anonymous forms which can be added to the site menu.
Recently, a few use cases popped-up with the necessity to expose certain AgilePoint portal pages outside of the enterprise. The typical use case could be putting up a quick event registration page or webinar page backed up by forms, integrations and workflow without having to change the website again and again. With AgilePoint NX V9, we have introduced an option to enable/disable anonymous access feature on portal page created in Page Builder module.
Diving a bit deeper, if you embed images, videos or text, these by default will be visible when accessed in anonymous mode. Coming to eForms, the eForm has to be anonymous in order to be included in the Anonymous Page. This is because the ‘regular’ eForms will have access restrictions. Work Center widget and Report Part widget cannot be embedded in Anonymous Page since they require authentication.
An additional security implementation includes whitelisting APIs. This feature ensures that only the APIs that are explicitly whitelisted can be consumed when the page is viewed in anonymous mode. So, if the page needs to access an AgilePoint API via a custom JavaScript to fetch data from a Data Entity or call a Server API, these have to be explicitly whitelisted. Page Builder APIs are whitelisted by default.
Now let’s look at this feature in action.
Note: Please note that this video is recorded while this feature is in beta version. Some of the labels and icons might change by the time it goes GA but the general concept of configuring these activities would remain the same.