Page Comparison

...

1. Create Department Entity:
   It passes tenant Id, master department id, hierarchy level, its children list with department entity name and code. Tenant, hierarchy level and the master department is root info about the department entity. If the department entity does not contain any child, that means it is a leaf department entity it can only seek for its parent.

2. Search Department Entity:
   It can make search requests based on any department entity attribute but can't skip tenant information, it returns the whole department entity details along with its child information. It finds all ancestry information of the current department entity.

3. Update Department Entity:
   Update the existing department entity by searching based on department entity id and tenant id.
   Mandatory Fields to update department entity "id" and "tenant id".
   We can update any attribute in department entity except “id” itself.
   updatable attribute list: tenantId, departmentId, code, name, hierarchyLevel and children.

   It does few validation before updating department entity.

   • departmentId and children can not be update without hierarchyLevel.

   • hierarchyLevel value should be valid for departmentId and children. If value got mismatch then it will throw appropriate error message.

   • It checks in the system before doing update, that department entity id is available or not. If exist then it'll update else throw a meaningful error message.

API List

...