hi all,
In our company we have implemented a purchase-invoice workflow in Ax2012 R2 and it is working well. We are able to push the invoices from an inbox to OCR and afterwards get them imported into Ax2012 where they can be submitted to the workflow. We are really satisfied with the result... off course we need to finetune parts to maximize efficiency. (Our solution uses a 3rd party solution, not only Ax default functions and currently has only minor customizations for workflow related functions)
Currently we are reviewing the Ax behavior when a reject takes place, either someone rejects (approval) or there is an auto-reject by the system based upon certain criteria as defined in the workfow. Our business-need is that all rejected invoices are accesible for a group of users. (local accounting in each entity). Based upon our testing & Ax default behavior, in case of a reject, Ax pushes the workflow back to the workflow originator. In our situation this is not acceptable as our input-activities are out-sourced and at this point in time, we do not want them to handle the rejected invoices as resolving rejected invoices requires more business-know how and you might need to reach out to other colleagues or even suppliers.
What options do we have to faciliate our business-needs as we find the default Ax logic very limited at the moment? is it "smart" to have a customization to change the Ax behavior in case a "reject" takes place?
Looking forward to your feedback and experience on the topic,
kind regards,
Jo
Hi Jo,
I do suspect that you are using a workflow template from the ISV partner. You can see the workflow type on the workflow configuration form. When you lookup that workflow type in the AOT, you can find objects related to events which are the class names.
hi Ludwig,
Yes; Onfortunately i expect our company to stay on Ax2012 ... at least for the next two years. :(
But in my opinion this is for the best as we have, in certain modules, heavily customized it and we are not using Ax in the most efficient way and therefore missing out on logical default functions which increased the need for customization. I expect our company to be courageous enough to transform our way of working over the next two years and minimize the customizations and than upgrade to D365. My experience is that upgrading and trying to change the way of working (processes, change mgt etc...) usually is not the best combination. :) (at least not for our company)
Based upon your feedback and Andre's feedback i will review the possibility for a customization.
thank you both for your input,
kind regards,
Jo
hi Andre,
Yes; We are using an ISV solution and i checked with them first about the Ax logic currently in place. They confirmed me that they did not change the default logic. (So i expect that we are using "standard")
Nevertheless, you are correct that when it would come to a customization, our developpers need to doublecheck where to apply the changes.
In case we need apply the changes to the default classes, can you tell me which classes they are?
kind regards,
Jo
Hello Jo,
If you plan to stay on AX2012 R2 for the next couple of years then a customization might be justified in my opinion.
To me it seems actually the only way based on what you described.
However, if you plan to upgrade to D365FO in the near future, I would wait a bit with the fine tuning and suggest to have a look at the business events / workflow / Powerautomate functionalities and how they can be integrated with D365FO. You certainly have more options available there that might help you avoiding a customization.
Best regards,
Ludwig
Hi Jo,
Are you using standard AX 2012 features or an ISV solution for the invoice workflow? There is an workflow interaction class where you can indeed define what to do in case of a rejection. Which class you need to look at, depends on if you are using standard or not.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156