Release Notes v5.36

What's new?

• The URSA_MEASURE_SCHEMA environment variable has been folded into the URSA_SCHEMA environment variable and is no longer necessary for deployments.
• Ursa Studio administrators will be able set a user's hidden namespaces, which represent the namespace whose objects and measures that the user is not authorized to view the contents of. Changes to a user's hidden namespaces will appear in the privilege escalation log, and will automatically log the user out of any current session to enforce the change to their authorization.
• Users will be blocked from seeing data from objects and measures in hidden namespaces. They will also be blocked from editing objects and measures in hidden namespaces, or invoking objects in hidden namespaces while working with other objects and measures. Users can still view and edit measures and objects in unprotected namespaces that already invoke hidden objects; they are only blocked from adding new upstream hidden objects.
• This allows data from sensitive namespaces to eventually flow into unprotected namespaces, but the only users capable of setting up such a data flow are users who themselves have access to the sensitive namespace. All redaction logic should happen in an object in the sensitive namespace, because once that object is invoked in an object or measure in an unprotected namespace, users can, for example, change the fields from the protected object that are published into the downstream unprotected object or measure.
• LOOK UP VALUE SET USING CLUSTER pattern.

What improvements have we made to existing features?

• The Table Dashboard CSV export will show the raw measure values instead of rounding large numbers as they are formatted onscreen.
• New boards will default to being shown on the leftnav in Analytics Portal.
• Added "Twelfths of Year" timing option to the ELAPSED TIME pattern, which, unlike months, does not try to correct for the variation in month length. For example, "Twelfths of Year" considers the distance between January 1 and February 1 to be 1.02, not exactly 1.