Best practice to extend Operator ID class
Dear Community,
We have a requirement to create an employee data model that holds all the employee's details. Also, an employee have to connect to the application, so we need to create an operator ID.
To implement this requirement, we have two options:
1) extend the operator ID class (add the employee's details to the operator ID class)
2) create a separate data type "employee" that holds all the necessary details and create a separate operator ID when a new employee is created
So what is the best practice in that case ?
Thanks in advance.
Hi @BOUANENEM: In my view, it is better to create a separate data type which will hold employee specific data. Even you can connect to a external system to get this. Operator ID will be more for your access / authentication and authorisation.
Thanks.