New Features:

•  Redesigned User Interfaces:  

  • Redesigned Form and Document Action Wizard UI

    • More intuitive names for file type options in all frevvo wizards

    • Control names now referenced in all frevvo Wizards instead of labels

  • Redesigned more intuitive Form Designer canvas

  • Ability to edit the Flow Step name in the Edit Step Properties wizard
  • New Form steps added to a flow are automatically named "Step #' and the form name is set to "Form #" while pulling an existing form into a flow names the step "Step#" but retains the original name.
•  Visual Rule Builder 
  • Rule enable checkbox moved to Rule Editor Canvas
  • Rule Editor is now automatically expanded when you create a new rule. It is no longer necessary to click the pencil icon to define the rule.
    
    
• Non Default Security Managers
  
  • Redirect to tenant's SAML URL if logging into a SAML tenant with frevvo normal login URL
  • Warning message on the Manage Users page to remind the tenant admin that user changes made on this page will be overwritten when the user logs in. The tenant admin will see this message for SAML Security Manager tenants configured for Discovery mode (Authentication Only not checked)  
  • New built-in admin URL for all non-default Security Managers including LDAP  
  • Configured built-in admin id now shows on the SAML & Azure Edit tenant page
    
    
• Form Styling Improvements:
  • Make custom JavaScript available to all designers in your tenant.
  •  Using custom fonts in the Message control markup 
  • Adding custom fonts to the Message Control Rich Text Editor
    

• Changes to passwords and the CSV upload

  • Tenant admin can select password expiration for users by checking the "Change Password on next login" option
  • Last used password is not allowed when changing password.
  • CSV Upload now has an option to send an email to create a password if a user does not have one
  • New user now receives an email with their frevvo id and password when added to tenant via the CSV Upload. Users added manually do not receive this email.
  • Passwords are no longer supported in CSV upload and will be ignored. Translation File:
    • Reorganized translation file entries into functional groups
    • Rule related strings grouped together in the translation file
• Default Spaces:

  • Ability to select a default space. Task perform links will render in the default space if selected

  • Default Space displays on the View Configuration screen

• Renaming a flow in production retains the original flow name for the submission in Reports and on the Task List. New submissions will show the updated flow name.
• Progress indicator for form loading when clicking the Perform icon, the Task List Search Magnifying icon or the Submit button on a Task List search
• Warning message if the user did not check the Replace checkbox when replacing a form/flow with an id that matches an existing form/flow
• Operational Reports are now available to non admin users
• Forms/Flows using the f-submit-error css class and Message controls to warn users about invalid controls are automatically hidden when the form/flow becomes valid
• Tenant/flow admin email notifications now contain the application form/flow name and error to easily identify the submission that did not reach it's destination
• Tenant/flow admins no longer receive an email if submissions are created while the Refresh Searchable Fields process is running.
• There is a 60-second batch delay when running Refresh Searchable Fields.
• New ComboBox property to allow only valid values that match available options

• "Cc" field added to task notifications, escalation reminders and escalation notifications to specify a list of email addresses

• Changes to workflow behavior for steps that are routed to a role, user or an email address (Task Boundaries). Tasks are created on the user's Task List if the user is eligible to perform the next step.

• Task assignment to role sends a single Task Notification email to all users belonging to that role.

• Unlimited mappable fields in Filesystem Connector wizard

• Improved template validation. A warning message displays in the designers if a template control was renamed/deleted

• Requires/Supports Java Open JDK 11

• Click anywhere in the signature panel for a Signed Section to sign.

• Custom option to add role and user support for the "Who can start the flow" permission on the Access Control List

• Label name in the PDF Mapping UI are no longer truncated in the tooltip

• Updated Error Message on Upload Forms/Flows to reinforce best practices

• Detect/log warning message when single formtype has more than one _types.xsd 
   

• Features Removed:

  • The "Close Window" Form Action wizard has been removed from frevvo

  • The box connector is no longer supported by frevvo 
    

frevvo is committed to making  more intuitive and easier to use. More features/improvements are coming in future releases.

Features Introduced in Prior Releases (In-House Customers)

