Publish a form for your app in Creator Studio

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 1 minute de lecture
  • Publishing forms once they're ready makes them available as catalog items in the production instance for published apps.

    Avant de commencer

    To publish a form, you must be given permission to work on the app.

    Pourquoi et quand exécuter cette tâche

    After you publish a form, it's available in the specified catalog on the instance you're working on. However, you still need to deploy your app to the production instance for users to access the form. For more information, see Deploying your Creator Studio app.

    Procédure

    1. Go to All > App Engine > Creator Studio to see all the apps on the Creator Studio home page.
    2. Open the application that contains the form you want to publish.
    3. Select the form you want to publish in the navigation panel.
      If you have multiple forms, make sure to select the form you're publishing.
      Remarque :
      If your app has a lot of forms, you can use the search box in the navigation panel to search for a specific form.
      Figure 1. Select the form
      Select the appropriate form from the navigation panel
    4. Select the Mark as ready button.
      Figure 2. Publish a form
      Mark your app as ready
      Remarque :
      If you haven't specified where the form will live, such as in a catalog or in the Employee Center, you're prompted to Edit location setting. For more information, see Edit the settings for a form in Creator Studio.

    Résultats

    The catalog item for the form is ready to be deployed with your app. Once the app is deployed, the form is available in the associated service catalog. If the form's app hasn't been deployed, you need to deploy it.

    Remarque :
    If you published a form and then edit it, you can’t use the version that's being edited in a condition for a playbook, for example as a trigger for the automation. However, you can use the published version of the form or publish the version that you’re editing, which makes its question answers available to use in playbook conditions.