Difference between revisions of "SOP-42Q-MDS0083 Label Engine Labels"
Line 1: | Line 1: | ||
− | < | + | ''' ''' |
+ | <br/> <br/> <br/> <br/> <br/> | ||
+ | '''Production''' | ||
− | + | '''Label Engine Labels''' | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | ''' | + | '''Version MES15.75''' |
− | ''' | + | '''Revision H1''' |
+ | <br/> <br/> <br/> <br/> <br/> <br/> <br/> | ||
+ | '''Table of Contents''' | ||
+ | | ||
+ | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.f5kwnwq3ltif Label Engine Labels]''' | ||
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.75em3l9b1avr LE Labels]''' |
− | [ | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.cr7l7w76744c Label Template File]''' |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.rcz1tpxg2tsg Add New Label]''' |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.2qpunb90yhtf General Information Tab]''' |
− | [ | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.vjwzk6vzbmrw Default Database Mapping]''' |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.1p7ba6qdejzx Part Number Mapping]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.9m52ono3xjc2 Upload Files Tab]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.6u33thpd757m Add File]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.axh6ulcib7p2 Edit File]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.x8fikssr714w Delete File]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.hzq6vo5xnixe Download File]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.7jzcxena9nyl View Label Sample]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.3a1halx57xtf Element Creation Tab]''' | |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.3vbrov2dftkn Add Element]''' |
− | [ | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.s2ik821n1840 Constant Value]''' |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.uhs9tzgl18vo Date/Time]''' |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.nc0gjlbgteou Database]''' | |
− | |||
− | |||
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.5h1oqy713eo5 Custom Function]''' | |
− | '''Value | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.w07lmakdryfs Entry Value Block]''' |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.2d1ms93o451l Delete Entry Value]''' | |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.as0h7idsjjav Edit Element]''' |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.67vcm32pmty8 Delete Element]''' |
− | [ | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.babf3migdmzc View Element]''' |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.7jyc3la05lv8 Label Printing]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.bsvcerce2reg New Version]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.9xg9sesfca23 Edit Label]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.adwp67ekhhnk View Label]''' | |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.7uzhheg1n9jb Add/Remove PN]''' |
− | [ | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.fik4rio95x4c Copy Label]''' |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.ul4n068v227k Delete Label]''' |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.qjz1lkgrvzsz Hide/Unhide Label]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.8onte31zixfn Publish Label]''' | |
− | |||
− | |||
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.pnwblwaj31bx View Label Sample]''' |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.9pkpa43g2e5m LE Reports]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.55l0ku6yb7qi LE Version History]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.yy5f9q5ahx7c LE Print History]''' | |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.ixl9hyjw7rim LE Statistics]''' |
− | [ | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.mkg2xhb1791z Appendix A – Key Terms]''' |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.lsxiwg13lswj Appendix B – File Types]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.3vi06n9i0qyk Appendix C – Business Rules]''' | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.hy18wuabiwlz Appendix D – Examples]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.ezt2bzuy5xmv How to create a block/element for containers]''' | |
− | ''' | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.5pceoi9cgztf Parallel Containers - Values Other than Just Serial Numbers]''' |
− | [ | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.hr9uou83t3mp Naming Template Fields]''' |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.gf4kbdod89h Container Element & Block Formulation]''' | |
− | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.7wfaafvtte16 Container Element Mapping]''' | |
− | = | + | '''[https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.ffk0qiq1o3nd Document Revision History]''' |
+ | <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> | ||
+ | # | ||
+ | = '''Introduction''' = | ||
− | + | | |
+ | '''Label Engine Labels is a web application that gives plants the ability to create, update, and print labels without the need for IT resources. It enables plants to easily define and access various different data sources like MES, and MESR, along with a variety of other database types. It allows users to map label fields to these data sources in order to create dynamic labels. It also enables plants to extract statistical information about the labels that are managed in Label Engine, as well as monitor the audit information.''' | ||
+ | | ||
+ | '''Users can create a label template or layout in the design tool (i.e.: For ZPL use BarOne or CodeSoft, and for RTF use Microsoft Office or another tool that provides RTF format.) of their choice. Using the design tool, they export the completed template as ZPL (Zebra Printer Language) or RTF (Rich Text Format). The template is uploaded to Label Engine and the fields in the template are mapped to data sources. At print time, Label Engine combines the template with the appropriate data to produce finished labels.''' | ||
+ | | ||
+ | '''The Label Engine Labels portlet allows the user to create, edit, copy, delete, and print labels. LE Admin History, LE Version History, and LE Print History reports can be viewed and/or printed from this page. LE Statistics Excel spreadsheets can also be created from the LE Labels page.''' | ||
+ | <br/> | ||
+ | '''To access the LE Labels application, navigate to Production > Label Engine Labels.''' | ||
+ | | ||
+ | '''Figure 1: Accessing Label Engine Labels ''' | ||
− | ''' | + | '''https://lh3.googleusercontent.com/gnnR7jMh_oi1LR4kaIR_gWgoRbswzX0MdEB6SZpC2Iga4Bo4uyBGNe5gmBIeM3kEFrUAV0Ojm34fScVGzLf8VzQBtel_1ObEY6h63R0sYI1-SHujq8looVf_xQuNeZ0gP7GB_-ZUxH2EPpnhY2SL3jvZi1abdV62lWSsDxXQAi3B5jcu2-Asce1-kQ''' |
+ | <br/> <br/> | ||
+ | '''Within the main screen of Label Engine View, the user will be able to see four different modules: ''' | ||
− | + | '''LE Labels, LE Version History, LE Print History, and LE Statistics.''' | |
− | + | # | |
+ | == '''LE Labels https://lh6.googleusercontent.com/9WcVP8b1Gf9Pf0xreH8VkQpUw4aExuYZVXOigUo9trICy7XB1L036Y1xe3M0CAH6S15uUcL09DMXwREmPqG5jC-8sHiQRX5PiGyG82Lp9P7MrRdSeQaFTo34CwCRibwaVdrCeKtkZD1GP5e-2Ds7BnKmuRGpwaQUoOx_sDjovQXUROhjpMg-JPT7lQ''' == | ||
− | | + | <br/> |
+ | '''To access the LE Labels, select the LE Labels from the Label Engine View menu.''' | ||
+ | | ||
+ | '''Figure 2: Label Engine Labels Main Page''' | ||
− | + | '''https://lh5.googleusercontent.com/Zft0Df4I9YELvigGiY6-ov0_F1QjxF9xxz-sD8ftTVmmhdbKLxgOWKYrFQ0AvZkPMMYcwwkwphalwZPNCwtJb7z9ACmLMRSb-t5PLTnMOMpSYfpiAGjN-yMTHBc1-TTPRH4nKroPhSUZ3wsyhG1GcnYbuSaMZl6tQJuqEefiIuw_dSLokwFRXpeRoUWd8BL9Jg''' | |
+ | | ||
+ | '''The main screen of the LE Labels page contains all previously created labels. The labels are sorted by name and are color-coded according to their status. The following are the colors and their statuses:''' | ||
+ | | ||
+ | * | ||
+ | '''Green=Production''' | ||
− | + | * | |
+ | '''Blue=Development''' | ||
− | + | * | |
+ | '''Red=Hidden''' | ||
− | ''' | + | * |
+ | '''Brown=Deprecated''' | ||
− | + | <br/> | |
+ | # | ||
+ | === '''Label Template File''' === | ||
− | + | | |
+ | '''The first step of creating a label is done outside of the Label Engine. A label layout and design tool are used to create the label template such that the finished label meets the customer's specifications. Typically the label specifications will cover such things as label media type, size, fonts, barcodes, tolerances, etc. Many different design tools exist and the choice of design tools is outside the boundaries of Label Engine. ''' | ||
+ | | ||
+ | '''A suitable design tool MUST be able to produce or export ZPL code (Zebra Programming Language) for use on Zebra Printers, or RTF (rich text format) for use on sheet / LaserJet printers. ''' | ||
+ | | ||
+ | '''As such, printing labels through Label Engine are limited to supporting printers that support ZPL (i.e. Zebra printers) or RTF (i.e. LaserJet printers).''' | ||
+ | | ||
+ | '''Label Engine’s main purpose is to provide a means of populating placeholder fields in labels. Label Engine keys in on values surrounded by $ (for example $partno$) to determine which label elements are mappable within the Label Engine. At print time, these placeholders are replaced with real data by Label Engine before sending the label to the printer. Not all design software or barcode formats will allow the use of the $ character, and in such cases manually editing/cleaning the ZPL might be necessary.''' | ||
+ | | ||
+ | '''The ZPL or RTF file(s) are uploaded to Label Engine as part of the label creation process.''' | ||
+ | <br/> <ol start="2"> | ||
+ | <li> | ||
+ | === '''Add New Label''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''To create a new label, select Add from the LE Labels main page.''' | ||
+ | | ||
+ | '''Figure 3: Add New Label''' | ||
− | + | '''https://lh4.googleusercontent.com/1svuJMqLIhb_h9-f7FtB2v3VtOkW9y2RGFgthxW2cll78qNpjysHeN8mvYgLA_chNKWEHf524G5cX8qFRwcmF8cjpUCzH9wj14NUCECXy3Hk4jnv-k3ZySM5mt0iVlE9CXVGOlMx-VP7DqgiVOUD1iBaBy1fClFnGvzurRx7cyIhJOGAdAGFqDTy1g''' | |
+ | | ||
+ | '''Enter the label name and customer and save the Label. Label names can only contain lower case characters, digits, and - (dash) and _ (underscores) all other characters and disallowed. Label names can not be changed after the first publishing of a label and label names MUST be unique so choose your name wisely.''' | ||
+ | | ||
+ | '''Figure 4: Save Label''' | ||
− | + | '''https://lh4.googleusercontent.com/NB6GYunp-O54twbTlvn4LG1iebFSWNK6AesKfDUxGiaprnHXtsEJjf2fOL3p7xounswOV3heYJH8Dn7NIO39iiEklfdH0y5d1M5jo8I4prCXo4eUUD0VsZ8uXoatoR1x_q6XKD94gSFLkVhI0z7soaujStWBZ4JfMnK3RvpRsdEs0JwP4DWaRa1L4g''' | |
+ | | ||
+ | '''A General Information screen will display. There are three tabs located to the right of the General Information form (Upload Files, Element Creation, and Label Mapping). ''' | ||
+ | <br/> | ||
+ | # | ||
+ | ==== '''General Information Tab''' ==== | ||
− | '''Figure | + | |
+ | '''The general information tab contains the same parameters that were on the initial creation screen so that these values can be updated. It also contains additional information in the database selection panel, and it contains additional controls to allow Parts to be associated with Labels.''' | ||
+ | | ||
+ | '''Figure 5: General Informationhttps://lh5.googleusercontent.com/EFCmPIa-CrewV22CbDp9ur7WeSRnR3CvnZ1m5TWagP33h_jeOQX9g_F8KbeCKBuk8ktqpylReEQKP43HwP4K0CjAmaJ8G229JTWVnWCpibnp4aSdFBqekfqqTB-ZDEuDuRx-FTL5rV8uFuDjMgYYeGF5fHATmBghWPDIRa3x_ohYyqmEW_DxcnenHQ''' | ||
+ | | ||
+ | # | ||
+ | '''The user will need to enter the following information in the General Information form:''' | ||
− | |||
− | ''' | + | * |
+ | '''Name - the unique name for the label. Each label must have a unique name. Label names can only contain lowercase letters, numbers, and underscore and the name is limited to 30 characters. Spaces are not permitted. The name is the key to printing labels using external web services.''' | ||
− | ''' | + | * |
+ | '''Version – Defines the current label version.''' | ||
− | + | * | |
+ | '''Size- Enter the size of the label.''' | ||
− | + | * | |
+ | '''Resolution – choose resolution based on the printer that will be used.''' | ||
− | + | * | |
+ | '''Customer – select a customer for the label from the drop-down list.''' | ||
− | + | * | |
+ | '''Kind of Material – Choose the material that the label will be printed: Kapton, paper, or polyester.''' | ||
− | + | * | |
+ | ''' Comments - label comments for any additional information.''' | ||
− | ''' | + | * |
+ | '''Duplicate Prevention - Use this to specify if the label should prevent printing this label more than once for any given "entry". This may be disabled due to administrative settings that are explained in the LE Admin SOP {put the link and proper name}''' | ||
− | ''' | + | <br/> <br/> |
+ | # | ||
+ | ===== '''Default Database Mapping''' ===== | ||
− | + | | |
+ | '''By filling out the Default Database section it will allow the user to use the option Part Must be Mapped in the case the selected database is an MDS Database. Moreover, it will provide the user with an autocomplete part of the creation of an element. Once a database is selected, the Table and Column lists will become available. Using these drop-down lists, define which database element will be provided at print time. This is also referred to as the default "entry" value.''' | ||
+ | | ||
+ | '''Figure 6: Database Mapping''' | ||
− | + | '''https://lh3.googleusercontent.com/pvID3Dfa59DiaR9Jb9Sb5e7ci7Y4Jk87OYMg3d2fqk_pHmp0OUUtGbbVjA3jB5fDUZmRUsKCl4n8OMnjtb3IkWvMiBZaYcyjS5RjSCCMvmWscEnRGujc6wwQBo5fU-HBIC0CwcJWmiuZdR4jiELIpvEVmWbaikF0KT0RpWIXuye2VrCy2-79Vb1JSg''' | |
+ | <br/> | ||
+ | # | ||
+ | ===== '''Part Number Mapping''' ===== | ||
− | + | | |
+ | '''Part number mapping allows the label to be associated with some Part Numbers. By having the Part Number informed in the Label Engine Print screen, it is very easy to find the label(s) that need to be printed by a Part Number. Depending on the Administrative configuration, Part Number mappings may be optional. Toggle the "Part Must Be Mapped" selection if the label should enforce part mapping at print time. If enabled and if the print time entry corresponds to a part that is NOT mapped to the label, the printing will be prevented. Note. This may be disabled due to administrative settings that are explained in the LE Admin SOP {put the link and proper name} ''' | ||
+ | | ||
+ | '''Enter the Part Number in the Part field and select Add 'to add the part in the Part Number list. To delete parts, select it, and select Delete.''' | ||
− | + | '''Figure 7: Part Number Mapping''' | |
− | | + | '''https://lh6.googleusercontent.com/hdckCT7hTDYPffKRKvYmm8uIUdS3Jj79fJ-IvqISxfy5ALk1ejzGrc_Ktpt0C9Hm9PG99F3lrWcdeBG22DjU3ss31GL443x4TA3LaKtJbzludwvF1WxeGikZ-8GIEWJ58qWehPIq67ifWd4z_Go6BhqOZuXO5THnVVwOhYrd0viiq-qvco_iYFnF7g''' |
+ | | ||
+ | '''Once you have provided all of the information on the General Information tab, select Save to commit your changes to the system, and then select Next. The user can also select the Upload Files tab.''' | ||
+ | | ||
+ | '''Note: Clear functionality will remove any data provided so you can start fresh.''' | ||
+ | <br/> <ol start="2"> | ||
+ | <li> | ||
+ | == '''Upload Files Tab''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''The Upload Files tab allows the user to manage the files and links for the label. To be usable, a label must have a template file as this contains the layout and definition of the label. A label engine label can only contain a single template file. ''' | ||
+ | | ||
+ | '''Label Engine's primary purpose is to collect, or generate, data and inject this data into the appropriate places within the template file and print the resulting complete label. Any "variable" data in a label template needs to be identified as a template field. Template fields are delimited by $ (dollar sign) characters. Label Engine identifies the template fields as the text between the $$, for example, $sn$ or $serial number$ or $serial_number$ would all be good template field identifiers as they are easy to understand what data is required. ''' | ||
+ | | ||
+ | '''When a template file is added to a label, Label Engine searches through the template and identifies a distinct list of template fields. Label Engine allows the label designer to "map" data to the template fields.''' | ||
+ | | ||
+ | '''As there are different printer types, LE supports different template types. LE has support for the following template files:''' | ||
− | + | * | |
+ | '''ZPL (*.txt or *.zpl) are for use with printers supporting the Zebra Printing Language''' | ||
− | + | * | |
+ | '''RTF (*.rtf) are rich text format files, for use on sheet printers.''' | ||
− | + | * | |
+ | '''DPL (*.txt or *.dpl) are for use with printers supporting the Datamax Printing Language''' | ||
− | + | * | |
+ | '''EPL (*.txt or *.epl) are for use with printers supporting the Eltron Printing Language ''' | ||
− | + | * | |
+ | '''Other Template Types (*.txt) is a catch-all that will allow you to upload any text-based printing language command file that the destination printer will support. Some examples would be J-Script (Brady Printers), IPL (Intermec), etc.''' | ||
− | ''' | + | |
+ | '''Many different label design tools exist and the creation of the printer-specific template file is outside the scope of Label Engine. LE simply requires a text file containing identifiable template fields. Template files are typically printer-specific command files. The exception to this is RTF. RTF files are converted to PDF files which can be printed on most sheet/laser printers. ''' | ||
+ | | ||
+ | '''Tip: It is possible to put multiple labels within a single template file. ''' | ||
+ | | ||
+ | '''The other supported "files" that can be uploaded are:''' | ||
− | ''' | + | * |
+ | '''Label Image Sample (*.jpg, *.jpeg, *.gif, *.png) are to include a static image of a sample label. A label will only allow you to include one image sample.''' | ||
− | + | * | |
+ | '''Font (*.fnt) are fonts that are required on your label. Fonts only apply to ZPL labels. <br/> The list of existing fonts will be displayed from which you can reference the one(s) your label needs.. If you need a font that has not yet been uploaded, you will be able to upload a new one. You can upload or link as many Font files as are needed for your label.''' | ||
− | + | * | |
+ | '''URLs are not actually uploaded and they don't have any content within LE. URL is so you can reference information about the specs of the label, or anything else you feel warrants adding a reference to. Basically, this is to allow LE to be the place you manage your label. ''' | ||
− | + | | |
+ | '''Figure 8: Upload Files''' | ||
− | + | '''https://lh5.googleusercontent.com/8vrNXwSUFCS6CPyAZQsk5pZGlz5nEoDLk6G_cH5mmSh38Muu8XhAmbNNXuSEeoH9ekzZivkws-35Fonb1Bv7SwVZluwmOOgLrdh0511GMT9B4GBpW1mn7sl9RQwOknCgWcZo36S7XHT57kuVvk4bep0brtaFfvKTqkD_tsmD-VFRPhRAMg6sKIVATA''' | |
− | == | + | '''Most files will be uploaded from the user’s local computer. However, if the font was already uploaded to the server for use in a different label it will be possible to reference the existing font instead of uploading it again.''' |
+ | | ||
+ | # | ||
+ | === '''Add File''' === | ||
− | + | | |
+ | '''To add a file to the label from your local computer, select Add from the Upload Files tab. ''' | ||
+ | | ||
+ | '''Figure 9: Add File''' | ||
− | ''' | + | '''https://lh5.googleusercontent.com/16t8dAer_nsCWTPyXiasYPDT5JIDPn2FzN2I0X7JBXkvAxq9zmwUIeJzPB6lganOk3P4qof-Pzx-YFM82zSb6Ab5A-9BuEtHNlHcCfcfFJbjQk1g7HeIDdisl5wFTZLUnSOW2Yk58mTDAYHGOMAFmNEoH3h-FfIZk8VaP9emk4kPJa8BV7R_8LZrvQ''' |
+ | | ||
+ | # | ||
+ | '''Select Browse to browse and select the file to add to the label.''' | ||
− | ''' | + | # |
+ | '''Add a description of the file.''' | ||
− | + | # | |
+ | '''Select Save to confirm the addition, Reset to clear the fields, or Cancel to cancel.''' | ||
− | 2 | + | <br/> <ol start="2"> |
+ | <li> | ||
+ | === '''Edit File ''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''For labels with files attached, the files can be edited as long as the label has not yet been published.''' | ||
− | + | # | |
+ | '''To edit a file, select the checkbox to the left of the file and then select Edit.''' | ||
− | |||
− | + | '''Figure 10: Edit File''' | |
− | + | '''https://lh3.googleusercontent.com/AvPmZD1XpCLavXbCG_1-i-NhcJdBflM0wer_UM-c8lE0XN9iGVINAmqQS0W3faRGcz8NMZlHG2_thnr5obJSBr72muYspJa2B-l_v40jU4FWPq-sR-AUdktE8UDndC1Mi7zSkVI-A3ZCe-OwDa9kQGanx5hFPqZn1Qf_xFwdow8m_rZo59T0fyXaoA''' | |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''Once the Edit button is selected, the Edit Files Uploaded pop-up displays to edit.''' | ||
+ | </li> | ||
+ | <li> | ||
+ | '''Only the Description portion of the file is available to edit.''' | ||
+ | </li> | ||
+ | <li> | ||
+ | '''Change the description and then select OK to save changes or Cancel to exit.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> <ol start="3"> | ||
+ | <li> | ||
+ | === '''Delete File''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | # | ||
+ | '''To delete a file attached to a label, select the checkbox to the left of the file name and select Delete.''' | ||
− | |||
− | + | '''Figure 11: Delete File''' | |
− | 2. Select ''' | + | '''https://lh6.googleusercontent.com/AKshJthWwl1ilEmR3HcYu8MiM6WvHFFsZ3Dy2Jq-5Dfp1AHb8tL2DSRkjJCPk6B-4GS45VR71Vj0Zb7Ih4r1BrFSCTM48m5OYususQpCxtsuySRD3xQhirfcf3gJNM3uBkXr79EG_c3FJnUEeNXlNNLlbhJW37WOnu6coq778BvCHVg_JdC_2ARVPw''' |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''A confirm box will display. Select Yes to confirm or No to exit.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <ol start="4"> | ||
+ | <li> | ||
+ | === '''Download File''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''Under the Upload files tab, the user can download the files attached to a label to retain the information from the label.''' | ||
+ | | ||
+ | # | ||
+ | '''To download the file, select the checkbox to the left of the file name and select Download.''' | ||
− | '''Figure | + | |
+ | '''Figure 12: Download File''' | ||
− | + | '''https://lh5.googleusercontent.com/cbG50moPH9m07HC1fVBs6UthgKF8QKGEGJqPOh37TRLj9saHLUybSh1Qe6Hs2zZjbKUmyEWWW_HPdDcSK_aa5ZSxoBfBgBoyeamRno1DmAYWvGC3e_TWV5dZfnm0WcVf-uPYup2KiCk9UPeqGxD6TOSp0s6RDuQtLWuDBSHWINISBRxo-f8tV4TMYg''' | |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''The download will be started automatically.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <ol start="5"> | ||
+ | <li> | ||
+ | === '''View Label Sample''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''The user can view a sample of the file that is attached to the label from the Upload Label tab.''' | ||
+ | | ||
+ | # | ||
+ | '''To preview a sample of the file, select the checkbox to the left of the file name, and select View Label Sample.''' | ||
− | + | | |
+ | '''Figure 13: View Label Sample''' | ||
− | + | '''https://lh3.googleusercontent.com/RXEx3gnnMinCUIJYEHkz_YJt397I3vNzrnFs3AR2achi52vCfFxIocbU7yAUryd03axYWOQQ4b1zbLlx7gvoWordMS-ScvFgePO83qMY-8mpxb9TdVT7BzrSh56clTSyIY7nhCWZ0_canOrLX4VhHNYHVsGOi9Fdpr2ke4LKv_YYwk3bNeKuZczMqSTiZrvB7w''' | |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''A sample of the file is displayed on a new screen.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> <ol start="3"> | ||
+ | <li> | ||
+ | == '''Element Creation Tab''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''The element creation tab is where users will create the "elements" of data that will be injected into the template at the print time via label mapping.''' | ||
+ | <br/> | ||
+ | '''Figure 14: Element Creation Tab''' | ||
− | | + | '''https://lh3.googleusercontent.com/wUairfmG2IkRMpLFoxmF2KLdOwBwfUiUi33DUV0Sutpl4hTFIlmkoz_JQ5fQ0I9yImC4qOc-RZMzTvoZWrY2veqIuJVp7hgtNFLJKooNZxSV4DBgpKf8cUjaWw3w8pIJKrqlFRTIeN4X7qWHsI4p4nlkiQzKvAUncqtx7D6xEwgo8VMX0G1OsIOggg''' |
+ | | ||
+ | '''On this tab, the user can create the elements. Elements are built up of 'blocks' of data, and elements are what is ultimately injected into the template file at a print time replacing the $place_holder$ fields.''' | ||
+ | | ||
+ | '''The application provides five functionalities (Constant Value, Date/Time, Database, Custom function, and Entry Value Block), from which the user is able to customize the elements.''' | ||
+ | <br/> | ||
+ | # | ||
+ | === '''Add Element''' === | ||
− | + | <br/> | |
+ | '''To add an element, in the Element Creation tab, select the Add Element button.''' | ||
− | + | '''Figure 15: Element Editor''' | |
− | + | '''https://lh4.googleusercontent.com/Z6GIHHdX46pBwJ2BNah8krPPtZAje5SxISYe6Q97HxI_IVAvn_9YC4Smn3otUGDjwvtup0O7LEUrRQJolMoNb9FWVzCgTCFqAlMris4iCks0LlUtrDBPtQy4Ta79QYQr3XhvUG3umD9yr5cE6uhP6assX4CTthb-JMzXrUPG-meeWj6Zcv5HvhlH''' | |
− | ''' | + | '''The Element Editor is displayed and the user can input the necessary information to the new element.''' |
+ | | ||
+ | '''Fill in the available fields:''' | ||
− | + | '''Element Name: the name of the element;''' | |
− | <br/> '''Figure | + | '''Comments: any necessary information that the user wants;''' |
+ | | ||
+ | '''Mandatory is a flag indicating that a non blank/non null value is required at print time. If the element value is empty at print time, the printing of the label is aborted and a message about the failure is recorded in the audit log and is reported back to the user. The default message contains a reference back to the element name. The element name is not always something that has meaning to an operator. To provide a more meaningful message (for the audit and the user response) LE allows the user to provide a mandatory custom message that will be used instead. When Mandatory is selected, an optional field, Custom Mandatory Message becomes available and this is where the label designer can provide the message to be used if a mandatory violation occurs. ''' | ||
+ | | ||
+ | '''Note: This Mandatory flag will be available at some of the functionalities and will be used for the same purpose. ''' | ||
+ | <br/> | ||
+ | '''Figure 16: Element Editor - Selecting Mandatory''' | ||
− | + | '''https://lh5.googleusercontent.com/7VUFO0owF5yMsI35lQb2h9L9V-CcbUiLtLRf1Fkpq_pEDI0fkU0pUmPfygGmGY6C3mC_0sBW3R6Q_CyG-Y3gBicTGw8T2Ezfpa6-ZoOhlfd-DXR8gsxXP9wchCEcG1jl17SDU4AG6HiEklPZWvmlsUp4QIUIXv5rJ4YemVnxNmADchJcMaNk_PCj1Q''' | |
+ | | ||
+ | '''Checking the Entry Point checkbox, it will be allowed to search values from two databases. It is used to set the database priority.''' | ||
+ | | ||
+ | '''The available functionalities are described below:''' | ||
+ | | ||
+ | # | ||
+ | ==== '''Constant Value''' ==== | ||
− | |||
− | + | '''Figure 17: Constant Value''' | |
− | | + | '''https://lh4.googleusercontent.com/95LeedPpy5nmxw9MHP2Qw13mQHmzEWmh8FyPLnAu2gs0Xo3SCX_iCnLrw6bSh92zknTBSCHKCTbk2pDOqaBQAg8pVbleAZM-CbR3wQE_LsqeLJoV0uJtzvALAYg0IKSUw_lGk8-v8ooqrPvv3ymmUyl3gtsCBRfulBxRQzPCMsFEq684C38cwwZSmg''' |
+ | <br/> | ||
+ | '''This functionality allows the user to create a constant value (fixed value) used for printing the value in the label.''' | ||
+ | | ||
+ | '''Block Name: this is the block title to be created;''' | ||
− | ''' | + | '''Value: Value to be printed in the label (any value type).''' |
+ | | ||
+ | '''Click on OK to finish.''' | ||
+ | <br/> | ||
+ | # | ||
+ | ==== '''Date/Time''' ==== | ||
− | + | | |
+ | '''This functionality will print the date and the time in the label.''' | ||
+ | | ||
+ | '''Figure 18: Date/Time''' | ||
− | + | '''https://lh3.googleusercontent.com/KZgRIiDfu5SGQRkQZLPWBLnvLi5IpKhb5j06gPzw6g6Ou7IQUbUpRhHmHcGXatE3_unm18dkG9fq2wm6h0UgHLLpdVVTvXb1iRn12A_15Spxou4l9CrT9zcrfOd9X55vMOLMRojwVbpyJv_ZjXM0KqZKdAeVmzAV-wUdE1IgtCBLSy0MzzWpykzxxg''' | |
+ | | ||
+ | '''Block Name: Name of the block to be created;''' | ||
− | + | '''Date/Time format: Select the format (from the available list) that will be printed in the label. ''' | |
+ | | ||
+ | '''Figure 19: Date/Time Format''' | ||
− | | + | '''https://lh5.googleusercontent.com/jp78G-9E-UBaYbzFHEDrzYEMoHZ_h3aFXxRqndqdkQTl1kn-hvSBROz48Rg7E8_z3vPKQVfbiu1SOJuP7sI8PW5RJ7yzV1QWUgXiz1_bEy41OOMRfyIpu07_ZJRbpPmAUawZSMOKkql6NFxk5ks2tdDmkGv1fBbwwjUVcQRuUhbTCajflAgqlOZYcw''' |
+ | | ||
+ | '''Block Modification Rules: It allows the user to set the rules to the selected field (date/time)''' | ||
− | + | '''Figure 20: Add Rule''' | |
− | + | '''https://lh5.googleusercontent.com/HA-WXx33-W15N58wADu5PqHa3s8QvBxh55nmVe6b5eJFU7keTSiaD88fvsmitF1cu6u88F_PopeppNeOXRtGUayxufM9evqbGx3n9jwviUzYe3U5iqL0jjoj5YLPxROf-ZO_yNABIFsn5afKSaHqeOgrzo9j53EOeBRUC3g-SkZCPTPjjUAN1Dk4aQ''' | |
+ | | ||
+ | '''The rules can be used to set or modify previously assigned label fields. Dynamic data, such as system date or time, can be formatted and assigned to a label field. Rules allow for data to be combined or transformed based on runtime conditions.''' | ||
+ | | ||
+ | '''It displays the details of the business rules assigned to the selected label field in the Rules list.''' | ||
+ | | ||
+ | '''Multiple business rules can be applied to any field. To add business rules to a field, follow these steps:''' | ||
+ | | ||
+ | '''To add a rule, select an existing rule from the list and click on the Add button. The new rule will be added to the list.''' | ||
+ | | ||
+ | '''The order in which business rules are applied can be changed using the arrows in the lower section of the details section. As well, business rules can be deleted or updated using the appropriate action icons.''' | ||
+ | <br/> | ||
+ | # | ||
+ | ==== '''Database''' ==== | ||
− | '''Figure | + | |
+ | '''This function loads the database information that will be printed on the label.''' | ||
+ | | ||
+ | '''Figure 21: Database''' | ||
− | + | '''https://lh6.googleusercontent.com/IqJuYplA6zb70Y2ZCeTjRyGvQxrTpBS1B67gUIbFMoKcBdMaboZg0B_ehuTDvs0NRFVAECVh13BqvRvTBIcQsupCnBEIx5crYLQfSm36M3FCwaLCxvYFcAxdPYql-I7hYHqXwaWeimhYEPf5bEzhTolgNiUsa_4DaYSAS6Fa_AysMdFpLHHMyj8bWw''' | |
+ | | ||
+ | '''Entry Value From: This form informs where the input for the element comes from. The common value is Print Call Entry.''' | ||
+ | | ||
+ | * | ||
+ | '''Print Call Entry: comes from the value used to print the label;''' | ||
− | + | * | |
+ | '''Element Name/Key: comes from the element;''' | ||
− | + | * | |
+ | '''Block Name/Key: comes from the block.''' | ||
− | | + | |
+ | '''The Entry Point Definition form displays the predefined values in the General Information.''' | ||
+ | | ||
+ | '''Value To Extract: The user needs to select the Table and the Column to get the information to be printed on the label.''' | ||
+ | | ||
+ | '''To provide a more meaningful message (for the audit and the user response) LE allows the user to provide a custom mandatory message that will be used instead. When the Mandatory checkbox is selected, an optional field, Custom Mandatory Message becomes available and this is where the label designer can provide the message to be used if a mandatory violation occurs. ''' | ||
+ | | ||
+ | '''Note: If the label is a Container Label, the user needs to select the Values Will Be Assigned To Different Fields option.''' | ||
+ | | ||
+ | '''Figure 22: Container Label Option''' | ||
− | + | '''https://lh4.googleusercontent.com/0SaOY3QD27oDcDHlFwZCWro2xA8n8Nys6B_pa5PEU3AVBygvr1JikoyyPoC72y6uSmEoxhiJKu_fg2NHLTizrl-5XV29VR0zXed_xQrCoDxbilAMjyW9kVuVwMt0PcU_5jMG4eJ-HJmKUuUFXeH1qCZNamfIXSCS6zooyW-5438M0phFbupky96mrA''' | |
+ | | ||
+ | '''The Block Modification Rule was already explained in the Date/Time topic.''' | ||
− | + | '''See [https://docs.google.com/document/d/1XoylUomqwCMYmKGUpQyu_p1ZSdnWFkeV459ifiLfyqE/edit#heading=h.vb55ud76nj7a Appendix D – Examples] for more information.''' | |
+ | <br/> | ||
+ | # | ||
+ | ==== '''Custom Function''' ==== | ||
− | ''' | + | <br/> |
+ | '''The Custom Function allows fetching database information through a customized function. ''' | ||
+ | | ||
+ | '''Figure 23: Custom Function''' | ||
− | + | '''https://lh5.googleusercontent.com/ZGngzHS4MH1U9ynB9QGyC2l5Q__lGdSRSbIcZTWQttV-53v1LEoiEAdTmV64-VADyM54yyaQaA6e_b3F55-qQ6FPDWBUoMsf8sV9XjvbwMS155Ie60mnWwCJuGc5bpCP0u5ZuERbXc-h3OYvr6AQkRbvYl8Hwjsj8ueZSqJGQpOAaj55Rr9isA93MQ''' | |
+ | | ||
+ | '''Entry Value From: This form informs were the input for the element comes from. The common value is Print Call Entry.''' | ||
+ | | ||
+ | '''To provide a more meaningful message (for the audit and the user response) LE allows the user to provide a custom mandatory message that will be used instead. When a Mandatory checkbox is selected, an optional field, Custom Mandatory Message becomes available and this is where the label designer can provide the message to be used if a mandatory violation occurs. ''' | ||
+ | | ||
+ | * | ||
+ | '''Print Call Entry: comes from the value used to print the label;''' | ||
− | ''' | + | * |
+ | '''Element Name/Key: comes from the element;''' | ||
− | + | * | |
+ | '''Block Name/Key: comes from the block.''' | ||
− | + | | |
+ | '''Database: after the database is selected, the functions are displayed in the list and the user can select them and inform the Function Details.''' | ||
+ | <br/> <br/> | ||
+ | # | ||
+ | ==== '''Entry Value Block''' ==== | ||
− | |||
− | + | ''' ''' | |
− | + | '''This functionality gets the entry information used to print the label (generally, the Serial Number).''' | |
− | + | ''' ''' | |
− | + | '''Figure 24: Entry Value Block''' | |
− | ''' | + | '''https://lh5.googleusercontent.com/UVjp_lp0149QQrvc-Ygv18f7ulJDH5DQUXeNFwoKzwsBnyyvitFX4YKijx65Qw3Ctwwiid8Tge7GbrORTlae7NMu8oHEj_LWx7xE6j9zdBZ5QWkctW83u9uEhksU40ZuPlJju7KW4BbaaTGXC4Q8xwtiZJnjs3Up0y-ph6FcMagYI3XE4uTQY4m2wg''' |
+ | <br/> | ||
+ | '''Click on Save to finish.''' | ||
+ | | ||
+ | # | ||
+ | ==== '''Delete Entry Value''' ==== | ||
− | + | | |
+ | '''Figure 25: Delete Entry Value''' | ||
− | '''< | + | '''https://lh6.googleusercontent.com/SOUb6x2VBXEUJT4vnTiOC5WcrLchN0sU8sCdUWavcmGtg8moVPQ7yeAVssTsClONBFk14TDnCIDaPit4tD8t6pQGyniaLSS4IbQgFV1soxemdHvwpfjOkdEQi9jVWDy94CgntRKx1DYfIoyvm5Bl3OoYDIREU9dsu8SHVyeNl8g3RxQkSrdXmlRPOw''' |
+ | | ||
+ | '''To delete, just select the Entry Value Block in the list and select Delete. A confirmation message is displayed, select Yes to delete or No to abort.''' | ||
+ | <br/> <ol start="2"> | ||
+ | <li> | ||
+ | === '''Edit Element''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''Editing elements work pretty similarly to Add Element. Refer to Add Element topic for further information.''' | ||
+ | | ||
+ | '''Figure 26: Edit Element''' | ||
− | + | '''https://lh3.googleusercontent.com/y4uLuwDmw-ZnzkH5jN0_nQuyX52nbrOnyej_jnNbU7aIf-XjEYvUxk9ftrlQSPPhmo_mEskHLTOgd4WL4J20pnng5TGYzXOrj5AJRnZQv5cUf1cQDr8l4VTGcOlOe3scus9JSpj7wSgov3lJqAbJLFWMBDN6svMDQWOpmWuPvAyOojeuydwgZN6ajA''' | |
+ | | ||
+ | '''Editing elements work pretty similar to Add Elements. Refer to Add Element topic for further information.''' | ||
+ | <ol start="3"> | ||
+ | <li> | ||
+ | === '''Delete Element''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''To delete, just select the Element Name in the list and select Delete.''' | ||
− | + | '''Figure 27: Delete Element''' | |
− | ''' | + | '''https://lh3.googleusercontent.com/jMIVcTAiKIEqKlfemqEuCJ8fsaU8THaTVfzl6K_ti9o35DT9TO_RUPw5NQvuQ1lnYVQYWqGgd9ZPl21NNbSsJmAJ8i3eNCSqpGUVd3YIjvJBth_dPuvAzeWJuRAut7k8oknnAXkcN7V28JpuygdMJxNRYvhK9CQKFJjQEeA4WCmL0uAiVfpFJ70l7Q''' |
+ | | ||
+ | '''A confirmation message is displayed, select Yes to delete or No to abort.''' | ||
+ | <br/> <ol start="4"> | ||
+ | <li> | ||
+ | === '''View Element''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''This functionality allows the user to view how the element was created.''' | ||
− | + | '''It is not allowed to do any updates on this page.''' | |
+ | | ||
+ | '''Figure 28: View Elements''' | ||
− | | + | '''https://lh3.googleusercontent.com/HG-7nuK3ItvaG2LBfGbj5W_wocBRTdcQY9sPFZUAFsPljyFZcT8Kgkl7JZuf0DzCyaFcAuFb8x1EhwZ2f8UmcUzBS0aW1IVIfNrTGdOlsWbpsagyTWLWnhfR6UlhsJndC4F7lku_vMZvMLqHw5HNX5w8xbqJFNaMpHOLg6uBDJR5GMQAABg_-jEyIw''' |
+ | <br/> <br/> <br/> <ol start="4"> | ||
+ | <li> | ||
+ | == '''Label Printing''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''One of the major features provided by Label Engine is printing labels. Users can print labels to any available printer. ''' | ||
− | + | '''This page changes based on the settings for duplicate prevention if the entry has been printed before.''' | |
+ | | ||
+ | '''Figure 29: Print Label''' | ||
− | + | '''https://lh3.googleusercontent.com/0jHL2XhovOfaIjsluLNOsmPFkmaAGuS7izwjI1YJYAkLORWdLdH0KO1pf8tamKEISYgnljoYjvAfh1LmuWmHaUpnxzN51aCLHXzF3uUsA9wifVerAkBNAj3-ZqENdhH4e3tfT7p47VlY-nDKm6MElk19D4yTZNQVdCsfNt-Z2XDoijhMfmntNapt''' | |
+ | | ||
+ | '''Figure 30: Print Label Options''' | ||
− | + | '''https://lh3.googleusercontent.com/EfU59P6MZGsjPlsc84JInEhWjBcluj-ta1_xYCPFpxNQ41Ai_03rIXYarZUCPYtu_mftxvzxE2BSNmGR3rS4j-N0pIxkZNKG574IDsYnVs6fqpIVW1DrDeoqbZstYxCroqcgCi681aT68SixKaM-8GbjbHvEQyDAluUd_lXqHIeTV9woX26qRoEM''' | |
+ | | ||
+ | '''To print a label:''' | ||
− | + | # | |
+ | '''Select the box to the left of the Label Name on the main Label Engine page.''' | ||
− | ''' | + | # |
+ | '''Select the printer icon on the far right of the screen.''' | ||
− | + | # | |
+ | '''Choose a Printer.''' | ||
− | + | # | |
+ | '''Enter the information used to print the label into the Entry field and select Print.''' | ||
− | | + | |
+ | '''View Raw Data: The user can get the raw content that will be sent to the printer.''' | ||
+ | | ||
+ | '''Local Print (download): This option allows the user to download the print result locally as a PDF or ZPL.''' | ||
+ | | ||
+ | '''Test Print: Duplicate prevention and Test printing. If the label (and the plant configuration) has duplicate prevention turned on after the Entry field loses focus, the print history is checked. If the label-entry combination has been printed, viewed, or downloaded before it can't be printed again. It can only be reprinted (as many times as needed). In order to perform a reprint (if the user has permission to reprint) the three fields (Reprint Reason, Approver, and Notes) need to be filled before the reprint options become available.''' | ||
+ | | ||
+ | '''Local Test Print (Download): Test Print / Local Test Print are always allowed. This feature still requires a valid entry, however, the print activity does not use up the one label entry allowed. It is still recorded and viewable from the audit, but it is recorded as a test print. Also, all of the elements have their value reversed before being injected into the template so, in fact, the generated label is significantly different from a regular print.''' | ||
+ | | ||
+ | '''Note: This section also discusses web service printing. The new LE web service is documented with Swagger (which allows the user to describe the structure of your APIs so that machines can read them. See the details at [http://p99ls9.sanmina.com:8081/lbleng-webservice/index.html http://p99ls9.sanmina.com:8081/lbleng-webservice/index.html]. ''' | ||
+ | | ||
+ | '''In addition, Label Engine has web services that expose printing functionality to other applications. For example, it is possible to print labels created in the Label Engine by using the SFDC Commands (!! Commands):''' | ||
+ | | ||
+ | ''' !!1LABENG.<labelname>.<print queue>''' | ||
+ | | ||
+ | '''where ''' | ||
+ | | ||
+ | '''<labelname> is the exact name of the label in Label Engine, and <print queue> is the exact name of the print queue defined in Label Engine.''' | ||
+ | <br/> <ol start="5"> | ||
+ | <li> | ||
+ | == '''New Version''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | # | ||
+ | '''To create a new version of a label, select the box to the left of a Production, Hidden or Deprecated label then select New Version.''' | ||
− | + | | |
+ | '''Note: Labels in Development cannot have New Versions created.''' | ||
+ | | ||
+ | '''Figure 31: New Version''' | ||
− | The | + | '''https://lh5.googleusercontent.com/FE-E-qEPKgH4t77elllfrtXk-H882ZBLj0XKnmLsnORyakxA_XodjmAOUfWhSDhJ481r-M5vKqWb8WiXgVANr8Bo4PbjF0M2tzIr-viUYmLUwSMuIXOTVMUvgr8kdlrvr8anWNabyrLzmC-YHFiU2Q-ODnEhK7g91qG4O5B9vBlLToLAUeiE88fxAA''' |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''The General Information form will be displayed. All fields are available to edit to create a New Version of the label.''' | ||
+ | </li> | ||
+ | <li> | ||
+ | '''Select Save.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <ol start="6"> | ||
+ | <li> | ||
+ | == '''Edit Label''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | # | ||
+ | '''To edit a label, select the box to the left of a label in Development.''' | ||
− | + | | |
+ | '''Note: Only labels in Development are available to edit.''' | ||
+ | <br/> | ||
+ | '''Figure 32: Edit Label''' | ||
− | '''< | + | '''https://lh6.googleusercontent.com/TW3sd9YkHS0UP8MdkEKd5J8AmoJCt8LIAAA4o70VPyqGDem2sMWZ9xVSNwTh2y4VgKGcYlx00Iy2D7UwhGT2pj8hDCnkbaB677vnnEwfoMIFqCZSSAYftt0fx1n4kWtfpYCkJYRvdtaswobpfW0MIsTTmN9FDHab13n0OU17H9P-XnWP3IWzn0BZfQ''' |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''The General Information form will be displayed. All fields are available to edit.''' | ||
+ | </li> | ||
+ | <li> | ||
+ | '''The Upload Files, Element Creation, and Label Mapping tabs are also available to edit.''' | ||
+ | </li> | ||
+ | <li> | ||
+ | '''Select Save to confirm changes.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <ol start="7"> | ||
+ | <li> | ||
+ | == '''View Label ''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''View functionality is very convenient to view how the label was created in case the user does not have permission to edit.''' | ||
+ | | ||
+ | # | ||
+ | '''To view a label, select the box to the left of a label in production.''' | ||
− | ''' | + | # |
+ | '''Select View.''' | ||
− | + | <br/> | |
+ | '''Figure 33: View Label''' | ||
− | | + | '''https://lh6.googleusercontent.com/Z8wDKWimEKn--n967jKY6L1EKRXYxjpLJFbE1uKYAi7egz_AhG8dKrOtE7mLLfIWqJjIs9gemkzpk_jZahAK627Zv2S32SAhYKZV-lOtVtVjdeo1NbwVmD_Kch7Pcqxkva-SjzZFOQtzmJ3aNguhZvnQYBTNJ45xR_jVa1JKGzlHXT4ZLP4ikS9NOQ''' |
+ | <ol start="3"> | ||
+ | <li> | ||
+ | '''All tabs will be displayed.''' | ||
+ | </li> | ||
+ | <li> | ||
+ | '''The label information is available to view only.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <ol start="8"> | ||
+ | <li> | ||
+ | == '''Add/Remove PN''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''This functionality allows the users to add or remove Part Numbers associated with the label.''' | ||
− | + | # | |
+ | '''To add or delete a Part Number from a label, select the box to the left of a label.''' | ||
− | |||
− | + | ''' ''' | |
− | + | | |
− | + | '''Figure 34: Add/Remove Part Number''' | |
− | + | '''https://lh4.googleusercontent.com/qIXYlx9fguq17YqhNO8NILqdoZzX2U_RnY-RvcJjNeBDziwYnkiCdifr_4KxeT1QujF2TEjasQkXOkfmDsmm5VglJT-TH_ADNM0zG5O4QwjbyIigirYbB1sdPcZDJRt-TAe32ollIBJeAT-29tXamIbn67VSfrLhcESNFdNuFk5SHnlVzi7pRV673Q''' | |
− | + | '''Figure 35: Part Number Mapping''' | |
− | + | '''https://lh6.googleusercontent.com/gbtZ0ygQQWVi18bEPGg0qHWe2no-zgsF1tO0US2M0EVsPhLyKWCafIB7Z5IRt9GxR4lygw2uXIer1M8oNnMZMQTyTsePzQtYnGejDmTogxG9rDqFyVAFhqoT8JrEsJfQc-EbAaqjrr1-m9KVYm5qRbC96iZflGNwySJIi9aTLSei92q8fMupPS1_EQ''' | |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''Enter the part number and select Add.''' | ||
+ | </li> | ||
+ | <li> | ||
+ | '''Select Add to confirm or Close to cancel.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''Figure 36: Delete Part Number''' | ||
− | To | + | '''https://lh6.googleusercontent.com/tfh1ZP8R473FdD7goH01scPCBpoDMIqrpXpIm-dFhXReMe1zaorEd3K7ENuQMmeFgDN4ZE5z-fgf0XAlmITeBtdOwNv-XziqK-6VYbPepXAc-ZG0J5u_LrHXDcmqQc3rYnSxUqm3KW4343uXoS2lzVS3MfKlAwtle3FyFkbJSdEALXvpvB8KI7Arig''' |
+ | | ||
+ | # | ||
+ | '''To delete a part number, select the box to the left of the part number and select Delete.''' | ||
− | ''' | + | # |
+ | '''A Confirm screen will display. Select Yes to confirm deletion or No to cancel.''' | ||
− | ''' | + | <br/> <ol start="9"> |
+ | <li> | ||
+ | == '''Copy Label''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | # | ||
+ | '''To copy a label, select any label from the Labels list and then select Copy.''' | ||
+ | | ||
| | ||
− | '''Figure | + | '''Figure 37: Copy Label''' |
− | |||
− | |||
− | |||
− | |||
− | + | '''https://lh6.googleusercontent.com/NNdTq7GK2siDQrjfnzJftkaouKFzBh2AX33im_npLOHelhXVMtxGeDH6GitNkuLfeoQUd54Puis-RJuTbURzvhEyLj3CmPdmRwRLYs1dl1OGuFG2suGo2v-WV6rLSqnsygOiV6tZQMbw-Xp9mFmmPMK7iD7Y9qzjF7Wwlcd_77msbyhS7LqjIbgkEg''' | |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''All tabs forms will be displayed. Apply the necessary changes and then, select Save at the bottom right of the screen to save the changes.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> <ol start="10"> | ||
+ | <li> | ||
+ | == '''Delete Label''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | # | ||
+ | '''To delete a label, select the box to the left of a label in development. ''' | ||
− | + | | |
+ | '''Note: Only labels in development status can be deleted.''' | ||
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''Select Delete.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''Figure 38: Delete Label''' | ||
− | + | '''https://lh4.googleusercontent.com/YoP-nYSILhqCwI7c9JUxyp1q2DuCr3qWtik0bGMB3YU2iUxvMi8xZ5rcDaT7kqIuDhmp9lJiCc-YBeeYQvWMP6V6wGaZQEYdrOKJ16l4-5n4jDOD7lyixEETxvySsSPN4GRaTx21IbgkThRFBH2wdB7OysAlZJJBb2vgHIaApwhnu-Lv_8H9cAQ7OQ''' | |
+ | <ol start="3"> | ||
+ | <li> | ||
+ | '''A confirmation message will be displayed. Select Yes to confirm deletion or No to cancel.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> <ol start="11"> | ||
+ | <li> | ||
+ | == '''Hide/Unhide Label''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''Certain labels can be hidden from the list of available labels using the hide function. Labels that are currently hidden can be revealed using the unhide function.''' | ||
+ | | ||
+ | '''Hide a production label, prevents the label to be printed by using SFDC Commands or any other print action from an external application, such as Shop Order Print module, SIT, and others.''' | ||
+ | | ||
+ | # | ||
+ | '''To hide a label, select the box to the left of a label in production and select Hide.''' | ||
− | | + | |
+ | '''Figure 39: Hide Label''' | ||
− | + | '''https://lh5.googleusercontent.com/4A2kd0CLZKwZqd2EGeP23c3YxbBqc6tAodLfuJbuM8BDok5otu_y0OXdRpEcmd5tgjsm9kZpo55-TiYnELONiYhyrUaprf-sKJLDced-nC4mDBKRBbZQS7kHZU0NFWON8_KNrnTDS3dgi4JeAPLITETmNlT_uShLbGtqMr2goPNeQQFeUTAE0bHroQ''' | |
+ | | ||
+ | '''Note: Only labels in production can be hidden.''' | ||
+ | <br/> | ||
+ | '''Unhide the label restores a previously hidden production label and it can be printed using SFDC Commands or other external applications.''' | ||
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''To unhide a hidden label, select the box to the left of a hidden label and select Unhide.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''Figure 40: Unhide Label''' | ||
− | To | + | '''https://lh3.googleusercontent.com/5GeKajD1mpdSZd7usELXXeSLwqdpDXruwwHgQM8nWwdWNjblxTyZXF7HMcPo1-X0XaPf6j6aHt49WgiB07DnBrP96TJZjY79P_xD_QybbqRr6oP4He4rjtRUS1eHETP1ASQUeRLRQu-H3USq-SEh7RVStNqZXmsfUrvTMsFkM6FSt0pzmTW8xnSxEQ''' |
+ | <br/> <ol start="12"> | ||
+ | <li> | ||
+ | == '''Publish Label''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''Publishing a development Label locks the label and makes it available for printing from other applications.''' | ||
+ | | ||
+ | # | ||
+ | '''To publish a label, select the box to the left of a label in development status, then select Publish.''' | ||
− | '''Figure | + | |
+ | '''Note: Only labels in development can be published.''' | ||
+ | | ||
+ | '''Figure 41: Publish Label''' | ||
− | + | '''https://lh6.googleusercontent.com/9miRhsHd_TnxX_CluTWYKP0WLGPKkZuazsYY8iw2IS9wk0uTaUdXoyy6OtO_AU808C8t71Tlz0IIUQUlDXY5-iQR-UZauXrd6p3MGeVljR6J6abeVtXMbVlQW5gioVjlan6mGlC0AiON45Urk51tQ5WUMJ8sjQzV4CClJzW95PiGSfOJ5TI9cS2S1Q''' | |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | '''A confirmation message will be displayed. Select Yes to confirm or No to cancel.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> <ol start="13"> | ||
+ | <li> | ||
+ | == '''View Label Sample ''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''The user can preview a sample of certain labels using the View Label Sample function.''' | ||
+ | | ||
+ | # | ||
+ | '''To preview a sample of a label, select the box to the left of a label in Production/Development.''' | ||
− | '''Figure | + | |
+ | '''Note: Only certain labels have previews attached to them. The only way to know which labels have previews is by selecting each one and looking for the Label Sample Preview functionality to become available.''' | ||
+ | <br/> | ||
+ | '''Figure 42: Label Sample Preview''' | ||
− | ''' | + | '''https://lh6.googleusercontent.com/GfHxwYBZjxHcog4_-9Pr46hlncyjMqS-8j0Xk5vXKicgd3sLfOox2WPGAu6jNpYZHpz89H_-TiT-DoRw8Bxnd9elvYarql34wuLj0udnm_XLhFUS1-1DIUS_OM5dWIqj9zEplihOh1SDf5rtThT-VJCdJnnUfuBlTw0VXJMn-O3jYM4W-cCRQxGxSw''' |
+ | <br/> <br/> <ol start="2"> | ||
+ | <li> | ||
+ | = '''LE Reports''' = | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> | ||
+ | '''The available reports allow the user to mine the logs to extract usage data. There are three report options: ''' | ||
− | + | * | |
+ | '''LE Version History''' | ||
− | + | * | |
+ | '''LE Print History ''' | ||
− | + | * | |
+ | '''LE Statistics''' | ||
− | + | <br/> | |
+ | # | ||
+ | '''Select LE Version History, LE Print History, or LE Statistics.''' | ||
− | + | <br/> | |
+ | # | ||
+ | == '''LE Version History https://lh6.googleusercontent.com/dzJ4fqviRUcJpF7Ix41pAHtPi1AsV9UWBO8HkgD3od0WpKWKDE_j5Wt-4x0Bsput536_qntbdWwgNkkvu2R3ZpKr3isOoJwPCjDBBtWkD9AOwoqLmIU1fdMMr5IrBbtet9vdMtmxE0Cfoicq8gRALlJehuAHnGTxnypJdqqmGjA-MKlSpT-I3trfEw''' == | ||
− | '''Figure | + | <br/> |
+ | '''To access the LE Version History, select the LE Version History from the Label Engine View menu.''' | ||
+ | <br/> | ||
+ | '''Figure 43: LE Version History Page''' | ||
− | + | '''https://lh6.googleusercontent.com/sPs19LwlD_j6cP8JixKO2KxuaGnfc9oXavxi7OTZxi_RfICuBIVG-qwImaqpsRV7BPj__pqRkfiYH6-v3JiqGbxhTgcCsFqEuwGCAULzGe_jZ_otGQ5MJLA-lSJ0d8CbL3Rn6uyjv2DtAdYZk0ooGioDV2-TQcnDs9Rt0nMCMSur8m7kS_y9KNC4sg''' | |
+ | | ||
+ | # | ||
+ | '''Set the filters as needed.''' | ||
− | + | # | |
+ | '''Select Filter to extract the data.''' | ||
− | ''' | + | # |
+ | '''The results of the query will be displayed in the List.''' | ||
− | ''' | + | <br/> |
+ | '''This report displays the history of the label: who created it, when, its version, and its status. ''' | ||
− | + | ''' ''' | |
+ | <ol start="2"> | ||
+ | <li> | ||
+ | == '''LE Print History https://lh3.googleusercontent.com/s8oqml7NY3s27LtMTMAMxEncJToCDSnjK_QYsqTNjEd5UCm3H8wKPu6YWyAmNzyZwe96kzsXyd_ZLaXTSfj8q79JRu64NdfLlW9E1VCAEKBe5_WI0-SeRDPEa4XVpQTXrxgyrcG6VQk814BU8WSTAhhoXBJWHGKtWpCRzO67SffoCu1AP8J0dXDjIw''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> | ||
+ | '''To access the LE Print History, select the LE Print History from the Label Engine View menu.''' | ||
+ | <br/> | ||
+ | '''Figure 44: LE Print History Page''' | ||
− | + | '''https://lh4.googleusercontent.com/5yyB0eJmRJiVuta_D9twSKu8EK_RaLsAbdmWVOwSLrlkG1i4_1iTIWuDPADvJPrO3I2mtt6LWomtWqTEvyUOIFYARjV4zITP9YAsmAlHGns4gRo74k9NWoBcC8xlABgfL4BNvjX4G3EHqJ7tUEV8pgMcsdfKYNNow4zmUzDmrZofUJRPnfdquNE3rw''' | |
+ | | ||
+ | '''This report displays when the labels were printed, which system or Web Service method invokes the print action, which entry value (e.g. Serial Number) was used to print the label, and other information related to the print action. ''' | ||
+ | <br/> <br/> <br/> <ol start="3"> | ||
+ | <li> | ||
+ | == '''LE Statistics https://lh5.googleusercontent.com/eee_YRC6eG6tRoUhZ8WS7j3dZ8BSE3NcFxq0gmz-Qu3vu8HktSAdyC2vgbp4sSIVbZ0tv0gtSrS3fFGuj9cs5qi2XHWL2uIEIRIz23S-ftr4AltN4DSDM5MaEQkD-yrKNVsdWKM6wIhNj3wOlX5o2bQUOvvtgIJlNz4uWaNJpT48kW4kc7TF-MXtTw''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> <br/> | ||
+ | '''To access LE Statistics, select it from the Label Engine View menu.''' | ||
+ | | ||
+ | '''Figure 45: LE Statistics Page''' | ||
− | + | '''https://lh5.googleusercontent.com/96p16oABePHkAEEVwOeM7Yz1zN2GqTeTfR2CjR2Ha3FcsMUQCdDlbLPOa-YZPDID0Tmfl-sdxKMzr0Me7WRjhnl8q1IPCl4Fdg3tFdXQ1lXjOieQQOl646fDbxbAj3j5sbUsQk6UWEbPpVhxtI8qBtVSjXgt2FqxmqFMpsxoVg0ZINZJ9svgIRVUCg''' | |
− | |||
− | |||
− | + | # | |
+ | '''To extract statistical information, select LE Statistics.''' | ||
− | + | <ol start="2"> | |
+ | <li> | ||
+ | '''Select the begin and end dates using the date selectors to define the time range for the statistics that will be generated and the Statistic Type:''' | ||
+ | </li> | ||
+ | </ol> | ||
− | + | * | |
+ | '''Print Activities''' | ||
− | | + | * |
+ | '''Created Revisions ''' | ||
− | + | * | |
+ | '''Created Labels''' | ||
+ | <ol start="3"> | ||
+ | <li> | ||
+ | '''Select Filter.''' | ||
+ | </li> | ||
+ | <li> | ||
+ | '''The results will be displayed in the Name column.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> | ||
+ | '''The user is able to save the report locally by clicking Export.''' | ||
+ | <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <ol start="3"> | ||
+ | <li> | ||
+ | = '''Appendix A – Key Terms''' = | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> | ||
'''C''' | '''C''' | ||
'''Column''' | '''Column''' | ||
− | The columns are parameters present | + | '''The columns are parameters present in tables. A column has a type and can represent a data type like an integer, date, or string or can be a link to another table being used on relationships. Columns are often referred to as database fields.''' |
− | + | | |
'''Customer''' | '''Customer''' | ||
− | A customer of 42Q will be related | + | '''A customer of 42Q will be related with a label.''' |
− | + | | |
'''D''' | '''D''' | ||
'''Database''' | '''Database''' | ||
− | Database that the label engine can be connected to retrieve data. The main parameters are described below. | + | '''Database that the label engine can be connected to retrieve data. The main parameters are described below.''' |
+ | | ||
+ | * | ||
+ | '''Name: The name of the database, this is the name to be used on the connection.''' | ||
− | * | + | * |
− | + | '''Type: The type of the database: PostgreSQL, ERP, MySQL, SQLServer or Progress.''' | |
− | |||
− | |||
− | |||
+ | * | ||
+ | '''Address: The address of the server where the database is running.''' | ||
+ | |||
+ | * | ||
+ | '''Port: The port on the database server that is accepting connections.''' | ||
+ | |||
+ | * | ||
+ | '''Schema: The schema is a namespace into the database that stores data in separated logical structures into the same database. PostgreSQL and ERP can use this kind of feature.''' | ||
+ | |||
+ | | ||
'''F''' | '''F''' | ||
'''Field Number''' | '''Field Number''' | ||
− | Field numbers are all fields that can be replaced or used with the result of a query or input data. Each field number must be related | + | '''Field numbers are all fields that can be replaced or used with the result of a query or input data. Each field number must be related with a format file.''' |
− | + | | |
'''Format File''' | '''Format File''' | ||
− | Format files are the templates where the field numbers are associated. | + | '''Format files are the templates where the field numbers are associated.''' |
− | + | | |
'''L''' | '''L''' | ||
'''Label''' | '''Label''' | ||
− | Labels are the representation of all files, data | + | '''Labels are the representation of all files, data and rules that are used to build a structure for printing a label.''' |
− | + | | |
'''P''' | '''P''' | ||
'''Plant''' | '''Plant''' | ||
− | Plants are each local 42Q factory. | + | '''Plants are each local 42Q factory.''' |
+ | | ||
+ | '''Printer''' | ||
− | ''' | + | '''The printer is present on a plant. These printers are installed on a print queue of the server that is running the label engine application.''' |
+ | |||
+ | # | ||
+ | '''Print Queue name of the installed print queue of the server''' | ||
− | + | # | |
+ | '''Address the IP or name address of the server that is running the label engine''' | ||
− | # | + | # |
− | + | '''Port the port that the label engine is running on the server''' | |
− | |||
+ | | ||
'''Project''' | '''Project''' | ||
− | The projects are structures related to Progress databases. In this sense, each project must have one database associated with it. A project identifies what | + | '''The projects are structures related to Progress databases. In this sense, each project must have one database associated with it. A project identifies what MDS will be used on the connection with the database to retrieve data.''' |
'''Q''' | '''Q''' | ||
Line 784: | Line 1,086: | ||
'''Query''' | '''Query''' | ||
− | + | '''Query is the entity used to represent how data can be retrieved from a database. A query can return values of one or more columns based on the relationships among a set of tables that can be configured by the user.''' | |
− | + | | |
'''T''' | '''T''' | ||
'''Table''' | '''Table''' | ||
− | The tables are the data structure present | + | '''The tables are the data structure present in databases. This table contains a set of columns and can be used to create queries.''' |
− | + | | |
'''U''' | '''U''' | ||
'''User''' | '''User''' | ||
− | The users of the Label Engine. | + | '''The users of the Label Engine. ''' |
− | + | | |
'''V''' | '''V''' | ||
'''Variable''' | '''Variable''' | ||
− | Variables are used as parameters of the business rules and are similar to field numbers they have a query associated with them, so the result of the query will be the data inserted on the parameters. | + | '''Variables are used as parameters of the business rules and are similar to field numbers; they have a query associated with them, so the result of the query will be the data inserted on the parameters.''' |
− | + | <br/> <ol start="4"> | |
− | + | <li> | |
− | + | = '''Appendix B – File Types''' = | |
− | + | </li> | |
− | + | </ol> | |
+ | | ||
'''Format File''' | '''Format File''' | ||
− | A format file keeps all the structure information to print an entire label or part of it. A label is composed of one or more format files. The system contains two types of format files: | + | '''A format file keeps all the structure information to print an entire label or part of it. A label is composed of one or more format files. The system contains two types of format files:''' |
+ | | ||
+ | * | ||
+ | '''User Format File: A file that doesn't contain an identifier. This file is represented by the icon User format file icon in the upload file tab.''' | ||
− | * | + | * |
− | + | '''Printer Format File: A file that contains an identifier. This file is represented by the iconPrinter format file icon in the upload file tab.''' | |
+ | | ||
'''Image''' | '''Image''' | ||
− | A file that represents an image will be sent to the printer. | + | '''A file that represents an image that will be sent to the printer.''' |
− | |||
− | |||
+ | '''This file is represented by the icon Image in the upload file tab.''' | ||
+ | <br/> | ||
'''Font''' | '''Font''' | ||
− | A file that represents a font style that will be used in a label. This file will be sent to the printer. It is represented by the Font icon in the upload file tab. | + | '''A file that represents a font style that will be used in a label. This file will be sent to the printer. It is represented by the Font icon in the upload file tab.''' |
− | + | <ol start="5"> | |
− | + | <li> | |
− | + | = '''Appendix C – Business Rules''' = | |
− | + | </li> | |
− | + | </ol> | |
− | + | | |
− | + | '''Parameters''' | |
− | ''' | ||
− | |||
− | |||
− | ''' | + | # |
+ | '''Initial index: the beginning index, inclusive.''' | ||
− | + | # | |
+ | '''Final index: the ending index, exclusive.''' | ||
+ | | ||
'''Parameters''' | '''Parameters''' | ||
− | *''' | + | * |
− | + | '''Search for value: Text''' | |
− | ''' | + | * |
+ | '''String position: Text''' | ||
− | + | | |
+ | '''Insert''' | ||
+ | '''Insert a string in the position informed.''' | ||
+ | | ||
'''Parameters''' | '''Parameters''' | ||
− | * | + | * |
− | + | '''String to be inserted: the string to be inserted.''' | |
− | + | * | |
− | + | '''Position of insertion: the position where the String to be inserted parameter should be inserted.''' | |
− | |||
− | |||
− | |||
− | |||
− | * | ||
− | |||
+ | | ||
'''Data Format''' | '''Data Format''' | ||
− | Return the date in the specified format. | + | '''Return the date in the specified format.''' |
− | + | | |
'''Parameter''' | '''Parameter''' | ||
− | + | # | |
+ | '''Data format: the pattern describing the date and time format.''' | ||
+ | | ||
'''Ends With''' | '''Ends With''' | ||
− | If the field number value ends with the specified Ending with | + | '''If the field number value ends with the specified Ending with parameter, the field number value is replaced by the string in the Change for parameter.''' |
− | + | | |
'''Parameters''' | '''Parameters''' | ||
− | + | <ol start="2"> | |
− | + | <li> | |
− | + | '''Ending with: the pattern to be matched.''' | |
− | + | </li> | |
− | + | <li> | |
+ | '''Change for: the value to be exchanged if the Ending with parameter is matched.''' | ||
+ | </li> | ||
+ | </ol> | ||
+ | <br/> | ||
'''Replace''' | '''Replace''' | ||
− | Returns a new string resulting from replacing all occurrences of Pattern to be matched parameter in the field number value with Pattern to be used parameter. | + | '''Returns a new string resulting from replacing all occurrences of Pattern to be matched parameter in the field number value with Pattern to be used parameter.''' |
− | + | | |
'''Parameters''' | '''Parameters''' | ||
− | + | # | |
+ | '''Pattern to be matched: the string to be found in the field number returned.''' | ||
− | + | # | |
+ | '''Pattern to be used: the string to be replaced by the pattern found in the field number.''' | ||
+ | | ||
'''Between''' | '''Between''' | ||
− | Returns a substring that is in between the Initial character parameter and the End character. | + | '''Returns a substring that is in between the Initial character parameter and the End character.''' |
+ | | ||
+ | '''Parameters''' | ||
− | ''' | + | * |
+ | '''Initial character: the initial character to be matched.''' | ||
− | *''' | + | * |
− | + | '''End character: the end character to be matched.''' | |
+ | | ||
'''No Ends With''' | '''No Ends With''' | ||
− | If the field number value does not end with the specified No ending with | + | '''If the field number value does not end with the specified No ending with a parameter, the field number value is exchanged by the string in the Change for the parameter.''' |
+ | | ||
+ | '''Parameters''' | ||
− | ''' | + | * |
+ | '''No ending with: the pattern to be matched.''' | ||
− | * | + | * |
− | + | '''Change for: the value to be replaced if the Ending with parameter is matched.''' | |
+ | | ||
'''Equals''' | '''Equals''' | ||
− | If the field number matches the specified If equals parameter, the field number value is replaced by the string in the Change for the parameter. | + | '''If the field number matches the specified If equals parameter, the field number value is replaced by the string in the Change for the parameter.''' |
− | + | | |
'''Parameters''' | '''Parameters''' | ||
− | + | # | |
− | + | '''If equals: the pattern to be matched.''' | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | # | |
+ | '''Change for: the value to be replaced if the If equals parameter is matched.''' | ||
− | | + | <br/> <ol start="6"> |
+ | <li> | ||
+ | = '''Appendix D – Examples''' = | ||
+ | </li> | ||
+ | </ol> | ||
+ | <ol start="6"> | ||
+ | <li> | ||
+ | == '''How to create a block/element for containers''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''See a full example using an existing label on how to create a block / element for a Container:''' | ||
+ | | ||
+ | '''Figure 46: Container Sample Label''' | ||
− | + | '''https://lh6.googleusercontent.com/mDsp7PKBk5DmHArphn_ssnRIMXJ50fAGKg2y_-iklvtcGsgEeqSjjtgAXIdA4zjnKG4n6t-DoUOZaUsffExk2jwz-2ExhcwTFKDyRN1zxYr43jc2sZH8Pb7poSYpyi4p4rZOafhwdXvU_WeZTFL2k-1vWcQXm3s9S9HbPRnFPrYpePEGEO3g68Hm''' | |
+ | <br/> | ||
+ | '''Figure 47: Container Sample Element''' | ||
− | + | '''https://lh5.googleusercontent.com/shu8kraS57Hl6psBZOIT9evaVTE-D3TZgjlpCiulyNQUPjRPL-BWo8spf4-vxzh3Lq7DtF-6ldmCq7L3EM3BfMmg3DQ2aQZbBGIFx-RsaPohhqslMeymX5WAGJ7aPEmIQM-0r_As6DqHCF5MGQX8cKGoQh-NWVVdaciOBPws0-rMwZ9Cv8iEhdQg''' | |
+ | <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> | ||
+ | '''Figure 48: Container Sample Label Mapping''' | ||
− | + | '''https://lh4.googleusercontent.com/KxM3_O33fI3Z3z2Lya4DMs9ciyP-bKobhKJIBu8_w3D5plyiPr6x4j35IOfE1fsS4e11VpWVly6ZT4WL4yrIP1IJHSrFoc3lck-v12g3BUD0FINbs9g01ze6FYLJan2z4kexwwB7Qwt7ALSWOmoP9QT2HBNoWmxMS4CCOTtWstpxJrN9JHbevZSU''' | |
− | + | <ol start="6"> | |
− | + | <li> | |
− | + | == '''Parallel Containers - Values Other than Just Serial Numbers'''<br/> == | |
− | + | </li> | |
− | + | </ol> | |
− | |||
− | |||
− | |||
− | |||
− | |||
+ | <br/> '''Often users will need a container label that contains the list of enclosed units / serial numbers as well as some other attribute(s) associated with each unit. For lack of a better name, Parallel Containers.<br/> <br/> The below explanation will help ensure the container label extracts the correct data, and prints it in the correct order.''' | ||
+ | <ol start="6"> | ||
+ | <li> | ||
+ | === '''Naming Template Fields''' === | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''When users work with Parallel Containers, it is very important to correctly name the template fields so that multiple containers are populated in the same order on the label.''' | ||
+ | | ||
+ | '''Below, you will see examples of good naming strategy:''' | ||
+ | | ||
'''sn_01, sn_02, sn_03, …sn_##''' | '''sn_01, sn_02, sn_03, …sn_##''' | ||
− | + | | |
'''mac_01, mac_02, mac_03, ...mac_## ''' | '''mac_01, mac_02, mac_03, ...mac_## ''' | ||
− | + | | |
'''comp_01, comp_02, comp_03, ...comp_##''' | '''comp_01, comp_02, comp_03, ...comp_##''' | ||
+ | | ||
+ | '''Note: In case there were more than 100 units listed on a single page of a container label, use three digits instead of two digits.''' | ||
+ | <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> | ||
+ | '''Figure 49: Sample Label with Good Naming Strategy''' | ||
+ | | ||
+ | '''https://lh4.googleusercontent.com/Xg2TMwdSvCofAtc5DWwoPg1Pnzzx8qmrTGaWmyR9PmXAprxTQsmm51VFzllk1C-rkH7qLQmldiF7nt3jQJaPfdNxbiigGA50JGpcTAvSQaOEkL3E2bzM2tKjoJOpOMTaz17FL8HYXiG_IyMx51vUDuOYqhPNiNXA8IsS2dxYMgF6gmNpLkm4j2Vp''' | ||
+ | <ol start="6"> | ||
+ | <li> | ||
+ | == '''Container Element & Block Formulation''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''When working with container labels, selecting the checkbox Values Will Be Assigned To Multiple Different Fields (Container) changes the scope of the data that is being extracted. Instead of the scope being the "container serial", the scope becomes the serial of each item in the container. The entry value will be the container serial number, but the value extracted will be the value for each item in the container. <br/> <br/> Figure 54 demonstrates how to extract the child serial numbers, the entry is the container serial number and the output would be serial.serial_number. '''<br/> | ||
− | + | <br/> | |
− | + | <br/> <br/> <br/> | |
− | + | '''Figure 50: Extracting Child Serial Numbers''' | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | | ||
− | |||
− | |||
− | |||
− | |||
− | | + | '''https://lh6.googleusercontent.com/LSbsao48PjEeIoU91bAmocnsIja9pfCNOJt8aVE0B9kRtfIJlmV2W3Hcm3-jxyK93GLzuWXebDGrlZe4y6FNUa_o0JbYQf2fa4dr7LZDHuJCpmGUtfkaeM4ftUL2HJ7T6wG4avTw-E_hXvJhxKMQdkm7CJsY61EXMZJdAwyX818aJhKR-7j0WHyl''' |
+ | | ||
+ | '''Figure 51 demonstrates the extraction of the mac addresses that were captured as components, using a reference designator of MAC_Address.''' | ||
+ | <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> | ||
+ | '''Figure 51: Extraction of the Mac Addresses''' | ||
− | '''Figure | + | '''https://lh6.googleusercontent.com/UOqVMUPE7g61xGbqP8p4WABrbB_jcPRkZ9F2sefWNcpMnME4-IOpKG8swOaRvYQ6C5UqrbzuTGwZFgxwMYcbhgUIjfe4z4NWetx9jmYiHOtCk75U5XAiL4VTeYr6AfVz3hS4q9POiYhKRLs_eM_pZ-Ez3NyRYVi-8BEGP9If5DAcRkLTTb5gjau1''' |
+ | <br/> <ol start="6"> | ||
+ | <li> | ||
+ | == '''Container Element Mapping''' == | ||
+ | </li> | ||
+ | </ol> | ||
+ | | ||
+ | '''Container mappings will be many template fields to a single Container Element. Multi-select the placeholder names (left side) and select the container element (right side) and click the Map button as in Figure 56.'''<br/> | ||
+ | | ||
+ | '''Figure 52: Label Mapping''' | ||
− | ''' | + | '''https://lh3.googleusercontent.com/q7NKs_JJsnoApOlXwXVFtSh5ZmMJhsPaX9a2gNZ2B-sioFrKat8D2xW5yGsMIK1_w-71eCewr7aLxT2HbqLmUlhRdqscfcKbKroI5RDWjD5SlvM3Aek71YbBy8Wt3Is5C5aKDtLKsfrJM1jyvaweEVeAtLWkRdyupY5f4nv2uJrgfXzrDQz2GrRT''' |
+ | | ||
+ | '''When users follow the previous steps and print labels, they will see labels similar to the image Figure 57.''' | ||
+ | | ||
+ | '''Figure 53: Resulting Label''' | ||
− | + | '''https://lh3.googleusercontent.com/eOdFRKQdejqpYY4-gR2YkvcKsEHcP77dldJ4nqujKL5KvTig9FvfUlakeqZPBCTavpcNQ8loIM446I4RdaAc0Y4FbcdCdK6o0Oi751nYHiFxQnPJPHDPSZ5tvgGFCl5PdJlZOigfgjIuY1LuWi-4tJMoZ7ov_exu9T_bK95aSaiB-485tmrJmUGp''' | |
− | + | <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> <br/> | |
− | + | = = | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |
Revision as of 16:54, 17 October 2022
Production
Label Engine Labels
Version MES15.75
Revision H1
Table of Contents
Label Engine Labels
How to create a block/element for containers
Parallel Containers - Values Other than Just Serial Numbers
Container Element & Block Formulation
Contents
- 1 Introduction
- 1.1 LE Labels https://lh6.googleusercontent.com/9WcVP8b1Gf9Pf0xreH8VkQpUw4aExuYZVXOigUo9trICy7XB1L036Y1xe3M0CAH6S15uUcL09DMXwREmPqG5jC-8sHiQRX5PiGyG82Lp9P7MrRdSeQaFTo34CwCRibwaVdrCeKtkZD1GP5e-2Ds7BnKmuRGpwaQUoOx_sDjovQXUROhjpMg-JPT7lQ
- 1.2 Upload Files Tab
- 1.3 Element Creation Tab
- 1.4 Label Printing
- 1.5 New Version
- 1.6 Edit Label
- 1.7 View Label
- 1.8 Add/Remove PN
- 1.9 Copy Label
- 1.10 Delete Label
- 1.11 Hide/Unhide Label
- 1.12 Publish Label
- 1.13 View Label Sample
- 2 LE Reports
- 2.1 LE Version History https://lh6.googleusercontent.com/dzJ4fqviRUcJpF7Ix41pAHtPi1AsV9UWBO8HkgD3od0WpKWKDE_j5Wt-4x0Bsput536_qntbdWwgNkkvu2R3ZpKr3isOoJwPCjDBBtWkD9AOwoqLmIU1fdMMr5IrBbtet9vdMtmxE0Cfoicq8gRALlJehuAHnGTxnypJdqqmGjA-MKlSpT-I3trfEw
- 2.2 LE Print History https://lh3.googleusercontent.com/s8oqml7NY3s27LtMTMAMxEncJToCDSnjK_QYsqTNjEd5UCm3H8wKPu6YWyAmNzyZwe96kzsXyd_ZLaXTSfj8q79JRu64NdfLlW9E1VCAEKBe5_WI0-SeRDPEa4XVpQTXrxgyrcG6VQk814BU8WSTAhhoXBJWHGKtWpCRzO67SffoCu1AP8J0dXDjIw
- 2.3 LE Statistics https://lh5.googleusercontent.com/eee_YRC6eG6tRoUhZ8WS7j3dZ8BSE3NcFxq0gmz-Qu3vu8HktSAdyC2vgbp4sSIVbZ0tv0gtSrS3fFGuj9cs5qi2XHWL2uIEIRIz23S-ftr4AltN4DSDM5MaEQkD-yrKNVsdWKM6wIhNj3wOlX5o2bQUOvvtgIJlNz4uWaNJpT48kW4kc7TF-MXtTw
- 3 Appendix A – Key Terms
- 4 Appendix B – File Types
- 5 Appendix C – Business Rules
- 6 Appendix D – Examples
- 7
Introduction
Label Engine Labels is a web application that gives plants the ability to create, update, and print labels without the need for IT resources. It enables plants to easily define and access various different data sources like MES, and MESR, along with a variety of other database types. It allows users to map label fields to these data sources in order to create dynamic labels. It also enables plants to extract statistical information about the labels that are managed in Label Engine, as well as monitor the audit information.
Users can create a label template or layout in the design tool (i.e.: For ZPL use BarOne or CodeSoft, and for RTF use Microsoft Office or another tool that provides RTF format.) of their choice. Using the design tool, they export the completed template as ZPL (Zebra Printer Language) or RTF (Rich Text Format). The template is uploaded to Label Engine and the fields in the template are mapped to data sources. At print time, Label Engine combines the template with the appropriate data to produce finished labels.
The Label Engine Labels portlet allows the user to create, edit, copy, delete, and print labels. LE Admin History, LE Version History, and LE Print History reports can be viewed and/or printed from this page. LE Statistics Excel spreadsheets can also be created from the LE Labels page.
To access the LE Labels application, navigate to Production > Label Engine Labels.
Figure 1: Accessing Label Engine Labels
https://lh3.googleusercontent.com/gnnR7jMh_oi1LR4kaIR_gWgoRbswzX0MdEB6SZpC2Iga4Bo4uyBGNe5gmBIeM3kEFrUAV0Ojm34fScVGzLf8VzQBtel_1ObEY6h63R0sYI1-SHujq8looVf_xQuNeZ0gP7GB_-ZUxH2EPpnhY2SL3jvZi1abdV62lWSsDxXQAi3B5jcu2-Asce1-kQ
Within the main screen of Label Engine View, the user will be able to see four different modules:
LE Labels, LE Version History, LE Print History, and LE Statistics.
LE Labels https://lh6.googleusercontent.com/9WcVP8b1Gf9Pf0xreH8VkQpUw4aExuYZVXOigUo9trICy7XB1L036Y1xe3M0CAH6S15uUcL09DMXwREmPqG5jC-8sHiQRX5PiGyG82Lp9P7MrRdSeQaFTo34CwCRibwaVdrCeKtkZD1GP5e-2Ds7BnKmuRGpwaQUoOx_sDjovQXUROhjpMg-JPT7lQ
To access the LE Labels, select the LE Labels from the Label Engine View menu.
Figure 2: Label Engine Labels Main Page
https://lh5.googleusercontent.com/Zft0Df4I9YELvigGiY6-ov0_F1QjxF9xxz-sD8ftTVmmhdbKLxgOWKYrFQ0AvZkPMMYcwwkwphalwZPNCwtJb7z9ACmLMRSb-t5PLTnMOMpSYfpiAGjN-yMTHBc1-TTPRH4nKroPhSUZ3wsyhG1GcnYbuSaMZl6tQJuqEefiIuw_dSLokwFRXpeRoUWd8BL9Jg The main screen of the LE Labels page contains all previously created labels. The labels are sorted by name and are color-coded according to their status. The following are the colors and their statuses:
Green=Production
Blue=Development
Red=Hidden
Brown=Deprecated
Label Template File
The first step of creating a label is done outside of the Label Engine. A label layout and design tool are used to create the label template such that the finished label meets the customer's specifications. Typically the label specifications will cover such things as label media type, size, fonts, barcodes, tolerances, etc. Many different design tools exist and the choice of design tools is outside the boundaries of Label Engine. A suitable design tool MUST be able to produce or export ZPL code (Zebra Programming Language) for use on Zebra Printers, or RTF (rich text format) for use on sheet / LaserJet printers. As such, printing labels through Label Engine are limited to supporting printers that support ZPL (i.e. Zebra printers) or RTF (i.e. LaserJet printers). Label Engine’s main purpose is to provide a means of populating placeholder fields in labels. Label Engine keys in on values surrounded by $ (for example $partno$) to determine which label elements are mappable within the Label Engine. At print time, these placeholders are replaced with real data by Label Engine before sending the label to the printer. Not all design software or barcode formats will allow the use of the $ character, and in such cases manually editing/cleaning the ZPL might be necessary. The ZPL or RTF file(s) are uploaded to Label Engine as part of the label creation process.
-
Add New Label
To create a new label, select Add from the LE Labels main page. Figure 3: Add New Label
https://lh4.googleusercontent.com/1svuJMqLIhb_h9-f7FtB2v3VtOkW9y2RGFgthxW2cll78qNpjysHeN8mvYgLA_chNKWEHf524G5cX8qFRwcmF8cjpUCzH9wj14NUCECXy3Hk4jnv-k3ZySM5mt0iVlE9CXVGOlMx-VP7DqgiVOUD1iBaBy1fClFnGvzurRx7cyIhJOGAdAGFqDTy1g Enter the label name and customer and save the Label. Label names can only contain lower case characters, digits, and - (dash) and _ (underscores) all other characters and disallowed. Label names can not be changed after the first publishing of a label and label names MUST be unique so choose your name wisely. Figure 4: Save Label
https://lh4.googleusercontent.com/NB6GYunp-O54twbTlvn4LG1iebFSWNK6AesKfDUxGiaprnHXtsEJjf2fOL3p7xounswOV3heYJH8Dn7NIO39iiEklfdH0y5d1M5jo8I4prCXo4eUUD0VsZ8uXoatoR1x_q6XKD94gSFLkVhI0z7soaujStWBZ4JfMnK3RvpRsdEs0JwP4DWaRa1L4g
A General Information screen will display. There are three tabs located to the right of the General Information form (Upload Files, Element Creation, and Label Mapping).
General Information Tab
The general information tab contains the same parameters that were on the initial creation screen so that these values can be updated. It also contains additional information in the database selection panel, and it contains additional controls to allow Parts to be associated with Labels. Figure 5: General Informationhttps://lh5.googleusercontent.com/EFCmPIa-CrewV22CbDp9ur7WeSRnR3CvnZ1m5TWagP33h_jeOQX9g_F8KbeCKBuk8ktqpylReEQKP43HwP4K0CjAmaJ8G229JTWVnWCpibnp4aSdFBqekfqqTB-ZDEuDuRx-FTL5rV8uFuDjMgYYeGF5fHATmBghWPDIRa3x_ohYyqmEW_DxcnenHQ
The user will need to enter the following information in the General Information form:
Name - the unique name for the label. Each label must have a unique name. Label names can only contain lowercase letters, numbers, and underscore and the name is limited to 30 characters. Spaces are not permitted. The name is the key to printing labels using external web services.
Version – Defines the current label version.
Size- Enter the size of the label.
Resolution – choose resolution based on the printer that will be used.
Customer – select a customer for the label from the drop-down list.
Kind of Material – Choose the material that the label will be printed: Kapton, paper, or polyester.
Comments - label comments for any additional information.
Duplicate Prevention - Use this to specify if the label should prevent printing this label more than once for any given "entry". This may be disabled due to administrative settings that are explained in the LE Admin SOP {put the link and proper name}
Default Database Mapping
By filling out the Default Database section it will allow the user to use the option Part Must be Mapped in the case the selected database is an MDS Database. Moreover, it will provide the user with an autocomplete part of the creation of an element. Once a database is selected, the Table and Column lists will become available. Using these drop-down lists, define which database element will be provided at print time. This is also referred to as the default "entry" value. Figure 6: Database Mapping
Part Number Mapping
Part number mapping allows the label to be associated with some Part Numbers. By having the Part Number informed in the Label Engine Print screen, it is very easy to find the label(s) that need to be printed by a Part Number. Depending on the Administrative configuration, Part Number mappings may be optional. Toggle the "Part Must Be Mapped" selection if the label should enforce part mapping at print time. If enabled and if the print time entry corresponds to a part that is NOT mapped to the label, the printing will be prevented. Note. This may be disabled due to administrative settings that are explained in the LE Admin SOP {put the link and proper name} Enter the Part Number in the Part field and select Add 'to add the part in the Part Number list. To delete parts, select it, and select Delete.
Figure 7: Part Number Mapping
https://lh6.googleusercontent.com/hdckCT7hTDYPffKRKvYmm8uIUdS3Jj79fJ-IvqISxfy5ALk1ejzGrc_Ktpt0C9Hm9PG99F3lrWcdeBG22DjU3ss31GL443x4TA3LaKtJbzludwvF1WxeGikZ-8GIEWJ58qWehPIq67ifWd4z_Go6BhqOZuXO5THnVVwOhYrd0viiq-qvco_iYFnF7g Once you have provided all of the information on the General Information tab, select Save to commit your changes to the system, and then select Next. The user can also select the Upload Files tab. Note: Clear functionality will remove any data provided so you can start fresh.
-
Upload Files Tab
The Upload Files tab allows the user to manage the files and links for the label. To be usable, a label must have a template file as this contains the layout and definition of the label. A label engine label can only contain a single template file. Label Engine's primary purpose is to collect, or generate, data and inject this data into the appropriate places within the template file and print the resulting complete label. Any "variable" data in a label template needs to be identified as a template field. Template fields are delimited by $ (dollar sign) characters. Label Engine identifies the template fields as the text between the $$, for example, $sn$ or $serial number$ or $serial_number$ would all be good template field identifiers as they are easy to understand what data is required. When a template file is added to a label, Label Engine searches through the template and identifies a distinct list of template fields. Label Engine allows the label designer to "map" data to the template fields. As there are different printer types, LE supports different template types. LE has support for the following template files:
ZPL (*.txt or *.zpl) are for use with printers supporting the Zebra Printing Language
RTF (*.rtf) are rich text format files, for use on sheet printers.
DPL (*.txt or *.dpl) are for use with printers supporting the Datamax Printing Language
EPL (*.txt or *.epl) are for use with printers supporting the Eltron Printing Language
Other Template Types (*.txt) is a catch-all that will allow you to upload any text-based printing language command file that the destination printer will support. Some examples would be J-Script (Brady Printers), IPL (Intermec), etc.
Many different label design tools exist and the creation of the printer-specific template file is outside the scope of Label Engine. LE simply requires a text file containing identifiable template fields. Template files are typically printer-specific command files. The exception to this is RTF. RTF files are converted to PDF files which can be printed on most sheet/laser printers. Tip: It is possible to put multiple labels within a single template file. The other supported "files" that can be uploaded are:
Label Image Sample (*.jpg, *.jpeg, *.gif, *.png) are to include a static image of a sample label. A label will only allow you to include one image sample.
Font (*.fnt) are fonts that are required on your label. Fonts only apply to ZPL labels.
The list of existing fonts will be displayed from which you can reference the one(s) your label needs.. If you need a font that has not yet been uploaded, you will be able to upload a new one. You can upload or link as many Font files as are needed for your label.
URLs are not actually uploaded and they don't have any content within LE. URL is so you can reference information about the specs of the label, or anything else you feel warrants adding a reference to. Basically, this is to allow LE to be the place you manage your label.
Figure 8: Upload Files
Most files will be uploaded from the user’s local computer. However, if the font was already uploaded to the server for use in a different label it will be possible to reference the existing font instead of uploading it again.
Add File
To add a file to the label from your local computer, select Add from the Upload Files tab. Figure 9: Add File
Select Browse to browse and select the file to add to the label.
Add a description of the file.
Select Save to confirm the addition, Reset to clear the fields, or Cancel to cancel.
-
Edit File
For labels with files attached, the files can be edited as long as the label has not yet been published.
To edit a file, select the checkbox to the left of the file and then select Edit.
Figure 10: Edit File
- Once the Edit button is selected, the Edit Files Uploaded pop-up displays to edit.
- Only the Description portion of the file is available to edit.
- Change the description and then select OK to save changes or Cancel to exit.
-
Delete File
To delete a file attached to a label, select the checkbox to the left of the file name and select Delete.
Figure 11: Delete File
- A confirm box will display. Select Yes to confirm or No to exit.
-
Download File
Under the Upload files tab, the user can download the files attached to a label to retain the information from the label.
To download the file, select the checkbox to the left of the file name and select Download.
Figure 12: Download File
- The download will be started automatically.
-
View Label Sample
The user can view a sample of the file that is attached to the label from the Upload Label tab.
To preview a sample of the file, select the checkbox to the left of the file name, and select View Label Sample.
Figure 13: View Label Sample
- A sample of the file is displayed on a new screen.
-
Element Creation Tab
The element creation tab is where users will create the "elements" of data that will be injected into the template at the print time via label mapping.
Figure 14: Element Creation Tab
https://lh3.googleusercontent.com/wUairfmG2IkRMpLFoxmF2KLdOwBwfUiUi33DUV0Sutpl4hTFIlmkoz_JQ5fQ0I9yImC4qOc-RZMzTvoZWrY2veqIuJVp7hgtNFLJKooNZxSV4DBgpKf8cUjaWw3w8pIJKrqlFRTIeN4X7qWHsI4p4nlkiQzKvAUncqtx7D6xEwgo8VMX0G1OsIOggg
On this tab, the user can create the elements. Elements are built up of 'blocks' of data, and elements are what is ultimately injected into the template file at a print time replacing the $place_holder$ fields.
The application provides five functionalities (Constant Value, Date/Time, Database, Custom function, and Entry Value Block), from which the user is able to customize the elements.
Add Element
To add an element, in the Element Creation tab, select the Add Element button.
Figure 15: Element Editor
The Element Editor is displayed and the user can input the necessary information to the new element. Fill in the available fields:
Element Name: the name of the element;
Comments: any necessary information that the user wants;
Mandatory is a flag indicating that a non blank/non null value is required at print time. If the element value is empty at print time, the printing of the label is aborted and a message about the failure is recorded in the audit log and is reported back to the user. The default message contains a reference back to the element name. The element name is not always something that has meaning to an operator. To provide a more meaningful message (for the audit and the user response) LE allows the user to provide a mandatory custom message that will be used instead. When Mandatory is selected, an optional field, Custom Mandatory Message becomes available and this is where the label designer can provide the message to be used if a mandatory violation occurs.
Note: This Mandatory flag will be available at some of the functionalities and will be used for the same purpose.
Figure 16: Element Editor - Selecting Mandatory
https://lh5.googleusercontent.com/7VUFO0owF5yMsI35lQb2h9L9V-CcbUiLtLRf1Fkpq_pEDI0fkU0pUmPfygGmGY6C3mC_0sBW3R6Q_CyG-Y3gBicTGw8T2Ezfpa6-ZoOhlfd-DXR8gsxXP9wchCEcG1jl17SDU4AG6HiEklPZWvmlsUp4QIUIXv5rJ4YemVnxNmADchJcMaNk_PCj1Q Checking the Entry Point checkbox, it will be allowed to search values from two databases. It is used to set the database priority. The available functionalities are described below:
Constant Value
Figure 17: Constant Value
https://lh4.googleusercontent.com/95LeedPpy5nmxw9MHP2Qw13mQHmzEWmh8FyPLnAu2gs0Xo3SCX_iCnLrw6bSh92zknTBSCHKCTbk2pDOqaBQAg8pVbleAZM-CbR3wQE_LsqeLJoV0uJtzvALAYg0IKSUw_lGk8-v8ooqrPvv3ymmUyl3gtsCBRfulBxRQzPCMsFEq684C38cwwZSmg
This functionality allows the user to create a constant value (fixed value) used for printing the value in the label.
Block Name: this is the block title to be created;
Value: Value to be printed in the label (any value type).
Click on OK to finish.
Date/Time
This functionality will print the date and the time in the label. Figure 18: Date/Time
https://lh3.googleusercontent.com/KZgRIiDfu5SGQRkQZLPWBLnvLi5IpKhb5j06gPzw6g6Ou7IQUbUpRhHmHcGXatE3_unm18dkG9fq2wm6h0UgHLLpdVVTvXb1iRn12A_15Spxou4l9CrT9zcrfOd9X55vMOLMRojwVbpyJv_ZjXM0KqZKdAeVmzAV-wUdE1IgtCBLSy0MzzWpykzxxg Block Name: Name of the block to be created;
Date/Time format: Select the format (from the available list) that will be printed in the label. Figure 19: Date/Time Format
https://lh5.googleusercontent.com/jp78G-9E-UBaYbzFHEDrzYEMoHZ_h3aFXxRqndqdkQTl1kn-hvSBROz48Rg7E8_z3vPKQVfbiu1SOJuP7sI8PW5RJ7yzV1QWUgXiz1_bEy41OOMRfyIpu07_ZJRbpPmAUawZSMOKkql6NFxk5ks2tdDmkGv1fBbwwjUVcQRuUhbTCajflAgqlOZYcw Block Modification Rules: It allows the user to set the rules to the selected field (date/time)
Figure 20: Add Rule
https://lh5.googleusercontent.com/HA-WXx33-W15N58wADu5PqHa3s8QvBxh55nmVe6b5eJFU7keTSiaD88fvsmitF1cu6u88F_PopeppNeOXRtGUayxufM9evqbGx3n9jwviUzYe3U5iqL0jjoj5YLPxROf-ZO_yNABIFsn5afKSaHqeOgrzo9j53EOeBRUC3g-SkZCPTPjjUAN1Dk4aQ
The rules can be used to set or modify previously assigned label fields. Dynamic data, such as system date or time, can be formatted and assigned to a label field. Rules allow for data to be combined or transformed based on runtime conditions.
It displays the details of the business rules assigned to the selected label field in the Rules list.
Multiple business rules can be applied to any field. To add business rules to a field, follow these steps:
To add a rule, select an existing rule from the list and click on the Add button. The new rule will be added to the list.
The order in which business rules are applied can be changed using the arrows in the lower section of the details section. As well, business rules can be deleted or updated using the appropriate action icons.
Database
This function loads the database information that will be printed on the label. Figure 21: Database
https://lh6.googleusercontent.com/IqJuYplA6zb70Y2ZCeTjRyGvQxrTpBS1B67gUIbFMoKcBdMaboZg0B_ehuTDvs0NRFVAECVh13BqvRvTBIcQsupCnBEIx5crYLQfSm36M3FCwaLCxvYFcAxdPYql-I7hYHqXwaWeimhYEPf5bEzhTolgNiUsa_4DaYSAS6Fa_AysMdFpLHHMyj8bWw Entry Value From: This form informs where the input for the element comes from. The common value is Print Call Entry.
Print Call Entry: comes from the value used to print the label;
Element Name/Key: comes from the element;
Block Name/Key: comes from the block.
The Entry Point Definition form displays the predefined values in the General Information. Value To Extract: The user needs to select the Table and the Column to get the information to be printed on the label. To provide a more meaningful message (for the audit and the user response) LE allows the user to provide a custom mandatory message that will be used instead. When the Mandatory checkbox is selected, an optional field, Custom Mandatory Message becomes available and this is where the label designer can provide the message to be used if a mandatory violation occurs. Note: If the label is a Container Label, the user needs to select the Values Will Be Assigned To Different Fields option. Figure 22: Container Label Option
https://lh4.googleusercontent.com/0SaOY3QD27oDcDHlFwZCWro2xA8n8Nys6B_pa5PEU3AVBygvr1JikoyyPoC72y6uSmEoxhiJKu_fg2NHLTizrl-5XV29VR0zXed_xQrCoDxbilAMjyW9kVuVwMt0PcU_5jMG4eJ-HJmKUuUFXeH1qCZNamfIXSCS6zooyW-5438M0phFbupky96mrA The Block Modification Rule was already explained in the Date/Time topic.
See Appendix D – Examples for more information.
Custom Function
The Custom Function allows fetching database information through a customized function.
Figure 23: Custom Function
https://lh5.googleusercontent.com/ZGngzHS4MH1U9ynB9QGyC2l5Q__lGdSRSbIcZTWQttV-53v1LEoiEAdTmV64-VADyM54yyaQaA6e_b3F55-qQ6FPDWBUoMsf8sV9XjvbwMS155Ie60mnWwCJuGc5bpCP0u5ZuERbXc-h3OYvr6AQkRbvYl8Hwjsj8ueZSqJGQpOAaj55Rr9isA93MQ Entry Value From: This form informs were the input for the element comes from. The common value is Print Call Entry. To provide a more meaningful message (for the audit and the user response) LE allows the user to provide a custom mandatory message that will be used instead. When a Mandatory checkbox is selected, an optional field, Custom Mandatory Message becomes available and this is where the label designer can provide the message to be used if a mandatory violation occurs.
Print Call Entry: comes from the value used to print the label;
Element Name/Key: comes from the element;
Block Name/Key: comes from the block.
Database: after the database is selected, the functions are displayed in the list and the user can select them and inform the Function Details.
Entry Value Block
This functionality gets the entry information used to print the label (generally, the Serial Number).
Figure 24: Entry Value Block
https://lh5.googleusercontent.com/UVjp_lp0149QQrvc-Ygv18f7ulJDH5DQUXeNFwoKzwsBnyyvitFX4YKijx65Qw3Ctwwiid8Tge7GbrORTlae7NMu8oHEj_LWx7xE6j9zdBZ5QWkctW83u9uEhksU40ZuPlJju7KW4BbaaTGXC4Q8xwtiZJnjs3Up0y-ph6FcMagYI3XE4uTQY4m2wg
Click on Save to finish.
Delete Entry Value
Figure 25: Delete Entry Value
https://lh6.googleusercontent.com/SOUb6x2VBXEUJT4vnTiOC5WcrLchN0sU8sCdUWavcmGtg8moVPQ7yeAVssTsClONBFk14TDnCIDaPit4tD8t6pQGyniaLSS4IbQgFV1soxemdHvwpfjOkdEQi9jVWDy94CgntRKx1DYfIoyvm5Bl3OoYDIREU9dsu8SHVyeNl8g3RxQkSrdXmlRPOw To delete, just select the Entry Value Block in the list and select Delete. A confirmation message is displayed, select Yes to delete or No to abort.
-
Edit Element
Editing elements work pretty similarly to Add Element. Refer to Add Element topic for further information. Figure 26: Edit Element
https://lh3.googleusercontent.com/y4uLuwDmw-ZnzkH5jN0_nQuyX52nbrOnyej_jnNbU7aIf-XjEYvUxk9ftrlQSPPhmo_mEskHLTOgd4WL4J20pnng5TGYzXOrj5AJRnZQv5cUf1cQDr8l4VTGcOlOe3scus9JSpj7wSgov3lJqAbJLFWMBDN6svMDQWOpmWuPvAyOojeuydwgZN6ajA Editing elements work pretty similar to Add Elements. Refer to Add Element topic for further information.
-
Delete Element
To delete, just select the Element Name in the list and select Delete.
Figure 27: Delete Element
https://lh3.googleusercontent.com/jMIVcTAiKIEqKlfemqEuCJ8fsaU8THaTVfzl6K_ti9o35DT9TO_RUPw5NQvuQ1lnYVQYWqGgd9ZPl21NNbSsJmAJ8i3eNCSqpGUVd3YIjvJBth_dPuvAzeWJuRAut7k8oknnAXkcN7V28JpuygdMJxNRYvhK9CQKFJjQEeA4WCmL0uAiVfpFJ70l7Q A confirmation message is displayed, select Yes to delete or No to abort.
-
View Element
This functionality allows the user to view how the element was created.
It is not allowed to do any updates on this page. Figure 28: View Elements
-
Label Printing
One of the major features provided by Label Engine is printing labels. Users can print labels to any available printer.
This page changes based on the settings for duplicate prevention if the entry has been printed before. Figure 29: Print Label
https://lh3.googleusercontent.com/0jHL2XhovOfaIjsluLNOsmPFkmaAGuS7izwjI1YJYAkLORWdLdH0KO1pf8tamKEISYgnljoYjvAfh1LmuWmHaUpnxzN51aCLHXzF3uUsA9wifVerAkBNAj3-ZqENdhH4e3tfT7p47VlY-nDKm6MElk19D4yTZNQVdCsfNt-Z2XDoijhMfmntNapt Figure 30: Print Label Options
Select the box to the left of the Label Name on the main Label Engine page.
Select the printer icon on the far right of the screen.
Choose a Printer.
Enter the information used to print the label into the Entry field and select Print.
View Raw Data: The user can get the raw content that will be sent to the printer. Local Print (download): This option allows the user to download the print result locally as a PDF or ZPL. Test Print: Duplicate prevention and Test printing. If the label (and the plant configuration) has duplicate prevention turned on after the Entry field loses focus, the print history is checked. If the label-entry combination has been printed, viewed, or downloaded before it can't be printed again. It can only be reprinted (as many times as needed). In order to perform a reprint (if the user has permission to reprint) the three fields (Reprint Reason, Approver, and Notes) need to be filled before the reprint options become available. Local Test Print (Download): Test Print / Local Test Print are always allowed. This feature still requires a valid entry, however, the print activity does not use up the one label entry allowed. It is still recorded and viewable from the audit, but it is recorded as a test print. Also, all of the elements have their value reversed before being injected into the template so, in fact, the generated label is significantly different from a regular print. Note: This section also discusses web service printing. The new LE web service is documented with Swagger (which allows the user to describe the structure of your APIs so that machines can read them. See the details at http://p99ls9.sanmina.com:8081/lbleng-webservice/index.html. In addition, Label Engine has web services that expose printing functionality to other applications. For example, it is possible to print labels created in the Label Engine by using the SFDC Commands (!! Commands): !!1LABENG.<labelname>.<print queue> where <labelname> is the exact name of the label in Label Engine, and <print queue> is the exact name of the print queue defined in Label Engine.
-
New Version
To create a new version of a label, select the box to the left of a Production, Hidden or Deprecated label then select New Version.
Note: Labels in Development cannot have New Versions created. Figure 31: New Version
- The General Information form will be displayed. All fields are available to edit to create a New Version of the label.
- Select Save.
-
Edit Label
To edit a label, select the box to the left of a label in Development.
Note: Only labels in Development are available to edit.
Figure 32: Edit Label
- The General Information form will be displayed. All fields are available to edit.
- The Upload Files, Element Creation, and Label Mapping tabs are also available to edit.
- Select Save to confirm changes.
-
View Label
View functionality is very convenient to view how the label was created in case the user does not have permission to edit.
To view a label, select the box to the left of a label in production.
Select View.
Figure 33: View Label
- All tabs will be displayed.
- The label information is available to view only.
-
Add/Remove PN
This functionality allows the users to add or remove Part Numbers associated with the label.
To add or delete a Part Number from a label, select the box to the left of a label.
Figure 34: Add/Remove Part Number
Figure 35: Part Number Mapping
- Enter the part number and select Add.
- Select Add to confirm or Close to cancel.
Figure 36: Delete Part Number
To delete a part number, select the box to the left of the part number and select Delete.
A Confirm screen will display. Select Yes to confirm deletion or No to cancel.
-
Copy Label
To copy a label, select any label from the Labels list and then select Copy.
Figure 37: Copy Label
- All tabs forms will be displayed. Apply the necessary changes and then, select Save at the bottom right of the screen to save the changes.
-
Delete Label
To delete a label, select the box to the left of a label in development.
Note: Only labels in development status can be deleted.
- Select Delete.
Figure 38: Delete Label
- A confirmation message will be displayed. Select Yes to confirm deletion or No to cancel.
-
Hide/Unhide Label
Certain labels can be hidden from the list of available labels using the hide function. Labels that are currently hidden can be revealed using the unhide function. Hide a production label, prevents the label to be printed by using SFDC Commands or any other print action from an external application, such as Shop Order Print module, SIT, and others.
To hide a label, select the box to the left of a label in production and select Hide.
Figure 39: Hide Label
https://lh5.googleusercontent.com/4A2kd0CLZKwZqd2EGeP23c3YxbBqc6tAodLfuJbuM8BDok5otu_y0OXdRpEcmd5tgjsm9kZpo55-TiYnELONiYhyrUaprf-sKJLDced-nC4mDBKRBbZQS7kHZU0NFWON8_KNrnTDS3dgi4JeAPLITETmNlT_uShLbGtqMr2goPNeQQFeUTAE0bHroQ
Note: Only labels in production can be hidden.
Unhide the label restores a previously hidden production label and it can be printed using SFDC Commands or other external applications.
- To unhide a hidden label, select the box to the left of a hidden label and select Unhide.
Figure 40: Unhide Label
-
Publish Label
Publishing a development Label locks the label and makes it available for printing from other applications.
To publish a label, select the box to the left of a label in development status, then select Publish.
Note: Only labels in development can be published. Figure 41: Publish Label
- A confirmation message will be displayed. Select Yes to confirm or No to cancel.
-
View Label Sample
The user can preview a sample of certain labels using the View Label Sample function.
To preview a sample of a label, select the box to the left of a label in Production/Development.
Note: Only certain labels have previews attached to them. The only way to know which labels have previews is by selecting each one and looking for the Label Sample Preview functionality to become available.
Figure 42: Label Sample Preview
-
LE Reports
The available reports allow the user to mine the logs to extract usage data. There are three report options:
LE Version History
LE Print History
LE Statistics
Select LE Version History, LE Print History, or LE Statistics.
LE Version History https://lh6.googleusercontent.com/dzJ4fqviRUcJpF7Ix41pAHtPi1AsV9UWBO8HkgD3od0WpKWKDE_j5Wt-4x0Bsput536_qntbdWwgNkkvu2R3ZpKr3isOoJwPCjDBBtWkD9AOwoqLmIU1fdMMr5IrBbtet9vdMtmxE0Cfoicq8gRALlJehuAHnGTxnypJdqqmGjA-MKlSpT-I3trfEw
To access the LE Version History, select the LE Version History from the Label Engine View menu.
Figure 43: LE Version History Page
Set the filters as needed.
Select Filter to extract the data.
The results of the query will be displayed in the List.
This report displays the history of the label: who created it, when, its version, and its status.
To access the LE Print History, select the LE Print History from the Label Engine View menu.
Figure 44: LE Print History Page
https://lh4.googleusercontent.com/5yyB0eJmRJiVuta_D9twSKu8EK_RaLsAbdmWVOwSLrlkG1i4_1iTIWuDPADvJPrO3I2mtt6LWomtWqTEvyUOIFYARjV4zITP9YAsmAlHGns4gRo74k9NWoBcC8xlABgfL4BNvjX4G3EHqJ7tUEV8pgMcsdfKYNNow4zmUzDmrZofUJRPnfdquNE3rw This report displays when the labels were printed, which system or Web Service method invokes the print action, which entry value (e.g. Serial Number) was used to print the label, and other information related to the print action.
To access LE Statistics, select it from the Label Engine View menu.
Figure 45: LE Statistics Page
To extract statistical information, select LE Statistics.
- Select the begin and end dates using the date selectors to define the time range for the statistics that will be generated and the Statistic Type:
Print Activities
Created Revisions
Created Labels
- Select Filter.
- The results will be displayed in the Name column.
The user is able to save the report locally by clicking Export.
-
Appendix A – Key Terms
C
Column
The columns are parameters present in tables. A column has a type and can represent a data type like an integer, date, or string or can be a link to another table being used on relationships. Columns are often referred to as database fields. Customer
A customer of 42Q will be related with a label. D
Database
Database that the label engine can be connected to retrieve data. The main parameters are described below.
Name: The name of the database, this is the name to be used on the connection.
Type: The type of the database: PostgreSQL, ERP, MySQL, SQLServer or Progress.
Address: The address of the server where the database is running.
Port: The port on the database server that is accepting connections.
Schema: The schema is a namespace into the database that stores data in separated logical structures into the same database. PostgreSQL and ERP can use this kind of feature.
F
Field Number
Field numbers are all fields that can be replaced or used with the result of a query or input data. Each field number must be related with a format file. Format File
Format files are the templates where the field numbers are associated. L
Label
Labels are the representation of all files, data and rules that are used to build a structure for printing a label. P
Plant
Plants are each local 42Q factory. Printer
The printer is present on a plant. These printers are installed on a print queue of the server that is running the label engine application.
Print Queue name of the installed print queue of the server
Address the IP or name address of the server that is running the label engine
Port the port that the label engine is running on the server
Project
The projects are structures related to Progress databases. In this sense, each project must have one database associated with it. A project identifies what MDS will be used on the connection with the database to retrieve data.
Q
Query
Query is the entity used to represent how data can be retrieved from a database. A query can return values of one or more columns based on the relationships among a set of tables that can be configured by the user. T
Table
The tables are the data structure present in databases. This table contains a set of columns and can be used to create queries. U
User
The users of the Label Engine. V
Variable
Variables are used as parameters of the business rules and are similar to field numbers; they have a query associated with them, so the result of the query will be the data inserted on the parameters.
-
Appendix B – File Types
Format File
A format file keeps all the structure information to print an entire label or part of it. A label is composed of one or more format files. The system contains two types of format files:
User Format File: A file that doesn't contain an identifier. This file is represented by the icon User format file icon in the upload file tab.
Printer Format File: A file that contains an identifier. This file is represented by the iconPrinter format file icon in the upload file tab.
Image
A file that represents an image that will be sent to the printer.
This file is represented by the icon Image in the upload file tab.
Font
A file that represents a font style that will be used in a label. This file will be sent to the printer. It is represented by the Font icon in the upload file tab.
-
Appendix C – Business Rules
Parameters
Initial index: the beginning index, inclusive.
Final index: the ending index, exclusive.
Parameters
Search for value: Text
String position: Text
Insert
Insert a string in the position informed. Parameters
String to be inserted: the string to be inserted.
Position of insertion: the position where the String to be inserted parameter should be inserted.
Data Format
Return the date in the specified format. Parameter
Data format: the pattern describing the date and time format.
Ends With
If the field number value ends with the specified Ending with parameter, the field number value is replaced by the string in the Change for parameter. Parameters
- Ending with: the pattern to be matched.
- Change for: the value to be exchanged if the Ending with parameter is matched.
Replace
Returns a new string resulting from replacing all occurrences of Pattern to be matched parameter in the field number value with Pattern to be used parameter. Parameters
Pattern to be matched: the string to be found in the field number returned.
Pattern to be used: the string to be replaced by the pattern found in the field number.
Between
Returns a substring that is in between the Initial character parameter and the End character. Parameters
Initial character: the initial character to be matched.
End character: the end character to be matched.
No Ends With
If the field number value does not end with the specified No ending with a parameter, the field number value is exchanged by the string in the Change for the parameter. Parameters
No ending with: the pattern to be matched.
Change for: the value to be replaced if the Ending with parameter is matched.
Equals
If the field number matches the specified If equals parameter, the field number value is replaced by the string in the Change for the parameter. Parameters
If equals: the pattern to be matched.
Change for: the value to be replaced if the If equals parameter is matched.
-
Appendix D – Examples
-
How to create a block/element for containers
See a full example using an existing label on how to create a block / element for a Container: Figure 46: Container Sample Label
https://lh6.googleusercontent.com/mDsp7PKBk5DmHArphn_ssnRIMXJ50fAGKg2y_-iklvtcGsgEeqSjjtgAXIdA4zjnKG4n6t-DoUOZaUsffExk2jwz-2ExhcwTFKDyRN1zxYr43jc2sZH8Pb7poSYpyi4p4rZOafhwdXvU_WeZTFL2k-1vWcQXm3s9S9HbPRnFPrYpePEGEO3g68Hm
Figure 47: Container Sample Element
https://lh5.googleusercontent.com/shu8kraS57Hl6psBZOIT9evaVTE-D3TZgjlpCiulyNQUPjRPL-BWo8spf4-vxzh3Lq7DtF-6ldmCq7L3EM3BfMmg3DQ2aQZbBGIFx-RsaPohhqslMeymX5WAGJ7aPEmIQM-0r_As6DqHCF5MGQX8cKGoQh-NWVVdaciOBPws0-rMwZ9Cv8iEhdQg
Figure 48: Container Sample Label Mapping
-
Parallel Containers - Values Other than Just Serial Numbers
Often users will need a container label that contains the list of enclosed units / serial numbers as well as some other attribute(s) associated with each unit. For lack of a better name, Parallel Containers.
The below explanation will help ensure the container label extracts the correct data, and prints it in the correct order.
-
Naming Template Fields
When users work with Parallel Containers, it is very important to correctly name the template fields so that multiple containers are populated in the same order on the label.
Below, you will see examples of good naming strategy:
sn_01, sn_02, sn_03, …sn_##
mac_01, mac_02, mac_03, ...mac_##
comp_01, comp_02, comp_03, ...comp_##
Note: In case there were more than 100 units listed on a single page of a container label, use three digits instead of two digits.
Figure 49: Sample Label with Good Naming Strategy
https://lh4.googleusercontent.com/Xg2TMwdSvCofAtc5DWwoPg1Pnzzx8qmrTGaWmyR9PmXAprxTQsmm51VFzllk1C-rkH7qLQmldiF7nt3jQJaPfdNxbiigGA50JGpcTAvSQaOEkL3E2bzM2tKjoJOpOMTaz17FL8HYXiG_IyMx51vUDuOYqhPNiNXA8IsS2dxYMgF6gmNpLkm4j2Vp
-
Container Element & Block Formulation
When working with container labels, selecting the checkbox Values Will Be Assigned To Multiple Different Fields (Container) changes the scope of the data that is being extracted. Instead of the scope being the "container serial", the scope becomes the serial of each item in the container. The entry value will be the container serial number, but the value extracted will be the value for each item in the container.
Figure 54 demonstrates how to extract the child serial numbers, the entry is the container serial number and the output would be serial.serial_number.
Figure 50: Extracting Child Serial Numbers
https://lh6.googleusercontent.com/LSbsao48PjEeIoU91bAmocnsIja9pfCNOJt8aVE0B9kRtfIJlmV2W3Hcm3-jxyK93GLzuWXebDGrlZe4y6FNUa_o0JbYQf2fa4dr7LZDHuJCpmGUtfkaeM4ftUL2HJ7T6wG4avTw-E_hXvJhxKMQdkm7CJsY61EXMZJdAwyX818aJhKR-7j0WHyl
Figure 51 demonstrates the extraction of the mac addresses that were captured as components, using a reference designator of MAC_Address.
Figure 51: Extraction of the Mac Addresses
-
Container Element Mapping
Container mappings will be many template fields to a single Container Element. Multi-select the placeholder names (left side) and select the container element (right side) and click the Map button as in Figure 56.
Figure 52: Label Mapping
https://lh3.googleusercontent.com/q7NKs_JJsnoApOlXwXVFtSh5ZmMJhsPaX9a2gNZ2B-sioFrKat8D2xW5yGsMIK1_w-71eCewr7aLxT2HbqLmUlhRdqscfcKbKroI5RDWjD5SlvM3Aek71YbBy8Wt3Is5C5aKDtLKsfrJM1jyvaweEVeAtLWkRdyupY5f4nv2uJrgfXzrDQz2GrRT When users follow the previous steps and print labels, they will see labels similar to the image Figure 57. Figure 53: Resulting Label