3.8.3 Illuminate Release

Modified on Wed, 7 May at 5:52 PM

TABLE OF CONTENTS

Version 3.8.3

Step Groups introduced in IDW 2.0’s Split Configuration module. Steps can now be grouped together and split on the same input.
Multiple If blocks can now be configured in IDW 2.0’s Actions module.
Code Functions can now be configured in IDW 2.0’s Data Mapping module.
Pagination module introduced in API creation flow.
Pre/Post path fields now available for non-IDW APIs.
List of affected IDW APIs will now be displayed when trying to modify IOValidations of an API.
Redesigned Package Migration UI.

Numerous security fixes and improvements.
Count of affected IDWs will now be displayed when unauthorizing an API being that is being actively used in IDWs.
Schemas can now be generated with JSONs containing inconsistent keys within objects.
Schema generation improved to handle arrays.
Improved efficiency and when performing migrations.
Migrations now run in the background, with progress being tracked in Migration Logs.
Improved performance of Process Flow & Rules page in IDW 2.0.
Independent steps now execute in parallel.
Updated list of available security questions.
Improved performance for API executions when back-end services are down.
Streamlined UI design of File Provider screen.
Leading and trailing spaces now trimmed when saving global variables.
Updated account creation/activation link to 24 hours.
Updated error messages to be more specific when configuring dependencies in IDW 2.0.
Confirmation popup will now appear when deleting a parent node in Template Center’s Design tab.
IDW 2.0’s Workflow Preview improved to handle complex workflows.
Added retry limits for Transactions to prevent unnecessary processing.

Multiple security fixes and improvements.
Fixed issues with String Functions in IDW 2.0’s data-mapping module.
Minor fix for Scheduler screen’s action icons.
Fixed issue where Certified Builds could not be undeployed due to the Default Consumer.
Fixed issue where configurations/jobs would still be active, viewable, and modifiable after relevant APIs are undeployed.
Fixed incorrect input fields in the File Provider page.
Fixed issue with global variable values not updating immediately, causing inconsistencies in the metadata.
Validation added to prevent path parameters and query parameters from having the same key in IDW 2.0.
Scheduler Job configuration page will now auto-scroll to fields that are throwing errors.
Fixed incorrect fields showing up and Next button missing in the Pre Dynamic Filtering page.
Fixed an issue with APIs incorrectly trying to authenticate using OAuth2.
Updated DND_Update_Jobs_In_Dkron to log failures instead of completely failing.

Fixed IDW 2.0 inputs failing validations due to their datatypes being implicitly parsed.
Fixes the issue of not being able to view or edit location level resource security settings
Fixes the issue of the Go Back button being hidden when the user brings the mouse over it
Fixes the issue of the log trace icon being greyed out even when log tracing is enabled
Updates the existing pagination configurations to fix errors in QA
Changes to prevent edit screen from breaking for APIs with pagination configurations after the update script
Fixed the old IDW issues and restricted edit popup to not show for deployed client APIs
Fixes the certified build global variables not recognized for client login in API Definition page
Fixed the display of Data mapping flows in IDW

Fixed IDMatch Dashboard failing.
Fixed staff login not being able to add new roles.
Fixes the issue of the Connections page not refreshing the url status for some clients
Fixes the issue of global variable values being formatted. For example - test&&test - test&&test.
Fixes the issue of users being misinformed about there being no APIs when all filters have been deselected within API Library
Fixes the issue of activation and password reset emails being sent for deleted/disabled users
Fixes the issue of users being prompted with security questions in the event of an expired password when there are no security questions configured
Fixes the issue of unwanted buttons showing up in the try it out screen for new IDW APIs
Fixes the issue of deleted packages being considered for services
Fixes the issue of APIs timing out for some clients

Changes to support APIs with same name, version but different types - GET/V1.0.0/returnPayload, POST/V1.0.0/returnPayload etc.
The screen displays Processing.... when it’s loading the OTP/Email change request verification screens

Fixed IDW 2.0 issue where children step’s back-end information were not being updated upon deletion of the parent step.
Fixed the issue duplicate records being created internally for schema related inputs and outputs.
Fixed the issue of characters being formatted unnecessarily on save and edit of global variables.
Fixed issue of FTP configurations not being displayed on edit of File-As-Source APIs.
Stopped the use of sending license expiry and sign up email alerts to sales@n2nservices.com
Fixes the display of special characters in Redeploy Confirmation screen

Fixes the issue of not being able to access the Try It Out screen for new IDW APIs
Fixes the issue of not being able to add Input XSLTS for PLSQL APIs

Newly designed Account Settings page.
Multi-Factor Authentication for Illuminate accounts is now available.
Announcements can now be configured to appear as a popup for all accounts upon logging in.

Fixed not being able to add profile pictures in Account Settings and Onboarding pages.
Only the main Illuminate account can now edit Location/Consumer Profile details.
Fixed some validations when adding new file providers.
Fixed an issue with split configuration creation

Fixes the issue of users receiving a blank error message when trying to do MFA for the first time
Remove the screen asking for client database credentials in the IIG Automation flow
Fixing the video page broken issue in login screen

Fixes the issue of installation instructions and other resources not being displayed for a new IIG version setup
Fixes the issue of users not being able to add/modify the Input Format for APIs when they have input schemas configured