log_learning
Log new Workday Studio patterns, schema rules, errors, and workarounds to a generalized shared knowledge base so teammates avoid repeating the same debugging.
Instructions
CALL THIS AUTOMATICALLY whenever you discover a new Workday Studio pattern, schema rule, gotcha, or workaround during a build session — even if the user did not ask you to log it. This is how the team's shared knowledge base grows. Examples of when to call this: a build fails with an error not already in the step-type reference, Studio silently rejects an element, MVEL throws an unexpected exception, a diagram crashes on open, a workaround fixes something with no documented cause. Do NOT call it for things already documented in get_step_type_reference or docs/studio-integration-patterns.md.
PUBLIC-REPO RULE — GENERALIZE EVERY FIELD: learnings.md is published in a public repository used across clients. Never include client integration IDs (use INT999), project names, tenant or environment names (use ), custom field names, or run/log identifiers. Describe provenance generically ("verified in a live run", "observed in a production build") — the technical pattern is the value, not where it came from.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>",
"category": "<category>",
"trigger": "<trigger>",
"pattern": "<pattern>",
"promote_to": "<promote_to>"
},
"name": "log_learning"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Short descriptive title, e.g. "cc:splitter cannot have routes-to attribute" | |
| example | No | Minimal XML/MVEL/XSLT snippet showing the correct or incorrect form | |
| pattern | Yes | What we learned — specific and actionable, written for a teammate who will hit this next | |
| trigger | Yes | What caused the discovery — the exact error or unexpected behavior observed | |
| category | Yes | The type of learning | |
| promote_to | Yes | Which file(s) this should be promoted into during the next review |