User Management (Frontend)

In this documentation, the User Management tile on the Pentos Feeder workspace incorporates the actual frontend, which is composed of the following:

• The Global Data View
• The Quick Search

The following operations and features are further explained:

• Add Data
• Edit Data
  • Mass Change
  • Change History
• Delete Data
  • Deleting A Single Entry
  • Deleting A Referenced User
  • Deleting Multiple Entries
  • Mass Deletion of Entries
• Search Data
  • The Search in Feeder 2
  • The Search in Feeder 1
  • Combination of Filters and Search Arguments
• Filter & Limit Data
  • Setting up a Filter (Simple Criteria, Simple Query Builder)
  • Using Complex Criteria
  • Complex Filter Arguments for Copy Pasting (Collection)
• Sort Data
• Import Data
  • How To Import
  • Import Configuration (General)
  • Automatic Importing (Auto Import)
  • Mailing Expert Mode for Admins
  • Managing the Visibility of Imports (Access)
• Export Data
  • How To Export
  • Export Configuration (General)
  • Querying Export Data (Query)
  • Automatic Exporting (Auto Export)
  • Managing the Visibility of Exports (Access)

---

Home Screen

The following screen displays the Home of the User Management, pre-filled with 400.000 sample employee entries. Characteristic of it are the buttons New, Delete, Export, Import, Filter providing central operations as well as a Quick Search field.

(Both modified and feeder_state are internal attributes where labels cannot be changed.)

Feeder Object Recognition

The screenshot displays the User Management, which is the representation of the SF_User object specified in the backend. The particular Feeder object can be recognized by the title SuccessFactors User which is the object’s translated label. If no translation is given, the technical name is displayed (here: SF_User).

List View

Arranged in a typical list view, details of employee entries appear in the order specified within the Object Configuration. Please note, that the sequence of attributes alias column headers (Surname, Forename, Email etc.) affects the Quick Search too!

Quick Search

If you want to search an employee with firstname=”Elle”, then the input needs to be “,Elle”. Surname is first, then Forename. Therefore the comma determins the column to be searched! In case that you want to search for a person with a particular surname only, the string itself e.g. “Aaron” suffices. Please make sure that your search argument does not contain any unwanted whitespaces!

Note

The combined use of an active filter and the quick search are possible and very convenient