The page cannot be used without entry points and depending on the entry point
used one role or other will be required.
FEA: ItEr76S30PermissionsEnhancements
Entry points can only be used by ROLE_BOUND_USER.
Moreover an extra checking has been added in the edit entry point to check that
the expense sheet is personal and it belongs to the worker bound to current
user.
FEA: ItEr76S30PermissionsEnhancements
Different situations:
* If user has ROLE_SUPERUSER: Redirect to "Planning > Company View"
* If user has ROLE_BOUND_USER: Redirect to "Personal Area > Home"
* If user has ROLE_PLANNING: Redirect to "Planning > Company View"
* If user has read or write authorizations over any project: Redirect to "Planning > Company View"
* Otherwise: Redirect to "Personal Area > Preferences"
FEA: ItEr76S30PermissionsEnhancements
Different situations:
* If user has ROLE_SUPERUSER: It'll keep working like before, if you set a
concrete URL you'll go to that URL, otherwise you'll go to "Planning > Company
View"
* If user has ROLE_BOUND_USER: Go to "Personal Area > Home"
* If user has ROLE_PLANNING: Go to "Planning > Company View"
* If user has read or write authorizations over any project: Go to "Planning >
Company View"
* Otherwise: Go to "Personal Area > Preferences"
FEA: ItEr76S30PermissionsEnhancements
* Projects Planning and Projects List: Allow access to ROLE_SUPERUSER,
ROLE_PLANNING and users that has any project authorization.
* Resource Usage and Limiting Resources planning: Allow access to
ROLE_SUPERUSER and ROLE_PLANNING.
FEA: ItEr76S30PermissionsEnhancements
If the user has read or write authorization over any project then the pages
"Planning > Company View" and "Planning > Projects" will be visible.
Configure properly the perspectives (tabs) in order to hide some of them if user
is not ROLE_SUPERUSER or ROLE_PLANNING.
FEA: ItEr76S30PermissionsEnhancements
Only bound users will have access to page "Personal Area > Home".
Moreover bound users will have access to expenses sheet edition form, even if
they don't have access to "Cost > Expenses" page.
Finally users with role ROLE_SUERUSER, ROLE_SUERUSER or ROLE_TIMESHEETS will
have access to monthly timesheets edition page.
FEA: ItEr76S30PermissionsEnhancements
* Move code for calculating all critical paths to its own class
* The former code broke in many clases so I reimplemented the algorithm
FEA: ItEr76S04BugFixing
The error was in the code that builds the graph for calculating the
CriticalPath. There was a very similar code for building the graph in
TemplateModel, the only difference were the two lines of the patch.
These two lines were changed for fixing bug #1423. I tried this bug
again with the patch applied and it works too.
FEA: ItEr76S04BugFixing
New role ROLE_WS_SUBCONTRACTING has been created, now the web services are
separated in two parts:
* Common web services are allowed to be read by role ROLE_WS_READER and written
by role ROLE_WS_WRITER
* Subcontracting web services are allowed to be read and written by role
ROLE_WS_SUBCONTRACTING
In this way you can give access to a different companies to your subcontracting
services, however prevent them to access to the rest of your data (via common
web services).
FEA: ItEr76S30PermissionsEnhancements
The problem was that before the change, the children of the order returned a
proxy when you used the method getOrder() over them. However, this doesn't
happen if you change the order of the parameters.
I guess that this is because of the converter of the Order is now called before
the converter of the OrderElement and the problem disappears.
FEA: ItEr76S04BugFixing
The casting was failing for milestones, because of they're leafs but not tasks.
Using method TaskElement.isTask() instead of TaskElement.isLeaf() to ensure that
the TaskElement is a Task and can be casted accordingly.
FEA: ItEr76S04BugFixing
