001 - Create/Update/Delete user/employee
From Host
This transaction is used for user and/or employee maintenance.
| Field | Description | Data Type | Mandatory | Comment |
|---|---|---|---|---|
| 1 | Action | Integer | X | |
| 2 | User ID | Text(10) | ||
| 3 | User profile | Text | ||
| 4 | Logon user ID | Text(50) | ||
| 5 | First name | Text(30) | (X) | |
| 6 | Surname | Text(30) | (X) | |
| 7 | Restricted to: Period profile ID | Text | ||
| 8 | Division ID | Text | ||
| 9 | Substitute | Text | ||
| 10 | Substitute from | Date | ||
| 11 | Substitute to | Date | ||
| 12 | Restricted to: Departments | Text | Comma separated list of departments that the user has access to | |
| 13 | Restricted to: Workcenters | Text | Comma separated list of work centres that the user has access to | |
| 14 | Restricted to: Approval groups | Text | Comma separated list of approval groups that the user has access to | |
| 15 | Create missing approval group | Logical | If true the user is assigned to the approval groups specified in field 17 | |
| 16 | Inactive | Logical | ||
| 17 | Approval group ID to setup | Text | Comma separated list of approval groups that the user can approve. If you want to add also a department for that approval group, you need to add it with :. Example: APPR-GRP1:DEPT1 | |
| 18 | Approval level | Integer | 1: Approve transactions | |
| 19 | User roles | Text | ||
| 20 | Password mode | Integer | 0: Unified login, | |
| 21 | Password | Text | Only used when password mode is 1 or 3 | |
| 22 | Employee number | Text | Mandatory if action >= 2 | |
| 23 | Card number | Text | ||
| 24 | Period profile ID | Text | ||
| 25 | Attendance profile ID | Text | ||
| 26 | Payroll code profile ID | Text | ||
| 27 | Category ID | Text | ||
| 28 | Employee Approval group ID | Text | ||
| 29 | Working place | Text | ||
| 30 | Department ID | Text | ||
| 31 | Employee group ID | Text | ||
| 32 | Registration method | Integer | ||
| 33 | First registration date | Date | ||
| 34 | Social security number | Text | ||
| 35 | Text | Update user and/or employee email depending on field 1 ''Action". | ||
| 36 | Approval group change date | Date | Use in connection with field #28 to change approval group via the employee's time queue. | |
| 37 | Approval group change time | Time | Use in connection with field #28 to change approval group via the employee's time queue. | |
| 38 | Append approval group restrictions | Logical | If this field contains "true" when a transaction is processed, then any approval group or groups received in field #14 (Restricted to approval groups) will be appended to any approval group restrictions that have already been assigned to the user. | |
| 39 | User's approver | Text | The approver of the user | |
| 40 | User's manager | Text | The manager of the user | |
| 41 | Append approval group ID | Logical | If this field contains "true" when a transaction is processed, then all approval groups received in field #17 (Approval group ID to Setup) will be appended to any approval group that have already been assigned to the user. | |
| 42 | Substitute user profiles | Text | A comma separated list of valid user profile | |
| 43 | Restricted to: Divisions | Text | Comma separated list of divisions that the user has access to |
Notes
| Id | Text |
|---|---|
| 1 | The following action codes can be used: * 0: New/changed user * 1: Delete user * 4: Delete user/employee * 5: New/changed user/employee * 14: Delete employee * 15: New/changed employee It's recommended to use action code 5 and 15 instead of action codes 2, 3, 12 and 13. These codes can be used in situations where it is important to have transactions treated as erroneous if the data in ProMark doesn't correspond to the external system's "expectations". Field 22 must always be used to identify an employee when one of the action codes 2 - 15 is used. When a new employee is to be created, fields 24, 25, 27 and 32 are mandatory. Update requests for an employee record will only involve field 5, 6, 23, 34 and 35 if the employee record has been created or updated by other means than through this host transaction, or if the employee has made a registration. An employee record cannot be deleted by this transaction if the employee has made a registration. |
| 2 | When a regular user is maintained (Action codes < 12) the following applies: * In case of unified login (password mode=0) a random password is assigned. If password mode is 1 a password is required. If password mode is 2 no password is assigned and the user will have to enter a password at login. If password mode is 3 a hashed password must be given and it is must be base64 encoded or "hex" coded; the hashing can be done using MD5, SHA-1, SHA-256 or SHA-512. If password mode is 3 and an employee is maintained, the password is assigned to the employee and must be used for logging on the portal. The employee will not be able to use pin code. The password on an employee can be removed by using password mode 2. * Password mode 0 and 2 can only be used when creating a new user or on existing users that has never logged in. Using password mode 0 or 2 on existing users that have logged in will just be ignored. * Password mode 0 is the default mode. When only an employee is maintained (Action codes >= 12) the following applies: * If password mode is 3 a hashed password must be given and it is must be base64 encoded or "hex" coded; the hashing can be done using MD5, SHA-1, SHA-256 or SHA-512. * If password mode is 2 any password assignment is removed from the employee who must thereafter use the regular PIN as assigned on the employee master screen or via host transaction type 373. * Other password modes are not allowed. |
| 3 | 1: Clock-in/out or all-day absence required 2: Clock-in/out or all-day absence when relevant 3: Only all-day or hourly absence 4: Present and hourly absence or all-day absence required |
| 5 | If action is 5 and the employee number is filled out then the user is mapped to the employee. If the employee number is the only employee field (field 22 to 37) that is fill out it is not required that the employee exists. |