Daily Digest: 2026-04-23

[github-actions]

We are given a daily digest for 2026-04-23. We need to structure the response as:

1. Highlights (1-3 bullet points of the most important changes)
2. Code Changes (summarize commits by theme, not individually)
3. Pull Requests (merged, opened, pending review)
4. Issues (new, closed, total open)
5. Repository Health (stars, forks, CI status)
6. Action Items (anything that needs attention: failing CI, stale PRs, unanswered issues)

Let's break down the provided data:

Repository Stats

• Stars: 74
• Forks: 22
• Watchers: 6
• Open issues: 1

Commits (last 24h)

There are many commits, but we are to summarize by theme.

Looking at the commits, we can see several themes:

• Microflow-related fixes (preserving various aspects like rule split, subtype, captions, nested IF, etc.)
• Expression parser improvements (built-in function case, qualified function calls)
• Workflow and catalog-related fixes (CE1613 for workflow-user-targeting, catalog builder and linter tests)
• Miscellaneous (help statement in test, etc.)

Pull Requests Merged (last 24h)

• No PRs merged.

Pull Requests Opened (last 24h)

• No new PRs.

Currently Open PRs

We have a list of open PRs (from #217 to #271, but note that some are old). We are to note the pending review (i.e., currently open).

Issues Opened (last 24h)

• feat: Manage Workflow Groups via MDL #272: feat: Manage Workflow Groups via MDL
• Roundtrip and integration-harness stabilization — batch of small fixes #257: Roundtrip and integration-harness stabilization — batch of small fixes (note: this was opened earlier, but we are only counting those opened in the last 24h? The data says "Issues Opened (last 24h)" and lists two: feat: Manage Workflow Groups via MDL #272 and Roundtrip and integration-harness stabilization — batch of small fixes #257. However, note that Roundtrip and integration-harness stabilization — batch of small fixes #257 might have been opened earlier but is being referenced again? We'll take the list as given.)

Issues Closed (last 24h)

• Daily Digest: 2026-04-22 #250: Daily Digest: 2026-04-22
• feat: Catalog Integration: Search and Discovery #213: feat: Catalog Integration: Search and Discovery
• feat: Support file:// URLs for OData metadata in CREATE ODATA CLIENT #206: feat: Support file:// URLs for OData metadata in CREATE ODATA CLIENT
• Support TARGET USERS clause on workflow USER TASK definitions #169: Support TARGET USERS clause on workflow USER TASK definitions

CI Status (latest runs on main)

We have three workflow runs:

• Daily Project Digest [2026-04-23T08:49:21Z] (no status indicated? Actually, the way it's written:
  • — Daily Project Digest 2026-04-23T08:49:21Z
  • success — AI Issue Review 2026-04-23T08:33:44Z
  • skipped — Enhancement Guide 2026-04-23T08:33:27Z

So:

• Daily Project Digest: no status emoji? It might be missing, but in the context we can assume it's the current run and we don't have a status? However, note that the digest is being generated, so it might be in progress or just completed without a status emoji? But the format shows a dash for the first one. Let's interpret:
  • The first run (Daily Project Digest) has no status emoji (just a dash) meaning it might be the one that is currently running? Or it's a placeholder? Actually, in the data it's written as:
    " — Daily Project Digest 2026-04-23T08:49:21Z"
  • The second has "success", the third has "skipped".

We'll note the CI status as:

• AI Issue Review: success
• Enhancement Guide: skipped
• Daily Project Digest: (no status given, but since it's the latest and we are generating the digest, it might be the one that just ran? However, without a status we cannot say. But note: the digest is for 2026-04-23 and the run is at 08:49:21Z, which is recent. We'll have to see if there are any failures. Since no status is given, we might assume it's not failed? But to be safe, we'll note that the Daily Project Digest run doesn't have a status emoji, so we cannot confirm. However, in the context of the digest, we are to report on CI status. We'll look for any failures.

Alternatively, note that the data says "CI Status (latest runs on main)" and lists three. We don't see a failure mentioned.

Dependency Changes

• None.

Now, let's structure the response:

1. Highlights

We need 1-3 bullet points of the most important changes.

From the commits, we see a lot of work on microflow roundtrip preservation (several commits about preserving rule split, subtype, captions, nested IF, etc.) and expression parser improvements (qualified function calls, built-in function case). Also, there are fixes for workflow and catalog.

Given the volume, we can highlight:

• Significant improvements to microflow DESCRIBE and roundtrip stability (preserving various elements like captions, rule splits, nested structures)
• Expression parser enhancements to handle qualified function calls and normalize built-in function case
• Workflow-related fix for CE1613 (UserGroup absent in workflow-user-targeting)

But note: the digest is for a single day, and we have many commits. We'll pick the most prominent.

Alternatively, note that the open issues include a stabilization issue (#257) and a new feature for workflow groups (#272). The closed issues show progress on catalog and workflow features.

Let's choose:

• Microflow roundtrip improvements: multiple commits focused on preserving microflow elements during DESCRIBE and roundtrip operations.
• Expression parser updates: now supports qualified function calls and normalizes built-in function case.
• Workflow fix: addressed CE1613 for workflow-user-targeting when System.UserGroup is absent.

2. Code Changes

Summarize commits by theme.

Themes observed:

• Microflow preservation:
  • Preserve rule split describer output and free annotations (27c0dc9, 57f8739, 6afde3c, 907184b, etc.)
  • Preserve rule-based decision subtype (56d8606)
  • Preserve decision/loop captions in nested control flow (1a202e5, 25a4252, 67263fa, 94bded8, cdfb0d0)
  • Handle terminal nested IF in flow builder (f850a37, 67263fa)
  • Gate Mx9 microflow roundtrip keys by project version (7b297fb, 971dc43)
• Expression parser:
  • Normalize built-in Mendix function case (8833afa, cf6860c)
  • Accept qualified function calls (0118360, e744810)
• Workflow and catalog:
  • Allow CE1613 for workflow-user-targeting (9656d2a)
  • Catalog builder and linter tests (multiple commits: 2a5be7f, 9767368, 5bd8d68, 9019199, e765498, 51ead9e, 593e19a)
• Miscellaneous:
  • Fix HelpStmt in test (e351f04)
  • Stabilize MDL roundtrip and integration test harness (PR fix: stabilize MDL roundtrip and integration test harness #267, but note: we don't have the commit for that? Actually, we see a commit for PR fix: stabilize MDL roundtrip and integration test harness #267? Not in the list. The list of commits doesn't include fix: stabilize MDL roundtrip and integration test harness #267. But we see an open PR fix: stabilize MDL roundtrip and integration test harness #267.)

3. Pull Requests

• Merged (last 24h): None.
• Opened (last 24h): None.
• Pending review (currently open):
  We have the following open PRs (from the list):
  fix: DESCRIBE PAGE recurses into ScrollContainer / TabControl children #271, fix: correct microflow body syntax in bug-test 258 #270, feat: import consumed REST client from OpenAPI 3.0 spec #268, fix: stabilize MDL roundtrip and integration test harness #267, fix: support log node expressions and harden microflow describe roundtrip #264, Update parsing of ScrollContainer and TabControl #219, fix: handle Microflows$Find, $Filter, $ListRange in list operation DESCRIBE #217
  Note: Some are old (like fix: handle Microflows$Find, $Filter, $ListRange in list operation DESCRIBE #217 and Update parsing of ScrollContainer and TabControl #219 from earlier). We are to report the currently open ones.

4. Issues

• New (last 24h): 2 (feat: Manage Workflow Groups via MDL #272 and Roundtrip and integration-harness stabilization — batch of small fixes #257)

• Closed (last 24h): 4 (Daily Digest: 2026-04-22 #250, feat: Catalog Integration: Search and Discovery #213, feat: Support file:// URLs for OData metadata in CREATE ODATA CLIENT #206, Support TARGET USERS clause on workflow USER TASK definitions #169)

• Total open: from the repo stats, we see "Open issues: 1". But note: the stats say "Open issues: 1", however we just closed 4 and opened 2, so the net change would be -2? But the stats are given at the top. We must use the provided stat: Open issues: 1.

  However, note: the stats table says "Open issues: 1". This is the current state. So despite the activity, the total open is 1.

5. Repository Health

• Stars: 74
• Forks: 22
• Watchers: 6
• CI Status:
  • AI Issue Review: success
  • Enhancement Guide: skipped
  • Daily Project Digest: (no status emoji, but we don't see a failure mentioned) -> we'll assume it passed or is in progress? Since we are generating the digest, and the run is recent, and no failure is indicated, we can note that there are no reported failures in the CI runs listed.

6. Action Items

We need to look for:

• Failing CI: none reported in the listed runs.
• Stale PRs: we have some old PRs (like fix: handle Microflows$Find, $Filter, $ListRange in list operation DESCRIBE #217 and Update parsing of ScrollContainer and TabControl #219) that are still open. We should check if they are stale.
• Unanswered issues: we don't have comment data, but we can note if there are issues without recent activity? However, we don't have that detail.

Given the data, we can note:

• There are several old PRs still open (e.g., fix: handle Microflows$Find, $Filter, $ListRange in list operation DESCRIBE #217 from 2024? We don't have dates, but the numbers are low: fix: handle Microflows$Find, $Filter, $ListRange in list operation DESCRIBE #217, Update parsing of ScrollContainer and TabControl #219, then jumping to fix: support log node expressions and harden microflow describe roundtrip #264 etc.). These might be stale and need attention.

• The open issue count is 1 (according to the stats), but we see two new issues opened in the last 24h and four closed. This implies that the open issue count of 1 is the current total, meaning that after the activity, there is only one open issue left. However, we don't know which one. But note: the stats are provided at the top, so we trust that.

  Alternatively, the stats might be as of the beginning of the day? But the digest is for the day, and the stats are given. We'll use the provided stat: Open issues: 1.

  Therefore, we don't have a backlog of issues.

But we do have old PRs. Let's note:

Action Items:

• Review and potentially close stale PRs (e.g., fix: handle Microflows$Find, $Filter, $ListRange in list operation DESCRIBE #217, Update parsing of ScrollContainer and TabControl #219) that have been open for a long time.
• Ensure that the CI for the Daily Project Digest runs successfully (though we don't see a failure, we should monitor).

However, without more data on the age of the PRs, we can only note that there are open PRs that are old (based on the low numbers).

Let's write the digest.

Note: We must be concise.

Let's draft:

Highlights

• Multiple commits improved microflow roundtrip stability, preserving elements like rule splits, captions, and nested structures.
• Expression parser now supports qualified function calls and normalizes built-in function case.
• Fixed workflow-user-targeting to handle CE1613 when System.UserGroup is absent.

Code Changes

• Microflow: Enhanced preservation of rule splits, decision subtypes, control flow captions, and nested IF handling; added version gating for Mx9 features.
• Expression: Normalized function case and added support for qualified function calls in parsing.
• Workflow/Catalog: Fixed CE1613 for workflow-user-targeting; added unit tests for catalog builder and linter rules.

Pull Requests

• Merged: None in the last 24h.
• Opened: None in the last 24h.
• Open: 7 PRs awaiting review (including fix: support log node expressions and harden microflow describe roundtrip #264, fix: stabilize MDL roundtrip and integration test harness #267, chore: normalize CRLF to LF in bug reports #26

---

Daily digest generated automatically — workflow source