Connector limitations
Majesco is the leading software partner to both the P&C and L&A insurance markets for modernization and optimization of their businesses.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 374: Supported operations for Users
Create User |
POST |
Get User by Id |
GET |
List Users |
GET |
Update User |
PUT |
Roles
Table 375: Supported operations for Roles
Get Role by Id |
GET |
Create Roles |
POST |
List Roles |
GET |
Update Role |
PUT |
Mandatory fields
Users
-
userName
-
displayName
-
emails[].value
Roles
User and Role mapping
The user mappings are listed in the tables below.
Table 376: User mapping
Id |
id |
userName |
userid |
name.Formatted |
name |
displayName |
name |
active |
status |
emails[].value |
email |
extension.customerCode |
customercode |
phoneNumbers[].value |
phoneno |
extension.domain |
domain |
extension.isExternalUser |
isexternaluser |
extension.isServiceUser |
isserviceuser |
extension.isUnlock |
isunlock |
extension.linkedUserId |
linkeduserid |
extension.sourceIdentityStoreName |
sourceidentitystorename |
extension.suspended |
suspended |
meta.Created |
createdate |
meta.LastModified |
modifieddate |
roles[].value |
userRoles[].id |
roles[].display |
userRoles[].rolename |
extension.applications |
userRoles[].rolename |
Table 377: Role mapping
Id |
id |
name |
rolename |
roleType |
roletype |
description |
roledescription |
parentRoles[].value |
parentroleslist[].id |
parentRoles[].display |
parentroleslist[].rolename |
childRoles[].value |
childroleslist[].id |
childRoles[].display |
childroleslist[].rolename |
meta.Created |
createddate |
meta.LastModified |
modifieddate |
members[].value |
roleMembers[].id |
members[].display |
roleMembers[].name |
LuccaHR
LuccaHR provides solutions to optimize administrative and HR processes.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 378: Supported operations for Users
Create User |
POST |
Get a user |
GET |
List Users |
GET |
Update a user |
PUT |
Departments
Table 379: Supported operations for Departments
Create a department |
POST |
Delete a department |
DELETE |
Get a department |
GET |
List department |
GET |
Update a department |
PUT |
Mandatory fields
Users
-
name.firstName
-
name.lastName
-
userName
-
email.value
-
extension.legalEntityId
-
extension. departmentId
Departments
User and Department mapping
The user and department mappings are listed in the tables below.
Table 380: User mapping
displayName |
displayName |
Emails.Value |
mail |
Extension.birthDate |
birthDate |
Extension.contractEnd |
dtContractEnd |
Extension.contractStart |
dtContractStart |
Extension.department.name |
department.name |
Extension.department.value |
departmentID |
Extension.employeeNumber |
employeeNumber |
Extension.gender |
gender |
Extension.legalEntity.name |
legalEntity.name |
Extension.legalEntity.value |
legalEntityID |
Extension.manager.name |
manager.name |
Extension.Manager.Value |
managerID |
Extension.rolePrincipal.name |
rolePrincipal.name |
Extension.rolePrincipal.value |
rolePrincipalId |
Id |
id |
meta.Created |
createdOn |
meta.LastModified |
modifiedOn |
Name.FamilyName |
lastName |
Name.Formatted |
name |
Name.GivenName |
firstName |
Roles[].display |
habilitedRoles[].name |
Roles[].value |
habilitedRoles[].id |
Title |
jobTitle |
UserName |
login |
Table 381: Department mapping
id |
id |
name |
name |
code |
code |
Active |
isActive |
head.value |
headID |
head.name |
head.name |
members[].value |
users[].id |
members[].display |
users[].name |
meta.Created |
createdOn |
meta.LastModified |
modifiedOn |
Connector limitations
-
A user once created cannot be deleted, but it can be terminated using the PUT API.
-
Multiple departments with same name can be created.
-
Departments with one or more active users cannot be deleted.
Supervisor configuration parameters
LuccaHR provides solutions to optimize administrative and HR processes.
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 378: Supported operations for Users
Create User |
POST |
Get a user |
GET |
List Users |
GET |
Update a user |
PUT |
Departments
Table 379: Supported operations for Departments
Create a department |
POST |
Delete a department |
DELETE |
Get a department |
GET |
List department |
GET |
Update a department |
PUT |
Mandatory fields
Users
-
name.firstName
-
name.lastName
-
userName
-
email.value
-
extension.legalEntityId
-
extension. departmentId
Departments
User and Department mapping
The user and department mappings are listed in the tables below.
Table 380: User mapping
displayName |
displayName |
Emails.Value |
mail |
Extension.birthDate |
birthDate |
Extension.contractEnd |
dtContractEnd |
Extension.contractStart |
dtContractStart |
Extension.department.name |
department.name |
Extension.department.value |
departmentID |
Extension.employeeNumber |
employeeNumber |
Extension.gender |
gender |
Extension.legalEntity.name |
legalEntity.name |
Extension.legalEntity.value |
legalEntityID |
Extension.manager.name |
manager.name |
Extension.Manager.Value |
managerID |
Extension.rolePrincipal.name |
rolePrincipal.name |
Extension.rolePrincipal.value |
rolePrincipalId |
Id |
id |
meta.Created |
createdOn |
meta.LastModified |
modifiedOn |
Name.FamilyName |
lastName |
Name.Formatted |
name |
Name.GivenName |
firstName |
Roles[].display |
habilitedRoles[].name |
Roles[].value |
habilitedRoles[].id |
Title |
jobTitle |
UserName |
login |
Table 381: Department mapping
id |
id |
name |
name |
code |
code |
Active |
isActive |
head.value |
headID |
head.name |
head.name |
members[].value |
users[].id |
members[].display |
users[].name |
meta.Created |
createdOn |
meta.LastModified |
modifiedOn |
Connector limitations
-
A user once created cannot be deleted, but it can be terminated using the PUT API.
-
Multiple departments with same name can be created.
-
Departments with one or more active users cannot be deleted.
Supported objects and operations
LuccaHR provides solutions to optimize administrative and HR processes.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Users
Table 378: Supported operations for Users
Create User |
POST |
Get a user |
GET |
List Users |
GET |
Update a user |
PUT |
Departments
Table 379: Supported operations for Departments
Create a department |
POST |
Delete a department |
DELETE |
Get a department |
GET |
List department |
GET |
Update a department |
PUT |
Mandatory fields
Users
-
name.firstName
-
name.lastName
-
userName
-
email.value
-
extension.legalEntityId
-
extension. departmentId
Departments
User and Department mapping
The user and department mappings are listed in the tables below.
Table 380: User mapping
displayName |
displayName |
Emails.Value |
mail |
Extension.birthDate |
birthDate |
Extension.contractEnd |
dtContractEnd |
Extension.contractStart |
dtContractStart |
Extension.department.name |
department.name |
Extension.department.value |
departmentID |
Extension.employeeNumber |
employeeNumber |
Extension.gender |
gender |
Extension.legalEntity.name |
legalEntity.name |
Extension.legalEntity.value |
legalEntityID |
Extension.manager.name |
manager.name |
Extension.Manager.Value |
managerID |
Extension.rolePrincipal.name |
rolePrincipal.name |
Extension.rolePrincipal.value |
rolePrincipalId |
Id |
id |
meta.Created |
createdOn |
meta.LastModified |
modifiedOn |
Name.FamilyName |
lastName |
Name.Formatted |
name |
Name.GivenName |
firstName |
Roles[].display |
habilitedRoles[].name |
Roles[].value |
habilitedRoles[].id |
Title |
jobTitle |
UserName |
login |
Table 381: Department mapping
id |
id |
name |
name |
code |
code |
Active |
isActive |
head.value |
headID |
head.name |
head.name |
members[].value |
users[].id |
members[].display |
users[].name |
meta.Created |
createdOn |
meta.LastModified |
modifiedOn |
Connector limitations
-
A user once created cannot be deleted, but it can be terminated using the PUT API.
-
Multiple departments with same name can be created.
-
Departments with one or more active users cannot be deleted.