IC 3.7.4 Release Notes

Forms change over time. Questions get reworded, options get updated, and fields that no longer apply get removed. Until now, those edits could change how older responses looked or hide answers altogether. For teams that rely on form responses as a record, such as HR requests, incident reports, or policy sign-offs, that made editing a live form risky.

Starting with 3.7.4, each response keeps the form exactly as the person saw it when they submitted it.

What stays the same on past responses:

• Field labels. If you rename "Branch" to "Location," older responses still show "Branch."
• Deleted fields. They are removed from new submissions only. Older responses still show the answer with its original label, marked as removed.
• Removed options. If you take an option out of a dropdown or radio list, responses that used it still show the original answer.
• Field order and required settings. Reordering fields or making a field required changes nothing on responses already submitted.
• New fields. Responses submitted before you added a field simply show it as blank, with no errors.

Requests already in approval are covered too. Approvers still see, and can edit, every answer as it was submitted, including answers to fields you have since deleted. Routing rules based on a deleted field still send the request to the same next step.

Your reporting stays complete. The responses grid and exports include a column for every field that appears in the responses you are viewing, with removed fields clearly marked, so nothing drops out of a report because the form was edited.

You'll know before you save. When you save changes to a form that already has responses or requests in approval, a short note tells you how many there are and confirms they keep their answers. Forms with no responses save as they always have.

Why it matters: if an auditor or examiner asks what someone was asked and how they answered, the response shows exactly that, however much the form has changed since.

Editing a workflow no longer quietly affects requests that are already moving. Requests in progress carry on under your updated workflow. If your change removes the step a request is currently waiting on, you'll get a warning showing how many requests are affected before you save, and you can cancel. If you go ahead, those requests go back to the person who submitted them with their answers intact, marked as declined by the system with the reason "Workflow updated," so it's easy to tell them apart from a decline made by an approver. You can filter and export by who declined a request.

Changing the approver on the step a request is currently on now reassigns it and notifies the new approver, and the previous approver's email link stops working. Completed steps keep their original approver and date.

Also fixed:

• Managers now receive an email when a request is routed to them through a Direct Manager approval step.
• Approvers no longer see a "Sequence contains no elements" error when submitting a form.

App Feed items can now show the full article, not just a summary. The "Show Description" setting is now "Show Body Content," with a choice between the item's description or a rich text (HTML editor) field. With the rich text option, articles such as blog posts and knowledge base pages read in full on the homepage, with their formatting and line breaks. If an app has more than one rich text field, you choose which one to use for each app. Apps without a rich text field show the title and description.

Each item now shows more at a glance. Attachments appear as downloadable chips under the item (on by default, and you can turn them off). The posted date and author use one consistent format across widgets, showing "2 days ago" style dates for the first week and the full date after that. Where the item lives now sits on its own line and links straight to that site, app, or folder.

Adding content from the homepage is quicker. When every folder a widget pulls from belongs to one app, admins and site owners now see a + button to add content and a More link to go to the app. This works on any widget that pulls from an app, not only App Feed. If one folder is selected, + takes you straight to adding content there. If the widget's header is hidden, the buttons appear when you hover over the widget.

The widget settings are clearer. A note under Source Folders updates as you pick folders and explains what your selection allows, such as whether quick add will be available. If reactions or comments are turned off in one of your selected apps, you'll see a single note saying so. Sort options are now Most Recent and Random. Alphabetical sorting has been retired and existing widgets using it are updated automatically. New widgets are titled "App Feed" by default and can be renamed.

Also fixed: folders in apps with more than 100 documents no longer show "No Content to Show" in the App Feed widget.

Published blog posts from IC 2 now move into IC 3 as part of your migration, together with their comments. Reply threads keep their structure, and comments written by people who are no longer on your intranet keep the author's name. Drafts and scheduled posts that were not yet live are not migrated. Paired with the new full-article view in App Feed, your blog content can be read right on the homepage.

You now have more room on employee cards. Photo, name, and job title always appear and no longer count toward your limit, so you can choose up to five additional fields to show. Extension is now a standard profile field that can sync from your directory, appear on cards, and show in search previews.

Also improved:

• Admins can now edit custom profile fields on any employee's profile, even when "Allow employees to edit this field" is turned off. Employees editing their own profile still follow that setting.
• The Org Chart now uses a light grey background so employee cards stand out.
• Scrollbars in the Birthdays and Workiversaries and Employee List widgets now line up with the edge of the widget.

Search results now only include items each person has permission to view, and people no longer see "not authorized" messages while searching.

This release includes security improvements identified through independent security testing. We strengthened server-side permission checks so that settings, user login details, and attachments can only be viewed or changed by people with the right access. We also removed technical detail from error messages and tightened how the site loads outside resources. A related fix makes sure a document always has exactly one current version after an attachment is moved.