Personal tools

Configuration mode

From Onlinehelp

Jump to: navigation, search

The configuration mode, formerly called CWC mode (for Customer Web Configuration), allows you to display and hide views of your solution like single elements, and to configure texts, forms, links, containers, and tables however you prefer. The Hide and Display functions also can be configured separately via Role groups for special view configurations. Please note that not all available CWC settings work everywhere — for instance, the configurations for document lists are very limited.

Attention.gif Please note that you can only use the configuration mode to configure your solution. That means your solution can only be configured, but not used in the normal way. For example, you cannot save forms in configuration mode. When you are done editing the configuration, exit the configuration mode to continue working normally in your umantis solution.

You will find the configuration mode at the top right of the main menu bar. As an administrator, you can click on "Configure view" to modify individual elements.

Important information and tips for configuration mode

Configuration mode (CWC mode) is a very powerful tool for configuring/modifying existing solutions — but certain configuration changes might also break the solution or render it unusable. The configurations can sometimes have extremely critical consequences, and we therefore recommend that configuration mode only be used by users who are fully aware of the consequences. Furthermore, every configuration should be tested after completion, and its effects/results checked.

Info.gif Conditions: Note that certain elements can be seen in configuration mode which may not be displayed outside of configuration mode. These elements are linked to certain specific conditions, and are only displayed when those conditions are met.

Here are some tips and some typical examples of changes in configuration mode that may have critical consequences:

  • Searches must not be hidden when search links (e.g. “open applications” on the homepage) are enabled for display.
Effect: Search link no longer functions properly.
  • Do not display multiple search fields with the same name
Searches with the same name should never be displayed at the same time (e.g. on the job board). This situation would lead to incorrect behavior in all searches.
  • Do not hide important fields: Password field, login name field, email field etc.
Effect: Hiding these important fields may result in applicants no longer having cockpit access, login may no longer be possible etc.
  • When creating jobs or job requisitions, the “Branch office” field should not be hidden.
Effect: Various incorrect behavior.
  • Renaming selection values that cannot be renamed
Certain selection values cannot be deleted because they are permanently linked to actions in the solution (e.g. the application status "Application submitted" is automatically assigned to all new applications). Any selection value that cannot be deleted should therefore be renamed in an informative way, if at all.
  • Only perform general renaming for specific words (e.g. do not rename "Comment" across the board)
Effect: Incorrect labels.
  • Do not set email fields to “display”
Display fields do not store any data — they are used to prevent the user from editing the content of the field (see Configure form).
  • Generally, use drilldown entry fields only for filters and searches
Drilldown entry fields can be defined at various places in the solution. However, they are not appropriate for setting values, but are mainly used for filters and searches.

Display and hide elements

Attention.gif Notes:

  • If certain data blocks are displayed twice in configuration mode, this is valid behavior, not an error. Each data block is linked to conditions and must be displayed twice in configuration mode in order to allow for changes to be applied.
  • Please note that there are certain dependencies between the different views/screens. Therefore, you should never hide the navigation elements at the top level or the first sub-level, for example, as this can lead to display problems.

Basics: Every element can be individually displayed or hidden. However, fields may be duplicated in some forms; in this case, only one element should be displayed.

  • Click on the Cwcvisibleoff.gif icon to hide or display the element:
    • The hidden element always has an orange background in configuration mode and is accompanied by the following icon: Cwcvisibleoff.gif.
    • The displayed element does not have an orange background in configuration mode and is accompanied by the following icon: Cwcvisibleon.gif
  • Click on the Config.gif to go to the configuration page. Under the "Visibility" menu item, the element can be displayed or hidden by selecting or deselecting the checkbox. If you have defined special role groups in the settings, these can be activated separately using the "Hide special settings" checkbox. If this box is checked, the element is no longer displayed for the specified role groups.
  • In addition, there are also so-called display fields. These are form fields which are displayed but do not allow the user to make changes or enter data. Please note that display fields do not save any data; for example, email fields should therefore never be set to “display”.
In Configuration mode, you can activate/deactivate display fields for various fields, either for all users ("Display/Input"), or only for the specified Role groups for special view configurations ("Display/Input (Special settings)"). For example, if you set the email address field for an employee to "Display" (Employee -> Employee Directory), then the email address can no longer be changed at this location — either by all users or only by the defined role groups. If empty fields are set to Display, they will no longer be shown.
Another example: You want to display documents about the job in the employee profile, but you may not want to allow the employee to upload their own documents. In this case, we recommend that rather than hiding the upload fields completely, you set the corresponding field to display . (If all fields for uploading documents are hidden, this affects the “show screen” and previously uploaded documents will not be shown.)

Configure texts and fields

There are different configuration options for texts, forms, links, and tables. Once you have located the element that you would like to configure, click on the Config.gif icon.

