Versions Compared

Key

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

...

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

  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.

    Image Added

Updating a Form or Flow in Production

...

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

  2. Multiple designer users can create and test forms/flows in each of their user accounts using the test users and roles.
  3. 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.
  4. 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. 

...