Hi,
Is it possible to call a dashboard (system or custom) from a BPM with custom code?
For example, If one of our users starts a job that has not had materials issued, then load issue Material dashboard.
Thanks in advance
-Ben
With a BPM data form you would but it sounds like a terrible idea.
Hi @josecgomez,
Thanks for your quick response.
Normally our materials are issued on job completion, back flushed automatically. However, we have a few parts that are serial tracked which need to be manually free issued. This is where our issue is as they keep forgetting to do it.
How would you do it through a BPM data form?
could you suggest a better way of achieving this?
Thanks again,
-Ben
You could do a preupdate BPM to check if required materials have been issued for the production reported and then Invoke BO for the material issue. Use Tracing to check the BO and method required.
Vinay Kamboj
Yeah, I have that part sorted. But using a BPM data form I would need to make the form dynamic. In some cases there may be 1 serial number, in others there may be 3 serial number to be entered. This is why I though maybe calling the issue material dashboard would help.
Is there a way of dynamically adding fields to a BPM data form? This would be the best way of doing it I think.
I believe you could launch the form using custom code in BPM. Someone here can give appropriate code to launch a form by passing appropriate launch form options if required.
Vinay Kamboj
You need to remember that Epicor ERP is a Smart Client Service Oriented Architecture application. As such, there is no way that code run on the Server can directly impact the Client and as BPM is executed on the Server, it cannot launch client forms.
As @josecgomez says, it is possible to run a Customization on a BPM Data Form and for that customization to launch another form. Also as Jose says - it is a Terrible idea. Moreover, it is a Terrible, Terrible idea.
BPM Data Forms are managed by the Client Framework as an intercept on the message returning to the client after an application call to the Server. Once the BPM Data Form is dismissed - Okay or Cancel - the original call made by the client is made again with all the original data intact and only the BPMData fields modified by the BPM Data Form. Bringing another UI with additional Server calls into this magical framework message management is a recipe for all sorts of problems.
Customization was added to the BPM Data Forms so that the form could be visually customized. Since customization is available it is possible to do some conditional prompting as long as the data driving the conditions and the prompt answers are passed via the BPMData fields.
3 Likes
Sounds like you can achieve that lookup on the UI by calling a few adapters or a BAQ on the Form itself.
Aside:
I had a case where I had to call a custom Form on Packout based on a set of very complex BPMs in E9 - basically PCID before PCID came to Epicor Base, I used FileWatcher… Still works, but I am sure you can use some better polling stuff in E10.
The BPM did:
It was writing to EpicorData\custom\ and the Customization monitored that folder for “trigger-myusername”. Sounds like SignalR