Trying to upgrade customizations and decided to not ignore the overlapping control warnings this go around but no matter what I do they won’t go away. So far 200.14 to 300.2 No BAQ errors, no BPM errors, and very minimal customization errors, just things like this that I force validated on 200. is there a trick to these location conflicts?
I am just really excited about EssentialObjects, because I can already visualize all the things I can make with it.
Epicor 10.2.300 Menu Maintenance let’s you select a URL Form now. This is going to be GREAT for anyone who has external web-apps, QlikSense, QlikView etc, or a full-width dashboard that creates gauges and charts from data retrieved via Epicor REST. The best part it runs EO which is a Chrome based web view, so you can make use of latest web technologies like WebGL, SVG…
Now if Stephen @Edge makes it happen as we use LaunchForm that we can pass in ?params then we can use it also as a pop-up to fetch more data,visuals for a given record.
You can Embed a webpage in the Active homepage and there are checkboxes to send the Context & Token to the website you are embedding, it’ll pass it in as various GET params ?token=… and then you can use that to call Epicor REST.
@jgiese.wci - Maybe increase the spacing between the label and Freight Charges combobox? I had to pop in a help ticket (Case CS0001143349) for similar issues on an 10.2.200.x, and requested an enhancement to reduce the padding and not warn for overlaps. Dan D. noted issues like this for enhancement in future releases…
The Problem Case Number is PRB0206232 and has the following Description:
SUGGESTED ENHANCEMENT #1: Improve Verify algorithm in Customization Maintenance to eliminate false “Visible Area” Location Warnings by ignoring padding and only looking at the control itself (i.e. label or text box) and not the handle squares around it.
That was my first guess, added 8px between them to start then 12px and still wasn’t resolving. At that point I determined I’m wasting more space than actually fixing anything LOL
Some Feature Highlights @Drozy2017 finds note-worthy; good share!:
Epicor Kinetic Framework
Contextual Video Help
Some forms now have an associated help video that will open in a browser, accessible via the Help menu
Enhanced PCID functionalities in Advanced Material Management
Company Configuration - Unapproved PO and Unconfirmed PO Settings
You can select to allow, warn or stop employees when they create receipts for unapproved/unconfirmed purchase orders
Supplier Price List – Part and Subcontract Operation file attachment support
Tracker Transaction History Range
Use the Number of Days field in Company Configuration to set the default number of days of history to retrieve when retrieving transactions in trackers
New Change Log for Supply Chain Programs and Trackers (27 of them!)
Posting Rules - Check Syntax Functionality
MES Menu Security Changes and additional reports
Job Entry now includes the RMA Line, RMA Number, DMR Number, DMR Action Number fields used to review if a job is tied to RMA or DMR records
DMR Processing – Return to Customer option can now automatically create a Miscellaneous Shipment Pack ID and DMR-SHP transaction type
Process MRP logging - new options for:
Append
Overwrite
Split - adds a date and time in the filename to create separate log files for each run
System Monitor Reports
The System Monitor sheets/tabs have been rearranged to get a more organized and more detailed display of report information
SQL Security Error Reporting with enhanced detail (what a concept!)
Menu Maintenance - Copy Security to Current Company (no not user security…)
Admin Console – FIPS 140-2 Encryption
Epicor ERP 10 now supports Federal Information Processing Standards (FIPS) 140-2 compliant encryption to meet the security requirements of the customers operating under the International Traffic in Arms Regulation (ITAR) Note: requires license file be purchased and installed before performing the upgrade
Advanced Print Routing
Workflow email routing now supports multiple email recipients
BAQ results now support Data Masking for fields with sensitive data to limit access
A bunch of random Financial crap that nobody really cares about
FIPS / ITAR - you do not need to purchase a new license but you do need to get a license re-issued. Turns out our license files themselves are not FIPS compliant so we had to modify them so they can work on a FIPS restricted system. Existing license will continue to work just fine if you are not FIPS.
Data Masking of Sensitive data - this actually applies everywhere and not just in BAQs. The data is masked / unmasked at the Server boundary so all processing and DB storage is done with the Actual value but it can be masked for viewing. This is essentially Column Level Security and in addition to the existing options of “Full / Read-Only / None” you can now specify that a column value is “Masked” - User will see existing data with a mask applied but can enter new values or change existing (of course they have to know the complete value of the field) and “Masked Read-Only”. This is a nice extension to security that allows you to decide what data is sensitive and who should be able to see it and change it. The masking only applies to “Text” data.
and @aidacra nice of you to worry about the Fin folks but the posting didn’t include a bunch of numbers or columnar data so they will never read it…