-
Notifications
You must be signed in to change notification settings - Fork 686
Two step processing for E-Documents on sales side #29070
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@Groenbech96, could you take a look? |
|
@miljance sounds like a clearance model scenario? Is it some manual check that is done outside BC ? |
No clearance outside BC. Just a manual check prior to sending it to the government portal. But if you are planning the clearance model with manual clearance in the BC that could also do the trick. |
|
Ok. We just add some changes to the workflow bit and should be synced here #29098 Can you take a look at those and see how they make sense with your changes? :D |
fed9d31 to
35b4b1f
Compare
|
I have synced the changes with the new clearance model. As the clearance model provided all the needed functions, the change can be done much easier.
@Groenbech96 Can you check if the new changes fit? Please evaluate the naming of the workflow step. |
Can you use the new response E-Document exported using X? We added that with support for clearance model? |
Do the new workflow step to export e-document |
Hi @Groenbech96 - I can add another Workflow response but, in this case, it will do the same thing as for clearance model. So, if I create a new workflow response, do you expect it to do something else compared to clearance model? I mean the clearance model does exactly what I need - postpones the sending until resent manually. I am wondering, what is trigger for clearance model to actually send the document afterwards? I also wondering if you see the changes I have made in regard to E-Document Status? The new Status called "Exported" might affect the clearance model as well. My question, the clearance model exports the document first - and then - what is the trigger for actually sending the document? |
|
@JesperSchulz Can the PR and the Issue be moved to BCApps as the E-Docs module has been moved to BCApps? |
I'm afraid I can only move issues. The PR will have to get recreated. |
|
Could not find linked issues in the pull request description. Please make sure the pull request description contains a line that contains 'Fixes #' followed by the issue number being fixed. Use that pattern for every issue you want to link. |
|
@JesperSchulz Thanks, I will create another PR over there. |


Description
Sending an e-document using E-Documents module in sales means that as soon as a sales document is posted it will be sent to the service provider. This is fine in most of the cases. However, the cancelling process in some countries might be cumbersome. Therefore, it is desired that an E-document is sent out to the service provider only after it is assured that the invoice being sent is correct. With a new Workflow response, it is possible to create an E-Document during posting of a sales document without sending the document to the customer. If the posted invoice is ok - the action "Send Document" on E-Document card can be called manually.
Summary
Work Item(s)
Fixes microsoft/BCApps#5004
Fixes AB#580686