Stay updated with Workflow Automation releases

Updates to the Nutrient Workflow Automation Platform typically occur every other Tuesday, although they may happen more or less frequently. All changes to the application are documented on this page.

The "Estimated Release" section highlights application changes that are either undergoing QA procedures or have passed QA but have not yet been released to the production environment. Most of these changes are expected to be included in the next production push and are estimated to go out on the date listed. However, the schedule is subject to change if urgent releases or fixes require prioritization or there are unforeseen delays.

If you have any questions about these updates, contact the Workflow Support Team.

Workflow 25.1.1 - 1/16/2025

Changes/Improvements

Add option to REST Client tasks to replace unsupported request method

Ref: WORKFLOW-38

Previously, the REST Client task type utilized the request library for API calls.

With this release, users can now switch to the fetch API in the task configuration. New tasks default to fetch, while existing tasks will continue using request unless manually updated. Some complex configurations may require adjustments when transitioning to fetch.

Additionally, the request library has been replaced with fetch internally across the application to address Server-Side Request Forgery vulnerability GHSA-p8p7-x288-28g6.

Fixes

Grids no longer allow blanks in required columns during submission

Ref: WORKFLOW-103

Previously, users could leave required Select List or Attachment columns blank and still submit the form.

With this release:

• Blanks in required Select List columns are no longer permitted during submission.

• Required Attachments columns display a red border when left blank.

• Entering 0 in a Number column is now correctly treated as a valid value rather than empty.

Grid’s ‘Show Label’ option now displays grid label and ‘Help’ icon correctly

Ref: WORKFLOW-105

Previously, selecting the Show Label option for a grid failed to display the grid label and associated Help icon.

With this release, the issue is resolved. When the Show Label option is selected, the grid label now appears above the grid at runtime or in completed forms, and the Help icon is displayed if Help text is configured.

Related ad-hoc launch requests now appear in Request Details

Ref: WORKFLOW-106

Previously, when a request was started via the Launch Related Request button, neither the newly created child process nor the parent process appeared in the related request section of the Request Details.

With this release, the issue is resolved. Related ad-hoc launch requests now correctly show up as related requests in the Request Details section, improving traceability and visibility.

Dashboard sizes now display correctly when adding a widget

Ref: WORKFLOW-108

Previously, when adding a new widget to a dashboard, the available display sizes in the drop-down menu would not appear unless the browser was resized.

With this release, the issue has been resolved. Dashboard sizes now display properly in the drop-down menu without requiring browser resizing.

Patches

• Ref: WORKFLOW-37: Versions of the tough-cookie package before 4.1.3 were vulnerable to Prototype Pollution when using CookieJar in rejectPublicSuffixes=false mode GHSA-72xf-g2v4-qvf3. The issue stemmed from improper handling and initialization of cookies. With this release, the vulnerability has been patched by upgrading to a secure version of the tough-cookie package.

• Ref: WORKFLOW-54: Improper validation of cookie name, path, and domain allowed the use of out-of-bounds characters, which could be exploited to alter other fields of the cookie. For instance, this could lead to unexpected values being set for cookies, potentially enabling attacks like XSS
  GHSA-pxg6-pf52-xh8x. With this release, the vulnerability has been patched by upgrading to version 0.7.0, which includes enhanced validation. As a workaround, applications should avoid passing untrusted or arbitrary values for these fields.

• Ref: WORKFLOW-48: Addressed GHSA-2vrf-hf26-jrp5 where all versions of Angular were vulnerable to Regular Expression Denial of Service (ReDoS) through the angular.copy() utility function due to an insecure regular expression. With this release, the code has been adjusted to mitigate this vulnerability, enhancing the security of applications using Angular.

• Ref: WORKFLOW-47: Resolved GHSA-5359-pvf2-pw78, an XSS vulnerability in TinyMCE’s content loading and inserting code. This issue allowed malicious SVG images to execute harmful scripts when loaded through object or embed elements. With this release, a patch has been applied. Enabled by default in TinyMCE 7.0.0, it requires manual activation for users of TinyMCE 6.8.1 or earlier.

• Ref: VULN-352: Fixed session cookie vulnerability CWE-614 where not setting the “Secure” attribute on session cookies could have allowed for session hijacking. With this release, the “Secure” attribute has been set on all session cookies, ensuring they are only transmitted over HTTPS, mitigating the risk of session hijacking.

• Ref: VULN-353: Fixed version information disclosure in HTTP response headers Hide Your NGINX Server Version vulnerability where exposing version information in HTTP response headers can allow attackers to target the system more effectively. By knowing the exact software version the server is running, an attacker can research known vulnerabilities specific to that version.
  With this release, we have removed platform-specific information from HTTP response headers, resolving the vulnerability. For NGINX servers, the server_tokens directive has been set to off in the nginx.conf file to prevent disclosing version details.

Workflow 25.1.0 - 1/7/2025

Fixes

Non-editable file attachment question in a grid caused form submission failure

Ref: WORKFLOW-83

Previously, if a grid contained a non-editable file attachment question, users encountered an unknown error pop-up and were unable to submit the form or add a row.

With this release, the issue has been resolved and users can now successfully add rows or submit forms containing such grid columns.

Patches

Ref: WORKFLOW-34: Resolved Prototype Pollution vulnerability in JSON5 via its Parse Method GHSA-9c47-m6qq-7p4h by updating the package and changing our code to work around it.

12/16/2024

Fixes

Read-only grid questions do not respect a defined column width

Ref: WORKFLOW-62

Previously, the read-only grid component allowed cells to expand to fit their content, which caused the rest of the form to shift and disregarded users’ defined column widths.

With this release, the behavior has been adjusted to ensure that defined widths are respected.

Set Recipients doesn’t work from Manage Tasks when there is a complex notification

Ref: WORKFLOW-66

Previously, issues with certain notification settings caused recipient assignment to fail, and file inclusions further exacerbated the problem.

With this release, the issues are fixed ensuring both cases no longer result in failures during recipient assignment.

Patches

• Ref: WORKFLOW-22, WORKFLOW-24: Patched Arbitrary Code Execution vulnerability GHSA-67hx-6x53-jw92 in Babel during compilation of malicious code by changing our code to work around it.

• Ref: WORKFLOW-23: Patched Arbitrary Code Execution vulnerability in underscore GHSA-cf4h-3jhx-xvhq by updating the package to a secure version.

• Ref: WORKFLOW-25: Fixed Prototype Pollution issue in webpack loader-utils GHSA-76p3-8jx3-jpfq by upgrading to a patched version.

• Ref: WORKFLOW-26: Patched Regular Expression Denial of Service (ReDoS) vulnerability in cross-spawn GHSA-3xgq-45jj-v275 by updating the package.

• Ref: WORKFLOW-36: Mitigated Remote Code Execution via the pretty option in JSON5 GHSA-p493-635q-r6gr by updating the package and changing our code to work around it.

• Ref: WORKFLOW-65: Patched Mongoose Search Injection vulnerability GHSA-m7xq-9374-9rvx by updating the package and sanitizing MongoDB query routes.

12/09/2024

Changes/Improvements

Add preview icon to grid question attachment columns

Ref: WORKFLOW-59

Previously, in runtime mode and the completed form view, there was no preview icon available for attachments within grid questions.

With this release, a preview icon has been added to grid question attachment columns. This enhancement improves usability by allowing users to quickly preview attachments within grids, both in runtime mode and the completed form view.

Fixes

Issue with recipients assignment and tasks completion

Ref: WORKFLOW-60

Previously, on the Set Recipients page, the recipients included three entities: the requester, a single user, and a group (containing a single user), all of whom were required for approval. However, during process execution, only two users were being assigned, and one of those assigned appeared without a name. This issue created discrepancies, as the task displayed three recipients, but the assignment details were incorrect.

With this release, recipients are now correctly assigned and displayed in the Request Details, ensuring accuracy and reliability in task assignments and approvals.

Unable to submit form when a row is added to grid

Ref: WORKFLOW-61

Previously, users encountered an issue when submitting a form task that required adding data to a grid. If a user added a row to the grid and attempted to submit, they received an “Unknown Error” pop-up in the browser. In developer tools, this corresponded to a 500 error with the following message:

Cannot read properties of undefined (reading ‘Answer’)

However, if users refreshed the page and submitted the form without adding a row to the grid, it would submit successfully. This behavior disrupted workflows and caused confusion.

With this release, the issue has been resolved. Users can now add rows to the grid and submit the form without encountering pop-ups or error messages.

Patches

