Assign use when publishing workflows and forms
This topic describes the concept of assigned use in the context of subscription licensing.
If your farm uses a subscription license, then you must specify assigned use when publishing workflows and forms in accordance with subscription licensing terms.
Assigned use options are as follows.
-
Development: Intended for the development phase; the workflow or form does not operate on or affect any business outcome or data outside testing and development. Watermarks appear on development workflows and forms as well as on email messages sent by workflows. (Form preview omits the watermark.)
Example: Running an expenditure approval workflow generates a request for purchase of a notebook computer and that request is approved, but no purchase occurs because the workflow is being tested.
-
Production: Intended for the production phase; the workflow or form operates on or affects live business data.
Example: Running an expenditure approval workflow generates a request for purchase of a notebook computer and that request is approved such that the notebook computer can be purchased.