var Text_start_index = Repeat1794.itemAdded ? Repeat1794.itemIndex : 0;
var Text_end_index = Repeat1794.itemAdded ? Text_start_index + 1 : Text.value.length;
var event = form.load;
for (let i = Text_start_index; i < Text_end_index; i++) {
 if (Text[i].value && Text[i].value.startsWith('a')) {
 Repeat1794.visible = true;
 }
} 

We recommend that you read the information below before you begin.

Automatic Upgrade for frevvo Online (Cloud Hosted) Customers

frevvo Online cloud hosted customers will be automatically upgraded on 8/10/2019. The automatic cloud upgrade will be seamless. Cloud customers should review these topics to prepare for the new version of .

•  Migration Considerations   

If you have any questions, please email support@frevvo.com.

Migration Considerations

Java/OpenJDK

 v9.0 was certified with JDK 11 (11.0.2) - OpenJDK. The cloud server will be upgraded to OpenJDK 11 with this release. In-house customers must upgrade to JDK 11 before upgrading to  v9.0.

Set up Form/Flow Properties with Helpful Wizards

The new Form/Flow Properties User Interface (UI) is intuitive and organizes logical groupings of related properties on individual tabs. Click the Edit Form/Flow Properties icon in the toolbar at the top of the Form/Flow work area to access the Properties Wizard. The Properties Navigator on the left side of the work area provides a quick view of the important settings for a form or flow. Clicking in a section of the Properties Navigator takes you directly to the tab within the Properties Wizard. Hover over any field on any tab for a helpful hint about the property. Links to the documentation are also provided. 

Form Actions and Document Actions included in Form/Flow Properties wizards

Form/Flow Actions and Document actions are now set up on tabs in the Edit Form/Flow Properties Wizard. Simply access the wizards by clicking on the Edit Form/Flow Properties icon in the toolbar of the designers.

Click the Form/Flow Actions tab to set up what the user sees when the form/flow is submitted. Click the Document Actions tab to specify what happens to the data when the form/flow is completed.

Helpful Tours on the Flow Step Properties Wizard

Click the Help icon at the top of any Flow Step Properties tab for a quick tour of the features in that section. Currently, tours are only available for Cloud customers.

Workflow Task Design Considerations

In prior versions, some workflow behavior was determined at run-time (rather than design-time) based on the user performing a step and the step assignment. It was hard for the designer to predict workflow behavior because of the possibility of different combination of users/assignments that may result in a screenflow vs. a standard workflow. 

In v8.0 and prior, these errors in flow design would be apparent in certain use cases such as:

1. The second step (i.e. Manager Approval) on a Vacation Request workflow was set to the template reports.to() which resolved to a manager's name. If the manager user was not configured correctly so that this template resolved to null, the user who performed the first step would automatically get a screenflow for the next step and could approve their own vacation request.
2.  A company used a launcher form to launch another flow, such as a budget request, by sending the first step of a flow to a specified user's task list. If the first step was a template that resolved to the same userId of the person running the launcher form, it would become a screenflow rather than putting that step on their task list. 
3. A Sales Order Form used the Anonymous Step feature to send an order form to a client. The salesperson wanted to access the task and reject it back to the first step to make a correction, but if the salesperson performed the anonymous step, that step would become a screenflow and the the reject button was not enabled. 

In v9.0, the designer now defines workflow behavior at design time using task boundaries. Task boundaries are created by setting assignments (user, role or email address), so each flow step with an assignment is considered a new task. Any subsequent flow steps without assignment are considered part of screen flow of the same task. This diagram illustrates how designers can manage task boundaries and workflow behavior:

Screenflows

To preserve the convenience of a screenflow, if the next step is a new task and the current user is eligible to perform it, a message will appear with a link to continue the flow in the same screen. When the user clicks the link provided, the flow will continue like a screen flow but a new task will be created behind the scenes. 

When navigating back using the navigation bar, consecutive unassigned tasks in a screenflow will be available to edit. Once a user has moved on to a subsequent assigned step, all prior steps will be read only.

When a task that is routed to templatized user, role, or email resolves to null or empty string, instead of becoming a screenflow, the task will now be assigned to the "invalid-task-assignment" userId and a notification with be sent to flow admin users (or tenant admin user if no flow admin is configured.) This will enable flow admin users to easily search mis-routed tasks assigned to the "invalid-task-assignment" userId and re-assign to valid user.

Considerations for "Task for First Step" Flows

