![]() ![]() I want to tell them “if it’s almost out, or out, just push the button. Also I don’t want to scare people from pushing the button thinking that they are going to order too many. Obviously, I don’t want 50 orders a day of these labels if they are out and everyone pushes the button. (like display on a dashboard, or even get to the point where there is a standing PO and automatically orders the stuff) That will write a row to a UD table in E-10 where I can do stuff with it. I want to put a button the bin with the labels that someone can push when they are almost out. ![]() The shop floor runs out of labels all of the time because no one will take the time to tell the purchaser that we are almost out. What’s the best way to do this? And what’s the easiest? (Because I’m sure they are not the same) Now that I got that working, I will need to inject some logic for filtering somewhere. (click on the picture to expand it, it’s taller than it shows in the preview) I’m not understanding the terminology of the header key and string, so I’m not sure how to translate the example that is in help. Here’s a screen shot of the input screen. Maybe Jitterbit will be a good option in the future? I want the shop floor to not be afraid to push the button when they need it, so I have to find a way to filter out false positives, which I could do with a BPM. I might use some other tools like zapier, to do something independent of epicor, but I really like the tools that I have in BPM conditions to be able to filter out things like the same button getting pressed every 10 minutes for 2 days. I know that I don’t know enough about security, but I am trying to learn. Maybe it’s not possible to set up what I want in a UI type environment. The use case is, the shop has a bucket of safety labels, when the bucket gets low, they can push this button to signal the purchaser to order more, or even maybe down the road bypass the purchaser altogether and just order them from the supplier. What I am hoping to do is configure a task for each button to make a row in a UD table so I can do something with it in E-10. It’s using their app to make a internet request. Well it’s not really writing an app (that’s way above my skill level). I’ll be interested to see what you come up with! That means some folks have had to add a different user for each company. With no header for Company, the users ‘CurComp’ (last logged in company) is used to set context. Not applicable to your button POC but something folks using tools like Microsoft Flow have to struggle thru. ![]() This means you may need a different identity per company. There are tools where you cannot pass custom headers such as the Epicor CallSettings header where you set the company. NOTE: Company setting is an interesting (frustrating) topic for many. You probably will be hard coding that for this in production since it will be hard to change companies on a button press (Press once for Company 1, press twice for company b? Probably not). *Set Context - Which company / plant / other Session variable do you want to have the server call execute under? You can easily pass the company in the header. Bonus points for adding a BPM to write out the tip number and the userid to a UD table or append to the tip text to play around and learn what is happening. Try something simple like adding a Tip record from Postman to see how things get updated. In that case, create a test user and brag the ‘basic auth’ line for it from PostMan for your test user. You COULD just hardcode a ‘ButtonAgent’ user in E10 for a POC but hopefully we can progress beyond that for production level. pass credentials to authenticate the ‘button’.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |