Difference between revisions of "B-Op HR Hub"
Jump to navigation
Jump to search
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| Line 8: | Line 8: | ||
## simultaneiously | ## simultaneiously | ||
## invoking each other (pictures imported by another plugin) | ## invoking each other (pictures imported by another plugin) | ||
# '''Transport''' with filtering (e.g. | # '''Transport''' | ||
##with filtering on row level (e.g. External users are not relevant to Klesy) | |||
##with filtering on column level (e.g. BKC is non relevant to Print environments) | |||
# '''Import plugins''' They are used to analyse users and e.g. add user-groups computed specifically according to target system. This plugins may have specific configuration-uis | # '''Import plugins''' They are used to analyse users and e.g. add user-groups computed specifically according to target system. This plugins may have specific configuration-uis | ||
Revision as of 10:00, 23 June 2023
HR Data importing is required for almost all usage cases of B-Op software, as larger companies typically have a HR system already in place.
To integrate with these HR-systems, B-Op HR Hub was created to integrate seamlessly.
Three steps
- Data acquisition plugins collecting base date from multiple systems
- simultaneiously
- invoking each other (pictures imported by another plugin)
- Transport
- with filtering on row level (e.g. External users are not relevant to Klesy)
- with filtering on column level (e.g. BKC is non relevant to Print environments)
- Import plugins They are used to analyse users and e.g. add user-groups computed specifically according to target system. This plugins may have specific configuration-uis