...
...
...
...
...
...
...
...
How
...
To Publish an App
...
Until you publish your app and as long as the yellow Draft flag is visible at the top left of the screen within the app, any changes you have made to your app will not be visible to submitters.
...
:
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.
...
If this is your NOTE: The first time publishingan app is published, more than likely you won't have any errors to correct, and you will see a screen similar to the picture below:
OR
NOTE: The first time an app is published, the screen below will display as you likely will not have any errors to correct.
...
Some notes on unsubmitted drafts:
One chance to enable drafts - You can only enable document drafts at the first publish of an app. This is a one-time decisionDocument 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 is only created when the user clicks "Save." Before that, the document doesn't exist to anyone but unsubmitted form/document is only available to the submitter.
The submitter is alerted - When the submitter saves the document/form (and this feature has been enabled for an app, the submitter is notified when they go to save the document. This lets them know that administrators will be able to read their contentis enabled), notification that administrators will have READ access to their content will be displayed.
Previously Published
If you have previously published your an app and are making changes to it, the Publish page will display a summary of changes you have made to this the draft, and it will show any errors that need to be corrected.
...
Until all errors are resolved, you will be unable to publish your appAll errors will need to be resolved prior to publishing the app again.
...
How
...
to delete
...
a draft without publishing
...
:
Undesired changes can be removed from the app while in Draft Mode , you can simply discard the draft and start over without your users ever knowingby discarding the draft. Users will be unaware that changes were made.
To discard your current draft, go to the Publish screen, and click Discard Draft.
...
Form URL
Once you publish you can click on the option the App has been published, click Share Form to copy the URL for posting to a website.
...
There are two options depending Depending on whether or not your form is authenticated (requires NetId NetID and password) or anonymous for public use without authentication., there are two options to share the form via the URL:
...
Important Note:This is the only way to get the
...
URL for the blank form.
...
Bookmarking a blank form
...
(from the browser) will store a DRAFT copy of the form
...
; 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:
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.
User Tip: Before going live with your application for the first time, it is recommended that you duplicate your application so that any versions (including removed fields) that were 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 note that is recommended to eliminate retention of old, unused fields will be retained unnecessarily.).