Skip to content

Conversation

@Pascal-Delange
Copy link
Contributor

@Pascal-Delange Pascal-Delange commented Nov 19, 2025

  • add "case_ai_review" to the license claims (and add it to organization_feature_access to pre-org disabling in our SaaS)
  • check on activation of this claim to actually do ai case review
  • introduce inbox setting to trigger case review on case creation / case escalation / manual request, and implement the corresponding workflows (not using a generic workflow concept for this for now).

Some other minor comments: see inline comments below.

@linear
Copy link

linear bot commented Nov 19, 2025

@Pascal-Delange Pascal-Delange force-pushed the pascal/mar-1297-implement-the-backend-workflows-for-case-events-that-trigger-2 branch from f4251f7 to 7fbaf1a Compare November 19, 2025 21:07
}

suite.blobRepo.On("GetBlob", suite.ctx, "test-bucket-url", aiCaseReview.FileTempReference).
suite.blobRepo.On("GetBlob", mock.Anything, "test-bucket-url", aiCaseReview.FileTempReference).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rationale behind this change and below: equality check on the context was breaking if I add tags on the logger and re-inject it into the context. The compiler won't let us pass something else than a context anyway so no need to test this specifically.

}
if hasAiCaseReviewEnabled {
aiCaseReview := models.NewAiCaseReview(caseId, d.caseManagerBucketUrl)
err = d.repository.CreateCaseReviewFile(ctx, tx, aiCaseReview)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NB: I did a small refactor here. The case review file is now created within the worker - there was no strong reason for needing to create it before, and this way it's not repeated in every place we need to trigger the workflow. We still generate the id of it in advance (so that the worker execution remains idempotent).

@Pascal-Delange Pascal-Delange force-pushed the pascal/mar-1297-implement-the-backend-workflows-for-case-events-that-trigger-2 branch from 04ee5e3 to 4d06625 Compare November 21, 2025 21:11
if !l.CaseAutoAssign {
o.CaseAutoAssign = Restricted
}
if !l.CaseAiAssist {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be commented to actually test the change in local dev mode (staging should be fine), until the prod release is deployed (license server updated).

@Pascal-Delange Pascal-Delange marked this pull request as ready for review November 21, 2025 21:51
@Pascal-Delange
Copy link
Contributor Author

@OrriMandarin can be re-read

@Pascal-Delange Pascal-Delange force-pushed the pascal/mar-1297-implement-the-backend-workflows-for-case-events-that-trigger-2 branch from d42a33b to 41dea19 Compare November 30, 2025 20:44
@Pascal-Delange Pascal-Delange force-pushed the pascal/mar-1297-implement-the-backend-workflows-for-case-events-that-trigger-2 branch from f9fc171 to df73fa9 Compare December 1, 2025 16:37
@Pascal-Delange Pascal-Delange force-pushed the pascal/mar-1297-implement-the-backend-workflows-for-case-events-that-trigger-2 branch from df73fa9 to 8c333a5 Compare December 1, 2025 16:41
@Pascal-Delange Pascal-Delange enabled auto-merge (rebase) December 1, 2025 16:41
@Pascal-Delange Pascal-Delange merged commit d514b0d into main Dec 1, 2025
6 checks passed
@Pascal-Delange Pascal-Delange deleted the pascal/mar-1297-implement-the-backend-workflows-for-case-events-that-trigger-2 branch December 1, 2025 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants