...
Create test roles and users in your development tenant. If you are using the default security manager, simply create the test users and roles in the tenant. Refer to this topic below if you are using the LDAP/Active Directory 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.
- Assign the frevvo.publisher role to one or more users on tyour pproduction your production server.
- One of the users with the frevvo.Publisher role will check-out the new application from source code (a repository outside of a frevvo server) and upload/replace the application into the production tenant.
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 user account in the production tenant.
The tenants on your development and production servers may have the same name although this is not required.
...
- The frevvo superuser can easily create both tenants for In-house customers.
- Cloud customers must purchase a second tenant for production.
Separate development/test tenants is recommended for the following reasons:
- The role names in your development tenant contains test users with test email addresses so that workflow notification does not impact/spam real company employees
- Test submissions will not be mingled with production submissions.
Publishing Forms/Flows from Development to Production
We recommend that the forms/flows be created by one/multiple designers in their own accounts in the development tenant. After the forms are designed/tested, they can be downloaded from the individual designer user accounts and uploaded to a generic special user account (ex: “formuser”) where the forms can be published.
Separate development/test tenants is recommended for the following reasons:
...
.
...
We recommend using a generic special user account to publish apps/forms/flows in your production tenant for the following reasons:
...