• Ref: WORKFLOW-21: Patched jsonpath-plus Remote Code Execution (RCE) vulnerability GHSA-pppg-cpfq-h7wr/CVE-2024-21534 by changing our code to work around it.

• Ref: WORKFLOW-63: Patched Mongoose search injection vulnerability GHSA-m7xq-9374-9rvx/CVE-2024-53900, ensuring complete protection against the issue across all repositories.

While the patched version for this vulnerability is 6.13.5, it was addressed across all repositories except for the client, which continued to exhibit the Mongoose search injection vulnerability.

12/03/2024

Fixes

Prefilled grid attachments marked as deleted on subsequent submissions

Ref: WORKFLOW-57

Previously, prefilled grid questions with attachments were incorrectly being marked as deleted. As a result, users encountered errors when attempting to download these attachments.

With this release, attachments are now automatically undeleted during processing, ensuring they remain accessible. Users will no longer face errors when downloading attachments from grids.

Task History section not displaying for some requests on the request detail page

Ref: WORKFLOW-58, HT-21348

Previously, certain requests would occasionally return null recipients. As a result, users were unable to view the Task History section of the Request Detail for those specific requests.

With this release, the system now ensures that null recipient data is handled correctly, preventing errors. Users will be able to see the Task History table on the Request Detail page for all requests without encountering any issues.

12/02/2024

Changes/Improvements

Grid questions rendered as plain text in email notifications

Ref: WORKFLOW-56, HT-21302, HT-21307

Previously, grid questions included in email notifications were being rendered as JSON, making them difficult to interpret and reducing the clarity of the information.

With this release, grid questions are now displayed as properly formatted tables within email notifications, ensuring better readability and a more user-friendly presentation. This improvement enhances the overall experience when reviewing grid-related information in emails.

Fixes

“Set Recipients” option missing in reports with the “Manage Tasks” column

Ref: WORKFLOW-16, HT-21227

Reports containing the Manage Tasks column encountered an issue where the Set Recipients action was unavailable. Regardless of a task’s status — whether Initialized or Started — the only action displayed was Reset Task, preventing users from assigning recipients directly through the report interface.

With this release, the Set Recipients action is now fully restored and functional in the Manage Tasks column of reports, allowing users to assign recipients as expected. This fix enhances task management capabilities and restores the intended workflow for affected reports.

11/27/2024

Changes/Improvements

intForm.requestSid missing for completed forms in certain contexts

Ref: WORKFLOW-18

Previously, the intForm object did not include the requestSid for completed forms opened from an Approval Task. While the requestSid was available for runtime forms, its absence in completed forms caused inconsistencies for users as they had to search multiple locations to retrieve the requestSid, leading to unnecessary complexity when using scripts.

With this release, the requestSid is now consistently included as an intForm object property for all states of a Workflow form, including completed forms. This update streamlines script usage by ensuring uniform access to the requestSid.

Fixes

Enhanced file security with new file access locking functionality

Ref: 2916

Previously, all authenticated users in the system had default access to files, regardless of their object permissions. This broad access posed potential security concerns, as file availability did not align with the more restrictive object permissions that may have been set.

With this release, a new functionality has been introduced that allows file access to be locked and aligned with object permissions. This ensures that only users with the appropriate permissions for a specific object can access its associated files.

How to Enable: Activate this functionality by enabling the new system setting, EnableFileSecurity. Once enabled, file access will follow the security rules defined by the object permissions, providing an added layer of control and enhancing overall file security.

Issues with mapping grid question footer data resolved

Ref: 2931, 2945, WORKFLOW-15

Prefilling using an individual footer cell from a grid question as a source was not functioning correctly under specific scenarios, leading to errors and inconsistencies:

• Grid footer data mapping as a prefill was failing in certain situations, causing incomplete or inaccurate data population.

• For select list columns in grid questions, the mapped output to template cells appeared as a JSON string representing the entire select list, making it difficult for users to work with the data.

• If a currency column in a grid template was mapped with currency formatting and then the grid column type was changed to a non-currency type, the currency formatting logic would still run. This caused errors when accessing the non-currency column.

With this release, these issues have been resolved:

• Grid templates now prefill successfully, regardless of where the grid question data is stored.

• Select list columns in grid questions now output only the selected option value, ensuring user-friendly and useful data formatting.

• Office templates no longer fail when a currency formatting prefill exists on a column that is no longer of currency type, eliminating errors and ensuring smoother workflows.

Console error fixed when navigating away from a new request without submission

Ref: 2940

A navigation-related issue caused an error in the console when users performed the following steps:

• Selected a process with a form

• Started a new request for that process

• Navigated away from the form without submitting

• Started another request

• Submitted or saved a draft of the form for the first request

The error would occur during the last step listed above due to multiple event listeners being created inadvertently when navigating away from the initial form without submission.

With this release, multiple listeners are no longer created when navigating away from a new request without submission. Users can now submit or save drafts for subsequent requests without triggering any errors in the console.

Invalid error message removed when selecting a new PDF template in PDF Generator task configuration

Ref: WORKFLOW-17

In the PDF Generator task’s configuration screen, users encountered an invalid error message after selecting a new PDF template file. While the error message suggested that the operation failed, the underlying API call was actually successful. This feedback created confusion for users.

With this release, selecting a new PDF template in the PDF Generator task configuration no longer triggers an invalid error message. The system now accurately reflects the success of the operation, ensuring a smoother and more intuitive user experience.

11/18/2024

Changes/Improvements

Paging parameter availability added to custom reports queries and column formatting moved server-side for enhanced performance

Ref: WORKFLOW-11

Previously, reports performed client-side formatting, which could result in performance issues, especially when dealing with large datasets.

With this release, we have moved the formatting routines from the client to the server to improve performance. In addition, two new custom paging parameters are now automatically passed to custom reports for use in queries:

• @rows_per_page: This integer value is set from the report footer, specifying the number of rows selected to be displayed per page.

• @report_page: This integer value represents the current page number being requested by the reporting interface. The page number is adjusted using the navigation arrows in the report footer.

How to Use: These parameters allow for server-side paging to be implemented in custom reports where automatic paging does not function or you would like to force server-side paging. To use them effectively, add the following SQL syntax at the end of your query, after the ORDER BY clause. These parameters can also be passed to stored procedures:

OFFSET @report_page * @rows_per_page ROWS
FETCH NEXT @rows_per_page ROWS ONLY

Corrected parameter values for embedded custom reports in request detail

Ref: WORKFLOW-13

When a custom report was embedded into a request detail, the parameter @requester_sid was incorrectly passing the same value as @user_sid. This caused confusion as both parameters were not reflecting the expected distinct values for the requester and the user.

With this release, the parameters @user_sid, @requester_sid, and @request_sid are now correctly being passed to the report in the request detail.

Reduced unnecessary network calls in dashboard designer for report widgets

Ref: WORKFLOW-14

The dashboard designer was previously making multiple, unnecessary network calls to run reports when a dashboard included a report widget. This caused slower load times and inefficient use of resources, especially when accessing the dashboard designer.

With this release, we have optimized the dashboard designer’s behavior. Now, only one network call is made when accessing the dashboard designer with a custom report widget. This improvement reduces unnecessary calls and enhances the performance and responsiveness of the dashboard, making it faster and more efficient to work with report widgets

10/22/2024

Changes/Improvements

• 2923: Added Nutrient logo, favicon, and application themes.

9/25/2024

Changes/Improvements

• 2906: Added the ability for links within Link question types that are used as a Prefill in Notifications to be active/clickable.

Fixes

• 2888: If a Form question is disabled, it cannot be used in a Form rule. A fix for this has been implemented.

• 2889: The Select List question type’s width cionfiguration is not adjusting to a configured value. A fix for this has been implemented.

9/18/2024

Changes/Improvements

• 2341: When viewing a Report, the colum Headers will now remain on the top while scrolling down to view the bottom rows. (FR-16822)

• 2876: Task failures are now posted to the Notification Center for Administrators to act on.

• 2884: Titles within the Tabs of Integrify will now display the name of the page that is being viewed.

• 2901: A ‘Don’t save delete column’ option has been added to the Grid question configuration to prevent column definitions from retaining multiple deleted columns in the data stream. It is the default for new grid questions, and can be turned on for pre-existing after checking functionality of form rules and custom JS in conjjunction with it.

Fixes

• 2870: When loading a Reports Scheduler or Process Scheduler configuration, if either were configured with a User in the ‘Run As’ configuration that was changed, missing, or deactivated, the ‘Run As’ option would disappear. A fix for this has been implemented. (HT-20185)

• 2903: When Users were mapping a Grid question’s select list column in a PDF Generator’s configuration using the Grid Specific Cell configuation as the source, the resulting mapped field was missing the value. A fix for this has been implemented. (HT-20512)