The Task for First Step property was removed from the General Settings tab of flow properties.

• Having an assignment to a flow step strictly enforces the task boundary and it is applicable for the first step of flow as well. This means to create a task for the first step there is no need to explicitly configure the Task for First Step property. Instead, configure the first step with an assignment.

• Designers can now define flow level Access Control by selecting Custom in the Who can start the flow property and entering user(s) or role(s).
  
  

Invalid Task Assignment

For workflows created in v9.0.x and later, when a task that is routed to a templatized user, role, or email resolves to null or empty string, the task will be assigned to the "invalid-task-assignment" userId and a notification with be sent to flow admin users (or the tenant admin user if no flow admin is configured.) This will enable flow admin users to easily search mis-routed tasks assigned to the "invalid-task-assignment" userId and re-assign to valid user.

Migrating Existing Flows

Existing flows with an assignment at the first step to control Who can start the flow will be automatically migrated to Access Control during the upgrade process to v9.0. 

• If Task for First Step was set to false (unchecked) and there was a user or role(s) assigned to the first step of the flow, then the assignment would come off the first step and move to the Who can start the flow custom permission.

• If Task for First Step was set to true (checked) and there was a user or role(s) assigned to the first step of the flow, then this would be considered as a valid assignment and there will be no change.

• If Task for First Step was set to true (checked) and there was not a user or role(s) assigned to the first step of the flow, then this will no longer be a task for first step flow. It will be a normal flow.

• If Task for First Step was set to false (unchecked) and there was not a user or role(s) assigned to the first step of the flow, then this would be considered as normal flow and there will be no change.

Changes to passwords and the CSV upload

Tenant Admins can expire passwords by checking Change Password on Next Login on the Edit User page. Tenant Admins can also update current users or add new users by uploading a CSV file. For security, the CSV file does not include a password column.

Setting notifyIfNewUser to TRUE causes  to send an email notification to the user prompting them to create a password. The defaults setting for notifyIfNewUser is FALSE, which allows Admins to set up users without passwords initially, and notify them to create passwords later.

• Set notifyIfNewUser to TRUE to send new users and current users without a password an email to create a password. Current users who already have a password will not receive a notification, even if notifyIfNewUser is set to TRUE.
• Set notifyIfNewUser to FALSE to not send an email notifications.

Users added manually will not get an automatic email prompt, but can be required to update their password on next login. This is by design to allow Admin users to add users prior to production, and then notify them to update their password later.

Uploading Users via the API

Box Connector

The box connector is no longer supported for . 

Microsoft Edge Browser

The Form Properties and Flow Properties windows are slightly slower to load on the Microsoft Edge browser than other browsers. This will be the case until Microsoft releases a version that supports custom elements and shadow DOM natively (date TBD).

Drag and Drop Enhancements

Enhancements to the drag and drop feature include increased padding around controls making the available drop space more intuitive, and allowing controls to be dropped into a section in the available space on any side of existing controls. When dragging a control to the design canvas,  will recognize the nearest control and prioritize placement to the right or below that control. The left side and top are also available by dragging the control in those directions.

On-premise Database and Filesystem Connectors for Cloud Tenants

Cloud customers running the Filesystem and Database connectors behind their firewall do not have to upgrade immediately.  The existing JDK/connector(s) will continue to work with v9.0 for a limited time. 

• Plan to upgrade your in-house JDK and connector(s) at your earliest convenience.
• Remember to:
  • Upgrade the server running the connector(s) to the supported version of Java OpenJDK
  • Use the recommended version of the connector(s) listed in the Release Notes.

Tomcat and Insight Server version Upgrades

The version of tomcat has been upgraded to 9.0.19 in the frevvo Cloud.

The version of the Insight Server has been upgraded to Solr 7.5.0 in the frevvo Cloud. Server functionality remains the same.

Internationalization Improvements

With the new  UI, several significant improvements were made regarding text externalization localization.

• Previously, all externalized text was found in the "default" file located in WEB-INF/data/locales. The "default" file remains. However, there are now several new file for specific areas of the application. The names of these files is intended to indicate the area for which the file contains externalized text strings:

  • form-designer-properties

  • flow-designer-properties

  • flow-designer-step-properties

  • rule-builder

  • frevvo-ui (currently covers the template install dialog)

