Recent changes to issues

Inconsistent decimal handling in non-english environments

Flemming — Fri, 23 Nov 2012 11:44:20 -0000

Inconsistent handling of decimals in enviroments with decimal separator other than "."

In environments in which "." is not the standard decimal separator the display and entry of decimal numbers is inconsistent in a number of places. To reproduce start xProcess with the option "-Duser.language=de" (decimal separator ",") and try one of the following in a project based on the "Simple Project" pattern from the "Simple Process" (the list is probably not complete):

1. Parameter entry on task/project/folder creation
1.1 Create a new "Task": Size is displayed as "2.0" (expected "2,0")
1.2 When clicked the number changes to "2,0" (correct).
1.3 Decimals must be entered using "," (correct); an entry of "40.0" results is interpreted as "400" and saved accordingly (probably OK).

2. Size of Overhead Tasks
2.1 Create a new Overhead Task and save it.
2.2 Open the task in the task editor, change the Size to "2", save and close the editor.
2.3 Open the task in the task editor: The task is displayed as having changes ("*" prepended to task name in the tab handle) and the task size is displayed as "2.0" (expected "2,0").
2.4 Save, close and reopen the task in the task editor: The task has changes and a size of "20.0" (should have been "2,0") ...

3. Price Record Entry
3.1 Create a new Price Record Entry for a Person or an Organisation; the price field displays "0.00 EUR" (expected "0,00 EUR").

4. Preferences
4.1 All decimal values on the Process Designer/Diagram Print and Workflow Designer/Diagram Print preference pages are displayed using "." as decimal separator and must be entered with "." as separator to be interpreted correctly (expected ",").
4.2 The entry of a number containing a "," results in a error message; the preferences cannot be applied.

I am currently trying to identify the source of the problem and hope to supply patches soon.

Custom columns (Javascript/OGNL) operating on wrong element

Flemming — Sun, 11 Nov 2012 10:45:22 -0000

Custom columns for tasks do not work correctly when Javascript or OGNL is used. Instead of operating on the current element they work on a task pattern. For example "#element.getName()" (Javascript) results in "$Name$" whereas "/getName" (reflection) correctly returns the name of the current task.

The problems seems to be located in com.ivis.xprocess.ui/src/com/ivis/xprocess/ui/tables/columns/custom/CustomColumn.java where in the case of Javascript and OGNL "getTestElement()" is passed to the processor instead "realElement" as in the case of reflection.

Suggested fix in CustomColumn.patch.txt attached.

Effort label "hours" inconsistent with preferences

Flemming — Mon, 14 May 2012 15:35:43 -0000

In the editor for parent tasks on the Required Resources tab the time unit label for Subtask and REST Estimate of Effort is "hours" even if Decimal Days has been set as time unt for effort estimates. The value is correct (in days not hours).

Drawing problem with current Beta on Win 7

Flemming — Tue, 27 Mar 2012 17:32:09 -0000

We are experiencing serious drawing problems with the newly released BETA version. The only solution is to restart xProcess (using Alt+F4 if the menu or close button are not usable). Will upload a sample screenshot.

At the moment we cannot say in which situations the problems occur.

Our setups:
- xProcess Beta 3.6.1.18476
- Windows 7 64-bit
- Oracle JRE 1.6.0_31-b05

Extend allowable constraints (feature request)

Andy Carmichael — Tue, 21 Feb 2012 09:59:05 -0000

the following dependencies should be allowed in xProcess:
- a task to depend on itself, e.g. to create a task running for 10 days: END must be after FORECAST START offset 10 days
- a task to depend on another task twice, again to create a 10 day task:
- Task 2 START must be after Task 1 FORECAST END
- Task 2 END must be after Task 1 FORECAST END offset 10 days

xProcess changes default values for Action Parameters

C R — Fri, 17 Feb 2012 08:50:04 -0000

When trying to define a default value for an "Action Parameter" of type FLOAT, xProcess changes the default value several times.
If I enter x as a default value, and hit "OK", xProcess will - sometimes - change that value to 10*x. When hitting "Ctrl+S" afterwards, xProcess will again - and always - multiply that value by 10, and change the value to 100*x.

Screenshots attached.

I am using the following version:

Version: Beta 3.6.0.18417
Build id: 3.6.0.18417
Build date: 25-Jan-2012

Patterns with the same name should not be allowed ...

Andy Carmichael — Tue, 14 Feb 2012 15:09:23 -0000

... in the same process. UI should prevent this but if they occur (e.g. by multi-user actions or historically) an alert should be generated.

If a process does not define a project pattern...

Andy Carmichael — Tue, 14 Feb 2012 14:08:31 -0000

...it does not allow you to create a project with the process even if it inherits a project pattern from other processes. It should allow this

xProcess does not show "fully qualified names"

C R — Tue, 14 Feb 2012 11:24:50 -0000

When trying to create a new task in the right-click context menu the activation of "Show fully qualified names" does not change a thing. The only names I may see remain the "presentation names" of the objects. This is annoying when having several different patterns of the same name.
I have appended a screenshot.

Thanks a lot for any help on that matter,
C.

Repeating date-based tasks (feature request)

Andy Carmichael — Mon, 13 Feb 2012 14:45:08 -0000

Date-based or "overhead" tasks in xProcess can span over an extended period (e.g. a general overhead task consuming a percentage of everyone's time over the whole project) but xProcess assumes the task should be scheduled on every day in the period. It is not currently possible to define a date-based task that repeats at regular intervals such as every 2nd Tuesday or the second Friday or the month. This is useful for repeating events in approaches such as Scrum. Another motivation is the desire to integrate xProcess with team members diaries. Since such events are easy to define in most calendar systems having this feature makes such integration more straightforward.

UI suggestions: https://sourceforge.net/apps/mediawiki/xprocess/index.php?title=US105:_Define_a_Repeating_Date-based_Task