As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
Create groupCreates a new group. Request: POST /group { "id": "admin", "name": "System administrator", "type": "security-role" } API: identityService.newGroup(); identityService.saveGroup();
if (identityService.createGroupQuery().groupId(groupInfo.getId()).count() == 0) { Group group = identityService.newGroup(groupInfo.getId()); group.setName(groupInfo.getName()); if (groupInfo.getType() != null) { group.setType(groupInfo.getType()); } else { group.setType("assignment"); } identityService.saveGroup(group); } else { throw new ActivitiException("group id must be unique"); } return new StateResponse().setSuccess(true);
CRUD HTTPCreate POSTRetrieve GETUpdate PUTDelete DELETE
CRUD HTTPCreate PUTRetrieve GETUpdate PUTDelete DELETE
After that discussion, a more realistic mapping would seem to be: Create = PUT iff you are sending the full content of the specified resource (URL). Create = POST if you are sending a command to the server to create a subordinate of the specified resource, using some server-side algorithm. Retrieve = GET. Update = PUT iff you are updating the full content of the specified resource. Update = POST if you are requesting the server to update one or more subordinates of the specified resource. Delete = DELETE.