• 2915: When configuring a new DB Push Task that includes the new “Which Options” drop down for grid data, the push task fails when using the “Entire Grid (JSON)” option. A fix for this has been implemented.

9/3/2024

Changes/Improvements

• 2674: Added and enhancement that gives Users the ability hide a Grid column from all users in both the question config and via JS using toggleColumnVisibilty(columnId) or setColumnVisibility(columnId, setTo). (FR-18281)

Fixes

• 2900: Fixed issue with ui length limitations on passwords that was preventing user creation in certain cases.

8/27/2024

Changes/Improvements

• 1954: Added license overage notifications to the Notification Center

• 2746, 2779, 2780, 2869, 2878, 2879: A Notification Center has been added to the application. This will be a central location for admins of the application to receive and manage notifications from the application regarding license status, overages, and updates. It is laid out similar to an email client and is accessible through a new bell icon in the upper right navigation of the application. The bell will also show the number of unread items. Users can flag, delete, and mark as read/unread any notification. (FR-14497)

• 2775: We added the ability to supply an alias for any completed form task selected for inclusion in an approval task. (FR-19238)

• 2880: Added scheduled report errors to the Notifiction Center

8/22/2024

Changes/Improvements

• 1954, 2746, 2779, 2780: A Notification Center has been added to the application. This will be a central location for admins of the application to receive and manage notifications from the application regarding license status, overages, and updates. It is laid out similar to an email client and is accessible through a new bell icon in the upper right navigation of the application. The bell will also show the number of unread items. Users can flag, delete, and mark as read/unread any notification. (FR-14497)

• 2879: A draggable Center divider between the notification list and notification viewer within the Notification Center has been added for better viewing.

Fixes

• 2776: If you change the Task Status filter of the My Tasks from the default “Open” to “All” and then change it back, the list of tasks does not display. The paging shows 0 of n, where n is the correct number of tasks. A fix for this has been implemented.

• 2867: When you have a REST Client task which uses a stored credential (such as API Key) the Test tab does not use the credential. If you’re using a credential, the Test tab should do the mapping automatically but not display the parameter. A fix for this has been implemented.

• 2869: The Badges that display on the Bell icon for the Notification Center do not automatically update when a new message is received. The User needs to manually refresh to see it. A fix for this has been implemented.

• 2874: Notifications with embedded images are not displaying for Recipients that receive thier emails outside of the Integrify system without an Integrify Token. A fix for this has been implemented.

• 2875: If a username is changed or made inactive the runas field on the report scheduler doesn’t show at all if that user was selected. If you schedule a report to start or end with a time that has 0 minutes the data saves, however when you go back and edit the schedule the start/end date time is blank. A fix for these bugs have been implemented.

• 2877: Reports with a column displaying files formatted with attachment displays the icon on its left side when it should be on the right. And Reports with a column displaying files formatted with attachment - icon don’t display a preview icon and preview. A fix for these bugs have been implemented.

8/13/2024

Changes/Improvements

• 2498: An option to bypass the login screen when using SSO has been implemented within the SSO settings under the Top right menu’s Gear icon. (FR-17449)

• 2727: When dragging or adding images into a rich text field in the application (form questions, notifications, descriptions, etc), we now save the file to the attachments file store and reference the file instead of embedding it into the data stream. This is seamless to the user and happens automatically.

• 2831: You can now map specific cells from grid questions into task prefills, parameters, variables, notifications, and start rules. For cells to be mappable, the grid question must have ‘Rows Specified’ in the ‘Rows Defined’ tab of it’s configuration. They are listed by number or 1st column values if they exist in the configuration.

Fixes

• 2761: When a User process was executed, the Grid Footer was not displaying. A fix for this has been implemented.

• 2822: When adding or moving a form, report, or process, the user is only able to select a category they have create rights to. It will not be in the list of available categoried if those rights do not exists.

• 2855: When a User Resets a task via Manage Requests, the Completion date of the previous task within the Task History is being changed. A fix for this has been implemented.

• 2860: Form IDs are no longer incrementing when a form is versioned.

8/7/2024

Changes/Improvements

• 2721: Added the ability to display a custom message on the Login Page to System Settings under “LoginMessage” (FR-18689)

Fixes

• 2854: In the task history for requests, The Office Templating task was labelling generated documents as “PDF Generated” regardles of format chosen in the configuration of the task. Also, within the Office Templating task’s Configuration>Configure Task, there a prefill section that uses a button containing named “Generated PDF Name” regardless of output type. A fix for these both has been implemented.

7/30/2024

Changes/Improvements

• 2840: normalized terminology used on the office templating task.

• 2842: Removed unnecessary and confusing options when mapping from the Credential Center

• 2845: When a user executed “Manage Requests > Reset Task” or “Redo-completions,” there was no confirmation popup to prevent accidental actions. As a result, users could unintentionally execute these actions, requiring them to redo tasks they had already completed. We removed the menu on hover, and made it appear on left click instead to support touch devices and prevent accidental execution. We also implemented a pop up that allows users to cancel the action if it was done by mistake. (FR-19925, FR-19926)

Fixes

• 2750: When removing a recipient that was delegated from a task, if a normal assignment to that same user existed it would also get removed. This no longer occurrs.

• 2826: When a User is selecting Contacts via a the Contact Search question (configured to accept multiple contacts), a previously selected Contact is automatically deleted when an additional search for a Contact has been cancelled. A fix for this has been implemented. (HT-19812)

• 2833: If a Non-Admin User has Manage permissions to a workflow, they are unable to change the dates for that workflow’s requests via Manage Requests when they should be able to. Only Admin Users are able to change dates for requests. A fix for this has been implemented. (HT-15369)

• 2835: If a User adds special characters in the Office Templating task config for prefills within the PDF name, it will result in the Task failing. A fix for this has been implemented where when adding special characters a warning message will display in red to the User informing them that those characters are not allowed. The configuration also will not be saved. (HT-19839)

• 2837: Within the Office Templating task, if a User doesn’t enter a “Name of Completed file” the task will fail. If a User enters a “Name of Completed file” but doesn’t enter a file name extension, the file will fail when downloading it from a prefilled Form.. A fix for this has been implemented where the “Name of Completed file” is required (a red box will be displayed if left empty) and if a User forgets to add an extension to the filename, one will automatically be added. (HT-19891, HT-19892)

• 2841: When previewing a User’s Signature from the User Profile screen within the Document Viewer popup, you could download the file without the required watermarks. The download and the export buttons also should not display when the viewer is used in this context. A fix for this has been implemented.

• 2844: When a User clicks on the attachment preview icon within a Completed Form, the preview does not open and an error is displayed in the browser console. A fix for this has been implemented.

• 2850: Within the Office Templating task, if a User maps any multi-option questions and chooses ‘Only Selected’ in the “Which Options” configuration, when the questions are left blank in the form at runtime, the selection status will still be TRUE in the output. A fix for this has been implemented.

7/24/2024

Fixes

• 2784: When a User starts a new request, the application isn’t displaying the proper task name iin the header. A fix for this has been implemented. (HT-19337)

• 2811: When a User does a Search within forms, it would intermittently fail with a 500 error under very specific circumstances. A fix for this has been implemented.

• 2822: The category list was not filtered by a user’s create permissions when addng or reconfiguring a form, report, or process. A fix for this has been implemented.

• 2838: Mappings from multi-answer questions to singular fields was showing the ‘which options’ dropdown. This is no longer the case.

• 2843: When saving a parameter set for a REST Client task that was beyond 4000 characters long, the application was not sending the data properly, this has been remedied.

7/16/2024

Changes/Improvements

• 1306: Users can now add a digital signature to their profile using the Signature option from the avatar menu (your initials in the upper right) You can either upload a file of your signature or use a signature pad. This signature can be passed into PDF generator tasks. (HT-11981, HT-17917)

• 2722: Credential Center - There is now a centrlal area under the gear icon to store system level credentials in a secure manner. these credentials can be used for rest cient tasks, database sources, web service tasks, and aws lambda tasks. All Database, and lambda credentials should have been converted for you automatically.

• 2732 (cloud only): you can now daisy chain PDF generator tasks by selecting previous PDF generator tasks as the template source instead of a file. This when used with the Keep editable option, allows for adding to a pdf template throughout the process (HT-18472)

• 2800: When using a number that has currency options set as a prefill, you can now prefill with the number formatted as currency or the numerical value. This should apply anywhere the prefill is an option.

