Hi Tal,
I checked this as well, and I believe you have identified a real difference between the Architect UI export and the current Archy CLI export.
The Architect UI explicitly provides the "Include tracking ID details" option when exporting a flow as YAML, which adds the tracking IDs for actions, menus and tasks.
However, looking at the documented options for:
archy export --exportType yaml
I also cannot find an equivalent parameter such as --includeTrackingIds or --includeTrackingIdDetails.
What is interesting is that Archy clearly has access to these IDs internally, since Tracking IDs are frequently exposed in Archy validation/debug output. The missing piece appears to be the ability to instruct the YAML exporter to serialize them.
This would be especially valuable for CI/CD and source-control scenarios, where preserving the identity of an Architect object makes comparisons between flow versions much more reliable.
So unless there is an undocumented option available through --optionsFile, I believe this capability is currently exposed in the Architect UI but not through the Archy export command.
It would be great if someone from Genesys could confirm whether this is intentional, or if an equivalent Archy export option is planned.
------------------------------
Fernando Sotto dos Santos
Consultor de Atendimento Senior Grupo Casas Bahia
------------------------------