Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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.

  2. Multiple designer users can create and test forms/flows in each of their user accounts.
  3. 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.
  4. Create a generic production user account (ex: “formuser” or whatever you want to name it) 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.

  5. Assign the frevvo frevvo.Publisher role to one or more other users in your production environment.
  6.  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.

  7. 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.

...

  1. Create a generic production user (ex: “formuser” or whatever you want to name it) 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.

  2. Assign the frevvo.Publisher role to one or more other users.
  3. 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.

...