Updating deprecated articles ahead of releases and informing recommended actions e.g. DateTime function now ISO8605

In 2026 build, the new ArcGIS Feature Services package replaces the older Portal Feature Service reader. The change is well documented in the article Working with Esri ArcGIS Feature Services in FME – FME Support Center

My question to a Safer is, how/when are 2026 deprecated formats like PORTALFEATURESERVICE listed in the article FME Deprecations – FME Support Center.

Can these now older ArcGIS Feature Service formats be added to the article; along with Recommendation actions listing out sections/bookmarks from the support article

Question about deprecations article

1. When do components get included to the article and how is it updated? 
2. is this a manual task or can the development team inform earlier updates when components are planned to be replaced?

Recently for example, randomly FME Date Time functions got added to the article, where it was listed as affecting in 2026.1…. yet we were already at 2026.2 release?

This would have been much handier to know about these ahead of time, earlier

Regarding the FME DateTime deprecation changes, DateTime functions and formats now default to ISO 8601. While this is understandable, there are a number of existing workspace patterns that may require review or future remediation.

For example, many workspaces use @DateTimeNow() and related functions within published parameters, transformers, or dataset paths to generate attribute values that are subsequently used for:

1. File writing and dataset fan-out

   Examples include dataset paths such as:

   \\Path\Output_@DateTimeFormatter(,%Y%m%d).csv

   which currently resolve to:

   \\Path\Output_YYYYMMDD.csv

   My understanding is that these workflows continue to function today. However, over time we will likely need to transition to the newer ISO-based DateTime functions and formatting approaches.

   Additionally, when modifying or replacing transformers that use legacy DateTime formats, FME often defaults the configuration to ISO formatting. In some cases we actually need to retain the traditional FME numeric DateTime format, so this can introduce unexpected issues if not identified during testing.

2. Published Parameters and Flow Apps

   We've also found that parameter defaults based on expressions such as @DateTimeNow() or @DateTimeDiff() no longer work in some Date-type user parameters. As a result, workflows that previously relied on dynamic default dates may now require alternative approaches, such as Dynamic Parameters when exposed through FME Flow Apps.

My main request is simply for earlier visibility of these types of changes, along with practical guidance on their real-world impacts. Articles, migration notes, examples, and "watch-outs" for common workspace patterns would be extremely valuable in helping us identify what needs to be maintained, updated, or tested before these deprecations become mandatory.