How can we help you today?

Release Notes | Daylight On-Site v.1.7 | 2019-01

Modified on: Wed, Aug 28, 2019 at 3:43 PM


Onsite Bugfixes:


Issue: Daylight doesn't use correct SMTP settings when sending emails

Details: Settings saved in the "Configure SMTP" form wouldn't actually take effect, so Daylight failed to send emails (such as user invitation or password reset emails). This was caused by an incorrect configuration file, which was hard-coded to use the mailserver we use in the office.

Fix: The configuration file now has Daylight talk to a mail server running in the VM, which forwards mail to whichever SMTP server the user configures.

Issue: Junk showing up in Admin Email Address field of Configure System Notifications form

Details: If you went to the "Configure System Notifications" form and entered an admin email address (for example "someone@luminoso.com"), then that email address would show up in subsequent visits as "someone@luminoso.com on { resource }". This was caused by the configuration menu code incorrectly parsing part of a configuration file as if it was part of the email address.

Fix: The configuration menu now only reads in the part of the config file that contains the email address.

Issue: Network interface settings lost on reboot

Details: Settings saved in the "Configure Interface" form would be lost when the system was rebooted.

Fix: When changing settings, the system updates the network configuration file to automatically start static network interfaces on boot.


Onsite New Functionality


Feature: Support for password-protected TLS keys

Details: In the "Configure HTTPS" form, there is a new field labeled "Key Password". This will allow you to use a PEM file which requires a pass phrase, as requested by a customer some months back.


Feature: More flexible configuration around SAML signing preferences

Details: There are two new checkboxes in the "Configure SAML" form: "Require SAML Response messages to be signed" and "Require SAML Response assertions to be signed". By default, our SAML provider is set up to expect both messages and assertions to be signed. However, we discovered that Amazon's identity provider was set up to sign assertions but not messages. Now, if a customer encounters this situation, they can change the configuration on our end to expect only one or the other to be signed.

(Note that at least one of these checkboxes MUST be checked, as going without signatures altogether is insecure).


Feature: Option to grant account_manage permission to Onsite users

Details: In addition to giving users read, write, and create permissions, you can now also give them account_manage permission, which allows them to invite other users into an account and handle some user management for themselves.


Feature: Slightly easier configuration of user permissions in Onsite

Details: Previously, there was a separate checkbox for each permission ("read", "write", and "create"), and you had to explicitly check all the permissions you wanted to give someone. However, giving someone a higher-level permission without giving them all the lower permissions would generally result in confusing misbehavior from the system when they logged in.

Now, the system only lets you select one permission, and each permission automatically includes all the lower ones. For example, if you give someone write permission they'll automatically have read permission as well. If you give someone account_manage, they'll automatically have read, write, and create.


Cloud version New Features, Functionality, and Bugfixes

In addition to the above onsite-specific features and bugfixes, the new release also incorporates everything that has been released to the cloud version of Daylight through January 5, 2019.


Bugfix:

Issue: New msgpack in production renders some large projects unusable

Bug Error Message: When attempting to open a project that creates a list that is too long, "An internal error occurred; contact Luminoso for assistance."

Reason: msgpack 0.6.0 replaced msgpack 0.5.6 on November 30 (https://github.com/msgpack/msgpack-python/blob/master/ChangeLog.rst). Among the changes that went in was a drastic lowering of how long an array can be, to prevent DoS attacks--specifically. Arrays can now only be 131,072 elements long, instead of as much as 2,147,483,647 elements long. Projects in that have more than 131,072 values for a particular piece of string metadata which msgpack 0.5.6 now refuses to decode because of the number of elements. 

Fix: The fix was providing an argument to `msgpack`, when unpacking, that told it to allow much longer lists, around 20 million.


New Features

Feature: Concept info bar in the Concept cloud has been eliminated

Functionality: The concept search box and the concept match count figures have moved to the top of the concept detail pane (screenshot below)

Details:

  1. The user can still select concepts in the ways they could before this change
  2. The "Save concept" button has moved along with the concept search box and "selected concept" over to the top of the concept detail pane



Feature: concept detail pane

Functionality: Make concept detail pane sections collapsible and additional enhancements

Details:

  1. The individual sections of the concept detail pane are now collapsible, following a design pattern similar to the filter selectors (screenshot below).
    It should not be possible to collapse all sections of the concept detail pane. If all but one are collapsed the last one should not allow the user to collapse it.
  2. The "Download matching documents" button is now a download icon button (shown below), with a tooltip that reads "Download matching documents".
  3. The "New project from documents" button will be a button below the list of matching documents excerpts. It is outside of the scrolling list of documents so the user can't scroll it away.



Feature: Concept Compare

Detail: The concept compare tool has reached feature complete with the addition of the completed concept details pane

Feature: Score Drivers - beta

Functionality: Expose the score driver icon in the left navigation bar (mocked-up screen shot below) and the score driver tool. Beta status indicates that this feature has achieved MVP, but is not yet functionally complete.  

Detail: Added the concept detail pane to the score drivers tool. Score drivers beta is automatically active for on-site users. 

Interactions for the Score driver tool
Adding the existing concept detail pane within the Score Drivers tool will provide enough additional detail for users to understand the context of concept-drivers.
Users can select concepts driving their score, for further discovery, in two places:

1) By clicking on it in the concept's scatter plot dot.
2) By manually searching for it in the concept detail pane's search box.

When the concept is selected:
1) If it is already visible in the scatter plot it should be visually highlighted (as shown in the mocked-up screenshot).

If a concept is not already present in the scatter plot, but is a driver, it will show in the scatter plot in a highlighted state.



Functionality: Add "score_"  type as a supported data type for metadata within a data set

Details: Because a user's data can have more than one metadata column of numeric data, the score_  data type allows the user to identify which column is identified as the score. If the user does not identify which numeric column represents the score the user will be prompted to choose it before Score Drivers are calculated.

Functionality: Only display the top 50 suggested score drivers

Details: Limit the number of score drivers displayed to the top 50.

Functionality: Remove top concepts from Score drivers select concepts dropdown

Details: "Suggested drivers" is the new default for the tool. Top concepts may not be project score drivers and therefore it does not make sense to use "Top concepts" in the score driver tool. The score driver science determines the top suggested drivers.

Functionality: Elimination of hashes from UI routes

Details: To effectively implement UI improvements improved UI analytics need to be collected, this is not possible with the existing hash routing. The UI API URLS must be switched to historyAPI routing.  

All routes which start with `/app/#/` should instead simply start with `/app/` (ex. `/app/#/upload` should become `/app/upload`).

There should be a redirect from the hash route to the non-hashroute. This can be done client-side.

In order for the client-side routing to work, the server will have to be altered so that it serves `dist/app/index.html` for every page request under `/app`.

Affected field customer-facing scripts:

tableau_export
copy_topics
load_topics
diff_analysis_exports
remove_foreign_lang

Required action: If your customer are using any of the affected scripts, contact Submit a Ticket for updated scripts 

Feature: New Language

Detail:  Bahasa Indonesia has been added to the platform and will be available as a language option during project creation.

Notes on the name Bahasa Indonesia

We intend to standardize the language name as "Bahasa Indonesia" in our communications about this new capability.

We refer to most of our languages by their standard name in English. This seems so obvious that we wouldn't need to write about it. If you're talking about French you say "French". The alternative is using the language's name used by its speakers. Generally, you wouldn't do this. It would be weird and snooty to drop the word "français" into an English sentence.

That seems like it should be the end of the story, but there's an exception regarding our newly supported language. Many sources that standardize this kind of thing agree that its English name is "Indonesian", and its name in its own language is "Bahasa Indonesia".

Many people find the language name "Indonesian" jarring, and expect to hear it called "Bahasa Indonesia", even in English. This expectation is particularly held by speakers of the language, which gives it some extra credibility. We favor the name "Bahasa Indonesia" because it seems to be what our customers expect.

Note that the language name is not "Bahasa". That's just the word that means "language". For example, the word for "English" in Bahasa Indonesia is "Bahasa Inggris".

Acceptable names to use for this language:

  • heavy_check_mark Bahasa Indonesia
  • Indonesian

Some wrong names not to use:

  • no_entry_sign "Bahasa Indonesian"
  • no_entry_sign "Bahasa-Indonesia"
  • no_entry_sign "Bahasa (Indonesia)"
  • no_entry_sign "Indonesian (Bahasa)"
  • no_entry_sign "Bahasa"


Feature: Reporting 

Enhancement: Include date in subject line of all usage reports

Functionality:New Monthly Cadence Billing Report

Details: Tab 1 contains Billing Summary: List of all accounts in Daylight with their calculated metering broken down by month. Ordering should be current month completed going back until the end of the clients current billing period with total. Tab 2: contains the Monthly Billing Detail:
For the current month, by account and then by user, and audit trail of all activity that contributed to metered usage for all accounts, expect multiple rows per user where good activity is occurring. 


Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.