In a custom script module, leveraging $Request.Put does not trigger a Change Workflow or other scripted customization (4377698)

When creating a custom script module, leveraging the $Request.Put method does not fire a Change Workflow or scripted customization that has triggering conditions which match updating that attribute.

For example:

function updateBoolean($Request)
{
    $Request.Put($edsvaBoolean, $TRUE)
}

This function would update the custom edsvaBoolean Virtual Attribute of the $Request object, but it would not fire a Change Workflow which is triggered by setting edsvaBoolean  to TRUE.

This is expected Active Roles functionality.

Instead of modifying the in-process request by updating the $Request object, instead, modify the $DirObj instead.

This will spawn a new $Request which is related to that specific update, and any Change Workflows or scripted customizations that are listening for those triggering conditions will fire as expected.

For example:

function updateBoolean($Request)
{
    $DirObj.Put($edsvaBoolean, $TRUE)
    $DirObj.SetInfo()
}