• 2805: When a User deletes a Task, the task, its properties, and mappings are deleted. The transitions TO the task and any transition conditions are also deleted. Any task or configuration referencing back at that task is now left untouched, Ex. start rules, prefills, task configuration options, notification prefils, and dynamic naming. These were previously wiped out in certain cases which causes problems loading thoses task configurations.

• 2810-2826: Upgrade all images to nodejs v20 and eliminate use of all deprecated libraries.

• 2832: Added additional representations when mapping to a multi-choice question within the Office Templating Task (Ex. Yes/No, On/Off, Active/Inactive, Enabled/Disabled, Visible/Hidden…) Including a custom representation which allows the User to enter custom text to be used.

Fixes

• 2459: If a User has a Form task that uses a DB Pull task for prefills, and then you delete the DB Pull task (because you can’t remove mappings, for example), you can then no longer open the configuration of the Form Task. An empty dialog opens and there’s no way to close it without refreshing the page. The task then has to be deleted and re-created. A fix for this has been implemented. (HT-18837)

• 2460: If a User has a Dynamic Assigner which references a Form task in the Query Parameter mappings, and that Form task is deleted, the User can no longer access the Query Parameters. An error is generated in the console. The task then has to be deleted and re-created. A fix for this has been implemented.

• 2823: Submitted Requests can be Cancelled by any User since Requester/Client Permissions are not being checked before allowing the ability to Cancel. A fix for this has been implemented.

• 2824: There is a dashboard HTML editor bug that does not allow you to access the source code and loses the scroll bar when trying make an edit to a Dashboard HTML panel on screen sizes that are smaller than desktop. A fix for this has been implemented. (HT-19617)

• 2830: When an Attachment Question type contains multiple attachments, the Document Viewer Icon is displayed in the wrong place within the Task History as the first attachment’s Document Viewer Icon is after the attachment’s separating comma and is incorrectly located next to/preceding the second attachment. A fix for this has been implemented.

• 2836: FILE_NAME is now appearing again in the PDF Generator task configuration screens.

7/2/2024

Changes/Improvements

• 2732: Within the PDF Generator Task, “Source of PDF to Complete” and “PDF task to begin document creation” configurations have been added for use when a User needs to chain multiple PDF Generator tasks together and reference the task not the Template within the PDF Generator Task. These options existed in v6 and v7. (HT-18472)

Fixes

• 2432: When a User tries to reassign specific Tasks from within the Replace User function, the list of Open Tasks appears to be limited to less than 100 tasks. A fix for this has been implemented. (HT-19530)

• 2792: The Date column within a grid stores data in a ’2024-06-22T04:00:00.000Z ’ format, which is inconsistent with the a regular Calendar question that saves as 2024-06-22. A fix for this has been implemented.****

• 2814: When a User is navigating to a Form, the theme selector will sometimes display and then disappear. A fix for this has been implemented. (HT-19507)

• 2815: Currently the ‘Force user to change password on next login’ option, within the Users Profiles, only functions when the ‘enforce password expiration’, within the Password Settings, is enabled but should always function. A fix for this has been implemented. (HT-19247)

• 2819: When a User selects an option in a Select list within a Grid and saved, the choice that was selected can’t be seen in the Grid row. A fix for this has been implemented. (HT-19691, HT-19723)

6/25/2024

Changes/Improvements

• 2558: AddedDocument Viewer (powered by PSPDFKit Web SDK and Managed Document Enine) which provides the abillity to preview common document types uploaded to Integrify without the need to downoad them. The preview can be activated by clicking the ‘eye’ icon next to an available file. Some of the locations this has been made available are: Request Detail, Attachment questions during form execution, Request Disscusion Posts, Excel batch task config and runtime, Excel import task config runtime, Task notification settings, and most places that allow for an attachment. Supported file types are here (FR-17393)

• 2599: An Office Templating task type powered by PSPDFKit’s Document Engine has been added, which allows for PDFS and DOCX files to be created from request data using a docx file with ‘placeholders’

• 2681: Added the abillity to wrap Question Labels via a “Wrap Question Label” option located in the Basics menu option. When editing a Question type, a User can enter a check in the “Wrap Question Label” checkbox to enable this option. (FR-18254)

Fixes

• 2782: When switching between print and normal view from the Completed form view, form javascript was executing on each switch. In certain rare cases, this woulld cause vlaues to chage at each switch. A fix for this has been implemented. (HT-14364)

6/20/2024

Fixes

• 2791: When a User is editing a Form’s Script and then after they click the SAVE button, the save functionality quits working after a short period of time (maybe 15 minutes). The User then needs to close the Form or refresh it to get it working again, possibly losing thier edits. A fix for this has been implemented.

• 2793: After a User changes a Process Name on the Process Detail tab, the change doesn’t get reflected in the Process Title Bar or category list. A fix for this has been implemented.

6/13/2024

Changes/Improvements

• 2397: The ability to logout failled login attempts have been added by using two configurations located in the System Settings. The first is “LoginLockoutAttempts”. This is a number that refers to the amount of login failures thats allowed before the User is locked out of the system. The second is “LoginLockoutTimeout”. This is a number that refers to the amount of time that the User is locked out of the system. A unlock icon has also been added. This is located next to the User name when viewing the Users list and is available for Admins to unlock a User or Users that are locked out of the system.

Fixes

• 2727: When a User attaches or embeds several large file size graphics and attachments in a Rich Text question or anywhere that uses a similair component (Process detail description, Form detail, Task detail, Display settings, System message body), they cause performance issues when loading the request detail or completed forms. A fix for this has been implemented.

• 2742: When a User deletes a Dashboard or Dashboards, there is no Confirmation Dialog presented to the user as the delete option currently removes them all without a way to modify and review the choices. A fix for this has been implemented. Now a User will be presented with a dialog consisting of a way to remove 1 or more of the Dashboards selected or Cancel them all from being deleted

• 2744: Form rules that set a Question as Editable are allowing Users to make edits on the Completed Forms. A fix for this has been implemented. (HT-18747)

• 2745: When you have the “Wrap all text in grid” option selected for a Grid question, the grid displays inconsistently on completed forms. Sometimes the grid data doesn’t display at all, other times the data displays but the text does not wrap. A fix for this has been implemented.

• 2768: When a User has a Form Task set to Request Record, it is initiated and assigned to the Recipient but the Recipient doesn’t get the Recipient task on the front end, although it is created backend. A fix for this has been implemented where the Request will be in the View Request Records section via the left Nav. (HT-19057)

• 2783: When a User makes changes to a Form’s Detail, JavaScript, or CSS, the Form’s Last Modified Time and Modified By information was not being updated accordingly. A fix for this has been implemented.

5/22/2024

Changes/Improvements

• 2468: A Feature that adds a System Setting to delete User login history after X amount of time has been implemented. The options indicate the number of days to keep User login history. ‘-1’ means keep all history, ‘0’ means keep no history, ‘1’ means keep 1 day…etc.

• 2766: Hyprlink question types on forms are now clickable when viewing a completed form or when read-only in active forms.

Fixes

• 2764: When an Admin was viewing a User’s Devices via Users > Manage Known Devices, there was no back button or way for the Admin to return to the User’s list. A fix for this has been implemented.

• 2770: If an Admin attempts to modify a User’s profile via Administration > Users > Edit User profile, they were forced to change the password if it did not already comply with global password settings and complexity. This prevented detail changes from being saved. A fix for this has been implemented. (HT-19171)

5/14/2024

Changes/Improvements

• 2633: We now track login success, device id, and method when users login.

• 2636, 2398: Enabled MFA functionality. With this users and administrators have control over devices, and how long MFA remembers a device.

Fixes

• 2730: Fixed issue where the scheduler service would crash and restart on certain errors.

• 2734: When building a Standard Task Report, that is not referencing a specific process, within the Column configuration window, selecting “Task” as the Source does not display the Process field option where a Process can be selected for the task. A fix for this has been implemented. (HT-18853)

• 2735: When a User attempts to prefill a calendar question with the Completion Date of a Form task, nothing is prefilled in the calendar question. A fix for this has been implemented.

• 2737: Grid Questions within a Form that contain Footers are not displaying the Footers when a User views the Completed Forms of a Request. A fix for this has been implemented.

4/24/2024

Changes/Improvements

• 2466: Added the scheduled date and time display to the Task History and the Monitor Request Flow View.

• 2698: The PDF Generator Task Type now has the abliltiy to generate an editable PDF by enabling a “Keep PDF editable for future appending” checkbox option within the Task’s Configuration>Configure Task>General Settings window. (HT-18472)

Fixes

• 2361: When a User creates a Form containing JavaScript to read the footer values in the grdItems grid question by accessing the getFooterValues() function, it throws an exception error. A fix for this has been implemented.

