decídalo
Documentation
Ask AI
Search Results for

    Show/Hide Table of Contents

    Project status automation

    To simplify the handling of resource requests or bookings assigned to projects, decídalo supports with an automatic postprocessing of project status changes. The automation can be activated and configured in the ‘Administration’ menu item under ‘Resource management’ and ‘Project Status Automation’.

    Note: Only users with the permission ‘Manage Users, Teams, and Permissions’ can configure the automation. It is activated by default.

    Project status automation table mapping each project status to booking and resource request statuses, with an on/off switch

    The automation can be activated by the switch in the top right corner, and configured using the selection dropdowns in the displayed table. A typical example use case is: If a project is withdrawn, all connected resource requests and bookings should be rejected, because they are not needed anymore. By default, this is already set up and can be seen in the 4th row of the table.

    Team bookings

    By default, the automation only moves bookings on people. To have it move team bookings as well, switch on Include team bookings below the table. The switch is off by default, marked as beta, and can only be changed while the automation is activated.

    With Include team bookings switched on, team bookings follow the same table as bookings on people, in all three automations: the project status, the project plan status and a withdrawn resource request. The pop-ups that announce a status change list the team bookings' transitions as well.

    • A team booking that the automation moves into the status the booking workflow starts on (reserved by default) takes part in the team booking workflow, exactly as if it had been set to that status by hand. With Team bookings switched on, the team lead gets an approval task (see Team bookings).
    • A team booking that the automation rejects no longer counts towards utilization on the team timeline or the resource plan (see Booking status).

    Position status

    If the Position status data field is active for bookings (see Position status), the table also shows what each project status does to the position status of the project's bookings:

    • Planned, Active and Completed mean that the project is won. Reaching one of them first sets the position status of the project's bookings to Confirmed and then applies the configured booking status transitions.
    • Every other project status keeps a soft booking soft while its own position is unconfirmed, even if the soft transition leads to reserved or confirmed. Soft bookings on confirmed positions follow the configuration as before.
    • Reserved and confirmed bookings always follow the configuration, and withdrawing a booking (rejected) is never held back.

    Which project statuses confirm positions is fixed and cannot be configured. The project plan status automation behaves the same way. When the project status is changed on the project page, the pop-up that announces the upcoming changes also names the position status changes.

    Confirming positions this way has the same effect as confirming them by hand: if the booking workflow starts on soft bookings, the approval tasks that waited for the positions are created and their emails are sent (see Approval while the position is unconfirmed).

    Note: If the booking workflow starts on soft bookings (see Workflow start status), set the soft booking transition of the project statuses Active and Completed to Soft. By default they move soft bookings to reserved, which takes them out of the workflow before anyone has approved them.

    Note: When a resource request is set to ‘Done’ or ‘Withdrawn’, by the automation or by hand, its open internal marketplace applications and candidate suggestions are rejected as well, the request is taken off the internal marketplace, and the applicants are informed by email. One project status change can therefore close several requests and notify every applicant on each of them.

    Note: Changes to the project status automation will only apply in the future and will not modify existing data.

    Note: The ‘Deleted’ row is activated, if the project status automation feature is activated globally. The row cannot be edited. That ensures the automatic deletion of orphan resource requests and bookings, after a project has been deleted. Team bookings are deleted with the project as well, whether or not Include team bookings is switched on.

    In This Article
    Version history Back to top Copyright © data assessment solutions · decidalo.com