...
Create roles and users in your development environment. If you are using the default security manager, simply create the users and roles in the tenant, otherwise refer to customers using the LDAP/SAML/Azure Security Manager.
Tip The role names in your development environment should be the same as the role names in your production environment. If they are different, modifications to your workflows will have to be made to users and workflows to reflect the production roles when they are moved to the production.
- Multiple designer users can create and test forms/flows in each of their user accounts.
- These designer users will download a finished and tested application and check it in to a source code repository (a repository outside of a frevvo server) as the new version of the application. Ex: SVN, CVS, Google drive.
Create a generic production user account (ex: “formuser” or whatever you want to name it“production@<your tenant>”) in your production environment 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 in your production environment.
When a designer is ready to deploy a form/flow to production or update one already in production, a frevvo.Publisher will check-out the new application from source code (a repository outside of a frevvo server) and upload/replace the application into the generic production user account in your production environment.
- Step 6 can be performed by the tenant admin or your generic production user if you prefer not to create users with the frevvo.Publisher role.
...
- Test roles & users allow your designers to test workflow email notifications and workflow task navigation without spamming real users' email inboxes and task lists.
- When a form/flow is in development you may consider:
- Temporarily switch the form/flow configuration to use your test roles and users.
- Temporarily turn off Show in History to prevent test forms/flows from cluttering production Task History Search.
- Temporarily turn off Who can view and/or edit submissions ACL to prevent test forms/flows from cluttering production Shared Items / Submissions, or switch the ACL to your test roles and users.
- When your form/flow is ready to deploy to production switch the roles/users from your test roles/users back to your production roles/users, and if desired re-enable task history search and view/edit submissions ACL.
- Follow the detailed steps below for Publishing Forms/Flows from Development to Production and Updating a Form or Flow in Production noting that your generic production users account (ex: "formuserproduction@<your tenant>") will be in the same tenant as your designer's user accounts.
...
We recommend that the forms/flows be created & tested by one/multiple designers in their own accounts. After the forms are designed/tested, they can be downloaded from the individual designer user accounts and uploaded to a generic production user account (ex: “formuser”) “production@<your tenant>" where the forms can be published and used by your end users.
...
Create a generic production user (ex: “formuser” or whatever you want to name it“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 frevvo.Publisher will check-out the new application from source code (a repository outside of a frevvo server) and upload/replace the application into the generic production user account.
...
- Create a generic production user account that has the frevvo.designer role (ex: “formuser” or whatever you want to name it“production@<your tenant>") on your production tenant to which you publish all forms/flows.
- Assign the frevvo.publisher role to one or more users. These users have permission to upload new versions of your applications to your production user formuser account.
- 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 generic production user account
...
If you are testing in a multiple tenant scenario and , we recommend that both your dev/test and production tenants are configured with the same security manger. This is recommended for the following reasons:
- 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: "formuserproduction@<your tenant>") must be created in your IDP (LDAP, Azure, SAML).