Connector limitations
Smartsheet is a software that offers enhanced collaboration and work management. It uses a tabular user interface to assign tasks, track project progress, manage calendars, documents. It is an enterprise platform for dynamic work that aligns technology and people resulting in an efficient work environment.
Supervisor Configuration Parameters
Supported objects and operations
Users
Table 342: Supported operations for Users
Create User |
POST |
Get a User |
GET |
List Users |
GET |
Update a user |
PUT |
Delete a user |
DELETE |
Groups
Table 343: Supported operations for Groups
Create a group |
POST |
Delete a group |
DELETE |
Get a group |
GET |
List groups |
GET |
Update a group |
PUT |
Mandatory Fields
This section lists the mandatory fields required to create a User or Group:
Users
Groups
Mappings
The mappings are listed in the tables below.
Table 344: Smartsheet User to SCIM user mapping
id |
id |
extension.admin |
admin |
emails[].value |
email |
name.givenName |
firstName |
extension.groupAdmin |
groupAdmin |
extension.lastLogin |
lastLogin |
name.familyName |
lastName |
extension.licensedSheetCreator |
licensedSheetCreator |
displayName |
name |
photos[].value |
profileImage.id |
extension.resourceViewer |
resourceViewer |
extension.sheetCount |
sheetCount |
active |
status |
title |
title |
timeZone |
timeZone |
Table 345: Smartsheet group to SCIM group mapping
id |
id |
extension.ownerId |
ownerId |
meta.created |
createdAt |
extension.description |
description |
members[].value |
members[] |
meta.lastModified |
modifiedAt |
displayName |
name |
extension.ownerEmail |
owner |
-
Connector does not return important meta information like created and lastModified for users.
-
While trying to create a user with already used details, the connector returns the existing user details.
-
While creating or updating a group, the members attribute is sometimes available with all members, sometimes it doesn't.
-
For larger page(cursor) values than the present number of pages in list response, the connector returns last page(cursor) response.
Pingboard
Pingboard is real-time organizational chart software that makes it easy to build professional looking org charts. It keeps company org charts in sync with HRMS software automatically, thus replacing the manual need to make the org charts using flow charting applications like Microsoft Visio or Lucidchart. Pingboard was designed to help companies organize their employees and departments, develop hiring and succession plans, and share this information on the corporate org chart.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 346: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User by Id |
POST |
List Users |
POST |
Groups
Table 347: Supported operations for Groups
Create Group |
POST |
Update Group |
PUT |
List Groups |
POST |
Get Group by Id |
POST |
Delete Group |
DELETE |
Mandatory fields
Users
-
name.givenName
-
name.familyName
-
emails[].value
Groups
-
displayName
-
extension.groupType
User and Group mapping
The user and group mappings are listed in the tables below.
Table 348: Pingboard user to SCIM mapping
id |
id |
userName |
email |
name.givenName |
first_name |
name.familyName |
last_name |
name.formatted |
first_name + " " + last_name |
displayName |
first_name + " " + last_name |
nickName |
nickname |
emails[].value |
email |
phoneNumbers[].value |
office_phone |
photos[].value |
avatar_urls.original |
timezone |
time_zone |
locale |
locale |
title |
job_title |
groups[].value (Only for read operation) |
links.groups[] & links.locations[] |
extension.description |
bio |
extension.manager.value |
reports_to_id |
meta.created |
created_at |
meta.lastModified |
updated_at |
Table 349: Pingboard group to SCIM group mapping
id |
id |
displayName |
name |
members[].value |
links.users[] |
extension.description |
description |
extension.type |
type |
meta.created |
created_at |
meta.lastModified |
updated_at |
Connector limitations
-
If all of the member IDs used in the create group request are invalid, an error with status 500 and no message will be returned but the group gets created. Even with at least one valid member ID, the group write operation gets successful.
-
Even though the Pingboard API supports custom attributes for user resource, the Pingboard connector does not support custom attributes for users. The reason being is to avoid the unnecessary overhead in retrieving the names of the custom attributes by making additional request as the target API returns custom attribute IDs instead of the attribute name for GET user details response.
-
An Admin user can also be deleted using APIs in which case the connector functionality will not work.
-
Random string value for user's locale gets saved due to the target API behavior.
Supervisor configuration parameters
Pingboard is real-time organizational chart software that makes it easy to build professional looking org charts. It keeps company org charts in sync with HRMS software automatically, thus replacing the manual need to make the org charts using flow charting applications like Microsoft Visio or Lucidchart. Pingboard was designed to help companies organize their employees and departments, develop hiring and succession plans, and share this information on the corporate org chart.
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 346: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User by Id |
POST |
List Users |
POST |
Groups
Table 347: Supported operations for Groups
Create Group |
POST |
Update Group |
PUT |
List Groups |
POST |
Get Group by Id |
POST |
Delete Group |
DELETE |
Mandatory fields
Users
-
name.givenName
-
name.familyName
-
emails[].value
Groups
-
displayName
-
extension.groupType
User and Group mapping
The user and group mappings are listed in the tables below.
Table 348: Pingboard user to SCIM mapping
id |
id |
userName |
email |
name.givenName |
first_name |
name.familyName |
last_name |
name.formatted |
first_name + " " + last_name |
displayName |
first_name + " " + last_name |
nickName |
nickname |
emails[].value |
email |
phoneNumbers[].value |
office_phone |
photos[].value |
avatar_urls.original |
timezone |
time_zone |
locale |
locale |
title |
job_title |
groups[].value (Only for read operation) |
links.groups[] & links.locations[] |
extension.description |
bio |
extension.manager.value |
reports_to_id |
meta.created |
created_at |
meta.lastModified |
updated_at |
Table 349: Pingboard group to SCIM group mapping
id |
id |
displayName |
name |
members[].value |
links.users[] |
extension.description |
description |
extension.type |
type |
meta.created |
created_at |
meta.lastModified |
updated_at |
Connector limitations
-
If all of the member IDs used in the create group request are invalid, an error with status 500 and no message will be returned but the group gets created. Even with at least one valid member ID, the group write operation gets successful.
-
Even though the Pingboard API supports custom attributes for user resource, the Pingboard connector does not support custom attributes for users. The reason being is to avoid the unnecessary overhead in retrieving the names of the custom attributes by making additional request as the target API returns custom attribute IDs instead of the attribute name for GET user details response.
-
An Admin user can also be deleted using APIs in which case the connector functionality will not work.
-
Random string value for user's locale gets saved due to the target API behavior.
Supported objects and operations
Pingboard is real-time organizational chart software that makes it easy to build professional looking org charts. It keeps company org charts in sync with HRMS software automatically, thus replacing the manual need to make the org charts using flow charting applications like Microsoft Visio or Lucidchart. Pingboard was designed to help companies organize their employees and departments, develop hiring and succession plans, and share this information on the corporate org chart.
Supervisor configuration parameters
To configure the connector, following parameters are required:
Users
Table 346: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User by Id |
POST |
List Users |
POST |
Groups
Table 347: Supported operations for Groups
Create Group |
POST |
Update Group |
PUT |
List Groups |
POST |
Get Group by Id |
POST |
Delete Group |
DELETE |
Mandatory fields
Users
-
name.givenName
-
name.familyName
-
emails[].value
Groups
-
displayName
-
extension.groupType
User and Group mapping
The user and group mappings are listed in the tables below.
Table 348: Pingboard user to SCIM mapping
id |
id |
userName |
email |
name.givenName |
first_name |
name.familyName |
last_name |
name.formatted |
first_name + " " + last_name |
displayName |
first_name + " " + last_name |
nickName |
nickname |
emails[].value |
email |
phoneNumbers[].value |
office_phone |
photos[].value |
avatar_urls.original |
timezone |
time_zone |
locale |
locale |
title |
job_title |
groups[].value (Only for read operation) |
links.groups[] & links.locations[] |
extension.description |
bio |
extension.manager.value |
reports_to_id |
meta.created |
created_at |
meta.lastModified |
updated_at |
Table 349: Pingboard group to SCIM group mapping
id |
id |
displayName |
name |
members[].value |
links.users[] |
extension.description |
description |
extension.type |
type |
meta.created |
created_at |
meta.lastModified |
updated_at |
Connector limitations
-
If all of the member IDs used in the create group request are invalid, an error with status 500 and no message will be returned but the group gets created. Even with at least one valid member ID, the group write operation gets successful.
-
Even though the Pingboard API supports custom attributes for user resource, the Pingboard connector does not support custom attributes for users. The reason being is to avoid the unnecessary overhead in retrieving the names of the custom attributes by making additional request as the target API returns custom attribute IDs instead of the attribute name for GET user details response.
-
An Admin user can also be deleted using APIs in which case the connector functionality will not work.
-
Random string value for user's locale gets saved due to the target API behavior.