Early Access - The Dcycle CLI is currently available for enterprise customers.
Contact us to learn more about access.
Overview
Goals and actions are the planning layer of a project. They are shared by ISO management-system projects and CSRD ones, and the difference is only what they point at.- A goal is a target with numbers: a baseline, where it stands now, and what it aims at. Progress is how far it has travelled from baseline to target.
- An action is a piece of work. It has one primary source — the thing it exists to address, which is what its code is derived from — and may address further sources on top.
Links are written as
type:id, comma-separated, rather than JSON.
A goal linked to exactly one custom KPI also reports that KPI’s latest submissions, so its current value tracks the KPI instead of being typed by hand. Zero or several KPI links leave the numbers as entered.
Available Commands
Both commands require
--project. --org overrides the default organization.
List Goals
Flags
Create a Goal
Flags
Without all three of
--baseline, --current and --target, progress cannot be computed and the goal lists with no percentage.Edit a Goal
create, plus --status. --start-date and --end-date are create-only.
List Actions
addresses lists every source, primary first.
Create an Action
Flags
The Reverse View
0 actions has a target but no work behind it, which is usually the more interesting gap.
--type accepts the same seven source kinds as --link. An unknown one fails locally, without a request.
Example: plan against a materiality assessment
Related
CSRD
Double materiality and IROs, the sources these goals answer
Projects
The projects goals and actions live in