Conversation
0584e21 to
a3c5197
Compare
luisDIXMIT
left a comment
There was a problem hiding this comment.
I'm reporting an error due to being all thumbs. I tried to force the execution of an automation.record.step, and when I hit play, the following error popped up:
psycopg2.errors.NotNullViolation: null value in column "partner_id" of relation "sign_oca_request_signer" violates not-null constraint
DETAIL: Failing row contains (3, 3, null, 1, null, null, 1, 2, 2, null, null, null, null, null, 2025-07-24 07:52:55.405643, 2025-07-24 07:52:55.405643, null, null).
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
|
Merging this for not losing it, being a new module. /ocabot merge nobump |
|
What a great day to merge this nice PR. Let's do it! |
|
@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-22-by-pedrobaeza-bump-nobump. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
|
To be rebased and checked. |
This module would allow us to integrate sign_oca with automation.
IT will allow us to detect automatically if the document is signed (or not) to continue on with next steps
Depends on: