...
- 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/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 (a 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
...
Create test users in your development tenant. If you are using the default security manager, simply create the test users in the tenant. Refer to this Customers using the LDAP/SAML/Azure Security Manager below if you are not using the default security manager.
Tip The role names in your development tenant should be the same as the role names in your production tenant. If they are different, modifications to your workflows will have to be made to users and workflows to reflect the production roles.
- Multiple designer users can create and test forms/flows in each of their user accounts using the test users and roles.
- The designer users will download a finished and tested application and check it in to a source code repository (versioning) as the new version of the application. Ex: SVN, CVS, Google drive.
When further updates/modifications are required, the forms/flows should again be edited in the designer user accounts and then upload/replaced in the generic production user account.
...
- The only way to guarantee the same behavior for both tenants is to configure both with the same security manager.
- Each tenant should point to it’s own instance of your security manager.
- For example if you are using LDAP, a development LDAP domain with a set of LDAP groups that are EXACTLY the same as your production LDAP domain is suggested. This way flows can be moved from your development tenant to your production tenant and workflow navigation w/roles is guaranteed to work correctly.
- The generic production user account (ex: "production@<your tenant>production") must be created in your IDP (LDAP, Azure, SAML).
...