Workspaces API release notes

1.6.0

• Added new internal endpoint to get an optionally non-paginated list of workspaces. Allowing services to get all workspace ids in a single GET request.

1.5.0

• Addition of new get endpoint for organizational settings. Allowing org level setting of ml_enabled.

1.4.0

• Added additional users fields (users_list and users_map) to users model to imrpove performance.
• Updated queries to improve performance

1.3.1

• Admin list workspaces endpoint update response. created_by and updated_by field will now contain user ID, user name, and user email.

1.3.0

• Added endpoint for admins to set a new ml_enabled flag on workspaces. This feature is available in preview mode and requires header Preview-API: opt-in to be set.

1.2.20

• The "list workspaces" endpoint now accepts created_at and updated_at as search filters

1.2.11

• Bentley IMS co-administrators may now act as Evo admins

1.2.0

• Added support of assigning the role to the user by email. This feature is available in preview mode and requires header Preview-API: opt-in to be set.
• Added endpoint for restoring soft deleted workspaces.

1.0.0

• Migrated from Seequent IDP to Bentley IMS for authentication.
  • Still supports Seequent tokens by looking for the user in the Bentley IMS.
  • All stored user/organization IDs are switched to Bentley IDs.
• Migrated from Seequent IDP user cache to Bentley IMS user cache for user lookup. This means user information (name, email, etc) will be retrieved from Bentley IMS.

Breaking changes

• Assign/delete user role endpoints will no longer accept Seequent IDs, those endpoints will only work with valid Bentley IDs.

0.0.194

• New query parameter order_by is introduced for "list workspaces" endpoint. Query parameter sort is deprecated and will be removed in a future release.

0.0.192

• filter[name] is deprecated and new filter by name is introduced. Previous filter will be removed soon.

0.0.184

• Client SDK now has less strict versioning requirements. Now only ensuring no major version increase above minimum versions.

0.0.182

• A client SDK is now available for the Workspaces API

0.0.179

• The field default_coordinate_system now supports WKT2 (Well Known Text) strings in addition to EPSG codes

0.0.178

• Added 410 (resource is gone) response in the API schema for target endpoints

0.0.172

• Bounding box [optional] needs to be a geoJSON of type Polygon with one exterior ring that represent the bounding box

0.0.171

• Users with "viewer" role can now delete themselves from workspaces
• New endpoint for Evo admins to add users to workspaces within a bulk request
• New endpoint for Evo admins to list the workspaces to which a specific user has access

0.0.169

• Admins can give permissions to multiple users in multiple workspaces just by one request. The new endpoint is /workspace/admin/orgs/{org_id}/action/bulk_assign_roles
• A new /workspace/admin/orgs/{org_id}/users/{user_id}/workspaces admin endpoint implemented that lists workspaces accessible by specified user along with that user role in each workspace.

0.0.165

• When retrieving workspaces, the user details are provided as well for the created_by and updated_by fields

0.0.164

• Default coordinate reference changes
  • The values set for the default coordinate reference systems are now validated against the list of valid EPSG codes
  • A new /coordinate-systems endpoint implemented that lists the valid EPSG codes tree

0.0.151

• Validate existence of an user in IDP during role assignment

0.0.1 - 0.0.150

The current workspace service version 0.0.150 includes workspaces, user roles, and thumbnails. You can make requests to the workspace service according to its API specification.