• 2679: When a User hovers over a completed task in the Process Flow View, the task type displayed frequently does not match the actual task type. A fix for this has been implemented.

• 2690: When User attempts to create a custom connection string with different ports an error is thrown when clicking the Test Connection button. A fix for this has been implemented.

• 2700: When a User imports a Process that has a Form containing a Notification configured with an Attachment, the Form Notification in the Process becomes blank. A fix for this has been implemented.

• 2703: Some Form Sections do not always show via an Approval task Form link and also in Completed Forms. A fix for this has been implemented. (HT-18415)

• 2715: When a User creates a Grid with, for example, Four Columns and then later adds a New Column and/or attempts to reorder the Grid Column order, the Grid loses all of the Column information upon clicking the “Save Changes” button.

• 2716: The Form Assigner scheduled time that displays within the Task History is incorrect. A fix for this has been implemented.

• 2717: When a User wants to reset thier password via the reset option on the login page, a link within a notification is sent with a one hour expiration. When a User attempts to use the reset link after it expires, a dialog displays allowing the User to enter new passwords and submit them after which they would receive an error. A fix for this has been implemented where the User will now see an expiration error message after clicking on the reset link.

• 2731: There is a preview eye Icon that displays on attachments that is currently supposed to be hidden, via a flag within the code, but it is visible. A fix for this has been implemented.

3/27/2024

Changes/Improvements

• 2676: When a User maps an attachment question from a Form in a Rest Client task, the mapping value returned is the name of the file. A dropdown has been added in the mappings configuration screen where the User can choose between the File Name and the File Stream. The File Stream can then be used in an API call.

Fixes

• 2663: When an Admin User views the Set Recipients option of a Task configured with the Recipients setting of “Each in Order” via Manage Requests, the Recipient order column is no longer displaying preventing the Admin User from adjusting the order. A fix for this has been implemented.

• 2692: When a User runs an Email Monitor, emails that are being processed that contain attachments are not prefilling Forms with said attachments as the attachments are not being passed in. A fix for this has been implemented.

• 2696: When a User checks the “Read Only” setting for a Form’s Link question type, the setting does not persist after saving and exiting the Link question type on the Form. A fix for this has been implemented.

• 2697: When a Dynamic Assigner is used to assign Recipients to a task with the “Each in Order” option selected for the Recipients, the Recipient Tasks are being assinged all at once instead of in order. And, when an Admin adds Recipients to the Task via Manage Requests, the existing Recipients are removed. A fix for this has been implemented.

3/21/2024

Fixes

• 2647: In the request detail, Request Records were not showing the last input data when viewed. The data would only show whe a user tried to edit the data. This has been rectified.

• 2682, 2684: When changing a task’s assignment type to ‘Each in order’, ordinals would not be assigned to pre-existing recipients. When trying to add the ordinals, negative ordinal numbers could be generated depending order chosen. A fix has been implemented for these issues.

• 2686: When a User Versions a Process with certain Permissions, the Permissions don’t copy over to the new Version. A fix has been implemented for these issue.

• 2687: If a User attempted to print a Completed Form that had multiple pages, only the first page would print. A fix for this has been implemented. (HT-18408)

• 2688: When viewing a Form grid in the Task History, the data shifts to the left placing the values under the wrong columns. A fix for this has been implemented. (HT-18210)

3/14/2024

Changes/Improvements

• 2596, 2628: A password screen has been added and will display to check the Current Password and require a New Password to be entered for Users that change their passwords. A screen for Users who forget their password will display and require a New Password to be entered but will not require them to enter the Current Password.

• 2606: Remove hard coded labels in Pages under Password settings, Translations, Api-keys, SSO settings, Active sessions, and API

• 2642: Remove Hard Coded Labels Under Request Pages. This makes localization of system labels more complete.

• 2643: Remove hard coded labels under process pages. This makes localization of system labels more complete.

• 2645: Remove Hard Coded Labels Under Reports Pages. This makes localization of system labels more complete.

• 2646: Remove hard coded labels under Admin > Forms. This makes localization of system labels more complete.

• 2649: Remove hard coded labels under Dashboards, Email Monitors, holidays, business hours, database sources system messages and system settings. This makes localization of system labels more complete.

• 2650: Remove hard coded labels under Users, Groups, Categories, Process Scheduler, and Report Scheduler. This makes localization of system labels more complete.

• 2651: Remove hard coded labels under Profile Icon pages, Help icon pages, and bookmarks. This makes localization of system labels more complete.

• 2661: In Monitor Requests, Manage Requests and View My Tasks, when a User enters a numeric value in the Search bar, it will now search descriptions and request names as well as request IDs (HT-18235)

Fixes

• 2605: Some system modal windows such as the windows for Contact Search and Searchbox, were not displaying the system theme colors when it was changed. A fix for this has been implemented (HT-18037)

• 2639: After manipulating dashboard widget positions, they would sometimes overlap after changing screen resolutions. This has been resolved. (HT-18106)

• 2648, 2654: Error messages were being displayed when running the PDF Generator task. The files were being created, just not saved back to the request. A fix for this has been implemented

• 2652: When an User viewed the Active Sessions via the Gear icon, there were duplicate session displaying if there were multiple browser tabs opened running Integrify A fix for this has been implemented (HT-17636)

• 2657: When Users either Submit a Form or select Save Draft on a Form containing JavaScript on a touch device, duplicate Form submissions could occur due to the buttons not immediately being disabled. A fix for this has been implemented that includes a new “EnhanceSubmissionProtection**”** configuration within the System Settings that Admins can engage to prevent this from occurring.

• 2666: Request time when submitting forms was doubled to prevent time-outs.

• 2685: When a User attempts to view a Form using a link within an Approval Task, the popup Form that displays was missing the scroll bar. A fix for this has been implemented (HT-18399, HT-18400, HT-18401, HT-18392, HT-18404)

2/13/2024

Changes/Improvements

• 2574: The ssp client API - left nav has been replaced

• 2585: The ssp client API - process / bypassstart has been replaced

Fixes

• 2629: When unsupported colors are used in an uploaded Logo, within the System Settings, the color thief used in system theming breaks. A fix for this has been implemented (HT-18027)

1/25/2024

Changes/Improvements

• 1058: The ability to allow selectable and searchable User Profile Attributes such as Name, Contact ID, Email, etc… in Assign Recipients screens has been added. This affects the following screens:

  • Assign recipients in process flow

  • Set recipients in manager requests - flow and task list

  • Task assigner at runtime

  • Role membership tables - show members under Roles and Permissions for Processes, Forms, Reports, Groups

  • Group membership table - show members (FR-10687)

• 2315: The Button code for dashboards to start requests for any version doesn’t work for non-admin users. A fix for this has been implemented that consists of new “Start Request By ID” Button links that have been added in the HTML Panel Widget (HT-16600)

• 2479: Two additional System Settings have been added for a Guest User. One is an Inactivity setting that can be set to a Maximum time that will end the Guest User session if no action is being made. The Second is a Custom Message that can be displayed after the Guest User session is timed out due to inactivity.

• 2508: An Admin configurable theme has been added to the System Settings which will allow Administrators to select custom System theme colors.

• 2519: Convert “My Account” to Vue

• 2546: A customizable Color-Theme has been added to the System Settings which will allow Users to create a system color theme based on an uploaded Image.

Fixes

• 2464: When viewing a request record, the User can’t scroll all the way down to view the entire form, and when resetting a request record, the status changes from ‘Initialized’ to ‘Completed’ and when there are 2 recipients in a request record form, only the requester can update the form. Fixes for these bugs have been implemented

• 2478: When a User removes a DB Pull Task’s configuration Mapping, the Task still attempts use to the removed Mapping at runtime and also throws an error. A fix for this has been implemented

• 2495: When a User has a query within a DB Pull that doesnt include a Column Name, the query doesn’t function. A fix for this has been implemented

• 2536: Users are unable to connect a transition line to the bottom of the End task within the process canvas. A fix for this has been implemented to enable this ability

• 2549: The “Compare To” Start Rule is not evaluating correctly for numeric values returned from a DB Pull. A fix for this has been implemented

• 2554: When copying Start Rules from a Task which Start Rules contained a “Compare to” in it, the Start Rules would not be copied in its entirety. A fix for this has been implemented

• 2557: When reordering Start Rules that contained a “Compare to” in it, the Rules that was used to compare would not move together resutling in what appeared to be, through the UI, an incorrect Rule. A fix for this has been implemented to keep the compared to Rules together when reordering

