On Friday, it’s EpiUsers Frideas Day! Have you been to the Epicor Ideas Portal recently? If so, are there some ideas you want to encourage other users to vote for? Maybe want to add comments to an existing idea?
I would really appreciate any additional votes I can scrounge around on this. We’re planning to go live this year and this is turning out to be a major hurdle for us.
It’s so very easy to do, and a practically universal standard practice - look at the tab headers every other website opens in your browser. No photoshop shenanigans were applied below. It’s just the text at <head><title>this is your tab title<\title>…<\head>
Response lacks guidance and can overlap into plausibly adversarial. Without a real commitment to appropriate response, reporting security problems creates a security problem and exposes the reporter to a nonzero risk of getting Swarz’d by someone with zero guardrails having a bad day.
In this scenario, if I try to edit the Part Description, or ECCN code or anything on the Part table, I get this error:
Non Quantity Bearing is only allowed for Parts that have No-Stock
And thus I cannot edit fields on the Part table.
YES I KNOW THERE IS A WORKAROUND. Just make Part.QtyBearing = true. It does not hurt the sites.
But I just get annoyed working around issues like this.
Now I (in IT) am going to do that workaround on 91 parts, so that a user can enter info (in a uBAQ dashboard) for international shipments.
This kind of bleeds into my other idea about Part Entry. I mean not really, because this is BO-level, not UI-level. But just throwing it out there, that there are users that just want to make an accurate commercial invoice document and then hit an error like this and have to ask IT or Engineering or someone utterly unrelated, in order to work around some odd bug feature.
Example: If I try to update a Project with DMT, it says Description is required and will not let me proceed until I add it. Why?This is not a new record. I understand that new records need this. But not updates.
I hate this - forced to put columns in my DMT that I didn’t want to update.
Thanks, I voted on the “Safe Harbor” policy regarding vulnerability reporting.
Kind of silly that we haven’t had that in place to date, and already an example of something being exposed to the community for lack of a better place to responsibly disclose.
I may or may not be aware of birdies flying around that know things.
Edit: I checked the box that says “Only share this comment with employees” that I hadn’t seen before, i’m curious if anyone else can see that.
Been meaning to write a similar one for ability to set milestones to a SOrder release level. Presently it’s line level so we’re making extra order lines to get milestone prebills to wash on customer shipment of release.
If anyone has time, these are some of the ideas that @vleveris and I came up with. There are plenty more ideas and I am open to discussing how ECM could work with anyone who has interest.
