IDEAS - Don't Lock Out Epicor During BPM and BAQ Development

I just submitted this Idea - would it be useful?

When the Designer is active in Method Directives Entry or Data Directives Entry, or the Calculated Field Editor in BAQs, Epicor locks the user out of the rest of the client. There are probably other instances I haven’t mentioned as well.

When creating customizations, developers need to see what fields are used, perform tests, and see different apps. When Epicor locks the user out of the app, the user then needs to note where they left off, save and close the Designer, use the app, and then re-open the designer and get back to their coding.

This wastes time and slows down the customization process.

Please make Epicor more developer-friendly.

1 Like