Vergleichsreport

PtmAttendanceServiceImpl

timeAccountName

Full Text, enter name (default: twistzeit)

In this field, you enter the name of the time account from the Interflex 6020 time recording system with whose balance the project time is to be compared (for comparison of project time vs. attendance time). The account must contain the daily actual working time of a person. If the parameter is empty, an attendance time of 0 is assumed.

PtmAttendanceServiceImpl

workingTimeDailyRightName

yet unknown

PtmAttendanceServiceImpl

zeroWorkingTimeUnlessRightSet

yet unknown

monthlyTimeAccountName

Full Text, enter name (default: vksumme)

Optional Interflex 6020 account holding the month-end value of the actual working time. If set, monthly attendance times (e.g. for the yearly project effort report or the job ReaccountMonthlyTimeEfforts, which redistributes the monthly efforts) are read directly from this monthly value instead of summing up the daily values of timeAccountName. For the current month, or if no monthly value is available, the daily values are still used. If the parameter is empty, the daily values are always used.

PtmAttendanceServiceImpl

workingTimeDailyRightName

-

Removed. This system parameter no longer exists. The attendance time is taken directly from the account configured in timeAccountName.

PtmAttendanceServiceImpl

zeroWorkingTimeUnlessRightSet

-

Removed. This system parameter no longer exists. The attendance time is taken directly from the account configured in timeAccountName.

PtmOptions

allowAnyGroupTypeForActivityConstraints

"true" or "false" (default: false)

A certain activity can be assigned to all group types during project booking (useful, for example, if the hierarchical groups are already allocated according to cost centers or are identical to these).

false:  A certain activity in the project posting can only be assigned to the group type "Cost center" (here a cost center structure must first be created, this is useful if a separate cost center structure is required, e.g. if the cost centers are structured differently from the hierarchical groups).

PtmOptions

approverCanReject

"true" or "false" (default: true)

The person responsible for approving project times (if subject to approval) can not only approve but also actively reject them.

false:  the person responsible for the approval can only approve project times (if subject to approval), but cannot reject them

A value in the client setting "Can approver decline the effort?" takes precedence.

PtmOptions

customerShownInProjectChooser

"true" or "false" (default: true

A dropdown list for selecting the )

The customer is available shown as a filter option for the project list during booking

false: The dropdown list for filtering projects by customer is not visible in the project booking action by default.

column and as a filter (dropdown list) in the project chooser dialog, so the project list can be filtered by customer.

false: The customer column and filter are not shown in the project chooser dialog.

A value in the client setting "Shall customer be shown as column and filter field in project chooser dialog?" takes precedence.

PtmOptions

deleteKioskEffortsBelowMinutes

insert a number of minutes (default: 0)

This is only relevant for Kiosk customers!

Here, you enter the number of minutes below which the project time booking is automatically ignored. If, for example, "2" is entered, all bookings that have lasted less than 2 minutes are automatically deleted - this prevents, for instance, accidental bookings.

With the default 0 all bookings are kept. A value in the client setting "Immediately delete stopped efforts booked on Kiosks if shorter than X minutes" takes precedence.

PtmOptions

initialStateExistsInApprovalWorkflow

"true" or "false"

yet unknown

(default: false)

true: new project times first get the state INITIAL in the approval workflow and have to be submitted.

false: new project times are submitted immediately (state SUBMITTED).

A value in the client setting "Is there INITIAL state in ApprovalWorkflow?" takes precedence.

PtmOptions

levelIsAMaximum

"true" or "false" (default: true)

Depending on the hierarchy levels defined for the element types, only certain element types can be selected for a new project that is assigned to a higher-level/parent project. The hierarchy level defined for these element types must be at least the same as or larger than the level defined for the project.

If, for example, the new project is designated to be on level 4 by being sub-project of a level 3 parent project, only element types starting with level 4 (and larger, i.e. 5, 6, 7, ...) are available to select for this project.

false:  In this case, only element types that have defined the exact level into which the new project is to be placed are available.

If level 3 is planned for the new project by the parent project being level 2, only those element types are available which have EXACTLY level 3.

PtmOptions

notifyEffortRejectsByMail

"true" or "false" (default: false)

The person who has booked project time receives a notification by e-mail if the booking is rejected (not confirmed) by the superior.

