Ability to store comments against BPMs

(Simon Hall) #1

Working in an environment where there are many different teams adding BPMs it would be nice to be able to have comments. I think dashboards already have something.

I had thought of just adding a custom code step to the BPM and using that for comments. I guess this links into the source control topic that Mark raised.

(Mark Wonsil) #2

And BAQs and Security groups and…

(Pierre Hogue) #3

And when we search for baq, having the Last modified date ( as available with dashboard search) would ease the search…

(Mark Wonsil) #4

Of course, a source control system responds to the needs of this enhancement and more.

(Pierre Hogue) #5

Just the way the Dashboard behaves, poping up a textbox where we put relative info , would do the job!

(Haso Keric) #6

BPM Nodes have Comments and so do BAQ Nodes, but not the BPM or BAQ itself.

(Mark Wonsil) #7

I was speaking to the Last Modified, and the Modified before that, and by whom, and what exactly changed so that it can be compared to a fresh version when moving to new versions…but a comment field would be nice.

(Pierre Hogue) #8

Sorry I said comment field but the way the dashboards “comment field” acts is when we save, it pop up a text box where you can write any relevant text you want, and saves it with the current version.
We are using it with the following structure : Version , Id of the workorder (we use an internal helpdesk for any change requests) and what was done. It saves by tagging the user and date/time.

Thats all we need for some follow up nothing complex…it is not perfect but does the job…

But will never say no to a revision control system !!! of course.


(Andris Skulte) #9

YES!!! Expand the comments to every single setup UI form too. Often I want to know why we do what we do, and it’s long ago history, and nobody knows anymore… Storing it in Epicor with the corresponding screen makes a lot more sense then tracking it outside the system.

(Simon Hall) #10

Not perfect but you can annotate the help for forms, but that starts to move into relm of end user procedure, which you could argue that is what EKM is for.

@hasokeric I must have been living under a rock on the node comments mention.

As Joshua Bardwell says. “Your gunna learn something today” and I did. Thanks. :grin: