I opened up End Activity in App Studio and was surprised to see an Actions section.
Does anyone know what this is and what module uses it?
I opened up End Activity in App Studio and was surprised to see an Actions section.
Does anyone know what this is and what module uses it?
Alright you pulled me into your rabbit hole.
Since it doesn’t (for me anyway) appear when I’m in MES… but is visible in App Studio, that means something is hiding it.
So, I searched for “Action” in the Data Rules and see it is being hidden based on Licensed Modules and “RecipeAuthoring”:
Still didn’t know what that was, so…
I’m assuming if you have Automation Studio, you can build a workflow (“Recipe”) and then your employees can check off tasks/actions they completed when they’re ending their labor activity.
… my best guess anyway.
My plan worked!!
I was actually thinking it was tied to the Recipe Module. The Recipe module has nothing to do with Automation Studio, it is an actual Epicor module. Basically, you can provide more detailed information in an operation. So you can actually add a “recipe” for mixing paints, chemicals, etc in one operation that will tell the operator exactly what they need to do the operation.
Interesting. If they already have “recipe” mean one thing… why couldn’t they pick a different term for Automation?
This is as clear as calling your sales rep a “Work Force”.
That’s what they do… (Kinetic… then rename to product to kinetic, Docstar to ECM, of which the previously had a product called ECM…)
Work Force is someone who can complete a Task. Task Sets started in the Sales area (CRM and Case Management) but then got added to ECO changes, and Time/Expense approvals. A Work Force person might not be an internal employee too, like an external auditor.
Their Automation Studio is powered by Workato, which already used the term “recipe”. The opposite could be asked to why Epicor didn’t rename their “recipe” that John referenced, but sometimes the name just works for its description I guess.
But then they used workforce values in a drop down from on the customer screen and labelled it Sales Person and tied the workforce items to Sales Terrritory and the same time tying the workforce the personcontact table… and tied that too the customer contact, and then decided that one employee record was not enough and put employee entry in two places…! It’s steaming pile at times. I get it in some instances perhaps you may have a requirement to have information in two places because of licensing…
Ever tried trying to work out why someone could not put enter in a case in case management, only to discover hours later you forgot to add them to the territory!
Honestly, I really don’t care what they name things. We’ll adopt and adapt.
THIS is what drives me nuts. How much effort would it have taken to put some kind of description on the LaborDtlAction table?
But, I suppose I shouldn’t complain because I’ve built myself a "glass house. I’m fully aware that whoever takes over my position someday will say the same thing about my customizations, UD columns, BAQs, Kinetic Layers, etc.
I can already hear them… “Would’ve been nice if that would have left some kind of useful description!”
100% agree paying if forward starts at home. Get your documentation in order folks. If the vendor doesn’t do it well we need to press them to. @timshuwy this is one of the BIGGEST pain that “We” have had to endure for many years, this issue is not new. The name might be meaningful the person doing the development at the time, but we all know how that goes.
If it’s a new field include the problem id, and a description that makes sense.
For us if it’s a custom field include a link or reference to the design doc etc.
Rant over… Sorry.
you are seeing something that was never finished, and will probably be deprecated in the future. We were building “recipes” functionality that would be used for some specialized process manufacturing that would have “actions” to be taken when completing an operation. Note that these “recipes” are different than Automation Studio recipes (something that came along just after we started developing these in Kinetic).
So, while it is something that you can SEE, it was never activated inside of Kinetic.
It is intriguing though and I think there is definitely a great case for this where you want to capture some other actions that revolve around an operation.
Tim, I think there is a place for not using the same term for two different things. It just leads to confusion… But I’m guessing the horse has already bolted there…
Perhaps next time
I wouldn’t worry about it too much, it sounds like its destined for the bin before it ever made it into use.