• 2559: Non-American Calendar question formats such as Day/Month/Year do not work with the Date question type. A fix for this has been implemented

• 2563: The Right-Click menu within the Rich Text fields no longer contain the Cell option for creating tables. A fix for this has been implemented where that option is now added as an Icon in the menu (HT-17890)

• 2589: The Guest and System Accounts were not filtering automatically from dynamic groups. A fix for this has been implemented. Please make sure your guest account has been specifically granted permissions to the processes, reports, and dashboards they need acces to.

12/28/2023

Changes/Improvements

• 2539: When viewing the tree view for Forms, Reports, Processes and Categories under Administration, the entire row for an object can be clicked instead of just the object icon. This also applies to tree views under Actions.

• 2544: duplicate notifications of tasks already being completed are no longer shown.

• 2329: New settings are immediate and persistent when changing themes. The sdefault theme is also used properly by the login screen.

• 2454: Removed an unecessary message from the title bar of the preview pop-up of the auto arrange function in the eprocess editor.

Fixes

• 2541: Open URL tasks now complete entirely and return to the next task.

12/22/2023

Changes/Improvements

• 2537: When a User assigns a recipient to a Task, the default setting is now “Dynamic” as this is more commonly used as a recipient when opening up an assign recipients dialog in the process designer

Fixes

• 2542: If a User clicked on a v7 link within the v8 version, the links would not translate correctly and would not function. A fix for this has been added which provides the ability for v7 (angular) links to translate over to v8 style links correctly.

• 2547: When the Task Assigner is configured with the second option, “Do not allow user to complete task if no recipients were selected”, the submit button would never enable at runtime. A fix for this has been implemented so that now the submit button is enabled.

12/21/2023

Changes/Improvements

• 2511: (2309 - OnPremise) We improved the way in which you can reorder the fields to capture. You can now drag and drop items in any order and a button is provided to automatically rearrange them in the order they appear on the form. This should help adjusting the order when large forms get new questions added to them.

• 2513: When assigning recipients to tasks, the filter menu is now check boxes instead of a submenu for easier access

• 2515: (2431 - OnPremise) We have added the ability to bulk activate/deactivate Users by adding checkmarks in checkboxes next to the Users on the left side and clicking on an Activate or Deactivate button. We also added the ability to activate/deactivate one User at a time by clicking on the green “Checkmark” or the red “X” on the right side of a User.

• 2516: (2426 - On Premise) A new “Last Login” column has been added to the Users screen under Administration. This will indicate the last time a User logged into the system by the Date and Time displayed in that column.

• 2518: The word “(default)” has been added as an indicator within the User’s Switch Theme dropdown next to the color selection that is the System Settings default

• 2534: When an Admin was configuring the category of a Form, Report, or Process, they needed to click on the folder icon to make a selection. A fix increasing the clickable area to include the name and space next to the folder icon has been implemented.

• 2535: Added functionality to the intForm object to disable or enable the ‘submit’ and ‘save draft’ buttons has been added. These should be used when custom functions for onSubmit and onSaveDraft are written in a form to reduce the risk of duplicate submissions:

  • intForm.submitButton.disable()

  • intForm.submitButton.enable()

  • intForm.saveDraftButton.disable()

  • intForm.saveDraftButton.enable()

Fixes

• 1402: When starting a request using a link/button from a dashboard, clicking the browser’s back button created an additional request instead of going back to the original location. A fix for this has been implemented to prevent the multiple requests and takes the user back to the link’s origin.

• 2512: (2383 - OnPremise) There was an issue where the Scheduled Reports exported reports contained an extra ‘r’ column. A fix for this to remove the ‘r’ from the exported results has been implemented

• 2514: (2477 - OnPremise) When performing a redo-completion action on a task from manage Request, the setting as assigned in the “When this task completes, set the following milestone” is not being set and used in the last milestone of the request. Instead a milestone downstream is persisting. A fix for this has been implemented

• 2517: (2446 - OnPremise) The system will now timeout for inactivity when a User configures the logout time within the System Settings > InactivityLogoutMinutes

• 2524: For processes with the request start screen enabled, users were able to click the Start Request button multiple times, causing multiple requests to be created. A fix to prevent this from occurring has been implemented

• 2526: Within the Adminstation > Groups, when a User is clicking on the Assign Roles icon for an individual group, and then “Show Members”, the role tree menu shows the top level, which is correct, but it should also show the group level that the User is on so they can jump back and forth within the menu. This should also apply to the Dashboards role tree menu. A fix for this has been implemented to enable this ability

• 2531: When a user viewed a request that was submitted prior to #1246 which contains a form with a contact search question marked to allow multiple contacts, an error is thrown within the devtools console. A fix for this has been implemented

• 2532: When a User sets the height settings within the Grid question type the height does not display the same at runtime. This was mainly an issue when the word wrap was enabled. A fix for this has been implemented (HT-17745)

• 2533: This issue confirms that the submit button is disabled immediately after being clicked for Approval task, Excel Batch, Excel Import, Milestone task, Task Assigner, and Task Scheduler so it cannot be clicked multiple times and cause duplicate requests.

12/15/2023

Fixes

• 2507: When prefill grids that has over 11 rows, the grid doesn’t display the rest of them and Users can’t search for them either. If a User clicks on a visible row the other rows will then appear. A fix for this has been implemented (HT-17631)

• 2510: Users without the correct top level permissions can access the top level roles but when attempting to select another User to add to a role, the screen throws permission errors and a progress bar displays. A fix for this has been implemented where the roles and permissions menu option will be disabled for User without the proper top level or any level permissions

• 2521: When a User is at the top level manage role members screen, the treeview menu displays but should not. A fix for this has been implemented

• 2522: The Shield icon for assigning Roles within Groups are displaying for Users with no Grant permissions but shouldn’t. A fix for this has been implemented

12/14/2023

Changes/Improvements

• 2496: The User theme selection has been moved from an Angular screen to a Vue popup

Fixes

• 2446: (Cloud Only) The system will now timeout for inactivity when a User configures the logout time within the System Settings > InactivityLogoutMinutes

• 2476: When a User configures a start rule that includes Status=TImed_Out or Status != Timed_Out the rule does not work. A fix for this has been implemented

• 2491: Process Administrator Permissions are Not Allowing Users To Edit Roles & Permissions with Grant rights. A fix for this has been implemented

• 2494: A stream of “inactivity logout” error messages have been displaying in the dev tools console. A fix for this has been implemented

• 2501: Within the Dashboards there is a HTML Panel Widget that allows Users to upload images. The only way to upload the image is through the image icon but currently not through the Insert>Image selection from the top menu. A fix for this has been implemented where both ways to upload is now available

12/8/2023

Changes/Improvements

• 1185: Added the ability to show owners in the role membership view and also added a tree view for the ownership in the top menu bar. In the role membership views, within the right panel it display the owner of the membership before the name of the group or user.

• 2309: (Cloud Only) We improved the way in which you can reorder the fields to capture. You can now drag and drop items in any order and a button is provided to automatically rearrange them in the order they appear on the form. This should help adjusting the order when large forms get new questions added to them.

• 2473: (Cloud Only) Added the ability to Save the last login date after logging in the app when an impersonate endpoint is used.

Fixes

• 2260: The PDF merge task fails if there is an attachment configured within the PDF merge task that was left empty during runtime. A fix for this has been implemented (HT-17508)

• 2261: When a User is displaying the Form Questions via Admin > Process > Process Detail > Form Questions, all the questions do not display when using a Process with duplicate forms and questions. A fix for this has been implemented

• 2477: (Cloud Only) When performing a redo-completion action on a task from manage Request, the setting as assigned in the “When this task completes, set the following milestone” is not being set and used in the last milestone of the request. Instead a milestone downstream is persisting. A fix for this has been implemented

• 2481: If a User changes the Field order of a form within the FIELDS TO CAPTURE tab via Form>Configuration>Configure Task, an error gets thrown when clicking on a Confirmation button for the order in a popup window. A fix for this has been implemented

• 2483: When a User views a Form using a form link within an Approval task, the whole form, depending on the size, can not be seen because the scroll bars would not scroll to the bottom of the Form. A fix for this has been implemented (HT-17478 , HT-17565)

• 2484: The Form Text Layout object looses text formatting like indentations and numbering at runtime and in preview mode. A fix for this has been implemented (HT-17563)

• 2487: The Form Task>Configuration>Display Settings are no longer keeping the formatting that is selected by the User and saved. And when a Custom Layout object is used to code custom buttons, the buttons are not keeping the User set system color theme setting. A fix for these bugs have been implemented (HT-17577)

11/27/2023

Changes/Improvements

