The capabilities described on this page are included in Appian's standard capability tier. Usage limits may apply. |
Making continuous improvements and updates to your portal is important to ensure the best possible experience for your users. To make your portal available to your users, you'll need to publish, test, and deploy your portal.
A portal consists of a portal object and at least one interface object. The interfaces contain the content for the portal object, displayed as separate pages. The portal object contains the settings used to create the portal.
When you publish a portal, Appian bundles up the portal object, the interfaces, and all of the objects used by the interfaces, and publishes them all as a cohesive serverless web app at a unique URL.
Publishing a portal makes it available to your users at the specified web address. This means that anyone with the URL can access your portal. For more information, see Who can access a portal during testing?.
You'll only directly publish a portal in the environment where you're developing the portal. When you're ready to publish the portal in another environment, deploy it. The publication status of the deployed portal will apply in the new environment. So if you deploy a published portal to another environment, it will automatically publish the portal in that environment. See Deploying portals for more information.
You can view all of the portals in your environment along with their publication status in the PORTAL MONITORING tab.
When you are ready to start testing your portal during development, publish it. Keep in mind that if you deploy a published portal to another environment, it will automatically publish the portal in that environment.
To publish a portal:
When you are ready to publish your portal for production use, you can prepare to have it automatically publish in your production environment through a deployment.
When you deploy a published portal to another environment, Appian will attempt to publish the portal in the target environment.
In order for the portal to publish successfully, before deploying your portal for the first time, you will need to set up the following in your target environment:
After the portal publishes successfully in the target environment for the first time, whenever you deploy the portal or its precedents from your source environment, it will update and republish the portal in your target environment. See Deploying portals for more information.
Follow the steps below to set up your portal to publish successfully in another environment.
Unpublishing a portal makes the portal unavailable to users. When you deploy a portal that has been unpublished to another environment, it will automatically unpublish in that environment.
To unpublish a portal:
While you're developing portals, we'll keep published portals up to date by automatically republishing them to reflect your latest changes. Additionally, if you deploy any of the following changes to another environment, the portal in the other environment will be republished.
We will automatically republish the portal when:
We also republish all published portals after an environment is restarted, such as when it is upgraded or hotfixed. This ensures portals in all environments reflect security updates and performance enhancements as soon as the environment is updated.
Although it is usually unnecessary, you can also manually republish a portal.
You may want to manually republish a portal if:
To manually republish a published portal:
As with all Appian applications, you should always fully test all objects that your portal relies on to make sure everything is functioning correctly. Be sure to test everything in your portal interface, including all input and selection fields, and connections, queries, and processes.
This section outlines some guidelines that are unique to testing portals. If you run into any issues while testing, see Troubleshooting a Portal.
After you've tested all objects and connections for your portal in Appian Designer, it's important to fully test your portal after it is published. Be sure to fill out all of the fields, whether they are required or not, and go through all of the steps in your portal.
Testing in a published portal will help mitigate the following concerns:
Be sure to fully test all parts of the connections to your portal with production-level data and usage. This includes all web APIs, integrations, and connected systems.
To make sure your portals are meeting operational standards when users interact with them, use the Portal Monitoring tab on the Monitor view of Appian Designer. The metrics on this tab alert you to potential issues so you can avoid serving slow or inaccessible portals to your users.
See Configuring reCAPTCHA for additional information on testing reCAPTCHA.
You must publish your portal to fully test it, which means that anyone with the web address can access your portal, maybe even before you're ready for them to.
To help limit access to the portal while you're testing, UUIDs are added by default to the web addresses of all portals in your development and testing environments. This means that only users that you share the URL with will be able to easily find the portal during development.
In production environments, this option is deselected by default to make the web addresses more intuitive and easier for your users to access them.
This setting can be changed in the Administration Console.
As with all objects, when you deploy a portal object all of the fields and configurations are deployed with it. After deployment, the value of the portal object's Published field in the target environment will be the same as the Published field value in the source environment.
For example:
When deploying a published portal, the portal will automatically publish in the target environment during deployment.
If your portal is published in the target environment and you deploy an updated precedent of the portal to that environment, the portal will automatically republish after import to include the latest updates.
For more information on packages and deployments, see:
If you are updating a plug-in that is being used in a portal, the plug-in must be updated in the environment before the portal is republished.
To update a plug-in being used in a portal:
For production environments, we recommend deploying portals during off-peak hours. When a portal is republished, users interacting with your portal may encounter errors or lose any work in progress. Remember that portals republish even when you deploy a change to a precedent of a portal object.
In some cases, you may need to provide connection information in an import customization file (ICF) when deploying portals. This table outlines the information you may need to provide in an ICF.
If your portal uses… | Don't forget! |
---|---|
Integrations and Web APIs to write or query data | ICF with API keys |
Querying or writing data directly from a publicly accessible external database | ICF with data source connected system credentials |
Google reCAPTCHA connected system | ICF with connected system credentials |
Environment specific constant | ICF with value of constant |
Integration to external system | ICF with connected system credentials |
Manage a Portal