ENOVIA Live

Collaboration™
V6R2013x

Matrix Navigator Guide

Copyright and Trademark Information

© Dassault Systèmes, 1994 - 2012

All rights reserved.

PROPRIETARY RIGHTS NOTICE: This documentation is proprietary property of Dassault Systèmes. This documentation shall be treated as confidential information and may only be used by employees or contractors with the Customer in accordance with the applicable Software License Agreement.
Adaplet, Compliance Connect, DesignSync, ENOVIA, ProjectSync, Synchronicity, Team Central, ENOVIA Collaboration Platform, ENOVIA Business Process Services, ENOVIA Platform Server, ENOVIA Modeling Studio, ENOVIA 3D Live, FCS, AEF, Application Exchange Framework, Application
Development Kit, ENOVIA V6X-BOM Engineering, ENOVIA Library Central, ENOVIA Materials Compliance Central, ENOVIA Variant Configuration, ENOVIA Program Central, ENOVIA Sourcing Central, ENOVIA Specification Central, ENOVIA Supplier Central, ENOVIA Collaborative
Interference Management, ENOVIA Semiconductor Accelerator for Team Collaboration, ENOVIA Aerospace and Defense Accelerator for Program Management, ENOVIA Apparel Accelerator for Design and Development, ENOVIA Automotive Accelerator for Program Management, ENOVIA Medical
Device Accelerator for Regulatory Compliance, ENOVIA X-BOM Cost Analytics, ENOVIA X-BOM Manufacturing, ENOVIA Synchronicity DesignSync DFII, ENOVIA Synchronicity DesignSync MW, ENOVIA Synchronicity DesignSync CTS, ENOVIA IP Gear, IconMail, ImageIcon and Star
Browser are either trademarks or registered trademarks of Dassault Systèmes or its subsidiaries in the US and/or other countries.
Oracle® is a registered trademark of Oracle Corporation, Redwood City, California. DB2, AIX, and WebSphere are registered trademarks of IBM Corporation. WebLogic is a registered trademark of BEA Systems, Inc. Solaris, UltraSPARC, Java, JavaServer Pages, JDBC, and J2EE are registered
trademarks of Sun Microsystems, Inc. Windows XP and Internet Explorer are registered trademarks of Microsoft Corp. HP and HP-UX are registered trademarks of HP. All other product names and services identified throughout this book are recognized as trademarks, registered trademarks, or service
marks of their respective companies.
The documentation that accompanies ENOVIA products describes the applications as delivered by Dassault Systèmes. This documentation includes readme files, online help, user guides, and administrator guides. If changes are made to an application or to the underlying framework, Dassault Systèmes
cannot ensure the accuracy of this documentation. These changes include but are not limited to: changing onscreen text, adding or removing fields on a page, making changes to the administrative objects in the schema, adding new JSPs or changing existing JSPs, changing trigger programs, changing the
installation or login process, or changing the values in any properties file. For instructions on customizing the provided documentation, see the Business Process Services Administrator’s Guide.
Dassault Systèmes ENOVIA
175 Wyman Street
Waltham, MA 02451
Telephone 781.810.3500
Email: enovia.info@3ds.com
http://www.3ds.com

Additional Components
This product also includes additional components copyrighted by other third parties. The sections that follow provide license and copyright notices of these software components.

Apache
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by
contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative
Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity
authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense,
and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise
transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation
against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such
litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The
contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot
be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work
otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein
shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without
limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of
permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct,
indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or
losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such
obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting
any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend
that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations
under the License.

Apache Ant
=========================================================================
NOTICE file corresponding to the section 4 d of the Apache License, Version 2.0, in this case for the Apache Ant distribution.
=========================================================================
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).
This product includes also software developed by :
- the W3C consortium (http://www.w3c.org) ,
- the SAX project (http://www.saxproject.org)
Please read the different LICENSE files present in the root directory of this distribution. [BELOW]

This license came from:

http://www.w3.org/Consortium/Legal/copyright-software-19980720
W3C® SOFTWARE NOTICE AND LICENSE
Copyright © 1994-2001 World Wide Web Consortium, <a href="http://www.w3.org/">World Wide Web Consortium</a>, (<a href= "http://www.lcs.mit.edu/">Massachusetts Institute of Technology</a>, <a href="http://www.inria.fr/">Institut National de Recherche en Informatique et en Automatique</
a>, <a href= "http://www.keio.ac.jp/">Keio University</a>). All Rights Reserved.
http://www.w3.org/Consortium/Legal/
This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including
modifications, that you make:
The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code:
"Copyright © 1999-2004 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"
Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY
PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT,
SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.

This license came from: http://www.megginson.com/SAX/copying.html. However please note future versions of SAX may be covered under http://saxproject.org/?selected=pd
This page is now out of date -- see the new SAX site at http://www.saxproject.org/ for more up-to-date releases and other information. Please change your bookmarks.
SAX2 is Free!
I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release all of the SAX 2.0 source code, compiled code, and documentation contained in this distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of fitness for any purpose.
David Megginson, david@megginson.com

Apache Axis
=========================================================================
NOTICE file corresponding to section 4(d) of the Apache License, Version 2.0, in this case for the Apache Axis distribution.
=========================================================================
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).

Apache Tomcat
[under Apache License, Version 2.0 above]

Apache Servlet-API
[under Apache License, Version 2.0 above]

FTP
Copyright (c) 1983, 1985, 1989, 1993, 1994
The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
This product includes software developed by the University of California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAYOUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Copyright (c) 1997-1999 The Stanford SRP Authentication Project
All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL STANFORD BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER
Copyright 1990 by the Massachusetts Institute of Technology.
All Rights Reserved.
Export of this software from the United States of America may require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in
supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or
implied warranty.

Getline
Copyright (C) 1991, 1992, 1993 by Chris Thewalt (thewalt@ce.berkeley.edu)
Permission to use, copy, modify, and distribute this software for any purpose and without fee is hereby granted, provided that the above copyright notices appear in all copies and that both the copyright notice and this permission notice appear in supporting documentation. This software is provided "as is"
without express or implied warranty.

GifEncoder
GifEncoder - write out an image as a GIF
Transparency handling and variable bit size courtesy of Jack Palevich.
Copyright (C)1996,1998 by Jef Poskanzer <jef@acme.com>. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

ImageEncoder
ImageEncoder - abstract class for writing out an image
Copyright (C) 1996 by Jef Poskanzer <jef@acme.com>. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

JavaMail
Sun Microsystems, Inc.
Binary Code License Agreement
READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE OPENING THE SOFTWARE MEDIA PACKAGE. BY OPENING THE SOFTWARE MEDIA PACKAGE, YOU AGREE TO
THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL THESE
TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF PURCHASE FOR A REFUND OR, IF THE SOFTWARE IS ACCESSED ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS AGREEMENT.
1. LICENSE TO USE. Sun grants you a non-exclusive and non-transferable license for the internal use only of the accompanying software and documentation and any error corrections provided by Sun (collectively "Software"), by the number of users and the class of computer hardware for which the
corresponding fee has been paid.
2. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Except as specifically authorized in any Supplemental License Terms, you may not make copies of Software, other than a single copy of
Software for archival purposes. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software. You acknowledge that Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility.
Sun disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement.
3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing,
Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software.
4. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
5. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you,
whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose.
6. Termination. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Upon Termination, you
must destroy all copies of Software.
7. Export Regulations. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the
responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.
8. U.S. Government Restricted Rights. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement;
this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).
9. Governing Law. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.
10. Severability. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate.
11. Integration. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order,
acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party.

JAVAMAILTM, VERSION 1.3.1

SUPPLEMENTAL LICENSE TERMS
These supplemental license terms ("Supplemental Terms") add to or modify the terms of the Binary Code License Agreement (collectively, the "Agreement"). Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Agreement. These Supplemental
Terms shall supersede any inconsistent or conflicting terms in the Agreement, or in any license contained within the Software.
1. Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement, including, but not limited to Section 3 (Java(TM) Technology Restrictions) of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license to reproduce
internally and use internally the binary form of the Software, complete and unmodified, for the sole purpose of designing, developing and testing your Java applets and applications ("Programs").
2. License to Distribute Software.* Subject to the terms and conditions of this Agreement, including, but not limited to Section 3 (Java (TM) Technology Restrictions) of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license to reproduce and distribute the Software
in binary code form only, provided that (i) you distribute the Software complete and unmodified and only bundled as part of, and for the sole purpose of running, your Java applets or applications ("Programs"), (ii) the Programs add significant and primary functionality to the Software, (iii) you do not
distribute additional software intended to replace any component(s) of the Software, (iv) you do not remove or alter any proprietary legends or notices contained in the Software, (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms
contained in this Agreement, and (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results
from the use or distribution of any and all Programs and/or Software.
3. Java Technology Restrictions.* You may not modify the Java Platform Interface ("JPI", identified as classes contained within the "java" package or any subpackages of the "java" package), by creating additional classes within the JPI or otherwise causing the addition to or modification of the classes in
the JPI. In the event that you create an additional class and associated API(s) which (i) extends the functionality of the Java platform, and (ii) is exposed to third party software developers for the purpose of developing additional software which invokes such additional API, you must promptly publish
broadly an accurate specification for such API for free use by all developers. You may not create, or authorize your licensees to create additional classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any naming convention
designation.
4. Trademarks and Logos. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, STAROFFICE, STARPORTAL and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, STAROFFICE, STARPORTAL and iPLANET-related
trademarks, service marks, logos and other brand designations ("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.
5. Source Code. Software may contain source code that is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement.
6. Termination for Infringement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right.
For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A
/(LFI#132726/Form ID#011801)/

Jakarta POI
[under Apache License, Version 2.0 above]

JDK
Sun Microsystems, Inc. Binary Code License Agreement
for the JAVA 2 PLATFORM STANDARD EDITION DEVELOPMENT KIT 5.0
SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL
LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASE READ THE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THIS SOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT. INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT"
BUTTON AT THE BOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY ALL THE TERMS, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THE AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT CONTINUE.
1. DEFINITIONS. "Software" means the identified above in binary form, any other machine readable materials (including, but not limited to, libraries, source files, header files, and data files), any updates or error corrections provided by Sun, and any user manuals, programming guides and other
documentation provided to you by Sun under this Agreement. "Programs" mean Java applets and applications intended to run on the Java 2 Platform Standard Edition (J2SE platform) platform on Java-enabled general purpose desktop computers and servers.
2. LICENSE TO USE. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of the Supplemental License Terms, Sun grants you a non-exclusive, non-transferable, limited license without license fees to reproduce and use internally Software
complete and unmodified for the sole purpose of running Programs. Additional licenses for developers and/or publishers are granted in the Supplemental License Terms.
3. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software. You acknowledge that
Licensed Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name
of Sun or its licensors is granted under this Agreement. Additional restrictions for developers and/or publishers licenses are set forth in the Supplemental License Terms.
4. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing,
Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. Any implied warranties on the Software are limited to 90 days. Some states do not allow limitations on duration
of an implied warranty, so the above may not apply to you. This limited warranty gives you specific legal rights. You may have others, which vary from state to state.
5. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
OR NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
6. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you,
whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. Some states do not allow the exclusion of incidental or consequential
damages, so some of the terms above may not be applicable to you.
7. TERMINATION. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Either party may
terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right. Upon Termination, you must destroy all copies of Software.
8. EXPORT REGULATIONS. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the
responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.
9. TRADEMARKS AND LOGOS. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations
("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.
10. U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this
Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).
11. GOVERNING LAW. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.
12. SEVERABILITY. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate.
13. INTEGRATION. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order,
acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party.
SUPPLEMENTAL LICENSE TERMS
These Supplemental License Terms add to or modify the terms of the Binary Code License Agreement. Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Binary Code License Agreement . These Supplemental Terms shall supersede any
inconsistent or conflicting terms in the Binary Code License Agreement, or in any license contained within the Software.
A. Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software "README" file, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a
non-exclusive, non-transferable, limited license without fees to reproduce internally and use internally the Software complete and unmodified for the purpose of designing, developing, and testing your Programs.
B. License to Distribute Software. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable,
limited license without fees to reproduce and distribute the Software, provided that (i) you distribute the Software complete and unmodified and only bundled as part of, and for the sole purpose of running, your Programs, (ii) the Programs add significant and primary functionality to the Software, (iii) you
do not distribute additional software intended to replace any component(s) of the Software, (iv) you do not remove or alter any proprietary legends or notices contained in the Software, (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms
contained in this Agreement, and (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results
from the use or distribution of any and all Programs and/or Software.
C. License to Distribute Redistributables. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive,
non-transferable, limited license without fees to reproduce and distribute those files specifically identified as redistributable in the Software "README" file ("Redistributables") provided that: (i) you distribute the Redistributables complete and unmodified, and only bundled as part of Programs, (ii) the
Programs add significant and primary functionality to the Redistributables, (iii) you do not distribute additional software intended to supersede any component(s) of the Redistributables (unless otherwise specified in the applicable README file), (iv) you do not remove or alter any proprietary legends or
notices contained in or on the Redistributables, (v) you only distribute the Redistributables pursuant to a license agreement that protects Sun's interests consistent with the terms contained in the Agreement, (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs,
liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.
D. Java Technology Restrictions. You may not create, modify, or change the behavior of, or authorize your licensees to create, modify, or change the behavior of, classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any
naming convention designation.
E. Distribution by Publishers. This section pertains to your distribution of the Software with your printed book or magazine (as those terms are commonly used in the industry) relating to Java technology ("Publication"). Subject to and conditioned upon your compliance with the restrictions and obligations
contained in the Agreement, in addition to the license granted in Paragraph 1 above, Sun hereby grants to you a non-exclusive, nontransferable limited right to reproduce complete and unmodified copies of the Software on electronic media (the "Media") for the sole purpose of inclusion and distribution
with your Publication(s), subject to the following terms: (i) You may not distribute the Software on a stand-alone basis; it must be distributed with your Publication(s); (ii) You are responsible for downloading the Software from the applicable Sun web site; (iii) You must refer to the Software as JavaTM 2
Platform Standard Edition Development Kit 5.0; (iv) The Software must be reproduced in its entirety and without any modification whatsoever (including, without limitation, the Binary Code License and Supplemental License Terms accompanying the Software and proprietary rights notices contained in
the Software); (v) The Media label shall include the following information: Copyright 2004, Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Sun, Sun Microsystems, the Sun logo, Solaris, Java, the Java Coffee Cup logo, J2SE , and all trademarks and logos based on Java are
trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. This information must be placed on the Media label in such a manner as to only apply to the Sun Software; (vi) You must clearly identify the Software as Sun's product on the Media holder or Media label, and
you may not state or imply that Sun is responsible for any third-party software contained on the Media; (vii) You may not include any third party software on the Media which is intended to be a replacement or substitute for the Software; (viii) You shall indemnify Sun for all damages arising from your
failure to comply with the requirements of this Agreement. In addition, you shall defend, at your expense, any and all claims brought against Sun by third parties, and shall pay all damages awarded by a court of competent jurisdiction, or such settlement amount negotiated by you, arising out of or in
connection with your use, reproduction or distribution of the Software and/or the Publication. Your obligation to provide indemnification under this section shall arise provided that Sun: (i) provides you prompt notice of the claim; (ii) gives you sole control of the defense and settlement of the claim; (iii)
provides you, at your expense, with all available information, assistance and authority to defend; and (iv) has not compromised or settled such claim without your prior written consent; and (ix) You shall provide Sun with a written notice for each Publication; such notice shall include the following
information: (1) title of Publication, (2) author(s), (3) date of Publication, and (4) ISBN or ISSN numbers. Such notice shall be sent to Sun Microsystems, Inc., 4150 Network Circle, M/S USCA12-110, Santa Clara, California 95054, U.S.A , Attention: Contracts Administration.
F. Source Code. Software may contain source code that, unless expressly licensed for other purposes, is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement.
G. Third Party Code. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME.txt file. In addition to any terms and conditions of any third party opensource/freeware license identified in the
THIRDPARTYLICENSEREADME.txt file, the disclaimer of warranty and limitation of liability provisions in paragraphs 5 and 6 of the Binary Code License Agreement shall apply to all Software in this distribution.
For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A.
(LFI#141623/Form ID#011801)
DO NOT TRANSLATE OR LOCALIZE.
The following software may be included in this product: CS CodeViewer v1.0;
Use of any of this software is governed by the terms of the license below:
Copyright 1999 by CoolServlets.com.
Any errors or suggested improvements to this class can be reported as instructed on CoolServlets.com. We hope you enjoy this program... your comments will encourage further development!
This software is distributed under the terms of the BSD License. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither name of CoolServlets.com nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY COOLSERVLETS.COM AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE."
The following software may be included in this product: Crimson v1.1.1 ; Use of any of this software is governed by the terms of the license below:
The Apache Software License, Version 1.1
Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and
wherever such third-party acknowledgments normally appear.
4. The names "Crimson" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
====================================================================
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation,
please see <http://www.apache.org/>.
The following software may be included in this product: Xalan J2;
Use of any of this software is governed by the terms of the license below:
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by
contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative
Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity
authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense,
and distribute the Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise
transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation
against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such
litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The
contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot
be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work
otherwise complies with the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein
shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without
limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of
permissions under this License.
8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct,
indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or
losses), even if such Contributor has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such
obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting
any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend
that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations
under the License.
The following software may be included in this product: NSIS 1.0j; Use of any of this software is governed by the terms of the license below:
Copyright (C) 1999-2000 Nullsoft, Inc.
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute
it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.Justin Frankel justin@nullsoft.com"
Some Portions licensed from IBM are available at: http://oss.software.ibm.com/icu4j/
Portions Copyright Eastman Kodak Company 1992
Lucida is a registered trademark or trademark of Bigelow & Holmes in the U.S. and other countries.
Portions licensed from Taligent, Inc.
The following software may be included in this product:IAIK PKCS Wrapper; Use of any of this software is governed by the terms of the license below:
Copyright (c) 2002 Graz University of Technology. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by IAIK of Graz University of Technology."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The names "Graz University of Technology" and "IAIK of Graz University of Technology" must not be used to endorse or promote products derived from this software without prior written permission.
5. Products derived from this software may not be called "IAIK PKCS Wrapper", nor may "IAIK" appear in their name, without prior written permission of Graz University of Technology.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE LICENSOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The following software may be included in this product: Document Object Model (DOM) v. Level 3; Use of any of this software is governed by the terms of the license below:
W3Cýý SOFTWARE NOTICE AND LICENSE
http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
This work (and included software, documentation such as READMEs, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following
terms and conditions.
Permission to copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including
modifications:
1.The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
2.Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C Software Short Notice should be included (hypertext is preferred, text is permitted) within the body of any redistributed or derivative code.
3.Notice of any changes or modifications to the files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY
PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.
This formulation of W3C's notice and license became active on December 31 2002.
This version removes the copyright ownership notice such that this license can be used with materials other than those owned by the W3C, reflects that ERCIM is now a host of the W3C, includes references to this specific dated version of the license, and removes the ambiguous grant of "use". Otherwise,
this version is the same as the previous version and is written so as to preserve the Free Software Foundation's assessment of GPL compatibility and OSI's certification under the Open Source Definition. Please see our Copyright FAQ for common questions about using materials from our site, including
specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org.
The following software may be included in this product: Xalan, Xerces; Use of any of this software is governed by the terms of the license below:
The Apache Software License, Version 1.1
Copyright (c) 1999-2003 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and
wherever such third-party acknowledgments normally appear.
4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
====================================================================
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation,
please see <http://www.apache.org/>.
The following software may be included in this product: W3C XML Conformance Test Suites v. 20020606; Use of any of this software is governed by the terms of the license below:
W3Cýý SOFTWARE NOTICE AND LICENSE
Copyright ýý 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/
This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including
modifications, that you make:
1. The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
2. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright ýý [$date-of-software] World Wide Web
Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"
3. Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY
PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.
This formulation of W3C's notice and license became active on August 14 1998 so as to improve compatibility with GPL. This version ensures that W3C software licensing terms are no more restrictive than GPL and consequently W3C software may be distributed in GPL packages. See the older
formulation for the policy prior to this date. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org.
The following software may be included in this product: W3C XML Schema Test Collection v. 1.16.2; Use of any of this software is governed by the terms of the license below:
W3Cýýýý DOCUMENT NOTICE AND LICENSE
Copyright ýýýý 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.
http://www.w3.org/Consortium/Legal/
Public documents on the W3C site are provided by the copyright holders under the following license. The software or Document Type Definitions (DTDs) associated with W3C specifications are governed by the Software Notice. By using and/or copying this document, or the W3C document from which
this statement is linked, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, and distribute the contents of this document, or the W3C document from which this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the document, or portions thereof, that
you use:
1. A link or URL to the original W3C document.
2. The pre-existing copyright notice of the original author, or if it doesn't exist, a notice of the form: "Copyright ýýýý [$date-of-document] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights
Reserved. http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but a textual representation is permitted.)
3. If it exists, the STATUS of the W3C document.
When space permits, inclusion of the full text of this NOTICE should be provided. We request that authorship attribution be provided in any software, documents, or other items or products that you create pursuant to the implementation of the contents of this document, or any portion thereof.
No right to create modifications or derivatives of W3C documents is granted pursuant to this license. However, if additional requirements (documented in the Copyright FAQ) are satisfied, the right to create modifications or derivatives is sometimes granted by the W3C to individuals complying with those
requirements.
THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER
RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to this document or its contents without specific, written prior permission. Title to copyright in this document will at all times remain with copyright holders.
----------------------------------------------------------------------------
This formulation of W3C's notice and license became active on April 05 1999 so as to account for the treatment of DTDs, schema's and bindings. See the older formulation for the policy prior to this date. Please see our Copyright FAQ for common questions about using materials from our site, including
specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org. webmaster (last updated by reagle on 1999/04/99.)
The following software may be included in this product: Mesa 3-D graphics library v. 5; Use of any of this software is governed by the terms of the license below:
core Mesa code include/GL/gl.h Brian Paul Mesa
GLX driver include/GL/glx.h Brian Paul Mesa
Ext registry include/GL/glext.h SGI SGI Free B
include/GL/glxext.h
Mesa license:
The Mesa distribution consists of several components. Different copyrights and licenses apply to different components. For example, GLUT is copyrighted by Mark Kilgard, some demo programs are copyrighted by SGI, some of the Mesa device drivers are copyrighted by their authors. See below for a
list of Mesa's components and the copyright/license for each.
The core Mesa library is licensed according to the terms of the XFree86 copyright (an MIT-style license). This allows integration with the XFree86/DRI project. Unless otherwise stated, the Mesa source code and documentation is licensed as follows:
Copyright (C) 1999-2003 Brian Paul All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
SHALL BRIAN PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
SGI Free Software Licence B:
, or is under common control with Recipient. For purposes of this definition, "control" of an entity means (a) the power, direct or indirect, to direct or manage such entity, or (b) ownership of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity.
1.12."Recipient Patents" means patent claims Licensable by a Recipient that are infringed by the use or sale of Original Code or any Modifications provided by SGI, or any combination thereof.
1.13."SGI" means Silicon Graphics, Inc.
1.14."SGI Patents" means patent claims Licensable by SGI other than the Licensed Patents.
2.License Grant and Restrictions.
2.1.SGI License Grant. Subject to the terms of this License and any third party intellectual property claims, for the duration of intellectual property protections inherent in the Original Code, SGI hereby grants Recipient a worldwide, royalty-free, non-exclusive license, to do the following: (i) under
copyrights Licensable by SGI, to reproduce, distribute, create derivative
The following software may be included in this product: Byte Code Engineering Library (BCEL) v. 5; Use of any of this software is governed by the terms of the license below:
Apache Software License
The Apache Software License, Version 1.1
Copyright (c) 2001 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and
wherever such third-party acknowledgments normally appear.
4. The names "Apache" and "Apache Software Foundation" and "Apache BCEL" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
5. Products derived from this software may not be called "Apache", "Apache BCEL", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.
The following software may be included in this product: Regexp, Regular Expression Package v. 1.2; Use of any of this software is governed by the terms of the license below:
The Apache Software License, Version 1.1
Copyright (c) 2001 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The names "Apache" and "Apache Software Foundation" and "Apache Turbine" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
5. Products derived from this software may not be called "Apache", "Apache Turbine", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org.
The following software may be included in this product: JLex: A Lexical Analyzer Generator for Java v. 1.2.5; Use of any of this software is governed by the terms of the license below:
JLEX COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
Copyright 1996-2003 by Elliot Joel Berk and C. Scott Ananian
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission notice and warranty disclaimer appear in supporting
documentation, and that the name of the authors or their employers not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss
of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of this software.
Java is a trademark of Sun Microsystems, Inc. References to the Java programming language in relation to JLex are not meant to imply that Sun endorses this product.
The following software may be included in this product: SAX v. 2.0.1; Use of any of this software is governed by the terms of the license below:
Copyright Status
SAX is free!
In fact, it's not possible to own a license to SAX, since it's been placed in the public domain.
No Warranty
Because SAX is released to the public domain, there is no warranty for the design or for the software implementation, to the extent permitted by applicable law. Except when otherwise stated in writing the copyright holders and/or other parties provide SAX "as is" without warranty of any kind, either
expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of SAX is with you.
Should SAX prove defective, you assume the cost of all necessary servicing, repair or correction.
In no event unless required by applicable law or agreed to in writing will any copyright holder, or any other party who may modify and/or redistribute SAX, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use SAX
(including but not limited to loss of data or data being rendered inaccurate or losses sustained by you or third parties or a failure of the SAX to operate with any other programs), even if such holder or other party has been advised of the possibility of such damages.
Copyright Disclaimers
This page includes statements to that effect by David Megginson, who would have been able to claim copyright for the original work.
SAX 1.0
Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of the XML-DEV mailing list, is hereby released into the public domain.
No one owns SAX: you may use it freely in both commercial and non-commercial applications, bundle it with your software distribution, include it on a CD-ROM, list the source code in a book, mirror the documentation at your own web site, or use it in any other way you see fit.
David Megginson, sax@megginson.com 1998-05-11
SAX 2.0
I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release all of the SAX 2.0 source code, compiled code, and documentation contained in this distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of fitness for any purpose.
David Megginson, david@megginson.com
2000-05-05
The following software may be included in this product: Cryptix;
Use of any of this software is governed by the terms of the license below:
Cryptix General License
Copyright © 1995-2003 The Cryptix Foundation Limited. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
EXERPT FROM JavaTM 2 Platform Standard Edition Development Kit 5.0 README
You can freely redistribute the J2SE Runtime Environment with your application, according to the terms of the Runtime Environment's license. Once you have developed your application using the JDK, you can ship it with the Runtime Environment so your end-users will have a Java platform on which
to run your software.
Redistribution
--------------------------------------------------------------------------------
NOTE - The license for this software does not allow the redistribution of beta and other pre-release versions.
--------------------------------------------------------------------------------
Subject to the terms and conditions of the Software License Agreement and the obligations, restrictions, and exceptions set forth below, You may reproduce and distribute the Software (and also portions of Software identified below as Redistributable), provided that:
you distribute the Software complete and unmodified and only bundled as part of Your applets and applications ("Programs"),
your Programs add significant and primary functionality to the Software,
your Programs are only intended to run on Java-enabled general purpose desktop computers and servers,
you distribute Software for the sole purpose of running your Programs,
you do not distribute additional software intended to replace any component(s) of the Software,
you do not remove or alter any proprietary legends or notices contained in or on the Software,
you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement, and
you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and
all Programs and/or Software.
The term "vendors" used here refers to licensees, developers, and independent software vendors (ISVs) who license and distribute the J2SE Development Kit with their programs.
Vendors must follow the terms of the J2SE Development Kit Binary Code License agreement.
Required vs. Optional Files
The files that make up the J2SE Development Kit are divided into two categories: required and optional. Optional files may be excluded from redistributions of the JDK at the vendor's discretion.
The following section contains a list of the files and directories that may optionally be omitted from redistributions of the JDK. All files not in these lists of optional files must be included in redistributions of the JDK.
Optional Files and Directories
The following files may be optionally excluded from redistributions. These files are located in the jdk1.5.0_<version> directory, where <version> is the update version number. Solaris and Linux filenames and separators are shown. Windows executables have the ".exe" suffix. Corresponding files with _g
in name can also be excluded.
jre/lib/charsets.jar
Character conversion classes
jre/lib/ext/
sunjce_provider.jar - the SunJCE provider for Java Cryptography APIs
localedata.jar - contains many of the resources needed for non US English locales
ldapsec.jar - contains security features supported by the LDAP service provider
dnsns.jar - for the InetAddress wrapper of JNDI DNS provider
bin/rmid and jre/bin/rmid
Java RMI Activation System Daemon
bin/rmiregistry and jre/bin/rmiregistry
Java Remote Object Registry
bin/tnameserv and jre/bin/tnameserv
Java IDL Name Server
bin/keytool and jre/bin/keytool
Key and Certificate Management Tool
bin/kinit and jre/bin/kinit
Used to obtain and cache Kerberos ticket-granting tickets
bin/klist and jre/bin/klist
Kerberos display entries in credentials cache and keytab
bin/ktab and jre/bin/ktab
Kerberos key table manager
bin/policytool and jre/bin/policytool
Policy File Creation and Management Tool
bin/orbd and jre/bin/orbd
Object Request Broker Daemon
bin/servertool and jre/bin/servertool
Java IDL Server Tool
bin/javaws, jre/bin/javaws, jre/lib/javaws/ and jre/lib/javaws.jar
Java Web Start
src.zip
Archive of source files
Redistributable JDK Files
The limited set of files from the JDK listed below may be included in vendor redistributions of the J2SE Runtime Environment. They cannot be redistributed separately, and must accompany a JRE distribution. All paths are relative to the top-level directory of the JDK.
jre/lib/cmm/PYCC.pf
Color profile. This file is required only if one wishes to convert between the PYCC color space and another color space.
All .ttf font files in the jre/lib/fonts directory.
Note that the LucidaSansRegular.ttf font is already contained in the J2SE Runtime Environment, so there is no need to bring that file over from the JDK.
jre/lib/audio/soundbank.gm
This MIDI soundbank is present in the JDK, but it has been removed from the J2SE Runtime Environment in order to reduce the size of the Runtime Environment's download bundle. However, a soundbank file is necessary for MIDI playback, and therefore the JDK's soundbank.gm file may be included
in redistributions of the Runtime Environment at the vendor's discretion. Several versions of enhanced MIDI soundbanks are available from the Java Sound web site: http://java.sun.com/products/java-media/sound/. These alternative soundbanks may be included in redistributions of the J2SE Runtime
Environment.
The javac bytecode compiler, consisting of the following files:
bin/javac [Solaris(TM) Operating System and Linux]
bin/sparcv9/javac [Solaris Operating System (SPARC(R) Platform Edition)]
bin/amd64/javac [Solaris Operating System (AMD)]
bin/javac.exe [Microsoft Windows]
lib/tools.jar [All platforms]
The Annotation Processing Tool, consisting of the following files:
bin/apt [Solaris(TM) Operating System and Linux]
bin/sparcv9/apt [Solaris Operating System (SPARC(R) Platform Edition)]
bin/amd64/apt [Solaris Operating System (AMD)]
bin/apt.exe [Microsoft Windows]
jre\bin\server\
On Microsoft Windows platforms, the JDK includes both the Java HotSpot Server VM and Java HotSpot Client VM. However, the J2SE Runtime Environment for Microsoft Windows platforms includes only the Java HotSpot Client VM. Those wishing to use the Java HotSpot Server VM with the J2SE
Runtime Environment may copy the JDK's jre\bin\server folder to a bin\server directory in the J2SE Runtime Environment. Software vendors may redistribute the Java HotSpot Server VM with their redistributions of the J2SE Runtime Environment.
Unlimited Strength Java Cryptography Extension
Due to import control restrictions for some countries, the Java Cryptography Extension (JCE) policy files shipped with the J2SE Development Kit and the J2SE Runtime Environment allow strong but limited cryptography to be used. These files are located at
<java-home>/lib/security/local_policy.jar
<java-home>/lib/security/US_export_policy.jar
where <java-home> is the jre directory of the JDK or the top-level directory of the J2SE Runtime Environment.
An unlimited strength version of these files indicating no restrictions on cryptographic strengths is available on the JDK web site for those living in eligible countries. Those living in eligible countries may download the unlimited strength version and replace the strong cryptography jar files with the
unlimited strength files.
jconsole
jconsole.jar
jconsole may be redistributed outside the JDK but only with Sun's JRE.
Endorsed Standards Override Mechanism
An endorsed standard is a Java API defined through a standards process other than the Java Community ProcessSM (JCPSM). Because endorsed standards are defined outside the JCP, it is anticipated that such standards will be revised between releases of the Java 2 Platform. In order to take advantage of
new revisions to endorsed standards, developers and software vendors may use the Endorsed Standards Override Mechanism to provide newer versions of an endorsed standard than those included in the Java 2 Platform as released by Sun Microsystems.
For more information on the Endorsed Standards Override Mechanism, including the list of platform packages that it may be used to override, see
http://java.sun.com/j2se/1.5.0/docs/guide/standards/
Classes in the packages listed on that web page may be replaced only by classes implementing a more recent version of the API as defined by the appropriate standards body.
In addition to the packages listed in the document at the above URL, which are part of the Java 2 Platform Standard Edition (J2SETM) specification, redistributors of Sun's J2SE Reference Implementation are allowed to override classes whose sole purpose is to implement the functionality provided by
public APIs defined in these Endorsed Standards packages. Redistributors may also override classes in the org.w3c.dom.* packages, or other classes whose sole purpose is to implement these APIs.
The cacerts Certificates File
Root CA certificates may be added to or removed from the J2SE certificate file located at <java-home>/lib/security/cacerts. For more information, see The cacerts Certificates File section in the keytool documentation.
Web Pages
For additional information, refer to these Sun Microsystems pages on the World Wide Web:
http://java.sun.com/
The Java Software web site, with the latest information on Java technology, product information, news, and features.
http://java.sun.com/docs
Java Platform Documentation provides access to white papers, the Java Tutorial and other documents.
http://developer.java.sun.com
Developer Services web site. (Free registration required.) Additional technical information, news, and features; user forums; support information, and much more.
http://java.sun.com/products/
Java Technology Products & API
--------------------------------------------------------------------------------
The J2SE Development Kit is a product of Sun MicrosystemsTM, Inc.
Copyright 2005 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A.
All rights reserved.

JDOM
Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.
3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact <request_AT_jdom_DOT_org>.
4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management <request_AT_jdom_DOT_org>.
In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the following:
"This product includes software developed by the JDOM Project (http://www.jdom.org/)."
Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.
THIS SOFTWARE IS PROVIDED ''AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. For more information on the JDOM Project, please see <http://
www.jdom.org/>.

Krypto
Copyright (c) 1997 Stanford University
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notices and this permission notice appear in all copies of the software and related documentation.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL STANFORD BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE
POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Copyright (C) 1995-1997 Eric Young (eay@mincom.oz.au)

All rights reserved.
This package is an SSL implementation written by Eric Young (eay@mincom.oz.au). The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution
is covered by the same copyright terms except that the holder is Tim Hudson (tjh@mincom.oz.au).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation
(online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
"This product includes cryptographic software written by Eric Young (eay@mincom.oz.au)"
The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related .
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement:
"This product includes software written by Tim Hudson (tjh@mincom.oz.au)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]

OpenLDAP
Public License for 2.3.34
The OpenLDAP Public License
Version 2.8, 17 August 2003
Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:
1. Redistributions in source form must retain copyright statements and notices,
2. Redistributions in binary form must reproduce applicable copyright statements and notices, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution, and
3. Redistributions must contain a verbatim copy of this document.
The OpenLDAP Foundation may revise this license from time to time. Each revision is distinguished by a version number. You may use this Software under terms of this license revision or under the terms of any subsequent revision of the license.
THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OPENLDAP FOUNDATION, ITS CONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S) OF THE SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The names of the authors and copyright holders must not be used in advertising or otherwise to promote the sale, use or other dealing in this Software without specific, written prior permission. Title to copyright in this Software shall at all times remain with copyright holders.
OpenLDAP is a registered trademark of the OpenLDAP Foundation.
Copyright 1999-2003 The OpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved. Permission to copy and distribute verbatim copies of this document is granted.

OpenSSL
License
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please
contact openssl-core@openssl.org.
OpenSSL License
Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution
is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation
(online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)"
The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License.]
Oracle
*****************************************************************
Oracle Instant client
End user license agreement ("Agreement")
*****************************************************************
MatrixOne Inc., ("MatrixOne") as licensor, has been given the right by Oracle Corporation (Oracle") to distribute the Oracle Instant Client software ("Program(s)") to you, an end user. Each end user hereby agrees: (1) to restrict its use of the Programs to its internal business operations; (2) that it is
prohibited from (a) assigning, giving, or transferring the Programs or an interest in them to another individual or entity (and if it grants a security interest in the Programs, the secured party has no right to use or transfer the Programs); (b) making the Programs available in any manner to any third party for
use in the third party's business operations (unless such access is expressly permitted for the specific program license or materials from the services acquired); and (3) that title to the Programs does not pass to the end user or any other party; (4) that reverse engineering is prohibited (unless required by law
for interoperability), (5) disassembly or decompilation of the Programs are prohibited; (6) duplication of the Programs is prohibited except for a sufficient number of copies of each Program for the end user's licensed use and one copy of each Program media; (7) that, to the extent permitted by applicable
law, liability of Oracle and MatrixOne for any damages, whether direct, indirect, incidental, or consequential, arising from the use of the Programs is disclaimed; (8) at the termination of the Agreement, to discontinue use and destroy or return to MatrixOne all copies of the Programs and documentation;
(9) not to publish any results of benchmark tests run on the Programs; (10) to comply fully with all relevant export laws and regulations of the United States and other applicable export and import laws to assure that neither the Programs, nor any direct product thereof, are exported, directly or indirectly,
in violation of applicable laws and are not used for any purpose prohibited by these laws including, without limitation, nuclear, chemical or biological weapons proliferation; (11) that Oracle is not required to perform any obligations or incur any liability not previously agreed to; (12) to permit MatrixOne
to audit its use of the Programs or to assign such audit right to Oracle; (13) that Oracle is a third party beneficiary of this end user license agreement; (14) that the application of the Uniform Computer Information Transactions Act is excluded.
Disclaimer of Warranty and Exclusive Remedies
THE PROGRAMS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MATRIXONE AND ORACLE FURTHER DISCLAIM ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT.
IN NO EVENT SHALL MATRIXONE OR ORACLE BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR DATA USE, INCURRED BY YOU OR ANY THIRD PARTY,
WHETHER IN AN ACTION IN CONTRACT OR TORT, EVEN IF MATRIXONE OR ORACLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. MATRIXONE'S AND ORACLE'S ENTIRE LIABILITY FOR DAMAGES HEREUNDER SHALL IN NO EVENT EXCEED
ONE THOUSAND DOLLARS (U.S. $1,000).
No Technical Support
Oracle and MatrixOne technical support organizations will not provide technical support, phone support, or updates to end users for the Programs licensed under this agreement.
Restricted Rights
For United States government end users, the Programs, including documentation, shall be considered commercial computer software and the following applies:
NOTICE OF RESTRICTED RIGHTS
"Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered
subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle Corporation, 500
Oracle Parkway, Redwood City, CA 94065."
End of Agreement
The end user may terminate this Agreement by destroying all copies of the Programs. MatrixOne and Oracle each have the right to terminate the end user's right to use the Programs if the end user fails to comply with any of the terms of this Agreement, in which case the end user shall destroy all copies
of the Programs.
Relationship Between the Parties
The relationship between the end user and MatrixOne and Oracle is that the end user is licensee, MatrixOne is distributor/licensor and Oracle is licensor. No party will represent that it has any authority to assume or create any obligation, express or implied, on behalf of any other party, nor to represent the
other party as agent, employee, franchisee, or in any other capacity. Nothing in this Agreement shall be construed to limit any party's right to independently develop or distribute software that is functionally similar to the other party's products, so long as proprietary information of the other party is not
included in such software.
Open Source
"Open Source" software - software available without charge for use, modification and distribution - is often licensed under terms that require the user to make the user's modifications to the Open Source software or any software that the user 'combines' with the Open Source software freely available in
source code form. If you as end user use Open Source software in conjunction with the Programs, you must ensure that your use does not: (i) create, or purport to create, obligations of MatrixOne or Oracle with respect to the Oracle Programs; or (ii) grant, or purport to grant, to any third party any rights
to or immunities under intellectual property or proprietary rights in the Oracle Programs. For example, you may not develop a software program using an Oracle Program and an Open Source program where such use results in a program file(s) that contains code from both the Oracle Program and the Open
Source program (including without limitation libraries) if the Open Source program is licensed under a license that requires any "modifications" be made freely available. You also may not combine the Oracle Program with programs licensed under the GNU General Public License ("GPL") in any manner
that could cause, or could be interpreted or asserted to cause, the Oracle Program or any modifications thereto to become subject to the terms of the GPL.

SSLUtils
The Apache Software License, Version 1.1
Copyright (c) 2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and
wherever such third-party acknowledgments normally appear.
4. The names "SOAP" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OFUSE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 2000, International Business Machines, Inc., http://www.apache.org. For more information on the Apache Software Foundation,
please see <http://www.apache.org/>.

Sun RPC
Sun RPC is a product of Sun Microsystems, Inc. and is provided for unrestricted use provided that this legend is included on all tape media and as a part of the software program in whole or part. Users may copy or modify Sun RPC without charge, but are not authorized to license or distribute it to anyone
else except as part of a product or program developed by the user.
SUN RPC IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND INCLUDING THE WARRANTIES OF DESIGN, MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE.
Sun RPC is provided with no support and without any obligation on the part of Sun Microsystems, Inc. to assist in its use, correction, modification or enhancement.
SUN MICROSYSTEMS, INC. SHALL HAVE NO LIABILITY WITH RESPECT TO THE INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY PATENTS BY SUN RPC OR ANY PART THEREOF.
In no event will Sun Microsystems, Inc. be liable for any lost revenue or profits or other special, indirect and consequential damages, even if Sun has been advised of the possibility of such damages.
Sun Microsystems, Inc.
2550 Garcia Avenue
Mountain View, California 94043

Tcl
This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee
is required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply.
IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES
THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS
PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the
software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and
others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license.

Xalan
[under Apache License, Version 2.0 above]

Xerces
[under Apache License, Version 2.0 above]

Xerces2
[under Apache License, Version 2.0 above]
 Table of Contents

Preface .......................................................................................................................... 17
Chapter 1. Getting Started.................................................................................... 19
Introduction to Matrix Navigator .............................................................................. 19
Beginning a Matrix Navigator Session .................................................................... 20
Beginning a Session Using the Web Version................................................... 20
Beginning a Session Using the Desktop Version ............................................. 20
Setting Context ................................................................................................ 21
Changing Session Context .............................................................................. 22
Changing User Password ................................................................................ 22
Setting Preferences ......................................................................................... 23
Using the Matrix Navigator Interface ...................................................................... 26
Set Menu.......................................................................................................... 27
Object Menu..................................................................................................... 28
Edit Menu ......................................................................................................... 30
View Menu ....................................................................................................... 30
Properties Menu............................................................................................... 32
Files Menu ....................................................................................................... 33
Relationships Menu.......................................................................................... 33
Session Menu .................................................................................................. 34
Tools Menu....................................................................................................... 34
Help Menu........................................................................................................ 34
Pop-Up Menus ................................................................................................. 34
Accessing Help ....................................................................................................... 35
Accessing Matrix Navigator Version Information .................................................... 36
Ending a Session .................................................................................................... 37

Chapter 2. Creating and Working with Objects .................................................. 39

Creating a New Object............................................................................................ 39
Defining the Object Type.................................................................................. 40
Defining the Object Name ................................................................................ 41
Defining the Revision Sequence ...................................................................... 42
Defining the Vault ............................................................................................. 42
Defining the Policy ........................................................................................... 43
Creating the Object .......................................................................................... 43
Clones and Revisions ...................................................................................... 45
Defining Object Attributes ................................................................................ 48
Associating an ImageIcon With an Object .............................................................. 49
Grabbing an Image .......................................................................................... 49
Importing an Image .......................................................................................... 50
Printing Objects and Browsers................................................................................ 53
Working with Object Properties............................................................................... 55
Using a Table ................................................................................................... 55
Info Dialog ........................................................................................................ 57
Inspecting Object Properties ............................................................................ 59

Table of Contents 11
 Working with Basic Information ........................................................................ 60
Working with Attributes..................................................................................... 63
Working with Revisions .................................................................................... 64
Looking at Historical Information ...................................................................... 67
Working with Forms ................................................................................................ 68
Viewing and Entering Data on a Form ............................................................. 68
Printing a Form................................................................................................. 69
Changing Ownership for an Object ......................................................................... 70
Reassigning an Object ..................................................................................... 70
Routing an Object ............................................................................................ 70
Delegating Access to an Object .............................................................................. 72
Access Delegation Scenarios .......................................................................... 72
Granting Access............................................................................................... 72
Revoking Granted Privileges............................................................................ 74
Deleting an Object .................................................................................................. 76
Editing the Work Area ............................................................................................. 77
Cutting an Object ............................................................................................. 77
Copying an Object............................................................................................ 77
Pasting an Object............................................................................................. 78

Chapter 3. Finding Objects................................................................................... 79

Overview ................................................................................................................. 79
Searching for Objects.............................................................................................. 80
Initiating a Query .............................................................................................. 80
Using Wildcard Characters .............................................................................. 81
Performing a Simple Query..................................................................................... 82
Indicating the Object Type................................................................................ 82
Indicating the Object Name.............................................................................. 83
Indicating the Object Revision.......................................................................... 84
Indicating the Object Owner............................................................................. 84
Indicating the Vault ........................................................................................... 86
Searching on File Data............................................................................................ 87
Searching on File Content................................................................................ 87
Searching on File Metadata ............................................................................. 88
Refining Your Query................................................................................................ 90
Indicating the Object Properties ....................................................................... 90
Limiting the Number of Objects to Display ....................................................... 97
Using the Expand Option ................................................................................. 97
Replacing or Appending Currently Displayed Objects ..................................... 97
Performing the Search ..................................................................................... 97
Query Strategies ..................................................................................................... 99
Where Clause Guidelines ................................................................................ 99
Modeling Considerations................................................................................ 108
Avoiding Unbounded Queries ........................................................................ 109
Avoiding Large Expands ................................................................................ 109
Object Existence ............................................................................................ 110
Query Instantiation ......................................................................................... 110
Nested Queries .............................................................................................. 110
Working With Saved Criteria ..................................................................................111
Saving Query Criteria......................................................................................111
Using Saved Criteria ...................................................................................... 112

12 Matrix Navigator Guide

 Using Recent Criteria ..................................................................................... 112
Deleting a Query ............................................................................................ 113
Find Like ............................................................................................................... 114
Initiating a Find Like Query ............................................................................ 114
Find Like Constraints ..................................................................................... 115
Expanding Types............................................................................................ 116
Memory .......................................................................................................... 116
Query Menu ................................................................................................... 117

Chapter 4. Using the Visuals Manager ...............................................................119

Overview ............................................................................................................... 119
Creating Visuals.................................................................................................... 121
Creating Any Visual........................................................................................ 121
Creating a New Filter ..................................................................................... 122
Creating a New Cue....................................................................................... 125
Creating an Object Tip ................................................................................... 129
Creating a Toolset .......................................................................................... 132
Creating a Table............................................................................................. 136
Viewing or Editing a Visual ................................................................................... 142
Cloning a Visual .................................................................................................... 143
Using Visuals in Matrix Navigator Browsers ......................................................... 144
Activating vs. Turning On Visuals .................................................................. 144
Activating and Deactivating Visuals ............................................................... 144
Turning Visuals On and Off ............................................................................ 145
Visuals and Views .......................................................................................... 146
Using the Filter Bar ........................................................................................ 147
Optimizing Performance ................................................................................ 148
Viewing Tip Content Instead of Object Titles ................................................. 149
Role-Based Visuals............................................................................................... 150
Accessing the Role Bar.................................................................................. 150
Deleting a Visual ................................................................................................... 152

Chapter 5. Working with Sets............................................................................. 153

Working With Sets ................................................................................................ 153
Defining a New Set ............................................................................................... 154
Saving a Set ......................................................................................................... 155
Opening an Existing Set ....................................................................................... 156
Loading Objects From a Set ................................................................................. 157
Removing Objects From a Set.............................................................................. 158
Deleting a Saved Set ............................................................................................ 159

Chapter 6. Using View Manager......................................................................... 161

Using View Manager to Create Personalized Views............................................. 161
Using View Manager............................................................................................. 163
Creating a New View...................................................................................... 163
Viewing the Content of a View ....................................................................... 165
Editing a View ................................................................................................ 165
Cloning a View ............................................................................................... 166
Deleting a View .............................................................................................. 166
Turning Views On and Off..................................................................................... 167

Table of Contents 13
 Practical Example Using Views............................................................................. 168
Scenario ......................................................................................................... 168
Visuals Used .................................................................................................. 168
Views Used .................................................................................................... 170

Chapter 7. Working with Connections .............................................................. 171

Overview ............................................................................................................... 171
Connecting Objects............................................................................................... 173
Relationship Direction .................................................................................... 173
Selecting Multiple Objects to Connect ........................................................... 175
A Note about Cardinality ................................................................................ 175
Drop Connect........................................................................................................ 176
Connecting Objects Using Drop Connect....................................................... 176
Replacing Objects Using Drop Connect......................................................... 179
Using the Navigator Browser ................................................................................ 182
Using the Star Browser Mode ........................................................................ 183
There and Back.............................................................................................. 184
Using the Indented Browser Mode ................................................................. 184
Adding Details ................................................................................................ 187
Using Paginated Mode................................................................................... 188
Using Other Functions ................................................................................... 191
Reviewing Relationships ....................................................................................... 192
Modifying Connections.......................................................................................... 195
Displaying and Modifying Attributes ............................................................... 195
Change Relationship Type ............................................................................. 195
Freezing Relationships................................................................................... 196
Thawing Relationships ................................................................................... 197
Disconnecting Objects .......................................................................................... 198

Chapter 8. Checking Files In and Out................................................................ 199

Overview ............................................................................................................... 199
Should You Open or Check Out a File? ................................................................ 201
Using the Formats Browser................................................................................... 202
Viewing Formats and Names of Checked-In Files ......................................... 203
Viewing File Basics ........................................................................................ 203
Opening Files for Viewing, Editing, and Printing ................................................... 205
Prerequisites .................................................................................................. 205
Opening Files for Viewing .............................................................................. 205
Opening Files for Editing................................................................................ 207
Printing a File ................................................................................................. 208
Tips for Opening Files for Edit, View, or Print................................................. 209
Checking Files In and Out..................................................................................... 210
For the Web Version Only .............................................................................. 210
Checking In a File .......................................................................................... 210
Checking Out a File........................................................................................ 214
Deleting a Checked-in File ............................................................................. 219
Locking and Unlocking an Object ......................................................................... 220
Locking an Object .......................................................................................... 220
Unlocking an Object ....................................................................................... 221

14 Matrix Navigator Guide

 Chapter 9. Using the Object Lifecycle............................................................... 223
Overview ............................................................................................................... 223
Viewing States ...................................................................................................... 225
Interpreting States Browser Symbols.................................................................... 226
Transitioning From State to State.......................................................................... 227
State Branching and Signatures .................................................................... 227
Satisfying Signature Requirements................................................................ 227
Reviewing Signature Comments.................................................................... 229
Reviewing Signature Access ......................................................................... 229
Scheduling ..................................................................................................... 230
Displaying Access Privileges ......................................................................... 231
Disabling Promotion ....................................................................................... 232
Enabling Promotion........................................................................................ 232
Overriding Promotion ..................................................................................... 232
Promoting an Object ...................................................................................... 232
Demoting an Object ....................................................................................... 233
Completion Warnings..................................................................................... 234

Chapter 10. Using IconMail .................................................................................. 235

Sending and Receiving Information ...................................................................... 235
Distributing Mail Manually ..................................................................................... 237
Sending Mail Manually ................................................................................... 237
Routing an Object .......................................................................................... 239
Receiving IconMail................................................................................................ 241
Working with IconMail .................................................................................... 243
Printing IconMail Messages ........................................................................... 243
Replying to a Message .................................................................................. 244
Forwarding a Message .................................................................................. 244
Deleting a Message ....................................................................................... 244
Sending Mail and Receiving IconMail Automatically............................................. 245

Chapter 11. Annotations and Attachments......................................................... 247

Annotating or Attaching Information to an Object ................................................. 247
Annotating an Object ............................................................................................ 248
Creating an Annotation Object ....................................................................... 248
Creating the Annotation ................................................................................. 250
Controlling Revisions ............................................................................................ 251
Attaching Information to an Object........................................................................ 252
Creating an Attachment Object ...................................................................... 252
Creating the Attachment ................................................................................ 254

Chapter 12. Working With Workflows ................................................................. 255

Working With Workflows ....................................................................................... 255
Creating a Workflow Instance ............................................................................... 257
Starting a Workflow ............................................................................................... 259
Working with Tasks ............................................................................................... 260
Checking IconMail for Tasks .......................................................................... 260
Accepting Tasks ............................................................................................. 262
Editing Task Attributes ................................................................................... 263
Attaching Business Objects to the Workflow.................................................. 263

Table of Contents 15
 Completing Tasks........................................................................................... 265
Managing Workflows............................................................................................. 266
Reassigning the Workflow.............................................................................. 266
Changing Workflow Status ............................................................................. 267
Deleting a Workflow Instance......................................................................... 269
Managing Workflow Tasks .................................................................................... 270
Reassigning Workflow Tasks.......................................................................... 271
Rescinding a Task .......................................................................................... 272
Changing Task Status .................................................................................... 273
Modifying Task Attributes and Attachments ................................................... 274

Chapter 13. Generating Reports .......................................................................... 275

Generating Reports............................................................................................... 275
Creating a Report.................................................................................................. 276
Viewing a Report................................................................................................... 278

Index ............................................................................................................................ 279

16 Matrix Navigator Guide

Preface

This guide is designed as an introduction and learning guide for Matrix Navigator. Matrix
Navigator presents information through graphical representations of functions and data
that you can quickly locate and identify. Hold your mouse pointer briefly over any button
on the toolbar and a small label appears (called a ToolTip) telling you what that button
does. Because you won’t need to waste time trying to remember confusing naming
conventions or typing complex instructions, you may choose to learn Matrix Navigator by
experimenting. In this case, you can use this Matrix Navigator Guide as a reference tool.

Desktop and Web This guide covers both desktop and Web Matrix Navigator applications. The two are very
Versions similar, but where there are differences, the guide describes those differences. The
graphics shown represent the Web version of the application, except for features that are
not available in the Web version.

Before You No matter how you choose to learn and use Matrix Navigator, you should refer to the
Begin… current Program Directory for any changes since the publication of this manual.

17
18 Matrix Navigator Guide
 1
Getting Started

Introduction to Matrix Navigator

Matrix Navigator is a powerful information management system that is flexible enough to

work in any business environment. The system allows your organization to share valuable
intellectual capital by tying people, information, and business processes together across
the organization and around the world.
Each organization can configure how its users interact with Matrix Navigator. Matrix
Navigator uses the schema designed by ENOVIA Live Collaboration Administrators in
the Business Modeler and System Manager applications.
For users, Matrix Navigator offers multi-level control of the information they encounter
with configurable settings so that only the data pertinent to their daily work is shown in a
graphic display with point-and-click usability.

19
 Beginning a Matrix Navigator Session

The procedure for beginning a Matrix Navigator session differs depending on whether you
have the desktop or Web version of Matrix Navigator:
• Beginning a Session Using the Web Version
• Beginning a Session Using the Desktop Version

Beginning a You launch the Web version of Matrix Navigator application from a Web browser, such as
Session Using the Mozilla or Internet Explorer, and use it to access an existing ENOVIA Live Collaboration
Web Version database. Consult your Administrator for the URL that contains the Start Matrix button.

To begin a Matrix Navigator session

1. Start your Web browser as you normally do.
2. Enter the URL provided by your Administrator.
The Matrix Navigator start page appears.

If you are using Internet Explorer and starting Matrix Navigator for the first time after
downloading installation files, the Start Matrix button may not appear. If it doesn’t, exit
your Web browser and repeat steps 1 and 2.

Several links are available at the bottom of the page:

Matrix Navigator Guide opens the first HTML file of this manual.
ENOVIA Home Page brings you to the ENOVIA website.

MQLTcl is no longer supported or packaged with the LiveCollaborationWebNavigator

tarkit. The “MQLTcl83 Extension for Matrix Web Navigator” link is removed from the
web client.

3. With some browsers, before the Start Matrix button becomes available on the start
page, you have to allow the applet to be downloaded by clicking Yes in the Security
Warning dialog.

Microsoft Internet Explorer requires that the browser remain open while running Matrix
Navigator. If you shut down Internet Explorer while Matrix Navigator Web Navigator is
open, Matrix Navigator shuts down.

You can import ENOVIA’s Public certificate to avoid this warning. Contact your
System Administrator and refer to the ENOVIA Live Collaboration Installation Guide
for details.
4. Next, click the Start Matrix button to begin.

Beginning a The way in which you begin a desktop Matrix Navigator session depends upon the
Session Using the platform you are using. On a UNIX system, you can type a command. On a Windows
Desktop Version system, you select a program item from the Start menu or from the Windows desktop.

20 Matrix Navigator Guide

Setting Context When Matrix Navigator first appears, the Session Context window box opens within the
Matrix Navigator browser, as shown below.

The session context identifies you to Matrix Navigator, giving you the appropriate access
privileges as defined by the Business Administrator. When you set user context, a
password may be required. The vault specified in the context setting is used as the default
vault for the objects you create. But you can access other vaults at any time.
You must set a session context when you first enter Matrix Navigator. You can change the
context at any time while working within a session.

To set context
1. When you first enter Matrix Navigator and see the Session Context window, enter
your name in the User box. Depending on your system setup, ENOVIA Live
Collaboration may be case sensitive, so you will need to know exactly how the
ENOVIA Live Collaboration Business Administrator “created” you in Matrix
Navigator.

2. Enter a password (if required, as defined by the Business Administrator) in the

Password box (passwords are always case sensitive).

3. Enter the vault name in the Vault box. Click the ellipse to bring up the Vault
Chooser from which to make a selection.
4. Click OK to set the context.
You are now ready to work with Matrix Navigator. The message bar says “Ready.”

Chapter 1: Getting Started 21

Changing Session To change the context
Context 1. Choose Context from the Session menu.
The Session Context window appears.
2. Complete the window as described above, entering the User name, Password, and
Vault, as appropriate.
3. Click OK.

Changing User When Required

Password
You may be required to create a new password when you first attempt to log into Matrix
Navigator and/or at specified intervals, such as every 90 days. If you are required to
change your password, you’ll see a window similar to the following when you attempt to
log in:

To change your password when required

1. Enter your current password in the Password box. If you don’t have a password,
leave the top Password box empty.
2. Enter a new password in the New Password and Verify Password boxes.
There may be rules about the kinds of passwords you can create. If the new password
you enter violates these rules, the system will tell you, so you can enter a corrected
password.

At Your Discretion
You may add or change your password at any time using the procedure below.

To change your password

1. Choose Password from the Session menu.
The Session Password window appears:

22 Matrix Navigator Guide

 2. Enter your existing password in the Password box. If you do not yet have a password,
leave this box blank.
3. Enter the new password in the New Password box. Then verify the new password by
entering it again in the Verify Password box.
4. Click OK.
The next time you set context, you must use your new password.

Setting Use the Session>Preferences option to configure many frequently-used settings. You can
Preferences reset preferences at any time. Matrix Navigator remembers preferences from one session
to the next. The preferences are written to the enovia.ini initialization file for the desktop
version and to the matrix.properties file for the Web version. For information on
configuring these files, see the ENOVIA Live Collaboration Installation Guide.

To set preferences
1. Select Preferences from the Session menu.
The Session Preference window appears, showing the View tab.

2. To set preferences related to how you view business objects and data, use the View
tab options.
View by—Specifies the default for how Matrix Navigator represents objects: Icons,
Images (ImageIcons), or Names (text only). You can also change the View mode
from the View menu.
Browse by—Specifies the default for how business object data is displayed in the
Matrix Navigator browser: as Icons or in a Details (table) format. You can also
change this from the View menu.
Navigate by—Specifies the default browser mode for the Navigator browser: Star,
Indented, or Details (Indented with table). For the Web version, the paginated option
is also available.
3. To set preferences for opening objects and to choose the default relationship for Drop
Connect, click the General tab.

Chapter 1: Getting Started 23

 Open for—Available on the desktop version only. Specifies the function that occurs
when you double-click on business objects. When you double-click on a business
object, Matrix Navigator launches the view/edit program that has been defined by
your Administrator for the file format. This often requires opening an external
application to access files from other sources that are stored in Matrix Navigator.
Open for Edit is not currently available in the Web version, so double-clicking always
results in viewing the files for the business object.
Drop Relationship—Specifies the relationship type to use by default for connecting
objects. Type any valid Matrix Navigator relationship or click the button on the right
to choose a valid relationship.
4. To set preferences related to checking in and checking out files, click on the Files tab.
These settings are summarized below. For more information on these settings, see
Checking Files In and Out in Chapter 8.

Checkin—You can set Checkin options here so the default behavior is always the
same when external files are added to Matrix Navigator. The following descriptions
explain what happens when each option is checked.
• Append Files—Append Files is selected in the Checkin window. Any files you
check in are appended to existing files. If Append Files is unchecked in Session
Preferences, then Replace Files is selected in the Checkin window.
• Confirm File Replace—If the file or files you are checking in will replace files
in the database, a message appears that lets you confirm the operation.
• Unlock Object—Unlock Object is checked in the Checkin window. The object
is unlocked after checkin so other users can check in files.
• Delete Files—Delete File After Checkin is checked in the Checkin window.
Each file that you check in is deleted from the local location.
Checkout—You can set Checkout options so the default behavior is always the same
when external files are copied from Matrix Navigator to your workstation. The
following descriptions explain what happens when each option is checked.

24 Matrix Navigator Guide

 • Confirm File Overwrite—When checking out a file to a directory that contains
a file of the same name, a message appears that lets you confirm that you want to
overwrite the file.
• Lock Object—Lock Object is checked in the Checkout window. Locking an
object prevents other users from editing files you have checked out.
• Overwrite Existing File—Overwrite Existing Files is checked in the Checkout
window. This means that if you check out a file to a directory that contains a file
with the same name, the local file is replaced with the checked-out file. No
warning is presented unless you check Confirm File Overwrite.
Warn On Higher Revision—If checked, a warning displays when functions are
attempted on an object for which a higher revision exists.
File path—You can set the default checkin and checkout file path. Type any valid
file path for your system or click the button on the right to browse available paths.
To control which toolbars are displayed when you start a Matrix Navigator session
and open browsers, click on the Toolbars tab.

Connect Bar—Check if you want the connect bar displayed by default when you
start Matrix Navigator.
Role Bar—Check if you want the role bar displayed by default when you start Matrix
Navigator.
Filter Bar—Check if you want the filter bar displayed by default when you start
Matrix Navigator.
5. When you have set your preferences, click OK.
If you made changes to view or toolbar settings, the changes take effect for the next
browser you open. All other changes take effect the next time you perform the
corresponding function (checkin, checkout, drop connect, etc.).

Chapter 1: Getting Started 25

 Using the Matrix Navigator Interface

The instructions in this manual assume you are familiar with basic computer operations,
such as: clicking and dragging the mouse; selecting objects; selecting commands from
down menus; using different components of windows; and manipulating windows. Some
components specific to Matrix Navigator are described.
Matrix Navigator browsers and windows display information and request information
from you. Matrix Navigator opens separate browsers and windows for each activity. In
this way, you can manage each task independently. When you first begin a session, you
won’t see any objects in the Matrix Navigator browser until you find or create objects.

Role Bar Filter Bar

Menu Bar
Tool Bar
Toolset
Toolbar

Scroll
Bar

Work
Area

Message Bar Business Objects Size Handle

Matrix Navigator browsers contain the elements described below.

• Role Bar—The role bar provides a drop-down list that contains all roles to which you
are assigned. Selecting a role from this list gives you access to any visuals associated
with the role.
• Filter Bar—The filter bar is to the right of or below the role bar. The filter bar can be
toggled on and off from the View menu. The ellipsis button brings up a Type or
Relationship Chooser, depending on what the displayed filter applies to. Refer to
Using the Filter Bar in Chapter 4 for more information.

26 Matrix Navigator Guide

 • Menu Bar—The menu bar consists of menus containing commands you can select to
initiate Matrix Navigator functions.
• Toolbar—The toolbar consists of buttons that you can click instead of selecting the
corresponding command from a menu.
• Toolset Toolbar—Toolset toolbars contain buttons that execute programs included
in your defined and active toolsets.
• Work Area—The work area displays business objects in your ENOVIA Live
Collaboration database.
• Message Bar—The message bar displays status messages as Matrix Navigator
executes selected functions.
The Matrix Navigator menus (with their associated options) are summarized in the
sections that follow in the order in which they appear on the Matrix Navigator browser,
from left to right:

Tools are included with associated menus/options for easy referencing. When no object is
selected, some tools are grayed out and cannot be used:

When an object is selected, the tools become available:

Set Menu The Set menu offers the following options to open sets and find objects, close the current
Matrix Navigator browser, and exit Matrix Navigator.

Set Menu Options

New Window Opens an additional Matrix Navigator browser.
New Clears the current objects from the working area.
(desktop only)
Opens a previously-saved set. All objects within that set appear in the
Open work area.
Load Loads objects from a saved set. Selecting Load... gives you a radio button
(desktop only) choice to replace or append the objects from the saved set into the current
window.
Save Saves the currently displayed set of objects with a specific name. You can
(desktop only) save a previously saved set using the same name.

Save As Saves the objects in the work area as a set with a specified name.
Delete Deletes a saved set of objects (but not the objects themselves).
Searches the database for objects that meet your search criteria. The
Find found objects display in the work area of the active Matrix Navigator
browser.

Chapter 1: Getting Started 27

 Set Menu Options
Find Like Provides a mechanism for formulating a query based on the properties of
a type. When you select a type, properties specific for the type appear,
allowing you to specify values for the properties you want to search on.
Page Setup Standard windows print setup dialog.
(desktop only)
Print Standard windows print dialog. Prints the current Matrix Navigator
(desktop only) window.

Close Closes the current Matrix Navigator browser.

Exit Terminates Matrix Navigator and returns you to your Web browser or
operating system.

Object Menu The Object menu offers the following options to create a new object or work with existing
objects:

Object Menu Options

New Original Creates a new object defined by its type, name, revision,
vault, policy, and attributes.
Revision Creates a new object which is the next revision of a
selected object.
Clone Creates a new object by using the basic information of an
existing object. For example, cloning is useful when
creating an object that is basically the same as (but not a
revision of) an existing object.
Annotation Connects an annotation (such as a drawing mark-up) to a
(desktop selected object.
only)
Attachment Attaches information (such as an audio comment, note,
(desktop photograph, or video) to a selected object.
only)
Report Generates a report on selected objects. The selected report
(desktop has a defined layout.
only)
Open Edit Opens a file checked into a selected object for editing.
Matrix Navigator launches the edit program that is
(desktop defined in that file’s format.
only)
View Opens a file checked into a selected object for viewing.
The Web browser (or Matrix Navigator) launches the
view application for the selected file format. If no file is
checked in, the view application does not launch.
Methods Allows you to select a method created by the Business Administrator to
automate tasks.

28 Matrix Navigator Guide

 Object Menu Options
Inspect Provides all of the information about an object in a new window. Displayed
(desktop properties include all basic and attribute information, current state,
only) methods associated with the object type, formats of checked in files, and all
relationships that the object maintains.
Change Enables you to change the type, name, revision, vault, and/or policy of a
selected object. You can also import a graphic image to represent the object
from this window.
Delete Permanently deletes selected objects from the database. Use this option
carefully!
Image Creates an ImageIcon of a selected business object. ImageIcons can be
(desktop created either manually by using a raster image clip tool or automatically
only) by using color printing routines for the source applications.
Grab Uses a raster image clip tool to create an ImageIcon. This
option is available only on UNIX platforms.
Import Imports images created with other applications.
Print Initiates the print process for an application associated with a file that is
(desktop checked in.
only)
Workflows Displays the workflow browser, showing workflows that you own. This
(desktop function allows you to examine tasks included in the workflow.
only)

Mailbox Displays IconMail (an object with a message attached) and TaskMail (an
activity assigned to you within a workflow) received. You can access
IconMail messages, as well as any related objects and files, from the
mailbox. You can also access task assignments. The button’s icon changes
to an open mailbox when you receive a new, unread message or task.
Send Creates and distributes IconMail (an object with a message attached) to
users that you specify. The system may also send IconMail automatically
based on an object’s policy when the object is in a specific state in its
lifecycle.
Reassign Changes the ownership of a selected object from one user to another,
provided the policy governing the object permits the reassignment.
Route Reassigns the selected object and sends IconMail to that user in one step.
Grant Provides specified accesses to a selected object for a named user.
Revoke Removes specified accesses to a selected object for a named user.

Chapter 1: Getting Started 29

Edit Menu The Edit menu enables you to select and manage objects using the following options:

Edit Menu Options

Cut Removes selected objects to a temporary storage area called a Clipboard.
Copy Copies selected objects to the Clipboard.

If an object is cut or copied to the Clipboard, any object previously in the Clipboard is
cleared and cannot be pasted.

Paste Places objects from the Clipboard into the current browser.
Select All Selects all objects in the browser work area.
Select None De-selects all objects selected in the browser.

Hint: To select most of the objects in a browser, choose Select All from the Edit menu and
then Shift+click the objects you want to de-select.

View Menu The View menu provides options for how objects are displayed in a browser:

View Menu Options

Icon Displays objects in the current browser as icons.
Image Displays objects in the current browser as ImageIcons. When an
ImageIcon for an object is not available, Matrix Navigator displays the
object as an icon.
Name Displays objects in the current browser as text information only: the object
name, type, and revision.
Title Returns the display to the standard title—which includes the object type,
(Web only) name, and revision— after choosing View >Tip.

Tip Replaces the standard title—which includes the object type, name, and
(Web only) revision—with the content of any tips that are currently turned on from the
View > Tip submenu.
Icons Lists the objects in the current browser in rows, as opposed to listing them
in a table (see Details below). The objects are displayed in the mode set
above (Icon, Image, or Name).
Details Lists the objects in the current browser in the table selected in the
View>Table menu. Objects are displayed in the mode set above (Icon,
Image, or Name).
Role (Web Lists all roles to which the user of the current context is assigned. When a
only) user switches from “Personal” to an assigned Role, the visuals and views
that are associated with that Role become available.

30 Matrix Navigator Guide

 View Menu Options
View Controls the appearance of business objects and relationships inside
Matrix Navigator browsers according to views you create. Views can
include filters, cues, object tips, toolset buttons, and tables. For details on
how to create views, see Using the Visuals Manager in Chapter 4 and
Using View Manager in Chapter 6.
When a view is active, all the options are activated at once.
All displays the default view for Matrix Navigator without any
user-defined options.
The menu lists all views created by the user alphabetically. A check mark
indicates the view is activated. Only one view can be activated at a time.
Filter Bar Toggles the display of the filter bar on the Matrix Navigator browser.
(desktop
only)
Role Bar Toggles the display of the role bar, which displays all roles to which the
(desktop user of the current context is assigned. When a user switches from
only) “Personal” to an assigned role, the visuals and views that are associated
with that role become available.
Filter Lists all filters created by the user alphabetically. When active, a filter
removes specified objects from the work area. Users create filters that
define what objects should be removed from view. A check mark next to a
filter name indicates the filter is active. Multiple filters may be active at a
time. For information on how to create filters, see Using the Visuals
Manager in Chapter 4.
Cue Lists all cues created by the user alphabetically and allows the user to
toggle them on or off. Cues control the appearance of business objects and
relationships in browsers to make certain objects and relationships stand
out visually. A check mark indicates the cue is active. Multiple cues may
be active at the same time.
Tip Lists all tips created by the user alphabetically and allows the user to
toggle them on or off. Tips are information pop-ups that appear when the
user holds the mouse pointer over an object or relationship. A check mark
indicates the tip is active. Multiple tips can be active at the same time. Tips
display in the order in which they are activated.

Chapter 1: Getting Started 31

 View Menu Options
Table Lists all tables created for the user alphabetically and allows the user to
select the table to use when in Details mode. Selecting a table changes the
browser to Details mode and lists the objects in the table. A check mark
indicates the table is active. Only one table can be active at any one time.
Tools Lists all toolsets created for the user alphabetically and allows the user to
toggle them on or off. Toolsets contain buttons to execute programs,
methods and/or wizards from a special toolbar. A check indicates the
toolset is active. Active toolsets are listed in the Tools menu and are also
available from the toolset toolbar.
Views Opens the View Manager to create, edit, view, clone, and delete views
defined by the user. For information, see Using View Manager in
Chapter 6.
Visuals Opens the Visuals Manager to create, edit, view, clone, and delete visuals
defined by the user. Visuals include filters, cues, tips, tables, and toolsets.
For information, see Using the Visuals Manager in Chapter 4.

Properties Menu The Properties menu contains options that allow you to see information about a selected
object.

Properties Menu Options

Forms Displays forms associated with an object type. Several forms can be
associated with an object.
Basics Displays general information (other than attributes) about a selected
object.
Info Displays information specified by the column definitions in the active
table, applied to the currently selected object.
Attributes Displays the characteristics (attributes) assigned to the selected object
type. This feature enables you to edit the attribute values, if the
associated policy permits.
States Presents a graphical view of the states of the selected object as defined
by its governing policy. States are displayed in a States browser.
Revisions Displays the revisions of the selected object.

History Displays historical information about all functions applied to the

selected object from the time it was created.

32 Matrix Navigator Guide

Files Menu The Files menu lets you manage files and formats.

Files Menu Options

Formats Lists the formats available for a selected object. The system displays
formats in an indented configuration, displaying any files checked in
below its format.
Checkout Copies file(s) from a selected object to a specified destination directory
on your system (if checkout access is allowed).
Checkin Copies selected files to a selected object in the database (if checkin
access is allowed).
Delete Delete(s) a checked in file(s).
(desktop only)
Lock Prevents another person from editing a file that you have checked out.
Unlock Unlocks an object so that others may access its files.

Relationships The Relationships menu lets you display and manage relationships between objects:
Menu
Relationships Menu Options
Navigator Displays a new window called the Navigator browser. Three modes
are available in the Navigator browser: Star, Indented, or Details.
The Navigator browser opens in the mode you select in the View
menu, but may be changed.
Star Displays related objects clustered around the selected
object in a star pattern.
Indented Displays related objects listed hierarchically on
indented lines beneath the selected object.
Details Displays a table view of connected objects
according to the user’s active table. Objects appear in an
indented format on the left and in the selected table format
on the right. Rows are synchronized between the two so as
the user scrolls, the related table information displays.
Connect Creates and defines a relationship between a selected object and any
number of other objects.
Disconnect Available only from a Navigator browser. Disconnects the selected
object or relationship from the displayed structure.
Freeze Available only from a Navigator browser. Freezes or “locks” a
relationship so that it cannot be disconnected unless first thawed.
Thaw Available only from a Navigator browser. To enable modifications
and disconnections of a frozen relationship, it must be first be
thawed.
Change (desktop Available only from a Navigator browser. Changes the relationship
only) used to connect two objects to another valid, unfrozen relationship.

Chapter 1: Getting Started 33

Session Menu The Session menu enables you to log into Matrix Navigator:

Session Menu Options

Context Identifies you (the user) to Matrix Navigator. Your Administrator set
aside a specific area of Matrix Navigator for your use. This area is
your context—who and where you are within Matrix Navigator.
Context is defined using your name and the vault in which you will
work on business objects.
Password Enables you to change your Matrix Navigator password.
Preferences Tailors the Matrix Navigator application for your work session. You
can indicate the default action for how objects are viewed, browsed,
navigated, opened, checked in, and checked out. You can also turn on a
warning to notify you of a higher version of the object, and the default
path to use when checking files in and out.

Tools Menu The Tools menu, available only for the Web version of Matrix Navigator, displays a list of
all programs and wizards that are part of the active toolset(s) of the logged on user.
Submenus from the toolsets show all programs and wizards contained in the toolset, which
may be selected for execution. Toolset toolbars are also available and may be toggled
from the Views/Tools submenu.

Help Menu The Help menu allows you to see the Matrix Navigator software version and copyright:

Help Menu Option

About Displays information about Matrix Navigator, including the software
version and copyright.
On Matrix Provides access to Matrix Navigator documentation, if it has been
Navigator installed and bound to the application. Additional Help files can also
(optional on be added. Consult the ENOVIA Live Collaboration Installation Guide
desktop only) for more information.

Pop-Up Menus When an object is selected, a right mouse click brings up a menu of commonly-used
functions:

34 Matrix Navigator Guide

 Accessing Help

To access help for the Web version

• From the opening Matrix Navigator start page, click the link for the Matrix
Navigator Guide.

To access Help for the desktop version

• If the administrator has configured the documentation, you can choose On Matrix
from the Help menu.

The options available on the help menu can be configured by the administrator. For
example, On New Features may also be available.

Chapter 1: Getting Started 35

 Accessing Matrix Navigator Version
Information

The Help menu provides information on the Matrix Navigator version.

To check the software version

1. Select About from the Help menu to review information about your version of Matrix
Navigator.
2. After reviewing the information, click Close.

36 Matrix Navigator Guide

 Ending a Session

To end a Matrix Navigator session

• Within Matrix Navigator, select Exit from the Set menu.

Chapter 1: Getting Started 37

38 Matrix Navigator Guide
 2
Creating and Working
with Objects

Creating a New Object

When you start an Matrix Navigator session, you must set the context, which identifies
you to Matrix Navigator. As an ENOVIA Live Collaboration user, you will own the
business objects you create. When you create objects, you should assign values to at least
some attributes—others may be filled in over time, at different states in the lifecycle,
perhaps. You can modify attribute values and basic properties if the policy permits. You
can also reassign or delegate objects if you have the appropriate privileges.
There are three ways to create a new object. You can create a:
• New object by specifying original information.
• Revision of an existing object in a revised (changed) state. Each revision is a distinct
business object.
• Clone using the basic information of an existing object to create the new object.
Cloning is useful when the object that you want to create is basically the same as (but
not a revision of) an existing object.
See Clones and Revisions later in this chapter.
There are two basic steps involved in creating a new object, regardless of whether it is an
original, a clone, or a revision:
1. Define the object by assigning it a type, name, revision, vault, and policy.

39
 2. Assign attributes for the object.
Once you create an object, Matrix Navigator refers to the object using the type, name, and
revision you assigned to it.
Each of the parameters associated with an object enables you to provide information about
the new object. The values you enter define and describe the object.

To create a new, original object

1. Select New from the Object menu.
2. Select Original from the New submenu.
The Original window appears.

3. Assign values as appropriate.

Each parameter and its possible values are discussed in the sections that follow.

Defining the You must assign the object a type previously defined by your Business Administrator.
Object Type Note that each object type is associated with an icon used to represent it graphically in
Matrix Navigator. Each icon is defined by your Business Administrator. For example, the
icon for a Drawing object might be a representation of an engineering drawing, and the
icon for a Change Order object might resemble a folder.

Object Type

The Web version of Matrix Navigator supports gif89a image files only. If the image file for
an icon isn't a gif89a format, the image appears broken or fuzzy.

40 Matrix Navigator Guide

 To assign a type to the object
• If you know the exact object type, you can enter it in the Type box, keeping in mind
that depending on your system setup, ENOVIA Live Collaboration may be case
sensitive.
Or

1. Click .
The Type Chooser appears.

By default, all defined object types are displayed. You can expand the types, or filter
the display by typing a partial type name with a wildcard in the Name text box and
clicking Filter. In the Type Chooser above, the DRAWINGS type is expanded to
show its subtypes.
2. Select an object type in the choose and click Ok.
For example, if you are a designer, you might create an object of type “Drawing.” The
selected type is then displayed in the Type text box in the Original window.
Note that a policy and, if applicable, revision are filled in for you. The Business
Administrator specified this policy and revision sequence when the defining the type.

Defining the You must specify the name of the object you are creating. All objects must have a unique
Object Name name assigned. When the object icon is displayed on your screen, the object name appears
under the object type.

Chapter 2: Creating and Working with Objects 41

 Object Name

Names are case-sensitive and spaces are allowed. You can use complete names rather than
contractions, making the terminology in your system easier for people to understand.
Generally, name lengths can be a maximum of 127 characters. Leading and trailing spaces
are ignored.
You should avoid using characters that are programmatically significant to Matrix
Navigator, MQL, and associated applications. These characters include:
/ \ | * ^ ( ) [ ] { } = < > $ % & ! ? “ ; : ,’ §

Legal characters in XML are the tab, carriage return, line feed, and the legal graphic
characters of Unicode, that is, #x9, #xA, #xD, and #x20 and above (HEX). Therefore,
other characters, such as those created with the ESC key, should not be used for ANY field
in Matrix Navigator, including business object names, description fields, and attributes.

Defining the You can use any valid alphanumeric character for the revision, as long as it is consistent
Revision with the sequence specified in the policy. For example, a policy might specify the
Sequence sequence as:
A, B, C,… or 1, 2, 3,… or I, II, III,….
The revision that you enter must be valid for the policy and appears under the object name
in Matrix Navigator. Note that the revision may have been filled in automatically when
you specified the object type (as described in Defining the Object Type).

Revision

You can type a number or letter in the Revision text box to change or establish a unique
revision for the object.

Defining the Vault You can identify the vault that will contain the created object. A vault is a database
grouping of objects established by your Business Administrator. The current vault is filled
in automatically when you begin the creation procedure for a new object.

To change the vault for the object:

• If you know the exact name of the vault, type it in the Vault text box, keeping in mind
that depending on your system setup, ENOVIA Live Collaboration may be case
sensitive.
Or

42 Matrix Navigator Guide

 • Click and select a vault from the Vault Chooser that appears.

If you did not include a vault when you set context, when you attempt to create a new
object (Object -> New -> Original), the window shows the default vault as
ADMINISTRATION, which is not a valid vault for business object creation. If you bring
up the Type chooser, the system gives a warning message “Vault name is invalid.”
Therefore when creating business objects, if you are not working within a defined vault,
you should specify the vault first. To alleviate the problem, you should always work within
a vault, by including a vault when you set context, or have your business administrator
define a default vault for you.

Defining the Policy Each object is governed by a policy based on its type. The policy defines access rules for
the roles of various people in your organization (such as the ability to check out files,
check in files, delete files, modify attributes, print files, and approve objects). The policy
also defines allowable file formats and its lifecycle.
You must enter a valid policy for the type specified—a policy previously defined by your
Business Administrator. Matrix Navigator does not allow you to specify a policy that does
not govern the type specified. The default policy is filled in automatically when you enter
the type for a new object.

To change the policy of the object

• If you know the exact name of the policy, type it in the Policy text box, keeping in
mind that depending on your system setup, ENOVIA Live Collaboration may be case
sensitive. The policy you type must be usable by the type of object being created.
Or

• Click and select a policy from the Governing Policy Chooser that appears.
Only policies associated with the object type are displayed in the chooser.

Creating the After you enter all the basic information for the new object, you are ready to create the
Object object.

To create the object

• Click Create in the Original window.
The new object icon is displayed in the work area and the Attributes window opens.
You must define the attributes for the new object as described in the section titled
Defining Object Attributes.

Chapter 2: Creating and Working with Objects 43

 New Object

Attributes Window

You receive an error message if a visual produces an error when it is evaluated

against the new object. When using the Web version of Matrix Navigator, the object
is not created. When using the desktop version, you will receive the error message but
the object is still created. To make object creation work as expected, turn off or fix the
problem visual.
Here are two examples of queries in cues that would produce an error when evaluated
against an object.
In the first example, the query is constructed correctly but would produce an error
when evaluated on an object whose policy has NO format at all:
where (default.hasfile == TRUE)
In the second example, the query would produce an error because “schedule” should
be “scheduled”:
where (current.schedule > Jan 1 1999)

44 Matrix Navigator Guide

Clones and It is important to realize the differences between a revision and a clone. The following
Revisions table describes the differences.

Differences/Similarities between Clones and Revisions

Property Clone Revision

Attributes Values are initially the same. A Values are initially the same. A
window appears upon creation so window appears upon creation so
you can change the attributes. you can change the attributes
Files Files may optionally be copied to Files may optionally be referenced
the clone upon creation. from the original until it is
necessary to copy them.
Connections to Depends on clone rules (Float, Depends on revision rules (Float,
other objects Replicate, None) set by Business Replicate, None) set by Business
Administrator. Administrator.
Connection to No implicit connection. Implicit connection may be
original viewed in Revision chain.
History The create entry shows the object The create entry shows the object
from which it was cloned. from which it was revised and
If you copy an object via MQL, original shows that it was revised.
you can optionally include the
original object’s history log.

Revising or Cloning a Structure

When objects are revised or cloned, the rule set in the relationship definition determines
what happens to the connections of the original, as shown in the diagram below:

Chapter 2: Creating and Working with Objects 45

 NONE Object Object Object
A A A
Original Original Revised

Object Object
B B

The revised (or cloned) object has no connection.

FLOAT Object Object Object

A A A
Original Original Cloned

Object Object
B B

The connection shifts to the revised (or cloned) object.

REPLICATE Object Object Object

A A A
Original Original Revised

Object Object
B B

A new connection is made to the revised (or cloned) object. The original connection is left intact.

Creating a Clone
Cloning is convenient when you want to change an object but also retain the original. You
must use a new name for the clone, and you may use any valid revision identifier, but the
type must be the same as the original. When a business object is cloned, any and all grants
are copied to the newly created object.

To create a clone
1. In the work area, select the object you want to clone.

46 Matrix Navigator Guide

 If the object is not currently displayed in the work area, you must find it. See
Searching for Objects in Chapter 3 for more information.
2. Select New from the Object menu, then select Clone.
The Clone window appears. This window is similar to the Original window shown
above, except that the current data for the selected object is displayed.
3. Modify the object name, revision, vault, and/or policy.
4. Uncheck Copy Files if you don’t want to include the original files in the new
revision.
By default Copy Files is checked and so any files contained in the original are copied
to the new object.
5. Click Create.
The new object icon appears in the work area and the Attributes window opens.
6. Assign values to the object’s attributes as described in Defining Object Attributes.
If the original object had any grant access, the cloned object inherits them. Refer to
Granting Access and Revoking Granted Privileges for more information.

Creating a Revision
When an object is revised, the type and name of the original object is used with a new
revision identifier. The revision is either:
• Entered automatically with the next available number in the sequence specified in the
policy; or
• Entered by the user creating the revision.

To create a revision
1. In the work area, select the object you want to revise.
If the object is not currently displayed in the work area, you must find it. See
Searching for Objects in Chapter 3 for more information.
2. Select New from the Object menu, then select Revision.
The Revision window appears. This window is similar to the Original and Clone
windows, with the current data for the selected object displayed.
3. Modify the object name, revision, vault, and/or policy.
4. Uncheck Inherit Files if you don’t want to include the original files in the new
revision.
By default Inherit Files is checked and so any files contained in the original are
initially referenced by the new object, rather than copied. Then, when changes are
made to the file list (or a file’s content) in any revision of an object, these references
are dropped and the files are copied to the appropriate objects in the revision chain.
5. Click Create.
The new object icon appears in the work area and the Attributes window opens.
6. Assign values to the object’s attributes as described in Defining Object Attributes.

Chapter 2: Creating and Working with Objects 47

Defining Object The Attributes window enables you to assign values for the attributes of the newly created
Attributes object. Your Business Administrator may specify any number of attributes for an object
type. For example, a Drawing object might have attributes such as Drawing Type and
Drawn By. The attributes of an Assembly might consist of many more entries.

To define object attributes

1. Type the attribute information in each text box. String attributes (as well as
description fields) have a limit of 2,048 KB. If you expect to enter more data,
consider checking in a file instead.
Or
If there is a drop-down list for an attribute, use it to show all possible values and
select the appropriate choice from the list.
2. If an attribute includes a unit of measure (defined by your administrator with a
dimension), you can type the value and units enclosed in quotes. The system converts
the value to the normalized units. For example, if you enter “3 ft” for an attribute
that uses in (inches) as the default, the saved value is 36.0.
If you do not include a unit with an attribute that has a dimension assigned, it assumes
the value is in the default units for the dimension. Check with your Business
Administrator for more information.
3. When all attribute information is entered, click Modify to accept the entries and close
the Attributes window.

You can click Cancel to discard all attribute entries.

48 Matrix Navigator Guide

 Associating an ImageIcon With an Object

An ImageIcon is a graphical representation of a business object. There are two ways to

capture an image and associate it as an object’s ImageIcon:
• Grab an image from your screen
• Import an existing image file

Associating ImageIcons with objects is available on the desktop version only.

Grabbing an Image When grabbing an image from your screen to be used as an ImageIcon, you must first tell
Matrix Navigator the size of the image in pixels. Matrix Navigator then creates a capture
box of this size, which you drag over the appropriate part of the screen. This captured
image is displayed in the Grab window.
You may need to experiment with the size of the capture box. You can repeat the
procedure until you grab the correct image. The image displayed in the Grab window is
not associated with the selected object until you click OK. Therefore, you can resize and
recapture the image as often as necessary before completing the association.

You can grab an image using the Grab option on the Object>Image menu (as described
in this section) only on UNIX desktop platforms.

To grab an image from the screen

1. Be sure the image that you want to grab (to become the ImageIcon) is displayed on
your screen (perhaps in another window and/or with an application such as a CAD
program).
2. Select the object for which you want to grab an image.
3. Select Grab from the Object>Image menu.
The Grab window opens.
4. Enter the width of the capture box (in pixels) in the Width box.
5. Enter the height of the capture box (in pixels) in the Height box.
6. Click Grab.
7. Hold down the mouse button, drag the capture box to the desired image, and release
the mouse button.
The captured image is displayed on the Grab window.
8. When you have grabbed the appropriate image, click OK to associate the image
displayed in the Grab window with the selected object.
The image becomes an ImageIcon and is displayed with the object when you select
Image from the View menu as shown below.

Chapter 2: Creating and Working with Objects 49

Importing an If you have an existing image in a file, you can import it to associate it with a selected
Image object. The image must be a *.GIF file type.

To import an image
1. Select the object for which you want to import an image.
2. Select Import from the Object>Image menu.
The Import window opens.

50 Matrix Navigator Guide

 3. Locate the image file.
Indicate the directory, as appropriate. Use the horizontal and vertical scroll bars as
necessary.
The images available in the selected directory are displayed in the right portion of the
window.

Matrix Navigator uses the “@” symbol for internal operations. Be sure that none of the
filenames or directories you are accessing to check in files include this symbol.

4. Select the image and click Import to associate it with the selected object.
The image becomes an ImageIcon and is displayed with the object when you select
Image from the View menu.

Chapter 2: Creating and Working with Objects 51

 You can retrieve imported gif images from an object using MQL. Refer to the MQL Guide
for more information.

52 Matrix Navigator Guide

 Printing Objects and Browsers

There are two options for printing in Matrix Navigator. You can:
• Print the complete contents of your active browser;
• Print the files contained in selected objects.
The Print option is available from two menus — Set and Object. The Set>Print option is
used for printing Matrix Navigator browsers, while the Object>Print option prints checked

in files. The print button, is used for printing Matrix Navigator browsers only.

Printing files checked into objects and printing Matrix Navigator browsers is available
for the desktop version of Matrix Navigator only.

When using the print button from the desktop version of Matrix Navigator, a blank page is
always ejected before printing.

Printing Browsers To print the contents of the active browser

1. Select Page Setup from the Set menu to make your page setup choices before
performing the rest of this procedure. This is where you can change the paper
orientation from Portrait to Landscape, or select a different paper source or size.

2. From the Matrix Navigator browser, click or select Print from the Set menu.
The standard print dialog displays.
3. Select the printer, print range, and copies.
4. Click OK.
The current contents of the browser prints in the selected browser format (Icon,
Image, Name and Icons or Details).

If you are using UNIX and a printer is not defined, a Print command from Matrix
Navigator causes Matrix Navigator to crash. See your UNIX system administrator to set
up the printer using OS administrator tools.

Printing Object Printing files checked into objects and printing browsers is available for the desktop
Files version of Matrix Navigator only.

You must have read access to an object in order to print its files. Access to the software
application defined in the file’s format is also required.

To print the files checked into an object(s)

1. Select the object(s) whose files you wish to print.
2. Select Print from the Object menu. The Print - Objects window appears with the
objects you selected.

Chapter 2: Creating and Working with Objects 53

 3. Click Print to print the files.

If a higher revision of the selected object exists, Matrix Navigator warns you and enables
you to continue with the old revision or cancel the operation.

54 Matrix Navigator Guide

 Working with Object Properties

Matrix Navigator provides several ways to look at the properties of an object. For any
selected object, you can display:
• Details about the object using a table; if the cell is editable, you can change
information
• Basic information (other than attributes)
• All the properties of an object using Object Inspector (desktop only)
• Attributes (characteristics); if the policy permits, you can edit the object’s attributes
• Revisions
• History of all functions that have been applied to the object from the time it was
created
You can look at object properties using the toolbar buttons and menus. You can also use
the right-click menu to access most options as shown in the example below.

Using a Table Tables are created as described in Creating a Table in Chapter 4. Use tables for:
• editing attributes of more than one object;
• reviewing and sorting data
• printing data
When a table is displayed, the objects that are in the browser are placed in the first column
of the table, and the column expressions are evaluated on each object to fill in the rest of
the table cells. In the table definition, columns that display descriptions or attributes can
be specified as editable. When a column is editable, the contents of each cell in the
column can be modified, provided the user has modify attribute access in the policy, as
well as on the attribute.

To display objects in the active table

• Click or click Details from the View menu.

Chapter 2: Creating and Working with Objects 55

 The system displays the objects in the table selected in the Visuals Manager.

If Details mode is selected and no table has been activated or no columns have been
added to the active table, scrolling is disabled. You must have a table selected at all times
to use the Details mode. If you are not provided with a default table when you begin using
Matrix Navigator, create one using the Visuals Manager or ask your Business
Administrator for assistance.

A progress window may be displayed when switching to Details mode from the Matrix?
(flat) or Navigator browsers depending on the amount of data to be loaded. This progress
dialog provides a Cancel button, allowing you to interrupt the operation at any point. If
interrupted, Matrix Navigator displays the objects that have been loaded so far.

To switch between tables

• Select the table you want to switch to from the Tables submenu of the View menu.
Switching tables allows you to view different information about the same objects with
a single mouse-click.

To modify the contents of an editable column

1. Find the objects you wish to modify.

2. Click or select Details from the View menu to display the active table. Or select a
table from the Tables submenu of the View menu.
3. With the table displayed, double-click in the cell you wish to edit (if using the desktop
version, only a single click is needed). If the cell contains a long text string, it may
wrap to fit on the screen with scroll bars provided for the cell. If an attribute has
defined ranges, they are displayed in a list.

4. Make your changes as needed.

5. To commit your changes, click any other cell or press Enter.
The table (as well as the object’s attribute) is updated to reflect the change.
To cancel your changes before committing them, press the Escape key.
Refer to More About Cell Settings in Chapter 4 for more information on the settings
influencing an editable cell’s characteristics.

56 Matrix Navigator Guide

 Also, if you make modifications to an object from either the Attributes or Change
windows, or from a form, during the same Matrix Navigator session, the table is updated.
The system also tracks and updates changes to object states as well as ownership
reassignments. For example, if a table has columns displaying the current state and owner,
the table immediately reflects promotions and reassignments.
By default, the objects in a table are listed alphabetically by type, name, and revision.
Tables provide the ability to sort data on the contents of any column, in either ascending or
descending order.

To sort objects in a browser by column content

• Click on the heading of the column you want to sort by.
The system sorts the objects on the left in ascending order (a to z, 0 to n) according to
the data in the selected column. To sort in descending order (z to a, n to 0), click the
column heading again. A triangle “arrow” appears in the column to indicate on which
column the information is sorted as well as if it is an ascending or descending sort.

To print the contents of a table (desktop version only)

1. Display the objects in the table you want to print.

2. Click .

Info Dialog In the Web version of Matrix Navigator, the Info dialog shows information specified by
the column definitions in the active table, applied to the currently selected object. The Info
Dialog is available if you have an active table; however, you do not need to be in the table
view mode.

If you select the Info dialog without having an existing table, the error message “No active
table” is displayed. You must create a table using the Visuals Manager or ask your
Business Administrator for assistance.

The Info dialog is similar to the Attributes and Basics windows.

Chapter 2: Creating and Working with Objects 57

 Notice the following:
• The window’s title includes Type, Name, Revision, and name of table used.
• The column headers in the active table define the labels for the fields.
• Fields representing ranged attribute values are drop-down lists.
• Fields are either single-line or multi-line (with scrollbar) as appropriate.
• Fields for attributes and description are editable if the user has appropriate access and
the table columns are defined as editable.
• Modify and Close buttons are available.
One Info dialog is opened at a time. Selecting another object changes the contents of the
Info dialog to display information for the newly selected object. If Edit> Select All is
used, information about the first selected object (top/left-most) is displayed. When you
change the active table, the fields and contents of the Info Dialog are also changed to that
specified by the new table for the currently selected object.

To use the Info dialog

The Info dialog is only available on the Web version of Matrix Navigator.

1. Select an object.

2. Click on the toolbar. The Info window is displayed, using the active table to
define its contents:

58 Matrix Navigator Guide

 3. Modify the fields if needed.
You may only modify fields if you have the appropriate permissions.
4. Click Modify to accept the changes. The window will remain open.
5. Click Close to close the window and return to the parent browser.

Inspecting Object The Object Inspector is available in the desktop version of Matrix Navigator only.
Properties
The Object Inspector provides all of the information about an object in a new window.
The properties displayed include all basic and attribute information, current state, methods
associated with the object type, formats of checked in files, and all relationships that the
object maintains. Attributes defined as “hidden” are displayed in the Object Inspector
even though they do not appear in the Attribute chooser or in the list of attributes for the
object.

If you do not have read access to an object, the Inspector window will not be displayed.

To inspect an object’s properties

1. Select the object for which you want to display properties.
2. Select Inspect from the Object menu, or right-click and choose Properties>Inspect.
The Object Inspector opens.

Chapter 2: Creating and Working with Objects 59

 The grantee field is empty if the object has not been granted. The Object Inspector
will not show specific grants if there are multiple grants on an object, but indicates
<multiple grants>. All the other fields associated with the grant, i.e., grantor,
granteeaccess, and granteesignature, will be blank.
3. When you are finished, click Close.

Working with The Basics window displays general information (other than attributes) about a selected
Basic Information object. This information includes:
• The object’s type icon.
• The object’s ImageIcon (small raster image), if it exists.

60 Matrix Navigator Guide

 • The vault in which the object is stored.
• The policy governing the object.
• The owner of the object.
• The grantee of the object, if it has been delegated.
• The person that locked the object, if it is locked.
• The date the object originated.
• The date the object was last modified.
• A description of the object.

You must have read access on an object to display basics for it. You must have modify
access to make changes to basics.

Displaying Basics for an Object

There are two ways to display basic object information. The procedure below describes
both methods.

To display basic information for an object

1. Select the object for which you want to display information.
2. Indicate that you want to display basic information in one of two ways:

Click .
Or
Select Basics from the Properties menu.
In either case, the Basics window appears.

Chapter 2: Creating and Working with Objects 61

 The grantee field is empty if the object has not been granted. The Basics Dialog will
not show specific grants if there are multiple grants on an object, but indicates
<multiple grants>.
3. Click Close when you are finished reviewing basic information.

Changing an Object’s Basics

If you have modify access to an object, you can change the object’s type, name, revision,
policy, or vault from the Change Object window. To change the owner, see Changing
Ownership for an Object. To change the description, see Working with Attributes. Other
basic fields cannot be modified by users.
Note that you can make changes to object properties only as the governing policy permits.
It is important to note that the rules governing the creation of business objects and
connections (e.g. definitions of type, relationship type, policy, etc.) are only enforced at
the time creation. These rules will be ignored during later modifications of those business
objects and connections.
For example, changing the type of business object on one end of a connection will ignore
the type restrictions defined on the relationship. This behavior is allowed to support a
dynamic modeling environment.

To change basic information of an object

1. Select the object you want to change.
2. Select Change from the Objects menu.
The Change window opens.

3. In the Change window, change object properties as required.

Type—Redefines the kind of business object. Matrix Navigator attempts to match
attribute values between the original type and the new type. However, because types
may be completely different, you may lose information with this change. Values of
original attributes that are not part of the new type definition are lost. New attributes
are added with their default values or with no value at all.
Name—Changes the name of a selected object. All of the connections, attributes, and
files of the original object are maintained.
Revision—Changes the revision of a selected object. Note that you can change the
revision only if you change the object name. If you attempt to change the revision
without changing the name, an error message appears.

62 Matrix Navigator Guide

 Vault—Changes the vault in which the object is stored but does not affect the
location of any files checked into the object.

A business object can appear to have two id's if it moves from one vault to another.
However, there is only one real id (in the current vault).

ENOVIA Live Collaboration keeps the record in the old vault to redirect to the
record in the new vault to avoid the following errors for programs that may continue
to operate on the object with the old id to complete their task:
‘business object stale’ and 'business object id not found'

Query for the object via Type Name Rev Vault will not return these errors.

The old records are cleaned during the original vault cleanup.
Policy—Changes the policy governing the object. The policy can be selected from a
list of policies valid for the object type. Matrix Navigator attempts to match the new
policy states and signatures to maintain the information contained in them.
When the current state of the original object has the same name as a state in the new
policy, the current state, scheduled and actual dates, approvals, and approver
comments are maintained. However, if the new policy does not contain a state having
the same name as the current state, when the policy is changed, the current state of the
object defaults to the first state in the new policy and all signatures from the old
policy are lost.

Matrix Navigator gives no error message or warning if a change in type or policy will lose
existing data. Use caution when changing types and policies.

If you change an object’s policy you may also inadvertently change the store used by
the object. In this case, newly checked in files will be kept in the new policy's store. If
the object contained it’s own files before the policy was changed, they will stay in the
old store, until/unless they are replaced during a subsequent checkin.
However, the old store will still be used in the case where another object contains a
reference to files in the object that now uses a different store. When the time comes to
for the reference to become an actual file (as when the file list changes between the 2
objects) the file copy is made in the same store the original file is located in.
4. Click Change to save the changes or Cancel to close the window without making
changes.
From the Change window for the desktop version, you can also grab an image or import
an image to associate with the object. Refer to the section Associating an ImageIcon With
an Object earlier in this chapter.

Working with Attributes depend on the definition of the object type. Your Business Administrator may
Attributes specify any number of attributes for an object. For example, a drawing type object might
have three attributes: description, title, and sheet count. The attributes for a component
type object might consist of a description, finish, material, weight, cost, etc. However,
each drawing or component instance will most likely have different values assigned to its
attributes.

Chapter 2: Creating and Working with Objects 63

 The Attributes window displays the attribute values assigned to the selected object. If you
have modify access to the type and attribute, you can change the values. There are two
ways to see an object’s attributes. The procedure below describes both methods.

You must have read access to an object to bring up its Attributes window and modify
access to edit the values.

To display and modify the attributes of an object

1. Select the object for which you want to display attributes.
2. Indicate that you want to display attributes in one of two ways:

Click .
Or
Select Attributes from the Properties menu.
In either case, the Attributes window appears. For example, if you work in
manufacturing, you might review the attributes of a part to determine the lead time:

3. To modify an attribute, enter a value in the text box for the attribute you want to
change.
Or
If there is a drop-down list for an attribute, use it to show all possible values and
select the appropriate choice from the list.
4. Click Modify to confirm the modifications and close the window. Use Close if you
haven’t made any changes, or wish to cancel the changes you entered.

Working with If you have read access to an object, you can view its revision chain.
Revisions

64 Matrix Navigator Guide

 To view revisions
1. Select the object for which you want to display revisions.
2. Indicate that you want to display revisions:

Click .
Or
Select Revisions from the Properties menu.
The Revisions window displays all revisions of the object.

3. Click Close when you are finished reviewing the revision chain.

Fixing a Revision Chain

These instructions apply to the desktop version of Matrix Navigator only.

At times, revisions may be in the wrong order in the revision chain. This can occur for
several reasons, such as when more than one revision is created and worked on at the same
time, and the later revision is completed before the earlier revision. For example, suppose
you have this revision chain:
Widget wid001 A = the original revision
Widget wid001 B = a revision to improve performance
Widget wid001 C = a revision to reduce weight
Work begins on revisions B and C expecting that B will be completed and release first, but
in fact, work on C is completed and released first. You now want to switch revisions B and
C to get:
Widget wid001 A = the original revision
Widget wid001 B = a revision to reduce weight
Widget wid001 C = a revision to improve performance
Use the procedure below to rearrange revisions.

Chapter 2: Creating and Working with Objects 65

 Revisions in general should have the same Type and Name. Dragging objects into a
Revision chain that are not of the same Type and/or Name would most likely be
unexpected by integrations or other automations that may be in place.

To fix a revision chain

1. Change the revisions of the objects such that they are sequential, using the Change
option from the Object menu. Note that Matrix Navigator does not allow you to
change only the revision, so you have to change the name as well. For example, make
changes as follows:
a ) Change Widget wid001 B to Widget wid001X C
b ) Change Widget wid001 C to Widget wid001X B.
c ) Change both Widgets again, removing the 'X's from the object names.
At this point revision B refers to the revision to reduce weight, and revision C refers
to the revision to improve performance.
2. From the Revisions window, you see the revisions in the order A C B. Drag and drop
revision C onto revision B to change the revision order to A B C. Note that you can
only drop an object onto the end of a revision chain.
You have now switched the meaning of B and C, and re-ordered the revision
sequence to put the (new) B before the (new) C as desired.
3. If a “revision” (i.e. same type and name) of an object does not appear in the Revisions
dialog, users may have created a new, original object, instead of a new revision.
These situations can be remedied by dragging objects from another browser into the
Revisions dialog, onto the last object in the revision chain. You can then rearrange the
objects as needed.

A note about files

With regard to an objects files, there are three possible “flags” on an object:
• An object can contain its own files that a user checked into it.
• An object can reference files from a previous revision that had files checked into it.
• An object can not contain nor reference any files.
When fixing revision chains, be aware of the following behavior with regard to file
content:
• If the dragged object has its own files, it keeps them. If these files were referenced by
newer revisions in the former revision chain, the reference is removed. If the object is
then moved to another spot in the new revision chain, later revisions that reference an
earlier revision’s files, will now reference the new object’s files.
• If the dragged object comes from another revision chain and references files from a
previous revision, the file reference is moved to the next previous revision that
contains files in the new revision chain (if there is one).
• If the dragged object had no files or file references, it continues to have none.
Because of these complexities, it is recommended that when fixing revision chains, the
objects do not contain files, or all objects in both revision chains contain their own files.

66 Matrix Navigator Guide

Looking at An object’s historical information includes:
Historical • The type of activity performed on the object, such as create, modify, connect, and so
Information on.
• The user who initiated the activity.
• The date and time of the activity.
• The object’s state when the activity took place.
• Any attributes applicable when the activity took place.

You can only see the history for objects to which you have read access.

To view an object’s history

1. Select the object for which you want to display history.

2. Click .
Or
Select History from the Properties menu.
The History window appears.

3. Use the filter bar to search the history record for the logs you are interested in. For
example, type *Smith_John* or *promote* in the Name box and click Filter to
display logs performed by Smith_John or to list the logs of all promote operations. Be
sure to include the * wildcard character.
4. Click Close.

Some events recorded in history before Matrix Navigator version 6 appear to be missing
information. For example, version 6 added “old” values for modify events so older entries
show “was:” with a null value.

Chapter 2: Creating and Working with Objects 67

 Working with Forms

A form is a window in which information related to an object is displayed. Each form is

designed by your Business Administrator and associated with an object type. A form
might include information such as attributes and expressions. An object may have several
forms, each displaying different information about the object.

Viewing and To display and enter information on a form

Entering Data on a 1. Select the object for which you want to display a form.
Form
2. Select Forms from the Properties menu.
The Forms window appears.

You can also open a form by right-clicking on the object and selecting the named
form from the Properties>Forms submenu. The form you select appears
immediately in Edit mode with an OK button at the bottom. If you opened the form
this way, you can skip the next step.

3. To edit the form, select a form and click or select Edit from the Form menu.
Or

To view the form, select a form and click or select View from the Form menu.
The Form window opens for the selected object.
4. Edit the form and click Modify to confirm the changes.
Only certain information can be edited on the selected form, depending on how the
form was designed by your Administrator, as well as your access privileges.

68 Matrix Navigator Guide

Printing a Form If a form is too large to print on a single piece of paper, the system scales it down to fit.
Scaling may result in reduced clarity for some fonts.
When printing to 8.5 x11 inch paper, scaling occurs if the height or width exceeds the
following dimensions:

Optimum Form Dimensions for Printing using the

Web version

Unit Width Height

Picas 75 64
Points 573.65 768

To print a form
1. Bring up the form as described in the previous section.
2. Click Print.
On Windows, the standard Print dialog opens allowing you to select a printer, number
of pages, and number of copies before sending it to the printer. On UNIX, the form is
sent to the default printer.

When using the print button from the desktop version of Matrix Navigator, a blank page is
always ejected before printing.

Chapter 2: Creating and Working with Objects 69

 Changing Ownership for an Object

Reassigning an If an object policy permits ownership reassignment, you can change the ownership of a
Object selected object from one user to another. Note that you can reassign an object to a person,
group, or role.
For example, if you are a designer who is leaving for a two-week vacation, you may need
to permit another designer to make changes to drawings that you own.

To reassign ownership of an object

1. Select the objects to reassign.
2. Select Reassign from the Object menu.
The Reassign window opens.

3. Type name of the new owner in the To box.

Or
Click the ellipsis button and select the person, group, or role from the User Chooser.
4. Click Reassign to change the ownership.

Routing an Object If an object policy permits reassignment of ownership, you can use the Route option to
send IconMail to a user and change the ownership of the selected object to that person in
one step.

To route an object
1. Select the objects to route. Two were selected in the example below.
2. Select Route from the Object menu.

70 Matrix Navigator Guide

 3. Type the name of the new owner in the To box.
Or

Click and select the person, group, or role from the User Chooser.
4. Enter the Subject and Message.
5. Click Route.

Chapter 2: Creating and Working with Objects 71

 Delegating Access to an Object

Managers and team leaders often have a need to delegate responsibilities to subordinates
or peers. These delegates (“grantees”) may not have the kind of global authority that the
manager has, so the manager may use access delegation to allow the person to accomplish
the assigned tasks. Access delegation is a way of granting specific accesses for a business
object to a person or group that would not ordinarily have them based on the governing
policy. The manager or “grantor” may only provide those privileges for which s/he is
authorized. Grantors and others with “grant” access may revoke the delegated privileges at
any time.
As the object goes through its lifecycle, if the grantor no longer has a privilege, the grantee
loses it as well. For example, assume a manager has checkout access in state1 of an object
and not in state2. If the manager grants checkout access to a grantee, the grantee will be
able to check out only while the object is in state1, unless, of course, the grantee has that
access independently.
Grantee and grantor are basic properties of an object. This means that:
• they are selectable
• from MQL, they are printed when a print bus command is issued
• they show up in the Basic properties list from Find/Where clause window
The history log for events performed by virtue of a delegated access indicates both the
grantee and the grantor. The grantee is listed as the user, with an additional comment at
the end of the entry indicating the grantor. For example:
modify - user: danny time: Wed Apr 14, 1999 8:53:06 AM state:
state1 description: Modified by danny for - user: besser

Access Delegation There are various times in the lifecycle of an object when a person would want to grant
Scenarios accesses on an object to another user while not changing the owner of the object. For
example:
• A manager is the owner of an object. He thinks one of his employees has the right
skills for solving the problem described in the object and so would like to assign it to
him. But the manager also wants to be aware of the project’s progress, so he does not
want to completely reassign the object to him.
• A project leader owns an object, and team members have a group access. However,
one member of the team requires an additional access not allowed to the team, so the
project leader/owner grants that access to the team member without reassigning it.
• A Purchasing Agent wants to get a quote from a vendor for a certain item. The
Purchasing Agent wants to give the vendor check-in access so the vendor can check
in the quote. The Purchasing Agent can grant only the required accesses for that one
object.

Granting Access Any person can grant their accesses on an object to any other person or group as long as
the person has “grant” access. The grantor is allowed to delegate all or a subset of his/her
accesses on the current state. The accesses that a person may grant are a combination of:

72 Matrix Navigator Guide

 • those given to the grantor as part of any user, group, and role accesses assigned in the
current state
• those given as part of the Public access assigned in the current state
• those given in access rules related to programs, forms, attributes, and relationships.

Users cannot grant the grant access itself. The intent is to provide just 1 level of
delegation. Although including grant in the list of accesses will not fail, the grantee of the
grant access will not be able to grant, unless s/he already has grant access.

Any accesses denied on a grantor’s person definition may never be granted to another
user, since the grantor never has those privileges. However, a grantee may be granted
privileges via delegation that are denied by his/her person definition.
Also note that a grantee can be a person, group or role, while an owner can be any kind of
user—a person, group, role, or association.

To grant access to a business object to another user

1. Select the object for which you want to grant access.
2. Select Grant from the Object menu.
The Grant window opens.

If the object is already delegated, the grantee’s name and accesses are shown. Any
changes made will overwrite and not add to the granted accesses of the object.

If the object contains multiple grants, the Grant window will show the following text at the
bottom of the dialog:

Note: One or more objects contain multiple grants.

All buttons but Cancel will be disabled.

If multiple grants are allowed and an object already has one grant, attempting to add
another grant may result in either of the following:
• if you are the existing grantor:
You will be allowed to edit the grant.

Chapter 2: Creating and Working with Objects 73

 • if you are not the grantor on the object:
You will NOT be allowed to edit the grant. The To field will be disabled but the
Access and Signature fields are enabled. Access and Signature are enabled only
so you can see what has been currently set. Grant is also disabled as a result. In
this case, the following error message is displayed:
One or more of the objects selected already has a grant on it. You are using
a version of ENOVIA Live Collaboration that supports 'Multiple Grants'.
This feature is however not supported in the GUI. Use MQL or the ENOVIA
Live Collaboration Studio Customization Toolkit to grant.
3. Enter the name of the user to whom you wish to grant access. If you are unsure of the
exact spelling of the name in the database, click next to the To box to select the
user.

4. Choose to bring up the Edit Access window:

Check and uncheck accesses as appropriate. You may select accesses that are not
valid in that state in order to grant them if you do have them in a future state. For a
description of each access, refer to the Business Modeler Guide. Click OK when
finished.

Users cannot grant the grant access itself. The intent is to provide just 1 level of
delegation. Although including grant in the list of accesses will not fail, the grantee of the
grant access will not be able to grant, unless s/he already has grant access.

5. If needed, check the Signature box, to allow the grantee to approve, reject, or ignore
the signatures on the selected business object for which the grantor is authorized.
6. Click Grant. The grantee now has the privileges granted on the selected object.

Revoking Granted Even if the grantor no longer has delegate access (for example, if the object was promoted
Privileges or demoted to a state where the grantor does not have delegate access), the grantor and
users that do have grant access may revoke the granted privileges by “revoking” access to
the object.

To revoke access to an object

1. Select the object.

74 Matrix Navigator Guide

 2. Select Revoke from the Object menu.
If there is only one grant, the Revoke dialog will be enabled.
The privileges are now revoked from the grantee.
The Revoke window is disabled when there are multiple grants on an object.
However, there is an indication that the object has multiple grants and a user would
have to use MQL or the ENOVIA Live Collaboration Studio Customization Toolkit
to revoke the object.

Chapter 2: Creating and Working with Objects 75

 Deleting an Object

You can delete one or more selected objects from the database, if you have the appropriate
access privilege. For example, if you are a designer, you might delete a drawing because it
is obsolete and no longer needed.
Before ENOVIA Live Collaboration removes objects from the database, they are first
disconnected from any related objects so that the disconnect event is recorded in their
history.

To delete an object
1. Select the object or objects you want to delete.
2. Select Delete from the Object menu.
The Delete window appears and shows the type, name, and revision of each object in
turn.

DELETE WITH CARE: Once you delete an object, you cannot recover it. You can
click the Cancel button to close the window without deleting the selected object.
3. Click the appropriate button:
• Yes: Delete the object whose type, name, and revision is displayed, and refresh
the display to show the type, name, and revision of the next selected object. The
object is removed from the database.
• No: Skip the object whose type, name, and revision is displayed— that is, do not
delete it, and refresh the display to show the type, name, and revision of the next
selected object.
• Yes to All: This button is available only in the desktop version. Clicking this
button causes ENOVIA Live Collaboration to sequence through and delete all
the remaining selected objects without additional confirmation dialogs. As the
objects are deleted, their type, name, and revision's are displayed in the
confirmation dialog. All of these deletions are done within a single transaction,
so if an error occurs in the course of deleting any one of the objects, the entire
transaction can be reversed. That is, any error in the deletion of any of a set of
multiple objects will result in no deletions at all.
• Cancel: Used at any time, it will exit the dialog without deleting any additional
objects. NOTE: The cancel button is not an undo button. Objects deleted using
Yes prior to using Cancel stay deleted.

76 Matrix Navigator Guide

 Editing the Work Area

The Edit menu provides functions that enable you to:

• Cut a selected object(s) from the work area
• Copy a selected object(s) from the work area
• Paste objects into different browsers
The Cut, Copy, and Paste options use the Matrix Navigator Clipboard, which is a holding
place for the object. If an object is cut or copied to the Clipboard, any object previously
placed on the Clipboard is cleared from the Clipboard and cannot be pasted. When you are
in the Details browser mode, you cannot cut or copy objects, but you can paste them from
other browsers.

Cutting an Object The Cut option removes the selected objects from the current browser and places them on
the Matrix Navigator Clipboard. It does not remove the object from the database.

To cut an object
1. Select the object to cut.
You can select more than one object by pressing and holding the Shift key while
clicking on each object. Or, you can select all objects by selecting Select All from the
Edit menu.
2. Select Cut from the Edit menu.
The selected object is cut from its current location and placed on the Clipboard.
Refer also to the description of the Paste feature, below.

Copying an Object There are two ways to copy an object:

• Drag a selected object from one browser and drop a copy of it into another browser.
You may drag and drop only one object at a time.
• Use the Copy option on the Edit menu. This places an identical copy of the selected
object in the Matrix Navigator Clipboard.
In both cases, the selected object is copied and not removed from its original location.

To copy an object using the Clipboard

1. Select the object to copy.
You can select more than one object by pressing and holding the Shift key while
clicking each object. Or, you can select all objects by selecting Select All from the
Edit menu.
2. Select Copy from the Edit menu.
A copy of the selected object is placed in the Clipboard.
Refer also to the description of the Paste feature.

Chapter 2: Creating and Working with Objects 77

Pasting an Object The Paste option copies an object from the Clipboard to the current browser. The object
remains in the Clipboard until something else is cut or copied. You can paste the object
multiple times.

To paste an object
1. Activate the browser onto which you want to paste the object that currently resides in
the Clipboard.
2. Select Paste from the Edit menu.
The object is placed in the work area of the current browser.

78 Matrix Navigator Guide

 3
Finding Objects

Overview

After setting context in Matrix Navigator, one of the first things you’ll want to do is access
the objects with which you need to work. You can find objects and place them in a
browser work area in several ways:
• You can search for objects that meet your search criteria. The criteria may include
specific vaults, object types, names, revisions, owners, and attribute values, as well as
text within checked in files and metadata.
• You can load objects into the Matrix Navigator browser by opening a saved set of
objects. Sets are part of a user’s “workspace,” so a user’s sets are only valid in his/her
context.
• You can search for an object by “navigating” the relationships that exist between
objects. This is discussed in Using the Navigator Browser.
• You may create new, original objects. The procedure for this is covered in Creating a
New Object.
This chapter describes how you can query an ENOVIA Live Collaboration database to
locate objects that meet your search criteria. The results (the “found” objects) are
displayed in the current browser. You will also learn how to open sets that have been
previously saved for your context.
In later chapters, you’ll discover how to explore the database further by selecting an object
and requesting a view of the objects connected to it.

79
 Searching for Objects

You can perform a simple search to find objects with a specific type, name, revision,
owner, or vault. You can further refine your search by specifying Where clauses on the
Advanced tab that search for more specific properties of the objects you want to find. In
addition, you can use the Files tab to find objects that contain files that include a text
string, are of a particular format, or are written by a certain author. The results (the found
objects) are displayed in the current Matrix Navigator browser.

Initiating a Query There are two ways to initiate a query. The procedure below describes both methods.

To find objects

1. Click .
Or
Select Find from the Set menu. In either case, the Find Objects window opens.

Notice there are three tabs: Objects, Files, and Advanced. The Find Object window
always opens showing the Objects tab, where you can specify many of the basic
properties of an object. The Files tab is used for text search, and the Advanced tab is
where you can create Where clauses. These tabs are described in the Searching on
File Data and Refining Your Query sections later in this chapter.
2. Enter the search criteria as described in the sections that follow.
Any search criteria you define once can be named and saved to use in future searches.
For example, if you need to collect a variety of objects to create a monthly sales
forecast report, you could set up the search criteria one month, then perform the
search, and save it. Then you could just re-run the saved query the next month to
create the updated report. See Working With Saved Criteria later in this chapter for
the procedures to save search criteria.

80 Matrix Navigator Guide

 You receive an error message if a visual produces an error when it is evaluated
against a found object. When using the Web version of Matrix Navigator, the find
operation fails. When using the desktop version, you’ll receive the error message but
the find operation succeeds. To make the find operation work as expected, turn off or
fix the problem visual.
Here are two examples of queries in cues that would produce an error when evaluated
against an object. In the first example, the query is constructed correctly but would
produce an error when evaluated on an object whose policy has NO format at all:
where (default.hasfile == TRUE)
In this second example, the query would produce an error because “schedule” should
be “scheduled”:
where (current.schedule > Jan 1 1999)

Using Wildcard In many cases, you can type a wildcard character for an entry in the Find Objects window.
Characters
* Indicates all. For example, if you enter * for the Owner
criteria, Matrix Navigator will search for objects matching
all owners.
? Indicates one character of any value. For example, if you
enter 12?-Acct for an object name, Matrix Navigator might
find 12C-Acct or 129-Acct. But it would not find
12ABC-Acct or 12752-Acct.

Notice that many of the fields in the Find Objects window default to the * wildcard
character. Click to reset all fields back to *.

Chapter 3: Finding Objects 81

 Performing a Simple Query

If you only need to search for a specific type or name, you can make your selections from
the drop-down lists and choosers available for each item in the Objects tab. If you need to
refine your search with more information about the objects, you can create a Where clause
that includes all your search criteria as described in Refining Your Query later in this
chapter. In addition, to search the database based on file content, the files tab may be used
as described in Searching on File Data and Searching on File Metadata.
The Objects tab contains the following search criteria that you can specify:

Type The type of business object (such as a Report, Drawing,

Assembly, or Component).

Name The name of the object (such as “Voyager XL6” or “726591”).

Revision The revision number or letter for the object.

Owner The object’s owner.

Vault The grouping that contains the business object. For example,
all users in one department may store their objects in the same
vault.

When defining criteria, you can either use the drop-down lists or chooser buttons to select
one or more options from a list or pattern window, or you can type one or more options for
each criteria in the text boxes. Spelling and the use of uppercase or lowercase letters is
important. If you type more than one option, separate each option with a comma but
without spaces.

The fields Type, Name, Owner, Revision and Vault are limited to 127 characters. This
means you can search for a list of these items in the text boxes of the Find Object window,
but the full list cannot exceed 127 total characters. This limit does not apply to Where
clauses found in the Advanced tab of the Find Objects window.

Indicating the Specify the object types you want to find.

Object Type
To specify object types
• If you know the exact names of the types, you can type them (separated by commas,
but not spaces) in the Type text box.
Or

1. Click to open the Type Chooser.

82 Matrix Navigator Guide

 .

By default, all “top level” types are displayed. You can filter the display by typing a
partial type name with a wildcard in the Name text box and clicking Filter.
2. Select a type or use Shift+click to select more than one type in the window and click
OK.
For example, you might select the type Mechanical Parts.
Also, notice the following feature in the Type Chooser:
When you click the (+) symbol to the left of a specific type, you expand the displayed
list as a tree of types. You can click the symbol again—now a (-) symbol—to collapse
the tree. When filtering the display, you can indicate that you want to display only the
Top Level of the expandable tree.
The selected types are listed in the Type text box in the Find Objects window.

Indicating the If you know the exact object name(s), enter the name in the Name box, or use the
Object Name drop-down list and wildcards characters.

Using the Name drop-down list

1. Click Name drop-down arrow.

Chapter 3: Finding Objects 83

 Select the appropriate pattern where the partial match of the name should be:
*123 Specifies that Matrix Navigator should find all objects that end with the
numbers 123. For example: ENGFORM123
123* Specifies that Matrix Navigator should find all objects that begin with the
numbers 123. For example: 123ENGFORM
*123* Specifies that Matrix Navigator should find all objects that contain the
numbers 123. For example: ENG123FORM
The selection you made appears in the Name text box.
2. Substitute the “123” with your own alphanumeric string. Alternatively, change the
“*” (to match n characters) to a “?” (to match a single character). Refer to Using
Wildcard Characters for more information.

Indicating the You can include the object’s revision in the search criteria. If you know the exact
Object Revision revision(s), enter it in the Revision box.

To find the latest revision of an object, use “Revision == last” in the “Where” box on the
Advanced tab.

To specify revisions
• Type the revision in the Revision text box.
Or
• Click the drop-down arrow next to the Revision box. Make your selection as
described for the Name drop-down list.

Indicating the You can also search based on who owns an object.
Object Owner

84 Matrix Navigator Guide

 To specify object owners
• Type the names of the owners (separated by commas and no spaces) in the Owner
box.
Or

1. Click to bring up the User Chooser:

Use the following features of the User Chooser:

• By default, all types of users are displayed. You can filter the display by typing a
partial type name with a wildcard in the Name text box and clicking Filter.
• In addition to the Name text box, the following check boxes are provided to
further filter the display:
Top Level—Displays only the top level of the expandable tree list.
Person—Displays persons.
Group—Displays groups that the owners work within.
Role—Displays roles in the organization.
For example, unchecking all but the Person check box and clicking Filter
displays only persons. Filtering with the Top Level and Group boxes checked
shows only the groups that do not have a parent group. You can use Top Level
with Role in the same manner as with Group, but Top Level has no effect when
used with Person.
• When you click the Expand button (+) to the left of a group, you display groups
and persons that comprise it. Similarly, expanding a role shows persons who are
assigned the role, as well as any defined “sub-roles.” Expanding a person
displays groups and roles to which the person belongs. You can click the
Collapse button (-) to collapse the tree.
• The View menu is available in the User Chooser. You can change the view to see
owners as icons, ImageIcons, or names (text only).

Chapter 3: Finding Objects 85

 2. Select the users you want to search for as owners of objects in the window and click
OK. You can select groups or roles as owners as well. For example, if you are the
manager of a group, you might want to search for all the objects owned by the group
and then reassign them to specific team members.
When you click OK, the User Chooser closes and the selected user(s) are listed in the
Owner text box in the Find Objects window.

Indicating the Complete the following procedure to indicate a vault in which to search.
Vault To specify the vault
• If you know the exact names of the vaults, you can type them (separated by commas
but not spaces) in the Vault text box.
Or

1. Click to bring up the Vault Chooser.

By default, all available vaults display. You can filter the display by typing a partial
vault name with a wildcard in the Name text box and clicking Filter.
2. Select vaults in the window and click OK.
For example, you might specify the Manufacturing vault. You may also select more
than one vault.
The selected vaults are listed in the Vault text field in the Find Objects window.

Vaults defined as Remote (for a loosely coupled database) must be explicitly listed in the
Vault box in order to be searched. This means that the use of an asterisk in the Vault box
searches only Local and Foreign (Adaplet) vaults.

If you entered all your search criteria and are ready to perform the search, skip to Limiting
the Number of Objects to Display later in this chapter for the final options and procedures.

86 Matrix Navigator Guide

 Searching on File Data

You can use the Files tab in conjunction with the other tabs (Objects and Advanced) in the
Find Objects window to return those business objects that contain the files that meet your
criteria. The business objects must also meet any conditions set in the other tabs.

Use of the Files tab to perform a file search has additional setup requirements and
limitations. Consult your System and/or Business Administrator to be sure that you can
use this functionality.

Searching on File Use the procedure below to search on the basis of the contents of a business object’s
Content file(s).

To enter file search criteria

1. From the Find Objects window, select the Files tab.

2. In the Search box, you can enter an exact string to search for, or you can use
wildcards to select the information you are seeking. For example, enter “ACME, Inc.”
to find objects with files that include this string. Refer to Using Wildcard Characters
for more information.
3. In the Format field, you can narrow your search by specifying the application used to
create the files for which you want to search. For example, you may choose to only
search for text strings in Microsoft Word (*.doc) files. To specify a file format, click

. The Format Chooser opens.

Chapter 3: Finding Objects 87

 You can enter all or part of the name of the application in the Name field, then click the
Filter button to narrow the list of formats.

4. Click on the format for which you want to search and click OK.
When a format is specified, the search checks only that format of files. For this
reason, it is crucial for files to be checked into the appropriate format. For example, a
search on the PDF format will not find objects that contain PDF files if they are
incorrectly checked into the HTML format of the object. Refer to Checking In a File
for more information.
The Find tab reappears, indicating the file format you selected.
If you have entered all your search criteria and are ready to perform the search, skip to
Limiting the Number of Objects to Display later in this chapter for the final options and
procedures.

If errors occur, consult your Business Administrator to be sure that the full text search
capability has been setup in your database.

Searching on File Many file formats store metadata, which is information about the file itself, such as author
Metadata or title. You can use the following select statements on the Advanced tab to search file
metadata:

Select Statement Object Value

search.title Evaluates to an optional document title returned
by the search engine.
search.author Evaluates to an optional author returned by the
search engine
search.score Evaluates to an optional search score returned
by the search engine

You may use each of these select statements in expressions contained in the Where clause
for queries, visual cues, filters, etc. For example, the following Where clause could be
used to find business objects that contain a file written by the specified author:

88 Matrix Navigator Guide

 search.author == sue
Actually, any text search defined in the Files tab could instead be specified in the Where
clause on the Advanced tab. For example, the following in the where field:
search == “Hello World”
performs the same search as the following:

Chapter 3: Finding Objects 89

 Refining Your Query

If you need to refine your search with more information about the attributes of objects,
you can create a Where clause that includes all your search criteria. The Advanced tab
gives you tools to build the Where clause. You can use the ellipsis button in the Advanced
tab to use a menu-driven interface that helps you create and format your criteria. If you are
familiar with MQL, you can type query conditions directly into the Where expression box.
See the “Selectables” appendix in the ENOVIA Live Collaboration Studio Modeling
Configuration Guide for details on the required syntax rules. You can also use a
combination of menu selections and direct entry to build a query expression.

Indicating the To refine your search, you can specify information that describes the object in the
Object Properties following procedures. For example, as an accountant, you might want to find items
applicable to Project Z that are made of aluminum and have a target cost between $1000
and $5000. The procedure below illustrates this example.

To specify object properties

1. Click on the Advanced tab of the Find Objects window. Then you can either type in a
properly written MQL expression or click the Where ellipsis button.
The Where Pattern window appears.

2. Click the Property ellipsis button to bring up the Select Pattern window:

By default, only Basic properties are displayed. You can filter the display by typing a
partial property name with a wildcard in the Name text box and clicking Filter.

90 Matrix Navigator Guide

 In addition to the Name text box, the following check boxes are provided to further
filter the display:
Basic—Displays basic properties.
Attribute—Displays attributes of objects.
Relationship—Displays relationships that may exist between objects.
For example, as an accountant, you might begin by filtering basic properties to
specify Project Z as the object description. Select the Basic check box and then click
Filter to display only basic properties.
If the Type box on the Objects tab of your query does not contain an *, then Matrix
Navigator filters your Select Pattern choices to include only those values associated
with the selected types. For example, filtering on attributes or relationships display
only the attributes or relationships for the type(s) entered in the Type box.
3. Select a property in the Select Pattern window, such as Description, and click OK.
The Property box shows the selected property in the Where Pattern window:

4. Select an operator in the Where Pattern window and enter values to establish
relationships for the property.
For example, select the Match operator and type ProjectZ in the text box to
indicate that you want to find items that contain the word ProjectZ in the description.

Reserved words such as keywords and select expressions must be afforded special
consideration in exact equal (==) expressions. See the MQL Guide, Working with
Workspace Objects for details.

Chapter 3: Finding Objects 91

 The available operators are:

Operator Finds business objects in which the selected property: Symbol

Between Is between two specified values. You can indicate whether the entered values are > and < or
inclusive. Use the Between operator for queries on numeric properties, revisions, dates, >= and <=
and time queries.

Equal Is exactly equal to a specified value. The value must comprise the entire property. For ==
example, to find an object named “Steel Widget”, you must query for “Steel Widget”. If
you enter “Steel” only, the query will not find the object because “Steel” doesn’t exactly
equal the object name.
Unlike the Match operators, Equal interprets the wildcards * and ? literally and not as
wildcards. Therefore, an Equals query of “Steel*” will not find the Steel Widget object.
Since * and ? are reserved characters and are not used in properties, do not use them at all
when using Equal and Not Equal operators.

Not Equal Is not equal to a specified value. Like the Equal operator, Not Equal queries apply to the !=
entire property. For example, to find all objects whose owner is not equal to Sam Smith,
enter “Sam Smith” for the value. If you enter “Sam”, the query would find objects owned
by “Sam Smith”. Do not use the wildcard characters * or ? with the Not Equal operator.

Less Than Is less than or equal to a specified value. <=

Equal

Less Than Is less than a specified value. <

Greater Than Is greater than a specified value. >

Greater Than Is greater than or equal to a specified value. >=

Equal

Match Contains the specified value. The query is NOT case sensitive. To find all objects with the ~~
word “steel” in the name, use the Match operator and enter “steel” for the value. The
query will find all objects with “steel”, “Steel”, and “STEEL” in the name.

Not Match Does not contain the specified value. The query is NOT case sensitive. For example, to !~~
find all objects that do not have a revision of A, enter “A” for the value. The query would
find objects with revisions of “B”, “C”, “1”, “2”, etc. Because the query is not case
sensitive, it would not find objects with revisions of “a”.

By default, ENOVIA Live Collaboration is case sensitive, but this may be disabled by System administrators. When
case sensitivity is turned off, the following 4 case sensitive operators behave identically to their string match
counterparts.

Not Match Does not contain the specified value. The query is case sensitive. For example, to find all !~=
Case objects that do not have a revision of A, enter “A” for the value. The query would find
objects with revisions of “B”, “C”, “1”, “2”, etc. Because the query is case sensitive, it
would also find objects with revisions of “a”.

92 Matrix Navigator Guide

 Operator Finds business objects in which the selected property: Symbol

Match Case Contains the specified value and the case of each letter also matches. For example, to find ~=
all objects with the word “Steel” in the name, use the Match Case operator and enter
“Steel” for the value. The query will find all objects with the word “Steel” anywhere in
the name. Since the query is case sensitive, the query will not find objects with “steel” in
the name.
Unlike the Equal and Not Equal operators, all four Match operators interpret the wildcard
characters * and ? as wildcard characters and not as literal values. Use the Match
operators to find objects with properties that contain (or don’t contain in the case of Not
Match and Not Match Case) the value you enter but don’t necessarily comprise the entire
property. The Where Pattern window automatically includes the wildcard * before and
after the specified value so the value need only be present (or not be present) in the
property to meet the query criteria.

The following operators are for use by searches on description or string attribute fields that contain more than 254
bytes of data. They do not have a symbol to represent them, and may only be used by typing in the where clause dialog.
Refer to Searching based on lengthy string fields for more information.

matchlong Contains the specified value, in either the lxStringTables or the lxDescriptionTables. The search is case
sensitive. To find all objects with the word “language” in the attribute Comments, and to ensure that
both tables are checked, use attribute[Comments] matchlong “language” in the Where clause. Since the
query is case sensitive, the query will not find objects with “Language” or “LANGUAGE” in the
Comments field.

nmatchlong Does not contain the specified value, in either the lxStringTables or the lxDescriptionTables. The “n” is
for not match. The query is case sensitive. To find all objects that do not contain the word “Language”
in the attribute Comments, use attribute[Comments] nmatchlong “language” in the Where clause. Since
the query is case sensitive, it will find objects with “Language” or “LANGUAGE” in the Comments
field.

smatchlong Contains the specified value, in either the lxStringTables or the lxDescriptionTables. The search is NOT
case sensitive. To find all objects with the word “Language” in the attribute Comments, and to ensure
that both tables are checked, use attribute[Comments] smatchlong “language” in the Where clause.
Since the query is not case sensitive, the query will find objects with “language”, “Language” or
“LANGUAGE” in the Comments field.

nsmatchlong Does not contain the specified value, in either the lxStringTables or the lxDescriptionTables. The search
is NOT case sensitive. The “n” is for not match. To find all objects that do not contain the word
“language” in the attribute Comments, enter “language” for the value. Because the query is not case
sensitive, it would not find objects with the word written as “LANGUAGE” or “Language” in the
Comments attribute, as well as those that did not contain the word at all.

5. Select the Only option button to indicate that this is the only (or first entered) value
for which you wish to test.
The And and Or options are described in Specifying Additional Criteria below.
6. Click OK.
The example below shows the results.

Chapter 3: Finding Objects 93

 Specifying Additional Criteria
You can also specify additional search criteria based on other properties. For example,
you can indicate that the target cost should be between $1000 and $5000 and that the
material is aluminum.
When you enter more than one set of properties criteria, you can select Only, And, Or, or
Cancel to indicate how you would like to continue:

Only Searches for criteria specified by the current Where Pattern window only. If
other where conditions have been set, they will be removed (Only is default
value for the first-entered set of criteria).

And Searches for criteria specified by the current Where Pattern window and for
previously-defined criteria. Use when entering more than one set of properties
criteria. If other Where conditions have been set, the current criteria is added
to those conditions. The database is searched to find objects that match each
set of criteria.

Or Use when entering more than one set of properties criteria. If other Where
conditions have been set, the current criteria is added to those conditions. The
database is searched to find objects that match one set or the other.

To specify additional criteria

1. In the Advanced tab, click the Where ellipsis button.
2. Open the Select Pattern window by clicking the Property ellipsis button.
3. Filter the display as needed to find properties.
For example, you could filter on attributes containing the word “Cost.” The results
might look like those below. (Note the use of the Name filter.)

94 Matrix Navigator Guide

 4. Select the property and click OK.
The selected property (Target Cost in this example) appears in the Where Pattern
window.
5. Select an operator. For example, for Target Cost, you might choose the Between
operator. Two text boxes are displayed with check boxes for Inclusive.

6. Enter the appropriate values—for example, 1000 and 5000—in the Between text
boxes, as shown.
If you select the Inclusive option for both values, the cost range will include $1000
and $5000.
If you do not select the Inclusive option for either value, the cost range will not
include $1000 or $5000 (the range will be $1001 through $4999). Select the And
option button to indicate that you want to use both sets of criteria entered so far: the
description of ProjectZ and the target cost between $1000 and $5000.
The example below shows the results.

Chapter 3: Finding Objects 95

 7. Open the Select Pattern window by repeating steps 1-3, but this time when you check
Attribute to filter the attributes, use the general wildcard *, then click Filter to see all
the attributes, not just the COST ones.
8. Select the Part Family attribute.
The selected attribute (Part Family) appears in the Where Pattern window. Select the
Match operator. The Match text field displays so you can enter a value.
9. Select the And option button to indicate that you want to use all three sets of criteria
entered: the description of ProjectZ, the target cost between $1000 and $5000, and the
Part Family of Gear.

When defining the where pattern, see the “Selectables” appendix in the ENOVIA Live
Collaboration Studio Modeling Configuration Guide for details on the required syntax
rules.

96 Matrix Navigator Guide

Limiting the Since you may be accessing very large databases, you need to consider limiting the
Number of Objects number of objects to display.
to Display • Click the Limit text box in the Advanced tab and enter a value for the maximum
number of objects to be found. The query will stop once this number is reached.
A warning notice is displayed to inform you when the limit is reached.

If you do not want to limit the search, enter 0 or leave the Limit text box blank.

Find Limit Preference

For desktop versions, you can set a default for the Find Limit, using the enovia.ini file
variable called “MX_FIND_LIMIT.” If you set this value, then the Find Limit will always
appear using that value for a default. If you do not have any findlimit defined in the
initialization file, the Find Limit field defaults to 0, or “no limit.” (The enovia.ini file for
the Live Collaboration Server has a similar variable called MX_BOS_FIND_LIMIT.)

Using the Expand If you specify a type on the Objects tab, Matrix Navigator finds those type(s) of objects
Option that meet all of the search criteria. With the Expand check box on the Advanced tab
selected, Matrix Navigator also finds subtypes of the specified types that meet the
additional criteria. For example, searching for Parts with Expand on find parts, but may
also return components and assemblies (which are not part of the type specification, but
are subtypes of parts).

You may get unexpected results when using expand with a wildcard in the Type box. For
example, if we specify a type as “A*” (to find types that begin with A) and check Expand,
the system would find all Assembly objects but also all subtypes of assembly that may not
begin with A, such as components.

Replacing or Before you perform the search, you need to decide if you want to add to the objects
Appending already displayed in your browser, or replace them.
Currently • Select either Replace Objects or Append Objects at the bottom of the Find Objects
Displayed Objects window.

Performing the Click Find to perform the search.

Search Matrix Navigator searches for all objects that match the defined criteria and briefly
displays a visual progress bar at the bottom of the window as it finds objects.

Chapter 3: Finding Objects 97

 Once the system finds all objects, Matrix Navigator loads and then displays them in the
current Matrix Navigator browser.
Or
Click Apply to perform the search and leave the Find Objects window open, ready to
accept new search criteria (presumably with Append selected).
Or
Click Cancel to close the Find Objects window without executing the query.

98 Matrix Navigator Guide

 Query Strategies

The problem with queries is simple: poorly structured queries cause memory and
performance problems. For example, the result of a query may be so large that the
computer system depletes resources in order to handle the result. Other queries may
consume more processing time than they should.
This section contains practices and guidelines for improving query execution and
performance.

Where Clause This section contains tips on how to include where clauses within a query.
Guidelines
Using Select Fields in well-structured Queries
Queries that perform well always include at least 1 field that can be converted to SQL to
limit the results returned from the database server. Criteria that cannot be converted to
SQL are evaluated against this candidate result set in memory and the final result set is
displayed. The smaller the candidate result set, the better. Well-structured queries use
several criteria that are “SQL convertible” so that the work performed in memory is kept
to a minimum.

SQL convertible fields were formerly referred to as “indexed” fields, before the advent of
indexed attributes.

The query optimizer processes a query in the following manner:

1. The where clause is first factored into the “OR” form: A || B || C || D. This is done
using the boolean logical equivalences. For example:
(A || B) && C
becomes
(A && C) || (B && C) and !(A && B) == !A || !B
Each of the OR’d terms will be processed independently.
2. Then the query is parsed to identify all fields that are SQL convertible (that is, which
terms can be converted into SQL and be included in the select commands issued to
the database server).
3. It is then determined whether the set of SQL convertible terms are primarily related to
business objects or relationships to decide if the initial selects are requested against an
lxBO table (businessobjects) or lxRO table (relationships).
4. The commands are then issued to the database server to select rows from lxBO or
lxRO including these SQL convertible terms. This will return a candidate result set
which satisfies the SQL convertible terms (associated to either objects or
relationships).
5. The remaining criteria (non-SQL convertible terms) is then processed against the
candidate objects (or relationships). This requires additional db selects to get the data
specified by those terms, and evaluating the expressions in memory within the
ENOVIA Live Collaboration process, and producing a final result set.

Chapter 3: Finding Objects 99

 6. Then any selects associated with the query are then processed, which may involve
further db selects to get additional data about the final result set.
Steps 4-6 are repeated for each vault identified by the Vault field of the query.
The most optimal queries use sufficiently specific SQL convertible terms to result in the
smallest possible candidate result set. This strategy provides the following advantages:
• using SQL fully leverages the database server’s optimization and indexing
• minimizing the candidate result set means there are less objects to postprocess to get a
final result set, which requires both less time and less in-process memory.
The following selectables are SQL convertible. All queries should include at least one of
these criteria:

SQL Convertible Field Meaning

Name object name
Type object type
Owner object owner
Policy governing policy of object
Format format of files checked into object
Originated date object was created
Modified date object was last modified
Current current state of object
attribute[] value of attribute on object
to[].attribute[] value of attribute on relationship connected to object
from[].attribute[] value of attribute on relationship connected from object
relationship[].attribute[] value of attribute on relationship connected to or from
object
format.file.store store containing files checked into object
format.file.location location containing files checked into object
search[] result of full text search
reserved Boolean indicating reserved status of business object or
connection.
reservedby a non-empty string or context-user

Queries that match unreserved objects and connections are unindexable. Indexable cases therefore do
not include reservedby matching an empty string, or reserved being false.

reservedstart date and timestamp of when the object is reserved

100 Matrix Navigator Guide

 SQL Convertible Field Meaning
to[NAME] == TRUE to find objects with relationships of given NAME pointing
to them
from[NAME] == TRUE to find objects with relationships of given NAME pointing
from them
revision == first to find objects which are the first revision of their revision
sequence
revision == last to find objects which are the last revision of their revision
sequence

You can use SQL convertible fields with any relational operator (==, !~=, <> etc.) applied
to a constant value that may include wildcards. For example,
name ~= 'A*B'
returns all objects whose name begins with “A” and ends with “B”. Note that use of select
fields in where clauses that are not in the list above will likely result in non-optimal
queries since non-SQL convertible fields have to be evaluated on the client.
It is best not to use any word that can be a selectable for a business object or connection as
a value in the Where clause of a query because it will be evaluated as a select clause rather
than being taken literally. See the "Selectables" appendix in the ENOVIA Live
Collaboration Studio Modeling Configuration Guide for a complete list of business object
selectables. If it is unavoidable, refer to Using const for reserved words.
Clauses that are not SQL convertible
Any selectables not on the above list are not SQL convertible when used in a where
clause. For example, the following are not SQL convertible:
description
grantor (and grantee, granteesignature)
state[]
revisions[]
previous (and next)
type.kindof

Note that “revision” is not SQL convertible when included in the where clause, but is SQL
convertible when included in the business object specification part of the query.

Selectables that are not SQL convertible cannot be built into the SQL commands that get
objects and connections from the database server, so these clauses are not used to limit the
number of objects that are retrieved from the server. Qualifying these clauses is very
sensitive to the number of objects retrieved, since for each such object, additional SQL
calls have to be constructed to retrieve the values of these fields, and data has to be stored
in the clients memory. Given these realities:

NEVER execute a query that has only fields that are not SQL convertible.

ALWAYS make sure that a query containing fields that are not SQL convertible also has
some SQL convertible fields to limit the number of objects retrieved.

Chapter 3: Finding Objects 101

 Here are a few examples of common queries that are bound to be slow. Note that in all of
them, the type (PART) is specified, but a production database can have huge numbers of
PARTs, so the type specification is not very limiting:
PART * * where 'description ~~ “*a word*”'
PART * * where 'state[StateName].satisfied == TRUE'
PART * * where 'revision == last'
In the above queries, it would be best to include an attribute that substantially limits the
number of PARTs that the system would have to examine.
The number of objects retrieved from the database server (that is, the size of the candidate
result set) by the SQL convertible fields is the biggest factor in query performance and
client memory requirements. The length (in characters) of the where clause or number of
expressions within the where clause are immaterial. Actually, a longer where clause is
desirable if much of it is comprised of SQL convertible fields that limit the number of
objects retrieved:
PART * * where ' (description ~~ “*a word*”) AND
(attribute[Keyword] ~~ “abc*”) AND (attribute[Keyword] ~~
“123*”) '

Indexed Attributes and Basics

An ENOVIA Live Collaboration business administrator can create an “Index” that
includes attributes (and optionally basic properties) to improve query performance. The
Index, once enabled, is used to access the specified group of selectables together, resulting
in improved performance of queries that use those items as criteria. If your queries
consistently include the same set of selectable criteria, ask your business administrator
about creating an Index. Query performance can be drastically improved. For details, refer
to “Working with Indices” in the System Manager Guide or “Maintenance” in the MQL
Guide.
For more information about building well structured queries, see Modeling
Considerations.

Processing Relational Expressions

The processing of a where clause is driven by the left-hand side of relational expressions
in several different ways:
• Creating efficient SQL for a relational expression depends on the left-hand side being
a select keyword that can be mapped to SQL AND the right hand side being a
constant. The only exception to the rule that the right-hand-side must be a constant
are the specific expressions 'revision == first' and 'revision == last'.
• The left hand side (if it is a select keyword) also drives the datatype of the expression.
That is, if the left-hand side refers to an integer attribute, ENOVIA Live
Collaboration attempts to interpret the right-hand side as an integer; if the left-hand
side is a date, it tries to interpret the right-hand side as a date.
• When the left-hand side represents a string in the database that is SQL convertible
(such as “attribute[Synopsis]”), ENOVIA Live Collaboration constructs SQL to
request the database server to return objects which match the right-hand side. In doing
so, the server will treat the database values as literal strings with no wildcards.
Wildcard matching only applies to the right-hand side.

102 Matrix Navigator Guide

 • However, when the left-hand side represents a string in the database that is not SQL
convertible (such as “description”, or “state[S].signature[SIG].signer”), the system
must read the value into memory for each object and do a match. In this case, * and ?
within the read values will be treated as wildcards. This is also true in the case where
“.value” is appended (such as “attribute[Synopsis].value”), since that makes the
clause not SQL convertible.
• Only the right-hand side is interpreted to include wildcards (unless you use == or
!==).
• When used with the Equal and Not Equal operators (==, !=) in the where clause, the
system treats the wildcard characters “?” and “*” as literal characters on both sides of
the expression. Do not use these characters when querying using the Equal or Not
Equal operators. On the other hand, MQL interprets “?” and “*” as wildcards when
used with the four Match operators and when used in the Type, Name, or Revision
fields of the query. For example, if you type the following query:
temp query bus * A*B *

MQL returns all objects that start with A and end with B. However, if you use the
equality operator in the where clause, as follows:
temp query bus * * * where name == A*B

MQL looks for the literal A*B as the entire object name rather than treating the * as a
wildcard.

Searching based on lengthy string fields

The ENOVIA Live Collaboration /Oracle database stores most string attribute values in
the lxStringTable for the object’s vault. However, lxStringTable cannot hold more than
254 bytes of data. When a string attribute’s value is larger than this limit, the data is stored
in the descriptions table (lxDescriptionTable), and a pointer to this table is placed in the
lxStringTable.
When performing an “includes” search (using match operators: match, match case, not
match, not match case) on string attribute values, ENOVIA Live Collaboration searches
on both lxDescription and lxString tables only when the attribute involved is of type
“multiline.” Also, if you use the equal operators (==, !=) and give a string of more than
254 bytes to be equal to, ENOVIA Live Collaboration checks the values in the
lxDescriptionTable only.
To search on description or other string attribute values for given text, and to force the
search of both tables, you can use the “long” match operators. These operators can be used
in any expression (including the where clause entry screen) but are not offered in the
query dialog in either the desktop or web version of Matrix Navigator. Refer to the table of
Relational operators in Indicating the Object Properties for more information.
Alternatively, you can include the .value syntax in the where clause, as shown below:
attribute[LongString].value ~~ "matchstring"
For more information about .value keyword, see the section below.

Using .value
If a query has a clause that is known not to be a good search candidate, .value will make
that clause the last thing evaluated in the query. For example, consider the two following
queries and the SQL they generate.

Chapter 3: Finding Objects 103

 The following examples are not valid queries per se, but examples to show how .value is
used.

Query 1:
rev = "*", type = "A", name = "*", and attribute[A] = 'this'
SQL generated:
(type=="A") && (revision == "*") && (name == "*") &&
(attribute[A] == 'this')
Query 2:
rev = "*", type = "A", name = "*", and attribute[A].value =
'this'
SQL generated:
(type=="A") && (revision == "*") && (name == "*") )
The difference is the processing order of the query. In query 1, all the clauses are
evaluated in order. In query 2, the type, name, and revision clauses are evaluated first, then
the result is evaluated with the attribute[A].value clause. It is important to note that .value
takes an attribute that ENOVIA Live Collaboration considers SQL convertible and makes
it not SQL convertible. Generally it is done because the final part of the query does not
help the search become more efficient due to a schema problem. The work in this case is
not done by the database, but by ENOVIA Live Collaboration .

When using .value, you should include as much criteria as possible — several ANDs and/
or ORs.

Query Syntax
• You must include a space before and after the operator in all where expressions.
• To find objects where a particular property is blank, use a double quote (no space).
For example, if you want find objects that do not contain a description, use
(description ~~ “”). For Boolean attributes, searching on “” results in finding objects
where the value for the attribute is False, even if the default is True. (Boolean
attributes, are either True or False, as opposed to Boolean expressions, which can be
True, False or Unknown.)
• To find objects where a particular property is non-blank, use a double asterisk. For
example, if you want be sure that all objects in the result of your query contain a
description, use (description ~~ “**”).
• The kernel expression parser does not give AND precedence over OR. They are
processed with equal priority left-to-right. Parentheses must be used to assert a
different priority to these operators. In complicated expressions, particularly those
that use ! or not, use parentheses to clearly state your intent. For example, in the
following, the ! is applied to the entire clause:
!relationship[Categorize] == True ||
relationship[Categorize].from.id =="43482.46832.5291.38424
To apply the ! to only the portion before the OR (||), change it to:
(!relationship[Categorize] == True) ||
relationship[Categorize].from.id == 4448.10921.47699.5768
• The datatype of relational expressions (>,<,==) in where clauses is determined by the
left operand. In the following example, the left operand is a hard coded string:

104 Matrix Navigator Guide

 temp query bus "Engineering Drawing" * * where ' "Jul 30, 2001
00:00:00 AM EDT" > originated ';
What appears to be a date (Jul 30...) is seen as a string by ENOVIA Live
Collaboration , and so would not find June originated dates because June
alphabetically comes after July. For the inequality to do a date comparison, put
originated on the left to establish the data type for the expression:
where 'originated > "Jul 30, 2001 00:00:00 EDT"
• Always enclose the entirety of the where clause in SINGLE quotes. If the expression
is not enclosed, MQL will not read it as a single value. Most query expressions
contain multiple values and spaces. Therefore quotes are necessary to determine the
boundaries of the expression.
• Strings in square brackets can have spaces—the square brackets delimit them, but any
other strings with spaces should be enclosed in DOUBLE quotes.
• When using where clauses with expand bus, you must always insert select
bus or select rel before a where clause.
The syntax of a query statement affects the execution of the query. ENOVIA Live
Collaboration occasionally has changes that handle commands slightly differently, or
maybe add a few new options to a command, for additional functionality. For example, the
change from version 9521 to version 9601 resulted in the handling of the
relationship keyword differently within a where clause. (The relationship
keyword can still be used in a select clause without adversely affecting performance.)
This caused queries that ran fast under the older version to run much more slowly. The
following query is an example:
temp query bus myType * * where
'(relationship[myRelationship].attribute[myAttribute] ...)';
In the newer version, the solution is to get rid of the relationship keyword and
instead create separate clauses with "from" and "to" in them, as shown here:
temp query bus myType * * where
'(from[myRelationship].attribute[myAttribute] ...)
Or
(to[myRelationship].attribute[myAttribute] ...)';

Query Parsing
The order of the query created becomes important when trying to structure a query for
performance. For example, consider a query:
where "A && (B || C)"
As the kernel parses the query, the expression passed to the database becomes:
(A && B) || (A && C)
The kernel uses ORs at the top level to separate the query into parts, then to accumulate
the results. Generally, the processing of a query is done left to right. Knowing this, a user
can structure queries so that the indexed attributes are used first. Front loading the query in
this manner restricts the sets of objects searched with non-indexed attributes.

Selects and Macros in Where Clauses

If a where clause makes use of a select, the ENOVIA product will evaluate the select for
each object found by the query. However, when using a macro, the macro is evaluated one
time only. This can result in a drastic performance difference.

Chapter 3: Finding Objects 105

 In the sample queries below, the first query uses a select, while the second query uses a
macro. The first query will return all the objects that match it, then apply the where clause.
The second query will evaluate the macro and use the result as part of the query. As a
result, it will return a smaller subset that already matches the owner, giving far better
performance.
Examples:
temp query bus <TYPE> * * where owner = context.user
temp query bus <TYPE> * * where owner = $USER

Searching on Date/Time
In order to include Date/Time in your query, you must use the format defined for your
system initialization file. ENOVIA Live Collaboration provides six different formats for
the display and entry of dates and times. Each can be modified by adding lines to the .ini
file or the startup scripts. See “Configuring Date and Time Formats” in the ENOVIA Live
Collaboration Installation Guide for details.
If your Date/Time query does not conform to the expected format, you will receive an
error message similar to the following:
Invalid date/time format ‘July 22. ‘02’.
Allowed formats are:
[day] mon dom, yr4 h12:min[:sec] [mer] [tz]
[day] mon dom, yr4
moy/dom[/yr2] h12:min[:sec] [mer]
moy/dom[/yr2]
When entering a date as a value in the Where clause box, Matrix Navigator assumes the
time is 12:00 AM unless a specific time is specified as part of the query.
The following table explains the tokens used in Date formats:

Token Meaning

day day of the week (mon, tue, wed,...)

DAY day of the week, not abbreviated

mon month (jan, feb, mar,...)

MON month, not abbreviated

tz time zone (edt, cdt, pdt,...)

TZ time zone, not abbreviated

mer time meridian (am, pm, or blank for 24 hour time)

sec seconds, 0 - 59

min minutes, 0 - 59

h12 hour in 12 hour format, “mer” will be non-blank

106 Matrix Navigator Guide

 Token Meaning

h24 hour in 24 hour format, “mer” will be blank

yr2 abbreviated year (96, 97, 98,...)

yr4 full year (1996, 1997, 1998..)

dom day of month (1, 2, 3,..., 31)

doy day of year (1, 2, 3,..., 365)

moy month of year (1, 2, 3,..., 12)

Using const for reserved words

Reserved words such as keywords and select expressions must be afforded special
consideration in exact equal (==) Matrix expressions. For example, the following
statement might be written to find business objects where the value of the attribute
‘Regression’ is ‘first’.
where 'attribute[Regression]==first';
But because ‘first’ is a select keyword that returns the first revision of a business object
and is evaluated as such, the result of the evaluation — rather than the literal word
‘first’— is compared with the attribute. (For a list of keywords and their meanings, see the
“Selectables” appendix in the ENOVIA Live Collaboration Studio Modeling
Configuration Guide for a complete list of business object selectables.)
For this type of situation, use const to indicate that whatever follows should not be
evaluated. For example:
where 'attribute[Regression]==const"first"';
Const has three possible forms: all uppercase, all lowercase, and initial letter capitalized
followed by all lowercase. No space can appear after the word const. It must be
followed by a quote (double or single, depending on the syntax of the rest of the
statement). Almost any character can appear within the quotes, with the exception of
backslash and pound sign. The characters between the initial and closing quotes remain
unevaluated.
If your implementations are using JSP/Tcl to compose a where clause dynamically (that
is, using a variable to construct the where clause), the const syntax must be used
because the value you pass in could be an ENOVIA Live Collaboration keyword. If this
happens, the where clause will not return an error, but you will get unexpected results.
Here are some examples of queries that will NOT return correctly without using const:
attribute[Some Attribute]==‘first’
attribute[Some Attribute]==‘FIRST’
attribute[Some Attribute]=="Current"
attribute[Some Attribute]=="owner"
description=="Current"
description=="policy"
However, the following will return correctly:
attribute[Some Attribute]==‘my first order’

Chapter 3: Finding Objects 107

 attribute[Some Attribute]~=‘*first*’

Invalid Where clauses

All queries that include at least some searchable criteria are evaluated, even if some parts
of the where clause is invalid or incomplete. Queries that include some invalid items in a
where clauses will issue warnings when:
• The where clause has a relational term in which both sides are constants.
• A conjunct or disjunct or unary negation has only a constant term.
• The entire where clause is just a constant.
(A constant term is one that is not a select clause, thus does not vary from object to
object.)
A message is also output to warn about these situations in those cases where the
expression might be indexed (made part of the SQL query to get candidate objects):
• The keywords fromset and toset used without a set name.
• The keywords from, to, and relationship used with a name that should be the name of
a relationship type, but it is not.
• The keyword attribute used with a name that should be the name of an attribute type,
but it is not.
If you receive such a warning, you should cancel the query evaluation and correct the
problem.

Modeling A big key to query performance is the data model that is used. It is much more efficient to
Considerations build queries that use attributes rather than to build queries using fields that are not SQL
convertible. Careful and intelligent use of attributes and triggers can limit the queries
created. Certain queries, while looking simple and returning a very small subset, may
actually cause extreme performance problems.
Below is a typical query, targeting objects of type Manufacturer, Facility, Group, and
Project:
temp query bus Manufacturer,Facility,Group,Project * * where
'from[Group Assignment].to.type == Person' select id dump ¿;
This query resulted in a small set of 12 objects, but it caused the generation of nearly four
hundred select statements and excessive memory growth. A better solution would be to
create an attribute that would make the query true or false. To create a SQL convertible
query, first add an attribute (for example, “Assigned to Person”) to each of the four target
types. For the purposes of this example, the values of this attribute are “YES” and “NO”.
When a business object of these particular types is created, set the value of attribute
“Assigned to Person” to “NO”. Next, create triggers to modify the “Assigned to Person”
attribute, either setting the value or unsetting it. As users update objects of the desired
type(s), the assignedToPerson trigger checks the relationships of the object. The work the
trigger will do can be summarized as “if the object meets the criteria specified in the
original non-SQL convertible query, then modify the 'Assigned to Person' attribute to
show that it does meet the criteria.” The trigger will check to see whether the business
object has a relationship to a person from its group assignment. If it does, set the
“Assigned to Person” attribute to indicate “YES”. If the user removes that relationship, set
the attribute value to “NO”.

108 Matrix Navigator Guide

 The new query would look something like this:
temp query bus Manufacturer,Facility,Group,Project * * where
'attribute[Assigned to Person] == YES' select id dump ¿;
It is also important to include some consideration of query performance when designing
your data model—in particular, when defining a new type.
For example, here are three modeling alternatives that minimize the need for queries on
descriptions. All three can easily be maintained using the ModifyDescription trigger on
the type:
• Add an attribute Synopsis, which holds the first 100 characters of the description
field.
• Add an attribute Keywords, and require values to be specified at create time.
• Write the description to a text file, check it into the object, and replace uses of
'description ==' by 'search[] =='.
In addition to the data model, knowing the application is another key. Really
understanding how the application works enables users to create better queries. The end
user knows what search parameters return lots of objects and which ones return a limited
object collection.
Keep in mind that ENOVIA Live Collaboration is best suited to expand/navigate
operations. Queries are not the most efficient way to access the object-oriented data that
the application manages. The best way to improve the performance of queries is to
eliminate queries. A data model focused on the expand/navigation of relationships helps
tremendously. However, one caveat concerning the use of type hierarchies and the use of
!expandtype: Performance problems may occur when using 1000s of subtypes and
then querying against the name of a base class. Traversing giant type trees can also cause
problems. Refer to “kindof selectable for types” in the MQL Guide for a possible solution
if large and deep type hierarchies are unavoidable.

Avoiding Unbounded queries can pose problems, especially with large databases. For example, a
Unbounded statement similar to "temp query bus * * *" will search every single item in the database.
Queries If the database is small, this is not an issue. As the database size increases, this becomes a
tremendous performance problem. To avoid this problem you can restrict the query by
vault or type, impose a find limit on the query, or create a query trigger.

Querying Vaults
Restricting the query to objects within the same vault is an obvious way to restrict a query.
Limiting the search to objects that are all known to be stored a certain way cuts down on
processing because all SQL statements related to the query have to be duplicated for each
vault involved in the search.

Avoiding Large Similar to a large query, a large expand also causes performance problems. For example,
Expands the statement “expand bus T N R recurse all;” attempts to expand all items connected to
the specified object, expand all of those objects, and on, and on. Once again, a small
database can hide the potential problem with this query because its results do not manifest
themselves until the database size gets very large. A suggested solution is to limit the
number of levels to expand (do not use recurse all, use recurse to 2).

Chapter 3: Finding Objects 109

Object Existence Generally, you should not use temp queries to check for the existence of objects.
Rather than using “mql temp query T N R”, it is better to use “mql print bus T N R select
exists”, which will return true if the object exists, false otherwise.

Query In instantiating queries, do not use a null string, use an empty string. Declaring a query as
Instantiation “Query q = new Query()” is not as good as “Query q = new Query q("")”. The empty
string query constructor could cause stability problems if the same users modify the same
query at the same time. Also, in this case the temp query opens the query .finder, updates
it with the new type, name, revision and vault information and then runs the query. If
.finder happens to have a where clause specified, it is not cleared. As a result, the query
might not return the MQL equivalent of "temp query bus type name rev vault". Using the
empty string also results in better performance since the query finder will not have to be
written to the database.

Nested Queries An additional problem with queries and/or transactions results from nesting them inside
one another. For example, the first set shows a transaction nested within another; the
second set shows two separate transactions.
Invalid sequence:
Start trans1
Start trans2
Commit trans2
Commit trans1
Valid sequence:
Start trans1
Commit trans1
Start trans2
Commit trans2
ENOVIA Live Collaboration does not allow nested transactions. However, savepoints
can be used to divide large transactions into smaller parts. If the start() method of the
context class is called a second time before the commit or abort methods are called for the
first transaction, the system throws a MatrixException. Use the isTransactionActive()
method to determine if a transaction is still alive before starting a transaction. If the result
is false, it is safe to begin a transaction; if true, the current transaction must be aborted or
committed before starting a new one. In addition, all exceptions within a transaction must
be handled, else the transaction could get stranded. If the transaction is stranded, it cannot
be recovered. Using a transaction timeout (to abort/commit the transaction once the
threshold has been exceeded) can help to solve the problem of stranded transactions.

110 Matrix Navigator Guide

 Working With Saved Criteria

In the Find Objects window, the Query menu options and tools enable you to work with
saved search criteria as described in the table below. This criteria includes the vault, type,
name, revision, owner, and Where clauses.

New Clears all fields from all tabs of the Find Objects window so
you can specify new criteria. “All” is indicated with an
asterisk (*) in each text box.
Open Lets you open a saved query.

Save As Lets you save the current query criteria with a specific
name.
Delete Lets you delete saved query criteria.
Back and Lets you scroll through the recent (unsaved) criteria.
Forward Each time you select Back, the next previous criteria
displays.
Each time you select Forward, the next saved criteria
displays.
Recent Displays lists of recent criteria. These are not saved lists.
(desktop They are simply text indicating the most recently used
only) criteria.

Defining New You can clear all fields in the Find Objects window. This prepares the window for you to
Query Criteria quickly specify new criteria. “All” is indicated with an asterisk (*) in each entry area.

To clear all fields to define a new query

• Click or select New from the Query menu.

Saving Query Once you specify the vault, type, name, revision, owner, and/or Where clauses as your
Criteria search criteria, you can save the current query criteria with a specific name.

To save a query
1. Select Save As from the Query menu.

Chapter 3: Finding Objects 111

 2. Type a name for the query in the Name text box.
Or
Select a query (to overwrite) from those displayed.
3. Click OK.

Using Saved There are two ways to open saved criteria:

Criteria • Select from a display of saved criteria.
• Scroll through criteria that was saved or used in the current session.

To select from saved criteria

1. Click or select Open from the Query menu

.

2. Select a query from those displayed.

Or
Type the name of the saved query in the Name text box.
3. Click OK.
The criteria for the selected query is displayed in the Find Objects window. Criteria
that was previously specified in any field of any tab in the Find Objects window is
replaced with the saved query’s criteria.

Using Recent Query menu options and tools enable you to work with recent search criteria. This criteria
Criteria includes the vault, type, name, revision, owner, and Where clause(s) that have been
specified during the current user session.

112 Matrix Navigator Guide

 Criteria are saved in the recent criteria list. It is possible to scroll through this recent
criteria.

To display the next previous criteria in the recent list

• Click or select Back from the Query menu.

To display the next saved criteria in the recent list

• Click or select Forward from the Query menu.

To select from recently used criteria (desktop version only)

1. Select Recent from the Query menu to display recent criteria.
These are not necessarily saved lists. They are simply text indicating the most
recently entered criteria. For example:

2. Select a line of criteria.

The selected criteria is displayed in the Find Objects window.

Deleting a Query You can delete a saved query.

To delete a saved query

1. Select Delete from the Query menu.
The Delete Query window is displayed:

2. Select a query from those displayed and click OK.

Chapter 3: Finding Objects 113

 Find Like

Find Like is a specialized find that lets you select business object types to help formulate
queries. Find Like is meant to augment, not replace, normal Find, which is useful for
finding multiple types or for simple queries without many constraints.
Find Like gives you the tools to build a query even if you don’t know the specifics about
the type of object for which you are searching. It lets you pick and choose search criteria
that is specific to the type selected.

Initiating a Find To find objects using Find Like, you must open the Find Like window and then specify the
Like Query search criteria.

To initiate a Find Like query

1. Click or select Find Like from the Set menu.

2. Select a type from the panel on the left side of the window. To see subtypes for a type,
click the plus sign (+) in front of the type.
3. Specify the search criteria on the right side of the window. The constraints in the right
side of the window are specifically related to the type selected. The constraints are
explained in the sections that follow.

If you change the type in the left side of the window, it may take a few seconds to load
values in the right side of the window, since Matrix Navigator is searching the database to
display only those constraints that match the selected type.

Since the search criteria is based on the type, you can only select one type at a time. To
search multiple types, use the Find window. See Memory for additional information.

114 Matrix Navigator Guide

 4. To clear the browser and display only objects that match your query, select Replace
Objects at the bottom of the Find Like window.
To add found objects to those already displayed in the browser, select Append
Objects.
5. Click Find to initiate the query.
Matrix Navigator displays the query results in the current browser. For example, if
you initiate the search from the Navigator browser, the results display in the browser.

Find Like The Find Like window contains constraints based on the basics and attributes of the
Constraints selected type. The constraints include properties, operators that are specific to those
properties, and values based on the properties. The constraints side of the window has
three sections:
Properties for Operators Values
selected type

Operators are context sensitive based on the kind of property:

Property Types Operators

String (e.g., Description, Name, etc.) begins with, ends with,
includes, is (exactly),
is not, matches
Real numbers and integers (e.g., at least, at most, does
Cost, Number of Pieces, etc.) not equal, equals, is
between, less than, more
than
Date and time (e.g., Modified, on, on or after, on or
Originated) before

For example, an attribute of Total Cost would have operators relating to numbers (at least,
at most, etc.) and would not include operators relating to words (begins with, ends with,
etc.)

Chapter 3: Finding Objects 115

 The values in the third column can be typed in. Whenever range values have been
predefined, a drop-down list is provided for you to select a value. For example, if the
property is Policy, only those policies that apply to the selected type are listed in the
value’s drop-down list:
When defining criteria, you can either use the drop-down lists or you can type in the
information to search on. If you type more than one option, separate each option with a
space. For example, when using the operator is between, type the two numbers with a
single space to separate them. For example:

Any information entered in a value field is ignored if the corresponding operator field is
blank.

Expanding Types In the Find window, there is a check box labeled Expand which causes Matrix Navigator
also to find the subtypes of the specified types that meet the search criteria. For example,
searching for the type Parts with Expand turned on results in objects of the type Parts, plus
objects of the type Components and Assemblies, which are subtypes of Parts.
In Find Like, Expand is always on and cannot be turned off.
If you are viewing a top-level type, you can select the plus sign (+) to the left of the type to
see subtypes. You’ll notice that in the right side of the window, all applicable constraints
are carried over to the subtypes. If any constraints are not included for a particular
subtype, they do not appear. If you then go back and view the original type again, you will
see the original constraints that you specified. In other words, the Find Like window has a
memory so you do not have to re-select constraints while navigating the type hierarchy.
For example, consider a type Furniture. Subtypes include Chair and Table. Subtypes of
Chair include Wingback and Recliner. Fabric is an attribute on Chair, so it also on
Wingback and Recliner. If you select Furniture, there is no Fabric attribute. If you expand
Furniture and Chair, you can then select Wingback and set fabric to “matches Tweed.” If
you look at Table, there will be no Fabric attribute. But if you then click again on Chair,
WingBack, or Recliner, you will see the Fabric attribute set to “matches Tweed.” You can
change your selection for any constraint at any time.

Memory Find Like contains a memory feature that persists throughout the current session. That is,
when you execute a search, Find Like retains all information from the most recent Find
Like query, including the type and all constraint information related to it. The next time
you select either Find or Find Like, the system remembers the previous Find Like query
information so you can use the same query again or make minor modifications.
• If you want to clear a single field in the Find Like window, use the Backspace or
Delete key to erase information from either the Value field or the Operator field.
You can also click the down arrow on the Operator field and select the blank option,
which is included at the top of the list in every Operator drop-down list.

• Click or select New from the Query menu if you want to define completely
different search criteria. All previously-defined search criteria is erased so you can
define all new constraints.

116 Matrix Navigator Guide

 The Find window also contains all information from the most recent Find Like query. Find
Like actually builds a query to go into the Where clause in the Find window. This is a
convenient way to expand your search for multiple types. For example, suppose your Find
Like search criteria includes a type of Blueprint and you’re looking for a description
containing the word “primary” and dates between March 1 and May 1. If you open the
Find window, you can then add Document to the Type field and initiate a search for both
Blueprints and Documents, sharing the previously specified search criteria.

Because the Find window can include complex Where clauses, information entered in the
Find window is not automatically translated to the Find Like window.

Query Menu In the Find Like window, the Query menu options and tools enable you to work with
saved search criteria as described in the table below.

New Clears all fields from the Find Like window so you can
specify new criteria.

Save As Allows you to save the current query criteria with a specific
name.

Chapter 3: Finding Objects 117

118 Matrix Navigator Guide
 4
Using the Visuals
Manager

Overview

Matrix Navigator can contain many different kinds of objects representing all sorts of
business items which may or may not be interrelated. However, in your role within the
company, you may only need to work with certain types of information at certain points in
its lifecycle, with which you can perform the same tasks.
For example, a purchasing agent may start a Matrix Navigator session and perform a
query to find all purchase requisitions to update a set. All of them are not yet approved, so
the day’s workload is not as large as the whole set. The purchasing agent could establish a
filter that only shows the purchase requisitions that are approved. The person could add
cues so approved requisitions appear in red, and then turn green once they are ordered. It
would then be very clear to the purchasing agent just what work needed to be done.
Visuals are tools that let you identify and manage the objects that you interact with in your
daily use of Matrix Navigator. Visuals are personal settings that are available only when
context is set to the person who defined them. Visuals can also be defined and shared
among users who are assigned to a role.
The following items can be set up using the Visuals Manager:
• Filters that parses information stored in ENOVIA Live Collaboration and displays
only those objects that meet the filter criteria, like only objects in a certain state or of
the latest revision. Different filter options provide differing view of the same
information based on the filter criteria.

119
 • Cues that control the color and font in which certain objects appear in all browsers.
For example, you could create a cue that would change the approved objects red or in
large bold font.
• Object Tips that automatically appear when you hold your mouse pointer over an
object. For example, if you want to quickly see if any files are checked into an object,
you could create an object tip to display file names.
• Toolsets that contain programs or wizards that perform routine tasks. For example,
the Purchasing Agent could add a program that creates a Purchase Order and attaches
it to the Purchase Requisition to a toolbar for execution via a button. When toolsets
are turned on, Matrix Navigator creates a toolbar with a button for each program that
is a member of the toolset.
• Tables that display the information you need to use. The table you create and select
appears when you choose Details from the View menu.
After creating a visual, it is available from the appropriate View submenu. For example,
suppose you use the Visuals Manger to create two cues called Past Due and Current.
When you select the View>Cue menu, Past Due and Current appear in the submenu. If the
cues are turned on, check marks appear next to them. You can toggle visuals on and off
from the submenus.
You can use View Manager (described in the next chapter) to create personalized views
that package multiple visuals so you can activate them all with a single mouse click.

120 Matrix Navigator Guide

 Creating Visuals

To create a new visual, use the procedures in the following sections. Refer to later sections
of this chapter to learn how to view, edit, clone, and delete any type of visual.

Creating Any Many of the steps for creating a visual are the same no matter which visual you are
Visual creating. This section gives the steps that are the same for any visual that you create.

To create any visual

1. Select Visuals from the View menu.
The Visuals Manager opens:

2. Click the toolbar button that represents the kind of visual you want to create or select
the visual from the View>New submenu.
The New window opens for the kind of visual you selected. As an example, here is
the New window for filters.

3. Create the new visual using the procedures in the following sections:

Chapter 4: Using the Visuals Manager 121

 Creating a New Filter
Creating a New Cue
Creating an Object Tip
Creating a Toolset
Creating a New Table
4. When you have entered the information for the new visual, click Create on the New
window.
The new visual is listed in the appropriate tab on the Visuals Manager.
5. If the visual you created is a table, proceed to Step 6. Otherwise, perform one of the
following steps, then skip to Step 7:
If you want the visual to be turned on every time you begin a session, make the visual
active by checking the box to the left of the visual. You can turn off an active visual at
any time by unchecking the visual from the View menu submenus in any Studio
Modeling Platform or Navigator browser.
Or
If don’t want the visual to be active whenever you begin a session, leave the box to
the left of the visual unchecked. You can turn on the visual at any time by checking
the visual from the View menu submenus in any Matrix Navigator browser.
For more information about activating and turning on visuals, see Using Visuals in
Matrix Navigator Browsers.
6. If you want the table to be the default table (the table displayed whenever Details
mode is selected in the Navigator browser), select the table so the circle to the left of
it is filled in.
Or
If you don’t want the table to be the default, leave the table’s circle blank. You can
switch to another table at any time by checking the table from View>Table in any
Matrix Navigator browser.
7. To keep the Visuals Manager open, click Apply.
Or
To close the Visuals Manager, click OK.
The visual is added to the appropriate submenu of the View menu. All newly created
visuals are turned off, even if you activated them. Activated visuals will not turn on
automatically until you begin a new session. (The behavior is slightly different if you
have a view selected when you create a visual. For information, see Visuals and
Views.)

Creating a New Filters limit the objects or relationships displayed in any browser to those that meet certain
Filter conditions previously set by you. You define filters using the Visuals Manager, then turn
them on or off depending on what you want to view. They may be active in one view and
available, but inactive, in another view. Refer to Using View Manager in Chapter 6 for
more information about views.
For example, you could specify that only objects in a specific state, or only the
relationships connected toward an object (not to and from or just from) be displayed when
a specific filter is turned on.

122 Matrix Navigator Guide

 Saved filters are personal settings and display on the Filters tab within the Visuals
Manager. They also appear in the Filter submenu of the View menu and in the filter bar
(desktop version only).
You can create a filter either by creating a new, original filter or by cloning an existing
filter. Creating a new, original filter is described in this section. See Cloning a Visual later
in this chapter for information on that procedure.

To create a new filter

1. From the Visuals Manager, click or select New then Filter from the View menu.
The New Filter window opens:

Enter a name for the filter in the Name text box. Filter names cannot include
asterisks.
2. Select whether the filter applies to Business Objects or Relationships.
Since relationships and objects can have the same attributes, filters must specify to
which one they should apply.
3. Choose the Query tab.

Chapter 4: Using the Visuals Manager 123

 You use this tab to define what objects should appear when this filter is applied in any
browser. For example, if only the Change Order type objects found in the Corporate
vault should appear when this filter is applied, you specify those conditions in this
tab. You can also define a more specific Where clause using the tab.
The New Filter Query tab is similar to the standard Query window. For details on
how to enter queries, refer to Searching for Objects in Chapter 3.
For filters that apply to relationships, you can specify the To and/or From side of the
relationship by choosing the Direction: To, From, or Both. (For filters that apply
only to business objects, Direction defaults to Both.)
4. After entering all of your query information, click Create to create the new filter.
The new filter is displayed in the Filters tab of the Visuals Manager.
.

5. If you want the filter to be turned on every time you begin a session, make it active by
checking the box to the left of the filter.
Or

124 Matrix Navigator Guide

 If don’t want the visual to be active whenever you begin a session, leave the box to
the left of the visual unchecked.
For more information about activating and turning on visuals, see Using Visuals in
Matrix Navigator Browsers.
6. To keep the Visuals Manager open, click Apply.
Or
To close the Visuals Manager, click OK.
The filter is added to the Filter submenu of the View menu. All newly created filters
are turned off, even if you activated them. Activated filters will not turn on
automatically until you begin a new session. (The behavior is slightly different if you
have a view selected when you create a visual. For information, see Visuals and
Views.)

Creating a New Cues control the appearance of business objects and relationships inside any Matrix
Cue Navigator browser—to make certain objects and relationships stand out visually for the
user who created them.
This appearance control is based on criteria that you specify such as attribute value,
current state, or lateness. Objects and relationships that meet the criteria can appear in any
distinct color. Line styles (thick, dotted, etc.) can also be applied to relationships, while
changes in font (style, size and bold) can be applied to objects.
You can save a cue and not make it active. This allows for multiple or different sets of
conditions to be used at different times or as a part of different views. See Using View
Manager in Chapter 6. You define cues using the Visuals Manager and save them in your
personal settings. You can turn on cues from the View menu.
You can create a cue either by creating a new, original cue or by cloning an existing cue.
Creating a new, original cue is described in this section. See Cloning a Visual later in this
chapter for information on that procedure.

To create a new cue

1. In the Visuals Manager, click or select New then Cue from the View menu.
The New Cue window opens.

Chapter 4: Using the Visuals Manager 125

 2. Enter a name for the cue in the Name text box. Cue names cannot include asterisks.
3. Select whether the cue applies to Business Objects, Relationships, or both Business
Objects and Relationships.
Since relationships and objects can have the same attributes, cues may specify to
which one they should apply. Also, the visuals of an object (described later in this
procedure) are color and font, while the visuals of a relationship are color and line
type.
4. Select the order in which the objects/relationships are displayed in relation to other
cues.
If more than one cue can apply to an object, Matrix Navigator needs to know which
visuals to present.
Before other cues—Lowest priority. These visuals are applied first with any
subsequent visual changes allowed.
With other cues—These visuals are applied in the order in which they are activated.
After other cues—Highest priority. Objects change to these visuals after any others
are first applied.
5. Click the Query tab.

126 Matrix Navigator Guide

 You use this tab to define what objects should appear with this cue displayed. For
example, if the cue should display for only the objects found in the Corporate vault,
specify the Corporate vault in this window. You can also define a more specific
Where clause.
The New Cue Query tab is similar to the standard Query window. For details on how
to enter queries, refer to Searching for Objects in Chapter 3.
For cues that apply to relationships, you can specify the To and/or From side of the
relationship by choosing the Direction: To, From, or Both. (For cues that apply only
to business objects, Direction defaults to Both.)
6. Click the Visuals tab.

7. Use this tab to define the appearance of the objects and relationships in any of the
browsers.

Chapter 4: Using the Visuals Manager 127

 • To specify a color for the object text and/or relationship arrow that normally will
be displayed when this cue is activated, choose a color from the Color list.
• To specify a color for the object text and/or relationship arrow that will be
displayed when the cue is activated and the object or relationship is selected,
choose a color from the Highlight list.
• To specify a font for the object text, choose a font from the Font list or type a
font name, such as MS Sans Serif or Arial. Choose whether you want the font to
be Bold or Italic, and enter a Size.
• To specify a line style for the relationship arrow displayed between objects,
choose a style from the Line style list. This control is available only if you are
applying the cue to relationships.
8. When you are finished defining the cue, click Create.
The new cue is displayed in the Cues tab of the Visuals Manager.

9. If you want the cue to be turned on every time you begin a session, make it active by
checking the box to the left of the cue.
Or
If don’t want the cue to be active whenever you begin a session, leave the box to the
left of the cue unchecked.
For more information about activating and turning on visuals, see Using Visuals in
Matrix Navigator Browsers.
10. To keep the Visuals Manager open, click Apply.
Or
To close the Visuals Manager, click OK.
The cue is added to the Cue submenu of the View menu. All newly created cues are
turned off, even if you activated them. Activated cues will not turn on automatically
until you begin a new session. (The behavior is slightly different if you have a view
selected when you create a visual. For information, see Visuals and Views.)

128 Matrix Navigator Guide

Creating an Object Object tips are small pop-up windows that appear when you hold the mouse pointer
Tip briefly over any object in a browser. They are similar to the ToolTips that appear over
toolbar buttons in many programs to tell you what the button is for. However, unlike
ToolTips, you can define the contents of the object tip window to display the information
you need most often about the objects you use. Each tip evaluates a single expression
about the object, but multiple tips can be created and applied simultaneously to the same
objects.
For example, you could include any attribute or basic property for an object that you
frequently need to know, such as the current owner, or the last date the object was
changed. This gives you a quick way to check basic data about an object without having to
select Basics or Attributes from the menu or toolbar. The graphic below shows a tip that
gives the object’s owner.

You can save object tip definitions by name (as personal settings) and turn them on or off
as you need them. A single tip may become part of several views, perhaps being activated
in one, and available in another. Refer to Using View Manager in Chapter 6 for more
information on views. You can also display the content of tips under objects that appear in
browsers instead of the standard title. For information, see Viewing Tip Content Instead of
Object Titles.
You can create an object tip either by creating a new, original object tip or by cloning an
existing object tip. Creating a new, original object tip is described in this section. See
Cloning a Visual later in this chapter for information on that procedure.

Creating a New Tip

To create a new object tip

1. In the Visuals Manager, click or select New then Tips from the View menu.
The New Object Tip window opens:

2. Enter a name for the object tip in the Name text box. Tip names cannot include
asterisks.

Chapter 4: Using the Visuals Manager 129

 3. Select whether the object tip applies to Business Objects or Relationships.
Since relationships and objects can have the same attributes, object tips must specify
to which they should apply.
4. Click the Query tab.

You use this window to define the objects to which the tip will apply. Enter all the
query information and click OK.
The New Object Tip Query tab is similar to the standard Query window. For details
on how to enter queries, refer to Searching for Objects in Chapter 3.
For tips that apply to relationships, you can specify the To and/or From side of the
relationship by choosing the Direction: To, From, or Both. (For tips that apply only
to business objects, Direction defaults to Both.)
5. Click the Expression tab.

You use this tab to define what information will be included in the tips pop-up when it
appears over an object, as described in the following steps.

130 Matrix Navigator Guide

 6. Click the Expression ellipsis button.
The Select Pattern chooser is displayed.

7. The Basic properties of an object are listed for selection. You can also display
Attributes, Relationships, or States by checking the boxes and clicking Filter. You
can filter on the Name as well.
Select the item you want to include in the object tip pop-up, and then click OK. The
Expression tab appears listing the item you just selected. You can further refine the
tip with a valid selectable for that item.
Selecting a Basic property or Attribute alone is enough to display that value—owner
or attribute[Target Cost] are both acceptable. However, using the
selectable syntax, you can get to and display more deeply rooted information. For
example, state[Release].scheduled displays the scheduled date for the
Release state. And relationship[Documents] displays true on objects that
have a connection of this type. For more information on selectables, see the
“Selectables” appendix in the ENOVIA Live Collaboration Studio Modeling
Configuration Guide.
Each tip can include only one MQL expression. That is, you cannot use && (and) or ||
(or) qualifiers. To show more than one piece of information about an object, activate
multiple tips.
8. Click Create.
The new tip appears in the Tips tab.

Chapter 4: Using the Visuals Manager 131

 9. If you want the tip to be turned on every time you begin a session, make it active by
checking the box to the left of the tip.
Or
If don’t want the visual to be active whenever you begin a session, leave the box to
the left of the visual unchecked.
For more information about activating and turning on visuals, see Using Visuals in
Matrix Navigator Browsers.
10. To keep the Visuals Manager open, click Apply.
Or
To close the Visuals Manager, click OK.
The tip is added to the Tip submenu of the View menu. All newly created tips are
turned off, even if you activated them. Activated tips will not turn on automatically
until you begin a new session. (The behavior is slightly different if you have a view
selected when you create a visual. For information, see Visuals and Views.)
Object tip pop-ups display up to 100 total characters. Each tip you turn on appears on
a separate line with lengthy values truncated. Tips appear top to bottom in the order
they are turned on.

Creating Tips that Include Text Labels

If you want to create multiple tips that first display a literal text label, and then the variable
text to be included in the tip, simply enclose the label text in quotes, such as, “Object
Owner”.
For example, you could create the first tip called OwnerText with the expression
“Object Owner” then a second tip called Owner with the expression owner. If you
first activate OwnerText (with the literal text label), then Owner, for each object you see a
tip where the first line contains the label Object Owner and the second line contains the
actual owner’s name.

When creating a literal text label tip, you cannot use keywords such as current or owner.
Quotes should be used with keyword expressions if spaces are used in the values (for
example, if spaces are used in state or user names).

Creating a Toolset Your Business Administrator creates programs to perform specific functions. Some
programs run automatically when certain trigger events occur, such as the promotion of an
object to a new state. Other programs can be executed to automate and standardize a
common task, such as creating a cost analysis for a project or creating a report on a
project. Business Administrators create three types of programs:
• Programs, which can be executed without first selecting an object. This type of
program might perform a query and generate a report on the found objects.
• Methods, which are programs that require a business object instance and are
associated with particular object types. For example, a method on a Product object
might create a User’s Guide object of the same name and connect it to the Product
automatically.
• Wizards, which are programs with a user interface that ask a series of questions and
then execute code. Wizards are similar to many Windows installation programs, and
can be used in Matrix Navigator to simplify or standardize a complex process.

132 Matrix Navigator Guide

 Wizards can be either stand-alone, like other programs, or require a business object
on which to act, and so become a method. Wizards are really a special type of Matrix
Navigator program and can be used as a program or a method within Matrix
Navigator.
When creating toolsets, you can access the list of all available programs and methods, and
then add a toolbar with access to these functions to your Matrix Navigator browsers.
Methods can also be executed from the menu bar. You may want to consult your Business
Administrator when customizing your toolsets to determine the optimal selection for your
individual use of Matrix Navigator. See Executing a Method later in this chapter.
You create a toolset by selecting the programs and methods you’ll need to execute, as
described in this section. You can also clone an existing toolset, as described in Cloning a
Visual later in this chapter.

To create a new toolset

1. From the Visuals Manager, click the Tools tab.

2. Click or select New then Tool from the View menu.

The New Toolset window opens.

3. Enter a name for the toolset in the Name text box. Toolset names cannot include
asterisks.
4. Click the Programs tab. The available stand-alone programs and wizards are
displayed. Select the programs and wizards to be added to the toolset. As you select
each program, click Add to move it to the left side of the New Toolset window. Click
Remove if you change your mind.
5. Select the Methods tab. An indented type hierarchy is displayed. Types can be
expanded to show their methods. Select the methods to be added to the toolset and
click Add to move them to the left side of the New Toolset window. Click Remove if
you change your mind.
6. When you are finished adding programs and methods, click Create.

Chapter 4: Using the Visuals Manager 133

 The tool is listed in the Tools tab.

7. If you want the tool to be turned on every time you begin a session, make it active by
checking the box to the left of the tool.
Or
If don’t want the visual to be active whenever you begin a session, leave the box to
the left of the visual unchecked.
For more information about activating and turning on visuals, see Using Visuals in
Matrix Navigator Browsers.
8. To keep the Visuals Manager open, click Apply.
Or
To close the Visuals Manager, click OK.
The tool is added to the Tool submenu of the View menu. All newly created tools are
turned off, even if you activated them. Activated tools will not turn on automatically
until you begin a new session. (The behavior is slightly different if you have a view
selected when you create a visual. For information, see Visuals and Views.)
The new toolbar only appears when the toolset is turned on, as shown below.

New toolset toolbar in

Matrix Navigator

Tips displaying the program name pop up in a window when the mouse pointer briefly
stops over the program buttons. However, you may wish to ask your Business
Administrator about supplying identifying icons to the programs you need on your
toolbar.

Executing a Method
To execute a method, you must first select an object. There are three ways to execute a
method:
• From the Objects menu.
• From the right-click menu in a browser.

134 Matrix Navigator Guide

 To execute a method from the Object menu
1. Select a business object.
2. Select Methods from the Object menu.
The Method Chooser is displayed, showing all methods, (programs and wizards)
associated with the type of object selected.

3. Select the method you want to execute.

4. Double-click the method, click , or select Execute from the Method menu.
The method is executed.
5. Click Close.

To execute a method from the right-click menu

1. Right-click an object and select Execute.

Chapter 4: Using the Visuals Manager 135

 2. Select the name of the method you want to execute from the Execute menu.
The method executes.

Creating a Table In Matrix Navigator, a table is a user-defined template of columns that you can use to
display information about objects. Each row of the table represents one business object.
These tables are displayed when Details mode is selected in either Studio Modeling
Platform or Navigator browsers. The following graphic highlights the characteristics you
control when you create a table. Each characteristic is described in detail below.
Column heading Editable column

• Number of columns—You add each column that you want in the table.
• Content of the columns (expression)—You control the content of a column by
specifying an expression that the system evaluates for each object (or relationship) in
the browser.

136 Matrix Navigator Guide

 For help formatting expressions, see the “Selectables” appendix in the ENOVIA Live
Collaboration Studio Modeling Configuration Guide.

• Whether the expression applies to objects or relationships—The expression you

enter for a column can apply to the business object or to the relationship. The
expressions for the first two columns in the table shown above apply to objects, the
second two columns apply to relationships.
Column expressions
can apply to the
business object

or to the relationship
in each row of a table

• Column headings—You can enter your own heading or let the system enter a
heading based on the expression.
Programs should be used only in special circumstances, since they can significantly
slow down the table display.
• Whether you can edit cells in the column—If you want to be able to edit the data
for a column, you can mark a column as editable. Only columns whose expressions
are attributes or descriptions can be edited and you must have the appropriate access
privileges to edit data. If an editable column is an attribute with defined ranges, a
drop-down list of all options is provided.

• Whether column widths are sized automatically—You can have the system
automatically adjust the column width to the width of the longest cell in the column or
you can choose to specify the column width. Widths are specified by dragging the
column heading in the table definition. In either case, you can drag the heading when
you use the table to adjust the column width.

Creating a New Table

You can create a table either by creating a new, original table or by cloning an existing
table. Creating a new, original table is described in this section. See Cloning a Visual later
in this chapter for information on that procedure.

To create a new table

1. From the Visuals Manager, click or select New then Table from the View menu
(in Visuals Manager).
The New Table window opens:

Chapter 4: Using the Visuals Manager 137

 2. Enter a name for the table in the Name text box. Table names cannot include asterisks
or commas.
3. Click Add. Use the Column Expression window to define each column in the new
table.

4. Define the content of the column by entering an Expression.

a ) Click the Expression ellipsis button.
The Select Pattern chooser opens and lists the Basic properties of an object. You
can also display Attributes, Relationships, and/or States by selecting the
appropriate check boxes and clicking Filter. You can filter on the Name as well.

b ) Select the property you want to include as a table column and then click OK.

138 Matrix Navigator Guide

 The New Table Column window shows the expression you just selected.
You must define a new column for each MQL expression you want to use in the
table. That is, you cannot use && (and) or || (or) qualifiers. However, you can use
operators on numeric values. For example:
attribute[Target Cost] - attribute[Actual Cost]
For help formatting expressions, see the “Selectables” appendix in the ENOVIA
Live Collaboration Studio Modeling Configuration Guide.
5. Select whether the expression applies to Business Objects or Relationships.
Expressions that apply to relationships will only be evaluated when shown in a
Navigator browser in details mode (the column will be blank when used in Studio
Modeling Platform browsers.) For more information about applying expressions, see
Applying Expressions to Relationships vs. Business Objects.
6. To enter a unique name for the column heading, check Custom Heading and enter
the name in the Heading text box. If you do not check Custom Heading, the column
heading defaults to the expression of the column.
7. To have the system automatically adjust the column width to the width of the longest
cell in the column, check Autosize Heading. If you do not check Autosize, you can
adjust the column width by dragging the column edges in the New Table window. For
more information on Autosize Heading, see More About Cell Settings.
8. To allow the user to modify the contents of cells in the column, check Editable. This
setting is only valid for columns that contain attributes or descriptions. For more
information about editable columns, see More About Cell Settings.
9. Click OK to add the column to the table. Repeat Steps 3 through 9 for each column
you want to include in your table.
10. When you have defined all the columns for your table, click OK.
The New Table window shows all the columns you have just defined.
You can rearrange and delete columns by selecting a column (not in the heading, but
in the area that displays the expression) and clicking Move Right, Move Left, and
Delete. You cannot move or delete the first column, Object.
You can rearrange columns only in the Studio Modeling Platform. To delete columns
in the Web version, double-click the column and choose Delete.
11. Once you are satisfied with the table, click Create.
The Visuals Manager Tables tab lists the new table you created.

Chapter 4: Using the Visuals Manager 139

 12. To make the new table the default table for Details mode, click the circle to the left of
it so the circle is filled in. This is different from the other Visuals check boxes since
only one table can be active at a time.
13. Click Apply or OK.

More About Cell Settings

The system displays the content of table cells based on the following settings:
• The Editable setting in the table column. If this setting is not selected for the column,
you cannot edit the contents of the column. The editable setting applies only if you
have modify access to the contents of the cell.
• The Multi-line setting in the attribute definition. Scroll bars are provided only when
an editable column contains a multi-line attribute (including description).
• The Autosize Heading setting in the table column. With the Autosize Heading setting
on, vertical scroll bars appear in multi-line, editable cells on the right of whatever
portion of the column is displayed. However, when off, the width of the column may
be adjusted by dragging the column separator line in the heading row when a table is
in use.
• Defined Ranges. If an attribute has one or more defined ranges, they are displayed in
a drop-down list when the table cell is double-clicked for editing.
With these points in mind, we recommend you turn off Autosize Heading when creating
editable table columns. This is especially true when column widths are unpredictable and
likely to be wide. This way, although the values are truncated, the width of the column is
known and the columns that follow will not be pushed off the screen. When selected, the
text of an editable, multi-line cell wraps and scroll bars appear. For single-line,
fixed-width columns, you may use the arrow keys for scanning truncated values, or you
can increase the column width. For more information on how to edit table cells, refer to
Chapter 2, Using a Table.

Applying Expressions to Relationships vs. Business Objects

How you choose to apply a column expression depends on the information you want, how
you define the expression, and how you want the information to display. You can get the

140 Matrix Navigator Guide

 same information into a table by defining a slightly different expression and applying it to
relationships instead of objects.
For example, suppose you want a column to show the quantity attribute of a relationship.
Since this attribute could be on multiple relationship types, you should first add a column
that contains the name of the relationship, using the expression name and applying it to
relationships. Then, you could add a column with the expression
attribute[Quantity] for the column’s expression, also applying it to relationships.
The graphic below shows this example.

On the other hand, suppose you wanted to display the “as manufactured” information
about multiple objects in one table, for use in a Studio Modeling Platform browser table
which does not display relationships. You could have a table with a column that showed
the name of the objects connected with that relationship (with an expression defined as
from[BOM-As Manufact].to.name), and another that showed the Quantity on the
relationship (with an expression defined as from[BOM-As
Manufact].attribute[Quantity]). The graphic below shows the results:

As you can see, expressions about relationships that apply to business objects are much
more complicated than those that apply to relationships.

Working with Tables

After you create tables, you can display them in browsers, switch between different tables,
sort and edit data, and print a table, as described in Chapter 2, Using a Table. You can also
add tables to a custom view, as described in the next chapter. Each time you activate that
view, the table you have defined for it displays.

Chapter 4: Using the Visuals Manager 141

 Viewing or Editing a Visual

You can view or edit any visual by following the procedures below. Once you have
created a visual, use the Edit procedure to make any changes. This is similar to the way in
which you would view or edit any object.

To view or edit a visual

1. Select Visuals from the View menu.

2. From the Visuals Manager, click the tab that lists the visual you want to edit or view.
In this case, the Tables tab is selected.
3. Select a visual from the existing list. It does not have to be activated to select it.

4. Click or select View from the View menu.

Or

Click or select Edit from the View menu. To edit the definition, you can also
double-click the object.
You can edit the conditions, queries, column headings, and expressions in the same
way you did when you created the visual. See each section about creating that type of
visual for more information.

142 Matrix Navigator Guide

 Cloning a Visual

You can create a clone of a visual, then edit it to create another visual. This saves time
when creating similar visuals, or copying complex filters or tables to modify them.

To clone a visual
1. Select Visuals from the View menu.
2. From the Visuals Manager, click the tab that lists the visual you want to edit or view.
3. Select the visual you want to clone to create a new visual.
4. Select Clone from the View menu in the Visuals Manager.
The Clone-visual window displays, where visual is the name of the visual you are
cloning. In this case, the Clone - Filter BOM As Manufactured window displays:

5. Enter a name for the new visual in the Name text box and click Create.
6. Edit the visual to differentiate it from the original visual.

Chapter 4: Using the Visuals Manager 143

 Using Visuals in Matrix Navigator Browsers

The Visuals Manager gives you the ability to create visuals to quickly identify certain
attributes and relationships of a selected object. With these visuals, accessed from the
View menu in any Studio Modeling Platform or Navigator browser, you can control the
objects that are displayed and what characteristics are shown.

It is important to realize that visuals are personal settings that are available only when
context is set to the person who defined them.

Activating vs. Activating a visual from the Visuals Manager is very different from turning on a visual
Turning On from the View menu submenus.
Visuals
Activating Visuals from Visuals Manager
Activating a visual from the Visuals Manager means the visual will be turned on in all
browsers whenever you begin a new session. After activating a visual, you must begin a
new session to have the visual turn on automatically.
The intent of the Visuals Manager is to prepare for a working session—to adjust (and
probably restrict) your view of the database according to the tasks you intend to perform.
You use filters to restrict your view of the database by displaying only the objects and
relationships that are pertinent to the task at hand. You use particular tips and cues to
graphically highlight information about them and particular tools (programs, wizards) to
perform operations on them.

Turning On Visuals from View Menu

Turning on a visual from a submenu of the View menu turns on the visual in the current
browser and any spawned from it. The next time you begin a new session, the visual will
be turned off (assuming the visual has not been activated from the Visuals Manager).
The intent of the submenus in the View menu is to provide a way of fine-tuning the setup
you established using the Visuals Manager.

Activating and This section describes how to activate and deactivate visuals. For a description of what it
Deactivating means to activate a visual, see the previous section.
Visuals To activate or deactivate a visual
1. Select Visuals from the View menu.
2. From the Visuals Manager, click the tab that corresponds to the kind of visual you
want to activate or deactivate. For example, to activate a filter, click the Filters tab.

144 Matrix Navigator Guide

 3. If you want the visual to be turned on every time you begin a session, make the visual
active by checking the box to the left of the visual. You can turn off an active visual at
any time by unchecking the visual from the View menu submenus in any Studio
Modeling Platform or Navigator browser.
Or
If don’t want the visual to be active whenever you begin a session, leave the box to
the left of the visual unchecked. You can turn on the visual at any time by checking
the visual from the View menu submenus in any Matrix Navigator browser.
For instructions on turning visuals on and off, see Turning Visuals On and Off.
4. To keep the Visuals Manager open, click Apply.
Or
To close the Visuals Manager, click OK.
If you activated the visual, it will not turn on automatically until you begin a new
session.

Turning Visuals You can use this procedure to turn a visual on or off from any Studio Modeling Platform
On and Off or Navigator browser. Before you can turn a visual on or off, it must first be created in the
Visuals Manager.

If you do not have read access to an object, a turned on visual is not applied, even if the
object meets the specified query criteria.

To turn a visual on or off in any browser

1. Use the View>View submenu to make sure the current view contains the visual.
Select All to access all visuals.
2. From the View menu, select the type of visual you want to apply. This example shows
a filter being selected from a Navigator browser in Indented mode, but the procedure
is the same in the Studio Modeling Platform browser, with other browser modes, and
with other types of visuals.

Chapter 4: Using the Visuals Manager 145

 3. To turn on a visual, select an unchecked visual from the submenu.
With the exception of filters, visuals affect the display of objects in all the browsers
and are applied immediately when they are turned on. Filters are applied immediately
in the Matrix Navigator browser and when used in the Navigator in Star mode.
However, when filters are applied in Navigator’s Indented or Details mode, they are
applied “from this point on”—subsequent expansions will use the new filter, allowing
each level of an indented structure to use different filter criteria.
When a visual is applied, the status field at the bottom of the screen displays a
"Loading..." message while the query criteria is processed.
– If you turn on more than one filter, the browser displays objects that meet any of the
applied filters. In other words, an object needs to meet only one applied filter to be
shown; an object need not meet all applied filters.
– If you load a toolset and it appears that one of the tools is missing, the program may
have been renamed or modified by the Business Administrator. You will need to add
the tool to the toolset again from Visuals Manager. Consult your Business
Administrator to determine the new name.
4. To turn off a visual, select a checked visual from the submenu.

Visuals and Views A view is a set of visuals that you can save and name. Views let you quickly turn on a
number of visuals and then switch to a completely different set of visuals. The following

146 Matrix Navigator Guide

 chapter explains how to create and use views. This section describes how turning on a
view determines which visuals are available.
When no view is turned on, all visuals that you have created are listed in the View menu
submenus. Having no view turned on means that All is selected from View>View. The All
selection indicates that all visuals are listed, not just those that belong to a particular view.
(Having no view turned on is sometimes referred to as the All view because it is the set of
all your visuals.)
When you turn on a view, only those visuals that you added to the view are listed in the
View menu submenus. All other visuals are removed from the submenus. To access the
removed visuals, you’ll have to select View>View>All or select a view that has the visual
you want.
If you create a new visual when no view is turned on (View>View>All is selected), the
new visual appears in the appropriate submenu of the View menu. However, if you create
a visual when a view is turned on, the visual does not appear in the View menu submenu
until the visual is added to the current view or View>View>All is selected.

For the Web version of Matrix Navigator only: If you create a new visual when a view is
turned on, the system temporarily displays the new visual in the appropriate View menu
submenu, allowing you to turn on the new visual immediately. When you begin a new
session or switch views and return to the view, the new visual is no longer listed in View
menu submenu (unless you add the new visual to the view).

Using the Filter Filters that are turned on are displayed in the filter bar. Using the Studio Modeling
Bar Platform, you can use the filter bar to:
• Change the types that are listed in the filter query.
• Change the direction of filters that apply to relationships.
These changes are for the current browser and other browsers that are spawned from it.
They do not affect the saved definition of the filter, nor browsers that are already open.

In the Web version of Matrix Navigator the filter bar is only available from an indented
(Navigator) browser, and is used only to show the definition. Ad-hoc changes to a filter
cannot be made in the Web version.

To make ad-hoc changes to a filter from the filter bar

1. Be sure the filter bar is displayed. If it is not, select Filter Bar from the View menu.
As you pass the cursor over the filter bar, a tip appears, indicating the filter and types
it affects. The filter bar looks like:

Chapter 4: Using the Visuals Manager 147

 The Navigator filter bar has either a Relationship or Type field depending on what
the displayed filter applies to. It also adds To and From options when the filter applies
to relationships:

All filters that are turned on are listed in the Filter drop-down list. If the filter bar is
grayed out, there are no filters that are currently turned on. The type or relationship
field shows the types or relationships that are listed in the selected filter’s query. For
example, the filter named “mine” applies to all (*) types. You can use the filter
drop-down list to show the types listed in any filter that is turned on.
The To and From check boxes in the Navigator browser filter bar indicate the
selected filter’s use of them. For example, if To and From are grayed out, we know
that the "mine" filter (shown in the first graphic above) does not apply to
relationships. The “Children” filter (shown in the second graphic above) shows From
relationships only.
2. From desktop Navigator only, to apply the selected filter to a different type or
relationship, enter a new name in the Type or Relationship box or click the ellipsis
button to select from the chooser. In Navigator browsers, the To and From check
boxes can also be changed.
3. Press Enter to update the display to filter on the type or relationship, and/or direction
changes. These changes are not applied to the saved filter definition.

You can hide the entire filter bar so it does not show on your browser by unchecking the
Filter Bar in the View menu. However, it is not a good idea to hide the filter bar while it is
being used, since turned on filters limit the objects in the browser and you may not realize
that you are seeing a filtered list.

Optimizing When many objects are loaded and/or when many visuals are applied (including, perhaps,
Performance a table with many columns), there may be a noticeable performance delay when a visual is
turned on or off. The following techniques can be used to minimize the impact of applying
visuals:
• Do your setup using the Visuals Manager when you begin a work session in Matrix
Navigator, or when ‘changing gears’ while you’re in Matrix Navigator. Close down
as many browsers as practical, and switch to Icon mode to defer unnecessary table
loading.
• Think about what you’re going to do, and only activate the visuals that you expect to
want turned on in ALL the browsers, then adjust as-you-go by toggling the visuals
using the View menu on an as-needed basis.
• Having set things up in the Visuals Manager according to the task-at-hand, you can
proceed and make subsequent adjustments using the submenus in the View menu,
thereby making those adjustments “locally”—that is, affecting only the single
browser in which you make the change.

148 Matrix Navigator Guide

 • When activating more than one visual, use the View menu and cancel the loading of
objects after activating each visual, if necessary. Then, apply subsequent visuals,
cancelling the load phase each time, and when all are set, allow the loading to
complete. With faster computers and/or fewer objects, you may not even see the load
meter, and therefore will not need to cancel loading.
If it takes more than a few seconds to load a browser, a “Load meter” displays, which
gives the status and allows you to abort the loading of the browser. If you are changing the
settings of multiple visuals in a heavily populated browser, you may want to abort the
table loading of all but the last visual change. This does no harm—the loading invoked by
the last visual change updates the browser to account for all the other changes as well.

Viewing Tip The ability to view tips instead of object titles is available in the Web version of Matrix
Content Instead of Navigator only.
Object Titles
When viewing objects in any Matrix Navigator browser, you can display the content of
tips instead of the standard object title by selecting View > Tip. Navigator replaces the
standard title—which includes the object type, name, and revision—with the content of
any tip that is currently turned on from the View > Tip submenu. To return to the display
that shows the standard title, select View > Title.

Standard title with type, Tip instead of title with

name, and revision two tips active: one for
name and one for owner.

Chapter 4: Using the Visuals Manager 149

 Role-Based Visuals

Visuals (filters, tips, cues, toolsets, tables) and views are generally defined by users for
their own personal use. They let users set up their workspace in a way that is comfortable
and convenient. Visuals can be used for many purposes, including organizing, prioritizing
tasks, providing reminders, or streamlining access to information. Each user can define
visuals in a way that is most helpful to that person.
Visuals can also be defined and shared among users who are assigned to a role. For
example, every person belonging to the role Accountant can have access to the same
visuals. This not only makes the work environment easier for a person just joining the
department, but also facilitates communication among persons within a group.
For example, suppose there is a role called Manager. At a weekly manager’s phone
conference, each person sitting in front of a computer can, with the click of a mouse,
switch visuals so the whole group is looking at the same thing. One could then suggest a
filter to view a particular subset of objects, or look at a table, or refer to “all objects
highlighted in red...”.
The person setting up visuals to be shared must have Business Administrator privileges
and access to MQL. Refer to the MQL Guide for more information.

Accessing the The Studio Modeling Platform browser and the Navigator browser display a role bar,
Role Bar which contains a drop-down list. If you are using the desktop version of Matrix Navigator,
you can toggle the display of the role bar by choosing View>Role Bar. If you are using the
Web version, the role bar is always displayed in the browsers and you can also access the
list of roles from the Role submenu in the View menu.
The role bar shows all roles to which you are assigned. If you aren’t assigned to any roles,
the role bar isn’t displayed. When the role bar is set to Personal, you have access to the
visuals that you created. When set to a role, you have access to all the visuals and views
for that role.
If you select a role from the role bar, the browser from which the role was selected is
affected and any browsers spawned from it. Any browsers that are already open are not
affected.

If you have a visual turned on from Personal and switch to a role that does not have that
visual, it is turned off while set to that role.

To access role-based visuals

1. Click on the arrow at the right side of the role bar. A list of roles for which you are
defined is displayed.

150 Matrix Navigator Guide

 The list of roles available includes those roles that are part of any combined group-role
assignments.

2. Select the role that contains the visuals you want to access. For example, in the screen
shown above, you can access visuals belonging to either Analyst, Employee, or
Management.

If you do not see the role you want, contact your Business Administrator. Roles and their
definitions, including the specific individuals assigned to the role, are defined in the
Business Modeler application.

The visuals and views for the role are now available from the View menu.

Chapter 4: Using the Visuals Manager 151

 Deleting a Visual

You can delete an existing visual from the Visuals Manager.

To delete a visual
1. From the Visuals Manager, select the appropriate tab for the visual you want to
delete.
2. Select the visual you want to delete.
3. Select Delete from the View menu.
The Delete-visual message appears, where visual is the name of the visual you are
deleting. In this case, the Delete - Cue Assigned Deliverable message displays:

4. Click Delete to delete the visual.

152 Matrix Navigator Guide

 5
Working with Sets

Working With Sets

A set is a user- defined collection of objects in Matrix Navigator database. An Matrix

Navigator user can define any number of sets and can decide what business objects will
belong to each set. You will commonly open a set when you first open Matrix Navigator,
and then find other objects to add to it. Your sets are not available to other users.
For example, you might have different sets for different projects with each set containing
all the objects related to that project. You create these sets in Matrix Navigator by first
finding all the existing objects related to a project (with a query). Then, you might create
additional objects for the project and add them to the set. Finally, you save the collection
of objects as a named set that you can easily open later to work on that project.
As you work with sets, keep in mind that sets are a static collection of objects. For
example, if you create a set called Projects that includes all objects with the type Project,
any new Project objects that are added to Matrix Navigator are not automatically added to
your saved set. However, changes to the objects within the set are updated. So if you
create a set of objects where the current state is Past Due, and then subsequently re-open
this set, some objects within the set may no longer have a current state of Past Due.
When you open a set, all objects within that set display in the current browser. If you add
other objects to the browser, by creating or finding them, they do not automatically
become part of the set.

153
 Defining a New Set

When you choose to define a new set, you start with an empty Matrix Navigator browser.
Then you place objects in the browser. If the objects to be included in the set are already in
the work area, choose Save As from the Set menu as described in Saving a Set. Otherwise,
use the following procedure.

To define a new set

1. Select New from the Set menu.(This option is available only for the desktop version.
Use New Window if you have the Web version of Matrix Navigator.)
The current Matrix Navigator browser clears. If you performed actions with the
current Matrix Navigator set and did not save your changes, you are prompted to do
so before the set is closed. Click Save to save the current set before defining a new
one.
Or
If you prefer to keep the work displayed in the original browser or are using the Web
version, select New Window from the Set menu. This leaves your existing browser
open and opens a new empty browser in which to define your new set.
2. Define a new set by finding and/or creating objects. Objects can also be dragged from
other open browsers, or cut and pasted to the browser.

154 Matrix Navigator Guide

 Saving a Set

You can save the currently displayed set of objects with a specific name using the Save As
command. If the set is new, only the Save As command is available. If you added to or
removed objects from a displayed set, both the Save and Save As commands are
available. The Save option lets you save the new set using an existing name.

The Save option is available only in the desktop version of Matrix Navigator.

To save a set
1. In the browser that contains the objects you want to save, select Save or Save As from
the Set menu.
A Save Set As window opens:

2. Select a set (to overwrite) from those displayed.

Or
Type a name for the set in the Name text field. It is helpful to assign meaningful
names to sets so that you can remember the purpose of the grouping. Set names
cannot include asterisks or commas.
3. Click OK.

Chapter 5: Working with Sets 155

 Opening an Existing Set

When you open an existing set, all objects within that set are placed in the current
browser, overwriting any objects that may already be in that browser.
If you add other objects to the window, by creating or finding them, they do not
automatically become part of the set; you must save the set if you want the additional
objects to become part of the set.

To open an existing set

1. Click or select Open… from the Set menu.

The Open Set window opens, showing previously saved sets for the current user:

2. Select a set from those displayed.

3. Click OK.

156 Matrix Navigator Guide

 Loading Objects From a Set

Loading sets is available for the desktop version of Matrix Navigator only.

You can load objects from one saved set to another set. When you load objects, you can
either add to the objects in the current browser (append), or replace everything in the
current browser with the new set being loaded. When loading sets with append, the last
loaded set name is put in the title bar, and a save of the set would use this name.

To load objects from a set

1. Select Load from the Set menu.
The Load Objects from Set window appears.

2. Select a set from those displayed.

3. Click the Replace Objects option button to replace currently loaded objects with
those from the selected set.
Or
Click the Append Objects option button to append the objects.
4. Click Load.

Chapter 5: Working with Sets 157

 Removing Objects From a Set

You can remove objects from a displayed set using the Edit>Cut command. Removing
objects from a set does not remove the objects from the database. When you use the
Edit>Cut command on an object within a set, the object is removed from the browser, but
not permanently removed from the set until you save the set.

To remove objects from a set

1. Click or choose Open from the Set menu, and open an existing set (see Opening
an Existing Set).
The objects contained in the set are displayed in the browser.
2. Select one or more objects that you want to remove from the set.
You can select more than one object by pressing and holding the Shift key while
selecting each object. Or, you can select all objects by choosing Select All from the
Edit menu.
3. Choose Cut from the Edit menu.
The Cut option removes the selected objects from the current browser and places
them on the Matrix Navigator clipboard. It does NOT cut them from the database.
4. Choose Save or Save As from the Set menu. (Web users must use Save As.)
You must save the set in order for changes to be recorded. If you do not save the set,
the cut objects will reappear the next time you open the set.
For additional information on cutting, copying, and pasting objects, see Editing the Work
Area in Chapter 2.

158 Matrix Navigator Guide

 Deleting a Saved Set

You can delete a saved set. When you delete the set, you are not deleting all the objects in
the set—just the container (set) in which the objects were temporarily held.

To delete a saved set

1. Select Delete from the Set menu.
The Delete Set window opens:

2. Choose the set you want to delete.

3. Click OK. The named set you just deleted will no longer appear in the set window,
but the objects contained in that set still exist in the database.

Chapter 5: Working with Sets 159

160 Matrix Navigator Guide
 6
Using View Manager

Using View Manager to Create Personalized

Views

Personalized views offer a flexible and convenient way to package frequently-used sets of
visuals. You probably have certain combinations of visuals that you use often. It may be
tedious to set up for a work session using the Visuals Manager, then adjust your views
as-you-go using the View submenus. Many users find themselves wanting to
simultaneously view different data in the database using different combinations of visuals.
Using views has the following advantages:
• You can turn on and off all of the visuals included in the view at once (and
simultaneously make all visuals not included in the view unavailable).
• Views are local, affecting only the browser in which you turn on the view and those
spawned from it.
• You can make visuals in a view definition deactive. This means they are turned off
when you activate the view, but they are available to you to turn on if you choose to.
• Activating a view shortens the View submenus, restricting them to show only the
visuals in the view definition.
• Views are inherited—if you open a new browser from a browser with a view turned
on, the new browser has the same view turned on.

161
 • Whether you have toggled several visuals using the View submenus or not, you can
switch immediately to a completely different set of visuals using View>Views>New
Named View.
• Similarly, if you have turned on a view, then toggled various visuals on and off, you
can reset the browser by reselecting View>Views>Same Named View.
When we look at some objects, we always need to know certain information and prefer
that we see it in a similar format. For example, for each new revision of a product
component, we might want to:
• Identify the latest change made with a red arrow cue
• List who performs work on it and who owns it with an object tip
• Filter out all the old revisions
• Always use the BOM Details table in the Details browser mode
• Run a program to create a new revision on command (with a tool button)
You can use View Manager to make your selections only once, name the view, and save it.
The next time you need to create a new product revision, you select the named view and
do your work.

162 Matrix Navigator Guide

 Using View Manager

This section describes how to create, edit, and delete views. You cannot create a view until
you have created visuals to add to the view.

Creating a New You can create a new view that includes selected filters, cues, object tips, toolsets, and
View tables. These saved and named views save steps when performing repeated tasks where
you need information presented in a consistent view.

To create a new view

1. Select View from the View menu.
The View Manager is displayed:

2. Click or select New from the View menu.

The New View window opens.

3. Enter a name for the new view in the Name text box. View names cannot include
asterisks.

Chapter 6: Using View Manager 163

 4. Click each tab to view the available visuals that can be included in this view. Select
the visual on each tab and click Add to move it to the content frame.
In the example below, we added the BOM as Manufactured filter, two tips,
three tables, one toolset, and four cues. Each time, we selected one item on the right,
then clicked Add to move it to the left content frame.

Notice that as each visual (except for tables) is added to the new view, it is also
checked. A checked visual means the visual will automatically be turned on when the
view is turned on. You can turn off a checked visual at any time using the submenus
in the View menu. See Turning Visuals On and Off in Chapter 4.
Since only one table can be active at a time, tables use small circle buttons that do not
toggle like the check boxes. When you add a table to a view, the circle is blank. The
selected table is used as the default when Details mode is selected and when the view
is turned on. You can turn on other tables at any time using the Table submenu in the
View menu.
5. If you want a visual (except for tables) to be available but not automatically turned on
when the view is turned on, uncheck the visual.
If you want a table to be used when Details mode is selected, click the circle next to
the table so it is filled in.
6. When all your view selections are complete, click Create. The View Manager
appears and lists the new view.

164 Matrix Navigator Guide

 Last view created.
Views are listed
alphabetically by
name.

Viewing the You can see which visuals are added to a view.
Content of a View To view the content of a view
1. Select the view in the View Manager.

2. Click or select View from the View menu in the View Manager.
3. After viewing the view, click Close.

Editing a View You can add or remove visuals from a view or change which visuals are automatically
turned on or off when the view is turned on.

To edit a view
1. From the View Manager, select the view you want to edit.

2. Click or select Edit from the View menu in the View Manager.
3. Make the following changes as needed:
–To add a visual to the view, choose it from the tabs on the right and click Add.
–To remove a visual from the view, choose it from the list on the left and click
Remove.
–To have a visual (except tables) automatically turn on when the view is turned on,
check it.
–To have a visual (except tables) automatically turn off when the view is turned on,
uncheck it.
–To make a table the default table for Details mode, click the circle to the left of the
table so it is filled in.
4. In the Edit - View window, click Edit.
5. In the View Manager, click Close.
If the view is turned on, all browsers refresh to reflect your changes. If the view is not
turned on, your changes appear the next time you turn on the view.

Chapter 6: Using View Manager 165

 For the desktop version of Matrix Navigator, views are updated as soon as you click the
Edit button in the Edit - View window.

Cloning a View You can create a clone of a view, then edit it to create another view. This saves time when
creating similar views to be used for slightly different purposes.

To clone a view
1. Select the view from the View Manager that you want to clone to create a new view.
2. Select Clone from the View menu in the View Manager.
The Clone-View window opens.

3. Enter a name for the new view in the Name text field and click Create.
4. Edit the cloned view to differentiate it from the original view.

Deleting a View You can delete an existing view from the View Manager. Use this procedure to delete it.

To delete a view
1. Select the view to delete from the View Manager.
2. Select Delete from the View menu.
The Delete-View message appears:

3. Click Delete.

166 Matrix Navigator Guide

 Turning Views On and Off

After creating a view, you can turn it on or off from any browser. Only one view can be
turned on at a time.

The view with the circle is the

currently-selected view.
To turn off all views and have
access to all visuals you have
created, choose All.

To turn on a view
• From the View>View submenu, select the view you want to turn on.
In the current browser, only the visuals added to the view are listed in the View menu
submenus. All visuals that are checked in the View Manager are turned on.
If the view was already turned on, then the visuals are turned on or off according to
their states (checked or unchecked) in the View Manager.

To turn off all views

• From the View>View submenu, select All.
In the current browser, all visuals that you have created are listed in the View menu
submenus.

Chapter 6: Using View Manager 167

 Practical Example Using Views

Scenario I’m an engineering manager. I have many jobs that include:

• Tracking the work of the engineers in my group. For this job, I review their work both
technically and with respect to project schedules. To do so, I look at Assembly,
Component, and Specification objects, connected by Assemble and Specify
relationships. To coordinate with our technical writing staff, I sometimes have to look
at assorted Manuals connected by the Documents relationship.
• I am a project manager. I define and monitor those parts of project schedules for
which my group is responsible. For this I look at Project, Function, and Task objects
connected by Requires and Depends relationships. Sometimes I have to dig deeper
and navigate from a Function or Task to the Assemblies through a Satisfies
relationship.
• I have to manage the processing of ECO’s (Engineering Change Orders) which are
connected to Products by a Request relationship and to Assemblies or Components by
a Depends relationship.
• I also deal with purchase requisitions, equipment inventory and personnel
management, etc...

Visuals Used I have a bunch of visuals to help me navigate through the database:

Filters
Assembly Objects: Assembly, Component; Relationships: Assemble
Assy-Doc Objects: Specifications, Manual; Relationships: Specify,
Documents
Project Objects: Project, Function, Task; Relationships: Requires,
Depends
Proj-Assy Objects: Assemblies, Components; Relationship: Satisfies.
ECO Objects: Product, ECO, Assembly, Component;
Relationship: Request, Depends.

Tips
Owner Owner of any object
ECO-Desc a synopsis of the description of the change required

168 Matrix Navigator Guide

 Cues
Specified if an Assembly or Component has a connected Spec
Soon if the scheduled date for any object’s next state is within the
next few weeks
Late if the scheduled date for any object’s next state has passed
Depends if an Assembly, Component, Function, or Task depends on
an object not owned by my group
OpenECO if an Assembly or Component has a connected ECO which is
in the Open state

Tables:
AssyFunc shows attributes of Assemblies/Components relating to their
functional Specifications (e.g. target weight, actual weight)
Analysis shows attributes of Assemblies/Components relating to
analysis data
Schedule shows state and schedule fields
ECO shows description, owner, state, priority of ECO’s
ECO-Assy shows data from Assemblies/Components connected to an
ECO.

Chapter 6: Using View Manager 169

Views Used I organize these visuals into the following views:

View Filters Tips Cues Tables

Assembly Assembly Owner Specified AssyFunc
Assy-Doc Soon Analysis
Late Schedule

Project Project ECO-Desc Depends Schedule

Proj-Assy Owner ECO-Open ECO
ECO Soon ECO-Assy
Late

ECO ECO ECO-Desc ECO-Open ECO-Assy

Proj-Assy Owner Soon ECO
Late Schedule

Note in particular how the filters that I have chosen to group together into views are
related to each other:
• When I’m technically reviewing an assembly, or working on my own assignment, I
use the Assembly view, with the Assembly filter. I might expand through a few levels
of an assembly, and at any point, I can see the Specs and Manuals attached to a certain
object by toggling the Assy-Doc filter on.
• When I’m reviewing the state of a project, I can easily go from Functions/Tasks to
related Assemblies and/or ECO’s by turning the Proj-Assy or ECO filter on.
• Conversely, when reviewing ECO’s, I can peek at the Assemblies by turning the
Proj-Assy filter on. Note that the ECO view does not include the Assembly filter that
lets me navigate through the entire Assembly structure. However, if I need to examine
an assembly in full detail, I can find my way to any member of the assembly in
question, then switch my active view to the Assembly view.

170 Matrix Navigator Guide

 7
Working with
Connections

Overview

Objects in Matrix Navigator can be connected via a relationship. When a relationship is

established between two objects, we refer to it as a connection. Connections in Matrix
Navigator are themselves objects and can have a description, an icon and attributes
associated with them. History is also logged on connections.
Your Business Administrator defines the kinds of relationship types that are available for
use by Matrix Navigator users. When Business Administrators define a relationship, they
identify the types of objects eligible to be used by the relationship, the to/from direction of
the relation and the rules governing the creation and modification of the connections. As
you would with a business object type, you may need to consult your Business
Administrator to understand the rules governing the relationships you use in your Matrix
Navigator installation.
Connections between objects can be made in three ways:
• Manually—You can create a relationship between a selected object and any number
of other objects. Conversely, you can disconnect relationships. This is described in
Connecting Objects. Conversely, you can delete connections, as described in
Disconnecting Objects.

171
 • Drop Connect—You can create a connection between objects by dragging them
from any kind of browser (Studio Modeling Platform browser, IconMail, etc.) and
dropping them onto any object in a Navigator browser (Star, Indented, or Details
mode). You can also replace objects in a structure. This is described in Drop Connect.
• Automatically—A relationship may be defined automatically if you annotate an
object with mark-up information (such as a drawing mark-up) or attach information to
an object (such as an audio comment, note, photograph, or video). These functions are
available in the desktop version of Matrix Navigator only.
Note that a relationship may also be defined automatically when creating revisions if
the Float or Replicate option is specified by the Business Administrator. In addition,
event triggers may exist that create relationships between objects based on the
occurrence of a specified database transaction. Wizards and programs may also make
connections automatically.

172 Matrix Navigator Guide

 Connecting Objects

The Connect option creates a relationship between selected objects. The basic procedure
involves three steps:
• Selecting the objects to be connected.
• Specifying the relationship and making the connection.
• Assigning values to the attributes of the connection, if any.
These steps are detailed in the following sections.

Relationship In most cases, only one direction is allowed for a particular relationship connecting two
Direction objects. The Connect window automatically connects items in the proper way in this case.
In cases where two objects are allowed to be connected in either direction, Matrix
Navigator connects from the target to the candidate. An example of this is two assembly
objects connected to form a product structure.
When you connect objects, the policy must allow you the privileges to do so. To establish
a connection, you must have toconnect privileges on the to object, as well as
fromconnect access on the from object. In addition, if the relationship has a rule, create
access on the relationship is also required. Policies and rules are created by Business
Administrators.

To create a relationship
1. Select the object to be connected to other objects.
This is the from or target object.

2. Click or select Connect from the Relationships menu.

The Connect window is displayed.

Chapter 7: Working with Connections 173

 Target
Object

Candidate
Objects

Valid
Relationships

In addition to the menus and tools at the top of the window, the Connect window
consists of three areas: the target object is displayed under the toolbar, the
relationships that are valid for the selected object are listed in the left scrollable area,
and candidate objects with which to connect are listed in the right scrollable area.
A candidate object is any object that was in the browser before the Connect option
was selected and can be connected to the selected object type (based on the defined
relationships).
3. Select candidate object(s) with which the target object will connect.
4. Select a relationship type to use to create the connection.
The message bar provides status information on the selected items. For example, if
the relationship is not valid between the target and candidate objects, the message will
say “Not a possible connection.” When the connection is valid, the meaning defined
in the relationship definition is displayed.
5. Click Connect to connect the objects and close the window.
Or
Click Apply to connect the objects and leave the window open so that you can
connect the target object to other candidate objects using a different relationship.
6. If the chosen relationship has attributes, the Attributes window opens upon
connection, allowing you to enter the values for this particular instance. This
procedure is identical to defining attributes of an object, as described in Defining
Object Attributes in Chapter 2, or modifying attribute values as described in
Displaying and Modifying Attributes, below.

174 Matrix Navigator Guide

Selecting Multiple If you initiate the connect function by selecting more than one object, separate Connect
Objects to windows are displayed for each target object. You would repeat the above procedure for
Connect additional objects.
You can connect a single target object to more than one object in a single procedure.

A Note about All Matrix Navigator relationships are defined by the Business Administrator with
Cardinality cardinality rules that define the number of connections of a given type that an object may
have. The cardinality of each end may be one of the following:
• One The end object may only have one connection of this relationship type at any
time.
• Many The connection end may have several relationships of this type
simultaneously.
Cardinality is defined for the business object on each end of a connection so there are
three possible combinations:

ONE-to-ONE One end object can be connected to only another

single object with this relationship. For example, this
type of cardinal relationship might indicate that only
one Change Order may be attached to the Drawing at
any time and only one Drawing object may be
attached to a Change Order. However, the Drawing
may be attached to other objects with a different
relationship type (the component the drawing is of,
for instance.)
ONE-to-MANY One connection end can be attached to many other
Or ends while the other end cannot. For example, a
MANY-to-ONE single Training Course object may have many Course
Evaluation objects attached to it. However, a Course
Evaluation relates to only one Training Course.
MANY-to-MANY Both connection ends can have more than one of this
type of relationship at any time. For example, a
Component object may be simultaneously connected
to many different Assembly objects while an
Assembly object may be simultaneously connected to
many different Component objects.

Errors occur if you attempt to connect more than one object with the same relationship
type when the cardinality is one.

Chapter 7: Working with Connections 175

 Drop Connect

Drop Connect is a quick and easy way to create connections between objects using the
Studio Modeling Platform and Navigator browsers instead of the Connect window. An
object can be dragged from most browsers to a Navigator browser and dropped onto
another object to create a relationship from the target object.
For example, you may have a business object called Piano. You would want to create
relationships between Piano and all components of Piano, including Keyboard, Sound
Board, Pedals, etc. Each component business object could be dragged to the business
object Piano, creating relationships where the components are related to the Piano.
With Drop Connect, you can also replace objects within a relationship by dragging the
new object to the relationship arrow of the object being replaced.
Of course, when you connect or disconnect objects, the policy that currently governs the
objects must allow you the privileges to do so (as with using the Connect dialog). To
establish a connection, you must have toconnect privileges on the to object, as well as
fromconnect access on the from object. In addition, if there is an the access rule
governing the relationship, it must allow you the create privilege. See the Business
Modeler Guide for more information on policies and access rules.

Connecting A connection can be created by clicking and dragging one object on top of another object.
Objects Using To create a relationship using Drop Connect
Drop Connect
1. Open two browsers.
The first browser, from which you will select and drag an object, can be virtually any
browser (for example: Studio Modeling Platformbrowser, Navigator browser,
IconMail, Revisions, etc.).

The Detailed mode of the Matrix Navigator browser and the Format browsers do not
currently support Drop Connect.

The second is any Navigator browser that graphically shows the relationships
between objects (that is, the Navigator browser in Star, Indented, or Detail mode).
2. In the second browser, click on the arrow on the right side of the connect bar.

176 Matrix Navigator Guide

 All active relationship filters are applied to the drop-down list. From the list, select
the relationship type that you want to use to make the connection. If you type the first
few letters of the relationship type in the connect bar entry area, and then click the
arrow, the first relationship that begins with those letters is displayed in the scrollable
list.

If you want to have the connect bar displayed by default each time you open a Navigator
browser, check Connect Bar on the Toolbars tab of the Session Preferences dialog. You
can also indicate the default drop relationship type to use on the General tab of Session
Preferences. Refer to Setting Preferences in Chapter 1 for more information.

3. Select an object in the first browser and drag it on top of the object in Navigator
browser to which you want to connect it. The target object can be a parent object or a
child object. The relationship created will be from the object in the second browser
(the target object).
For example, in the following, you click and drag ECR 1998-1 0 from the Matrix
Navigator browser to the Navigator browser in Indented mode. In the Navigator
browser, as you drag the cursor over the object you want to connect, the status line
describes what the connection will be, in this case “Connect ECR, fromVehicle
U40001 A to ECR 1998-1 0”:

Chapter 7: Working with Connections 177

 When you release the mouse button, the objects are connected. If the relationship has
attributes, a window pops up so you can supply the necessary information.

Note that the status line contains from and to information, explicitly defining the
connection that will be made.

For performance reasons, the relationship validity check is not made until after you
release the mouse button. All drop connect relationships are assumed from the target
object. Any error messages are displayed after the mouse button is released.

The Navigator browser shows the new connection:

178 Matrix Navigator Guide

Replacing Objects When replacing an object using Drop Connect, if you drop onto a child object to replace it,
Using Drop Matrix Navigator keeps the same relationship that was already there rather than using the
Connect relationship shown in the connect bar. You are actually modifying one end of the
connection, not deleting the relationship and creating a new one. This means that connect/
disconnect access is checked only the end of the connection that is changing. Create and
delete access are checked if the relationship has any rules applied. If the existing
relationship is not valid, or if the user is not allowed to make connections of that type, the
connection attempt will fail.

To replace an object in a relationship using Drop Connect

1. Open two Matrix Navigator browsers, as described in step 1 above.
2. Drag an object from the first browser to the relationship arrow of the object you want
to replace in the Navigator browser.
For example, in the following, you click and drag ECR 1998-1 0 from the Matrix
Navigator browser to the relationship arrow of ECR 4000 0 in the Star mode of the
Navigator browser. As you drag the cursor over the relationship arrow of the object you
want to replace, the Navigator status line describes the action that will happen when you
release the mouse button, in this case “Replace ECR, ECR 4000 0 with ECR 1998-1 0?”

Chapter 7: Working with Connections 179

 When you release the mouse button, the object is replaced. If the relationship has
attributes, a window pops up so you can supply the necessary information.

Notice that when replacing objects, the relationship type of the original connection is
used, not the relationship displayed in the relationship bar.

For performance reasons, the relationship validity check is not made until after you
release the mouse button. Any error messages are displayed after the mouse button is
released.

The following shows the Navigator browser, where the original ECR has been replaced
with the new ECR:

180 Matrix Navigator Guide

Chapter 7: Working with Connections 181
 Using the Navigator Browser

While using Matrix Navigator and working with objects, you may need to navigate an
object’s relationships to review connected objects’ attributes and other characteristics.
You can do this with the Navigator browser, which supports several modes that provide
different views of the same structure:
• Star—When you set the Navigator browser to Star mode, objects connected to the
selected object are displayed in a circular pattern around the object.
• Indented—When using the Indented mode, the objects connected to the selected
object are displayed below it. These objects may be expanded to show their
connections as well, with each level indented from its “parent”.
• Details—When the Navigator browser is in details mode, an indented table is
displayed. The indented format is shown side-by-side with the details of your current
active table.
When an expanded object structure is very large, performance degradation may occur,
especially when using details mode and connecting via the internet. This is due to the fact
that large amounts of the structure are returned at one time. But in many cases, much of
the returned data is of no interest to the user. To allow more efficient browsing of tables, a
fourth mode of the Navigator browser is available the Web version of Matrix Navigator:
• Paginated—When using Paginated mode you can request just the portion of the
connected structure that you are interested in viewing. You can then request
subsequent “pages” of the structure, as needed. Paginated mode is similar to details
mode, but differs in the following ways:
There is no automatic expansion of the root object. This allows you to change the
selected table and apply views, filters and other visuals before expanding so that
Matrix Navigator will retrieve and display only the data you require.
A paginate bar lets you define a range of values for any column in the table. Only
those connected objects that fall between the range specified will be displayed.
Only one level of the structure may be presented. However, you can switch between
modes, or open a new navigator on a connected object, just as in any other mode of
the Navigator browser.

Paginated mode is available only when using the Web version of Matrix Navigator—it is
not available in the desktop version.

The default Navigator mode is set in session preferences.

To set preferences
1. Select Preferences from the Session menu.
The Session Preference window appears, showing the View tab.
2. To use the Paginated mode by default, choose Paginated for your Navigate by
preference.

Paginated mode is available only when using the Web version of Matrix Navigator—it is
not available in the desktop version.

3. When you have set your preferences, click OK.

182 Matrix Navigator Guide

 To activate the Navigator browser
1. Select the object you want to explore.

2. Click or select Navigator from the Relationships menu. Or, use the pop-up
menu by right clicking on the object and selecting Relationships > Navigator.
The mode set in your Session preferences is displayed by default, unless you have no
tables defined, and the preference is Details or Paginated. In this case, Indented mode
is the default.
3. To change the browser mode, select Star, Indented, Details, or Paginated from the
View menu.
Or

Use the star , indented , details (indented table), or paginated buttons

from the toolbar of the Navigator browser.

Using the Star Navigator’s star browser mode shows related objects clustered around the selected object.
Browser Mode

Once the star is displayed, you can navigate through database relationships in two ways:
• By activating a separate Navigator browser of a connected object, as outlined above
in Using the Navigator Browser.

Chapter 7: Working with Connections 183

 • By using the There and Back tools, as described in There and Back.
When There or Back tools are used, the current window is re-used for the newly selected
object; therefore the browser mode stays the same.

There and Back When you display related objects, sometimes you want to explore further by looking at the
connections of an object connected to the object you expanded. The Star and Indented
Navigator modes provide There and Back tools for this purpose. You can jump to a
Navigator display of a new object without creating a new Navigator browser. Then you
can jump back to the previous display. This is different than displaying additional
Navigator browsers because you will only have one browser to close when using There
and Back.

Navigating with There and Back

1. Select an object from the Navigator browser.

2. Select the tool.

Or
Select There from the Relationships menu. In either case, the Navigator browser
display changes from the current object to the newly selected object.

3. To return to the original display, select the tool.

Or
Select Back from the Relationships menu.
All jumps are remembered and you can continue to go back through history with this
tool.

There and Back functions are also available from the pop-up menu by right-clicking on
the object.

Using the Indented The Indented browser mode of the Navigator browser shows related objects on indented
Browser Mode lines beneath the selected object.

184 Matrix Navigator Guide

 Parent Object

Once the browser is displayed, you can navigate through database relationships in three
ways:
• By activating a separate Navigator browser of a connected object, as outlined in To
activate the Navigator browser.
• By using the There and Back tools, as described in Navigating with There and Back.
• By expanding a connected object, as described in the section that follows.

Expanding the Indented structure

When you first activate the Navigator browser in Indented mode, one level below the
selected object is displayed. These are the same objects which would be displayed
surrounding the object in Navigator’s Star mode. The Expand button (+) to the left of the
displayed objects enables you to expand the hierarchical display one level.
For example, if you click the Expand button (+) to the left of Assembly 010AN90002 A,
another level of detail is provided.

Chapter 7: Working with Connections 185

 You can click other Expand buttons to display additional levels of detail.
When you click the Expand button, the symbol changes to (-) (the Collapse button).
Click the Collapse button to collapse or remove a level of the display and change the
button back to Expand (+).

Expanding an Entire Tree

You may be able to quickly display the entire tree by holding down the Shift key when
you click the Expand button. However, because indented structures can be very large if no
filtering is being performed, Shift+click expansions by default generate an error:
Can’t expand recursively in both to and from directions
You will need to have a filter set up that only allows the Shift+click to expand in one
direction. You could, for example, have predefined filters called “children” and “parents,”
which filter the direction “from” and “to.”
If you want to allow all expansions, even if a filter is not used, you can set the
MX_RESTRICT_EXPAND variable to False in the enovia.ini file (desktop version only).
(The enovia.ini file for the Live Collaboration Server has a similar setting called
MX_BOS_EXPAND_LIMIT.)

186 Matrix Navigator Guide

Adding Details The third mode of the Navigator browser is arguably the most useful. It is the details
mode, which shows an indented structure with a table attached to its side.

You must have a table selected before selecting the Details mode. If you do not have a
table defined, only the object column is displayed. Refer to Creating a Table in Chapter 4
or talk to your Business Administrator for assistance in setting up tables.

Each connected object is displayed in a row with columns of information (the table) about
it or its connection to the originally expanded object. The indented and table sections are
synchronized. When you scroll the indented section vertically the table section scrolls
also. When you expand or collapse an object in the indented section, the table is updated
to add or remove rows to match.
You can sort the objects in each column of a table by clicking on the column heading. The
first sort will be in ascending order; another click reverses the sort order to descending
order.
When a user switches to details mode, a progress window may appear when a large
amount of data needs to be retrieved, for example when loading cells and visuals after a
user expands an object in an indented table to reveal a large number of objects. This
Progress dialog shows the number of objects being loaded, and contains a Cancel button,
that allows you to interrupt the operation at any point. When interrupted, the data already
retrieved is displayed. In the Web version this means that some table cells may remain
empty. Also, objects in these empty rows will not have tips or cues applied.

Chapter 7: Working with Connections 187

 In the Web Navigator, in a navigator window only, (currently not enabled in a flat table or
in the desktop version), you can use the Refresh option to retrieve missing data.

To retrieve missing data in an indented table

• Select any number of unfilled object rows and choose View > Refresh to retrieve data
for those objects only.
Or
• Use the pop up menu (right click on a selected object(s)) and choose Refresh.
Or
• Without making any selection, choose View > Refresh to retrieve all missing data.
The table cells are filled in, and any tips and cues are applied.

Using Paginated When you first display a Navigator browser in paginated mode, only the object to be
Mode expanded is displayed—its connections are not yet shown:
The typical navigator menus and tools, as well as the paginate bar are available. The
paginate bar’s drop-down list shows all the columns the active table contains. At this
point, you can:
• Select another table from the View/Table menu, if required, and the paginate bar will
be updated to reflect the columns of the new table.
• Select any of the columns making up the active table from the drop-down list in the
paginate bar, and enter a minimum (From) and/or maximum (To) value, to be used as
criteria to determine what objects to present.
• Change the active view and/or filters, to further limit the number of connections
displayed.
• Change other visuals, like cues and tips.
When you are satisfied with the information, press Apply on the paginate bar to expand
the object based on the combination of active filters and the specified criteria. All the other
features of details mode, including sorting, cancel and refresh, and there and back, are
available from paginated mode, except that you cannot expand a child object.

Expanding the parent object by clicking the (+), is treated as Apply.

Paginate Bar
The paginate bar’s drop-down list presents all the column headings from the active table.
You can then select a column and specify a range of values for that column using the From
and To fields in order to minimize the size of the table to be presented.

You should use the From and To fields to reduce the number of unneeded table rows as
much as possible. Because of the additional overhead of applying the search criteria, if
the query result yields all (or most) of the rows, paginated navigator may actually take
longer to load than navigator in details mode.

You can use the paginate bar as follows:

• When you enter both a From and To value, a “between” expression is formulated. To
be more precise, the criteria formulated is:

188 Matrix Navigator Guide

 (COLUMN_EXPRESSION) >= FROM_VALUE &&
(COLUMN_EXPRESSION) <= TO_VALUE
In this case, you can click Previous and Next on the paginate bar to scroll through
“pages” of data. The difference between the From and the To value is used to
determine the next or previous range. Generally, you would provide unique To and
From values when using columns that display integer or real numbers, date/times, or
“well-formed” strings as described in Using Alpha-numeric Ranges and Mapper
Programs.
• When you enter just a From or just a To value, “a greater than or equal” or “less than
or equal” where clause is expressed, and Previous and Next are not available. You
could provide either a To or a From value when using columns that display integer or
real numbers, date/times, or “well-formed” strings, as described in Using
Alpha-numeric Ranges and Mapper Programs.

When using dates in a range, they must follow the format specified in the .ini file.

• If you want to use a string column, such as owner, state, or a Boolean or alphabetic
string attribute as your criteria, enter the same value in both the To and From fields;
that is a user name, state name, or attribute value, such as False or Blue. Note that
since the equal operator will be used, the criteria is case sensitive. Wildcard
characters are not allowed. All objects meeting the criteria are presented, and
therefore Previous and Next are not available.

While this last use case is possible, the paginated navigator was designed for use with a
sorting attribute. You could create reusable filters to cover this scenario, activating them
before clicking Apply.

Hidden Columns
You may want to use an attribute for paginating that you don’t want displayed in the
resulting table. If this is the case, you can mark a column as Hidden in the table definition.
Such a column will be listed in the paginate drop-down list, but will not be displayed in
the resulting table, whenever the table is used (that is, in either flat table, Navigator with
details, or paginated Navigator mode, in either the desktop or Web version of Matrix
Navigator.)

To create a hidden table column

1. Select Visuals from the View menu.
2. From the Visuals Manager, click the Tables tab.
3. Select the table you want to edit.
4. Click the edit button or select Edit from the View menu. To edit the definition, you
can also double-click the object. The Edit Table dialog is displayed.
5. Double click a column heading to edit the column. The Edit Column window appears.
6. To hide the column when the table is displayed, check Hidden. Hidden columns may
be used to paginate a table when in paginated mode, but are not shown when the table
is displayed.
7. Click OK to edit the column.
8. When you are done modifying the table, click Edit in the Edit Table window.

Chapter 7: Working with Connections 189

 Using Alpha-numeric Ranges and Mapper Programs
In order to scroll through data with Previous and Next in the paginated navigator, and use
it to its full benefit, use a column that contains values that can be ordered in a meaningful
way so that it makes sense to give the start and end values of a range. An integer attribute
works fine since it contains integer values, which have a natural order, based on number
theory. Giving a range from 10 to 120 (sometimes written as [10, 120]) would return all
rows that have a value in the integer column that is greater than or equal to 10, and less
than or equal to 120. Real numbers also have a natural order so real attributes can be used
without any concerns. In addition, alpha-numeric string attributes may be used, but only if
their values are “well-formed.” A well-formed string attribute is one in which the values
have the same number of characters, so that the system can derive sensible numeric
values. For example, ENOVIA Live Collaboration understands that “SR000201” falls
into the range [SR000100, SR000300].
Suppose you want to paginate data based on the reference number of the parts found in an
assembly. This reference number is typically made up of multiple fields that are
meaningful to you and others in your company. One portion of the string may identify the
type of part, while another portion of the string may represent where the part is located in
the assembly. There is no standard that ENOVIA Live Collaboration should understand,
since each company will have its own naming convention. Some companies may even
have several different naming conventions, especially those that have gone through a
number of mergers. If such string values are not “well-formed,” the system must resort to
lexicographical ordering (based on the position of character ASCII values), which is
generally not useful. In this case you may want to use a shadow attribute that will
guarantee that the field contains a well-formed value because of the inclusion of a mapper
trigger program.
A shadow attribute is one that is hidden from the user, but may be associated with a visible
attribute, such that when the visible attribute value changes, the shadow attribute is
automatically updated. This mapping is accomplished using a “modify attribute” trigger
program. The logic in the trigger program is free to do whatever mapping makes sense
when deriving the value of the shadow attribute from the value of the visible attribute. As
a simple example, “S1” might map to “S0000001” and “S25” to “S0000025”. In this case,
two ill-formed strings map to two well-formed strings. The important thing to note is that
some portion of the code in the trigger program defines the mapping logic.
The same mapping logic must also be used in another program that is executed by the
paginated navigator when the following parameter is set in the start Matrix html page:
<param name="PaginateRangeMapper" value="PROGNAME">
The program specified in this parameter is executed whenever the paginate bar is used;
that is when Apply (or the (+) next to the object), Previous, or Next is clicked. When a
shadow attribute is in place, and the visible attribute to which it is associated is selected in
the paginate bar, the user will generally enter To and From values that use the naming
convention of the visible attribute. The paginate range mapper program must map the
ill-formed From and To values using the same logic as in the modify attribute program,
and then use these values along with the shadow attribute to formulate the where clause.
When Previous and Next are used, the range values are also updated in the paginate bar.

When PaginateRangeMapper is set on the HTML page, the specified program is currently
executed every time the paginate bar is used. The mapping program may be designed to
do nothing in some circumstances, but the additional call will have an impact on
performance.

190 Matrix Navigator Guide

Using Other You can select an object in any of the Navigator browser modes and use the menus and
Functions tools displayed on the browser. For example, you can select an object and use the connect
button to establish a relationship for the selected object. You can also view basics, history,
states and other information from the Navigator toolbar. Visuals and views may also be
toggled on and off in the Navigator browser in the same way as from the Matrix Navigator
browser—from the View menu.

Chapter 7: Working with Connections 191

 Reviewing Relationships

Notice that some arrows in the browser point “to” the selected object while others point
“from” the object. The object on the flat side of the arrow is referred to as the “from”
object, while the object near the arrowhead is known as the “to” object.

Most of these
relationships are
defined from the
selected object.

These two
relationships are
defined to the
selected object.

When used in a browser, filters enable you to show only “to” or “from” relationships of
the selected objects, as well as a limited display to connected objects of a specified type or
with a specific relationship. Any of your saved filters may be toggled on or off, as
described in Using Visuals in Matrix Navigator Browsers in Chapter 4.
You may determine the relationship type that connects the objects, as well as other general
information about it by displaying its basics. You may also display the history of a
connection, and the attributes for a relationship.

To display basics of a connection

1. Select the relationship arrow that you want to review.

2. Select the tool.

Or
Select Basics from the Properties menu.
Or

192 Matrix Navigator Guide

 Right-click on the relationship arrow and selecting Properties>Basics.
The Basics window for the selected relationship arrow is displayed.

The Basics window displays the relationship type name in the title bar and lists general
information (other than attributes) about the selected relationship. It shows the
information defined for both ends of the connection: From and To. This information
includes:
• The meaning, which helps you identify the meaning of each end of the connection.
• The type, which defines the types of business objects you can use for each connection
end within the relationship.
• The cardinality, which deals with the number of relationships that a single object can
have, is part of the definition of each end of the relationship.
• Upon Revision and Upon Clone show how the relationships are maintained when one
of the connected objects is revised or cloned. This information is also part of the
relationship definition for each connection end.

To view the history of a relationship

1. From the Navigator browser, select the arrow of the relationship for which you want
to display information.

2. Click or choose History from the Properties menu.

Matrix Navigator displays the history of the relationship as shown below.

Chapter 7: Working with Connections 193

 You can view the attributes of a relationship by double-clicking on the connection itself.

194 Matrix Navigator Guide

 Modifying Connections

When you view related objects in the Star or Indented modes, you begin to realize that the
connections themselves are objects. The arrows may be selected, basic and history
information can be obtained about them, and they can even have attributes.

Displaying and The Attributes window displays the characteristics assigned to the selected relationship.
Modifying This enables you to edit the attribute values if the policy and any attribute rules permit.
Attributes Attributes are dependent upon the definition of the relationship. Your Business
Administrator may specify any number of attributes for a relationship in its definition.

To view relationship attributes

• In the Star browser mode (circular or spiral) or Indented mode, select the arrow of the
relationship for which you want to display attribute information.

Click or select Attributes from the Properties menu. Or, use the pop-up menu by
right-clicking on the relationship arrow and selecting Properties > Attributes.
The Attributes window appears. For example:

If the policy and attribute rules permit, you can edit the attribute values.

Change The ability to change a relationship type is available in the desktop version of Matrix
Relationship Type Navigator only. To change a relationship in the Web version, disconnect and then connect
the objects.

The relationship used to connect two objects can be changed to another valid relationship,
as long as the appropriate access is allowed and the relationship is not frozen.

To change the relationship type

1. Select the relationship arrow that you want to change.
2. Select Change from the Relationships menu.
The Change window opens.

Chapter 7: Working with Connections 195

 3. If you know the exact name of the relationship you want to change to, type in the
name in the Type field.
Or
Click the Type ellipsis button. The Relationship Pattern window appears.

4. Select the relationship and click OK.

The selected relationship appears in the Type field.
5. Click Change.

Freezing Connections may be frozen, or locked, so they cannot be disconnected (unless first
Relationships thawed). Also, attributes of a frozen relationship may not be edited. You must have freeze
access on the objects on both ends of the connection in order to lock a relationship in this
manner. In addition, if the relationship has a rule, you must have freeze access on the
relationship.

To freeze a relationship
1. From the Star or Indented browser modes, select the relationship to be frozen.
2. Select Freeze from the Relationships menu.

196 Matrix Navigator Guide

 The connection is frozen and must be thawed before anyone can modify its attributes
or disconnect it. The frozen/thawed state of the relationships is shown in the Basics
window. If frozen, a padlock icon appears in the Basics window (in some browsers).

Thawing In order to allow modifications or disconnections of a frozen relationship, it must be

Relationships thawed by someone with thaw access on the objects on both ends of the connection. In
addition, if the relationship has a rule, this user must also have thaw access on the
relationship.

To thaw a relationship
1. From the Star or Indented browser modes, select the relationship to be thawed.
2. Select Thaw from the Relationships menu.
The connection is thawed and may now be modified or disconnected.

Chapter 7: Working with Connections 197

 Disconnecting Objects

You can disconnect objects while in the Star or Indented browser mode. When you
disconnect objects, the selected relationship between the objects is removed. In order to
connect or disconnect objects, the policy and relationship rules must allow you the
privileges to do so. To disconnect, you must have todisconnect privileges on the to
object, as well as fromdisconnect access on the from object. In addition, if the
relationship has a rule, delete access on the relationship is also required.

To disconnect objects
1. From the Star or Indented browser mode, select the relationship arrow to be removed.
2. Select Disconnect from the Relationships menu.
The connected object is disconnected and removed from the browser.

198 Matrix Navigator Guide

 8
Checking Files In and Out

Overview

Business objects are designed to store information. Much of that information can be
accessed from within Matrix Navigator browsers and windows. However, you can also
store files from virtually any computer application with a business object.
If you were a purchasing agent, you might store all your vendor information in business
objects that you could view quickly from within Matrix Navigator. Each object might also
include the Microsoft Excel or Lotus 1-2-3 spreadsheets you need to perform cost
analyses or print purchase requisitions.
You include these external files in the business objects using a simple procedure similar to
how you add an attachment to an e-mail message—this is called checking in the file.
When you want to view or edit the file, you can either request that Matrix Navigator
launch the appropriate source application (defined in the file format) or you can check out
the file from Matrix Navigator and work on it directly.
A file format is defined by the policy for that type of business object. The format specifies
how the files will be opened in order to view, edit or print them from within Matrix
Navigator. For example, if a Drawing object has a CAD format, the application for editing
might be mechanical drafting software. The application for viewing might be a viewer
application.
The Formats browser, which looks like the Navigator in Indented mode, gives you an easy
tool to manage the files checked in to an object. Matrix Navigator depends on you to

199
 check in the appropriate files to each object under the correct format for that file (as listed
in the Formats browser). If you do not see a format you need for that object, see your
Business Administrator to add additional formats.
After a file is checked in, Matrix Navigator automatically manages how the file will be
handled as you perform Matrix Navigator commands, such as Open>View, Open>Edit
(desktop version only), Check Out, Lock or Unlock, based on the object’s policy. You can
easily open a file to view or edit by simply double-clicking on it from the Formats
browser.
When you check out a file from Matrix Navigator, it is copied to the destination
workstation, but never removed from Matrix Navigator. A master copy of the file is held
within Matrix Navigator at all times (unless you explicitly delete it).

ENOVIA Live Collaboration can handle the transfer of large files (that is, files larger
than 2 gb) for checkin or checkout. However, the larger a file is, the longer it takes to
check it in.

200 Matrix Navigator Guide

 Should You Open or Check Out a File?

When a file is checked in to an object, you can open to view or open to edit the file if the
policy gives you viewing and editing privileges. Alternatively, you can check the file out
of Matrix Navigator. Although opening a file to view or edit is similar to checking out a
file, there are differences.

Open for viewing is available in the desktop and Web versions of Matrix Navigator, but
open for editing is available only in the desktop version. Therefore, if you are using the
Web version and need to edit a checked in file, you should check out the file, edit the file,
and then check the file back in.

Object Open Edit Object Open View File Checkout

(desktop version only)
What happens to Matrix Navigator copies the checked-in Matrix Navigator copies Matrix Navigator lets you
the file? file to the Temp directory on your the checked-in file to the copy the file from the database
workstation.* Temp directory on your to a location that you specify.
workstation.*
Is the file changed When you exit the editing application, The file is not updated or You must check in the file
within the ENOVIA the file is updated in the database. If you changed within the again in order to update
Live Collaboration saved edits to the file in the application, database, even if you edit Matrix Navigator with a new
database? Matrix Navigator is updated with the the file and save it.* version of the file. Otherwise,
new file. If you did not save the edits, Matrix Navigator has no
the database is updated with the knowledge of the new file
unchanged file. contents.
Can other users edit Matrix Navigator locks the checked-in Matrix Navigator does Optionally, you can (and
the file while I’m object so that other users cannot access not lock the object. Other should) lock the file so that no
using it? it for editing. This prevents others from users can also open it if other users with editing
checking in and changing the same file they have privileges to do privileges can change it
or overwriting it with a different one. so. (overwrite your working
copy).
How is the Matrix Navigator launches the editing Matrix Navigator (or You run the viewing/editing
application application defined in the file format. your Web browser) application outside of Matrix
associated with the launches the viewing Navigator.
file launched? application defined in the
file format.
Under what This is useful for short-term editing. This is useful for viewing This is useful for long-term
conditions should I You can continue to use Matrix the file only. editing since you may need to
use each method? Navigator for other tasks while you are exit Matrix Navigator (maybe
editing. You also avoid locking the file at the end of the work day)
and checking it out and then in again. before all your edits are
However, you cannot exit Matrix complete. As a practice, you
Navigator until you have completed should lock the object after
your edits and saved them. you check it out so other users
cannot edit the file while you
are.*
* If the policy “enforces locking,” objects must be locked upon checkout if you want to check the file back in.

Chapter 8: Checking Files In and Out 201

 Using the Formats Browser

The Format browser lets you easily see which files are currently checked in to an object. It
displays a list of formats and then (in an indented view) shows each file that is checked in
to that format.

Formats available
for this object

Documents
checked in to
this object for
each format

Expand and
collapse controls

Indicates a locked object

The Formats browser lets you:

• check files into an object in any format that is allowed for the object by its governing
policy
• check files out of the object
• lock and unlock the object
• view checked in files in their associated application without checking out the file
• edit checked in files in their associated application without checking out the file
(desktop version only)
• print checked in files (desktop version only)
• display file information including originating path and host, and size (desktop version
only)
• delete specific files from an object (desktop version only)
The default format is listed in the above example as ASCII, but files are also checked into
MS Word and GIF formats. The default format is defined by the policy for that type. For
the desktop version, Matrix Navigator uses the default format when you check in a file
from any browser besides the Formats browser. For the Web version, Matrix Navigator
selects the default format when you check in a file from any other browser but you can
select a different format.

202 Matrix Navigator Guide

Viewing Formats Use the Formats browser to see the formats available for an object and to see the names of
and Names of checked-in files.
Checked-In Files To view formats and the names of checked-in files for an object
1. Select the desired object from the Studio Modeling Platform or Navigator browsers.

2. Click or select Formats from the Files menu.

The Formats browser opens, showing the different file formats available for the
selected object. By default, Checked In is checked and only those formats that
currently contain checked-in files are displayed.
3. To see all the available formats for the object, uncheck Checked In and click Filter.
4. If you are using the desktop version of Matrix Navigator, the Formats browser
expands to show all checked in files.
If you are using the Web version, click the Plus (+) sign next to a format to see the
files checked into the format.

In the desktop version, the Formats browser expands to show all checked-in files for an
object. If displaying the browser takes too long, however, your System Administrator can
change a setting that will keep the browser from displaying all checked-in files until you
choose the ones you want to view.

Viewing File You can view general information about any checked-in file. If the object the file is
Basics checked into is locked, the user who locked the object is shown in the Locked By box.

File basics is available from the desktop version of Matrix Navigator only.

To see basic information about a file

1. From the Formats browser, select a file listed below a format.

2. Click or select Basics from the Files menu. The Basics window opens.

Chapter 8: Checking Files In and Out 203

 Please note that in V6R2010, the file path was removed from the Basics for a checked-in
file. The file path was not very useful since paths can be deleted or the system from which
the file was checked in could be retired.Only the filename is displayed in the Path field
now.

204 Matrix Navigator Guide

 Opening Files for Viewing, Editing, and Printing

Opening a file that is checked into an object means launching the application associated
with the file and opening the file in the application. For example, when you open a file (for
viewing, editing, or printing) with an .xls extension, MS Excel launches and the file opens
in MS Excel.

Open for viewing, editing, and printing is available in the desktop version of Matrix
Navigator. Only open for viewing is available in the Web version.

Prerequisites For both the desktop and Web versions of Matrix Navigator, users can only open files
checked into an object (for viewing, editing, or printing) if they have read access for the
object. The Business Administrator establishes user privileges in person definitions,
policies, and rules. Additionally, the applicable software must be installed and associated
with the appropriate filenames.

Opening Files for When you open a checked in file for viewing, Matrix Navigator copies the file to a Temp
Viewing directory on your local workstation while you view the file. When you finish viewing the
file, Matrix Navigator does not update the file in the database. So if you make changes to
the file, you need to save it to your workstation and then check in the file to update the
database.
The procedure for opening a file for viewing differs depending on whether you are using
the desktop version of Matrix Navigator or the Web version. The first procedure below is
for the Web version. For instructions on opening for viewing using the desktop version,
see To open a file for viewing using the desktop version.

To open a file for viewing using the Web version

1. From Matrix Navigator, select the object containing the file(s) to view.
2. Perform one of following steps to open files:
Double-click the object, if your preference is set to View (not Edit).
Or
Right-click the object and select Open >View from the menu.
Or

Select the object and click .

Or
Select Open >View from the Object menu.
a ) If no files are checked in, an error message: “<Type> <Name> <Revision>
contains no files” is displayed.
b ) If one file is checked in, the file is opened for view (whether the file is checked
into the default format or not).
c ) If more than one file is checked in, the Open For View window appears, showing
all formats for the object.

Chapter 8: Checking Files In and Out 205

 • Double-click on a format to open all files in this format for view.
Or
• Expand a format to show its files and double-click on a file to open it for
view.
You can select multiple objects and choose Open for View. The Open for View
method loops through all selections and handles them separately. For business objects
that contain many files, your interaction is required for each separate Open for View
window that is displayed.
Matrix Navigator sends all files of the default format to the Web browser for opening.
If the appropriate file associations are established, the appropriate application
launches and opens the file(s).
3. Exit the application as normal when you are done viewing the file. You are returned
to Matrix Navigator.

If you make edits to documents while using Open for View, remember to save the file
locally before exiting the application. These changes will not be reflected in the copy of
the file that is kept in the database, until and unless you check in the file.

To open a file for viewing using the desktop version

1. Select the object containing the file(s) to view.
2. Perform one of following steps to open files:
Double-click the object, if your preference is set to View (not Edit).
Or
Right-click on the object and select Open>View from the menu.
Or

Select the object and click .

Or
Select Open>View from the Object menu.
a ) If no files are checked in, an error message: “<Type> <Name> <Revision>
contains no files” is displayed.
b ) If one file is checked in, the file is opened for view (whether the file is checked
into the default format or not).

206 Matrix Navigator Guide

 c ) If more than one file is checked in, the file that is checked in to the default format
is opened.
Or

Click or select Formats from the Files menu.

The Formats browser opens.
a ) Select the file you want to view.

b ) Click or select View from the Object>Open menu.

Matrix Navigator launches the application for the selected or default viewing
format. For example, if you open a Drawing object that is in a CAD file format,
Matrix Navigator launches the associated external viewing application (as
defined in the format).
If a higher revision of the selected object exists, Matrix Navigator warns you and
enables you to continue with the old revision or cancel the operation.
3. When you finished viewing the file, exit the application as normal.
You are returned to Matrix Navigator.

If you make edits to documents while using Open for View, remember to save the file
locally before exiting the application. These changes will not be reflected in the copy of
the file that is kept in the database, until and unless you check in the file.

Opening Files for Open for editing is available for the desktop version of Matrix Navigator only. If you are
Editing using the Web version and need to edit a file, you should check out the file, make your
edits to the file, and then check the file back in.

As described in Should You Open or Check Out a File?, all but extensive editing can
easily be performed from within Matrix Navigator. When you open a file for editing,
Matrix Navigator copies the file to a Temp directory on your workstation. When you
finish your edits and save the file, Matrix Navigator updates the checked in file.

To open a file for editing

1. Select the object containing the file.

2. Click or select Formats from the Files menu.

The Formats browser opens.
3. Select the file you want to edit.

4. Click or select Edit from the Object>Open menu.

Matrix Navigator launches the application for the selected or default editing format.
For example, if you open a Report object that is in an ASCII file format, Matrix
Navigator launches the associated word processing application (as defined in the
format).
If a higher revision of the selected object exists, Matrix Navigator warns you and
enables you to continue with the old revision or cancel the operation.

Chapter 8: Checking Files In and Out 207

 If the object is locked by another user, an error message appears and you cannot open
the file associated with that object.
5. When you have completed your work (editing) within the application, save your edits
and exit the application as normal.
You are returned to Matrix Navigator, and the file is updated in the database. If you
saved edits to the file in the application, Matrix Navigator is updated with the new
file. If you did not save the edits, Matrix Navigator is updated with the unchanged
file. If you have completed your edits, be sure to unlock the object.

If the selected object is part of a revision chain, saving the file may seem to “hang” the
system. This is because references to the file list are being replaced with an actual copy of
the file.

Printing a File Printing files is available for the desktop version of Matrix Navigator only. If you are
using the Web version and need to print a file, you should check out the file and print it
from the associated application.

To print a checked-in file

1. Select the desired object(s).
2. Open Print from the Object menu.
The Print window opens.

3. Click Print.
If a higher revision of the selected object exists, Matrix Navigator warns you and
enables you to continue with the old revision or cancel the operation.

When using the print button from the desktop version of Matrix Navigator, a blank page is
always ejected before printing.

208 Matrix Navigator Guide

Tips for Opening Here are some tips to keep in mind when opening files:
Files for Edit, • This tip applies only to desktop versions. If more than one file is selected for editing
View, or Print from the Formats browser, and you are allowing multiple files to be opened (by
setting the enovia.ini variable MX_BACKGROUND_OPEN equal to True), only the
first file selected opens, and an error occurs. This is because Matrix Navigator locks
the object when the first file is opened for edit, and so it is already locked for
subsequent open attempts. For this reason, it is recommended that to edit multiple
files within one object, first do a checkout with a lock, make the edits, and then
checkin and unlock. Use the formats browser to check out files that are not in the
default format.
Matrix Navigator supports opening multiple files in a single object for editing ONLY
in the following circumstances:
a ) If an editor that is capable of handling multiple files is invoked by selecting the
business object or format. In this case, the editing application is launched with a
list of files. This is true for both settings of MX_BACKGROUND_OPEN.
b ) If MX_BACKGROUND_OPEN=False, and you select multiple individual files
within the Formats browser. In this case, the editing application will be called
repeatedly in a loop with a single file each time, so it will work even for editing
applications that only handle one file at a time.
• Multiple objects may have files opened simultaneously, and the user can switch
between any of the launched applications and Matrix Navigator. The limit to this
would be dependant on the amount of memory in the user's machine, and the size of
the opened files.
• When a user opens an object, Matrix Navigator launches the supporting application
needed to open the file. Matrix Navigator does not check to see if the supporting
application is already running, nor if that application allows multiple files to be open
at the same time. If the supporting application is already running, it launches another
instance of that application.
• Double-clicking an object attempts to open ALL files checked in to the object’s
default format. If more than one exists, double-clicking causes an error, since the
object is locked when the first file is opened.
• If you double-click on an object which has no files checked in, Matrix Navigator
creates a 0-byte file and checks it into the object in the default format.

Chapter 8: Checking Files In and Out 209

 Checking Files In and Out

You can check in or check out 1 or more files for an object.You can check out all files in a
particular format or all files in all formats.
Keep in mind that the policy governing an object determines the users who have checkin
and checkout privileges. In addition, the policy governs the control Matrix Navigator has
over the files checked in.

For the Web This section contains information applicable to checking files in and out when using the
Version Only Web version of Matrix Navigator only.
When files are checked in or out, the system must read or write to the user’s file system.
With some browsers, you have to grant the applet this access by clicking Grant in the
Security Warning dialog.
You can import ENOVIA’s Public certificate to avoid this warning. Contact your System
administrator and refer to the ENOVIA Live Collaboration Installation Guide for details.

Checking In a File When you check in a file, you move a copy of the file from your workstation to an object
in the database. Matrix Navigator assigns this file the default format for the object type,
unless you specify a different format. If using the desktop version, you can check in
multiple files to an object at the same time. You can also delete the original file from the
workstation directory upon check-in.

If locking is enforced in the object’s policy, you can only check in a file (for all but the
initial checkin) if you were the last person to check out a file for the object and you locked
the object when you checked it out.

The procedure for checking in files differs depending on whether you are using the
desktop or Web version of Matrix Navigator. The first procedure below is for the Web
version. For instructions on checking in using the desktop version, see To check in a file
using the desktop Navigator.

To check in a file using Web Navigator

1. Select the object into which you want to check a file.
Note that if multiple revision objects exist (such as Drawing 123 A and Drawing 123
B), the file is checked into the selected object (revision) only.

2. Click or select Checkin from the Files menu.

Or
Right-click on the object and select Files>Checkin.
The Checkin window appears.

210 Matrix Navigator Guide

 The allowed formats are displayed under the object in an indented arrangement. You
can expand the formats to show file names of checked in files.
3. To check in a file of a format other than its default, select the format of the file you
want to check in.
4. Click Browse to locate and select a file to check in to the object.

5. Select an option to specify how the checked in files affect the files currently checked
into the object.
Replace Files—The selected files replace all files currently checked in to the object
in the selected format. If three files of that format are currently checked in and you
check in a file using Replace Files, the one file replaces the previous three files (they
are removed). Existing files of other formats are not removed.
Append Files—The selected files are added to any files currently checked into the
object, in the selected format.
6. To allow users to check in files to the object and open checked-in files for edit, check
Unlock Object. If an object is locked, a padlock icon is displayed to the left of the
message bar in the Checkin window (in some browsers).
7. To delete the files from the directory on disk after they are checked into the object,
check Delete Files After Checkin.
8. Click Checkin.

Chapter 8: Checking Files In and Out 211

 If the selected object is part of a revision chain, the checkin may seem to “hang” the
system. This is because the system is replacing references to the file list with actual copies
of the files in one or more of the revisions.

To check in a file using the desktop Navigator

1. Select the object into which you want to check a file.
Note that if multiple revision objects exist (such as Drawing 123 A and Drawing 123
B), the file is checked in to the selected object (revision) only.
However, if a higher revision exists, Matrix Navigator warns you of the fact if the
warning option is set (refer to Setting Preferences in Chapter 1).

2. If you want to use the default format, click , select Checkin from the Files menu,
or right-click the object and select Files>Checkin.
Or
If you want to select a specific format to check the file into:

a ) Click , select Formats from the Files menu, or right-click the object and
select Files>Formats.
The Formats browser is displayed.

b ) If necessary, uncheck the Checked In box and click Filter to see all available
formats.
c ) Select the desired format.

d ) Click or select Checkin from the Files menu.

The Checkin window is displayed.

212 Matrix Navigator Guide

 A default check-in file path can be specified with a Session Preferences option. Refer
to Setting Preferences in Chapter 1 or talk with your Business Administrator for more
information.
Notice that the title bar of the checkin window indicates a format for the file to be
checked in. To check in a file of another format, click Cancel and refer to Using the
Formats Browser earlier in this chapter.
3. Double-click the directory in which the file resides.
The files contained in the selected directory are displayed.

Matrix Navigator uses the “@” symbol for internal operations. Be sure that none of the
filenames or directories you are accessing to check in files include this symbol.

4. Select one or more files to check in to the object.

5. Select an option to specify how the checked-in files affect the files currently checked
in to the object.
Replace Files—The selected files replace all files currently checked in to the object
in the selected format. If three files of that format are currently checked in and you
check in one more file using Replace Files, the one file replaces the previous three
files (they are removed). Existing files of other formats are not removed.
Append Files—The selected files are added to any files currently checked in to the
object, in the selected format.
6. Check Unlock Object to unlock the object so that other users can access the files
being checked in. If an object is locked, a padlock icon is displayed to the left of the
message bar in the Checkin window.
7. Check Delete Files After Checkin to delete the files from the directory on disk after
they are checked in to the object in the database.
8. Click Checkin.

Chapter 8: Checking Files In and Out 213

 The file is checked in, but does not immediately appear in the formats browser. To see
the file listed, click the collapse button of the format and then expand it again.

If the selected object is part of a revision chain, the checkin may seem to “hang” the
system. This is because references to the file list are being replaced with actual copies of
the files in one or more of the revisions.

Checking Out a When you check out a file, you move a copy of the file from the ENOVIA Live
File Collaboration database to a destination directory. There are several approaches that can
be used:
• You can check out one or all files checked in to an object
Or
• You can check out all files of a specified format.

When checking out a file from c:\documents and settings\username\my documents, you
may receive the following error: No write access for file <file>, even though the My
Documents directory is writable. This error is due a Sun JVM bug. The work-around is to
run the "attrib -r" command on c:\documents and settings\username\my documents.

The procedure for checking out files differs depending on whether you are using the
desktop or Web version of Matrix Navigator:
• To check out an object’s files using the Web version
• To check out an object’s files using the desktop version

To check out an object’s files using the Web version

1. Select the object(s) from which you want to check out files.

2. Click or select Checkout from the Files menu.

Or
Right-click the object and select Files>Checkout.
If the business object does not contain any files, the Checkout window does not open.
Instead the following error is displayed:
<Type> <Name> <Revision> contains no files
Otherwise, the Checkout window appears. The number of formats used and files
present determines how the file list is presented:
• If the business object only contains one file, the Checkout window tree is
expanded to the file level and the file is selected.

• If the business object contains many files but only in one format, the Checkout
window tree is expanded to the format level and the format is selected.

214 Matrix Navigator Guide

 • If the business object contains many files in different formats, the Checkout
window tree is expanded to show all formats with checked in files. No format is
selected by default.

• If you selected multiple objects before selecting Checkout, one Checkout

window shows all selected objects expanded appropriately.

3. Select the file(s) to be checked out. You can:

• select a format to checkout all files in the format
• expand a format to see all files, and select specific files from the file list
• select the business object (the top level of the “tree”) to checkout all files in all
formats
4. Click Browse to select the directory where Matrix Navigator should place the copied
files.
5. Check Lock Object to prevent another person from editing any checked in files while
you have the file(s) checked out.
When an object is locked, no files can be checked in to the object. This means that
attempts to open for edit, as well as checkin, will result in an error. However, files can
be checked out of a locked object and also opened for view.

Chapter 8: Checking Files In and Out 215

 If you intend to make changes to the file you are checking out and then check the file
back in again, you should lock the object during the checkout. In fact, if locking is
enforced in the policy, you must lock the object when you check it out or you will be
unable to check it back in.
Enforced locking prevents you from overwriting changes made by another user, only
allowing check in when:
• the object is locked
and
• the user that locked it is the user that is checking in
6. Check Overwrite Existing Files to replace an existing file in your workstation
directory with the checked out file if it has the same name.
7. Click Checkout.

If a higher revision of the selected object exists, you get a warning that a higher revision
exists. You can continue checking out a file from the old revision or cancel the operation.

To use the formats window to checkout files in the Web version

1. Select the object(s) from which you want to check out files.

2. Click or select Formats from the Files menu.

Or
Right-click on the object and select Files>Formats.
3. Expand a format to see all files, and select specific files from the file list.

4. Click or select Checkout from the Files menu of the Formats window. A
checkout window requests the path in which to place the selected files:

5. Click Browse to select the directory where Matrix Navigator should place the copied
files.
6. Check Lock Object to prevent another person from editing any checked in files while
you have the file(s) checked out
When an object is locked, no files can be checked in to the object. This means that
attempts to open for edit, as well as checkin, will result in an error. However, files can
be checked out of a locked object and also opened for view.
If you intend to make changes to the file you are checking out and then check the file
back in again, you should lock the object during the checkout. In fact, if locking is
enforced in the policy, you must lock the object when you check it out or you will be
unable to check it back in.

216 Matrix Navigator Guide

 Enforced locking prevents you from overwriting changes made by another user, only
allowing check in when:
• the object is locked
and
• the user that locked it is the user that is checking in
7. Check Overwrite Existing Files to replace an existing file in your workstation
directory with the checked out file if it has the same name.
8. Click Checkout.

If a higher revision of the selected object exists, you get a warning that a higher revision
exists. You to continue checking out a file from the old revision or cancel the operation.

To check out an object’s files using the desktop version

1. Select the object from which you want to check out a file.

2. To check out all the files checked into the object’s default format, click or select
Files>Checkout.
Or
To check out specific files or files that are not of the default format:

a ) Click or select Formats from the Files menu.

Or
Right-click on the object and select Files>Formats.
The Formats browser opens.
b ) Select the file or files you want to check out. Use the Shift or Ctrl key to select
more than one file.

c ) Click or select Files>Checkout.

The Checkout window opens.

Chapter 8: Checking Files In and Out 217

 3. Select the directory into which you want to place the file(s).
A default checkout file path can be specified with a Session Preferences option or in
the initialization file. Refer to Setting Preferences in Chapter 1 or talk with your
Business Administrator for more information.

Matrix Navigator uses the “@” symbol for internal operations. Be sure that none of the
filenames or directories you are accessing to check in files include this symbol.

4. Check Lock Object to prevent another person from editing the files.
When an object is locked, no files can be checked in to the object. This means that
attempts to open for edit, as well as checkin, will fail. Files can be checked out of a
locked object, and also opened for view.
If you intend to make changes to the file you are checking out and then check the file
back in again, you should lock the object during the checkout. In fact, if locking is
enforced in the policy you must have locked the object when you checked it out or
you will be unable to check it back in.
Enforced locking prevents files from inadvertently being overwritten, only allowing
check in:
• when the object is locked
and
• when the user who locked it is the user that is checking in

218 Matrix Navigator Guide

 5. Check Overwrite Existing Files to replace an existing file in your workstation
directory with the checked-out file if it has the same name.
6. Click Checkout.

If a higher revision of the selected object exists, Matrix Navigator warns you and enables
you to continue with the old revision or cancel the operation.

Deleting a You can delete:

Checked-in File • A selected file that has been checked in
• All checked-in files for a selected format

Checked-in files can be deleted in the desktop version of Matrix Navigator only.

To delete a file or files check-in for an object

1. Select the object from which you want to delete a checked-in file(s).

2. Click or select Formats from the Files menu.

The Formats browser opens.
3. To delete one checked-in file, select the file to delete.
Or
To delete all checked-in files for one format, select the icon for the format.
4. Select Delete from the Files menu.
You are prompted to confirm the deletion.
If you selected to delete all files for a format, Matrix Navigator attempts to delete all
checked-in files of the format selected. If there are no files in the selected format in
the object, an error message is displayed.

When deleting files from the last object in a revision chain, only the link to the files is
deleted. However, when deleting a file/format from a business object that is not the last in
a revision chain, the file is first copied to the next object in the revision chain, if a
reference to that file exists. This latter case may impact performance.

Chapter 8: Checking Files In and Out 219

 Locking and Unlocking an Object

When an object is locked, no files can be checked into the object until the lock is released,
even if the file will not replace the checked-out file that initiated the lock. This means that
attempts to open for editing, as well as checkin, will fail. Files can be checked out of a
locked object and also opened for viewing. For example, if you are the department
accountant, you may want to check out an audit file and lock its object. Only you can
modify the object’s file(s) while it is locked. Then, after you have completed your
modifications, you might check in the file and unlock the object so that the company
controller can enter additional changes.
You can lock an object when you check out files, as described in Checking Out a File.
You can unlock an object when you check in files, as described in Checking In a File. In
addition, you can lock and unlock all objects manually, as described in the following
sections.

If an object is governed by a policy that has Enforce Locking turned on, then you cannot
manually lock the object. You can only lock the object when checking out a file.

For the desktop version, the locked status of a file is shown in the File Basics window. If
the object a file is checked into is locked, the user who locked the object is shown in the
Locked By box.
For users who are using the Web version, a padlock icon will also be displayed to in the
lower left of the Formats browser if the object is locked.

Locking an Object You must have lock access to lock an object.

To lock an object
1. Select the object in the Formats browser.
2. Select Lock from the Files menu.
When an object is locked the lock icon appears on the Formats browser window. If the
object is unlocked, nothing appears in that space.

220 Matrix Navigator Guide

 Lock Icon

If another person needs checkin access to the object, it must be unlocked, as described
below.

Unlocking an If you place a lock on an object, you are allowed to unlock it, regardless of your access
Object privilege. However, if you are not the user who locked the object, you may unlock it if you
have unlock access on the object.
You can determine the locked/unlocked status of an object by reviewing its history, as
described in Looking at Historical Information in Chapter 2 or by looking in the Formats
browser.

To unlock an object
1. Select the object.
2. Select Unlock from the Files menu.

Chapter 8: Checking Files In and Out 221

222 Matrix Navigator Guide
 9
Using the Object
Lifecycle

Overview

Each object has a lifecycle—a series of states through which it passes during its existence.
The window in which a lifecycle is displayed is called a States browser. The States
browser below shows an example of a lifecycle and its states from inception to
completion.

223
 The lifecycle of an object is defined by the object’s policy. Referring to the lifecycle
displayed above, the policy controls when the object is planned, started, reviewed, tried
out, and released. And, at each state in an object’s lifecycle, the policy defines the person
or groups of people who can perform each possible action with the object. The policy also
defines the requirements to move an object from state to state.
For example, if you are the Project Manager for a new product, you might need to set up a
schedule of milestones and completion dates that must occur to meet production
schedules. In addition, you might need to control all aspects of the product development
from inception to its release. Matrix Navigator lets a Business Administrator set up
policies that implement the business practices used within your organization. As a result
of this underlying Matrix Navigator schema, you, as a Matrix Navigator user, are able to
manage objects within Matrix Navigator quickly and easily using the object lifecycle
feature, as described in this chapter.

224 Matrix Navigator Guide

 Viewing States

The States option enables you to look at and work with the states in an object’s lifecycle.
For example, as a Project Manager, you would define the milestones in the product
development cycle.
1. Select the object.

2. Click or select States from the Properties menu.

The States browser is displayed.

The States browser shows all possible states defined by the policy governing the
selected object. Each state is shown graphically. The current state (Planned, in the
example above) is marked with a vertical arrow.
The States browser provides several unique tools and symbols. A summary of all
States browser icons is provided in a table below.
3. Click Close to close the States browser.

Chapter 9: Using the Object Lifecycle 225

 Interpreting States Browser Symbols

When you display a States browser for a selected object, icons appear as tools on the
States browser or as symbols beneath a state. The following table presents an overview of
possible tools and symbols, as well as their meanings.

States Browser Tools and Symbols

Indicates the current state of a selected object in its lifecycle.

State transition arrow that indicates the transition from one state to the
next. May also skip states and be shaped more like the second picture
shown here.

Indicates that a file may be checked into the database in this state
(when displayed beneath a state).
Indicates that the scheduled completion date of the state is approaching
or has passed. A yellow pin indicates that the selected date is near. A
red pin indicates the completion date of the state has passed, and the
actual date was after that, or has not yet occurred. (It’s LATE!)
Displays the signature requirements necessary to promote an object to
its next state, allowing selection and signoff.
Displays the scheduled and actual completion dates for the selected
state. The scheduled date may be specified with this tool, but the actual
date is entered by Matrix Navigator when the object is promoted to
this state.
Displays the logged on user’s access privileges for the selected state.

Enables promotion from one state to the next.

Disables promotion from one state to the next. When displayed below a
state, this symbol indicates that promotion is disabled for the state.
Overrides the requirements of the state. When displayed below a state,
this symbol indicates the requirements for promotion to the next state
have been overridden.
Promotes an object from its current state to the next.

Demotes an object from its current state to the previous state.

226 Matrix Navigator Guide

 Transitioning From State to State

Objects can be moved from one state to the next when conditions for state transition are
met as defined in the object’s policy. An object is promoted to the next state automatically
if the policy specifies auto-promotion and all requirements are met. The following
operations are performed with the States browser displayed.

State Branching A signature specifies who can control the promotion or rejection of a business object.
and Signatures When an object is promoted, it moves to the next defined state and is subject to the access
rules associated with that new state. When an object is rejected, it remains in the current
state until it meets the criteria for promotion.
A branch defines what the next state will be after a signature is applied. For each state, it
is possible to have more than one branch. Which branch is taken depends on which
signature is satisfied.
Your Business Administrator defines the policy and whether state branching is allowed.
When promotion is initiated, the system chooses the state for which all signatures are
satisfied. If more than one branch is enabled, an error occurs.

Satisfying You can apply an electronic signature to satisfy the signature requirements necessary to
Signature promote an object to its next state. Signatures are defined by the object’s policy.
Requirements For example, the appropriate signatures are required before a product can be promoted to
the next scheduled step in its development cycle.

To apply an electronic signature

1. Select the state transition arrow between the current state and the state to which you
wish to promote it. There may be several branches possible.

2. Double-click the state transition arrow.

Chapter 9: Using the Object Lifecycle 227

 Or

Click .
Or
Select Signature from the Path menu.
The Signature Requirements window is displayed, listing the applicable signatures.

3. Select the object that corresponds to the signature you want to apply. Signatures are
defined by the policy.

4. Click or select Approve from the Signature menu to approve the selected
signature.
Or

Click or select Reject from the Signature menu to reject the selected signature.
Or

Click or select Ignore from the Signature menu to indicate that the selected
signature is not necessary for promotion.
An Approve, Reject, or Ignore message is displayed. An example of an Approve
message is shown below.

5. Type a comment in the Comment box. The comment may contain an unlimited
number of characters.

228 Matrix Navigator Guide

 For example, you might want to explain the conditions under which you chose to
approve the signature.

When you ignore a signature, you must enter a comment (as well as have ignore access to
the signature) in order to complete the operation.

6. Click Approve, Reject, or Ignore to confirm your entry.

The Signature Requirements window redisplays and reflects your action.
7. Click Close when finished.

Reviewing You can review the comments that were added for a signature.
Signature
To review signature comments
Comments
1. Select the desired signature, such as Complete, in the Signature Requirements
window.

2. Click or select Review from the Signature menu.

The Review window is displayed.

The Review window shows the name of the signer, the disposition (approved,
rejected, or ignored) of the signature, and any comments that were added to the
signature. Click Close when finished.

Reviewing You can display lists of all users who are authorized to perform actions on a signature.
Signature Access This information is retrieved from the policy.

The ability to review signature access is available in the desktop version of Matrix
Navigator only.

To review signature access

1. From the Signature Requirements window, select the desired signature.

2. Click or select Access from the Signature menu.

The Signature Access window opens.

Chapter 9: Using the Object Lifecycle 229

 The Signature Access window is divided into three list boxes, indicating the users
(Persons, Groups, and Roles) that have Approve, Reject, and Ignore access to the
signature. These accesses are defined in the policy.
3. Click Close.

Scheduling You can indicate the scheduled arrival dates for each state in the lifecycle. For example, as
a Project Manager with the appropriate access (as defined in the policy), you could define
the proposed completion dates of each milestone.

To schedule state arrival dates

1. Select the state you want to schedule in the States browser.

230 Matrix Navigator Guide

 The scheduled date for P.O. In Process, for example, would be the date that the object
should be promoted (completed) from the Initiate Purchase state.

2. Double-click the state, click , or select Schedule from the State menu.
The Schedule window is displayed.

3. Enter the scheduled date for the state in the Scheduled text box.
A date can include the year, month, day, hour, minute, and/or second. Abbreviations
or full-words are acceptable for the day of the week and month. The acceptable range
is January 1, 1902 through December 31, 2037. For example:
Wed Feb 15, 1995
2/15/95
If you have problems entering dates, ask your ENOVIA Live Collaboration Business
Administrator for information on the date format established for your Matrix
Navigator system. The administrator has control over the formats for entry and
display of dates.
4. Click Schedule.
5. Click Close.
Matrix Navigator automatically adds the actual date in the Actual text box when the
object actually reaches that state.

Displaying Access As an individual involved in a project, you can review your access privileges for each state
Privileges in the lifecycle.

To review your access privileges for a state

1. Select the state for which you want to show access privileges.

2. Click or select Access from the State menu.

The Access window is displayed.

Chapter 9: Using the Object Lifecycle 231

 This window shows the privileges of the current user (as set in the session context) to
access activities at the selected state. Your access at the selected state may be limited.
3. Click Close.

Disabling It is possible to disable promotion from one state to the next. Key roles would have this
Promotion privilege—typically the same roles as those with privileges to enable promotion.

To disable promotion of a state

1. Select the state for which you want to disable promotion.

2. Click or select Disable from the State menu.

When the object reaches this state, it may not be promoted until the state is enabled
again even if all promotion requirements are satisfied. Notice that the red light is
displayed below the selected state.

Enabling It is possible to enable promotion from one state to the next if promotion has been
Promotion disabled. Only key roles (Engineering, Quality Control, and Production Managers) might
have this privilege.

To enable promotion of a state

1. Select the state for which you want to enable promotion.

2. Click or select Enable from the State menu.

When the object reaches this state, it may be promoted when all promotion
requirements are satisfied.

Overriding If you have an override privilege, you have the authority to override any other
Promotion requirements for promotion. This privilege typically is given to a project leader or a
department supervisor. Complete the following to override promotion requirements from
one state to the next.

To override promotion requirements

1. Select the state for which you want to override promotion requirements.

2. Click or select Override from the State menu.

When the selected object reaches the selected state, it may be promoted without
satisfying any of the promotion requirements. Notice that the override symbol is
displayed below the selected state.

To “undo” an override, disable and then enable the state.

Promoting an When the criteria defined for meeting any given milestone (state) are met, as defined in
Object the policy, promotion to the next state in the lifecycle should occur.

232 Matrix Navigator Guide

 An object is promoted automatically when the last requirement is met and Auto Promote
is enabled on the state in the policy. If a state has no requirements (signatures or program
checks) Auto Promote has no meaning and the object must be explicitly promoted.
You can manually promote an object from its current state to the next if you have the
privileges to do so. Signatures must be met or overridden as described in the previous
sections.

To promote an object

• With the States browser open, click or select Promote from the State menu.

The object is promoted to the next state, as indicated by , the up arrow.

Before promotion:

After promotion:

Demoting an You can also demote an object from its current state to the previous state. For example, a
Object major re-design in a product might cause it to be demoted from its current state back to its
previous state.

Chapter 9: Using the Object Lifecycle 233

 To demote an object

• With the States browser open, click or select Demote from the State menu.

The is moved to the previous state to indicate that the object has been demoted.

Completion If you have defined scheduled dates for states, Matrix Navigator will warn you if the
Warnings scheduled date of a state is approaching or has passed. The warning is displayed beneath
the applicable state.

A yellow pin indicates that one week or less remains until

the scheduled date arrives.
A red pin indicates that the scheduled date of the state has
passed.

234 Matrix Navigator Guide

 10
Using IconMail

Sending and Receiving Information

Information is distributed across Matrix Navigator in two basic ways:

• Manually—Mail can be distributed to any users involved in the flow of work during
an object’s lifecycle.
• Automatically—Mail can be sent and received automatically based on an object’s
lifecycle states, or via a trigger, wizard, or method.
When mail is sent, Matrix Navigator checks the recipient’s person definition (set by the
Business Administrator) to determine the destination for the mail. The person definition
may be set to receive mail as:
• IconMail (described below)
• E-mail
• Both IconMail and e-mail
• Neither IconMail nor e-mail
IconMail is mail generated, sent, and received within Matrix Navigator. Distributed
information is in the form of an object with an attached message. Since a reference to the
object is sent, IconMail makes it easy to access all related objects and associated files.
After selecting the mailed object, you can use any of the options described in this guide,
such as opening, editing, viewing, and so on. This means you can quickly access the files

235
 associated with the IconMail (if the policy governing the object permits). You can choose
the files to obtain and the formats in which to display them.
TaskMail is also received in the IconMail inbox. Activities that are assigned to you as part
of a workflow are distributed in this manner. You may open the activity from within the
IconMail inbox and perform necessary operations as required. Refer to Working With
Workflows in Chapter 12 for more information.
Matrix Navigator periodically checks for the arrival of new mail for the current user
context. When new mail is detected, the IconMail button in the main browser switches
from an empty mailbox to a mailbox with letters. This indicator only detects the existence
of unread or newly delivered mail. It will not indicate the presence of previously read
mail.
If the mail destination is e-mail, it is not possible to send the object with direct access to
the associated files. However, the object type, name, and revision are added to the
message so that the recipient can identify the object. To read an e-mail message, you must
use your e-mail system. In order to receive TaskMail, users must be setup to receive
IconMail.

236 Matrix Navigator Guide

 Distributing Mail Manually

You can distribute mail to other users at any time. When you distribute mail, you send one
of the following to each person or group on a distribution list:
• IconMail—A message with an object attached. IconMail is copied to an IconMail
window for each specified recipient on the distribution list.
• E-mail—E-mail is sent to the recipient with the object name in the message. Users
must use their e-mail system to read it.
The destination (IconMail or e-mail) is determined by the way the recipient is defined by
the Business Administrator. To send either type of mail, you:
• Select the object to which you will attach a message
• Select the appropriate recipients
• Enter a subject for the message
• Compose a text message
• Send the object and message
For example, if you are a Stress Analyst who needs to notify people of the need to change
Drawing 12345, you might use Matrix Navigator to send mail to the Design department,
your manager, and the QA engineer.
The activities involved in sending mail are described in the following procedures.

Sending Mail When you send mail manually, you must select the objects, open the Send window, define
Manually the distribution list, and enter the message. You can send one or more objects at the same
time.

To send mail manually

1. Select the object(s) to which you will attach a message.

2. Click or select Send from the Object menu.

The Send window is displayed, with the selected objects shown near the top.

Chapter 10: Using IconMail 237

 3. In the To box, enter the names of the persons, groups, and roles to whom you want to
send mail.

When sending mail to multiple users, enter each name delimited with a comma but no
space.

Or

Click next to the To box and select persons, groups, and roles from the User
Chooser that appears.

By default, all defined users are displayed. You can filter the display by typing a
partial type name with a wildcard in the Name box and clicking Filter.

238 Matrix Navigator Guide

 In addition to the Name box, the following check boxes are provided to further filter
the display:
Top Level—Displays only the top level of the expandable tree list.
Person—Displays persons.
Group—Displays groups that the owners work within.
Role—Displays roles in the organization.
4. Repeat Step 3 to specify in the CC text field any users to whom you want to send a
copy of the message.
5. Type a brief description of the subject of your message in the Subject box. The
Subject field is limited to 255 bytes.
6. Type the message in the Message box.
The results of your entries will look similar to the following.

7. Click Send to send your message to the selected recipients.

Routing an Object If an object policy permits reassignment of ownership, you can use the Route option to
send IconMail to a user and change the ownership of the selected object to that person in
one step.

To route an object
1. Select the objects to route. Two were selected in the example below.
2. Select Route from the Object menu.
The Route window is displayed.

Chapter 10: Using IconMail 239

 3. Type the name of the new owner in the To box.
Or
Click the To ellipsis button and select the person, group, or role from the User
Chooser that appears.
4. Enter the Subject and Message.
5. Click Route.

240 Matrix Navigator Guide

 Receiving IconMail

Matrix Navigator periodically checks for the arrival of new mail for the current user
context. When new mail is detected, the IconMail button in the main browser switches
from an empty mailbox to a mailbox with letters. You can then read the mail you have
received.

For desktop version users: The enovia.ini file contains a variable, MX_CHECK_MAIL,
which indicates how often to check for new IconMail. The default is every 15 minutes. You
can adjust this setting if you want to change how often to check for new IconMail.

Recipients of e-mail must use their e-mail system to read mail.

If new mail or tasks are sent to you while your inbox is open, it is not automatically
received. You must first close the IconMail inbox and reopen it to see new messages.

To read mail

1. Click or select Mailbox from the Object menu. The IconMail-inbox window is
displayed.
By default, all IconMail and TaskMail received is displayed. The IconMail inbox
indicates the status of the message (new, unread, or read), the sender’s name, the date
and time the message was sent, and the subject of the message.
Workflow tasks can be identified by the task icon in the left column of the
inbox. Refer to Working with Tasks in Chapter 12 for information and procedures
related to TaskMail.

In a distributed environment with more than one server, only the mail received by
users logged into the same server as the current context user is displayed. (Applies to
desktop version only.)
The Filter Bar provides the following fields where criteria can be specified to limit the
messages displayed:

Chapter 10: Using IconMail 241

 Server—Shown for desktop version only. By default, mail received from the server
to which the current user is logged onto is displayed. Changing the entry to * shows
mail received from users of all servers.
Subject: You can enter text found in the subject of a message, with or without
wildcard characters.
In addition to these text boxes, the following check boxes are provided to further filter
the display:
New—Displays only IconMail received since the last time you opened the inbox.
Unread—Displays only IconMail that has not been read (opened).
Read—Displays only IconMail that has been read.
Once the criteria is specified, click Filter and only those messages that meet the
criteria display.
The IconMail inbox indicates the status of the message (unread or read), the sender’s
name, the date and time the message was sent, and the subject of the message.
Messages are displayed in the order they are received. However you can sort based on
any of the columns by clicking on a column heading. Clicking again will change the
sort order (ascending or descending).
2. Double-click on the desired IconMail.
Or
Select the desired IconMail.
The item is highlighted in the inbox.

Click or select Read from the Message menu.

The Read Mail window is displayed.

3. Click OK after reviewing the message.

242 Matrix Navigator Guide

Working with IconMail messages provide access to the objects they contain. You can quickly access the
IconMail files associated with the IconMail (if the policy permits). Also, access to most browser
menus and tools is provided in the Read Mail window, so objects received can be
reviewed (open for view or view attributes), navigated, and/or approved right from the
IconMail message.
The Icons or Table button is available in the inbox, depending on what mode your Matrix
Navigator browser is in. This provides a means of placing any or all connected business
objects into a browser for further inspection and manipulation.

To access IconMail objects

• Double-click on the object in the Read Mail window to open its checked-in file.
Or
1. Select the desired object in the Read Mail window.
2. Use any of the options described in this book—such as open for view, open for edit
(desktop version only), checkout, or View>Attributes Modify—to manipulate the
object that is the subject of the IconMail.
You can also access objects from the IconMail inbox (desktop version only):
1. From the IconMail inbox, select a message.

2. Click or select Objects from the Message menu.

The Matrix Navigator browser appears, showing the object referenced in the message.

If you select Objects from the Message menu without a message selected, all objects from
all messages appear in the Matrix Navigator window.

Printing IconMail Printing IconMail is available in the desktop version of Matrix Navigator only.
Messages
You can print the context of an IconMail message.

To print IconMail messages

1. From the IconMail inbox, select the message that you want to print.

2. Click or select Print from the Print menu.

The Print window appears. Change options as desired.
3. Click OK.

When using the print button from the desktop version of Matrix Navigator, a blank page is
always ejected before printing.

To define the Page Setup for printing

Matrix Navigator IconMail allows you direct access to the Print Setup window. To select a
different printer or set up different printer preferences:
1. From the IconMail inbox, select Page Setup from the Print menu.

Chapter 10: Using IconMail 243

 2. Change options in the Print Setup window.
3. Click OK.

Replying to a You can reply to the author of an IconMail message from the IconMail-inbox.
Message To reply to IconMail
1. Select Reply from the IconMail Message menu.
The Send window opens with the selected objects shown in the top portion of the
window. The To field shows the name of the person who sent you the message. The
Subject field contains Re: and the subject as included in the original message.
2. Type your message in the message box. You can leave the original message in the
message area as a reminder to the author, or select it and delete it.
3. Click Send to send your reply.
To reply to the author and also to all other recipients of the original message, select Reply
All from the IconMail Message menu, then follow the steps shown above.

Forwarding a You can forward an IconMail message you received to other Matrix Navigator users who
Message might have interest in or need the information included in the message that was sent to
you. Generally, when forwarding mail, you leave the original message intact and
sometimes include an explanatory message from yourself to the recipient(s). You may
also edit the original message.

To forward an IconMail message

1. Select Forward from the IconMail Message menu.
The Send window opens with the selected objects shown in the top portion of the
window. The Subject box contains the subject as it was included in the original
message.
2. In the To box, type the names of the persons, groups, and roles to whom you want to
forward the mail.
Or
Click the To ellipsis button and select Persons, Groups, and Roles from the User
Chooser that appears (as described in Sending Mail Manually).
3. If you wish, you can include additional information in the message area, or edit the
message that is already there.
4. Click Send to forward the message.

Deleting a You can delete IconMail from the IconMail-inbox.

Message To delete an IconMail
1. Select the IconMail to be deleted.
2. Select Delete from the Message menu.
The specified IconMail is deleted.

244 Matrix Navigator Guide

 Sending Mail and Receiving IconMail
Automatically

Matrix Navigator may distribute mail messages automatically as an object passes from
one state to another during its lifecycle. Your Business Administrator defines this process.
You can read IconMail that was sent to you automatically in the same way that you would
if it was sent manually by another user. Refer to the procedures for Receiving IconMail.
When receiving e-mail messages from Matrix Navigator or other sources, you must access
and read the messages through your e-mail system. IconMail messages received as e-mail,
cannot contain ImageIcons. However, the object type name and revision are added to the
message so that the recipient can identify the object.

Chapter 10: Using IconMail 245

246 Matrix Navigator Guide
 11
Annotations and
Attachments

Annotating or Attaching Information to an

Object

Two common activities that can take place during an object’s lifecycle are:
• Connecting an annotation (such as a drawing mark-up) to a selected object.
• Attaching information (such as an audio comment, note, photograph, or video) to a
selected object.
Connecting Objects in Chapter 7, described how to define a relationship between objects.
As you will see in this chapter, a relationship is defined automatically when you annotate
an object or attach information.

Annotations and attachments are available in the desktop version of Matrix Navigator
only and are not available in the Web version.

247
 Annotating an Object

You create an annotation, such as a drawing mark-up or a text mark-up, using another
software application, such as design/drafting or word processing software. Then, within
Matrix Navigator, you can attach the annotation (as an object) to another object. Like
other types of business objects, a policy governs annotations.
This chapter leads you through a sample procedure for annotating an object. When you
indicate that you want to annotate an object, Matrix Navigator:
• Creates an object of the selected annotation type (such as a drawing mark-up).
• Opens the appropriate annotation application (such as design/drafting software) to
create a file for the annotation.
• Adds attributes that describe the attachment.
• Checks the file into the annotation object.
• Connects the annotation object to the object to be annotated.
When you have completed the annotation procedure, Matrix Navigator displays the
annotation object with other objects on your browser. You can then use this object as you
would use any other business object.

Check with your Business or System Administrator to be sure that Annotation types,
relationships, and policies are defined.

Creating an To create an annotation object

Annotation Object 1. Select the object to which you will connect an annotation.
2. Select Annotation from the Object>New menu.
The Annotation window opens.

A default name and vault may be displayed. The name is generated by Matrix
Navigator automatically. You can modify any field as required, as described in the
steps that follow.
3. Type the name of an annotation type in the Type box.
Or

248 Matrix Navigator Guide

 Click the Type ellipsis button and select an annotation type from the Type Chooser.

A default revision, relationship, and policy are entered automatically based on the
annotation type you selected. This information was associated with the type when the
Administrator created it.
4. Change the default name by typing a new name in the Name box.
5. Change the revision by typing a new one in the Revision box.
6. Type the name of the relationship between the annotation and the object to which the
annotation will be connected in the Relationship text field.
Or
Click the Relationship ellipsis button and select a relationship using the Relationship
Pattern window that appears.
7. Type the name of the vault that will contain the annotation in the Vault box.
Or
Click the Vault ellipsis button and select a vault from the Vault Pattern window that
appears.
8. Type the name of the policy that should govern the annotation in the Policy box.
Or
Click the Policy ellipsis button and select a policy using the Governing Policy Pattern
window that appears.
The results of your entries are displayed in the Annotation window, as shown in the
following example.

Chapter 11: Annotations and Attachments 249

Creating the After you enter all information for the annotation, you are ready to create it. To do so,
Annotation click Create on the Annotation window. Matrix Navigator opens the appropriate
application so you can create a file for the annotation. Refer to your application for
specific instructions.
After closing the application, Matrix Navigator enables you to add a description to the
annotation. Enter a description and click Modify to enter the information in the object and
close the window.
Then, Matrix Navigator:
• Checks the file into the annotation object.
• Connects the annotation object to the originally selected object (the object to be
annotated).
If you display the Navigator browser in Star mode for the object to which the annotation
was connected, you see the newly created annotation object.

250 Matrix Navigator Guide

 Controlling Revisions

You can create a revision of an object if revision privileges are available as defined by the
object’s policy. The original object with all associated characteristics is copied and
perhaps modified to create the revision. Note that the original object is not replaced.
For example, assume that an engineer has changed the material type for a part that has
already been released. In order to assure that this change is incorporated, the engineer
would raise the revision level for the part drawing.
The procedure to create a revision of an object is basically the same as creating a new
object. Refer to the description in Creating a New Object in Chapter 2.

Chapter 11: Annotations and Attachments 251

 Attaching Information to an Object

You can attach information to an object using different applications. For example,
depending on the application available, you might attach an audio comment, video,
photograph, or note. Available applications vary based on how your Administrator has
configured Matrix Navigator. This chapter leads you through a sample procedure for
attaching information to an object.
When you indicate that you want to attach information, Matrix Navigator:
• Creates an object of the selected information type (such as a note).
• Opens the appropriate application (such as word processing software) to create a file
for the attachment.
• Adds attributes (a description) to the attachment.
• Checks the file into the attachment object.
• Connects the attachment object to the originally selected object (the object to which
the information will be attached).
When you have completed the attachment procedure, Matrix Navigator displays an
attachment object with other objects on your browser. You can then use this object as you
would use any other business object.

Check with your Business or System Administrator to be sure that Attachment types,
relationships, and policies are defined.

Creating an To create an attachment object

Attachment Object 1. Select the object to which you will attach information.
2. Select Attachment from the Object>New menu.
The Attachment window is displayed.

A default name and vault may be displayed. The name is generated by Matrix
Navigator automatically. You can modify it and the vault, if desired.
3. Type the name of an attachment type in the Type box.
Or

252 Matrix Navigator Guide

 Click the Type ellipsis button and select an attachment type from the Type Chooser
that appears.

A default revision, relationship, and policy are entered automatically based on the
attachment type you selected. This information was associated with the type when the
Administrator created it.
4. Change the default name by typing a new name in the Name box.
5. Change the revision by typing a new one in the Revision box.
6. Type the name of the relationship between the attachment and the object to which the
attachment will be connected in the Relationship box.
Or
Click the Relationship ellipsis button and select a relationship using the Relationship
Pattern window that appears.
7. Type the name of the vault that will contain the attachment in the Vault box.
Or
Click the Vault ellipsis button and select a vault from the Vault Pattern window that
appears.
8. Type the name of the policy that will govern the attachment in the Policy box.
Or
Click the Policy ellipsis button and select a policy using the Governing Policy Pattern
window that appears.
The results of your entries are shown in the Attachment box.

Chapter 11: Annotations and Attachments 253

Creating the After you enter all information for the attachment, you are ready to create it. To do so,
Attachment click Create on the Attachment window. Matrix Navigator opens the appropriate
application so you can create a file for the attachment. Refer to your application for
specific instructions.
After closing the application, Matrix Navigator lets you add a description to the
attachment. Enter a description and click Modify to enter the information in the object and
close the window.
Then, Matrix Navigator:
• Checks the file in to the attachment object.
• Connects the attachment object to the originally selected object (the object to which
the information is attached).
If you display the Navigator browser in Star mode for the object to which the attachment
was connected, you see the newly created attachment object.

254 Matrix Navigator Guide

 12
Working With Workflows

Working With Workflows

Workflows are fully implemented in the desktop version of Matrix Navigator only. In the
Web version, users can only work with tasks they are assigned, which includes checking
for tasks, accepting tasks, editing task attributes, and completing tasks (all these
procedures are initiated from the IconMail window).

Workflow is concerned with the automation of procedures, where documents, information

and tasks are passed among participants according to a defined set of rules to achieve or
contribute to an overall business goal.
In the Business Modeler application, Business Administrators create workflow process
definitions. The process definition contains a set of activities (tasks) connected with
intelligent links that allow branching within the process.
In Matrix Navigator, users create and start Workflow instances, based on processes. A
workflow instance is the representation of a single enactment of a process; it consists of
workflow activities, also known as tasks.
When workflow is launched, the workflow instance and all the constituent activity
instances are automatically created. The task assignments are dropped off in each user’s
IconMail inbox. A user completes the task and communicates the status of that task
assignment to the workflow system. Based on the rules defined in the process definition,

255
 the workflow system routes the next task to the next task performer(s), until the workflow
is completed. Workflow owners are allowed to abort or suspend a workflow instance.

256 Matrix Navigator Guide

 Creating a Workflow Instance

Workflow instances are based on workflow processes, which are created by Business
Administrators within Business Modeler. Like business objects, workflows are stored in
vaults, have an owner, and may have attributes. Workflows are referred to by a
combination of the process name and workflow instance name.
Workflow instances can be created within Matrix Navigator by any user. The user who
creates a workflow instance becomes the owner of that instance and is the only one who
can view the workflow instance and constituent activity instances from the Matrix
Navigator browser.

Workflow instances cannot be created from the Web version of Matrix Navigator.

To create a workflow instance

1. From Matrix Navigator, click or choose Workflows from the Object menu. The
Workflows window opens:

If you have not created any other workflows, the workflow list is blank. Otherwise
any workflows that you previously created are listed.

2. From the Workflows window, click or choose New from the Workflow menu
.

Chapter 12: Working With Workflows 257

 In the Process box, type the name of an existing process on which the workflow

instance will be based, or click to select a process from the Process Chooser.
In the Name box, assign a name for the new workflow instance. Workflow instance
names must be unique in Matrix Navigator federated databases, that is, across vaults.
The workflow name is limited to 127 characters.

In the Vault box, type the name of an existing vault, or click to select a vault
from the Vault Chooser.
3. Click Create to create the new workflow instance. The new workflow is listed in the
Workflows window.
ENOVIA Live Collaboration runs a validation check as it creates a workflow instance.
The validation check gives appropriate error messages if the process on which the
workflow is based is not valid.

258 Matrix Navigator Guide

 Starting a Workflow

Workflows can be started only by the owner of the workflow instance. When the
workflow is started, it immediately sends out task assignments for the first activity in the
workflow. The status on the Workflows window reports “Started.”
There are two methods to start a workflow:
• The workflow starts automatically as soon as the workflow instance is created if the
Auto Start check box was enabled when the workflow process was designed. See
“Creating a Workflow Process Definition” in the Business Modeler Guide for
information.
• If the Auto Start check box was not enabled, you can start a workflow manually.

Workflows cannot be started from the Web version of Matrix Navigator.

To start a workflow

1. Click or choose Workflows from the Object menu in the Matrix Navigator
browser. The Workflows window opens and lists the workflows you own:

The left column shows the name of the workflow instance and above it, the name of
the process on which it is based. The right column shows the current status of the
workflow. If the workflow has not yet been started, the right column is blank.
2. Select the workflow that you want to start.

3. Click or choose Start from the Workflow menu. You can also right-click on the
workflow itself and then select Start from the shortcut menu.

Chapter 12: Working With Workflows 259

 Working with Tasks

This section describes how to respond to tasks that are sent to you once a workflow is
started.

All the procedures in this section apply to the desktop and Web versions of Matrix
Navigator.

Checking IconMail When a workflow instance is started, the first activity of the workflow is sent as a task to
for Tasks the IconMail inbox(es) of the assigned user(s). As users complete each task, the workflow
sends new interactive tasks to users’ inboxes. Each user can check tasks included in his/
her IconMail.

To check IconMail for workflow tasks

1. From the Matrix Navigator browser, click or choose Mailbox from the Object
menu.

You can identify workflow tasks in the IconMail-inbox by the task icon in the
left column of the inbox:

The From column contains the name of the workflow instance owner and the Subject
column contains the Activity (Task) Name.

If you receive new mail or tasks while your inbox is open, they do not automatically
appear in the inbox list. You must first close the IconMail-inbox and reopen it to see new
messages and tasks.

2. To see details on the task, double-click the task icon.

The Activity window opens, showing the Basics tab.

260 Matrix Navigator Guide

 The Name of the task is shown, along with a Description and the Assignee, the user
to whom the task is assigned.
Also shown is the Priority (Urgent, High, Medium, Low), the Duration (the
estimated number of days the task is allocated) and the Rate (the percentage of time
per day allocated to the task).
The values for these fields are defined in Business Modeler and cannot be edited in
Matrix Navigator.
3. Click the Instructions tab to see what details have been provided about the task.

The instructions for the task are defined in Business Modeler and cannot edited in
Matrix Navigator.
4. To see attributes associated with the activity, click the Attributes tab. The task owner
can modify task attributes. See Editing Task Attributes for details.
5. To see attachments associated with the activity, click the Attachments tab.
Double-click attached objects to open for them viewing. The task owner can also add
new attachments. See Attaching Business Objects to the Workflow for details.

Chapter 12: Working With Workflows 261

Accepting Tasks If a task is assigned to a group or role, one person must accept the task. Then Matrix
Navigator will automatically inform the rest of the group that the task is no longer
pending.

To accept a task
1. To accept the task, click the Accept check box in the lower left corner of the Activity
window.

2. Click OK. The task is removed from all other assigned users’ inboxes and they
receive an IconMail message stating that the task has been rescinded. Use Cancel to
close the Activity without accepting it.
After you accept the task and click OK, when you reopen the Activity window, the check
box label reads Complete rather than Accept. When you have finished the task, you must
mark it as complete in order to advance the workflow and remove the Activity from your
inbox. See Completing Tasks for more information.

262 Matrix Navigator Guide

Editing Task While you are working on a task, you may need to edit the task attributes. For example, if
Attributes you are the owner of the Order Materials task, you may need to type in attributes such as
height, diameter, cost, etc.

To edit task attributes

1. From the Activity window, click the Attributes tab
.

All attributes defined for the current workflow, both local (activity) and global
(workflow), are listed.
2. Modify attributes as necessary.
3. Click OK.

Attaching If you have a file associated with your activity, you can check in the file to the appropriate
Business Objects business object and attach the business object to the workflow. For example, if your task
to the Workflow in the workflow is to supply the blueprint used to create a part, you would check the
blueprint into the business object for that particular part and then attach the business
object to the workflow. Attachments can be removed, added, and viewed, as described in
this section.

To remove attachments
1. From the Activity window click the Attachments tab.

Chapter 12: Working With Workflows 263

 2. Select an attachment and click Remove.

To add attachments
1. From the Attachments tab of the Activity window, click Add.
The Attachment Chooser opens:

2. Specify a Type or click to select a type from the standard Matrix Navigator
Type Chooser.
3. Type in a Name and Revision.

4. Specify a Vault or click to select a vault from the Vault Chooser.

5. Click OK.

If the business object does not exist, you will receive an error message stating that fact. Be
sure the spelling is correct; Matrix Navigator is case-sensitive.

To view attachments
1. Select one or more objects from the Attachments tab of the Activity window.
2. Click Browse.

264 Matrix Navigator Guide

 A new window opens, displaying the selected objects. You can then save the objects
as a set, view files checked in to the object, view basics and attributes, etc. See
Creating a New Object in Chapter 2 for details.

Completing Tasks When you complete a task, you must mark the task as complete so the workflow can
proceed to the next activity.

To mark a task as completed

1. From the Activity window, check Complete in the lower left corner.

2. Click OK.
Matrix Navigator marks the task as completed, updates the workflow, and automatically
moves on to the next activity or subprocess and makes new task assignments. Completed
activities are removed from users’ inboxes.

If you don’t mark the task as completed, the workflow cannot proceed.

Chapter 12: Working With Workflows 265

 Managing Workflows

The owner of the workflow instance can make changes to the workflow instance. The
workflow owner is the only one who can start, stop, suspend, and resume the overall
workflow.
For example, if an order is expected to be shipped at a specific date and the process to
fulfill the order takes three months, the workflow owner must decide when to start the
workflow. If there is an unforeseen delay during that time, the workflow owner can
suspend the workflow for a certain period of time. The owner then has the responsibility to
resume the workflow when it is appropriate. If a problem occurs and the order cannot or
need not be completed at all, the workflow can be stopped.
Initially, the owner of the workflow is the person who created it. But that user can then
reassign the workflow to someone else, who then becomes the new owner.
A workflow contains a set of tasks, usually assigned to different users. In addition to
managing the workflow as a whole, the workflow owner also has control over reassigning,
suspending, resuming, rescinding and overriding the individual tasks. See Managing
Workflow Tasks.

The procedures in this section cannot be performed using Web version of Matrix
Navigator.

Reassigning the Only the workflow owner can reassign the workflow to a different user. Initially, the
Workflow owner of the workflow is the person who creates it. That person can then reassign the
workflow to a new owner. For example, you may have one person in the group who
creates workflow instances, and then reassigns them to other users to manage.

To reassign a workflow

1. From the Matrix Navigator browser, click or choose Workflows from the
Object menu. The Workflows window opens, showing all workflow instances that
you have created:

266 Matrix Navigator Guide

 2. Select the workflow instance you want to reassign.
3. Choose Reassign from the Workflow menu. The Reassign-Workflow window opens:

4. In the To box, type the name of the user to whom the workflow should be reassigned,

or click to select a name from the User Chooser.

5. Click Reassign.
When you reassign a workflow, the new owner becomes the manager of the workflow
instance with all rights that the original owner had to control the workflow and also all
activity instances included in the workflow.

Changing Only the owner of a workflow can make changes to the workflow status. The workflow
Workflow Status owner can choose any of the following commands to change the workflow status: Start,
Stop, Suspend or Resume, as described in the following sections.

Chapter 12: Working With Workflows 267

 To view workflows that you own, click or choose Workflows from the Object menu
in the Matrix Navigator browser. The Workflows window opens:

For information on starting a workflow, see Starting a Workflow.

To stop a workflow
1. From the Workflows window, select the workflow that you want to stop.

2. Click or choose Stop from the Workflow menu or right-click on the workflow
and choose Stop from the shortcut menu. The workflow status changes to “Stopped.”
If any users are already working on tasks within the workflow, the tasks are rescinded
and users receive an IconMail message.

To suspend a workflow
A suspended workflow is temporarily stopped until the workflow owner issues the
Resume command.
1. From the Workflows window, select the workflow that you want to suspend. When a
workflow is suspended, no new tasks are assigned until the workflow is resumed.
(However, tasks that have already been assigned are not rescinded.)

2. Click or choose Suspend from the Workflow menu or right-click on the

workflow and choose Suspend from the shortcut menu. In the Status field, the word
“Started” is replaced with “Suspended.”
A workflow is automatically suspended in the following cases:
• If a problem is encountered within the workflow (for example, a bug in a trigger
program) that prevents the workflow from continuing.
• An OR-split does not have a valid path to follow (that is, none of the transition
expressions are satisfied).

To resume a workflow
1. From the Workflows window, select a suspended workflow that you want to resume.

268 Matrix Navigator Guide

 2. Click or choose Resume from the Workflow menu or right-click on the
workflow and choose Resume from the shortcut menu. When a workflow is resumed,
the workflow engine checks which tasks have been completed since the workflow
was suspended and if necessary, proceeds to the next activity and assigns new tasks.
In the Status field, the word “Suspended” is replaced with “Started.”

Deleting a If the workflow is no longer needed, the workflow owner can delete it. Only workflows
Workflow Instance that are stopped or “Finished” can be deleted.

To delete a workflow instance

1. From the Workflows window, select the workflow that you want to delete.
2. Choose Delete from the Workflow menu.
The workflow instance, including all constituent activity instances, is deleted from
the database. All tasks are removed from workflow participants’ IconMail inboxes,
and workflow participants receive a message that the task has been rescinded.

Chapter 12: Working With Workflows 269

 Managing Workflow Tasks

The owner of the workflow instance can make changes to the individual tasks included in
the workflow instance. The owner can reassign tasks to different users or rescind tasks
from users. The owner can also change task status to override, suspend, and resume.
The task owner can make changes to the attributes and attachments for a task, but the
workflow owner can also make these changes.

The procedures in this section cannot be performed using the Web version of Matrix
Navigator.

To manage workflow tasks

1. From the Matrix Navigator browser, click or choose Workflows from the
Object menu. The Workflows window opens, showing all workflow instances that
you own:

2. Double-click the workflow instance that contains a task you want to work with. The
Workflow activities window opens.

Activities are specified by their process name on the first line, and the workflow
instance name followed by the activity name on the second line.

270 Matrix Navigator Guide

 The Status field is blank until the activity is started by the workflow engine as a result
of starting the workflow or completing the previous activity. It displays “Started” if
the activity is started or resumed. It also reflects when the activity is Suspended or
Overridden.
The Owner field is blank until the owner is resolved, which occurs when a user
accepts the task.
The Assignee field shows which user (person, group, role or association) have been
assigned the task in the process definition only. Assignees added by workflow owners
currently may only be shown in MQL.
The functions that may be performed on individual workflows are described in the
sections that follow.

Reassigning Only the workflow owner can reassign a task to additional user(s). Taskmail for the
Workflow Tasks activity that is reassigned is sent to all users that were the original Assignees in the process
definition, plus any additional users specified during reassignment. However, the
ownership of the activity is not resolved until someone accepts the task.
You can add assignees to activities before the workflow has been started, while it is
started, or by stopping (and restarting) it. (You cannot add assignees to activities when the
workflow has been suspended or stopped.) When you restart a workflow, it returns to the
beginning of the process.

To add assignees to tasks in Matrix Navigator

1. From the Workflow activities window, select the workflow activity you want to
assign.

2. Choose Reassign from the Workflow menu. The Reassign-Activity window opens:

Chapter 12: Working With Workflows 271

 3. In the To box, type the name of the user(s) to whom the task should be reassigned, or

click to select the name(s) from the User Chooser.

4. Click Reassign.
The additional users are added to the list of assignees and receive taskmail when the
activity is started.

Rescinding a Task In some cases, you may need to rescind a task. When you rescind a task, you take the task
away from the assignee without immediately reassigning it to someone else. Perhaps a
person has left the company and you are waiting for a replacement, or you have not yet
decided to whom the tasks should be reassigned.

To rescind a task
1. From the Workflow activities window, select the activity you want to rescind.

272 Matrix Navigator Guide

 2. Click or choose Rescind from the Workflow menu or right-click on the
workflow task and choose Rescind from the shortcut menu.
Tasks are automatically rescinded by the workflow engine in the following cases:
• When a person accepts a task that has been assigned to multiple users (a group, role or
association), tasks are rescinded from other assignees.
• When you reassign a task, the task is rescinded from the previous assignee.

• When the workflow owner clicks or chooses Stop from the Workflow menu in
the Workflows window, tasks are rescinded from all participants in the workflow.
• When the workflow owner chooses Delete from the Workflow menu in the
Workflows window, tasks are rescinded from all participants in the workflow.
• When the workflow includes an OR-split following parallel tasks, the first task that
completes causes the other parallel tasks to be automatically rescinded.
• Completed tasks are automatically removed by the workflow engine.
• Tasks that have been overridden are rescinded from the assignee’s inbox.

Changing Task The workflow owner can choose any of the following commands to change the task status:
Status Suspend, Resume, Rescind, and Override, as described in the following sections.

To override a workflow task

To override a task means to skip the task in order to move forward with the next activity in
the workflow. You may decide that the task is not essential to the overall process, or there
may be some error that causes the workflow to auto-suspend.
1. From the Workflow activities window, select the task you want to override.

2. Choose Override from the Workflow menu or right-click on the workflow task and
choose Override from the shortcut menu. The workflow continues with the next task.

Chapter 12: Working With Workflows 273

 To suspend a workflow task
1. From the Workflow activities window, select the task that you want to suspend.

2. Click or choose Suspend from the Workflow menu or right-click on the

workflow task and choose Suspend from the shortcut menu.

To resume a workflow task

1. From the Workflow activities window, select a suspended task that you want to
resume.

2. Click or choose Resume from the Workflow menu or right-click on the

workflow task and choose Resume from the shortcut menu.

Modifying Task Both the workflow owner and the task owner have the ability to make changes to the
Attributes and attributes and attachments of a task. The workflow owner may want to change the number
Attachments of parts that should be ordered, or add a document that would help the task owner to
complete the task.
Task owners access the Activity window from IconMail. The workflow owner accesses
the same window from the Workflow activities window.

To modify task attributes or attachments

1. From the Workflow activities window, double-click the task for which you want to
modify attributes or attachments. The Activity window opens, showing the Basics
tab.

This is the same window the task owner sees when viewing the task from IconMail.
2. Click on the Attributes or Attachments tabs to make changes. For detailed
information, see Editing Task Attributes and Attaching Business Objects to the
Workflow for details.

274 Matrix Navigator Guide

 13
Generating Reports

Generating Reports

A report is an organized presentation of the selected contents of a business object. You

can generate a report about selected objects using one of the report formats designed by
your Administrator. The format determines:
• The type of information that is reported.
For example, you might generate a Material Properties report for several assemblies.
Based on the report definition, Matrix Navigator collects certain types of information
about the objects: name, description, material type, and target and actual costs.
The report might also reflect lifecycle approvals.
• The layout of the report.
The Material Properties report might list the information in five columns.
The report that you generate is created as a new object. You can find, view, edit, and print
it just as you would with any other business object. In addition, a text file of the
information about the selected objects, formatted as specified in the layout of the report, is
checked into the Report object.

Reports are available in the desktop version of Matrix Navigator and are not available in
the Web version.

275
 Creating a Report

To define a new report for selected objects

1. Select the objects for which you want to generate a report.
2. Select Report from the Object>New menu.
The New Report window is displayed.
.

The current vault is displayed by default.

3. Type the name of the defined report in the Report box.
Or
Click the Report ellipsis button and select a report using the Report Pattern window
that appears.
The Report box identifies which defined report style and content you wish to produce
about the selected objects.
4. Enter the object type to create for the report in the Type box.
Or
Click the Type ellipsis button and select a type from the Type Chooser that appears.
The Type indicates what object type will be created when the report is generated. For
example, you may have Engineering Reports, Accounting Reports, and Management
Reports.
5. Type a unique name for the report object in the Name box.
When the object icon is displayed on your screen, the object name that you specify
appears beneath the type. The current date and time are entered by default but can be
changed if desired.
6. Type a unique revision for the object in the Revision box.
The Revision defaults to 1 unless otherwise specified in the policy.
7. Type the name of the vault that will contain the report in the Vault box.
Or

276 Matrix Navigator Guide

 Click the Vault ellipsis button and select a vault from the Vault Pattern window that
appears.
8. Type the name of the policy that will govern the report in the Policy box.
Or
Click the Policy ellipsis button and select a policy using the Governing Policy Pattern
window that appears.
The results of your entries are displayed in the New Report window, as shown in the
following example:

9. Click Create to create the report for the selected objects.

The Attributes window opens.

10. Type a description and other attributes, if any, for the report and click Modify.
The report is generated as a new object and its icon (based on the type indicated) is
displayed in the work area.

Chapter 13: Generating Reports 277

 Viewing a Report

You can work with a report object (based on the governing policy) just as you would any
other type of object. For example, you might want to look at the report.

To view a report
1. Select the report object.
2. Select View from the Object > Open menu.
If the object policy permits viewing, the report is opened for you to view.
3. Exit the viewing application as normal.

278 Matrix Navigator Guide

Index

A activity 261
About option 36 creating file 254
access creating object 252
delegating for object 72 defined 252
displaying your privileges for state 231 modifying task 274
granting 72 workflow 263
reviewing signature 229 attribute
revoking 74 activity 261
activating assigning values 48
cue 145 changing for object 64
filter 145 comparing value of 107
table 145 defined ranges 140
tip 145 displaying relationship attributes 195
visual 145 editing task 263
vs. turning on visuals 144 modifying relationship attributes 195
activity modifying task 274
attachments 261 multi-line 140
attributes 261 reviewing an object’s 64
description 261 auto promote 232
name 261 Autosize Heading 139, 140
priority 261
actual date 231 B
advanced query Back button 184
performing 90 basics
All view of a file 203
no view turned on 146 of a relationship 192
turning on 167 of an object 60, 62
annotation between operator 92
creating file 250 branching 227
creating object 248 browsers
defined 248 Details mode 182
appending files Indented mode 182
setting preference for 24 Matrix 26
when checking in 211, 213 Navigator 182
attachment

279
 preferences 23 unlocking 221
printing 53 vault 42
Star mode 182 viewing all properties for 59
business object viewing historical information 67
annotating 248 viewing revisions 64
associating with ImageIcon 49 buttons, showing and hiding 25
attachment 252
attributes 64
basic information for 60, 62
C
changing revision chain 64 cardinality 175
checking in files 210 cell
checking out files 200, 210 defining 137, 140
cloning 46 editing data 56
connect accesses 173 changing
connecting 173 basic information for object 62
copying 77 relationship type 195
creating 39, 43 revision chain 64
cutting 77 checking in files
defining attributes 48 defaults 24
delegating access to 72 how to 210
deleting 76 overview 199
demoting 233 preferences 25
disconnecting 198 Web version 210
displaying in table 55 checking out files
double-clicking 209 copied to destination 200
errors on creation 44 default path 218
errors on finding 81 defaults 24
files checked in 202 how to 214
finding 82, 97 overview 199
formats for 202 preferences 25
granting access to 72 vs. opening 201
icon 40 clearing query fields 111
lifecycle 223 clone
loading from set 157 defined 39
locking 220 different from revision 45
name 41 cloning
pasting 78 business object 46
performing a query for 97 cue 143
policy 43 filter 143
printing files 53 table 143
promoting 232 tip 143
reassigning ownership 70 toolset 143
relationships 171 view 166
removing from set 158 visual 143
revision 251 column
revision sequence 42 Also see table and cell.
revoking access to 74 content 136
routing 70, 239 editable 137
states 225 heading 137
tip for 30, 149 width 137
title for 30, 149 completion warnings 234
type 40 connecting objects

280 Matrix Navigator Guide

 candidate object 174 preferences 23
connect bar 25 tool bars 25
connect option 173 warning messages 24
direction 173 defined ranges 140
drop connect 176 defining
overview 171 where clause 91
connection. See relationship. delegating access 72
const 107 deleting
context business object 76
changing user password 22 checked in file 219
setting context 21 cue 152
copying a business object 77 files when checking in 24
copying files. See checking in and checking out filter 152
files. IconMail 244
creating query 113
annotation file 250 set 159
annotation object 248 table 152
attachment file 254 tip 152
attachment object 252 view 166
business objects 39 visual 152
filter 122 workflow 269
reports 276 demoting business objects 233
revision 47, 251 description
set 154 activity 261
tables 136 task 261
tip 129 viewing for object 60, 62
toolset 132 desktop version
view 163 checking in files 212
workflow instance 257 starting 20
cue Details browser mode
activating 145 choosing 55
cloning 143 displays table 136, 187
deleting 152 must have table to use 56
editing 142 scrolling in tables 56
order 126 setting preference for 23
viewing 142 disabling promotion 232
cutting a business object 77 disconnecting objects 198
double-clicking objects 209
drop connect
D connecting objects 176
date default relationship 23
actual 231 replacing objects 179
object was created 60
object was modified 60
scheduled 230 E
default Edit menu
browser view modes 23 copy 77
checkout path 24, 218 cut 77
drop relationship 23 options summarized 30
file checkin preferences 24 paste 78
file checkout preferences 24 editable
open for setting 23 and other cell settings 140

Index 281
 column 137 F
defining column as 139 file
editing Also see initialization file.
business object 55 basics 203
checked in files 207 checking in 210
cue 142 checking out 200, 214
filter 142 default path for checkin/checkout 25, 218
table 142 deleting checked in 219
table data 55 formats 202
tip 142 host 203
toolset 142 listing checked in 202
visual 142 locking 220
electronic signature 227 name 203
e-mail 237 name of locker 203
Also see IconMail. opening
enabling promotion 232 for edit 207
ending a session 37 for printing 208
enovia.ini for viewing 205
Live Collaboration Server multiple files 209
find limit 97 prerequisites for 205
restrict expand variable 186 tips for 209
restrict expand 186 vs. checking out 201
equal operator 92 path 203
erasing query criteria 111 preferences 24
error printing 53
invalid date/time 106 size 203
error message unlocking 221
invalid date/time 106 file content, query by 87
errors file metadata, query by 88
creating business object 44 file path 25
finding business object 81 Files menu 33
in visuals 44, 81 filter
evaluating activating 145
reserved words and selectables 107 cloning 143
executing creating 122
method 134 deleting 152
program 134 editing 142
exiting Matrix Navigator 37 filter bar 25
expand option turning on multiple 146
query 97 viewing 142
with wildcards 97 filter bar
expression changing a saved filter 147
applies to object 137 described 26
applies to relationship 137 showing and hiding 25
defining for table 138 using 147
in table column 136 find
expressions Also see query.
unexpected results 107 initiating 80
using const for exact equal 107 latest revision 84
limiting results 97
objects 82, 90

282 Matrix Navigator Guide

 produces errors 81 viewing for object 60
Where clause 90 IconMail
find like query accessing files 243
constraints 115 deleting 244
initiating 114 distributing manually 237
memory 116 forwarding 244
findlimit preference 97 printing messages 243
float revision rule 45 reading 241
Formats browser 202 receiving automatically 245
formats, file formats for object 202 receiving manually 241
forms replying 244
definition 68 routing an object 70
print 69 sending automatically 245
view and edit 68 sending manually 237
forwarding an IconMail message 244 task 260
freezing relationship 196 image
file format required for Web 40
gif format required 50
G grabbing 49
gif image file importing 50
gif89a for Web version 40 ImageIcon
required format for icons 50 associating with object 49
grabbing an image 49 defined 49
grantee viewing for object 60
accesses 73 importing images 50
person or group only 73 Indented browser mode
viewing for object 60 described 182
granting access 72 expanding the structure 185
greater than equal operator 92 setting preference for 23
greater than operator 92 using 184
Info dialog
H defined 57
displaying 57
heading
using 58
automatic 139
initialization file
autosize 140
default checkout path 218
custom 139
findlimit 97
specifying for table column 137
MX_BACKGROUND_OPEN 209
width 139
MX_CHECK_MAIL 241
Help menu 34
MX_RESTRICT_EXPAND 186
help with Matrix 35
session preferences written to 23
history 67
instructions for workflow 261
and clones 45
Internet Explorer
must run while running Matrix Navigator 20
I starting Matrix Navigator from 20
icon
associating with object 49 K
for object type 40
keyword
gif format required 50
in expressions 107
preferences 23
in queries 107
setting preference for 23

Index 283
L MX_RESTRICT_EXPAND 186
less than equal operator 92
less than operator 92 N
lifecycle name
completion warnings 234 changing for object 62
demoting 233 defining for object 41
IconMail 245 query by 83
overview 223 navigating with There and Back 184
promoting 232 navigation preferences 23
scheduled dates 230 Navigator browser
limiting query results 97 activating 183
loading saved set 157 modes 182
locker none revision rule 45
viewing for object 60 non-SQL convertible fields 101
viewing name of 203 not equal operator 92
locking a business object not match case operator 92
how to 220 not match operator 92
setting preference for 25

O
M Object Inspector 59
match case operator 92 Object menu 28
match operator 92 object tip. See tip.
Matrix Navigaor 37 object. See business object.
Matrix Navigator objects
introduction to 19 find 90
software version 36 Open for 24
starting opening
desktop version 20 file
Web version 20 for editing 207
matrix.ini for printing 208
Also see initialization file. for viewing 205
findlimit 97 preferences 23
memory prerequisites 205
controlling requirements for queries 101 tips for 209
in query features 116 multiple files 209
menu bar 27 preference 24
message bar 27 set 156
metadata, query by 88 origination date 60, 62
method overriding
executing 134 promotion 232
toolset 132 workflow task 273
modeling considerations 108 overwriting files
modified date 60, 62 setting preference for 25
Mozilla when checking out 216, 217, 219
starting Matrix Navigator from 20 owner
multi-line setting 140 query by 84
MX_BACKGROUND_OPEN 209 reassigning 70
MX_BOS_EXPAND_LIMIT 186 routing 70
MX_BOS_FIND_LIMIT 97 viewing for object 60
MX_CHECK_MAIL 241

284 Matrix Navigator Guide

P Q
password query
changing 22 advanced 90
setting context 21 Also see find.
pasting a business object 78 always use only SQL convertible fields 101
path of checked in file 203 clearing fields 111
policy date/time 106
changing for object 62 deleting 113
defining for policy 43 file content 87
viewing for object 60 file metadata 88
preferences find like 114
find limit 97 initiating 80
for files 24 keywords 107
for toolbars 25 memory of previous 116
for viewing 23 memory requirements 101
general 23 modeling considerations 108
multiple files open 209 non-SQL convertible fields 101
setting 23 object name 83
written to files 23 object owner 84
prerequisites for opening files 205 object revision 84
printing object type 82
checked in files 208 optimizing 99, 101
current screen 53 relational operators 92
files for an object 53 reserved words 107
form 69 saving criteria 111
from a browser 53 select expressions 107
IconMail messages 243 select fields 99
table 57 simple 82
priority for activity 261 SQL convertible fields 99
privilege strategies 99
access 231 unexpected results 107
disabling promotion 232 using object properties 90
enabling promotion 232 using recent criteria 112
overriding promotion 232 using reserved words 107
program using saved criteria 112
executing 134 vault 86
toolset 132 wildcard characters 81
program bar 25
promoting business objects 232
promotion
R
disabling 232 ranges for attributes 140
enabling 232 reading IconMail 241
overriding 232 reassigning
properties workflow 266
query by 90 workflow task 271
viewing for business object 59 recent queries 112
properties file 23 relational operators in queries 92
Properties menu 32 relationship
properties. See properties file. attributes 194
cardinality 175
changing type 195

Index 285
 connect bar 25 S
connecting objects 171 saving
creating 173 query criteria 111
creating with drop connect 176 set 155
direction 173 scheduling states 230
disconnecting 198 search. See find and query.
freeze 196 select expressions
revision rules 45 in exact equal comparisons 107
table column applies to 137 in queries 107
thaw 197 select fields in queries 99
Relationships menu 33 sending IconMail 237
removing objects from set 158 session
replacing files ending 37
setting preference for 24 preferences
when checking in 211, 213 setting 23
replicate revision rule 45 written to file 23
replying to IconMail 244 starting
report desktop version 20
defined 275 Web version 20
defining 276 Session menu 34
viewing 278 set
rescinding workflow task 272 defined 153
reserved words in queries 107 defining 154
resuming deleting 159
workflow 268 loading objects 157
workflow task 274 opening 156
reviewing removing objects 158
basic information for object 60 saving 155
basic information for relationship 192 Set menu 27
signature access 229 setting context 21
signature comments 229 signature
revision applying 227
changing for object 62 branching 227
creating 47 requirement 227
defined 39 reviewing access 229
different from clone 45 reviewing comments 229
fixing a revision chain 65 signing off on a state 227
query by 84 simple query 82
rules 45 size of file 203
sequence 42 software version 36
warning 25 sorting data in table 57
revision sequence for object 42 SQL convertible fields 99
revoking granted access 74 Star browser mode 183
role bar starting Matrix
accessing 150 desktop version 20
described 26 Web version 20
purpose of 150 starting workflow 259
role-based visuals 150 state
routing object 239 branching 227
completion warnings 234
demoting 233

286 Matrix Navigator Guide

 disabling promotion 232 accepting 262
displaying access privileges 231 attachments 261
enabling promotion 232 attributes 261
overriding promotion 232 completing 265
overview 223 description 261
promoting 232 modifying attachments 274
scheduling 230 modifying attributes 274
signature access 229 name 261
signature comments 229 overriding 273
signature requirement 227 reassigning 271
signing off on 227 rescinding 272
transitioning 227 resuming 274
viewing 225 suspending 274
States browser workflow 260
demoting 233 thawing relationship 197
disabling promotion 232 There button 184
displaying access privileges 231 tip
enabling promotion 232 activating 145
overriding promotion 232 cloning 143
promoting 232 creating 129
tools and symbols 226 deleting 152
stopping a workflow 268 editing 142
suspending instead of object title 30, 149
workflow 268 View menu option 30, 149
workflow task 274 viewing 142
symbols in States browser 226 title for object 30, 149
tool
executing 134
T States browser 226
table toolbar
activating 145 described 27
Autosize Heading 140 preferences 25
cloning 143 Tools menu 34
column width 137 toolset
content 136 activating 145
creating 136, 137 cloning 143
deleting 152 creating 132
displaying 55 deleting 152
editable columns 137 editing 142
editing data 55, 56 missing tool 146
editing definition 142 viewing 142
expression 136, 138 toolset toolbar 27
heading 137, 139 transitioning
multi-line cells 140 defined 227
number of columns 136 signature requirement 227
printing 57 turning on visuals vs. activating 144
sorting 57 type
switching between two 56 changing for object 62
target for expressions 137 changing relationship 195
using 55 defining for object 40
viewing 142 query by 82
task

Index 287
U and views 146
unlocking business object cloning 143
how to 221 deleting 152
setting preference for 24 editing 142
user errors in 44, 81
setting context 21 produces error 44, 81
role-based 150
using 145
V using in views 161, 168
vault
changing for object 62
defining for object 42
W
finding objects in 86 Web version
query by 86 checking in files 210
viewing for object 60 errors 44, 81
version 36 prerequisites for opening files 205
view starting 20
and visuals 146 supported gif format 40
cloning 166 where clause
creating 163 defining 91
deleting 166 where expressions 91
determine available visuals 146 width
editing 165 of columns 137
errors in 44, 81 of table heading 139
file 206 wildcard
overview 161 and expand option 97
practical example 168 in queries 81
preferences 23 windows. See browsers.
turning off all 167 wizard
turning on 167 toolset 132
viewing 165 work area 27
View Manager 161 workflow
View menu accepting tasks 262
options summarized 30 attaching objects 263
turning on visuals 144 basics 261
viewing completing tasks 265
checked in files 205 creating instance 257
connection attributes 194 deleting 269
cue 142 editing task attributes 263
filter 142 IconMail tasks 260
object historical information 67 instructions 261
object revisions 64 reassigning 266
object states 225 resuming 268
report 278 starting 259
table 142 stopping 268
tip 142 suspending 268
toolset 142 task. See task.
visual 142
visuals
activating 145
activating vs. turning on 144

288 Matrix Navigator Guide