spot process separation studio 4 pre release

The model-level policies replace the default policies at object level. It is now possible to define data policies at model level. Being invited to the model package is not required as admin users can access all model packages.įor more information, please refer to Creating a named API client for the Bizzdesign Open API and Managing API client access to a model package. Managing API client access on the API client and model package pages requires the Administrator or System Administrator role. New API clients can also be invited to the package on this page, and their access to it can be revoked. The package overview page lists API clients that can access the model package. The access can be set on the API client's manage page in Horizzon.ĪPI client access to a specific package can also be managed via the model package overview page. To enhance security, access to model packages can be restricted by assigning an API client access to all packages or only specific packages. Previously, API clients defined in Bizzdesign Horizzon would have read and/or write data access to all model packages (and/or audit log access). For the latest API specification, please refer to Bizzdesign Open API.Īvailability: Cloud-hosted only Horizzon Server (), Enterprise Studio () New features and enhancements Data integration and contribution The Open API version 2.0 has been updated with this change. The endpoint has a new boolean parameter 'includeRejections' that, when true, will add information about the skipped links to the response. From now on, the bulk will no longer fail but will continue and skip any failing links. The OpenAPI bulk endpoint for creating/updating links would fail when one or both endpoints of a new link no longer existed, making the entire batch fail. When a model package contained defects of the kind 'objects without mandatory reference' and only of that kind, the Check and Repair command would claim to have repaired (deleted) those objects but afterward not offer the option to commit the repairs. Selecting objects in a view (or expanding layers in the model browser) in a model package not stored on a server would add unnecessary error messages to the Enterprise Studio log file.

The site link for a refined ArchiMate object copied in Enterprise Studio could point to a different object. Values in data fields of type object reference on the Contribute page were inadvertently displayed with a hyperlink, suggesting they could be clicked to navigate to the referred object.

Spot process separation studio 4 pre release