What is "Publish Application"?
Authors can configure an Application that displays Modules they selected and make that Application available to testers or their target audience.
Why would you publish an Application?
Publishing an Application for testing purposes enables authors to thoroughly review the navigation and custom theme applied. They can make it available to a target audience. If you have multi-client publishing enabled, you can also make the Application available to clients.
In the Publish Application tab:
- Authors can publish one Application and select individual components that should be included on the Published Application page
- The Application can be tested before activating the LIVE Application
- The URL can be shared and accessed by any authenticated user
Example use cases
Data Breach Assessor
The Data Breach Assistant helps companies assess, document and report suspected data breaches according to requirements set out in the GDPR. The tool saves valuable hours for companies by simplifying their complex obligations.
Innovation Tracker: Use case pipeline
A published Application allows project managers to offer one page to submit new use case ideas and assess their feasibility. Colleagues can view an overview of all submitted use case ideas - through a Data View – and add their own – through a Module. Whereas project managers can use Modules and Data Views to qualify and prioritize submitted ideas as well as to keep track of their status.
How does Publish Application work?
Structure of a published Application
Access control
Only authenticated end-users can access a published Application. This refers to end-users with an admin, author, or user role attributed in the BRYTER Admin Console.
As to which Modules actually appear and can be used by these authenticated end-users, this depends on access settings in the publishing menu of each Module. More information and a step-by-step guide on how to restrict access to only authenticated end-users can be found in the article 🚀 How to restrict access to published Modules for selected end-users.
❗ Please note that Modules secured via Only accessible via an API key will not appear in the Publish Application navigation.
How to set up and use Publish Application
Publish Application configuration
In an Application, select Publish Application to open the Publish Application configuration.
Add a Module and publish it in an Application
Configure the page by selecting the Modules that should appear in the Publish Application navigation.
Authors can also change the display name of the Application or Modules and rearrange the Modules' order. Changes to the name in the configuration will only affect the execution view for end-users and not change the name of the Modules in the Application.
Save changes and test your published Application or use the generated URL to share it with end-users.
When ready, activate “Live” toggle to activate LIVE Publish Application. This will create a unique URL for the LIVE environment of the Publish Application.
Add a Data View and publish it in an Application
Data Views cannot be directly selected in the Publish Application configuration. But authors can use Modules that only contain a redirect result node to link to a Data View and display a Data View in Publish Application.
In a newly created Module, add a Redirect Result Node (and delete the automatically added Input Node) and choose Data View. Select the correct Data View from the list below.
In the Publish Application configuration, add this new Module and save the new configuration. The Data View will now appear on the Publish Application page.
Authors can use a Module to create a Redirect Result Node to a Data View. It can then be displayed in the Application setup and subsequently published.
Adding custom views or integrating external pages in Publish Application
Following a similar approach to Data Views, authors can also integrate external webpages. Repeat the steps shown above to integrate a URL using a Custom URL in a Redirect result node in a separate Module.
If the website has no conflicting security settings (see limitations below), it will be displayed in the published Application and can be used as expected.
Testing and sharing a published Application
Save changes in the configuration in case you have not done it yet and activate the Test toggle. The Test published Application is now available. Click Open Test to test the published Application configuration or Copy link to share with colleagues
Please note:
- When saving changes, any updates will be applied automatically to the TEST and LIVE published Application pages
- When ready, activate "Live" toggle, to activate LIVE published Application
- Open LIVE to test the published Application configuration or Copy link to share with colleagues
Known/current limitations
- Select Data Views in Publish Application configuration is not yet available and Data Views do not appear in the navigation. They can only be included with a Module and a redirect to the Data Ciew.
- Come back later and restart page will link to an individual Module, not back to the published Application
- Resume Module session when switching between components (when switching between components of a published Application, the session data will not be stored)
- Modules secured via Only accessible via an API key will not appear in the Publish Application navigation
- Responsive design for smaller devices
- Configuration of landing page
- Websites can only be included with a Module containing a redirect result if the website in question allows iframe embedding. Websites setting a
x-frame-options: SAMEORIGINheader cannot be displayed due to their security settings
The following limitation is by design:
- Published Applications can only be used by authenticated users