• 2426: A new “Last Login” column has been added to the ADMINISTRATION>Users screen. This will indicate the last time a User logged into the system by the Date and Time displayed in that column.

• 2431: We have added the ability to bulk activate/deactivate Users by adding checkmarks in checkboxes next to the Users on the left side and clicking on an Activate or Deactivate button. We also added the ability to activate/deactivate one User at a time by clicking on the green “Checkmark” or the red “X” on the right side of a User.

Fixes

• 2475: When Users were loading multiple Reports to view they were getting logged out of the system. A fix for this has been implemented

11/16/2023

Changes/Improvements

• 2208: When a User has duplicate questions on a form, it is hard to distinguish which question is which when viewing them from within a Data>Source configuration. A fix for this has been implemented to add Client IDs in parenthesis to all Source - Data whenever duplicates are being used (FR-15936)

• 2426: A new column has been added to the User’s view (UI) that displays a User’s last login time stamp

Fixes

• 2330: Within the Database Pull Task’s Configuration>Configure Task>Mappings, Users were unable to remove existing MAPPINGS because there was no option to remove them. A fix for this has been implemented

• 2445: An Email Approval Bad Request Error message incorrectly displays when using a notification approval link twice when the approval wasn’t completed the first time. A fix for this has been implemented (HT-17232)

11/14/2023

Fixes

• 2455: When there is a form task preceding a task using a “does not contain” rule to evaluate the preceding form’s empty checkbox, radio button or select list, the form does not evaluate and halts the process. A fix for this has been implemented

• 2456: If a User placed a full screen configured chart into a dashboard, the chart would render about one fifth the size when viewing at runtime. A fix for this has been implemented (HT-17343)

• 2458: When a User is editing the Grid question type and is configuring the “Define Rows” Menu option, the Add Row and Delete Buttons appear when Users check the respected checkboxes and disappear when unchecked. Now a preview indicator tool tip displays when hovering over said buttons to confirm this is only for preview purposes.

11/10/2023

Fixes

• 2294: If a User has a Task Scheduler task in a process, the User cannot configure a Notification to include the Date, Time or Timezone selected from the task via the Configuration>Notification Settings>Prefill Notification With Request Data. A fix for this has been implemented

• 2313: When a User attempted to update a request record, the task would not load on the first try. A refresh was required to open the task. Also, when the task was opened, and the user went back to the request detail and tried to click the request record to edit again, it would not change focus back to the request record. A fix for this has been implemented

• 2452: When in the form editor, a form admin was unable to delete rows from grid questions because the Delete button would not enable upon selecting a row. The delete button should be enabled so the form admin can click on it to delete the selected rows. A fix for this has been implemented (HT-17332)

11/2/2023

Fixes

• 2438: Existing PDF Generator tasks are failing as the Names of PDFs are being modified to incorrectly include HTML tags. A fix for this has been implemented

10/31/2023

Fixes

• 2387: When a User deleted an imported Report, the deleted Report would still display on the list of Reports. A fix for this has been implemented

• 2436: Within the Dashboard’s HTML widget, there was an “Upgrade” button that was not intended to be a part of the configurations. A fix for this has been implemented (HT-17172)

• 2437: Some form questions were not lining up correctly on a form so the form was displaying off - center. A fix for this has been implemented (HT-17178)

10/27/2023

Fixes

• 2435: Existing PDF Merge tasks are failing as the Names of PDFs are being modified to incorrectly include HTML tags and the Parameters are being wiped. A fix for this has been implemented (HT-17171)

10/26/2023

Fixes

• 2340: Auitocompleting forms were submitting “NULL” values to the Database for blank questions instead of skipping them. A fix for this has been implemented

• 2374: In the Process Editor, within a Task’s Start Rules, “Compare To” rules with “Task Completer” or “Task Recipient” as the source, were not working properly. A fix for this has been implemented

• 2433: :Legacy report, dashboard, start request links, and other legacy API calls were not redirecting properly. A fix for this has been implemented to support them.

10/25/2023

Changes/Improvements

• 1897, 2345: Applied security fixes to all necessary modules to comply with zero vulnerability - zero deprecation policy. Standardized on a singlular rich text editor module.

• 2321: The ability to override the Form Calendar Question’s “Future Dates Only” setting has been added to accommodate prefill values, which allows Forms to be submitted successfully without any “future dates only” error messages preventing form submission

Fixes

• 2346: When using Filter Reports via the View My Reports left menu option, the search did not include the Description and only the report Name was being searched. The Description was also displaying in raw HTML instead of being formatted and links within the Report’s description were not clickable. A fix for this has been implemented (HT-13783)

• 2354: When adding or editing System Messages, Admins were unable to add Links or Images. A fix for this has been implemented (HT-16900)

• 2372: When an Excel Batch task was being used in a process, the launched child process from the Excel Batch task was stalling on a Milestone task because the Milestone rules were not being evaluated. A fix for this has been implemented

• 2383: There was an issue where the Scheduled Reports exported reports contained an extra ‘r’ column. A fix for this to remove the ‘r’ from the exported results has been implemented

• 2384: When viewing a Form containing a Calendar question type, the form would freeze and throw errors if the User switched tabs from one view to another multiple times. A fix for this has been implemented

• 2386: Users could not delete checked Rows within the Grid Question type via the Delete button becuase it was disabled. A fix for this has been implemented (HT-17075, HT-17076, HT-17100)

• 2415: Task Notifications that are configured to include a PDF Generator task’s generated PDF as an attachment did not contain the PDF. A fix for this has been implemented

• 2418: Upon opening new Process or Report Schedulers, the required fields validation fired and highlighted the required fields before the User had a chance to enter in values. This validation should occur after the User clicks on the Save button. A fix for this has been implemented

10/10/2023

Changes/Improvements

• 2115: In the database sources configuration screen, we added a ‘Test Connection’ button so that admins can ensure a connection is properly configured. The screen was also converted from angular.

• 2268: Task Recipient Cleanup added. This new feature allows a process designer to set a task to clean out any recipients of a task who did not complete the task. This is helpful for ‘claim’ tasks or tasks assigned to groups where information about users who did not complete the task is unnecessary.

• 2303: The pop-up window displayed when clicking a question’s help icon in a form now resizes to the content as it was designed.

Fixes

• 2186: When a Form Admin tried to create a form rule based on a newly created question on the form, the rule would fail to save with an error message. This has been rectified, and rules can be created immediately against new questions.

• 2191: When a user opened multiple processes in the Process Editor during their session, the application would attempt to refresh the process diagram of all these processes whenever an edit was made in a process editor. Only the current diagram should have been getting refreshed. This caused unnecessary load on some of the backend services. This has been fixed.

• 2262: Within the FTP Task > Configuration > Configure Task, the “File to Send” dropdown displayed the unique identifier of the process’s file assets instead of the friendly labels. A fix for this has been implemented

• 2288: In the Prefill Settings tab of the Configure Task dialog for a Form Task, there is a Restricted View To Role column. Once a user was selected in that column, there was no way to remove the selection if needed. An X was added to allow clearing the option.

• 2317: In Task Notifications and Dynamic Names, the text editor can be resized to the point where it completely collapses. There is no way to resize them again, as the arrow icon used to resize the editors is hidden. A fix for this has been implemented.

• 2318: When configuring a notification from within the Process Editor, resizing the window would not force scrollbars to appear when they should have. This made sections of the dialog inaccessible to the user. A fix for this has been implemented

• 2319: Custom Reports that use stored procedures had an incorrect row count when run. If Report Parameters were configured with Values, they were ignored when a User exported the report. Fixes have been implemented for both issues.

• 2322: Within Form Rules, Operands in the Conditions of the rules were not displaying, causing an inability to update those rules. A fix for this has been implemented

• 2342: There was an issue where exported reports contained an extra ‘r’ column. This has been removed from the results when exporting.

• 2344: When using the Form Editor from within the Process Editor, a question’s help pop-up was displayed behind the embedded form editor window. A fix for this has been implemented to display the Help text in the front of the Form

9/5/2023

Changes/Improvements

• 2054: In the process editor, when viewing the start rules of a task, if the task does not have rules yet, you can copy rules from another task in the process. This helps save time if a process admin needs most of another task’s rule to split a process down a parallel path.

• 2169: We refined the min and max date range properties of the calendar question in the form editor. A form admin can now use ‘natural language’ to define absolute and relative minimum and max values for a calendar question. This allows for more set-it-once situations for configurations of the question type. We also tweaked the user interface to allow for better input of dates further away from ‘today’. See this page for more information.

Fixes

• 2264: Validated that the InactivityLogoutMinutes System Setting functions properly when the user had logged in through SSO.

