Analysis criteria

Indicate which criteria of analysis will be used for better visualization of the courses and knowledge required for the position.

It allows determining which criteria will be considered to present the Training, Improvement and Knowledge courses according to the requirements of the position of the collaborators. When setting a certain criterion, such as the criterion 'Progress Situation' of the Training Course, the situation will be verified in the history of the training course of the employee. If you are with the situation 1-Progress, then it will be considered requirement met. If you meet at least one of the criteria (historical, Progress, complete, Quitter.) defined for its course, the requirement will be presented as.

The same goes for the Cipa and EPI, brigade items, where it will be checked whether the developer was or was not trained for the course required by the category to which the employee belongs.

In relation to the Review criteria, will be observed if the start date of the last dev course history is prior to the date of the last revision will mean that he owns the requirement, but it will be outdated/defeated and on grid Requirements will be presented the Red course featuring what the developer does not have the latest revision.
Considerations: When the developer is in progress and during this is created a new revision by changing its content, the course in progress will have its content outdated and will be presented at the consultation requirement (review) not answered. The developer must take the course with the new revision.
If the course of improvement does not have informed reviews, this criterion will not influence the outcome of the needs assessment.

Local requirements/posts can be considered simultaneously the requirements by function according to the developer's function histories. When there is a history of function, the routine will consider the requirements for function, but when does not exist, will continue searching for the requirements of the position.

The Override item Requirements When is checked, will consider the role of historical collaborator, overlaying the original developer position requirements.
If the indications Consider function and History Overlap Requirements are marked and the developer does not have any history of function, the system considers the official position of the developer to get the requirements.