Get Employee EMC Visibility
post
/config/sim/v1/employees/getEMCVisibility
Gets all the EMC modules visible for the given employee in the specified organization
Request
Supported Media Types
- application/json
- multipart/form-data
Header Parameters
-
Simphony-OrgShortName: string(string)
Org Identifier
A request body
Root Schema : EMCVisibilityGetRequestBody
Type:
object
The input Body model that needs to be given.
Show Source
-
include(optional):
string
Objects included in response
-
languages(optional):
string
If specified, limits translated strings returned
-
limit(optional):
integer
If using paging, number of results returned in this page.
-
objectNum:
integer
Unique reference of the employee in the system.Example:
1
-
offset(optional):
integer
Starting resource record index. Not required if paging parameters are not supported
-
orderBy(optional):
string
Sorts the response by the specified field name and sort order.
-
searchCriteria(optional):
string
Search criteria to filter results based on field value
Response
Supported Media Types
- application/json
200 Response
A collection of all visible hierarchy nodes to the particular employee in an organization.
Root Schema : EmployeeEMCVisibility
Type:
object
Model for an Employee EMC Visibility Object
Show Source
-
hierObjNum(optional):
integer
Object number of the hierarchy unit where the employee EMC visibility is configuredExample:
26
-
hierUnitId:
integer
Unique reference of the hierarchy unit where the employee EMC visibility is configuredExample:
3599
-
hierUnitName(optional):
object HierUnitNameTranslatedString
A string that contains translations of hierarchy unit name into multiple languages
-
objectNum:
integer
Unique reference of the employee in the system.Example:
1
-
propagateToChildren(optional):
boolean
Boolean flag indicating if the EMC visibility is propagated to child nodes of the hierarchy unitExample:
true
Nested Schema : HierUnitNameTranslatedString
Type:
object
A string that contains translations of hierarchy unit name into multiple languages
Example:
{
"en-US":"Property",
"de-DE":"Eigentum",
"ar-AR":"??????????"
}
400 Response
400 Bad Request
Root Schema : ErrorDetails
Type:
object
Response body when the request returns an error.
Show Source
-
detail(optional):
string
A short, human-readable summary of the problem.Example:
Specified Data is invalid
-
errorDetails(optional):
string
A human-readable explanation specific to this occurrence of the problem.Example:
Entity Does Not Exist
-
o:errorCode(optional):
integer
Error code of the problemExample:
55223
-
status(optional):
integer
HTTP status code.Example:
400
-
title(optional):
string
A short, human-readable summary of the problem type.Example:
VALIDATION ERROR
-
type(optional):
string
A URI reference that identifies the problem type. When this member is not present, its value is assumed to be "about:blank".Example:
http://www.abc.org/xyz.html