• 2269: When using the Task’s Dynamic Names feature for the Request Name, it inserts both the Field Name and Value correctly and includes stray characters. A fix for this has been implemented

• 2280: When editing a task’s rule in the process editor, saving a rule without making changes did not save the rule’s information in its entirety. This has been fixed, so the rule is completely saved. (HT-16329)

• 2282: For Tasks that include the Recipient configuration. Within the Recipients>Assignment Settings, the verbiage for the option “Cancel Tasks for Other Recipients After Assignment” has been corrected to read as “Cancel Tasks for Other Recipients After Reassignment.”

• 2297: The saved Username and Password text that displays on the Integrify Login Page incorrectly overlaps. A fix for this issue has been implemented (HT-16607)

• 2298: The Display Settings within the Configuration for Tasks were disabled, so Users were not able to add text or edit existing text within them. A fix for this has been implemented (HT-16660)

• 2304: Exporting form questions stops exporting if any Form fields contain a “#” (pound symbol) in the label; when exporting the list of questions to .csv, the export file stops right before that “#” symbol. A fix for this issue has been implemented

• 2307: Within the Approval Task Notifications, Users cannot edit the text in the body or the subject and throw 500 errors when attempting to save the edits. A fix for this has been implemented

• 2308: When using the Developer Form Task in a process, it displays in read-only mode at runtime, so Users cannot input data into the Developer Form. A fix for this has been implemented

• 2310: When attempting to import a process, certain start rules with non-task-based sources (like a request - last milestone, for example) would fail to import. This has been fixed

• 2311: The Description/Notes within the Task>Configuration> Edit Detail > Description/Notes were disabled, so Users could not add or edit existing text within them. A fix for this has been implemented

8/23/2023

Fixes

• 2160: The grid question now displays the Client ID to the user when editing a grid column via the Form Builder in the Define Columns configuration

• 2234: Users with only ViewConfig permissions can no longer make changes to processes flow views (HT-15988)

• 2256: When editing a Task Configuration from the Process Editor, users can save prefill mappings against form questions that do not have a label.

• 2258: When a User had two separate tabs open in a browser, and they were running two separate processes that were both currently on an open Form Task, if the User then refreshed one of the tabs, the process in the refreshed tab would be redirected to the other tab’s process. A fix was implemented for this bug

• 2271: There was a discrepancy in logic in some parts of the application as to when to save data to the overflow table. This has been rectified. This issue was not visible to users in any way.

• 2272: In a completed form view, when using the currency question in a grid, the footer symbol was displayed with the symbol that the grid question was currently configured to use instead of what the symbol was when the form was submitted. A fix for this has been implemented so that the currency symbol in the footer represents that of the submitted data.

• 2273: When using the grid currency question in Notifications, the symbol was not displaying for all the rows in the grid. A fix for this was implemented.

• 2275: When using the Approval By Email option in the Approval Task’s notification, the approval links within the notification were improperly requesting a user to login. This has been rectified. Additionally, If a user has already submitted an approval and selects an approval by email link again, there is now a message displayed to the User indicating that the approval has already been made (HT-16442)

• 2277: When filling out a form, the calendar question listed previously selected dates as ‘auto-fill’ in a window in front of the calendar, blocking part of it. This issue has been fixed so the browser will ignore calendar questions for auto-filling. (HT-16449)

• 2284: When using the Approval By Email option in the Approval Task’s notification, approving a request by email link displayed the system-themed page to the User. A fix for this issue has been implemented (HT-16529)

8/3/2023

Fixes

• 2266: When the PDF Merge Task referenced a Form Task that had been submitted multiple times, it created duplicate Forms in the PDF Output. A fix for this bug has been implemented (HT-16316)

7/28/2023

Fixes

• 2243: Dynamic names used to rename a request’s ‘Name’ when the task is either started or completed in Tasks from v7 processes that were migrated to v8 are now displaying correctly within the Task>Configuration>Dynamic Names page

• 2249: When there is an existing specific prefill mapping within a Form Task, and it is changed to (None), the dialog retains the ID of the previous mapping. A fix for this bug has been implemented

• 2252: An Error was being thrown whenever a User was adding a Request Parameter within the configuration window of the REST Client Task Configuration>Configure Task>Request Parameters tab. A fix for this bug has been implemented

• 2255: When configuring Tasks, within the Task>Recipients>Recipients window, Users choosing the Dynamic Recipients list can now add more than one Task Completer without the other Task Completer recipients being disabled as if they were added with the first one. Also, if Tasks share the same name, the Task ID in parenthesis will be added to the name within the Dynamic Recipients list

• 2265: When editing and saving a Report Column where “Request” or “Data” was the Source in the Column configuration, the Field and Task would be removed, and subsequently, the Report would error out. A fix for this bug has been implemented (HT-16297)

7/19/2023

Fixes

• 2251: While editing a Select List, Radio button, or checkbox question type in a Form, re-saving the modified Client ID within the Basic configuration option with the same value more than once will no longer display a “Client ID must be unique” error (HT-16213, HT-16217)

7/13/2023

Fixes

• 2209: Task Configuration>Notification Settings are displaying normally now and are editable for Users that have Process Admin Permissions but that are not full Administrators (HT-15854)

• 2248: Within Task’s Task Configuration - Configure Rules, there is a checkbox at the top left of the screen that, when selected, a Delete button to allow Users to delete all of the rules at once. This checkbox and Delete button will now be disabled after it is selected and used to prevent all process’s task rules in the database from being deleted (HT-16165)

7/10/2023

Changes/Improvements

• 1071: Process admins can now add links to completed forms into notifications (FR-12196)

• 2096: Tasks with the same name will now display the task ID in parenthesis after the name if there are duplicates for Users to identify within dropdowns in task rules, notification settings and report filters

• 2172: “Task” has been added as a Source Option within the Task Configuration Notification Settings Prefills, Task Rules, Task Recipient Rules, Task Dynamic Names and Form Task Prefill Settings, Query Parameters and Variable Mappings

Fixes

• 2171: prevented console error from occurring when loading the ace-editor component. This affected all places where the editor was being loaded (SSO config, among other places)

• 2198: Special characters like an ampersand are no longer displaying with Encoded Characters within the notification subject line when used in the Task Configuration - Notification Settings

• 2236: The User Profile Task that is used to update User information is no longer missing a Password option that is within the dropdown of options that contain other options such as First Name, Last Name, Phone, etc… These options are used as Parameters within the User Profile’s Task Configuration Profile Mappings that update User information when selected (HT-16035)

• 2245: Errors are no longer thrown when a User is attempting to use the Import Fields option within the Prefill Settings of a Form Configuration - Configure Task (HT-16141)

6/15/2023

Changes/Improvements

• 1989: Within the task configuration-notification settings, an additional input text box has been added to the Prefill Source when selecting the ‘Request Link’ or ‘Task Link’ for insertion into the notification body where a User can type a ‘friendly name’ for the link giving Users the opportunity to hide the link behind text of their choosing (FR-14604)

• 2083: Within the Form Editor, all client id’s on a Form should now be validated to make sure they are not empty or are duplicates. This is for all question types, sections, and containers on a form. If a client id is invalid, the client id field in the dialog will display an error state (red underline). When the save button is clicked with the client id field in an invalid state, there will be a message displayed at the bottom of the dialog

• 2110: When a User modifies a Field Client ID within a Form task that is mapped to a DB Pull task, the modification is passed back to the DB Pull task Mappings and a toast message will appear to the User when accessing the DB Pull config to inform the User that a mapped update was automatically made

• 2113: Users with the appropriate permissions are now able to view Cancelled requests within in the View My Requests, Monitor Requests and Manage Requests filter dialog via a new “Request State” Filter option that is now available

• 2116: The Form Roles and Permissions screen has been updated to a Vue component

• 2160: The Grid Question now displays Column IDs within the Grid column configuration dialog that Users can reference in JavaScript for additional functionality

Fixes

• 1972: Within Task Configuration - Notification Settings, the yellow blocked Prefill Mappings are now displaying in body and subject line of the Notification

• 2176: When User creates a number field with the currency format is used on a Form task, the currency symbol and decimal for the currency yellow block Prefill is no longer missing within a Task Configuration - Notification Settings when configured/used in the subject line of a Notification

• 2185: Users are now able to view Form Questions via the Form Builder>Detail>Questions menu option for use when exporting to a JSON or CSV format

• 2190: The DataBase Task table no longer saves a new process task attribute record for a milestone task every time a User saves a diagram on the process canvas that contains a milestone task where the modified date is null in the process

6/5/2023