# Epicor BPM & Functions Design Feedback **URL:** \ **Category:** Kinetic ERP\ **Created:** [July 28, 2021, 5:14pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023 "2021-07-28T17:14:33Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![Hogardy](https://www.epiusers.help/user_avatar/www.epiusers.help/hogardy/32/18785_2.png) [@Hogardy](https://www.epiusers.help/u/Hogardy)\ **Post date:** [August 3, 2021, 12:08pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/21 "2021-08-03T12:08:21Z")
> [@askulte](#): > > Add a date created and date modified field so I can search by the latest one. Likely that I’ll be modifying one of those, rather than one I created 5 years ago. That would certainly improve the searching ! Not perfect but at least with the Dashboards, I can sort by date and find the latest one I worked on to continue working on it the next day! For Menu maintenance, the ability to change all same menu at once ! or at least select the ones to have the new custo! Everytuime I change Part maintenance, it is a pain … 14 menu searches to modify by hand… 🙄 ---
**Author:** ![Mark\_Wonsil](https://www.epiusers.help/user_avatar/www.epiusers.help/mark_wonsil/32/51594_2.png) [@Mark\_Wonsil](https://www.epiusers.help/u/Mark_Wonsil)\ **Post date:** [August 3, 2021, 12:14pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/22 "2021-08-03T12:14:06Z")
> [@askulte](#): > > For import, give the option to overwrite (instead of making a 2nd copy where it isn’t clear which one is the new one). Having a date created field would help. Again, I prefer the Git hash since it is a positive ID to the exact code imported where a date (well, date time since you may very well import the same file twice in a day) might not always align with the date in the import file. ---
**Author:** ![Callum\_Stott](https://www.epiusers.help/user_avatar/www.epiusers.help/callum_stott/32/36368_2.png) [@Callum\_Stott](https://www.epiusers.help/u/Callum_Stott)\ **Post date:** [August 3, 2021, 1:15pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/23 "2021-08-03T13:15:24Z")
Adding a date created would help for less specific/more general searches and queries but I completely agree that a hash or similar is always required for the actual version IDs. ---
**Author:** ![Hogardy](https://www.epiusers.help/user_avatar/www.epiusers.help/hogardy/32/18785_2.png) [@Hogardy](https://www.epiusers.help/u/Hogardy)\ **Post date:** [August 3, 2021, 5:28pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/24 "2021-08-03T17:28:05Z")
The ability to use a specific calendar ID to find the next (or previous) X business days. (I wander why it is not implemented yet in Epicor! ?)Just playing with week ends is not enough… We should be able to easily find the next business day including holidays… Currently we all using our own version of special code to do that… would be nice to have it part of Epicor list of functions… ---
**Author:** ![timshuwy](https://www.epiusers.help/user_avatar/www.epiusers.help/timshuwy/32/90122_2.png) [@timshuwy](https://www.epiusers.help/u/timshuwy)\ **Post date:** [August 4, 2021, 11:58pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/25 "2021-08-04T23:58:41Z")
> The ability to use a specific calendar ID to find the next (or previous) X business days. (I wander why it is not implemented yet in Epicor!) That is simply a “Standard Function” that could/should be developed and be available for people to use. YOu are right, many of us have developed similar tools because this is lacking. I have one that I have talked about for years that needs to be converted to an Epicor Function… it was very fast but did “too much” for a basic function. Maybe someday I will have a few hours free to create a function. In my version, you could provide a calendar ID, and then the number of days after (positive number) or days before (Negative number) and it returned the working date for that date using the Calendar as the basis for calculation. it had all sorts of additional rules like “What if “today” is a holiday or weekend”, etc… ---
**Author:** ![fuji36](https://www.epiusers.help/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@fuji36](https://www.epiusers.help/u/fuji36)\ **Post date:** [August 5, 2021, 11:24am UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/26 "2021-08-05T11:24:23Z")
Though not ‘functions related’, I agree- update the customization ‘active form’ in All menu locations would be great. ---
**Author:** ![fuji36](https://www.epiusers.help/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@fuji36](https://www.epiusers.help/u/fuji36)\ **Post date:** [August 5, 2021, 11:27am UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/27 "2021-08-05T11:27:09Z")
I agree, there had got to be a way for customers to maintain their holiday schedule. ---
**Author:** ![josecgomez](https://www.epiusers.help/user_avatar/www.epiusers.help/josecgomez/32/55731_2.png) [@josecgomez](https://www.epiusers.help/u/josecgomez)\ **Post date:** [August 5, 2021, 12:47pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/28 "2021-08-05T12:47:37Z")
4 posts were split to a new topic: [How to call a function in code from a BPM](https://www.epiusers.help/t/how-to-call-a-function-in-code-from-a-bpm/81292) ---
**Author:** ![Hogardy](https://www.epiusers.help/user_avatar/www.epiusers.help/hogardy/32/18785_2.png) [@Hogardy](https://www.epiusers.help/u/Hogardy)\ **Post date:** [August 5, 2021, 12:20pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/29 "2021-08-05T12:20:17Z")
In BPM, using the AutoPrint widget (which I discovered recently !) you can setup to use email. Well, it would be much appreciated if we could have the same email interface as the email widget where we can add variables from the context menus so it can be better configured !! Pierre ---
**Author:** ![JasonMcD](https://www.epiusers.help/user_avatar/www.epiusers.help/jasonmcd/32/22326_2.png) [@JasonMcD](https://www.epiusers.help/u/JasonMcD)\ **Post date:** [August 5, 2021, 1:30pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/30 "2021-08-05T13:30:43Z")
> [@fuji36](#): > > to maintain their holiday schedule You mean like across multiple calendars? Maybe that’s not what you mean, but it’s something I think of. I make liberal use of calendars (one for production, one for suppliers, three for cycle counts, one for sales). But our holidays are the same company-wide. It would be nice to have the option to layer the calendars, IMHO. ---
**Author:** ![fuji36](https://www.epiusers.help/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@fuji36](https://www.epiusers.help/u/fuji36)\ **Post date:** [August 5, 2021, 2:04pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/31 "2021-08-05T14:04:31Z")
Yes- I haven’t personally done much with ‘calendars’ but that sounds like the correct place to have the data required associated to. ---
**Author:** ![klincecum](https://www.epiusers.help/user_avatar/www.epiusers.help/klincecum/32/100137_2.png) [@klincecum](https://www.epiusers.help/u/klincecum)\ **Post date:** [August 5, 2021, 2:25pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/33 "2021-08-05T14:25:11Z")
> [@J\_I](#): > > Perhaps include the ability to have a data structure (I.e. an Array or List) as an out-of-the-box variable type. > > When parsing multiple things it’s a pain to store details in a delimited string and then have to parse them into what I want afterwards. > > (If this isn’t a thing already!) That’s a perfect use case for json. Epicor has libraries available in the assemblies to handle that. ---
**Author:** ![KevinK](https://www.epiusers.help/letter_avatar_proxy/v4/letter/k/e9a140/32.png) [@KevinK](https://www.epiusers.help/u/KevinK)\ **Post date:** [August 5, 2021, 2:26pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/34 "2021-08-05T14:26:24Z")
> [@jimship](#): > > I’m a beginner to BPM’s but one thing I find missing is the ability to comment and add notes to a BPM. I’ve worked around the absence of a dedicated “notes” widget by adding an unconnected code widget containing only a block comment. ---
**Author:** ![KevinK](https://www.epiusers.help/letter_avatar_proxy/v4/letter/k/e9a140/32.png) [@KevinK](https://www.epiusers.help/u/KevinK)\ **Post date:** [August 5, 2021, 2:49pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/35 "2021-08-05T14:49:29Z")
Not exactly BPM or Functions, but I recently joined a company using Kinetic and sorely miss the ability to run ad hoc queries to answer business questions or develop SSRS reports. We can write BAQs or upload RDLs, but it would shorten the change/test cycle if there were a facility for running SQL directly. ---
**Author:** ![J\_I](https://www.epiusers.help/letter_avatar_proxy/v4/letter/j/c37758/32.png) [@J\_I](https://www.epiusers.help/u/J_I)\ **Post date:** [August 5, 2021, 3:07pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/36 "2021-08-05T15:07:20Z")
Something like what Epic Games do with [comments in Unreal Engine blueprints](https://docs.unrealengine.com/4.26/Images/ProgrammingAndScripting/Blueprints/UserGuide/Comments/type_box_comment.webp) would work really well. ---
**Author:** ![askulte](https://www.epiusers.help/user_avatar/www.epiusers.help/askulte/32/7325_2.png) [@askulte](https://www.epiusers.help/u/askulte)\ **Post date:** [August 5, 2021, 7:31pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/37 "2021-08-05T19:31:11Z")
> [@timshuwy](#): > > I have one that I have talked about for years that needs to be converted to an Epicor Function… it was very fast but did “too much” for a basic function. Maybe someday I will have a few hours free to create a function. @timshuwy - Could you get Epicor to have you create this for the BPM Cookbook as a functions example? I’d love to have this!!! I would bet every Epicor customer would use this. ---
**Author:** ![josecgomez](https://www.epiusers.help/user_avatar/www.epiusers.help/josecgomez/32/55731_2.png) [@josecgomez](https://www.epiusers.help/u/josecgomez)\ **Post date:** [August 10, 2021, 2:57pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/38 "2021-08-10T14:57:54Z")
A post was split to a new topic: [Better Design for business objects](https://www.epiusers.help/t/better-design-for-business-objects/81468) ---
**Author:** ![josecgomez](https://www.epiusers.help/user_avatar/www.epiusers.help/josecgomez/32/55731_2.png) [@josecgomez](https://www.epiusers.help/u/josecgomez)\ **Post date:** [August 10, 2021, 2:56pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/39 "2021-08-10T14:56:13Z")
A post was split to a new topic: [Add Misc Charges to Cust Shipment](https://www.epiusers.help/t/add-misc-charges-to-cust-shipment/81467) ---
**Author:** ![mng](https://www.epiusers.help/user_avatar/www.epiusers.help/mng/32/39965_2.png) [@mng](https://www.epiusers.help/u/mng)\ **Post date:** [August 18, 2021, 2:59pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/40 "2021-08-18T14:59:17Z")
It would be nice to be able to see the using statements in a Function without having to demote it and click edit. Maybe as another tab right next to Overview, Signature, Notes? ---
**Author:** ![KevinK](https://www.epiusers.help/letter_avatar_proxy/v4/letter/k/e9a140/32.png) [@KevinK](https://www.epiusers.help/u/KevinK)\ **Post date:** [August 19, 2021, 6:35pm UTC](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023/41 "2021-08-19T18:35:25Z")
Since Epicor already drops the code you write into the body of a generated function in a generated class that you never see, it should be pretty simple to parse out any using statements you write inline and put them where they belong. [Previous page](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023.md?page=1) [Next page](https://www.epiusers.help/t/epicor-bpm-functions-design-feedback/81023.md?page=3)