Discover the latest updates
Context and objective
Key enhancements
Ability to create multiple work calendars within a single environment.
Each calendar includes:
a customizable weekly schedule defined per day (0 / 0.5 / 1),
country-based preconfigured public holidays,
the ability to manually add custom public holidays.
Collaborators are assigned to a work calendar through their periods.
All key calculations (working days, absences, capacity) are now based on the collaborator’s calendar.
Update of the Teams module configuration to support advanced work calendar management.
Automatic creation of a “France” calendar for all existing environments, with automatic assignment of all existing collaborators.
Impacts
Timesheets & absences
Automatic application of non-working days and public holidays to empty and future timesheets.
Adjustment of recurring absences based on the collaborator’s weekly schedule and calendar holidays.
Capacity
Capacity calculations now reflect the collaborator’s work calendar.
When automatic alignment from absences is enabled, non-working days are taken into account.
Planning & project management
Non-working days from the default calendar are greyed out in project Gantt planning.
Durations expressed in working days within Gantt charts are calculated based on this calendar.
Project closure tasks take the collaborator’s calendar into account when calculating due dates.
Import / Export
A new “Work calendar” column has been added to the user export.
The same column is available in imports when multiple calendars exist.
If the column is empty during import, the default calendar is automatically applied.
Context and objective
User experience
A new “Enter my time” button appears on the Abraxio dashboard for users with occasional time entry enabled, with secondary access to “Enter my absences.”
Clicking “Enter my time” opens the current month’s timesheet directly, with the ability to navigate to past or future months.
If no values have been recorded on any timesheet, no timesheet is displayed.
As soon as at least one value is entered, the timesheet moves to the “to be completed” status.
The “Enter my time” / “Enter my absences” buttons also remain available in the Portfolio Summary tab.
Additional impacts
Teams interface
A new “Occasional entry” column has been added to the Teams > Collaborators table.
Excel exports
Addition of the “Occasional entry” column to the “User list” export.
In the timesheet export, only timesheets containing at least one entered value are included for collaborators with occasional time entry enabled.
API
Timesheets with no recorded entries are no longer returned by the API route.
Context and objective
Documenting key information that needs to be shared with all authorized collaborators.
Capturing personal, private “post-it” style notes intended solely for their author.
In this first release, notes can be associated with the following objects: projects, activities, suppliers, and contracts.
Note content and behavior
A free-text field.
A note type, configured in Admin > Transverse.
A date (defaulting to the current date, with no restriction on modification).
A public/private visibility status:
Private notes are visible only to their creator.
Public notes are visible to all users who have access to the parent object.
Notes are sorted from oldest to most recent and can be:
Pinned (displayed at the top of the list regardless of creation date),
Edited,
Deleted,
Filtered.
Creation and consultation
To create a note, the user must have edit permissions on the parent object (project, supplier, etc.).
A note can be created:
via the + button at the top right of the object,
via the contextual three-dot menu,
from the Notes section in the Management tab
(or from the Contract tab in the case of contracts).
Notes can be consulted from the same entry points.
Upcoming enhancements
Addition of a text search within the notes panel.
Extension of notes to a broader range of objects.
For more details, please refer to our dedicated article.
Context and objective
Decision details
This panel remains persistent while navigating within the same module.
Decision fields
Title
Reference (automatically generated if configured in Admin > Configuration > Transverse)
Owner
Associations:
One association per object type: project, activity, fiscal period, budget line, supplier, contract.
When a decision is linked to a budget line, the related project or activity is automatically added.
Instance:
Instances are configurable in Admin > Configuration > Transverse.
By default, two instances are available on all environments: Executive Committee (CODIR) and Steering Committee (COPROJ).
Analytical dimensions:
Up to three analytical dimensions can be enabled for decisions.
Attachments:
Documents can be added as attachments.
History
The full history is available in read-only mode via the History menu in the decision panel.
Permissions Overview – Decisions
Summary of permission rules for decisions based on their status:
| Decision status | Read | Create | Edit | Delete |
|---|---|---|---|---|
| Draft / Pending | If you have read access to an object, you can view decisions linked to it. | If you have edit rights on an object, you can create decisions for it. | Only the decision owner or designated decision-maker can edit the decision, provided they have edit rights. | Only the decision owner or designated decision-maker can delete the decision, provided they have edit rights. |
| Validated / Rejected / Abandoned | If you have read access to an object, you can view decisions linked to it. | If you have edit rights on an object, you can create decisions for it. | Decisions are read-only; only the owner/decision-maker can modify the status. | Deletion is not allowed; the decision’s status must be changed instead. |
Decision visibility rules
Summary
| Screen | Visible decisions |
|---|---|
| Project/Activity decision tracking | Decisions linked to the project/activity. Decisions linked to a budget line are visible only with access to the associated sub-budget. Budget-related decisions require read access to at least one project sub-budget. |
| Portfolio decision review | Aggregation of the rules above. |
| Supplier decision tracking | Decisions linked to the supplier or its contracts. |
| Supplier decision review | Aggregation of the rules above. |
| Fiscal period decision review | Decisions linked to the fiscal period are visible only with read access to the full budget. Decisions linked to a budget line require access to the associated sub-budget. |
| Budget line decision tracking | All decisions linked to the budget line. |
For further details, please refer to our dedicated article.
Context and objective
This feature is designed to facilitate data integration into BI tools, in particular Power BI.
Key points
New API access scope: “Supplier Dataset” (not automatically granted to existing API credentials).
Availability of several API endpoints to retrieve:
active or referenced suppliers,
contracts and key dates,
analytical dimensions (suppliers and contracts),
evaluations.
Introduction of a unique functional identifier for each contract, enabling easier data reconciliation and cross-analysis.
Update of supplier Excel exports, now based on this functional identifier for the Contracts, Key Dates, and Commitments tabs.
Upcoming enhancements
Availability of a demonstration Power BI report to visualize supplier, contract, key date, and evaluation data.
Restricted addition of collaborators to teams
Planned effort visibility in timesheets for all collaborators
The display of planned effort in timesheets is now configurable at the organization level:
Admin > Configuration > Teams > Timesheets
- Once the toggle is enabled, all collaborators have access to the planned column in their timesheets.
- If the option is disabled, manager profiles continue to have access to this column.
Harmonization of labels between Time Tracking and Timesheets
Changes in Time Tracking
“Loaded JxH” is now labeled “Entered worked JxH”.
“Entered JxH” is now labeled “Total entered JxH”.