RSS Feed
ATTN: Inquisiq SaaS Downtime
Posted by Jessica D'Apice on 25 April 2018 02:15 PM

(If you are utilizing an ICS-hosted or on-premises Inquisiq solution, you may disregard this message.)


Hello Inquisiq SaaS Clients!

The latest version of Inquisiq will now handle courses in a more secure fashion to ensure that your courses may only be accessed by your users logged in to your system. To implement this change, along with several other improvements, all Inquisiq SaaS portals will be down and inaccessible from Sunday, April 29th at 8:00 PM EST to Monday, April 30th at 12:00 AM EST (4 hours of downtime).



  • Inquisiq SaaS will be down from Sunday, April 29th 8:00 PM EST thru Monday, April 30th 12:00 AM EST
  • This update fixes several issues and improves the way courses are handled on the back-end. This change will not affect the way that you upload and publish content. Your processes will stay the same, and everything from your perspective will still look and feel the same.
  • After the downtime, if you use to sell courses, update your E-commerce Processing Method to “Authorize.NET (Accept.js)”
  • Update to the new “Sweet” Theme for mobile responsiveness, improved workflows, less clicks, and less/shorter page-load times!


Here are some more detailed notes on what to expect after the downtime.



Several of these fixes have already been implemented and are already live on your system, but here are all of the changes and fixes between the first release of this version of Inquisiq, version, to the latest version,, which will be pushed April 29th:


  • Changed integration method from deprecated DPM method to Accept.js method.
  • Changed the way content is stored and handled to prevent course launch outside of the LMS.

Bug Fixes:

  • Fixed an issue where the use of the Forgot Password link was causing user profile data to be cleared.
  • Fixed an issue where the system was attempting to grant certificates for courses that did not have certificates, and therefore throwing errors.
  • Fixed an issue where certificates that were awarded through activity data imports were not correctly attributed to the person who uploaded the activity data.
  • Fixed an issue where a portal’s global non-HTTPS forward to HTTPS process was re-directing without forwarding the data. The global non-HTTPS to HTTPS will now be bypassed for API calls and properly utilize the API setting for allowing HTTP or HTTPS.
  • Fixed an issue with certificate data imports where multiple rows for the same user and same course codes with different timestamps threw an error, and the error was displayed incorrectly.
  • Fixed an issue where the user’s My Account page’s Progress analytic counted enrollments that had not started yet as a result of recurring enrollments that were to create future enrollments.
  • Fixed issues with translations of conclusion slides and “Submit” and “Done” buttons in lessons created in the built-in quiz/survey authoring tool.
  • Fixed an issue where the enrollment expiration dates were not appearing under the Learning Activities section of the user’s My Account page.
  • Fixed an issue where coupon codes that applied to specific catalogs were not working.
  • Fixed an issue where the last column on the User Batch page was listed as AW, when the last column in the batch upload is actually AS.
  • Fixed an issue where hovering over an expired enrollment’s Go button showed an untranslated tag.
  • Fixed an issue where new users created by the administrator using the New User button are initially unable to be impersonated.
  • Fixed an issue where the Access Period on the course launch page was listed incorrectly.
  • Fixed an issue where profile records of Supervisors whose profiles had been deleted were not being cleared from their supervisee’s profiles.
  • Fixed an issue with printing certificates in the Microsoft Edge browser.


AUTHORIZE.NET CHANGE is in the process of deprecating the DPM integration method, in favor of Accept.js, a JavaScript-based solution for sending secure payment data directly to They will soon be announcing an official end-of-life timeline for the DPM method. In preparation for this, we have already switched Inquisiq to the new Accept.js method.

If your e-commerce feature is currently utilizing the (DPM) processing method, after the down-time this weekend, you will need to change the method to Accept.js. From your Administrator Menu, click E-Commerce, and from the “Processing Method” drop-down, select “Authorize.NET (Accept.js)”, re-enter your account information, click “Save Changes,” and if the status does not say “Verified,” check your account information, and click “Save Changes” again.



Controlled only by ICS Support Staff in previous versions of the software, the concept of interface-controlled Themes was introduced in Inquisiq version, and it will carry over in this update. There are two Themes (or layouts) that will no longer be supported after this update: 2014 and Classic.

If you are on either the “2014” or “Classic” Themes, your portal appearance will not immediately change after this update. However, you will need to switch your theme to either the R4 Theme or the “Sweet” theme, as the “2014” and “Classic” Themes will both be completely eradicated with the next release. (If you are unsure of which Theme/layout your portal is currently utilizing, contact ICS Support at and we will verify for you.)

The update will still include the new “Sweet” theme. This new theme improves workflows (less clicks, less page loads, more intuitive interface), increases mobile responsiveness, and has a sleek, updated feel that we know you and your users will love! You can update your theme by going to your Administrator Menu and clicking on Theme in the Interface section. Under “Styling”, select the “Sweet” Theme (2017), select your preferred color (controls the colors of the tops of the portlets/sections), and then click “Save Changes.”

