nx1-deployer image
v1.16.1New features
This section contains new features recently added to the NexusOne platform.Business rules
Business rules is a new item under Catalog & models for the decisions your systems make from data, such as a loan applicant’s risk tier. You build a rule, get it approved, and publish it for your code or a Trino or Spark query to call. Rules live in workspaces, which are project-like folders with their own members. Access to the feature has two layers:- NexusOne role: Lets you reach the feature on the portal or its API endpoints.
nx1_decisions_user: Reach the endpoints. What you can do then comes from your workspace role.nx1_decisions_admin: Manage every workspace in NexusOne, including creating new ones.
- Workspace role: Decides what a
nx1_decisions_usercan do in a given workspace.approver: Everything a simulator can do, plus approve, reject, and publish versions. Can’t author.author: Everything a simulator can do, plus create rules, edit drafts, submit for approval, and import or export bundles.simulator: Everything a viewer can do, plus evaluate and simulate rules.viewer: Read rules and their audit history.workspace_admin: Everything an author can do, plus publish versions and manage members. Can’t approve.
Audit
Audit is a new feature under Govern for searching NexusOne’s audit records. The records cover who accessed what data, who called its APIs, and who changed a business rule. You need thenx1_audit_viewer role to reach Audit, on the portal or through its
API endpoints.
Enhancements
This section contains enhancements to existing app features on the NexusOne platform.Elyra pipeline editor in JupyterHub
JupyterHub now includes the Elyra pipeline editor. You drop notebooks and scripts onto a canvas as nodes, connect them into a pipeline, and run it. NexusOne compiles the pipeline into an Airflow DAG, and Airflow runs each node as its own pod, with its own resources, retries, and history. Elyra also adds a Code Snippets panel and standalone Python, R, and Scala script editors. The editor is for iterating on pipelines, not for governed production, so a pipeline built here has no lineage trail, approval step, or versioned rollback. To promote one to production, register it as a Notebook pipeline app via the App Manager feature. You need thenx1_jupyterhub_elyra role to use the editor. You can launch JupyterHub from the portal, as described in
Launch a hosted app.
