Changes

Changes in (JCSM72-0290-01(E)) JP1 Cloud Service/Operations Integration 02-90

Additions and changes Location
By collaborating with your AI agent, tickets can be managed and Ops I definitions can be created and edited efficiently. 1.5
Added the query parameters "filterBy" and "sortBy" to "GET /api/v1/gitops-logs" in Standard API functions (v1). 2.1.1
Changed the upper limit of the "pageSize" query parameter for "GET /api/v1/practice-contexts" in Standard API functions (v1) to 10,000.
Changed the upper limit of the "pageSize" query parameter for "GET /api/v1/users" in Standard API functions (v1) to 1,000.
Changed the upper limit of the "pageSize" query parameter for "GET /capi/v1/tickets" in Custom API functions to 10,000.		 2.1.1, 2.2
Added filtering, sorting, and pagination features to the "GET /api/v1/import-jobs" API. 1.4, 2.1.1
Added "params" to the response of the "GET /api/v1/practice-contexts/{id}" API.
This change allows you to reference parameters specified during workflow execution.		 2.1.1
Added "params" to "dtos.ContextDTO". 2.1.1
Added "customers" and "groups" to "dtos.CategoriesDTO". 2.1.1
The response for the "GET /api/v1/service-catalogs" API now allows you to reference the following:
  • Parameters specified at runtime
  • Groups granted access
  • Customers granted access
 2.1.1
Added "PATCH /api/v1/practice-contexts/{id}" to Standard API functions (v1). 1.4, 2.1.1
The "GET /api/v1/practice-contexts" and "GET /api/v1/practice-contexts/{id}" APIs now allow you to retrieve the following properties:
  • description
  • category
  • dueDate
  • note1
  • note2
  • note3
This change allows you to retrieve information from the additional columns displayed in the workflow list. 		2.1.1
Added "DELETE /capi/v1/tickets" to Custom API functions. 1.4, 2.2
Added "DELETE /api/v1/practice-contexts" to Standard API functions (v1). 1.4, 2.1.1
Enabled the retrieval of the "Customer" to which a user belongs via the "GET /api/v1/users" and "GET /api/v1/users/{id}" APIs.
Additionally, enabled filtering and sorting by "Customer" name in the "GET /api/v1/users" API.		 2.1.1
Added Standard API functions (v2) to the APIs provided by Ops I, and added APIs for the items below. This change allows you to use the API to retrieve or update information regarding the following items, as well as retrieve or update related resources:
  • User
  • Group
  • Role
 1.4, 2.1.2
When retrieving data via the "POST /api/v1/graphql" API, you can now specify the "limit" parameter to set the number of records retrieved at once and the "offset" parameter to specify the starting position of the records to retrieve. With this change, you can now retrieve data in batches. 2.1.1
Added "GET /api/v1/knowledge-articles/{id}/attachments/{attachmentID}/download" to Standard API functions (v1).
Additionally, added the following API to Custom API functions:
  • GET /capi/v1/knowledge-articles
  • GET /capi/v1/knowledge-articles/{id}
  • POST /capi/v1/knowledge-articles/{id}/vote
  • GET /capi/v1/knowledge-categories
  • GET /capi/v1/knowledge-articles/{id}/attachments
 1.4, 2.1.1, 2.2
Added the "includeTasks" query parameter to the "GET /api/v1/practice-contexts" API.
This change allows you to retrieve the "tasks" property, which was previously only available via the "GET /api/v1/practice-contexts/{Id}" API.		 2.1.1
Updated the following schemas in Standard API functions (v1):
  • GroupDTO:
    Removed "assignedUsers", "assignedRoles", "effectiveRoles", "relatedGroups", "childGroups", and "gitMembers".
  • UserDTO:
    • Added a note stating that "GET /api/v1/users" does not return "assignedGroups".
    • Added a note stating that "GET /api/v1/users/{id}" does not return "groups".
    • Removed the required flag for "assignedGroups".
Since this is only a change in the API reference, there are no changes to the actual API response values. 		2.1.1
Removed "validity" from the fields that can be specified in the "filterBy" query parameter for the Custom API functions listed below, and added a new query parameter, "validity", in its place. The "validity" query parameter can be set to "true" or "false", and the default value is "true".
  • GET /capi/v1/customers
  • GET /capi/v1/customer-users
  • GET /capi/v1/agents
As a result of this change, to retrieve invalid customers, customer users, and assignees, specify "validity=false" instead of "filterBy=validity:eq:false" or "filterBy=validity:ne:true".
Additionally, to retrieve both valid and invalid customers, customer users, and assignees, execute the Custom API functions twice, specifying "validity=true" and "validity=false". 		2.2
Fixed an issue where users without permissions could retrieve files via the "GET /api/v1/files/{group}/{repository}/{path}/raw" API. －
Added explanations about the data that can be obtained from API responses in the usage examples for API use cases. 1.3.1
Summarized information about the status codes returned by the API in the "Error information" section. Additionally, included information about status code "404". 1.6, 2

(Legend) -: N/A
Simple typos, omissions, and the like have been corrected without notice.