• The scheme for placing locale-specific (language-specific) files into the WEB-INF/data/locales folder is similar to before. The "default" file is still copied and named "some-locale". The scheme for the other files is similar except that the locale is pre-pended onto the file. For example for french, "form-designer-properties" becomes "fr-form-designer-properties". Note that all 6 files are required for each locale in order for this to work properly. For example for french (fr), you must place the following files into WEB-INF/data/locales, even if not all of them are translated:

  • fr

  • fr-form-designer-properties

  • fr-flow-designer-properties

  • fr-flow-designer-step-properties

  • fr-rule-builder

  • fr-frevvo-ui

• The way that locale/language is determined at run-time is unchanged from before. It may be set in the browser properties (preferred language) or using the locale=parameter on the form/flow type share URL (either edit or use mode)

Refer to Creating Runtime and Design-TimeTranslations for more information.

Control Options/Dropdowns in Wizards

The control dropdowns in the Sharepoint and Filesystem Connector Wizards now display control names (not labels.) The Searchable Fields and Saved Fields properties also display control names (not labels) in the Available Fields column. Hovering the cursor over a field name will display a tooltip that includes the control's section as well for clarity when multiple controls have the same name. This enhancement is consistent with other wizards throughout  and will increase accuracy and clarity when selecting controls.

Admin Warning for SAML Discovery Tenants 

Tenants using a SAML Security Manager in discovery mode (with "Auth Only" unchecked) should not edit users or roles from the Manage Tenant page because changes made this way are temporary. The next time the user logs in the user will be re-synced via discovery -- deleted roles will be added back (if the user has them) and the user will be updated (roles added by admin will be deleted and roles deleted will be added back). In v9.0, a warning message will appear on the User List to alert the admin that they are in discovery mode and should make permanent changes in their IDP instead.

Adding a Rule

In prior versions, when adding a new rule the designer had to click the pencil icon to expand the rule properties. Now, when adding a new rule, the rule properties will automatically expand giving the designer quick access to the rule name, description and Visual Rule Builder.

Rule Enabled Checkbox in Collapsed View 

The Enabled checkbox is now visible and accessible when rules are in collapsed view. This allows the designer to quickly enable/disable rules without editing/expanding each one.

Failure Notification for Doc Actions

E-mail notifications to form/flow admins upon Document Action failure will now include additional information to help the user identify the form/flow that is has a failure in order to correct it. Doc Action failure notifications will now include form/flow name, tenant, designer, and application.

Workflow Step Automatic Naming 

New and Existing Forms added as workflow steps are automatically named "Step #." Dragging a New Form into the flow designer sets the step name to "Step #" and the form name to "Form #". Dragging a form that was previously created in the form designer sets the step name to "Step #" and leaves the form name unchanged. Use the pencil icon on the step to access the step Properties Panel and rename the step(s). 

Email Option Enhancements

'CC' Functionality 

In prior releases, the doc action Email allowed email submissions to multiple addresses, CC and BCC. In v9.0, the 'CC' functionality extends to workflow Task Assignment, Escalation Notification, and Escalation Reminders. This feature enables the designer to specify a 'CC' email which is useful in the following scenarios:

• A task is assigned to an anonymous user, but the user does not get the task (due to a bounced email, or the user never opened the task.) In this scenario, the cc'd user/role can "grab" the Pending task and reassign or resend it.
• Notifying a manager that a task has been sent to a new sales rep in training, so the manager will be able to monitor the trainee's tasks and follow up.
• Notifying a second party for escalations to ensure follow up at this stage of the flow.

Single Email vs. Multiple Emails

In prior releases, scenarios that required emailing multiple users (such as assigning a task to a Role that multiple Users have) would send separate emails to each user in the list. In v9.0, these scenarios and the 'cc' functions described above will trigger a single email to be sent to all intended recipients. This will provide more efficient use of system resources and speedier processing.

Template Validation

Template references used in  will be automatically validated when the form/flow is first migrated from an earlier version into the v9.0 version, upon upload of a form/flow and upon saving a form/flow. If there is a previously existing typo in the control name, or if the control doesn't exist, then that template will have a validation error to alert the designer to the errors and guide the designer to correct them. Forms and flows with validation errors appear in the list of forms/flow with a pink/salmon background. This warning is non-fatal and will still allow the form/flow to run.