Release Notes v8.28

What's new?

• Support optional "preprocessing script" in import objects. Users can select a preprocessing script from a dropdown that includes some built-in scripts, such as for a Claims Reduction File (CRF), along with any of the bespoke models that have been created in the Advanced Analytics zone. These scripts are meant to transform the selected file to CSV or related format, after which the rest of the import workflow will function per usual.
• Add custom action to migrate all value sets and lookup tables in a namespace.
• Add custom action to migrate all objects, measures, and reports in a namespace. The user will be able to supply find/replace strings both for asset names (i.e object name, report name, or measure identifier), as well as for object table names.

What improvements have been made to existing features?

• Bump Ubuntu to 24.04 and NodeJS to v22, along with many open-source dependencies to current.
• Support module namespace de-collision for customer promotion of packages. If a customer wants to promote, for example, their URSA-CORE assets from a dev environment to a production environment, we want them to be able to do so without it colliding with the URSA-CORE assets that we maintain in the Ursa Library. Within the Global Variables screen in Metadata Manager users should set their Module Submission Prefix in their dev environment to a unique code, and they should set their Module Import Prefix in the production environment to the same unique code. This will create an alternate naming convention for the Ursa Library, while otherwise being mostly invisible to the app.