CSS NOTE: If you have any custom CSS on your portal, you will most likely need to make changes to this CSS in order to reflect the changes that you desire correctly in the new theme. Your best bet will be to clear out any changes you have made via CSS and start from scratch.

Due to the new version of Inquisiq's focus on mobile responsiveness, the “Sweet” Theme’s masthead has been greatly simplified from previous Inquisiq layouts so as not to take up too much space on mobile devices with smaller screens. The new "Sweet" masthead is simplified and out of the way to keep the focus on the content.

The new masthead allows you to upload one small logo image on the left side, and then allows you to choose three colors that blend into one another across the masthead. There is no longer the allowance to add a right-side image, nor a background image. This has been done to simplify and reduce the size of the masthead for the best possible end-user experience across all devices.

When making changes to the colors in your masthead, after you click "Save Changes," CLEAR YOUR BROWSER'S CACHE in order to see the changes live in your masthead. Your end users will need to clear their browser cache to see any changes to the masthead colors, as well.



If you have any questions, concerns, or comments about anything described above, or anything else pertaining to your Inquisiq SaaS account, please go to and submit a ticket. We at ICS Learning Group Support are always happy to assist in any way that we can!

Read more »

ATTN: Inquisiq Remote Installations - Changes
Posted by Jessica D'Apice on 19 February 2018 08:12 AM

If you…

  • are using Inquisiq installed remotely on your own server
  • have integrated your account into Inquisiq
  • are using TLS protocol 1.0 or 1.1

… this information pertains to you. Otherwise, please disregard.


Background: Transport Layer Security (TLS) is a technology used to encrypt sensitive information sent via the Internet. TLS is the replacement for Secure Sockets Layer (SSL). New PCI DSS requirements state that all payment systems must disable early TLS by June 30, 2018.

What You Need to Know: plans to disable TLS 1.0 and TLS 1.1 on FEBRUARY 28, 2018. They have disabled the sandbox in advance of production to allow time for testing to ensure that you completely phase out TLS 1.0 or 1.1 by February 28th, 2018. Inquisiq DOES support TLS 1.2 for the API connections, so we are already ready for this transition.

Note that if you are not using the current version of your web browser, you should upgrade it as soon as possible, as browsers released prior to 2014 may not support TLS 1.2. You can check your browser’s TLS support by visiting


If you have any questions about this topic, please visit’s FAQ page here:

You can reach support with specific questions at (877) 447-3938.

Read more »

Asentia Release 1.11
Posted by Jessica D'Apice on 14 February 2018 10:33 AM

Asentia Release 1.11


New Features:

  • Added mini-analytic dashboards to user, course, learning path, and content package grids to display aggregate data about those objects.
  • Added an “online” indicator to users in the user grid to allow an administrator to determine whether a user is currently logged into the system.
  • Added “Supervisor” field to transcript reports.
  • Added the ability to query “enrolled” or “waitlist” users in ILT transcript reports.
  • Added the ability to re-zip and download content packages.


  • Modified the Administrator Menu to display administrator options in a more workflow friendly layout.
  • Moved User Field Configuration to the System category of the Administrator Menu.
  • Modified object listing grids to display more information about an object as well as provide shortcut buttons to more commonly used functions of an object.

Bug Fixes:

  • Fixed an issue in Quiz/Survey packages where the exit button on the Quiz/Survey does not exit properly.
  • Fixed an issue where placeholders used in Email Notifications are automatically appended to the end of the text as opposed to where the cursor is.
  • Fixed an issue on the User Enrollment Activity Page where entering a score less than 100 rounds the score to either 0 or 1.
  • Fixed an issue where only one report filter could be added to a report in IE11.
  • Fixed an issue with downloading calendar files in IE11.
  • Fixed an issue with updating completion status of a user’s enrollment in IE11.

Read more »

Server Requirements for Inquisiq Installation Updated
Posted by Jessica D'Apice on 02 February 2018 12:18 PM

*As of January 2018, Inquisiq's minimum server requirements have changed. Any installations/upgrades from version onward will adhere to these requirements.*

Note that you may install the Inquisiq™ application and your database software on the same or different servers. If you install them on the same server, then be sure that the server meets the minimum (or recommended) requirements listed below and the minimum (or recommended) requirements of your database software as well as a reasonable buffer (i.e. running both on the same server that only meets the minimum requirements of one may not have enough resources to run both).

Applies To:

Inquisiq LMS Version and later.

Minimum Supported:

  • Dual Processor @ 2.0 GHz
  • 4 GB RAM
  • .NET Framework 3.5 Service Pack 1
  • Microsoft Windows Server 2008 R2 (x64) (Standard Edition)
  • Internet Information Services (IIS) 7.x
  • Microsoft SQL Server 2008 R2 w/Service Pack 2 (Workgroup Edition)


  • Dual Processor @ 2.0 GHz or higher
  • 8 GB RAM
  • .NET Framework 3.5 Service Pack 1
  • Microsoft Windows Server 2012 R2 (x64) or later (Standard Edition or higher)
  • Internet Information Services (IIS) 7.x
  • Microsoft SQL Server 2014 or later (Standard Edition or higher)

