On the commentary on the multi-auth mode login ui that’s presented in the web version in 2022.2. This was really a feature parity item we added it because previously the web made a choice and if you needed to use two methods there was no reasonable way to get to the second method in the browser vs. the client where you could do it. We recognize that not everyone wants every method that’s technically configured to be advertised so this feature comes with settings:
There’s an ICE.sysconfig setting (thought this is a direct db update) that can tell it to hide a particular mode from advertisement even if enabled. This may get a ui in the future, we built it mainly for our own saas hosting thus it’s placement only in the db.
We will be shipping a url format like login/?authmode=aad in a 22.2.x update release so that you can have a direct url to bypass the selection option for some users who are not going to understand it by giving them a direct link instead. This is actually a bug in that we intended to have this with the GA release, so that is upcoming as a bugfix though it’s more of an additional feature.
I would highly recommend keeping the product the same as much as possible between the cloud and on-prem.
I personally believe that greatest friction to cloud adoption is concern about what one might be losing in the move from on-prem.
Even understanding the history, multi-tenant’s extra codebase put the cloud product back years. Even well-respected Epicor employees were unsure at times what features were in the Public Cloud vs. MT because of the doubts dragged up by the Multi-Tenant architectural choices.
Most features, if not all, that are good for the cloud team will be good for on-prem customers. Why add complexity to the codebase that just leads to bugs and lower quality?
As you mentioned in the episode, let’s reach for feature parity. Today, we may not do things the same way in the cloud as on-prem from an admin POV, so let’s provide new methods that erases the difference.
The more the software works the same, the better shot Epicor has at converting companies to SaaS. There’s always a marketing moron at every tech company who thinks, “If we just add features to SaaS, then they’ll HAVE to come on-board.” Oh, they may move to SaaS, but it may not be your product.
I’m not trying to be anti-Social or unwilling to Collaborate, but boxing people into a SaaS product sometimes backfires.
I would highly recommend keeping the product the same as much as possible between the cloud and on-prem.
So i hope it’s clear that in this case this is not a saas only feature. The url method is what we’re intending most users to use and that’ll be out in an early 22.2 update. The ice.sysconfig based option can be applied on prem as well and is supported in that environment though it’s true that we didn’t provide UI for this configuration flag in the first pass.
Update: I neglected to actually share the key it is
ICE.Sysconfig:
Key1: ‘AdvertiseAuthentication’
Key2: ‘Basic’ //or SSO or AAD or…
SysCharacter01: true/false
Again though we think the url method is the better option for most cases and that’ll be out soon.
Hello @bconner,
Talking of things web, is it possible to confirm if Lite Kinetic MES was deprecated? Using the same URL in 2022.2 as 2021.1 yields a 404, I noted the /Apps/MES folder is not there anymore. I’m assuming this is because Data collection is now fully functional in Kinetic web?
Dont cloudify everything. Keep it Hybrid I think its an Epicor strength in competing with SAP, NetSuite, Dynamics, Sage. You know if some of the folks from Epicors 100% Club would actually visit their big customers, they would change the roadmap drastically.
Here is an idea… Epicor should go open source All Customers will say lets do this. Epicor claims to listen to the Customers. So Lets Go! Open Source is the future.
Kinetic Framework once was available on Stackblitz and npmjs, why was it taken away. Seems like we are going backwards here
I’m not sure you mean Single Tenant/EMS. Single Tenant architecture is same as on-prem. Sounds more like Multi-Tenant, or the first shot at cloudifying - Epicor Express.
That aside, I agree with you that hybrid is an important feature, and there will always be companies who need on-premise.
ROFL at the marketing moron bit.
You are correct - Data Collection was rebuilt in Application Studio and the hand-coded web application version is replaced by it so that it’s more standard and you can customize it which was the major limitation of the early version. EWA variants of screens are also on the way out for the same reason now that we have first class web versions in the new technology.
actually, it is not a big can of worms any more than planning by Part Attribute which is also a relatively new feature…
Think of planning by rev as though the PartNumber/REV was one field. the way that we did this is through the ATTRIBUTES feature that can be applied to a part. We have a Revision attribute and so it works just like Attribute planning.
One additional clarification… what we USED to call MES, is now called “Data Collection”. Reason is because it was never a full fledged MES module, and was mostly misnamed. In fact we now have a new MES module that Epicor purchased that is very robust, and will be integrated with Kinetic. The Data Collection module still exists, and is very functional in the new Browser based UI.
Ah, yes. This is like capabilities for materials then? That would make it easier than having to have to plan each and every revision that was interchangeable.
So how will a Job Pick list work? Do you have to select a version at Get Details time or at picking time?
In fact, we now have two MES modules that Epicor purchased that are very robust… MATTEC has a very slick integration with Jobs/MOMs, and eFlex seems to have an excellent data collection process along with a very good training module.