📄️ User Care
In cases such as dismissal, change of the current user ID, the status of the user's registration in the system is inactive. The current id may be defined in the processes currently executing in the system. As soon as the record falls into inactivity, when the ongoing processes reach this passive record, the system will give a "user passive" warning and the process will be blocked. In order to avoid this problem, it is necessary to define an active user id instead of a passive user id from the User Care area. The defined active user means that he will now replace the passive user.
📄️ Position Maintenance
Workflows can be carried out both user-based and position-based. When a position is used in process steps, trades are executed by the person who owns that position. Just like the user, when the position is inactive, the system will give a "passive position" warning if a passive position is found in the process steps. The Position Maintenance area is used so that this warning is not received and trades can continue over an active position instead of a passive position.
📄️ Department Maintenance
An existing department in the organization can be closed, merged with another department, and received a new ID and definition. In such a situation, the situation of the current department becomes passive. The Department Maintenance field under the Organization Maintenance heading is used to define a new one to replace the passive department.
📄️ Title Maintenance
When an existing title definition in the organization falls into inactivity, an active title definition can be made instead of a passive title from the Title Care field under the Organization Care heading.
📄️ Human Resources
Organization Maintenance
📄️ Organization Maintenance
Organization Maintenance