| Section | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Create a generic production user (ex: “production@<your tenant>”) and give this user the frevvo.Designer role. All your production forms/flows will be in this user account.
Tip If you are using a non-default security manager, this step and the next step would be done via your IDP software.
- Assign the frevvo.Publisher role to one or more other users.
- When a designer is ready to deploy a form/flow/application for production or update one already in production, the designer will download the form/flow/application zipfile and check it into a source code repository (outside of a frevvo server).
- A frevvo.Publisher will check-out the new form/flow/application from the source code repository (outside of a frevvo server) and upload/replace the form/flow/application into the generic production user account.
Updating a Form or Flow in Production
...
| Info |
|---|
When a production flow that has pending tasks associated with it is edited and replaced with an updated version, pending tasks will contain the changes the next time they are "performed" from the task list. For example, let's say you
When you edit a flow and change business rule or add/remove fields, all the pending tasks pick up the latest version of the flow. Pending tasks for a form/flow that integrates with a Google sheet reflects any changes made to the Google sheet while the tasks are in-flight. |
Form/Flow designer edit ACL
The Access Control feature in allows the designer to assign other users permission to make changes to forms and flows.
| Warning |
|---|
The ability to edit a Form/Flow should not be given to other users if the form/flow is in production. Giving this permission would enable those users to edit your production forms directly thereby subverting the best practices described in this guide. |
Multi-Tenant Scenario
Development Tenant
...