Publish flows

When publishing flows, Provisioning Portal commits flows customization to a pre-configured network path. The Web farm (IIS instances) references this path as the physical path (source path) of the scripts virtual folder for your tenant.

Stop

Check with your service provider for the exact publishing behavior before using this feature. Depending on the system configuration, the path to write flows (publish) may be the same as the path to read flows (reload), or the two paths may be different.

Caution

If the two paths are different, publishing means committing flows customization on top of the last synchronized flows copy, in which, the last synchronized copy may be different from the production copy.

Note

  • If both paths are the same, publishing means committing flows customization made on top of the production copy.
  • The value for the PublishScriptFolder key is configured in the PS.ProvisioningPortal web.config file:
<add key="PublishScriptFolder" value="\\{FQDN}\IVRScripts\{tenantId}\{appName}\" />
  • The value for the ReloadScriptFolder key is configured in the PS.ProvisioningPortal web.config file:
<add key="ReloadScriptFolder" value="\\{FQDN}\IVRScripts\{tenantId}\{appName}\" />
  • Provisioning Portal creates a backup of files to be updated. The backup files are located in the following folder: Flows_PublishedFilesBackup{Date.Now}
  • Provisioning Portal keeps track of Publish and Reload by using the Provisioning Portal database. It does so by duplicating the application’s data and providing a new version of it. Currently only ASG engineers can revert the application to a specific version.

To publish the flows:

  1. On the Flows page, click .
  2. In the Publish dialog, click Publish.