Other Required Software and Services:

  • SMTP Service running or access to an SMTP server (for email capability)

Important Notes:

  • Inquisiq is not supported on 32-bit Server Operating Systems.
  • Inquisiq is not supported in shared server environments (such as those running Plesk, CPanel or other control panel management software).
  • Due to the "virtual site" capability of Inquisiq and its domain name based routing, it must be installed in the root folder of its own website on a dedicated IP unless otherwise recommended by technical staff.

Browser Requirements:

No more security alerts, plug-in installs or help desk calls because Inquisiq LMS has been designed with compatibility in mind. The latest browsers have converged on the XHTML standard allowing Inquisiq LMS to be universally accessible by both PC and Macintosh clients. In addition, our unique approach to the server communication issue has allowed us to avoid browser plug-ins that so often cause implementation problems in highly-secured client-server environments.

  • Google Chrome
  • FireFox
  • Microsoft Internet Explorer 10 - 11
  • Microsoft Edge
  • Safari 10 (OS X/macOS)

Important Notes:

Content that you load into the Inquisiq LMS may have additional requirements not listed here. Be sure to check the requirements of your authoring tool or with your content developer.

Read more »

Asentia Release 1.10.5
Posted by Jessica D'Apice on 07 December 2017 05:04 PM

Asentia Release 1.10.5

New Features:

  • Added a searchable “documents widget” to the dashboard that allows a user to search the system for documents they have access to. These documents consist of files attached to Groups/Communities the user is a member of, materials for Courses/Learning Paths the user is enrolled in, and materials marked as public for Courses/Learning Paths.
  • Added the ability to run reports on Certifications.
  • Added the ability to attach files to user profiles.
  • Added an email notification for “Message Center” message received.
  • Added the ability for portals with more than one language installed to detect the user’s preferred browser language and automatically switch to that language.


  • Modified the Administrator Menu to open on rollover instead of on click.
  • Modified the User Registration and User Modify pages to display in sections instead of tabs for user data.
  • Moved User Field Configuration from Users & Groups to System menu.
  • Modified the Role Manager permission so that it controls access to assigning roles, in addition to creating/modifying them. Prior to this release, the ability to assign roles was under the User and Group Manager permissions. The Role Manager permission was also modified to only be assigned to the built-in “System Administrator” role.
  • Added the ability to remove avatars from Users, Groups, Courses, and Learning Paths.
  • Added the ability to duplicate ILT sessions.
  • Added the ability to have more than one “organizer account” for GTM, GTT, GTW, and WebEx integrated ILT sessions.

Bug Fixes:

  • Fixed an issue with some Activity Data records being duplicated upon import.
  • Fixed an issue with sort order in Pending User Registration and Pending Enrollment widgets.

Read more »

Changes to Flash Settings in Chrome 62
Posted by Jessica D'Apice on 15 November 2017 12:19 PM
Chrome is making it harder to run Flash. In Chrome 62, you either have to enable or disable Flash completely, or have to allow Flash per website.
To enable/disable Flash in Chrome:
  1. Click the menu option in the top right corner of the Chrome window (three dots aligned vertically).
  2. In the drop-down, click "Settings."
  3. Scroll down to the bottom of the page and click "Advanced Settings."
  4. Click "Content Settings."
  5. Click "Flash."

Turn "Block sites from running Flash" OFF to ENABLE Flash.

Turn "Block sites from running Flash" ON to DISABLE Flash.

To allow Flash for individual websites:
  1. In Chrome's Flash settings, enable "Ask first".
  2. Go to the Flash website.
  3. Click "green lock" icon or "i in circle" icon at the left side of address bar.
  4. In the menu, choose "Always allow on this site" for Flash.
  5. Reload.
If the content contains Flash plugins smaller than 400px x 300px, they will always be blocked. You will need to click the "plugin blocked" icon in top right corner and click "run all plugins this time".

Something rather important worth mentioning, all browsers will stop supporting Flash altogether by then end of 2020, as announced by Adobe themselves: 

Flash has long been known for its instability and security issues. With the introduction of HTML5 as a more secure mark-up language for structuring and presenting content on the internet and its subsequent rise in popularity, HTML5 is being chosen over Flash as the preferred content delivery method, and Flash is being phased out.

We highly recommend that you start preparing now. You will need to start re-publishing your courses to HTML5. You have until the end of 2020, but having a head start is better than having to scramble to re-publish all of your courses at the end of 2020. Republishing your courses, depending on your library size, may take time, but it will be well worth it as the movement away from Flash becomes permanent and widespread.

Read more »