...
- If designers publish production forms/flows from their individual designer accounts and edit a production form/flow, they will be editing a live form. This does not give any source code / QA control.
- If there are multiple people designing forms in designer publishing production forms/flows from their own accounts, then your production apps/ forms/flows will be scattered around between different user accounts and it may will be more challenging to maintain them.
- The username of the user account where the form/flow is published is used in the form/flow url and you might not want the username to be known to all other form users.
- Designer users have permission to view submissions. Publishing forms in a generic production account prevents the designer from viewing production submissions.
...
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 for production or update one already in production, the designer will download the form/flow zipfile and check it into a source code repository (outside of a frevvo server).
- A frevvo.Publisher will check-out the new form/flow from the source code repository (a repository outside of a frevvo server) and upload/replace the form/flow into the generic production user account.
...