How To Publish an App:
Unpublished Apps are flagged with a yellow DRAFT icon and are not initially visible to submitters.
Publishing the app will remove the display of the yellow DRAFT flag from the top left.NOTE:
The app must be published for users/submitters to view changes.
...
Click the Publish button at the top right of the page to publish an App.
...
...
The first time an app is published, the screen below will display as you likely will not have any errors to correct.
...
Unsubmitted document drafts:
One chance to enable drafts - Document drafts can ONLY be enabled when the app is published the first time. This setting can be configured only one time.
Only on Save - A draft document is only created when the user clicks "Save." Before that, the unsubmitted form/document is only available to the submitter.
The submitter is alerted - When the submitter saves the document/form (and this feature is enabled), notification that administrators will have READ access to their content will be displayed.
...
Previously Published
If you have previously published an app and are making changes to it, the Publish page will display a summary of changes made to the draft , and any errors that need to be corrected.
...
To discard your current draft, go to the Publish screen, and click Discard Draft.
...
Form URL
Once the App has been published, click Share Form to copy the URL for posting to a website.Note: It is not advisable to direct
We do not recommend directing users to the Kuali Build Home screen to launch a form
...
because they will see a large number of applications.
...
Instead, copy the form
...
URL to an appropriate web site and direct users to
...
that website.
...
There are two options for sharing the form URL. If your form is authenticated (requires a NetID and password) or , use the top option - Shareable Link to Form. If your form is anonymous for public use without authentication, there are two options to share the form via the URL:
...
use the second option - Shareable Link to Form (Anonymous).
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Critical: You must use the “Shareable Link to Form” feature to copy the URL for use on a website or to share with someone. |
...
and not the URL for the published form. |
Versioning
Modifications to an already live application will only impact new records from the point of publish forward. Any completed records or in progress records retain the version of the form and workflow at time of submission. Any record in draft mode prior to submitting will be updated to the latest version of the form when the submitter tries to open it from their drafts.
Important Notes:
| Tip |
|---|
When publishing changes, new or removed fields will remain available to administrators in the documents/forms area. Workflow approvers will need to distinguish between versions of the form. |
| Tip |
|---|
...
Add notations on the form to indicate changes. For example, if an automated email notification on denial was not initially included on the form, but was added later, approvers would need to be aware which version of the form they are reviewing (with our without the notification) so they can take appropriate action. |
| Tip |
|---|
...
It is recommended that a duplicate of the application be made prior to the application “going live” for the first time. This will ensure that versions (including fields that have been removed) used during development/testing are discarded. Duplication is not required |
...
but is recommended to eliminate retention of old, unused fields. |
Next
...