User-defined fields

You will find user-defined fields at various places in the umantis solution. These fields are provided in addition to umantis “default fields” and can be customized.

Modify the order of elements

In configuration mode, you can modify the order of elements using Drag & Drop:

  • Left-click on an element and, holding down the mouse button, drag the element to the desired position and drop it there.
  • Once you have changed the umantis default order, a button to Reset element order is displayed in the top area. If you click on this button, the original umantis default order is restored.

You can define a specific order using this function. This is especially helpful for forms that include a large number of user-defined fields.
Info.gif Notes:

  • Changes in the order of user elements should be carried out consistently in all associated forms.
  • Moving items below the associated buttons (e.g. Save, Cancel, Search etc.) is not possible.
  • Table rows and columns cannot be moved.

Configure text

Practically any text in the solution can be customized in every language. This includes labels (for fields), help texts, icon "alt texts", column titles, headers, and navigation elements.

  • If you want to rename an element and the new name is only to be applied at this location, enter the new name and place a check mark next to "Specific renaming" (under "Editable attributes"). Otherwise the new name will be applied throughout the entire solution, regardless of the context in which it appears. It is therefore recommended that you rename items globally by searching for the term with the "View texts" search function.
  • You can also configure texts for multiple actions (MultiAction). These fields are dropdown lists which you can edit by clicking on the Config.gif icon (right next to the list). The individual texts for the actions can be displayed, hidden, and renamed, both generally and for the defined role groups. Multiple actions should, however, only be renamed in a logical manner, as the underlying functions remain unchanged.

Info.gif The white box in the upper right corner in configuration mode allows you to change the language. Regardless of the active language settings, the texts can all be set to any language.

Info.gif To undo a change made manually, save the input field with no value. Before saving, check that the input field is truly empty and does not contain a space, as otherwise this will be displayed in place of the original text.

Role-specific visibilities

You can restrict the visibility of individual elements (form fields for entry and search), containers, and table columns to specific roles:

  • In configuration mode, click on Config.gif for each item (container or table column) and use the section "Roles that can see this element" to specify the roles to which visibility is to be limited.

In umantis Employee Management

In configuration mode, you can limit visibility either on the user role level:

  • Administrator (system administrator)
  • HR (HR expert also includes Manager role)
  • Superior plus OrgUnits (Manager with access to direct subordinates and other organizational units)
  • Superior (Manager)
  • Employee (Employee)
Or directly at the module level:
  • Employee file (Employee file)
  • Salary and bonus (all salary/bonuses)
  • Goals and tasks (for ERM)
  • Personnel development (for ERM)
  • Succession planning (Succession planning)
  • Applicant management (Applicant Management)
  • Event administrator (manages events)
  • Network administrator (manages networks)
  • Survey administrator (Surveys)

In umantis Applicant Management

In configuration mode, you can limit visibility either on the user role level:

  • Administrator
  • HR expert
  • HR assistant
Or directly on the access permissions level:
  • Administer HR experts and HR assistants
  • Administer hiring managers
  • Administer committee members
  • Administer recruiters
  • Publishing jobs
  • Administer job requisitions and approval
  • Administer appointments
  • Administer applications
  • Administer assessments
  • Administer central templates
  • Use analytics
  • Start job and application imports
  • Sensitive data
Info.gif The "Sensitive data" field is a sort of "template" which, unlike the other values, is not pre-configured. You might use "Sensible data" permissions for salary information, for example.

Info.gif Example

You have an HR assistant who performs certain tasks but who should not have access to sensitive data. You can define their permissions in the User overview right when you add the new HR assistant to the system, or with existing/active HR assistants, and select all entries in the Roles and permissions section except for the permission: "Sensitive data".

As per “Role-specific visibility”, you can then restrict the visibility of individual elements, containers,, and table columns:

  • If there are certain sections of the solutions which you consider sensitive and do not want to display to this HR assistant, use configuration mode and check the “Sensitive data” box underRoles that can see this elementfor each sensitive element.
  • The visibility is then restricted to only those HR experts and HR assistants who have "Sensitive data" permissions.

Attention.gif Note that in extreme cases, the administrator can set up a very complex permissions structure (if a company has many HR experts and HR assistants working for it). This is not advisable. Use the approach that works best for you, and avoid excessive restrictions and overly complex interactions among the permissions and visibilities assigned to different people.

Configure form

The following attributes can be defined for certain fields in forms:

  • Input for display
Form fields are generally used for entering data. If the user should not be allowed to edit a given field, the field can be set to Display.
  • Type of input field
  • For text fields, the size of the text field can be set from “TextArea5Rows” (small) to “TextArea25Rows” (large).
  • For selection list fields, see the section on how to Configure entry method for selection lists.
  • Type of display in profile