false: there will be not e-mail notification

This parameter is currently dormant and fulfills no function!

A value in the client setting "Notify rejected efforts by email" takes precedence.

PtmOptions

projectAdminRoleName

Full Text, insert a role name (default: ProjektAdmin)

Here you enter the name of the role that exists in the system and is to be given collective rights to edit all projects stored in the system.

PtmOptions

projectAttributeNames

add fields via the button "add" (default: Wichtigkeit, Kostenfaktor, Termingebunden)

Here additional fields can be added, which should be visible for each project in the project view and can be filled with additional information

These attributes are preset (empty) on newly created projects and are offered as additional fields (prefixed with "_") in the project connector for import and export.

PtmOptions

projectAuthorRoleName

Full Text, insert a role name (default: ProjektAutor)

Here you enter the name of the role existing in the system which is to be given the right to create new projects in the project overview using the "New Project" button.

PtmOptions

projectChooserShowsProjectEffortStats

"true" or "false" (default: false)

true: the project chooser additionally shows key project figures (planned hours, hours booked to date, billable hours booked to date, open hours).

A value in the client setting "Shall the project chooser display key project effort statistics?" takes precedence.

PtmOptions

projectChooserShowsTreeViewInitially

"true" or "false" (default: false)

true:  in the project booking mask the tree view is shown by default to select the projects for booking

false: the tree view is not shown by default, instead the list view appears for project selection

A value in the client setting "Shall the project chooser dialog initially show tree view?" takes precedence.

PtmOptions

projectLongLabelParentsSeparator

enter any desired character string (default: " -> ")

Selection of the character string (e.g. "-->") which is to be used in the "LongLabel" representation to separate higher-level projects from their subprojects.

e.g. if parameter is ">>" then the view is as follows: Parent project >> Subproject Subproject

Only applies if projectLongLabelShowsParents is active. A value in the client setting "Time effort: Separator sequence for parent projects" takes precedence.

PtmOptions

projectLongLabelShowsParents

"true" or "false" (default: true)

true: the "LongLabel" representation of a project also shows its parent projects (separated by projectLongLabelParentsSeparator).

A value in the client setting "Time effort: Shall parent projects be displayed?" takes precedence.

PtmOptions

projectLongLabelVelocityScript

Velocity text pattern (default: $name)

Text pattern for the "LongLabel" representation of a project in project time; parent projects are shown with the same pattern.

A value in the client setting "Time effort: Template for display of project names" takes precedence.

PtmOptions

projectMediumLabelVelocityScript

Velocity text pattern (default: $shortName ($name))

Text pattern for project names in project views (e.g. project chooser).

A value in the client setting "Project: Template for display of project names" takes precedence.

PtmOptions

selfApprovalGroupNames

list of group short names (default: empty)

Short names of groups whose members may approve their own project times.

A value in the client setting "Short names of groups whose members can approve their time efforts themselves" takes precedence.

PtmOptions

showActivity, showCustomer, showChargeable, showTA, showTime

"true" or "false" (default: showActivity false, showCustomer false, showChargeable true, showTA true, showTime false)

Defaults for whether the project time actions (time effort entry, favorites, project effort reports) show the activity, the customer, the chargeable flag, the comparison with working time (attendance) or the time intervals (from-to times). If a value is set in the action configuration, it applies.

A value in the client settings "Time effort: Show activity", "Time efforts: Show customer", "Time effort: Show chargeable flag", "Time effort: Show comparison with working time" or "Time efforts: Show time intervals" takes precedence over the system parameter.

PtmOptions

useEffortStateAndApprovalWorkflow

"true" or "false" (default: true)

true: the state of a project time (e.g. submitted, approved, rejected) is shown and used for the approval workflow.

false: project times are managed without a state; the action for approving project times cannot be used.

A value in the client setting "Shall effort state be displayed and used for workflow control?" takes precedence.

PtmOptions

usePtmAttendanceTimeAfterDays

number of days (default: -1)

Number of days in the past for which time effort entry queries attendance data directly from Time & Attendance; for days further back the attendance data stored in project time is used (faster). 0: always use the project time attendance data; -1: always use the Time & Attendance data.

A value in the client setting "Use PTM attendance data instead of TA attendance data after this many days" takes precedence.