Iām pretty sure that Collaborate plays well with Slack and Teams - maybe with an extra license .
This is a two-way street. I want to reduce context switching. I donāt want to be in Teams or Outlook and have to switch to Kinetic either. If I already have a collaboration tool, I donāt want to add another one. This was the deal-breaker for Epicor Social IMHO which I shared freelyā¦and all too often.
Teams is what they showed. There wasnāt anything else that they mentioned. Iām assuming since they are a microsoft partner they are sticking with them. And I get not needing to be actually in Epicor to get a message. Iām sure you could do some stuff with Workato to whatever program you wanted, but they said with the Teams plugin, it was 2 way, so when you made a reply in Teams, is showed in the appropriate thread in collaborate. (Not that I was able to test it, but I did ask the question). I think a home grown connection would be a lot of work to get the same functionality.
There were not any huge Epicor ideas that were closed, but many small ones, especially in the UX Improvements category. We presented our completed items for 2022.2, and 2023.1 which had lightbulbs showing the items that came out of Epicor Ideas. We have recently ramped up our use of Epicor Ideas again, so that in the 2023.2 release, there will be way over 1000 votes closed due to the ideas.
There are 341 ideas closed for UX optimization in 2023.1ā¦ thank you all for your suggestions! Other items included USB Scale interface, Co-Parts as a first class citizen, Lot trace views, Automated Fulfillment, visual Procure to pay interfaceā¦
in 2022.1, we completed eSignatures, MTO in Fulfillment WOrkbench, Rev based inventory & Planning by revision, PCID for WIP.
@Mark_Wonsil@Banderson Context switching is a problem - absolutely. Second or third collaboration tool - also a problem. My idea is categorization of data - in our case itās pretty cut and dry. For others it may be too indistinct to be useful or clear enough for people to work with.
As for Teams, I donāt think itās for us. We donāt really use Teams for āteamsā and we use it sporadically now for anything other than meetings, I think the re-focus to Collaborate might work well for us for customer-oriented data and internal conversations. But thatās us, not everyone.
If you have your customers and/or partners linked up in Teams groups, and they participate in these conversations, then I think itās a great idea.
They are working on more, but I am limited on saying anything else without asking and it would be littered with liberal @timshuwy , oops I mean safe harbor - forward looking statements
Sample of some of the slides from one of my Sessions (which are apparently of little value - tough crowd).
These are images of the Portal in itās current form and it will be somewhat different in the general release. For example, Start/Stop will likely go away replaced with Restart.
Restart - Yes
Copy Prod to Pilot / Other - yes (and you can pick from any Backup - Prod or Pilot - as the source DB).
Upload Electronic Interface programs - on the roadmap
Perform a Backup - no. Refresh DB option allows selection of all Backups made in last 30 days.
Any chance of that leaking into on-prem? Iām sure you will have some nice automation built into that where, while we may not need it could be helpful/useful.
The new cloud SDK was sweet I am excited about that because it means there is a slim chance one day we may be able to go SaaS.
But regardless the new cloud friendly features of the SDK are . I like the idea of a Basic CRUD service and everything else driving by functions and bpm.
And yes those are available for on-prem too, if you have the SDK you can now add tables, relationships and spin up a fully working CRUD service including SWAGER docs with no code and that is hot stuff!
You buried the lead! AKS instead of manual installations!!! That means on-prem users could use those images with Azure Arc as well! This is a great direction @Rich.
Ok, I will pile on this topic, would be nice to copy all forms from live to pilot which sit outside the database. Seams like the next logical step with the portal.
I have to admit. I was saying AKS but thinking ACI. Yes, AKS is not easy to set up but easier than rolling your own clusterā¦(second word left off to keep it PG13).
If you type Epicor in the GIF search, these are the only two that return.
I was hoping for something funnier to give you an image @Mark_Wonsil , but the second one is definitely weird. I wonder if @hmwillett made it with DALL-E
.
. I like the idea of a Basic CRUD service and everything else driving by functions and bpm.