Indicate here whether and how items should be displayed in the profile.
  • default: display occurs depending on the individual field
  • not displayed
  • displayed without label: displayed without Original content Label
  • displayed completely
  • Error correction during entry
Several conditions can be defined for entries.
  • Required: The user must enter a value
  • Not required: Entering a value is not required
  • Check MIME type: When saving the field, the uploaded document is checked against the permitted file format (defined in Security Settings). If the format does not match, an error message is displayed.
  • Check on uniqueness: The entry may only occur once in the form
  • Only decimal numbers: Only decimal numbers are permitted
  • Only integer numbers: Only whole numbers are permitted
  • Only lowercase: Only lowercase letters and numbers are permitted
  • No spaces: Spaces are not permitted
  • Only a-z, A-Z, 0–9: Only individual letters or numbers are permitted
  • Allow HTML
Indicate whether HTML should be interpreted or not. See the instructions in the Configure data fields — HTML security restriction section.
  • default
  • interpret HTML
  • do not interpret HTML
  • Turn off HTML editor
The HTML editor appears only in TextArea fields that interpret HTML. Select “no editor” to turn off the HTML editor.
  • Shortcut key
A user can enter a letter or number here to create a shortcut, which can later be used to jump directly to the field with the key combination <ctrl> + <shift> + <Kurztaste>

Configure entry method for selection lists

  • In configuration mode, any multi-select list can be converted into a single-select list.
  • Conversely, certain single-select lists can be converted to multi-select lists.
  • The following list types can be selected under "Input field type":
    • Multiselect lists / Checkboxes: List or checkboxes in which one or more options may be selected. The selection can be defined by the number of rows.
    • Single-select dropdown / radio button: Dropdown list or list of option fields — only one option can be selected.
  • Single-select dropdown, searchable: Activate this list type to activate a search function within the input field. To use it, enter the first few characters, and you will immediately get suggestions for all the selection values that contain that sequence of characters. Searchable single-select dropdown lists can be especially useful for dropdown lists with a very large number of choices.
Info.gif Within a type, the selection list can be changed as desired. For example, you can easily switch from "Single-select dropdown" to "Single-select radio button".
  • Drilldown entry fields: These input fields are used for navigating through hierarchical data; as such, they can be used for filters and searches (but not for setting values).
    • Drilldown Multiselect All Levels Selectable — allows multi-select at all levels
    • Drilldown Multiselect Lowest Levels Selectable — allows multi-select at the lowest level
    • Drilldown Singleselect All Levels Selectable — allows single select at all levels
    • Drilldown Singleselect Lowest Levels Selectable — allows single select at the lowest level

Configure data fields -— HTML security restriction

By default, all data fields in umantis are subject to certain security restrictions, therefore e.g. only specific HTML formats are permitted. Unauthorized HTML commands or scripts (e.g. JavaScript) are blocked. However, since it still makes sense to disable these limitations for certain applications, configuration mode can be used to define individual fields as “unsecured” or “unrestricted” (not recommended). The contents are then no longer verified.

Info.gif For instance, one situation where this type of reduced restriction might be useful is when uploading images via WYSIWYG text editor.

Fields that can be set to "unsecured" or "unrestricted":

  • Publication contents for external and internal job postings
  • Signature & footer
  • Emails (certain emails e.g. system emails, email templates etc.)
  • Privacy policy statements
  • Wizards (certain content such as title, text, help, and description)
  • Job boards (activation and deactivation emails)

Configure table

When configuring a table (using the Config.gif icon in the top left corner of the table), you can define the number of rows displayed per table. The default value is 15 (rows). You can also select the column which determines default sorting.
Info.gif To avoid performance issues, you should keep the "Number of rows displayed" low — typically no more than 25.

  • You can specify whether the content of a given column should be combined with the next column by using "Combine this column with the next".
  • Using "Separator between combined elements", you specify whether the combined values in this cell are to be separated visually with a space or with a certain symbol/letter etc. of your choice. You can use HTML to do this. For example, if the separator you specify is a comma (,) followed by a line break, i.e. if you enter " ,<br> " as your separator, two or more values in the affected cell will be separated by a comma followed by a line break.

Info.gif Be careful not to combine similar contents with each other in this way. For example, if one value remains empty, only the other (non-empty) value will be displayed, and it is no longer clear whether this belongs to the first or second column.

Load more lines dynamically

Info.gif Please note that dynamic loading is only possible for pages that are not integrated via iFrame.

When configuring tables for the main views (via Config.gif), you can choose to check the box for Load more lines dynamically. This activates the dynamic loading of additional lines, thus simplifying the selection of multiple entries from this table (and executing multiple actions).

Attention.gif When the "Load more lines dynamically" function is activated, the settings under "Number of lines displayed" will be ignored. Instead, 10 lines will be shown, and 10 more lines will be loaded when the user scrolls down. Loading occurs three times. After that, you can click on Infinite 1.png to load additional lines (10 at a time).

  • Infinite 1.png — Click on this arrow at the bottom of the table to load 10 more lines.
  • Infinite 2.png — Click on this icon to jump to the last entry. If you then scroll up, previous entries will be loaded.
If the last entries in the table are being displayed (rather than the first ones), this icon will appear at the left (and pointing in the other direction).

Info.gif Once activated, dynamic loading of entries is also available in the "Card View".

Info.gif The "Load more lines dynamically" function can also be activated for tables in the detailed views (e.g. in the applicant overview for a job — /Recruiting/Vacancies/ID/Selection). In this case, additional table entries are loaded not by scrolling, but by clicking. The reason is that most detailed views include a large number of elements. Dynamically loading table entries by scrolling would push elements under the table further and further down on the page.

Configure link

Various details can be specified for fields with links (using the Config.gif icon on the left next to the column header):

  • Link target: The link target fields serve as links within the system, and therefore only the extension (everything after "") needs to be specified. Refer to the original link (original content in the comment under the "Link target" field) to see the values that you can use as placeholders for the numbers (IDs) in the different URLs.
To insert a link target:
  • In configuration mode, find the relevant link and click on Config.gif
  • Enter the URL under "Link target" (e.g. /Employment/ProzessA).
Attention.gif Note: Since search links perform a search in the background and display the search result in the appropriate overview, link targets should only be configured if you understand exactly what search is performed by the search link (and whether the search is displayed).

For links to external sites, be sure to write out the complete link, beginning with http://www...

  • Open link in new window?: When this option is selected, the linked site will open in a new window. With "Default" preselected, the browser controls this automatically.

Info.gif See also User-defined links

Configure login pages

It is possible to customize the login page specifically for individual users. To do so, use the following links:

  • Administrator view:
  • User view for employees:
  • Hiring manager:
  • Board Member:

Hide search box on job board

It is also possible to hide the entire search box in the job board. To do this, use the following CSS code:
.icon.iab_hide::before { display: none; } div.container_actionbar_sh_AB { display: none; }

Special settings

Whatever is entered for the two special settings Hide (special setting) and Display / Input (special setting) applies only to the Role group for special view configurations defined in the settings. Schloss 16.png By default, all fields can be edited by all users and all entries are permitted. However, if a field is globally set to Display under "Display/Input", then no changes can be made by the user. Similarly, for predefined role groups such as "HR expert" and "Administrator", the field can be set separately to "Display" using the Configuration mode menu item "Display / Input (Special Setting)", so that only these role groups are prevented from editing the field.

More tips from consultants

Info.gif If you cannot edit certain texts in configuration mode, it could be that you are working on an element of the so-called fixed lists. Certain system-controlled texts appear as fixed lists so that they can be correctly displayed depending on the language. An example of this are the "Employee review meeting" areas on the "Overall assessment" page.

Info.gif Upload fields should not be defined as required fields or mandatory fields (mandatory fields: see under Error correction during entry) in configuration mode / entry mode, as this will trigger an error message.

Info.gif If you would like to configure the applicant, hiring manager or recruiter views, you can open a second browser (e.g. Mozilla Firefox, if you already have Internet Explorer open) and log in as the desired role. This lets you see how these areas appear to users in that role. If you want to configure a view, copy its Internet address into the address bar of the browser window where you are logged in as an administrator, and perform the configuration there.

Info.gif However, if you would like to configure a view for committee members (/SelfServiceBoard), your administrator access must first be assigned to a committee. After administrator access has been assigned, all you need to do is to release a job and an applicant to this committee member, and you can then make changes as usual.

Info.gif If you would like to make changes to pages that are accessed via links sent with tokens (?Key=), proceed as follows: Delete "?Key= Parameter" from the link and log in as an administrator, or copy the link without "?Key= Parameter" into the address bar of the browser window where you are already logged in as an administrator. Example URL for third parties without access (SelfServiceAppraisals):

/SelfServiceAppraisals/ID/Profile/Applications/ID/Profile/Appraisals/ID/EditAppraisal?Key=8663aa03e3f60e640342e6711d72fcad&customer=ID&lang=fre Delete "Key=8663aa03e3f60e640342e6711d72fcad" from the link.

Log in as administrator and add the changed link: /SelfServiceAppraisals/ID/Profile/Applications/ID/Profile/Appraisals/ID/EditAppraisal?&customer=ID&lang=fre

Common problems in Configuration mode

If Configuration mode is not working, or if no changes can be made, follow this procedure:

  1. Empty the cache, i.e. delete everything in the URL after “” and enter “?clearCache=true” in its place to force the cache to be emptied.
  2. Check whether Role groups for special view configurations have been applied; if so, remove them.
  3. Enter a New administrator password.
In other languages