DateTimeDiff vs GetDayOfWeek in Architect Data Action JSON mapping

Could someone explain the evaluation order of date functions within Architect Data Action JSON mappings? I am building a webhook payload that requires conditional logic based on the day of the week and the age of a record. I have tried using DateTimeDiff to calculate the age in days and GetDayOfWeek to determine the current weekday. The issue arises when I nest these functions inside a JSON string value. I am attempting to map a field like this: {"isWeekend": "${GetDayOfWeek() in ['Sat','Sun']}"}. This fails validation. I suspect the expression engine does not support array containment syntax directly within the JSON template string. I have tried wrapping the logic in a separate step using DateTimeDiff(${record.createdTimestamp}, ${now()}, 'days') but the resulting integer is not being cast correctly for the downstream API. I need to know if I should use a Data Action to pre-calculate these boolean flags before the JSON mapping step or if there is a specific syntax for inline date comparisons. I am using the standard REST endpoint for the integration. The error is a generic JSON parse error. I have verified the tokens are valid via Vault. I need the exact expression syntax for comparing dates in this context.

The documentation actually says Architect evaluates expressions sequentially. Nesting complex date logic in JSON strings causes parsing errors. Use intermediate variables instead.

{
 "payload": {
 "isWeekend": "{GetDayOfWeek(CurrentTime()) == 0 || GetDayOfWeek(CurrentTime()) == 6}",
 "ageDays": "{DateTimeDiff(RecordCreated, CurrentTime(), 'days')}"
 }
}

Separate calculation from mapping.

This is actually a known issue…

The suggestion above is technically correct but misses the real pain point. Architect’s JSON parser chokes on nested function calls because it tries to evaluate the string literal before resolving the expression context. I hit this exact wall last week while building a React Native client that needs to sync local state with Architect attributes. The workaround isn’t just about intermediate variables; it’s about forcing the evaluation order. You need to calculate the boolean in a separate Set Variable action first. Then, map that variable into the JSON payload.

{
 "payload": {
 "isWeekend": "{WeekendCheck}",
 "ageDays": "{DaysOld}"
 }
}

If you inline the GetDayOfWeek logic directly, the parser throws a syntax error during the webhook call. It’s frustrating because the docs imply direct mapping works, but in practice, the expression engine gets confused by the JSON string escaping. Keep the logic in distinct steps.

This issue stems from the expression parser treating nested function calls as invalid JSON syntax during the initial string interpolation phase. The SDK enforces strict evaluation order, preventing complex logic inside literal strings. Review the internal parsing rules here: https://genesyscloud.docs.fake/architect/expression-parsing-rules. Use intermediate data action steps instead.

Have you tried offloading this logic entirely out of Architect? Embedding complex date math in JSON mappings creates brittle flows that are painful to debug. I handle similar conditional payloads by triggering a webhook to an AWS Lambda function. Let Node.js process the date logic, then return a clean, pre-calculated JSON object. This keeps your flow clean and leverages actual programming logic instead of fighting the expression parser.

// Lambda handler example
exports.handler = async (event: any) => {
 const created = new Date(event.body.created);
 const now = new Date();
 const diffDays = Math.floor((now.getTime() - created.getTime()) / (1000 * 60 * 60 * 24));
 const day = now.getDay();
 const isWeekend = day === 0 || day === 6;

 return {
 statusCode: 200,
 body: JSON.stringify({ ageDays: diffDays, isWeekend })
 };
};

This approach gives you full control and avoids parsing errors.