Technical Documentation General
Papyrus Software - Getting Started and News General Information
www.isis-papyrus.com getstartede V7.6 SP3 ISIS Papyrus Europe AG © ISIS Papyrus Europe AG 2012 - 2021 Papyrus Platz 1 All rights reserved. A-2345 Brunn/Gebirge Phone: +43-2236-27551 Reproduction in any form, in whole or in part, without express written Fax: +43-2236-21081 permission is prohibited. E-Mail: [email protected] Website: www.isis-papyrus.com getstartede V7.6 SP3 Last modification: chapter 11.11.1 on 2021/06/18 Product Support: Phone: +43 2236 27551-111 This document was created by the ISIS Papyrus Academy E-Mail: [email protected] using the Papyrus Communications and Business Process Platform. Contents
Contents
About this document ...... 16
1 Papyrus delivery - contents and naming conventions...... 17 1.1 Names of executables and product directories for Windows and UNIX ...... 17 1.2 Papyrus DVD contents and directory structure...... 19 1.2.1 Papyrus base installation...... 19 1.2.2 Papyrus Server directories...... 22 1.2.3 ISISCOMM directory structure...... 23 1.2.4 IPAS standalone directory structure...... 23 1.3 Names of z/OS product datasets ...... 24
2 Papyrus software installation and upgrade...... 25
3 Technical product documentation...... 27 3.1 General documents ...... 28 3.2 OverView AFP Designer...... 29 3.3 OverView Font Editor...... 30 3.4 OverView Image Editor ...... 30 3.5 Papyrus Analysis Toolkit ...... 30 3.6 Papyrus Capture Solution ...... 30 3.7 Papyrus Client...... 31 3.8 Papyrus Designer & DocEXEC...... 32 3.9 Papyrus Designer Capture...... 32 3.10 Papyrus Designer FreeForm ...... 32 3.11 Papyrus Font Converter...... 32 3.12 Papyrus Host...... 33 3.13 Papyrus ImageConverter...... 33 3.14 Papyrus Objects ...... 33 3.15 Papyrus PDF-in...... 35 3.16 Papyrus PostCalc ...... 35 3.17 Papyrus PostProcessing...... 36 3.18 Papyrus Printer Driver ...... 36 3.19 Papyrus Scan...... 36 3.20 Papyrus Server ...... 36 3.21 Papyrus WebArchive ...... 37
4 Operating systems...... 38
5 Support of web applications ...... 39 5.1 Papyrus business web applications overview...... 39 5.2 Plugin-free web applications ...... 40
6 Supported languages ...... 42
7 Important information for all DVDs...... 43 7.1 Important notes ...... 43 7.1.1 Operating system updates ...... 43 7.1.2 General ...... 43 7.2 General information...... 47
8 Main updates in V7.6...... 48 8.1 General changes...... 48 8.2 Papyrus Adaptive Case Management Solution ...... 48 8.2.1 Information relevant for business users...... 48 8.3 Papyrus Automated Document Factory Solution...... 48
getstartede V7.6 SP3 3/389 Contents
8.3.1 Information relevant for administrators and developers...... 48 8.3.2 Information relevant for business users...... 50 8.4 Papyrus Business Capture Solution ...... 50 8.4.1 Information relevant for administrators and developers...... 50 8.4.2 Information relevant for business users...... 51 8.5 Papyrus Business Correspondence Solution...... 52 8.5.1 Information relevant for administrators and developers...... 52 8.5.2 Information relevant for business users...... 54 8.6 Papyrus Mobile Solution - Heading ...... 56 8.6.1 Information relevant for administrators...... 57 8.7 Papyrus Reporting Solution ...... 57 8.7.1 Information relevant for administrators, developers and business users ...... 57 8.8 Papyrus Client Document Creation (Canvas) ...... 58 8.9 Papyrus Database Interfaces...... 58 8.10 Papyrus Designer, Papyrus DocEXEC...... 58 8.10.1 Information relevant for DOCDEF developers ...... 59 8.10.2 Information relevant for administrators ...... 63 8.11 Papyrus Objects (WebControl/WebRepository) ...... 64 8.11.1 Papyrus Adapters and Typemanagers...... 64 8.11.2 Papyrus Depot ...... 65 8.11.3 Papyrus EYE Widgets...... 65 8.11.4 Papyrus Objects System ...... 65 8.11.4.1 Information relevant for developers...... 65 8.11.4.2 Information relevant for administrators...... 66 8.11.5 Papyrus Ontology Framework ...... 66 8.11.6 Papyrus Query Language (PQL) ...... 66 8.11.6.1 Information relevant for developers...... 66 8.11.7 Papyrus Resource Collection ...... 67 8.11.8 Papyrus WebPortal...... 67 8.11.8.1 Information relevant for administrators...... 67 8.12 Papyrus Server ...... 67 8.12.1 AFP to PDF ...... 67 8.12.2 AFP to Thumbnail...... 68 8.12.3 E-mail...... 68 8.13 OverView Image Editor ...... 68
9 Updates in V7.6 SP1...... 69 9.1 Papyrus Designer, Papyrus DocEXEC...... 69 9.1.1 Information relevant for DOCDEF developers...... 69 9.1.2 Information relevant for administrators...... 69 9.2 Papyrus Objects (WebControl/WebRepository) ...... 69 9.2.1 Papyrus WebPortal...... 69 9.2.1.1 Information relevant for administrators ...... 69
10 Updates in V7.6 SP2...... 70 10.1 General changes...... 70 10.2 Papyrus Adaptive Case Management Solution ...... 70 10.2.1 Information relevant for business users ...... 70 10.3 Papyrus Analysis Toolkit ...... 71 10.4 Papyrus Automated Document Factory Solution...... 71 10.4.1 Information relevant for administrators and developers...... 71 10.4.2 Information relevant for business users ...... 71 10.5 Papyrus Business Capture Solution ...... 71 10.5.1 Information relevant for administrators and developers...... 71 10.5.2 Information relevant for business users ...... 72 10.6 Papyrus Business Correspondence Solution...... 73 10.6.1 Information relevant for business users ...... 73
getstartede V7.6 SP3 4/389 Contents
10.6.2 Information relevant for administrators and developers...... 74 10.7 Papyrus Reporting Solution ...... 74 10.7.1 Information relevant for administrators, developers and business users ...... 74 10.8 Papyrus Client...... 76 10.9 Papyrus Client AFP Viewer ...... 76 10.10 Papyrus Designer, Papyrus DocEXEC...... 76 10.10.1 Information relevant for DOCDEF developers ...... 76 10.11 Papyrus FontConverter...... 78 10.12 Papyrus Objects (WebControl/WebRepository)...... 78 10.12.1 Papyrus Depot ...... 78 10.12.2 Papyrus Objects System ...... 78 10.12.2.1 Information relevant for administrators...... 78 10.13 Papyrus PrinterDriver ...... 78 10.14 Papyrus Server ...... 79 10.14.1 AFP to PDF ...... 79
11 Updates in V7.6 SP3...... 80 11.1 General changes...... 80 11.2 Papyrus Adaptive Case Management Solution ...... 80 11.2.1 Information relevant for business users ...... 80 11.3 Papyrus Automated Document Factory Solution...... 80 11.3.1 Information relevant for administrators and developers...... 81 11.3.2 Information relevant for business users ...... 82 11.4 Papyrus Business Capture Solution ...... 82 11.4.1 Information relevant for administrators and developers...... 82 11.4.2 Information relevant for business users ...... 83 11.5 Papyrus Business Correspondence Solution...... 84 11.5.1 Information relevant for administrators and developers...... 85 11.5.2 Information relevant for business users ...... 85 11.6 Papyrus Mobile Solution...... 86 11.6.1 Information relevant for administrators ...... 86 11.7 Papyrus Reporting Solution ...... 86 11.7.1 Information relevant for business users ...... 86 11.8 Papyrus Client AFP Viewer ...... 87 11.9 Papyrus Designer, Papyrus DocEXEC...... 87 11.9.1 Information relevant for administrators ...... 88 11.9.2 Information relevant for DOCDEF developers ...... 89 11.10 Papyrus Objects for WebRepository/WebControl ...... 90 11.10.1 Papyrus Depot ...... 90 11.10.2 Papyrus Objects System ...... 90 11.10.2.1 Information relevant for administrators...... 91 11.11 Papyrus Server ...... 91 11.11.1 AFP to PDF ...... 91 11.11.2 PCL...... 92 11.12 OverView Image Editor ...... 92
12 Appendix: main updates in V7.5...... 93 12.1 Main updates in V7.5...... 93 12.1.1 General changes...... 93 12.1.2 OverView Image Editor ...... 94 12.1.3 Papyrus Adaptive Case Management Solution ...... 94 12.1.3.1 Information relevant for business users ...... 94 12.1.4 Papyrus Analysis Toolkit ...... 94 12.1.5 Papyrus Automated Document Factory Solution...... 95 12.1.5.1 Information relevant for business users ...... 95 12.1.5.2 Information relevant for administrators and developers ...... 96 12.1.6 Papyrus Business Capture Solution ...... 97
getstartede V7.6 SP3 5/389 Contents
12.1.6.1 Information relevant for administrators and developers ...... 98 12.1.6.2 Information relevant for business users ...... 99 12.1.7 Papyrus Business Correspondence Solution ...... 100 12.1.7.1 Information relevant for administrators and developers...... 100 12.1.7.2 Information relevant for business users...... 103 12.1.8 Papyrus Reporting Solution...... 104 12.1.8.1 Information relevant for administrators, developers and business users ...... 104 12.1.9 Papyrus Client Document Creation (Canvas)...... 105 12.1.10 Papyrus Designer, Papyrus DocEXEC ...... 106 12.1.10.1 Information relevant for DOCDEF developers ...... 106 12.1.10.2 Information relevant for administrators ...... 109 12.1.11 Papyrus Objects (WebControl/WebRepository)...... 109 12.1.11.1 Papyrus Objects System ...... 109 12.1.11.2 Papyrus Depot ...... 111 12.1.11.3 Papyrus Query Language (PQL) ...... 112 12.1.11.4 Papyrus Resource Collection ...... 112 12.1.11.5 Papyrus EYE Widgets...... 112 12.1.11.6 Papyrus WebPortal...... 112 12.1.12 Papyrus PrinterDriver ...... 113 12.1.13 Papyrus Server...... 113 12.1.13.1 AFP to PDF ...... 113 12.1.13.2 AFP to Text ...... 114 12.1.13.3 PCL...... 114 12.1.13.4 PostScript ...... 114 12.1.13.5 HTML...... 114 12.2 Updates in V7.5 SP1 ...... 114 12.2.1 General changes ...... 115 12.2.2 Papyrus Automated Document Factory Solution ...... 115 12.2.2.1 Information relevant for administrators and developers...... 115 12.2.2.2 Information relevant for business users...... 115 12.2.3 Papyrus Business Correspondence Solution ...... 116 12.2.3.1 Information relevant for administrators and developers...... 116 12.2.3.2 Information relevant for business users...... 116 12.2.4 Papyrus Business Document Capture Solution ...... 117 12.2.4.1 Information relevant for administrators and developers...... 117 12.2.4.2 Information relevant for business users...... 118 12.2.5 Papyrus Reporting Solution...... 120 12.2.5.1 Information relevant for business users...... 120 12.2.6 Papyrus Client AFP Viewer...... 121 12.2.7 Papyrus Designer, Papyrus DocEXEC ...... 121 12.2.7.1 Information relevant for DOCDEF developers...... 122 12.2.8 Papyrus Objects (WebControl/WebRepository)...... 122 12.2.8.1 Papyrus Desktop ...... 123 12.2.8.2 Papyrus Objects system...... 123 12.2.8.3 Papyrus Query Language (PQL) ...... 123 12.2.8.4 Papyrus Depot ...... 123 12.2.8.5 Papyrus Adapters and Typemanagers...... 124 12.2.8.6 Papyrus EYE Widgets...... 124 12.2.8.7 Papyrus WebPortal...... 125 12.2.9 Papyrus Server...... 125 12.2.9.1 AFP to PDF ...... 125 12.2.9.2 IPDS ...... 125 12.2.9.3 E-Mail...... 125 12.3 Updates in V7.5 SP2 ...... 125 12.3.1 General changes ...... 126 12.3.2 Papyrus Automated Document Factory Solution ...... 126 12.3.2.1 Information relevant for administrators and developers...... 126
getstartede V7.6 SP3 6/389 Contents
12.3.2.2 Information relevant for business users...... 127 12.3.3 Papyrus Business Correspondence Solution ...... 127 12.3.3.1 Information relevant for business users...... 127 12.3.3.2 Information relevant for administrators and developers...... 128 12.3.4 Papyrus Business Document Capture Solution ...... 128 12.3.4.1 Information relevant for administrators and developers...... 129 12.3.4.2 Information relevant for business users...... 129 12.3.5 Papyrus Reporting Solution...... 130 12.3.5.1 Information relevant for administrators, developers and business users ...... 130 12.3.6 Papyrus Designer, Papyrus DocEXEC ...... 130 12.3.6.1 Information relevant for DOCDEF developers...... 130 12.3.7 Papyrus Objects (WebControl/WebRepository)...... 130 12.3.7.1 Papyrus Adapters and Typemanagers...... 131 12.3.7.2 Papyrus Depot ...... 131 12.3.7.3 Papyrus Resource Collection...... 132 12.3.8 Papyrus Postprocessing/Printpool ...... 132 12.3.8.1 Papyrus Tuner...... 132 12.3.9 Papyrus Server...... 132 12.3.9.1 IJPDS ...... 132
13 Appendix: main updates in V7.4 ...... 133 13.1 Main updates in V7.4...... 133 13.1.1 General changes ...... 133 13.1.2 Papyrus Adaptive Case Management Solution ...... 133 13.1.2.1 Information relevant for administrators and developers...... 133 13.1.2.2 Information relevant for business users...... 134 13.1.3 Papyrus Automated Document Factory Solution ...... 134 13.1.4 Papyrus Business Capture Solution...... 134 13.1.4.1 Information relevant for administrators and developers...... 135 13.1.4.2 Information relevant for business users...... 136 13.1.5 Papyrus Business Correspondence Solution ...... 138 13.1.5.1 Information relevant for administrators and developers...... 138 13.1.5.2 Information relevant for business users...... 140 13.1.6 Papyrus Reporting Solution...... 142 13.1.6.1 Information relevant for business users...... 142 13.1.7 Papyrus Analysis Toolkit...... 142 13.1.8 Papyrus Client Canvas...... 142 13.1.9 Papyrus Designer FixForm and Server FixForm...... 143 13.1.10 Papyrus Designer FreeForm and Server FreeForm ...... 144 13.1.11 Papyrus Designer, Papyrus DocEXEC ...... 144 13.1.11.1 Information relevant for DOCDEF developers ...... 144 13.1.11.2 Information relevant for administrators ...... 147 13.1.12 Papyrus FontConverter...... 147 13.1.13 Papyrus Objects (WebControl/WebRepository)...... 147 13.1.13.1 Papyrus Objects System ...... 148 13.1.13.2 Papyrus Depot ...... 148 13.1.13.3 Papyrus Adapters and Typemanagers...... 149 13.1.13.4 Papyrus EYE Widgets...... 149 13.1.14 Papyrus Printer Driver...... 150 13.1.15 Papyrus Server...... 150 13.1.15.1 AFP to PDF ...... 150 13.2 Updates in V7.4 SP1 ...... 150 13.2.1 General changes ...... 150 13.2.2 Papyrus Automated Document Factory Solution ...... 150 13.2.2.1 Information relevant for administrators and developers...... 151 13.2.2.2 Information relevant for business users...... 151 13.2.3 Papyrus Business Correspondence Solution ...... 151
getstartede V7.6 SP3 7/389 Contents
13.2.3.1 Information relevant for administrators and developers...... 151 13.2.3.2 Information relevant for business users...... 152 13.2.4 Papyrus Business Document Capture Solution ...... 153 13.2.4.1 Information relevant for administrators and developers...... 153 13.2.4.2 Information relevant for business users...... 155 13.2.5 Papyrus Mobile Solution ...... 155 13.2.5.1 Information relevant for administrators ...... 156 13.2.6 Papyrus Client Document Creation (Canvas)...... 156 13.2.7 Papyrus Designer, Papyrus DocEXEC ...... 156 13.2.7.1 Information relevant for administrators ...... 157 13.2.7.2 Information relevant for DOCDEF developers...... 157 13.2.8 Papyrus FontConverter...... 158 13.2.9 Papyrus Objects (WebControl/WebRepository)...... 158 13.2.9.1 Papyrus Objects system...... 158 13.2.9.2 Papyrus Query Language (PQL) ...... 159 13.2.9.3 Papyrus Depot ...... 160 13.2.9.4 Papyrus Adapters and Typemanagers...... 160 13.2.10 Papyrus Postprocessing/Printpool ...... 160 13.2.10.1 Papyrus Tuner...... 161 13.2.11 Papyrus Server...... 161 13.2.11.1 AFP to PDF ...... 161 13.2.11.2 PJL ...... 161 13.2.11.3 IPDS...... 161 13.2.12 OverView Font Editor ...... 161 13.3 Updates in V7.4 SP2 ...... 161 13.3.1 Papyrus Adaptive Case Management Solution ...... 162 13.3.1.1 Information relevant for business users...... 162
14 Appendix: main updates in V7.3 ...... 163 14.1 Main updates in V7.3...... 163 14.1.1 General changes ...... 163 14.1.2 ISIS Papyrus Product Authorization Service (IPAS) ...... 163 14.1.3 Papyrus Adaptive Case Management Solution ...... 163 14.1.4 Papyrus Automated Document Factory Solution ...... 163 14.1.4.1 Information relevant for administrators and developers...... 163 14.1.5 Papyrus Business Capture Solution...... 164 14.1.5.1 Information relevant for administrators and developers...... 164 14.1.5.2 Information relevant for business users...... 165 14.1.6 Papyrus Business Correspondence Solution ...... 166 14.1.6.1 Information relevant for Administrators and Developers ...... 166 14.1.6.2 Information relevant for Business Users ...... 168 14.1.7 Papyrus Client AFP Viewer...... 170 14.1.8 Papyrus Designer FixForm and Server FixForm...... 170 14.1.9 Papyrus Designer, Papyrus DocEXEC ...... 171 14.1.9.1 Information relevant for DOCDEF developers...... 171 14.1.10 Papyrus Objects (WebControl/WebRepository)...... 171 14.1.10.1 Papyrus Objects System ...... 172 14.1.10.2 Papyrus Depot ...... 172 14.1.10.3 Papyrus Adapters and Typemanagers...... 172 14.1.10.4 Papyrus Query Language (PQL) ...... 173 14.1.10.5 Papyrus Resource Collection...... 173 14.1.10.6 Papyrus EYE Widgets...... 173 14.1.11 Papyrus Server...... 173 14.1.11.1 AFP to PDF ...... 174 14.2 Updates in SP1...... 174 14.2.1 Papyrus Adaptive Case Management Solution ...... 174 14.2.2 Papyrus Automated Document Factory Solution ...... 174
getstartede V7.6 SP3 8/389 Contents
14.2.2.1 Information relevant for administrators and developers...... 175 14.2.2.2 Information relevant for business users...... 175 14.2.3 Papyrus Business Correspondence Solution ...... 175 14.2.3.1 Information relevant for administrators and developers...... 175 14.2.3.2 Information relevant for Business Users ...... 176 14.2.4 Papyrus Business Capture Solution...... 176 14.2.4.1 Information relevant for administrators and developers...... 176 14.2.4.2 Information relevant for business users...... 177 14.2.5 Papyrus Client Document Creation (Canvas)...... 178 14.2.6 Papyrus Designer, Papyrus DocEXEC ...... 178 14.2.6.1 Information relevant for administrators ...... 178 14.2.6.2 Information relevant for DOCDEF developers...... 178 14.2.7 Papyrus Objects (WebControl/WebRepository)...... 179 14.2.7.1 Papyrus Objects System ...... 179 14.2.7.2 Papyrus Depot ...... 179 14.2.7.3 Papyrus EYE Widgets...... 179 14.3 Updates in SP2...... 179 14.3.1 General changes ...... 179 14.3.2 Papyrus business Capture Solution...... 180 14.3.2.1 Information relevant for administrators and developers...... 180 14.3.2.2 Information relevant for business users...... 180 14.3.3 Papyrus Business Correspondence Solution ...... 181 14.3.3.1 Information relevant for Administrators and Developers ...... 181 14.3.3.2 Information relevant for Business Users ...... 181 14.3.4 Papyrus Client ...... 181 14.3.5 Papyrus Client AFP Viewer...... 181 14.3.6 Papyrus Designer, Papyrus DocEXEC ...... 181 14.3.6.1 Information relevant for administrators ...... 182 14.3.6.2 Information relevant for DOCDEF developers...... 182 14.3.7 Papyrus Objects (WebControl/WebRepository)...... 183 14.3.7.1 Papyrus EYE Widgets...... 183 14.3.8 Papyrus Server...... 183 14.3.8.1 Papyrus Server IPDS...... 183 14.3.8.2 Papyrus Server PCL...... 183 14.3.8.3 Papyrus Server PDF ...... 184
15 Appendix: main updates in V7.2 ...... 185 15.1 Main updates in V7.2...... 185 15.1.1 General changes ...... 185 15.1.1.1 Information about main updates before V7.2...... 185 15.1.1.2 New platform codes...... 185 15.1.1.3 New documents...... 185 15.1.2 Papyrus product installation ...... 185 15.1.3 ISIS Papyrus product authorization service ...... 186 15.1.4 Papyrus Adaptive Case Management Solution ...... 186 15.1.5 Papyrus Automated Document Factory Solution ...... 186 15.1.6 Papyrus Business Correspondence Solution ...... 187 15.1.6.1 Information relevant for Business Users ...... 187 15.1.6.2 Information relevant for Administrators and Developers ...... 188 15.1.7 Papyrus Business Capture Solution...... 189 15.1.7.1 Information relevant for business users...... 189 15.1.7.2 Information relevant for administrators and developers...... 190 15.1.8 Papyrus Client AFP Viewer...... 190 15.1.9 Papyrus Client Document Creation (Canvas)...... 190 15.1.10 Papyrus Designer, Papyrus DocEXEC ...... 190 15.1.10.1 Information relevant for administrators ...... 190 15.1.10.2 Information relevant for DOCDEF developers ...... 191
getstartede V7.6 SP3 9/389 Contents
15.1.11 Papyrus Designer FixForm and Server FixForm...... 192 15.1.12 Papyrus Word to Correspondence ...... 192 15.1.13 Papyrus Objects (WebControl/WebRepository)...... 192 15.1.13.1 Papyrus Objects System ...... 192 15.1.13.2 Papyrus Depot ...... 192 15.1.13.3 Papyrus Adapters and Typemanagers...... 192 15.1.13.4 Papyrus Query Language (PQL) ...... 193 15.1.13.5 Papyrus EYE Widgets...... 194 15.1.13.6 Papyrus WebPortal...... 194 15.1.14 Papyrus Server...... 194 15.1.14.1 AFP to PDF ...... 194 15.1.14.2 PDF-in ...... 194 15.1.14.3 SMTP/E-mail ...... 194 15.1.15 OverView AFP Designer ...... 194 15.1.16 Papyrus best practices ...... 194 15.1.16.1 Sample applications ...... 195 15.2 Updates in SP1...... 195 15.2.1 Papyrus Adaptive Case Management Solution ...... 195 15.2.1.1 Information relevant for administrators and developers...... 195 15.2.2 Papyrus Business Correspondence Solution ...... 195 15.2.3 Papyrus Designer, Papyrus DocEXEC ...... 195 15.2.4 Papyrus Objects (WebControl/WebRepository)...... 195 15.2.4.1 Papyrus EYE Widgets...... 196 15.3 Updates in SP2...... 196 15.3.1 Papyrus Adaptive Case Management Solution ...... 196 15.3.2 Papyrus Business Capture ...... 196 15.3.3 Papyrus Business Correspondence Solution ...... 196 15.3.4 Papyrus Client Document Creation (Canvas)...... 197 15.3.5 Papyrus Designer, Papyrus DocEXEC ...... 197 15.3.6 Papyrus Objects (WebControl/WebRepository)...... 197 15.3.6.1 Papyrus Objects System ...... 197
16 Appendix: main updates in V7.1 ...... 199 16.1 Main updates in V7.1 SP9...... 199 16.1.1 General changes ...... 199 16.1.1.1 New documents...... 199 16.1.1.2 Discontinued documents ...... 200 16.1.1.3 New platform codes...... 200 16.1.2 ISIS Papyrus Product Authorization Service...... 201 16.1.3 Papyrus Adaptive Case Management Solution ...... 202 16.1.4 Papyrus Automated Document Factory Solution ...... 202 16.1.5 Papyrus Business Correspondence Solution ...... 204 16.1.6 Papyrus Business Document Capture Solution ...... 220 16.1.6.1 Papyrus Client Capture ...... 220 16.1.6.2 Papyrus Scan...... 221 16.1.6.3 Papyrus Business Document Capture Solution...... 223 16.1.6.4 Papyrus Capture Categorizer ...... 224 16.1.7 Papyrus Reporting Solution...... 225 16.1.8 Papyrus Analysis Toolkit...... 225 16.1.9 Papyrus Client AFP Viewer...... 226 16.1.10 Papyrus Client ...... 227 16.1.11 Papyrus Client Document Creation (Canvas)...... 227 16.1.12 Papyrus Designer, Papyrus DocEXEC ...... 228 16.1.13 Papyrus Designer and Server - FixForm ...... 232 16.1.14 Papyrus Designer and Server - FreeForm...... 233 16.1.15 Papyrus Objects (WebControl/WebRepository)...... 233 16.1.15.1 Papyrus Objects ...... 233
getstartede V7.6 SP3 10/389 Contents
16.1.15.2 Papyrus Adapters and Typemanagers...... 236 16.1.15.3 Papyrus Query Language (PQL) ...... 238 16.1.15.4 Papyrus Resource Collection...... 240 16.1.15.5 Papyrus EYE Widgets...... 241 16.1.15.6 Papyrus WebPortal...... 242 16.1.15.7 Papyrus Word to Correspondence...... 242 16.1.16 Papyrus Database Interfaces ...... 242 16.1.17 Papyrus Host ...... 242 16.1.18 Papyrus PrinterDriver ...... 242 16.1.19 Papyrus Postprocessing/Printpool and WebArchive AFP Splitter ...... 243 16.1.20 Papyrus PostCalc...... 243 16.1.21 Papyrus Server...... 243 16.1.21.1 General ...... 244 16.1.21.2 AFP to PDF ...... 244 16.1.21.3 AFP to text ...... 244 16.1.21.4 AFP to thumbnail...... 244 16.1.21.5 Tuner...... 245 16.1.22 OverView AFP Designer ...... 245 16.1.23 OverView Image Editor...... 246 16.1.24 Papyrus best practices ...... 246 16.1.24.1 Interactive PDF documents...... 246 16.1.24.2 Project management guidelines ...... 246 16.2 Main updates in V7.1 SP8...... 246 16.2.1 General changes ...... 246 16.2.2 Papyrus product installation ...... 247 16.2.3 ISIS Papyrus Product Authorization Service...... 247 16.2.4 Papyrus Adaptive Case Management Solution ...... 247 16.2.5 Papyrus Automated Document Factory Solution ...... 247 16.2.6 Papyrus Business Correspondence Solution ...... 247 16.2.7 Papyrus Business Document Capture Solution ...... 251 16.2.8 Papyrus Analysis Toolkit...... 252 16.2.9 Papyrus Client Document Creation (Canvas)...... 253 16.2.10 Papyrus Designer and Server - FixForm ...... 254 16.2.11 Papyrus Designer, Papyrus DocEXEC ...... 255 16.2.12 Papyrus Objects (WebControl/WebRepository/IPAS)...... 257 16.2.12.1 General ...... 257 16.2.12.2 Papyrus Depot ...... 258 16.2.12.3 Papyrus Objects ...... 259 16.2.12.4 Papyrus Query Language (PQL) ...... 260 16.2.12.5 Papyrus Resource Collection...... 262 16.2.13 Papyrus Server...... 262 16.2.13.1 AFP to PDF ...... 262 16.2.13.2 HTML...... 264 16.2.13.3 PCL...... 264 16.2.13.4 PDF-in ...... 264 16.2.13.5 Postscript ...... 265 16.2.14 OverView AFP Designer ...... 265 16.2.15 OverView Image Editor...... 265 16.3 Main updates in V7.1 SP7...... 265 16.3.1 General changes ...... 266 16.3.2 Papyrus business user interfaces in V7.1 SP7...... 267 16.3.3 ISIS installation routine...... 268 16.3.4 ISIS product installation ...... 270 16.3.5 ISIS Product Authorization Service ...... 270 16.3.6 Papyrus Adaptive Case Management solution ...... 271 16.3.7 Papyrus Automated Document Factory Solution ...... 271 16.3.8 Papyrus Business Correspondence Solution ...... 271
getstartede V7.6 SP3 11/389 Contents
16.3.9 Papyrus Business Document Capture Solution ...... 272 16.3.10 Papyrus Reporting Solution...... 273 16.3.11 Papyrus Targeted Messaging Framework ...... 273 16.3.12 Papyrus Analysis Toolkit...... 273 16.3.13 Papyrus Client AFP Viewer...... 273 16.3.14 Papyrus Client Document Creation (Canvas)...... 274 16.3.15 Papyrus Designer and Server - FixForm ...... 276 16.3.16 Papyrus Designer, Papyrus DocEXEC ...... 276 16.3.17 Papyrus FontConverter...... 280 16.3.18 Papyrus Host ...... 280 16.3.19 Papyrus Objects (WebControl/WebRepository/IPAS)...... 280 16.3.19.1 Papyrus Objects ...... 281 16.3.19.2 Papyrus Depot ...... 282 16.3.19.3 Papyrus Query Language (PQL) ...... 282 16.3.19.4 Papyrus Frameworks ...... 283 16.3.19.5 Papyrus Adapters...... 283 16.3.19.6 Papyrus Resource Collection...... 284 16.3.19.7 Papyrus WebPortal...... 285 16.3.20 Papyrus Postprocessing/Printpool ...... 285 16.3.21 Papyrus PrinterDriver ...... 285 16.3.21.1 Papyrus PrinterDriver batch ...... 285 16.3.21.2 Papyrus PrinterDriver...... 286 16.3.22 Papyrus Server...... 286 16.3.22.1 IPDS...... 286 16.3.22.2 PDF-in ...... 286 16.3.22.3 HTML...... 287 16.3.22.4 PageEXEC ...... 288 16.3.22.5 AFP to PDF ...... 288 16.3.23 Papyrus WebArchive...... 289 16.3.24 OverView AFP Designer ...... 289 16.4 Main updates in V7.16 ...... 289 16.4.1 Important notes...... 289 16.4.2 ISIS product installation ...... 290 16.4.3 ISIS Product Authorization Service ...... 290 16.4.4 Papyrus Adaptive Case Management Solution improvements and new features...... 290 16.4.5 Papyrus Automated Document Factory Solution - improvements and new features...... 290 16.4.6 Papyrus Business Correspondence Solution improvements and new features...... 291 16.4.7 Papyrus Business Document Capture Solution improvements and new features...... 291 16.4.8 Papyrus Campaign Management Solution improvements and new features ...... 292 16.4.9 Papyrus Client AFP Viewer...... 292 16.4.10 Papyrus Client Canvas ...... 292 16.4.11 Papyrus Designer, Papyrus DocEXEC ...... 293 16.4.12 Papyrus Designer and Server - FixForm ...... 295 16.4.13 Papyrus FontConverter...... 296 16.4.14 Papyrus Server...... 296 16.4.14.1 General ...... 296 16.4.14.2 AFP to HTML...... 296 16.4.14.3 AFP Tuner ...... 296 16.4.14.4 IPDS...... 297 16.4.14.5 PDF ...... 297 16.4.14.6 PDF-in ...... 297 16.4.15 Papyrus Objects (WebControl/WebRepository/IPAS)...... 297 16.4.15.1 Papyrus EYE Widgets...... 297 16.4.15.2 Papyrus Query Language (PQL) ...... 298 16.4.15.3 Papyrus Depot ...... 299 16.4.15.4 Papyrus Objects Kernel ...... 299 16.4.15.5 Papyrus Desktop ...... 299
getstartede V7.6 SP3 12/389 Contents
16.4.15.6 Papyrus Adapters...... 299 16.5 Main updates in V7.15 ...... 299 16.5.1 ISIS installation routine...... 299 16.5.2 Papyrus Business Document Capture Solution improvements and new features...... 300 16.5.3 Papyrus Designer, Papyrus DocEXEC ...... 300 16.5.4 Papyrus Objects (WebControl/WebRepository/IPAS) ...... 300 16.5.4.1 Papyrus EYE Widgets...... 300 16.5.5 OverView AFP Designer ...... 300 16.6 Main updates in V7.14 ...... 300 16.6.1 General changes ...... 301 16.6.2 Papyrus AFP PrinterDriver ...... 301 16.6.3 Papyrus Business Correspondence Solution improvements and new features...... 301 16.6.4 Papyrus Client Canvas...... 302 16.6.5 Papyrus Designer, Papyrus DocEXEC ...... 303 16.6.6 Papyrus Designer and Server -FixForm...... 304 16.6.7 Papyrus Objects (WebControl/WebRepository/IPAS) ...... 305 16.6.7.1 Papyrus Objects Kernel ...... 305 16.6.7.2 Object Space...... 305 16.6.7.3 Papyrus EYE Widgets...... 305 16.6.7.4 Papyrus Query Language (PQL) ...... 306 16.6.8 Papyrus Server...... 306 16.6.8.1 PDF...... 306 16.7 Main updates in V7.13 ...... 306 16.7.1 Main updates in V7.13 (DVD v131212) ...... 306 16.7.2 Main updates in V7.13 (DVD v121119 )...... 307 16.7.2.1 Release of Papyrus EYE Widgets...... 307 16.7.2.2 Overview AFP Designer...... 307 16.7.2.3 Papyrus Client Canvas ...... 307 16.7.2.4 Papyrus Designer, Papyrus DocEXEC...... 308 16.7.2.5 Papyrus Server ...... 308 16.7.2.6 Papyrus Objects (WebControl/WebRepository/IPAS) ...... 308 16.8 Main updates in V7.12 ...... 310 16.8.1 Main updates in V7.12 (DVD v131216) ...... 310 16.8.2 Main updates in V7.12 (DVD v120829) ...... 310 16.8.2.1 General changes...... 310 16.8.2.2 Papyrus AFP PrinterDriver...... 310 16.8.2.3 Papyrus Client Canvas ...... 310 16.8.2.4 Papyrus Designer, Papyrus DocEXEC...... 311 16.8.2.5 Papyrus Designer and Server - FixForm...... 312 16.8.2.6 Papyrus Objects (WebControl/WebRepository/IPAS) ...... 313 16.8.2.7 Papyrus Server ...... 315 16.8.3 Main updates in V7.12 (DVD v120329) ...... 315 16.8.3.1 General changes...... 316 16.8.3.2 Release of Papyrus e-mail with HTML for Windows ...... 317 16.8.3.3 WebArchive/CGI solution removed from ISIS DVD...... 317 16.8.3.4 Overview AFP Designer...... 317 16.8.3.5 Papyrus Designer, Papyrus DocEXEC...... 317 16.8.3.6 Papyrus AFP Viewer...... 318 16.8.3.7 Papyrus Client Vanvas ...... 318 16.8.3.8 Papyrus Client...... 318 16.8.3.9 OverView Image Editor ...... 319 16.8.3.10 Papyrus Server ...... 319 16.8.3.11 Papyrus AFP PrinterDriver...... 319 16.8.3.12 Papyrus Postprocessing/Printpool...... 319 16.8.3.13 Papyrus Host...... 319 16.8.3.14 Papyrus Objects (WebControl/WebRepository/IPAS) ...... 319
getstartede V7.6 SP3 13/389 Contents
17 Appendix: main updates in V7.0 ...... 321 17.1 Main updates in V7.02 ...... 321 17.1.1 Main updates in V7.02 (DVD v111108) ...... 321 17.1.1.1 General changes...... 321 17.1.1.2 Papyrus AFP Compare...... 321 17.1.1.3 Papyrus Designer, Papyrus DocEXEC...... 321 17.1.1.4 OverView Image Editor ...... 322 17.1.1.5 Papyrus Server ...... 322 17.1.1.6 Papyrus Host...... 322 17.1.2 Main updates in V7.02 (DVD v110208) ...... 322 17.1.2.1 General changes...... 323 17.1.2.2 ISIS installation routine ...... 323 17.1.2.3 OverView AFP Designer...... 323 17.1.2.4 Papyrus Designer, Papyrus DocEXEC...... 324 17.1.2.5 Papyrus Derver...... 324 17.1.2.6 Papyrus Host...... 324 17.1.3 Main updates in V7.02 (DVD v101103) ...... 325 17.1.3.1 Release of Papyrus AFP Viewer and Papyrus Client Canvas...... 325 17.1.3.2 Release of Papyrus AFP PrinterDriver for Windows vista and Windows 7 ...... 325 17.1.3.3 Release of Papyrus IMAP Receiver ...... 325 17.1.3.4 Release of SPNEGO mechanism for AIX...... 325 17.1.3.5 Papyrus HTTP server functionality requires Papyrus server/https authorization ...... 326 17.1.3.6 General changes...... 326 17.1.3.7 ISIS installation routine ...... 326 17.1.3.8 OverView AFP Designer...... 326 17.1.3.9 Papyrus Designer, Papyrus DocEXEC...... 326 17.1.3.10 Papyrus Client...... 329 17.1.3.11 OverView Image Editor ...... 330 17.1.3.12 OverView Font Editor...... 330 17.1.3.13 Papyrus AFP PrinterDriver...... 330 17.1.3.14 Papyrus Postprocessing/Printpool...... 330 17.1.3.15 PapyrusPostCalc...... 331 17.1.3.16 Papyrus Server ...... 331 17.1.3.17 Papyrus Imageconverter...... 332 17.1.3.18 Papyrus Objects (WebControl/WebRepository/IPAS) ...... 333 17.1.3.19 Papyrus Designer/FreeForm, Papyrus Server/FreeForm ...... 334 17.1.3.20 Papyrus Designer/FixForm, Papyrus Server/FixForm...... 334 17.2 Main updates in v7.01 including updates since v6.20...... 334 17.2.1 Release of User-Trained Agent, activity recorder and natural language rules ...... 334 17.2.2 Release of Papyrus Aapplication and Performance Analyzer (APA)...... 335 17.2.3 Release of Papyrus Adapter/Soap ...... 335 17.2.4 Release of Papyrus Scan Receiver ...... 336 17.2.5 Release of Papyrus MAPI Receiver/Render...... 336 17.2.6 Papyrus DocEXEC MI version not delivered anymore...... 336 17.2.7 Release of ISDN fax solution on Windows ...... 336 17.2.8 Release of HTTP client for Windows and AIX ...... 336 17.2.9 Release of ISIS products for Windows Vista ...... 336 17.2.10 Netkey solution not delivered anymore...... 336 17.2.11 New release of the following ISIS products for z/os Unix ...... 336 17.2.12 Product updates ...... 336 17.2.12.1 General changes...... 336 17.2.12.2 ISIS Papyrus installation routine V7.0...... 341 17.2.12.3 Papyrus AFP Compare V7.0...... 342 17.2.12.4 OverView AFP Designer 7.0...... 343 17.2.12.5 Papyrus Designer V7.0, Papyrus DocEXEC V7.0 ...... 343 17.2.12.6 Papyrus Client V7.0 ...... 355
getstartede V7.6 SP3 14/389 Contents
17.2.12.7 OverView Image Editor v7.0 ...... 364 17.2.12.8 OverView Font Editor v7.0...... 365 17.2.12.9 Papyrus AFP Printer Driver v7.0 ...... 365 17.2.12.10 Papyrus FontConverter V7.0...... 366 17.2.12.11 Papyrus PostprocessingPrintpool V7.0 ...... 366 17.2.12.12 PostCalc v7.0...... 367 17.2.12.13 Papyrus Host v7.0...... 367 17.2.12.14 Papyrus Server V7.0...... 368 17.2.12.15 Papyrus Objects V7.0 (WebControl/WebRepository/IPAS) ...... 373 17.2.12.16 Papyrus Designer/FreeForm V7.0, Papyrus Server/FreeForm V7.0...... 385 17.2.12.17 Papyrus Designer/FixForm V7.0, Papyrus Server/FixForm V7.0 ...... 386 17.2.12.18 Papyrus Scan Client v7.0...... 387 17.2.13 Profile updates ...... 387 17.2.14 Limitations...... 388 17.2.14.1 OverView AFP Designer...... 388 17.2.14.2 Papyrus PostCalc since V6.00 ...... 388 17.2.14.3 Papyrus WebArchive since V6.00...... 388 17.2.14.4 Papyrus Host...... 388
Support & contact information...... 389
getstartede V7.6 SP3 15/389 About this document
About this document
This ISIS Papyrus software delivery contains Papyrus products in release level V7.6 SP3. The notation reads as follows:
V
Getting Started video tutorial The "Getting Started with Papyrus Products" video tutorial gives a general overview of the installation process on different platforms, the concept of product authorization, product documentation, and product support. Open the tutorial from the Windows Start menu or with the link:
Start | All Programs | ISIS Papyrus Tutorial Videos | ISIS Papyrus - Getting Started with Papyrus Products
www.isis-papyrus.com/video-getting-started-E
getstartede V7.6 SP3 16/389 Papyrus delivery - contents and naming conventions
1 Papyrus delivery - contents and naming conventions
A Papyrus installation consists of two main directories: ISIS and ISISCOMM. The ISIS directory contains top-level product documentation and configuration data, as well as subdirectories with product-specific binaries, resources, input data, output files, sample applications, product profiles and more. The ISISCOMM directory contains libraries and associated data that are shared among several Papyrus applications. The DVD contains a collection of sample applications, which help to get you started with Papyrus products. The samples make use of several kinds of resources such as fonts, images, overlays, ICC profiles. These resources are only suitable for demo purposes and must not be used for production in order to avoid copyright infringement. The following chapters explain how the names of product directories and executable files are composed of product family, product prefix, operating system, filename extension (if applicable), and version number. This structure and naming convention is the standard for all Papyrus products. 1.1 Names of executables and product directories for Windows and UNIX
The names of products and product directories, where e.g. the executables and library files for the respective Papyrus product can be found, are built up according to the pattern below. Likewise, the names of the executables follow this system. Based on the naming convention of the executable file, the name of the directory structure is additionally supplemented with the 3-digit version number.
Product name:
Product family This placeholder can be replaced by one of the following lowercase letters:
o - OverView p - Papyrus
Product prefix This placeholder can be replaced by one of the following two-lowercase-letter combinations:
ad - AFP Designer fs - Fast Search Index Generator an - Analysis Toolkit hf - Host ca - Capture ic - ImageConverter cl - Client ie - Image Editor dd - Designer oc - Objects components dr - AFP PrinterDriver pc - PostCalc dt - Desktop pp - Postprocessing/Printpool de - DocEXEC se - Server fc - FontConverter fe - Font Editor
Filename extension This placeholder can be replaced by a dot and one of the following three-lowercase-letter combinations under Windows:
exe - filename extension for executable files dll - filename extension for dynamic link libraries
getstartede V7.6 SP3 17/389 Papyrus delivery - contents and naming conventions
Operating system This placeholder can presently be replaced by one of the following two-lowercase-character combinations:
l3 - Linux (Intel X86, 32-bit) l6 - Linux (64-bit) mu - z/OS Unix s3 - Solaris (32-bit) t3 - HP-UX Itanium(64-bit) w3 - Windows (32-bit) w6 - Windows (64-bit) x3 - AIX (32-bit) x6 - AIX (64-bit) z3 - z/Linux (32-bit)
A new platform code for z/OS native is only displayed in log file entries. For more details, see chapter "15.1.1.2 New platform codes".
Version The version number consists of three digits, for example:
700 - Version 7 710 - Version 7.1 through 7.6
Examples
\oadw3700 = Directory of OverView AFP Designer for Windows 32-bit V7.0x \pdew3710 = Directory of Papyrus DocEXEC for Windows 32-bit V7.1x - V7.6x oadw3.exe = OverView AFP Designer for Windows (32-bit) pdes3 = Papyrus DocEXEC for Solaris (32-bit)
getstartede V7.6 SP3 18/389 Papyrus delivery - contents and naming conventions
1.2 Papyrus DVD contents and directory structure
The Papyrus software is delivered on a DVD. A local installation normally stores the product-specific software in the \ISIS directory. The following table shows typical content of an ISIS directory which provides a general understanding of the applied directory structures. Note that this sample content is subject to change in newer releases.
1.2.1 Papyrus base installation
Directory Content description Extension \afpds240 240-pel AFPDS *.afp, *.* \afpds300 300-pel AFPDS *.afp, *.* \afpds600 600-pel AFPDS *.afp, *.* \arabic Arabic True Type Font support *.ttf \AutoSave Automatic save directory \browser Browser plugins \cpts Code page tables for ASCII/EBCDIC conversions *.cpt \data Data files for general Papyrus Designer samples and *.asc, *.ebc job files for FormFill *.dat, *.job \data_tec Data files for technical Papyrus Designer samples *.asc,*.chk, *.dat,*.ebc, *.txt \datacs Data files for the Correspondence System *.asc \DataInterface Papyrus sample directories and files for XML and File Adapter \db_admin SQL installation scripts *.sql \demo Papyrus demo files \docdef DOCDEF source files for general Papyrus Designer *.prj, *.dfa, *.idf, *.job \docdef_tec DOCDEF source files for technical Papyrus Designer *.dfa, *.prj \docdefcs DOCDEFs for the Correspondence System *.dfa \document ISIS Papyrus product documentation *.pdf, *.txt, *.doc \fdf_pdf Compiled FormDef/PageDef files P1*.PDF, F1*.FDF \fonts_as.400 Fonts for AS 400 \fonts240 240-pel fonts X0*.FON, C0*.CHS, T1*.CDP \fonts300 300-pel fonts X0*.FON, C0*.CHS, T1*.CDP \fonts600 600-pel fonts X0*.FON, C0*.CHS, T1*.CDP
getstartede V7.6 SP3 19/389 Papyrus delivery - contents and naming conventions
\fontsout Outline fonts \formfill PP Client FormFill sample frame files *.frm \hpgl HPGL sample files for Papyrus Designer/DocEXEC *.hpgl \implib PP Designer text import sample files *.imp \install Installation routine for Windows *.exe\ \install_msi MSI packages for plugin installation \ipas IPAS Standalone (not via DC of WebControl / WebRepository) \oadw3
getstartede V7.6 SP3 20/389 Papyrus delivery - contents and naming conventions
\phfx3
getstartede V7.6 SP3 21/389 Papyrus delivery - contents and naming conventions
1.2.2 Papyrus Server directories
All Papyrus Server directories pse
\archive Archive module (DB check-in, TIFF/PDF/GIF conversions) \ascii ASCII \fax_g3 TIFF G3 (FAX) \htm AFP to HTML \ijpds Scitex IJPDS \inf AFPDS Analyzer \ipds IBM IPDS \metacode Xerox Metacode \pcl PCL3/4/5 Standard \pdf Native PDF \pe PageEXEC \pic Image Converter \pjl Printer Job Language \ps Postscript \tun AFP Tuner
getstartede V7.6 SP3 22/389 Papyrus delivery - contents and naming conventions
1.2.3 ISISCOMM directory structure The following table shows the content of the ISISCOMM directory, which is by default installed at the same level as the ISIS directory. This directory contains subdirectories for at least one of the operating systems shown.
Directory Content description \data Common data such as messages or information on time zones \l3 Library and tools for Linux (Intel X86, 32-bit) \mu Library and tools for z/OS Unix \s3 Library and tools for Solaris (32-bit) \t3 Library and tools for HP-UX Itanium (32-bit) \w3 Library and tools for Windows (32-bit) \x3 Library and tools for AIX (32-bit) \z3 Library and tools for z/Linux (32-bit)
The ISISCOMM directory is also the place of the PCS log file for standalone products. Each Papyrus process creates messages that provide information on the progress of the processes. These messages are written into this log file. PCS log files names are created in the form of pcs
1.2.4 IPAS standalone directory structure This structure is used for IPAS standalone when that product is installed. It uses a reduced Object Space and kernel configuration (without subdirectories) to minimize disk space consumption.
Directory Content Description \ipas\isiscomm ISISCOMM directory for IPAS \ipas\objects Object Space for IPAS \ipas\pdtw3
getstartede V7.6 SP3 23/389 Papyrus delivery - contents and naming conventions
1.3 Names of z/OS product datasets
All dataset names follow a basic structure that provides information about product, version, compilation and library:
ISIS.
Papyrus Host modules:
ARC - Archive module MET - Metacode module PCL - PCL module PE - PageEXEC module PDF - PDF module
Papyrus WebArchive modules:
HTP - HTTP server PCG - CGI
LOADLIB SAMPLIB OUTLIB ...
Examples:
ISIS.PDEMU700.LOADLIB ISIS.PSEMF710.MET.SAMPLIB
getstartede V7.6 SP3 24/389 Papyrus software installation and upgrade
2 Papyrus software installation and upgrade
For general prerequisites that must be addressed before the installation process, see chapter "Prerequisites" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)".
Papyrus software base installation The base installation of Papyrus software under Windows is usually a two-step process: 1. Installation under Windows from the Papyrus DVD by means of the Papyrus Installation Routine 2. Final configuration of products according to product-specific documentation on the target machines The base installation of Papyrus software under UNIX (including z/OS-USS) is usually a three-step process: 1. Installation under Windows from the DVD by means of the Installation Routine 2. Transfer of copied tar-files from Windows via FTP to the target machines 3. Final configuration of products according to product-specific documentation on the target machines The base installation of the Papyrus software under mainframe z/OS native is usually a three-step process: 1. Installation under Windows from the Papyrus DVD by means of the Installation Routine 2. Transfer of copied load libraries from Windows via FTP to the mainframe 3. Final configuration of products according to product-specific documentation on the target machines For details, see "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Further product-specific installation procedures are described in the respective product documents (see chapter "3 Technical product documentation"). If ISIS Papyrus Consultants or the ISIS Papyrus Product Support team have provided separate installation media please proceed according to the available delivery documentation, which will guide through the installation steps or refer to technical product documentation. It is highly recommended that the complete Papyrus documentation be installed. Read the relevant product documentation carefully. For more details, please contact ISIS Papyrus Product Support.
getstartede V7.6 SP3 25/389 Papyrus software installation and upgrade
Papyrus software upgrade It is recommended to update Papyrus installations to the most recent release level in order to benefit from new features and an optimal support. The extent of the upgrading process depends on the complexity of the Papyrus installations and may comprise one or more of the following topics: l Upgrading Papyrus WebRepository/Papyrus WebControl (environment infrastructure for complex solutions; also referred to as "Papyrus Objects") l Upgrading Papyrus products (client and server applications) l Upgrading IPAS (authorization service) l Upgrading Proximity Technology Software (third-party software for spellchecking/hyphenation) l Upgrading plugins (thin clients) ISIS Papyrus supports customers with the technical steps that have to be taken during the upgrade procedure. Depending on the size of the Papyrus installation and the Papyrus experience of customer personnel, additional consultancy services are recommended. For an introduction to the various topics that are important when upgrading a Papyrus installation, see chapter "Upgrading/Updating Papyrus installations" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Apart from these areas of upgrade there are three types of upgrade: l Major release upgrades l Minor release upgrades l Service pack upgrades These upgrade types correlate to the convention used for labeling Papyrus software releases.
Major release upgrades are upgrades from one major release version to another. For example, an upgrade from V6.2 to V7.1. Such updates may require adjustment of the Papyrus system in several places. All involved Papyrus components have to be upgraded to the same release (Papyrus products, Papyrus Objects domain nodes).
Minor release upgrades are upgrades from one minor release version to another, within a major release. For example, an upgrade from V7.0 to V7.4. Minor release upgrades are usually less complex than major release upgrades. Within such upgrades all components need to be upgraded to the same release level. Exceptions are possible but should be agreed on in consultation with ISIS Papyrus Product Support.
Service pack upgrades are upgrades from one service pack level to another, for example from V7.5 SP1 to V7.5 SP2. Within such upgrades it is not necessary to lift all components of the Papyrus environment to the same release level. Within a Papyrus Objects domain it is possible to operate products on different service pack levels. Such setup configuration should always be done in consultation with ISIS Papyrus Product Support.
IPAS and KeySet file An upgrade of the IPAS is usually not needed but should be handled as instructed in ISIS Papyrus product documentation or agreed on in consultation with Product Support.
Note that the KeySet file installed in the IPAS for authorizing Papyrus products is version-independent and continues to authorize the product even after you have updated it.
Note for upgrades on Windows platforms: If Papyrus products are already installed and shortcuts are present under Start | Programs then these shortcuts should be deleted before a new version is installed. Otherwise it could happen that unusable old shortcuts remain.
The shortcut ISIS Papyrus Products or ISIS Papyrus Produkte can remain as product shortcuts are installed with the version and different versions can exist in parallel.
getstartede V7.6 SP3 26/389 Technical product documentation
3 Technical product documentation
ISIS Papyrus provides technical product documentation for all Papyrus software products and Papyrus Objects based Frameworks, Applications and Solutions in PDF format located on the Papyrus DVD in the directory \document and its subdirectories. For installation information for all platforms (Windows, UNIX, z/OS), see "Software Installation and Product Authorization Installation and Administrator Guide (iinste)" (on DVD under \ and under \document\General\). The recommended Papyrus default directory structure created by the installation procedure as well as product and file naming conventions are described in this document. All Papyrus product documentation is aligned to the shipped product version. The product version is printed on the cover page of each document. This means that all documents belonging to a particular shipment version display the same version number on their cover page. However, in the event of intermediate shipments or when products have not been changed, it can be that the shipment comes with a mixed document delivery. The documents may display two different version numbers on their title page in this case.
Languages supported by technical documents When the Installation Routine is used for installation, Papyrus documentation for all products is installed by default in PDF format into the folders ISIS Papyrus Documentation English and ISIS Papyrus Dokumentation Deutsch. Technical product documentation for administrators and developers is provided by ISIS Papyrus in English only. Technical product documentation addressing business users is also delivered in German. The document number suffix denotes the respective document language, e.g. "getstartede" for English and "getstartedd" for the German version of this document.
Installation guide and IPAS tutorials It is highly recommended that the reader starts with the Software Installation and Product Authorization Installation and Administrator Guide (iinste), which also contains information on the mandatory Papyrus product authorization installations including the ISIS Papyrus Product Authorization Service (IPAS).
Two IPAS tutorials demonstrate how to install and configure the IPAS and how to administer and maintain product authorizations. Open the tutorials from the Windows Start menu or with the link:
Start | All Programs | ISIS Papyrus Tutorial Videos | IPAS Tutorial Part 1 (Installation and Configuration)
www.isis-papyrus.com/tutorial-ipas-1
Start | All Programs | ISIS Papyrus Tutorial Videos | IPAS Tutorial Part 2 (Administration and Maintenance)
www.isis-papyrus.com/tutorial-ipas-2
Product tutorials ISIS Papyrus provides a growing number of tutorial videos about Papyrus products. Open the tutorials from the Windows Start menu or with the link:
Start | All Programs | ISIS Papyrus Tutorial Videos
www.isis-papyrus.com/tutorial-videos
getstartede V7.6 SP3 27/389 Technical product documentation
Documentation - general overview and printing manuals After the installation has completed successfully, the documentation for the selected products is available in English or German on your hard disk for printing. Via shortcut in the start menu every document file can be opened and printed using the standard PDF Viewer of the target machine.
Select Programs | ISIS Papyrus Documentation and then the name of the manual you want to view or print.
General overview of the contents of the manuals The following sections give a documentation structure overview and description of the available Papyrus technical documents.
3.1 General documents
Papyrus Project Management The entry point for all Papyrus project related questions. Provides general Guidelines (pmguide) guidelines about the project management methodology recommended by ISIS Papyrus for running a successful Papyrus project. Explains the usage of the following three fill-in project documents. Project and Configuration This editable Project Implementation template considers the Plan for the Papyrus System recommendations of the Papyrus Project Management Guidelines in order at [Customer] (custsysinste) to cover all technical and architectural aspects, including a project plan template in XLS format and a check list of items to be verified before going into production. Project Scoping This editable Project Scoping template guides through the scoping phase Questionnaire for the for a potential Papyrus installation and serves as basis for the following Papyrus System at [Customer] project planning and implementation phase. (custscopee) Test Plan for the Papyrus This editable Test Plan template provides a template for designing a test System at [Customer] strategy, defining test cases, and documenting the testing phase. It (custteste) contains templates in XLS format for functional and non-functional test case documentation. 64-bit Software Installation Provides detailed instructions for installing the available 64-bit software Installation and components on all currently supported platforms. The document is a Administrator Guide supplement to the documents "Software Installation and Product (gen64iage) Authorization Installation and Administrator Guide (iinste)" and "WebRepository and WebControl Installation and Administrator Guide (poinste)" Codepage and Cross Platform Explains the purpose and importance of a codepage as these play a major Considerations General role in the ISIS OverView and Papyrus products. The document explains Information (cdpgie) some of the behaviors of the underlying systems from the point of view of the codepage handling including character naming conventions of AFP resources. Thorough understanding is necessary for seamless data and cross-platform integration applications using tile transfer protocols like FTP with Papyrus. Contacting ISIS Papyrus for Explains what information should be prepared to make a request Support General Information regarding the use of Papyrus products. (supporte) HTML Document Applications Provides an overview of the ISIS Papyrus solutions related to the Developer Guide production of HTML documents such as web pages and e-mails. It (phtmldadge) describes how HTML can be generated with Papyrus products. Use cases range from a pure conversion of an AFP document to the generation of getstartede V7.6 SP3 28/389 Technical product documentation
JSON files and their integration into existing projects to produce individualized responsive web pages. Interactive PDF Documents Describes how to integrate interactive PDF-features into the development Developer Guide (pipdfddge) with Papyrus Designer. It is targeted towards marketing people (especially this introductory chapter) and DOCDEF developers. Output Management Describes Papyrus Output Management components and options. It is Applications Architecture addressed to system architects, application analysts, and application Guide (pomarcge) developers who evaluate Papyrus Output solutions. Papyrus Best Practices Data Provides general best practice guidelines about the integration and Formats and Integration connection of external business applications like SAP, Archive systems, etc. Solutions with Papyrus with the Papyrus platform as recommended by ISIS Papyrus. (bpintegrate) Papyrus Software - Getting This is the main entry document into the Papyrus software and solution Started and News General world. It informs about the Papyrus software delivery contents, product Information (getstartede) news, naming conventions used by ISIS Papyrus and gives an overview of the provided technical documentation. Product Messages Reference Reference manual for all messages issued by products from both OverView Guide (ipmrge) and Papyrus product families. Resource Library Reference All Papyrus AFPDS processing products either create or work with AFP Guide (reslibrge) Resources, for example, with AFP Fonts, FORMDEFs, PAGEDEFs or Pagesegments. The resources can reside locally on an application client or centrally on a server being pointed to via the default.lbp profile settings or can be imported into the Resource Collection of the Papyrus WebRepository, which also allows a versioned access via the Resource GUID. Sample Applications Describes Papyrus technical samples provided with the Papyrus software Reference Guide (isasie) delivery. Smart Document Application Provides a concise overview of the design architecture of Papyrus Design Architecture Guide Document Systems describing document types, a wide variety of (pdadarcge) document design features, interesting details related to release management and outlines the features of Papyrus Designer. Software Installation and Gives all details of Papyrus software installation on all platforms (Windows, Product Authorization UNIX, mainframe z/OS native and z/OS-USS), product authorization, Installation and Hardlock and Unix Keyfile installation. In addition, ISIS Papyrus Product Administrator Guide (iinste) Authorization Service (IPAS) with KeySets and MasterKey numbers and the organization of product authorizations are described. Topics like disaster recovery, ISIS Common Directories (ISIS_COMMON), upgrading of Papyrus Object Spaces, ISIS_KEY_TRACE, ISIS_KEY_MODE, ISIS_KEY_TIMEOUT, ISIS_OMS_DOMAIN, ISIS_OMS_PORT, PCS-Monitor, permanent online product authorizations, KeyRequester, Windows services, etc. are addressed as well. Spellchecking and Describes the installation and use of the spellchecking and hyphenation Hyphenation Installation utility used by several OverView and Papyrus products. Guide (spellhyphe)
3.2 OverView AFP Designer
AFP Designer Application Describes the OverView AFP Designer functions and their usages including Developer Guide (oaddge) Forms Design Mode, Data Placement Mode, shortcuts and keys help, Batch-Compiler and starting a specific OGL/PPFA as well as the OverView Digitizer Pad mode.
getstartede V7.6 SP3 29/389 Technical product documentation
AFP Designer Building Page- Describes the Page Printer Formatting Aid (PPFA) features as defined by and FormDef Applications IBM for use by the OverView AFP Designer. It describes how Form Reference Guide (ppfa370e) Definition and Page Definition Commands work, how to create a complex printout. Descriptions are made in a demonstrative way for an easy understanding. Images and tables guide through the reference guide to provide an explanation by sample covering also conditional processing and N_UP printing.
3.3 OverView Font Editor
Font Editor Application With the OverView Font Editor, application administrators and developers Developer Guide (ofedge) create and modify AFP fonts in an easy and comfortable way controlling the coded font, codepage and characterset of single-byte character set (SBCS) and double-byte character set (DBCS) fonts.
3.4 OverView Image Editor
Image Editor Reference Guide The OverView Image Editor is designed to offer the application (oierge) administrator and developer convenient ways to create, convert and edit different types of images in AFP image formats.
3.5 Papyrus Analysis Toolkit
Analysis Toolkit Application Quick start guide for the Papyrus Analysis Toolkit, which contains Developer Guide (pandge) application developer tools to analyze AFPDS files. Currently, the Toolkit comprises the AFP Compare tool and the AFP Lister, which can be used to facilitate mass tests with the comparison of results against reference data as needed for migration or upgrade projects.
3.6 Papyrus Capture Solution
Capture Categorizer Provides a comprehensive description of Papyrus Categorizer. This Papyrus Administrator and User Guide WebRepository application is an integrated part of the powerful Capture (popcfcatauge) Solution Framework that enables to classify virtually any type of documents such as scanned documents, a wide range of file types, PDF, AFP or e-mails. Capture Solution Tutorial It it the user guide for the Papyrus Capture Tutorial providing all Guide (popcftut) knowledge required to be able to successfully step through all stages of the tutorial from the installation procedure over set-up and configuration of the "Capture tutorial - Solution" to simple development tasks and the usage of the Capture user interfaces. Papyrus Business Designer Describes in detail how to define a document type (document class, Document Capture Business category) for a Capture Solution with Papyrus Capture Business Designer Administrator Guide application. (popcfbdae) Papyrus Client - Capture User Papyrus Client Capture is the common denomination for all graphical user Guide (popcfuge) interfaces implemented by the EYE Widget applications "Capture Workplace" and "Capture Administration Workplace" which enable user interaction with a Capture Solution. This guide describes all views of "Capture Workplace" except for "Scan" view which is documented in ISIS document "Papyrus Scan Administrator and User Guide" and "Capture Administration Workplace". getstartede V7.6 SP3 30/389 Technical product documentation
Papyrus Server - Capture Papyrus Capture Server is a Papyrus application used to extract data from Reference Guide (psecaprge) business documents. Papyrus Capture Server supports FreeForm® as well as FixForm projects for the specification of the extraction definition. While WebRepository - Capture Solution Administrator and Developer Guide (popcfade) describes the integration of Capture Server within Papyrus WebRepository, "Papyrus Server - Capture Reference Guide (psecaprge)" describes the configuration and usage of Papyrus Capture Server used as standalone application, i.e. the application is started and run directly on operation system level and the required data (project definitions, document files) are retrieved from file system and the result data are stored in the file system as well. WebRepository - Capture Describes the Capture Solution. It outlines the conceptual basis as well as Solution Administrator and the infrastructure (classes, templates) for a Capture setup in Papyrus Developer Guide (popcfade) Objects.
3.7 Papyrus Client
Papyrus Client Administrator Describes the functions of the Papyrus Client (classic) and its usage to and User Guide (pclauge) view, print, and create a DOCDEF document (text editor) or complete a PPFA forms template (FunctionFill or Formsfill ). The configuration profile papyrus.prf is also described. Papyrus Client AFP Viewer Describes the functionality of the AFP Viewer and its usage to view AFP Administrator and Reference documents. Guide (pavarge) Papyrus Client Application Contains information about the Papyrus Client (classic) in standalone and Integration Developer Guide as Plugin and its integration into a Papyrus Objects application or a (pcldge) third-party application using DDE. It is primarily meant for application developers who want to integrate the Plugin into Papyrus Objects based Correspondence Solutions or create a DDE connection to the Papyrus Client from an external application. The technical descriptions assume a prerequisite basic knowledge of DDE programming and Papyrus Objects. Detailed information about DDE can be found in the relevant literature on Windows programming. For information on installation and usage of ISIS Papyrus Client, see "Papyrus Client Administrator and User Guide (pclauge)". Papyrus Client CD-ROM Describes the functionality and usage of the Papyrus CD-ROM solution. Solution with Fast Search The CD-ROM solution allows to distribute AFP documents, in their original Index Administrator and User format, to many users of those documents. For example: the distribution of Guide (cdromauge) bill documents to customer care agents throughout a country. Papyrus Client Document Describes the functions of the Papyrus Client Canvas and its usage to Creation (Canvas) create documents based on DOCDEF prompting application forms. It is the Administrator and Reference standard interface for the Papyrus Business Correspondence Solution. Guide (pcnarge)
getstartede V7.6 SP3 31/389 Technical product documentation
3.8 Papyrus Designer & DocEXEC
DocEXEC - Access to Describes the access opportunities of Papyrus DocEXEC to the Papyrus WebRepository Developer Objects Object Space. It contains a description of those DocEXEC functions Guide (pdeoadge) and commands that are able to access Papyrus Objects and read and write attribute values of particular objects also via PQL calls. These function and command descriptions comprise syntax explanation and description of return values as well as short examples of practical application. DocEXEC and Document Describes the installation and usage of Papyrus DocEXEC on Windows, Designer Installation Unix, and z/OS platforms including the DocEXEC profile, ppde.prf, Administrator Guide (pdeage) command line, struct file, project and CAPSCAN topics. DocEXEC Reference Provides a complete reference of the structure and syntax of DOCDEF Application Developer Guide (Document Definition Language) as required for processing by Papyrus (pdedge) DocEXEC to create a document. All functions, command lists, indexing, postprocessing, prompting, page break processing and DOCDEF object positioning are described. Processing XML with Papyrus Has been prepared for DOCDEF developers to help them understand the Designer Tutorial working and interaction of the two commands and it should present some ideas how these commands can be put into use.
3.9 Papyrus Designer Capture
Designer Capture Application This document describes the software product Papyrus Designer Capture Developer Guide (pcddge) which combines the power of the no longer maintained Papyrus products Papyrus Capture Designer/FixForm and Capture Designer/FreeForm. Papyrus Designer Capture allows the Capture developer to create document types (document definitions) for any kind of input documents. FixForm projects are seamlessly usable in the Papyrus Designer Capture whereas FreeForm projects have to be migrated.
3.10 Papyrus Designer FreeForm
Capture Designer FreeForm® Papyrus Capture FreeForm Extract is the product for un- and Application Developer Guide semi-structured document data extraction and classification. It is used to (ffddge) read data from documents, verify the contents and prepare it for further processing. Used in combination with the Papyrus Business Document Capture Solution it allows to automate the scanning and recognition processes.
3.11 Papyrus Font Converter
FontConverter Application Papyrus FontConverter is a product converting the respective TrueType or Developer Guide (pfcdge) Adobe PostScript screen and printer fonts into AFP Raster Fonts in 240, 300, and 600 dpi resolution and to AFP Outline Fonts. It uses the GDI engine, which is also used by the graphic platform for display and printing and therefore produces excellent quality.
getstartede V7.6 SP3 32/389 Technical product documentation
3.12 Papyrus Host
Papyrus Host Administrator Describes the installation and usage of Papyrus Host serving as a z/OS FSS Guide (phfage) Print Task or CICS Interface.
3.13 Papyrus ImageConverter
Papyrus ImageConverter Describes the usage and parameters of the Papyrus ImageConverter as a Reference Guide (picrge) supplement to the general description of the Papyrus Server.
3.14 Papyrus Objects
Papyrus Business Designer Describes Papyrus Business Designer and Papyrus Client Business and Papyrus Client Business Correspondence, products for business users to provide all the functions Correspondence User Guide that are required to create and deliver business correspondence. (pocfuge) EYE Widgets Developer Guide Describes Papyrus EYE Widgets - the system behind platform-independent (popeyewdge) GUIs. Widgets are ready-to-use GUI components provided by ISIS Papyrus that can be combined to a workplace for any business application. Filesystem Synchronization Describes Papyrus Filesystem Synchronization Framework which is an Framework Developer and application that allows to import files and directories from file system into Administrator Guide Papyrus WebRepository. Imported directories and files are automatically (pofsfwdage) kept in sync with their originals in file system and also be shared with other nodes and users. Mobile Application Describes the basic configuration steps for creating mobile user accounts, Administrator Guide utilizing the generic Papyrus Enterprise App which is available for all (pomaage) leading mobile devices. It also provides an overview of various business applications designed for specific business requirements to support different Papyrus Solutions. Monitoring, Analyzing, Describes how Papyrus Objects system administrators as well as Troubleshooting and Tuning application developers can learn about monitoring and analyses Guide (pmatage) techniques of a Papyrus Objects Domain. The core component for that is the Papyrus Application and Performance Analyzer (APA). Since each organization has individual requirements, this document explains how the default setup can be customized in order to meet the organization's requirements best. Papyrus Business Designer Describes the standard user interface of the Papyrus Adaptive Case and Papyrus Client - Adaptive Management Solution (ACM). The target audience for this document are Case Management User Guide knowledge workers who work with cases on the Papyrus ACM Solution. (poacmuge) Papyrus Client - Automated Describes the Automated Document Factory Solution (ADF), which offers Document Factory User Guide businesses intelligent end-to-end automation of their print and mail-shop (poadfuge) production processes, which are normally handled manually. Furthermore this manual explains how to use the Bounce handling workplace and the Depot search workplace. This manual describes the Papyrus EYE Widgets based graphical user interface (GUI) from the operator's point of view. Papyrus Client - Targeted Describes the graphical user interface (GUI) of the Papyrus Targeted Messaging User Guide Messaging Framework. The target audience for this document are (potarmuge) campaign administrators. They are business users who create, manage and test promotions, campaigns and messages on the Papyrus Targeted Messaging Framework.
getstartede V7.6 SP3 33/389 Technical product documentation
Papyrus Objects in a Nutshell Provides a general overview of Papyrus Objects. It is aimed at Papyrus General Information (pongie) customers and other readers, who want to understand the technical concepts behind Papyrus Objects, get to know its potential fields of application, and learn how it is used to manage business processes and data. Papyrus Word to Provides information on how to migrate Word documents to DOCDEF or Correspondence and DOCDEF Business Correspondence building blocks. Migration Administrator and User Guide (pow2cauge) WebPortal Installation and Describes the thin client solution Papyrus WebPortal, which allows to Developer Guide (powpidge) access business applications defined in the Papyrus Objects Domain with a web browser or mobile devices. WebRepository - Adapter and Describes all interfaces that enable the communication of Papyrus Objects Type Managers Developer with external applications and processes (e.g. MQ Series, SAP, etc.). and Administrator Guide (poadaptmdage) WebRepository - Adaptive Describes the Adaptive Case Management Solution (ACM), which is a Case Management Solution highly flexible case management system that is goal-oriented and not Administrator and Developer bound to strict processes. Business users can dynamically adapt processes Guide (poacmade) during production, while executives and managers have at all times complete transparency. WebRepository - Automated Describes the Automated Document Factory Solution (ADF), which offers Document Factory Solution businesses intelligent end-to-end automation of their print and mail-shop Administrator Guide production processes, which are normally handled manually. Furthermore (poadfage) this manual deals with the Print and E-Delivery Solution (PED) and the Bounce Handling Solution. This manual describes these solutions from the administrator's point of view, explaining how to set them up and configure them. WebRepository - Business Describes business application solutions on Papyrus Objects. It presents Application Solutions and the functionality of the Papyrus Objects applications and frameworks Frameworks General delivered by ISIS Papyrus in the context of these business solutions and Information (poappfwgie) outlines their key benefits. The document provides an entry point into the Papyrus Objects documentation and guides the reader towards more specific reference manuals. WebRepository - Business Describes the Business Correspondence Solution, which is used for the Correspondence Solution system integration of distributed document applications. Administrator and Developer Guide (pocfdage) WebRepository - Depot Describes the Papyrus Depot facility as well as the components of the Framework Developer and Depot Framework of Papyrus WebRepository. Administrator Guide (podepotdae) WebRepository - DOCDEF Covers the migration from a file-based DOCDEF application to Papyrus Migration to Correspondence Objects. Explains the different approaches and implementations that can Administrator Guide be used from a first implementation based on Papyrus Web Repository to a (pocfmage) solution based on the Correspondence Framework. WebRepository - Ontology Describes how to design, create and work with Papyrus business Framework Business Analyst ontologies. Ontologies enable business users to query application data and Developer Guide with the terminology used in the business's specific domain instead of (pontbadge) technical jargon. In the language that an ontology defines, you can also write business rules for adaptive workflows that must fulfill business constraints or regulatory requirements.
getstartede V7.6 SP3 34/389 Technical product documentation
WebRepository - Papyrus Describes the Papyrus Query Language (PQL), which is a script language to Query Language (PQL) interact with the Object Space. Developer Guide (popqldge) WebRepository - Reporting Describes the Reporting Solution provided by ISIS Papyrus, which allows Solution Administrator, you to set up various data sources to use them for the generation of report Developer and User Guide documents and for query user interfaces called dashboards. (rpaduge) WebRepository - Targeted Describes the installation and administration of the Papyrus Targeted Messaging Framework Messaging Framework, which allows the central management of Developer and Administrator marketing messages for any type of targeted communication Guide (potarmdage) WebRepository and Describes the Print Management Framework as basis for the Automated WebControl - Print Document Factory (ADF) Solution, which is used for the print management Management Framework across platforms based on Papyrus WebControl or Papyrus WebRepository Administrator Guide to control the Papyrus Server modules and business processes. (popmage) WebRepository and Describes the installation and configuration of Papyrus Objects, which is WebControl Installation and the underlying infrastructure component of Papyrus WebControl and Administrator Guide (poinste) Papyrus WebRepository. Furthermore the creation and configuration of new nodes and Papyrus Objects kernel parameters are described. In addition the document covers issues like backup and recovery recommendations. WebRepository Application Describes Papyrus WebRepository, which is an object-oriented graphical Developer Guide (pwride) workflow management system. It is used to build highly flexible frameworks that allow to control arbitrary processes.
3.15 Papyrus PDF-in
Papyrus PDF-in Reference Describes the usage and parameters (attributes) of the Papyrus PDF-in Guide (ppdfinrge) module.
3.16 Papyrus PostCalc
PostCalc - Postage Describes installation and functionality of Papyrus PostCalc, the postal Calculation and Optimization optimization product on top of a DB based Papyrus PrintPool. It generates Reference Guide (ppcrge) Print Lists for further processing by Papyrus DocEXEC postprocessing.
getstartede V7.6 SP3 35/389 Technical product documentation
3.17 Papyrus PostProcessing
Database Interfaces Describes the interaction of Papyrus DocEXEC based products with Developer and Administrator database systems. ISIS Papyrus supplies two database interfaces (PAS and Guide (pdbdage) PDB) for use in several business applications. Migration of database structures as well as general database issues are also covered. Papyrus Tuner Reference Describes the parameters of the Papyrus Color to Black and White Guide (ptunrge) Conversion module (AFP tuner) as a supplement to the general description of the Papyrus Server. Its functionality is available with every Papyrus Server module and is certified for Papyrus AFPs. Postprocessing/Printpool Describes Papyrus Postprocessing/Printpool and gives detailed General Information and information about the conception of postprocessing with Papyrus Developer Guide Printpool, particular DOCDEF commands, and additional tools.
3.18 Papyrus Printer Driver
PrinterDriver Administrator Describes the Papyrus PrinterDriver functions and their usages to convert and User Guide (pdrauge) from any Windows applications documents into AFP document files, AFP overlays including AFP fonts and AFP indices. It addresses the file-based AFP Printer Driver and the Papyrus Objects integrated solution. PrinterDriver Batch Describes the Papyrus PrinterDriver Batch, which is designed to convert Administrator Guide various types of input documents into AFP documents in batch mode as (pdrbage) extension of the Papyrus PrinterDriver.
3.19 Papyrus Scan
Capture Scan Administrator Papyrus Scan is an integrated application of Capture Solution framework and User Guide (poscanauge) for scanning documents and importing the scanned images. The guide describes the Papyrus Scan user interface, which is a view of the Papyrus EYE Widgets-based "Capture Workplace".
3.20 Papyrus Server
Papyrus E-Mail - Solutions Describes the Papyrus Server E-Mail solutions, installation, requirements Architecture and for the usage, parameter settings and the supported file formats of the Administrator Guide attachments as a supplement to the general description of the Papyrus (pemailsole) Server. Papyrus Server - AFP to PDF Describes the usage and parameters of the AFP to PDF module as a Reference Guide (psepdfrge) supplement to the general description of the Papyrus Server. Papyrus Server - AFP to Text Describes the usage and parameters of the AFP to Text module as a Reference Guide (psetxtrge) supplement to the general description of the Papyrus Server. Papyrus Server - AFP to Describes the usage and parameters fo the AFP to Thumbnail module as a Thumbnail Reference Guide supplement to the general description of the Papyrus Server. (psetnrge) Papyrus Server - ASCII Describes the usage and parameters of the ASCII module as a supplement Reference Guide (pseasciirge) to the general description of the Papyrus Server. Papyrus Server - Fax G3 Describes the usage and parameters of the FAX/G3 module as a Reference Guide supplement to the general description of the Papyrus Server. (psefaxg3rge)
getstartede V7.6 SP3 36/389 Technical product documentation
Papyrus Server - HTML Describes the Papyrus Server module for the conversion of AFP files into Reference Guide (psehtmlrge) HTML documents as a supplement to the general description of the Papyrus Server. It explains the usage of the AFP to HTML Converter module running standalone and within Papyrus Objects and gives an overview of its configuration as well as practical examples. Papyrus Server - IJPDS Describes the usage and parameters of the IJPDS module as a supplement Reference Guide to the general description of the Papyrus Server. (pseijpdsrge) Papyrus Server - IPDS Describes the usage and parameters of the Papyrus IPDS module as a Reference Guide (pseipdsrge) supplement to the general description of the Papyrus Server. Papyrus Server - PageEXEC Describes the usage and parameters of the PageEXEC module as a Reference Guide (pseperge) supplement to the general description of the Papyrus Server. PageEXEC is the base component of Papyrus Server providing same functionality as IBM's PSF. Papyrus Server - PJL Describes the Papyrus Server PJL (Printer Job Language) module specific Reference Guide (psepjlrge) usage and parameter settings as a supplement to the general description of the Papyrus Server. Papyrus Server - PCL Describes the usage and parameters of the PCL module (PCL3, 4, 5) as a Reference Guide (psepclrge) supplement to the general description of the Papyrus Server. Papyrus Server - PostScript Describes the usage and parameters of the PostScript module as a Reference Guide (psepsrge) supplement to the general description of the Papyrus Server. Papyrus Server - Xerox Describes the usage and parameters of the Papyrus Xerox Metacode Metacode Reference Guide module as a supplement to the general description of the Papyrus Server. (psemetarge) Papyrus Server General The main entry point into Papyrus Server processing. Describes the Installation and Papyrus Server installation, configuration by ISIS Control Data (ICD) Administrator Guide (pseiae) parameter files and integration with Papyrus WebControl and WebRepository. Each individual Papyrus Server component is documented separate documents.
3.21 Papyrus WebArchive
Papyrus The Papyrus Archive Module performs AFP split conversions and check-in Postprocessing/Printpool and tasks as used by Papyrus Postprocessing/Printpool and WebArchive. It is WebArchive AFP Splitter and also used for Papyrus Server batch conversions from AFPDS into TIFF, GIF Check-in Reference Guide into PDF/TIFF, PDF/Native. The Archive Module document comprises also (psearcrge) the description of TIFF, GIF and PDF/TIFF parameters. For a description of PDF/Native parameters, see "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". WebArchive Installation and Papyrus WebArchive based on Papyrus WebRepository and opens the Administrator Guide world of mass customer documents distribution to the corporate Intranet. (pwaiage) Corporations with a large number of customers regularly addressed with mass printing have now the option to offer company-wide document access, as well as customer direct access via the HTTP World Wide Web Internet technology as a value added service to those same documents.
getstartede V7.6 SP3 37/389 Operating systems
4 Operating systems
Papyrus software can be installed on a variety of operating systems. The following operating systems are supported by Papyrus: l Windows, l AIX, l Solaris, l HP-UX, l Linux, l z/Linux, l z/OS (native) and l z/OS Unix. For a detailed overview of the operating system versions and their derivatives supported by the current release, see "Operating systems" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Papyrus software can also be installed in virtual environments and in the cloud. For more information about the options, see chapter "Introduction to installation and product authorization" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)"
getstartede V7.6 SP3 38/389 Support of web applications
5 Support of web applications
Papyrus applications employ graphical user interfaces that are either web-based or implemented as Windows applications. 5.1 Papyrus business web applications overview
With web-based graphical user interfaces, which are also referred to as Papyrus business web applications, customers have the choice between two options: l Using ready-made web applications, which are provided by ISIS Papyrus l Using custom-made web applications, which have to be built individually Ready-made web applications provided by ISIS Papyrus are based on the following components: l A Browser application calling the Papyrus Desktop/EYE Widgets plugin collaborating with a Papyrus web server (Papyrus WebPortal) An alternative is to run the application with Papyrus EYE Widgets Desktop connected to a Papyrus web server (Papyrus WebPortal) l Papyrus Desktop/HTML collaborating with a Papyrus web server (Papyrus WebPortal) Custom-made web applications are built using one the following technologies or approaches: l Websites integrating Papyrus EYE Widgets components collaborating with a Papyrus web server (Papyrus WebPortal) l Websites integrating Papyrus Portal Language (PPL) collaborating with a Papyrus web server (Papyrus WebPortal) l Websites integrating Papyrus Client components collaborating with a non-Papyrus web server (e.g. Apache) Both web application types, ready-made and custom-made web applications, can make use of plugins in order to load particular Papyrus Client components. For Google Chrome and Mozilla Firefox, the plugin is based on the Netscape Plugin API (NPAPI) technology. For Microsoft Internet Explorer, the plugin is an ActiveX-based plugin. Plugin support is changing for some modern web browsers. The Papyrus Client components fulfill the following tasks: l View AFP files l Edit documents l Fill forms Papyrus plugins are certified to support the following browsers: l Microsoft Internet Explorer n v10 and v11 l Firefox n ESR, v45+ Papyrus Desktop/HTML applications are certified to support the following browsers: l Microsoft Internet Explorer n v10 and v11 l Google Chrome n for Windows: v52 and v53 n for Android: only latest version due to the high fragmentation of the Android phone market l Microsoft Edge n only for Windows 10 l Firefox n ESR v45+ l Safari n iOS, always latest version bundled with the iOS security updates getstartede V7.6 SP3 39/389 Support of web applications
For information for which particular client application plugins are available and how to install these plugins on web browsers, see chapter "Installing browser plugins on Windows" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". To learn how you can integrate these plugins in custom-made web applications, see "Papyrus Client Application Integration Developer Guide (pcldge)".
5.2 Plugin-free web applications
Support for plugins is changing for some modern web browsers because of security, performance and stability issues. As a result the complete web ecosystem is approaching a point where most recent browser versions will not be available to run plugin content. Companies may stay with a browser vendor version that supports plugins. ISIS Papyrus is committed to continue support for IE and Firefox that support NPAPI. The following table gives an overview of web browsers recommended by ISIS Papyrus and vendors' announcements regarding plugin support (information taken from the vendors' websites):
Web browser Plugin support by vendor Windows Internet Explorer Windows IE, where NPAPI plugins take the form of ActiveX objects, will continue support of plugins. Note: Windows IE will be replaced by Windows Edge as standard Windows browser in the long run. Windows Edge does not support NPAPI plugins. Mozilla Firefox NPAPI plugin support will be removed by end of 2016. For more detailed information, see the Mozilla support page https://support.mozilla.org/en-US/questions/1216281.
Note that all other browser vendors, which are not listed here, have already deprecated plugin support.
ISIS Papyrus strategy for plugin-free operation Phasing out plugin support forces ISIS Papyrus to offer strategies and guidance for plugin-free operation of Papyrus business web applications. The strategies have to cover two aspects: l Handling of future implementation of web applications l Migration of current web applications Implementing plugin-free web applications Setups need to follow one of the following approaches: l Use Papyrus business applications based on Papyrus Desktop/EYE Widgets implemented as Windows application instead of plugin. These Windows applications are by default fully HTTP(S)-enabled and are fully compatible with the EYE Widgets Browser Plugin installation. No application changes are needed.
l Use Papyrus business applications based on Papyrus Desktop/HTML without plugins which will require functional application changes. ISIS Papyrus will provide solutions as needed with the coming Papyrus releases.
getstartede V7.6 SP3 40/389 Support of web applications
Migrating current web applications l Papyrus Desktop/EYE Widgets Current setups that operate Papyrus business web applications from a web browser calling the Papyrus Desktop/EYE Widgets plugin will have to change to the Windows application counterpart of Papyrus Desktop/EYE Widgets. There are two options for opening Papyrus Desktop/EYE Widgets as Windows application: - open by standard Windows shortcut - open from within web browser. In this case Papyrus Desktop/EYE Widgets is being called in a separate Windows application window and not inside the browser. Papyrus Desktop/EYE Widgets both as plugin and as Windows application provides the same user experience. For more information on this topic, see chapter "Migration from plugin to Windows application" in "EYE Widgets Developer Guide (popeyewdge)".
l Papyrus Desktop/HTML Current setups that operate Papyrus business web applications based on Papyrus Desktop/HTML via web browser have the following options: - Use web browsers that support plugins. Windows Internet Explorer 11, for example. ISIS Papyrus is committed to continue support for IE and Firefox that support NPAPI. - Change to web applications based on Papyrus Desktop/EYE Widgets implemented as Windows application. - Keep Papyrus Desktop/HTML but replace the plugin part with an alternative solution that will be offered by ISIS Papyrus.
l Papyrus Portal Language (PPL) Current setups that operate Papyrus business web applications based on Papyrus Portal Language via web browser have two options: - Use web browsers that support plugins. Windows Internet Explorer 11, for example. ISIS Papyrus is committed to continue support for IE and Firefox that support NPAPI. - Use web browsers without plugin support and configure the browser so that Papyrus Client as Windows application is called instead of the plugin. For more information on this topic, see chapter "Usage with a Papyrus WebPortal" in "Papyrus Client Application Integration Developer Guide (pcldge)".
l Non-Papyrus Portal applications Current setups that operate web applications without Papyrus Portal back-end but employing Papyrus Client plugins have two options: - Use web browsers that support plugins. Windows Internet Explorer 11, for example. ISIS Papyrus is committed to continue support for IE and Firefox that support NPAPI. - Use web browsers without plugin support and configure the browser so that Papyrus Client as Windows application is called instead of the plugin. For more information on this topic, see chapter "Usage with a non-Papyrus web server" in "Papyrus Client Application Integration Developer Guide (pcldge)". ISIS Papyrus offers consultancy and migration support for all migration concerns.
getstartede V7.6 SP3 41/389 Supported languages
6 Supported languages
Technical documentation and the user interface of Papyrus products are provided by ISIS Papyrus either in English only or in English and German, depending on which audience they address.
Technical documentation Technical documents in the form of PDF documents or online help for developers and administrators are delivered by ISIS Papyrus in English.
Technical documents in the form of PDF documents for business users are delivered by ISIS Papyrus in English and German. For more details on technical documents, see chapter "3 Technical product documentation".
User interface The user interface of Papyrus products for developers and system administrators is delivered by ISIS Papyrus in English.
The user interface of Papyrus products for business users are delivered in English and German. English and German user interface texts are constantly updated, maintained, and tested by ISIS Papyrus in each release to meet the high quality standards set by ISIS Papyrus.
Note that the user interface for business users may be delivered by ISIS Papyrus in languages other than English and German, however, these languages are provided due to particular project requirements only. User interface texts in languages other than English and German are not constantly updated, maintained, and tested by ISIS Papyrus in each release. For information about setting up or updating user interfaces of Papyrus products in languages other than English and German within a Papyrus implementation, please consult ISIS Papyrus Marketing.
getstartede V7.6 SP3 42/389 Important information for all DVDs
7 Important information for all DVDs
This chapter is a summary of important information and new features relevant for all DVD releases. The subsequent chapters show the detailed information for each individual DVD release. Bug fixes and patches that are provided for certain products are not listed in detail but will be provided in certain problem constellations by ISIS Papyrus Product Support. 7.1 Important notes
7.1.1 Operating system updates l Important service pack patches for AIX
Due to an AIX issue which was so far encountered with AIX 6.1 (service pack 6100-09-08-1642) and AIX 7.1 (service pack 7100-04-03-1642), you must apply iFix IV94647 provided by IBM in order to prevent possible fatal behavior of Papyrus processes and non-Papyrus processes.
This known AIX issue was reported by ISIS Papyrus to IBM under PMR 88329,010,618 / PMR 88380,010,618. In order to get the iFix, you must open a service request at IBM.
For more details see chapter "Important service pack patches for AIX" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)".
l Certain Windows updates lead to product crashes
Due to an incompatible Windows function change, the installation of the following Windows Updates can lead to product dumps on product termination. This applies also to all processes started by the Papyrus Objects Kernel. This is valid for all Papyrus release branches.
- Windows Update KB2862973 - Windows Update KB2882822 - Windows Update KB2875501
Either uninstall the Windows Update or use a Papyrus version with build number from the first week of December 2013 or newer.
7.1.2 General l To achieve seamless functionality and integration with Windows 8 or Windows 10, it is necessary to set the properties of the Freeform Designer executable to Windows 7 compatibility mode.
l Changed handling of vector graphics in AFP Since v161005.v719 the ROUND values of a BOX are interpreted - in accordance with the GOCA-specification - as diameter. Previous versions interpreted the values as radius. Thus the corners of a rectangle are now less radiused. For details, see chapter "BOX command" in "DocEXEC Reference Application Developer Guide (pdedge)".
This affects all Papyrus products that view, manipulate and create AFPs with the exception of Papyrus Server PageEXEC. If you want to use the old interpretation, set GOCARoundedBoxUseRadius=YES in the profile file AFPRES.PRF, which can be found in \isiscomm\data\ttffonts\.
Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please read the description carefully and check if existing projects are concerned.
getstartede V7.6 SP3 43/389 Important information for all DVDs
l Unified conversion from RGB to CMYK and CMYK to RGB in all products Since v120217.v712 the conversion from RGB to CMYK and from CMYK to RGB was unified. Image Editor and Papyrus AFP Viewer used a different method (from isislib) than other products (using afpres). Now all products use the newer and better algorithm. For AFPs with colors this might lead to slight color differences in viewing and conversion from AFP to other formats (e.g. PDF). In specific cases the conversion is already used when producing AFPs with Papyrus DocEXEC and therefore color differences may also occur already at AFP production (e.g. define RGB colors in charts but create IOCA FS45 with CMYK).
Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please read the description carefully and check if existing projects are concerned.
l Wrong definition in Papyrus Designer and DocEXEC tool in Object Space may lead to malfunction The attribute "CPTS Directory" should point to the corresponding directory (e.g. "..\cpts"). Due to enhanced OMSCALL functionality since v090217.v700 a wrong definition leads to problems running Papyrus Designer and DocEXEC in Papyrus Objects (e.g. external DFAs defined in main DFA are not correctly loaded). All Papyrus Designer and DocEXEC tool instances have to be corrected. The attribute was wrong in Object Spaces on V6.20 CDs ("%ResGrp/Group=Group%"), in V7 it is correct. The TRFs on the DVD include the PQL "DocEXEC and Designer instances set CPT directory to '..\cpts'".
See chapter "Object Space" below the first V7 DVD below "available with V6.20" for more details.
l Papyrus DocEXEC/Designer: Access via Papyrus DocEXEC to system attributes requires $ Since v091109.v70x the default behavior for attribute access via Papyrus DocEXEC was corrected. System attributes must be accessed with preceding '$' (e.g. &TASKID.$EDITABLE), user attributes must be accessed without preceding '$'. For compatibility reason we introduced the new parameter SystemAttributeDollar={"Yes"|"No"} Default="Yes": + Yes: New behavior + No : Old behavior with the additional possibility to use '$' for access to system attributes only Be aware that you have to update the Object Space to the latest level to have this new parameter available when running Papyrus Client, Designer and/or DocEXEC in Papyrus Objects.
Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please read the description carefully and check if existing projects are concerned.
l Papyrus DocEXEC/Designer: Suppressed errors/warnings in DFA projects after occurrence of MAXINDEX In old versions, errors/warnings in DFA projects occurring in the DFA code after MAXINDEX were suppressed. With v090504.v700 this behavior is corrected. This may lead to additional errors/warnings (e.g. " not declared", "Main level if command not determined") when upgrading from older versions. The solution is to correct the DFA application accordingly.
Samples for different behavior of IF condition:
IF EXIST(A) AND A[MAXINDEX(A)-1]=='' New behavior: Second part of expression (after AND) is erroneous because A not yet declared, the IF part of the condition is processed (which is the default behavior for erroneous expressions), the warning "Main level if command not determined" is issued. The correct construct is:
IF EXIST(A) IF A[MAXINDEX(A)-1]=='' Any other occurrences of "Main/Sublevel level if command not determined" must be resolved by changing the IF construct like in the sample above or making sure that no undeclared variables are part of an IF condition.
getstartede V7.6 SP3 44/389 Important information for all DVDs
Old behavior: Second part not erroneous (because it was suppressed), the expression is false, the ELSE part of the condition is processed. ARRAY[1]=1 ARRAY[2]=2 ~INDEX=MAXINDEX(ARRAY)+1 IF ARRAY[~INDEX]==3 Although this is an erroneous DFA logic, these constructs are widely used. The THEN branch was not executed in previous versions, but it will be executed in newer versions. The correct solution is: ARRAY[1]=1 ARRAY[2]=2 ~INDEX=MAXINDEX(ARRAY)+1 IF EXIST(ARRAY[~INDEX]) IF ARRAY[INDEX]==3
Note: Different behavior between older and newer versions if MAXINDEX is used: The default behavior was corrected. Upgrading from older versions to the version on this DVD may lead to different results. Please read the description carefully and check if existing projects are concerned. l Papyrus DocEXEC/Designer: Corrected positioning when using NOPRECORD and INDEX commands on SL In old versions NOPRECORD and INDEX commands on sublevel (SL) could influence the position of subsequent outputs (PLACE, OUTPUT, TEXT). Defining a NOPRECORD/INDEX command on sublevel generates a SL command at 0,0 with size 0,0. Before this change it was calculated during the object positioning, and in some circumstances it caused bad object positions. With v100805.v702 this SL object is ignored during position calculation.
Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please read the description carefully and check if existing projects are concerned.
l Papyrus DocEXEC/Designer: Corrected handling of ASSIGN commands with positional keywords holding values for horizontal and vertical position since V7.1 Concerned keywords: LEFT, LASTMIN, LASTMAX, LAST, MIN, MAX, SAME, NEXT The return value in an ASSIGN was dependent on the previous command and could be either the horizontal component or the vertical one. This has been changed, so that always the vertical component is returned. The new sample \docdef_tec\SAMPLE_POSKW.PRJ shows concerned constellations and the recommendations how to avoid the changed behavior by using other positional keywords.
Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please read the description carefully and check if existing projects are concerned. Changing the keywords like demonstrated in the sample assure correct behavior with any version.
l Improved behavior of $ie in PQL With v100608.v702 the usage of $ie was changed to automatically run the according PQL in a subtransaction allowing to completely roll back the transaction in case of errors. When using $ie and setting certain attributes for later check it might lead to the situation that this change is rolled back as well, therefore the error handling has to be carefully checked. The usage of sub transaction consumes more memory of and reduces the performance. Therefore $ie should not be used in case of high volume processing where memory usage and performance are usage critical. In case the accessibility of objects is to be checked, $io or $im can be used instead.
Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please read the description carefully and check if existing projects are concerned.
getstartede V7.6 SP3 45/389 Important information for all DVDs
l Central DLLs in isiscomm include latest version only. Before V7, Papyrus CDs included cumulated DLLs in isiscomm including DLLs from older versions back to V6.10 to assure that all DLLs are available for existing older products not updated by the new installation. With V7 isiscomm includes only latest version. The installation routine was adapted as follows:
Existing product directories are copied to .BAK. Product directories and isiscomm from DVD are copied over existing directories, i.e. existing files are overwritten, missing files are added. l The installation routine checks the version of products to assure that newer (younger) versions are not overwritten by older versions. The installation automatically checks the version number (if empty the modification date) for files of type .EXE, .DLL and .OCX and the modification date for other files. Papyrus products include the build number in the version number of files of type .EXE and .DLL. In case an older version has to be intentionally installed, the related product needs to be uninstalled by the Papyrus Installation Routine and then installed again from e.g. an older DVD.
l New isiscomm\data directory for usage of common DLLs (ISISCOMM) In V7, the additional directory "data" was introduced. It includes time zone and message files. On the DVD it is located under \isiscomm\data. After the installation it has to be located under the ISISCOMM directory, e.g. "C:\isiscomm\data". The installation routine does this installation on Windows automatically. For Unix, the tar commondata.tar file needs to be considered in the manual installation steps.
l Virtual parent references for Repository, Library and Storage Introduced with CD v090810.v620 and v090722.v700 respectively. When upgrading an older Object Space a "check this object" needs to be done on every node when it is online. See chapter "Object Space" below the first V7.0 DVD below "available with V6.20 " for more details.
l Considerations for definitions of the Proxy Management Collection Be aware that with mode "1: update only" the synchronization mechanism synchronizes at node startup only those proxies that already exist on the target nodes. Mode "2: update and transfer missing" would push changed objects from the source node to all target nodes according to the proxy management definitions independent from whether or not the proxy already exists on the target node. To keep the amount of objects transferred to a minimum, ISIS recommends to check the proxy management definitions carefully and keep the number of objects as small as possible in case they are frequently changed or newly created on the source node(s). If the defined proxy management definition would also include classes like ISISLOG, NODE, TASK, MATERIAL, SESSION, VIEW the corresponding modifications of the saved SESSION/VIEW/USER attributes would be also pushed to all nodes causing a huge network traffic. Therefore is is recommended not to include them.
l Avoid unnecessary search of not existing X1 fonts (unbounded box fonts) When working with the Resource Collection of Papyrus Objects in V6.20, it is recommended to make sure that raster fonts of MCF2 format are used in Papyrus Designer and OverView AFP Designer. With version V7 this is not necessary anymore as the search was optimized in the tools accordingly.
l With V7 it is recommended to use the new SPNEGO mechanism as solution for Single Sign-On (SSO) instead of the syslog.dll logon parameter The start of Papyrus Desktop without logging in using the command line parameter /Logon=syslog.dll was changed with V7. This feature now works only if the kernel can determine the Windows user name of the client (e.g. if both kernel and client run under the same user or under different users of the same Windows domain) and pipe is used as the shared memory (socket connection is not supported). For security reasons, the feature is disabled by default and must be enabled by setting the new attribute Allow Syslog in the System Settings.
getstartede V7.6 SP3 46/389 Important information for all DVDs
7.2 General information
l Service Pack Concept and version numbers Since major release V7.0 Papyrus DVDs are released as Service Packs. V7.01 e.g. is the first Service Pack of V7.0, V7.02 is the second one. In case of V7.0 the first Service Pack was released without Papyrus Objects, the second Service Pack includes Papyrus Objects. The build number shown in the Help about dialogs shows the major release and Service Pack in the first 3 digits, e.g. 7.01.0.nnnnn shows 7.01 at the begin, the fourth digit may be 0 or 1, the last part (nnnnn) is a sequential number. The directory names change with major release but not with Service Packs, i.e. all Service Packs of one major release use same directory names e.g. "pdew3700" as directory name for Papyrus DocEXEC is used for all Service Packs (V7.01, V7.02 etc.) of major release V7.0.
l Update Papyrus Objects/Object Space It is strongly recommended to update every Object Space (Domain Controller and IPAS standalone) together with the upgrade to new product versions. Since v061222.v620 the Papyrus Objects Kernel checks if key classes are on the same level. If this is not the case the message "POTR0534E Key Management: Please install the newest KEY classes on this system." might occur. This indicates that the used Object Space was not updated. On Papyrus DVD under \ISISCD02\POUpdate all transfer files are available.
Notes: When working with Papyrus Objects and upgrading to a newer version within the same release, the Object Space has to be updated accordingly. For more details, see chapter "Upgrading Papyrus Objects Installations on Service Pack Level (in 7.1)" in "". When running IPAS standalone on level V6.20 or newer the Object Space of IPAS will be automatically updated to the V7 level of the DVD when installing IPAS standalone V7 with the Installation Routine. In case of existing older IPAS standalone the Object Space is not compatible and will not be updated. The installation routine will install a new empty Object Space for V7.0 in this case, which means that the KeySets need to be imported into this Object Space.
When working with Papyrus Objects and upgrading from an older release level (e.g. V6.09a), the Object Space has to be upgraded. For more details, see chapter "Upgrading Papyrus Objects Installations" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". l Mix of V6.10 or V6.20 with V7 versions Generally it is recommended to upgrade all products to the same V7 release level. In case of Papyrus Objects installations complete nodes may run in special situations with different versions, e.g. V6.20 and V7, using the same ISISCOMM directory (new isiscomm has to be added to existing isiscomm). Within a node a mix of versions is not possible. V6.20 products have to be at least on level of CD v080813.v620. In case of mixing different versions take care of appropriate program objects. ISIS Product Support helps with the configuration.
getstartede V7.6 SP3 47/389 Main updates in V7.6
8 Main updates in V7.6
This delivery includes Papyrus products in release level V7.6. 8.1 General changes l Online helps With V7.6, the online help files for Papyrus Designer, OverView AFP Designer, OverView Image Editor, Overview Font Editor, Papyrus FontConverter and Papyrus PrinterDriver are created using a new procedure that improves the handling of the help files. The new procedure has the effect that when using the index functionality in the help, an additional file with the extension *.chw is created in the file location (the product directory). 8.2 Papyrus Adaptive Case Management Solution
8.2.1 Information relevant for business users l Introducing ACM Business Designer The user guide "Papyrus Client - Adaptive Case Management User Guide" was renamed into "Papyrus Business Designer and Papyrus Client - Adaptive Case Management User Guide" in order to reflect the introduction of the Papyrus Adaptive Case Management Business Designer and release and change management for ACM with version 7.6.
8.3 Papyrus Automated Document Factory Solution
8.3.1 Information relevant for administrators and developers
Automated Document Factory Solution l Template creation below ADF setup container possible again Changing the class of the ADF Setup root from Folder to ADFGeneralContainer had the unintentional side effect that templates from classes below ADF tasks could no longer be created. This has been fixed with V7.6.
l ADF Operator View: suppress input data preview Until V7.6 a preview of the uploaded input data was always shown. The creation of this view had an impact on the performance, especially with very large XML data files. Thus there is now the option to generally disable the preview via the Settings Explorer in the "ADF EyeWidget views settings". For details, see chapter "ADF general" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)".
l Quality check feature: verify and vote on steps of an ADF Task With V7.6 a mechanism was introduced to insert a quality check step at an arbitrary position in an ADF workflow. Once a task lands in the Quality check queue one or more users have to give their ok for the process to continue. For more details on how to set up the necessary queues in an existing ADF setup, configure the new step (=material), integrate it into existing tasks and create the users to do the voting, see chapter "ADF quality check feature" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)".
getstartede V7.6 SP3 48/389 Main updates in V7.6
Print and E-Delivery Solution l For developers: easier customizations with new methods for information retrieval With V7.6 several methods were added that allow easier navigation to obtain data by means of getter methods. The new methods can be found on the ADFTask and PedIsisIndex classes. This information is relevant for developers and system integrators. For details, see chapter "Methods for information retrieval" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)".
l Flexible PED task design with additional step Under certain circumstances it would be nice to add an additional step (material) to a task without redesigning the entire template. Thus V7.6 introduces the possibility to do so by adding two new attributes on each OC object within PED. There are many ways to define which step is added under which conditions. For details, see chapter "Adding steps under conditions" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)".
l Flexible rule processing based on input data and PED rule structure Until V7.6 Print and E-Delivery only offered to define parallel outbound channels (by building up a rule-structure for parallel processing) or, if needed, an alternative channel in case the previous failed. With V7.6 it is now possible to trigger rules sequentially, so the next rule will be triggered as soon as a previous was completed (without error). Furthermore two rules can be triggered by the same input object in parallel. There are three new modes: Sequential processing via input data, sequential processing via PED rule structure and parallel processing via input data. For details, see chapter "Sequential and parallel processing of rules" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)".
l Bundling enhancements to increase flexibility and ease of use With V7.6 it is possible to group bundles by specific arguments. The attribute, which is read for grouping, can be defined either directly in a new attribute or as a result of a method executed on a defined object. This allows, for instance, to collect mails and then send them to one address or create different letters based on the bundle criteria. For details, see chapter "Grouped bundling" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)".
Depot search workplace l Full Text Search (FTS) available With V7.6 the Depot search workplace now also supports FTS. FTS looks into binaries like PDF. It is available for Simple search mode. The data which should be searched has to reside on a 64-bit node and necessary indexes have to be created with a wizard. Furthermore details have to be configured with the Settings Explorer in Depot search settings. For details, see "Full Text Search (FTS) - Make objects' textual content searchable" in "WebRepository Application Developer Guide (pwride)" and "Full Text Search (FTS) settings" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)".
getstartede V7.6 SP3 49/389 Main updates in V7.6
8.3.2 Information relevant for business users
ADF workplaces l ADF Operator View: suppress input data preview Until V7.6 a preview of the uploaded input data was always shown. The creation of this view had an impact on the performance, especially with very large XML data files. Thus there is now the option to disable the preview directly in the workplace.
l Quality check feature: verify and vote on steps of an ADF Task With V7.6 a mechanism was introduced to insert a quality check step at an arbitrary position in an ADF workflow. Once a task lands in the Quality check queue one or more users have to give their ok for the process to continue. For this purpose a new workplace is available. For more details, see chapter "ADF Inbox workplace - voting during quality check" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)".
Depot search workplace l Selection of index classes as search index fixed Under certain conditions not all classes that should have been selectable based on the configuration in the Settings Explorer were shown. This has been fixed with V7.6.
l Full Text Search available Full text search looks into binaries like PDF. It is available for Simple search mode. Full text search has to be set up by an administrator. For details, see chapter "Depot search workplace" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)".
8.4 Papyrus Business Capture Solution
8.4.1 Information relevant for administrators and developers l Capture solution creation wizard: adapter selection before template duplication If a Capture solution template is duplicated before the instantiation, then now it is possible to select the desired adapters before the duplication of the original Capture solution template. This feature has been added in version v7.6. For details, see the chapter "Setup a Capture Solution with the Capture solution creation wizard" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)".
l Add adapter to solution wizard: Tenant selection for adapters of a multiple tenant solution If the Capture solution for which the Add adapter to solution wizard is called has more than one Tenant assigned, then the wizard displays the additional attribute Tenant, which allows the Capture administrator to select the Tenant for the adapters to be added to the Capture solution. This feature has been added in version v7.6. For details, see the chapter "Wizard "Add adapter to Solution"" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)".
l Capture (BDC) Eye Widgets settings: new tab "Extended Completion" As of the version v7.6 a new tab Extended Completion has been added to the Capture (BDC) Eye Widgets settings and contains the attributes for the new Extended Completion view of the Capture user interface Capture workplace. For details, see the section "Extended Completion" of the chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)".
getstartede V7.6 SP3 50/389 Main updates in V7.6
l Capture document definition: OCR cache data The scope of the feature OCR cache data has been extended and a new class has been provided for the storage of the cache data. This feature allows to store extracted data for reuse in later stages of the Capture workflow. This feature has been added in version v7.6. For details, see the chapter OCR cache data in WebRepository - Capture Solution Administrator and Developer Guide (popcfade).
8.4.2 Information relevant for business users l Capture workplace: new view "Extended Completion" As alternative to the "Completion" view, the new "Extended Completion" view has been provided for the Eye Widgets workplace "Capture Workplace". This view offers the same features as the "Completion" view and additionally uses a thumbnail viewer for document search and selection. This allows the user to edit documents a similar way as on the "Document workplace" view. For details, see the chapter "Extended Completion view" in "Papyrus Client - Capture User Guide (popcfuge)".
l Papyrus Capture Client views: Feature "Open email" not available for MAPI The feature "Open email" of the Completion view, Document workplace view and the Document depot view of the Capture administration workplace was disabled for documents received by MAPI adapter. This has been fixed in the version v7.6. l Scan view appearance: new settings attribute for the tab position A new Capture (BDC) Eye Widgets settings attribute Tab location has been introduced in the version v7.6. If the thumbnail viewer of the Scan view contains the panels Scanned items and Search and the panels are overlapping, then the attribute Tab location can be used to determine if the tabs are diplayed at top or at the bottom of the thumbnail viewer. For details, see the chapter "Variants of the scan view layout" in "Capture Scan Administrator and User Guide (poscanauge)".
l Search view of Papyrus Scan: new button "Confirm" To the toolbar of the optional Search view of Papyrus Scan, a new button Confirm has been added in the version v7.6. This button allows the user to confirm documents ready for confirmation also in the Search view. For details, see the chapter "Thumbnails viewer buttons" in "Capture Scan Administrator and User Guide (poscanauge)". l Capture Business Administrator workplace: Table extraction As of the version v7.6 Capture business administrator users can use the Capture Business Administrator workplace to create extraktion definitions for tables in input documents. For details, see the chapter "Create a definition for a table extraction" in "Papyrus Business Designer Document Capture Business Administrator Guide (popcfbdae)".
l Extraction training: improvements for table definitions n As a new feature in the version v7.6 it is now possible to define an end anchor of a table n Now it is possible to train table columns without patterns
l Regression tests: improvements and extensions n In the version v7.6 improvements and extensions for differences calculations (shifts, modifies) have been added. n The feature table compare has been improved in the version v7.6. n A detection of removed and added elements has been added.
l Extraction designer: page cache size not loaded correctly The page cache size was not loaded correctly if set in the project. This has been fixed in the version v7.6.
l Extraction server: Results for layouts not retrieved The results for layouts could not be retrieved. This has been fixed in the version v7.6.
getstartede V7.6 SP3 51/389 Main updates in V7.6
l Capture Business Designer configuration: Duplicate document definition template wizard As of the version v7.6 it is possible to create a user-defined document definition template for the Capture Business Designer application. For this purpose, the Duplicate document definition template wizard has been provided which creates a duplicate of a selected document definition template which can be used as basis for a customized document definition template. For details, see the chapter "Capture Business User settings" in "Papyrus Business Designer Document Capture Business Administrator Guide (popcfbdae)". 8.5 Papyrus Business Correspondence Solution
8.5.1 Information relevant for administrators and developers l Document default font: configure default font for Business Designer The system administrator can configure a default font in the Correspondence Definition Collection that is automatically selected in the creation and modification of text variants. Introduced in V7.6. For more details, see chapter "Define a default font for text elements" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Document validation messages: error handling for expression evaluation The new ExtendedBuildingBlockErrorInformation attribute will produce an additional error message helping the template administrator to find incorrect expressions for building blocks. Introduced in V7.6. For more details, see chapter "Configuring error handling for expression evaluation in building blocks" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Configurable views in Business Designer: customize the columns displayed to a business user The content and formatting of tables displayed to clerks is configurable by creating and configuring a table data binding. Introduced in V7.6. For more details, see chapter "Customizing the format and content of table columns created for business users" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l External wizard invocation: configure back to wizard button The BACK TO WIZARD button can be configured so that it can be disabled for those wizards that contain a Service Task as they do not require any business user interaction. The BACK TO WIZARD button cannot be disabled for those wizards that contain a user Form Step. Introduced in V7.6. For more details, see chapter "Configure wizard back button for a service task" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Document delivery output options: hide output options The Output option tabs that are visible in Business Designer can be selective hidden from the business user. Introduced in V7.6. For more details, see chapter "Hide tabs in the output options dialog" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Business user workplace configuration: building blocks can be moved in document preview Workplace can be configured to enable template administrators to move a building block within Papyrus Client Canvas by dragging it to another position. Introduced in V7.6. For more details, see chapter "Enable drag and drop in Papyrus Client Canvas for template administrator" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Submit and Reset button in PDF forms: parameter list to control appearance A submit button sends filled-in data or the PDF document to the address defined. A reset button clears the content of the PDF form. Introduced in V7.6. For more details, see chapter "Define Submit and Reset buttons in PDF" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
getstartede V7.6 SP3 52/389 Main updates in V7.6
l Import PDF with bookmarks: new attribute on the PDF data object This attribute defines whether the bookmarks of a natively (IOB/PDF) imported PDF are imported or ignored. Configuration is performed on the CF scope configuration object, and can be defined on the PDF data object. Introduced in V7.6. For more details, see chapter "Merge Bookmarks when importing PDF with IOB(PDF)" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Dynamically change a page definition: store active page definition The page definition for a document can be dynamically changed. To enable this to happen the OID of the page definition has to be stored in the DOCDEF. The CF3_1_GET_LAYOUT include file (INC) has been created to store the active layout in &CF_RETURN variable. Introduced in V7.6.
l Extend customizable methods for document task: customizable method operations Developers can extend the functionality for business users that interact with document task (CfTask) by using customizable method operations. Introduced in V7.6. For more details, see chapter "Extend customized methods of the document task (CfTask)" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Assign multiple group indexes to a DOCUMENT material: group index attribute extended to accept multiple group indexes The group index attribute on the DOCUMENT material has been extended so that it can accept multiple group indexes and is no longer restricted to only one group index. Introduced in V7.6. For more details, see chapter "Assign group index to document template" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l PDF/UA: create multi-language documents It is now possible to create multi-language documents in an AFP data stream and generated PDF document by configuring the PDF/UA scope settings, language group index and document template. Introduced in V7.6. For more details, see chapter "Configure dynamic language selection and multi-language documents using tags" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Text variants: new setting controls if page break information is saved to the text variant IMP A new setting is available under CF scope document creation where you can determine if page break information is saved to the IMP. If the Keep pagebreak information during saving check box is selected, the BREAK(ON) information is saved to the text variant IMP. Introduced in V7.6. For more details, see chapter "Keep page break information during saving" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Paragraph styles: for each style, a style icon can be defined For each style, an icon can be defined in the Style icon attribute. This icon (e.g. a thumbnail preview of the list) is displayed to business users when they click the Set paragraph style button on the Style toolbar. By clicking the style icon, business users can select a style. Introduced in V7.6. For more details, see chapter "Define a style icon for a paragraph style" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Upgrading to Papyrus V7.5: Base FW project including POLICY class has to be set to active Before a migration to version 7.5 or higher, the project including the POLICY class has to be set to active. If the POLICY class is in test, the Privilege attribute on this class cannot be used for using the correct Business Designer product authorization after migration. Introduced in V7.6. For more details, see chapter "Setting the Base FW project to active" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
getstartede V7.6 SP3 53/389 Main updates in V7.6
l Compatibility settings: "PDF multiline prompt" available The compatibility DEV719_COMP_PDF_MULTILINEPROMPT parameter used for multiline prompting is required to provide backward compatibility by ensuring that document formatting is not affected and remains the same in previous framework releases. Introduced in V7.6. For more details, see chapter "PDF multiline prompt (V7.19)" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Forms: new forms definition for wizards Template administrators can now create forms in a new and easier way to be used for wizards. The new forms designer is shared with the Business Designer for ACM and offers more options for handling dynamic data. For compatibility reason, the previously used forms designer can still be used for backward compatibility with existing forms. However, it is recommended to define new wizard definitions exclusively with the new forms design mechanism. Introduced in V7.6. For more details, see chapter "Configure forms designer for template administrator" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Reporting Solution for Correspondence: configure standard dashboards and PDF-reports available for reporting users With the standard dashboards and PDF-reports delivered in the Reporting Solution for Correspondence, a set of ready-to-use report library content queries are available and also allow to configure dashboards to perform different online analysis. Introduced in V7.6. For more details, see chapter "Reporting Solution for Correspondence" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
l Resource names: configuration available to forbid special characters in image names With the new setting Restrict resource names under CF scope workplace, system administrators can define that business users can use only letters, numbers, "_" and "-" in image names when uploading or renaming an image in the image editor. Introduced in V7.6. For more details, see chapter "Restrict resource names" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)".
8.5.2 Information relevant for business users l Taxonomies: "Taxonomy" for grouping related items together has been renamed to "Category" The term "Taxonomy" as a mechanism for grouping related items in a system of categories has been renamed to the more business relevant term "Category". Introduced in V7.6. For more details, see chapter "Using categories for building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Dynamic tables: keep multi-line rows on one page Template administrators working with document templates can define for a dynamic table positioning element in the Document structure that lines in a cell are not separated by a page break but kept together on one page. Introduced in V7.6. For more details, see chapter "Keep lines in a row together on one page" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Line design building blocks: variables can be used for width and length of the line Template administrator working with document templates can now define the width and length of a Line design building block not only with static values but use also variables instead. Introduced in V7.6. For more details, see chapter "Define the size of the line" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
getstartede V7.6 SP3 54/389 Main updates in V7.6
l Checkbox design building blocks: a value can be predefined for the check box Template administrators working with a Checkbox design building block in a document template can predefine a value for the check box by selecting the value from the Checkbox content drop-down list in order to have the check box already in a selected state for the clerk. Introduced in V7.6. For more details, see chapter "Define attributes on the "Expert" tab for a check box" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Layouts: new repeat type available for all pages but the first and the last Template administrators working with a layout can now select the AllButFirstAndLastPage option from the Repeat type drop-down list for elements that should be output on every page except the first and the last. Introduced in V7.6. For more details, see chapter "Define repeat type for a layout definition element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Radio buttons: new design building block available to insert a simple radio button Template administrators working with document templates can now use the new Radio buttons design building block to insert radio buttons into the document. The options of the radio buttons can be selected by a value coming from a variable. Introduced in V7.6. For more details, see chapter "Inserting radio buttons into a document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Text input fields:
n Modifications are saved when building block is deselected When clerks working in the document editor view with building block selection modify the content in a user input field and then deselect the building block in the Document structure, the modifications are saved and they are available when the building block is selected again. Introduced in V7.6. For more details, see chapter "Text input fields and document structure" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
n Double-clicking a building block activates the input field Clerks working in the document editor view with document structure can activate the user input field by clicking the building block in the Document structure, if an internal prompt name was defined for the building block. Introduced in V7.6. For more details, see chapter "Define text input field" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l All building blocks: double-clicking a building block in a list or in a tree opens the building block for editing Template administrators can edit a building block directly by double-clicking the building block in the list of the Administrator main view or in a tree structure. The building block is then opened on a separate tab in the building block editor, either in edit mode or, if the building block is in production or editing is not allowed, in read-only mode. Introduced in V7.6. For more details, see chapter "Editing building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Document templates, groups, layouts: building blocks can be moved in document preview Template administrators can move a building block within the document preview by dragging it to another position, if this is configured by the system administrator. Introduced in V7.6. For more details, see chapter "Moving building blocks in the document preview" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
getstartede V7.6 SP3 55/389 Main updates in V7.6
l Wizards: sample wizard available to select the document template as first step Clerks can instantiate a sample wizard (Wizard with document selection), which prompts them to select the document for linking it to the wizard as the first wizard step. Template administrators can adapt this sample wizard to their requirements. Introduced in V7.6. For more details, see chapter "Wizard with document selection at runtime" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Table design building block: table cells can be defined as user input fields Template administrators working with tables created with the Table design building block can define cells as user input fields. Introduced in V7.6. For more details, see chapter "Define a table cell as user input field" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Variable groups:
n Clicking the cross in the "Default value" field of the variable variant sets the attribute to invalid Template administrators working with variables of Integer and Float type can set the Default value attribute to invalid by clicking the cross in the Default value field. Previously, clicking the cross set the value to 0. Introduced in V7.6. For more details, see chapter "Variable type, default value, and default format" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
n Formatting information can now be defined also for variables of "String" type Template administrators working with variables can now define formatting of String variables. Introduced in V7.6. For more details, see chapter "String variable" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Forms: new forms definition for wizards Template administrators can now create forms in a new and easier way to be used for wizards. The new forms designer is shared with the Business Designer for ACM and offers more options for handling dynamic data. For compatibility reason, the previously used forms designer can still be used for backward compatibility with existing forms. However, it is recommended to define new wizard definitions exclusively with the new forms design mechanism. Introduced in V7.6. For more details, see chapter "Forms designer" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Reporting Solution for Correspondence: standard dashboards and PDF-reports available With the standard dashboards and PDF-reports delivered in the Reporting Solution for Correspondence, a set of ready-to-use report library content queries are available and also allow to configure dashboards to perform different online analysis. Introduced in V7.6. For more details, see chapter "Creating reports on document and building block use" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Design building blocks: Natural Language Rules (NLR) can be defined for most design building blocks For template administrators working in a document template, group or layout, the ability to define conditions using NLR has been extended to cover now most design building blocks available, such as Assign, Change layout to, or Page break. Introduced in V7.6. For more details, see chapter "Define Natural Language Rules for design building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
getstartede V7.6 SP3 56/389 Main updates in V7.6
8.6 Papyrus Mobile Solution - Heading
8.6.1 Information relevant for administrators l Updated Settings "Mobile ACM Dashboard Settings" for ACM Mobile Applications The "Mobile ACM Dashboard Settings" is extended to customize the cases displayed on the dashboard of a user. Now you can customize the cases as well as the options displayed for the cases. For details, see "Filter ACM application libraries" in "Mobile Application Administrator Guide (pomaage)"
8.7 Papyrus Reporting Solution
8.7.1 Information relevant for administrators, developers and business users l Reporting Eye Widgets workplaces: updating the workplaces to the new design As of the version v7.6, the design of all Reporting Eye widgets workplaces have been improved and their names changed. User using already existing Reporting workplaces can easily update their workplaces to the new design and naming. For details, see the chapter "Updating Reporting solution EYE Widgets workplaces to version v7.6" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)".
l Reporting users: "Reporting user" renamed "Reporting clerk" As of the version v7.6 the hitherto Reporting user has been renamed Reporting clerk. For details, see the chapter "Create Reporting users" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)".
l Report document administration workplace: new wizard "Design report" The wizard "Design report", new in the version v7.6, guides the Reporting administrator through the various steps when a new report is to be defined. For details, see the chapter "Reporting wizard "Design report"" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)".
l Report document administration workplace: Report release process As of the version v7.6, a new report release process has been put in place. A wizard guides the Reporting administrator through the various stages of releasing a report for the Reporting users. For details, see the chapter "Report release process" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)".
l Reporting workplace settings: new attribute "Allow development" The attribute Allow development, new in the version v7.6, has been added to the Reporting workplace settings". It allows the Reporting administrator to edit activated workspaces. For details, see the chapter "Reporting workplace settings" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)".
l Reporting user settings: hide timestamps in dashboards and charts The attributes Show updated time per frame and Legend visibility, new in the version v7.6, have been added to the Reporting user settings. They allow the Reporting administrator to hide the time stamp in a dashboard frame and the legend of charts. For details, see the chapter "Reporting user settings" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)".
getstartede V7.6 SP3 57/389 Main updates in V7.6
l Bar charts: new settings attribute "Chart scale" The dashboard settings attribute Chart scale, new in the version v7.6, now allows to specify the scaling of the dimensions of a bar chart also as logarithmic. You can also set it as default with the Reporting user settings attribute Chart scale. For details, see the chapter "Reporting workplace settings" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". 8.8 Papyrus Client Document Creation (Canvas) l Insert expression dialog: new option to insert ASCII text into a text input field The new Nativectrl_nl option in the Insert expression dialog enables you to define that a variable's content to be inserted into a text input field translates CR/LF into a new line (NEWLINE). The new option is available in V7.6. Nativectrl_nl is a complement to Nativectrl, which translates CR/LF to a new paragraph (NEWPARAGRAPH). For more details, see chapter "Insert expression" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)".
l Spellchecking and Hyphenation: words or phrases between typographic quotation marks Words or phrases between typographic quotation marks were not hyphenated respectively spellchecked by Papyrus Client Canvas, Papyrus Designer or Papyrus DocEXEC prior to V7.6. This situation could occur, for example, when text from a Microsoft Word document was inserted into a text input field. V7.6 has fixed this problem. 8.9 Papyrus Database Interfaces
l PDB ODBC: Connection with PostgreSQL database was implemented With V7.6, the PDB ODBC module was extended and now also works with a PostgreSQL database. For more details, see "PostgreSQL" in "Database Interfaces Developer and Administrator Guide (pdbdage)".
l Support of Windows 64 bit: new modules for DB2 and ODBC available With V7.6, new modules to support Windows 64 bit for DB2 and ODBC will be delivered. For more details, see "Supported database client versions" in "Database Interfaces Developer and Administrator Guide (pdbdage)".
getstartede V7.6 SP3 58/389 Main updates in V7.6
8.10 Papyrus Designer, Papyrus DocEXEC
8.10.1 Information relevant for DOCDEF developers l Bar charts:
New parameter YAxisImages to define images instead of Y axis values and add supportive lines to the chart The new YAxisImages parameter, which is available for bar charts of type TowerMinMax, serves several purposes: 1. Display images instead of values on the Y axis. 2. Draw a line on the Pivot axis. 3. Display the 0 axis line in a different shape. The new parameter is available with V7.6. For more details, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)".
LineChartBasedOnBar parameter enhanced with additional value to define the line's starting point The new value enables you to connect the starting point of the line to the first value of the chart. The new value is available with V7.6. For more details, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)".
BackgroundColor parameter enhanced with optional pane definition for 3D bar charts For 3D bar charts, an optional additional value can be defined for the BackgroundColor parameter, which allows you to specifically determine the different sections of the background to be colored. The new value is available with V7.6. For more details, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)".
l Compare documents that include charts: different results with Papyrus AFP Lister If you compare a listed document that includes charts and is created with Papyrus DocEXEC V7.6 with the same listed document created with a prior version of Papyrus DocEXEC, then you will notice differences. Because of an internal improvement, the order of commands in the AFP structure has changed in V7.6, so that listed documents show different results. The change becomes only obvious in the inner structure, not in the visual appearance of the document.
getstartede V7.6 SP3 59/389 Main updates in V7.6
l QR barcode:
Swiss QR barcode generation You can create Swiss QR barcode, which is used for nationwide financial transactions, Invoke DLL (CREATEOBJECT QR(QR)) and Invoke DLL (CREATEOBJECT IOBDLL(IOBDEFS)). Swiss QR barcode generation is available with V7.6. For more details, see chapter "CREATEOBJECT QR(QR)" in "DocEXEC Reference Application Developer Guide (pdedge)".
New parameter BarcodeWidth to define the barcode width The new BarcodeWidth parameter for QR barcodes enables you to explicitly define the exact width of the barcode. The new parameter is available with V7.6. For more details, see chapter "CREATEOBJECT QR(QR)" in "DocEXEC Reference Application Developer Guide (pdedge)".
New DOCDEF command and function to output QR barcode in HTML The Outimage DOCDEF command has been introduced in V7.6 to facilitate the output of QR barcode in HTML. Papyrus DocEXEC creates HTML output by means of socalled recording functions, which transform the DFA code content of a Text/Textprompt command to HTML. The Outimage command in combination with the new Text/Textprompt subcontrol OUTIMAGE allow to generate QR barcode as image, which can then be output through Text/Textprompt. An additional aspect is that the QR barcode, which is created as an image, can be made available and be treated as a resource. Once exported as image (through the recording functions) it can be re-imported by the Invoke DLL command (CREATEOBJECT IOBDLL(IOBDEFS)). For more information, see chapter "OUTIMAGE command" in "DocEXEC Reference Application Developer Guide (pdedge)".
l Application output format: add to AFPDS the location of resources in file system by relative or absolute path notation The Application output format parameters dialog allows to write the location of resources in the file system to the AFPDS. This is done by the Res. file name checkbox. When checked, Papyrus DocEXEC writes resources' path and file names names into the AFPDS' NOP records. Prior to V7.6 a resource location was always written as absolute path specification. With V7.6 it is also possible to write relative path specification. To do so, Papyrus DocEXEC main profile parameter RELATIVERESOURCENAMES, which has been introduced with V7.6, has to be set to "YES". For more information about the Res. file name checkbox, see chapter "APPLICATION-OUTPUT-FORMAT command" in "DocEXEC Reference Application Developer Guide (pdedge)". For more information about the RELATIVERESOURCENAMES main profile parameter, see chapter "RELATIVERESOURCENAMES" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)".
l PQL set: SET_PROPERTY function enables reading of struct type attributes The SET_PROPERTY function enables Papyrus DocEXEC to directly read attributes of datatype "struct" into PQL set variables. With the option of direct reading, the parsing of the result by means of complex string operations is obsolete. SET_PROPERTY is available in V7.6. For more information, see chapter "SET_PROPERTY" in "DocEXEC Reference Application Developer Guide (pdedge)".
getstartede V7.6 SP3 60/389 Main updates in V7.6
l Text/Textprompt command:
IMPORTANT and UNIMPORTANT subcommands for "overruling" subcommand definitions of the same type IMPORTANT and UNIMPORTANT help in situations where specific subcommand definitions in several external text elements should be overruled without having to reset each particular definition. IMPORTANT and UNIMPORTANT are available in V7.6. Form more information, see chapter "IMPORTANT" in "DocEXEC Reference Application Developer Guide (pdedge)".
New subcommand option and function for mapping control characters in ASCII files: FILTER NATIVECTRL_NL and NATIVECTRL_NL() When importing external text files into Text/Textprompt command by FILTER subcontrol it is important to determine how the imported text should be interpreted. For the interpretation as ASCII text with control characters the FILTER option NATIVECTRL is available. Whenever CTRL is encountered in a file, NATIVECTRL translates it to NEWPARAGRAPH. The new FILTER option NATIVECTRL_NL translates CRLF to NEWLINE. As counterpart to FILTER NATIVECTRL_NL also new Text subcommand has been implemented: NATIVECTRL_NL(). Different to the FILTER option, which imports the text from a file, the NATIVECTRL_NL function reads the text from a variable. The interpretation of the ASCII text is the same. The FILTER NATIVECTRL_NL subcontrol and the NATIVECTRL_NL function are available in V7.6. For more information, see FILTER and "NATIVECTRL_NL" in "DocEXEC Reference Application Developer Guide (pdedge)".
Suppressing redundant empty lines and blanks caused by variables without values: variable merging The Text/Textprompt functionality Merge variables (EMPTYVAR_MERGE) was enhanced in V7.6. Merge variables allows to define how to deal with variables that should be output by the Text/Textprompt command but are empty. The attempt of outputting empty variables in combination with subsequent blanks or tabs, or a preceding NEWLINE, or a combination of both can cause undesired text formatting. For example, seemingly redundant empty lines or blanks. Prior to V7.6, Merge variables allowed for four options to deal with such situations (by specifying 0, 1 , 2 or 3 for Merge variables). With V7.6 four additional options are made available (4, 5, 6, 7). Although Merge variables was already implemented in V7.5, the parameter is announced in V7.6 for the first time. For more information, see chapter "TEXT command" in "DocEXEC Reference Application Developer Guide (pdedge)".
Continued text handling across multiple Text/Textprompt commands improved The handling of 'continued' text has been improved in V7.6. By means of the Continue checkbox it is possible to define that text properties of a leading Text/Textprompt command are also use in immediately subsequent Text/Textprompt commands can be used. This way, for example, the set COLOR of the first command is also applied in the subsequent commands. Prior to V7.6, the Continue option worked correctly except for one special case: When the leading Text/Textprompt command had a text property definition (like COLOR) that was not followed by immediate text output in the same command, then this text property definition was not 'continued' in the subsequent Text/Textprompt commands. This handling has been improved in V7.6 so that such definition situations are taken over in following commands.
l Text styles command: define custom style icons The new parameter Style icon (STYLEICON) on the Text styles dialog allows to specify PNG images as icons for paragraph styles. This image is then displayed in Papyrus Client Canvas denoting particular styles in the style selection dialog. Style icon definitions are available in V7.6. For details, see "TEXTSTYLE command" in "DocEXEC Reference Application Developer Guide (pdedge)".
getstartede V7.6 SP3 61/389 Main updates in V7.6
l Prompted variable command: specify formatting pattern for variable type "number" by PDFNumPictureDef The Prompted variable command (VARPROMPT) was enhanced by a parameter that allows the specification of a formatting pattern for prompted variable values. For the PDFNumPictureDef parameter you can specify a formatting pattern similar to the pattern definition of the NUMPICTURE function. The prompted value is then displayed according to the pattern definition. The pattern definition is only available for PDF forms. Prompting applications for AFPDS in Papyrus Client Canvas do not support pattern definitions. The pattern definition only takes effect for variable type 'Number'. For example, by pattern definition '#,###.00' the prompted value '2345' would be displayed as '2,345.00'. PDFNumPictureDef is available in V7.6. For more information, see chapter "VARPROMPT command" in "DocEXEC Reference Application Developer Guide (pdedge)".
l XML read command: execution of "Document format on tag begin" now correct when XML validation is applied on self-closing XML tags Papyrus DocEXEC versions prior to V7.6 did not enter the DocFormat defined by Document format on tag begin and process the commands therein under a certain condition: When the XMLREAD command had activated XML validation and encountered a self-closing tag (self-closing tags are tags like
l Positioning of objects: DFA() function corrected for plain value calculation The DFA() function interprets positional expressions stored in variables. For example, assign the string 'NEXT + 20 MM' to variable HIGH_POS, then you can use DFA(HIGH_POS) in a command's horizontal or vertical position parameter. DFA() would transform the string 'NEXT + 20 MM' to the positional expression 'NEXT + 20 MM', which is required for these parameters. If just a number is assigned to the variable without a unit, then the number has to be preceded by a '#' character like HIGH_POS = '#20'. The value is then calculated as page coordinate in PELS, in this case 20 PELS. Prior to V7.6, when a number was not preceded by '#' but just entered as plain value, then the error message PPDE7223E Error parsing '
l BCD (binary coded decimal) value type interpretation as page coordinate has changed BCD value types, for example '500.5123456789123', have to be rounded by the system to an integer type, if they are used as page coordinates. Prior to V7.6, when the calculation result was BCD, then the result was truncated. In this example, to '500'. With V7.6 when the calculation result is BCD, then the result is rounded to integer (just like in case of double value). In this example, to '501'. So there might be slightly different results for page coordinates in some cases. The difference is most often not even visible, but if the generated files are compared, for example by Papyrus Analysis toolkit, then a difference of 1-2 PELs can be reported.
getstartede V7.6 SP3 62/389 Main updates in V7.6
l Protected DOCDEF keywords: new keywords introduced in V7.6: _FONTNAME _FONTSCRIPT _FONTSIZE _FONTTYPE Some keywords were removed from the list: DFACODE HTMLCODE NATIVECODE NATIVECTRLCODE Protected DOCDEF keywords must not be used as names in applications (e.g. variable name, font name, document format name a.s.o.). If new protected keywords were implemented, customers should check their applications whether these protected keywords are used in their applications as names. If an existing application does contain a name which has become a protected keyword with this version, Papyrus Designer/Papyrus DocEXEC displays error message PPDE9999E (
8.10.2 Information relevant for administrators l Project file: Changes in the way how Papyrus Designer saves path specifications in a project Version 7.6 comes with improved save mechanism for relative and absolute path specification in project files. u The path specifications in the .prj file are compared to the real path in the file system. If possible Papyrus Designer simplifies the path specification. Prior to V7.6, Papyrus Designer used to save relative path specifications, for example like DEPROF="..\..\PPDE1.0\..\PPDE1.0\.\T392\DD\ppde_utf8.prf" With V7.6 such a specification is simplified to DEPROF=".\..\..\PPDE1.0\T392\DD\ppde_utf8.prf" u Path specifications are saved in a case-sensitive way. A path specification is defined so that it follows the authentic capitalization used for path names in the file system. u There is one situation where Papyrus Designer project files with the new path specification style are incompatible. When the project contains UNC path specifications with slashes, for example DEPROF="//test/isis/userisis/ppdeutf8.prf" then the project cannot be used by Papyrus Designer respectively Papyrus DocEXEC versions prior to V7.6. On Windows operating systems, these version are only able to read UNC path specifications with backslashes, for example DEPROF="\\test\isis\userisis\ppdeutf8.prf". In this case Papyrus Designer or Papyrus DocEXEC display the messages: PPDE7225E Profile file '//test/isis/userisis/ppdeutf8.prf' not found! Defaults are used. PPDE7046F No LOGICALPAGE to generate document
getstartede V7.6 SP3 63/389 Main updates in V7.6
l Compatibility parameters:
OBJRESOURCETYPECHECK: print AFPDS correctly with 3rd-party products in case of resources with same name The OBJRESOURCETYPECHECK compatibility parameter has been implemented because of an improvement in Papyrus DocEXEC's treatment of resources. Certain 3rd-party products that process AFPDS (e.g. IBM PSF) had problems with a certain type of resources. The problem becomes evident in case these resources have same names but different data types. Wrong printing results could be the consequence. Papyrus DocEXEC renames such resources with V7.6. OBJRESOURCETYPECHECK can be used to set DocEXEC back to the old behaviour. For more information, see chapter "DEOBJRESOURCETYPECHECK / OBJRESOURCETYPECHECK" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)".
V719_COMP_PDF_MULTILINEPROMPT: creation of single-line and multi-line prompts in PDF The V719_COMP_PDF_MULTILINEPROMPT compatibility parameter has been implemented because of an improvement in Papyrus DocEXEC's way of text prompts by the Textprompt command in PDF documents. The parameter sets back Papyrus DocEXEC's behavior of processing single-line and multi-line prompts in PDF to the behavior of DocEXEC versions prior to V7.1 SP9. The changed behavior can cause different results in the created PDF document, wherefore the parameter was implemented. The parameter has an effect on the creation of single-line prompts and on the vertical positioning of text in single-line prompts. V719_COMP_PDF_MULTILINEPROMPT is available in V7.6. For more information, see chapter "DEV719_COMP_PDF_MULTILINEPROMPT / V719_COMP_PDF_MULTILINEPROMPT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)".
PDF417_REMOVEBORDER: avoid redundant white space at bottom right corner The PDF417_REMOVEBORDER compatibility parameter has been implemented because of an improvement in the display of PDF417 barcode. Papyrus DocEXEC adds an area of white space of 4 PELS to the bottom and right boundary of the barcode symbol. As a consequence, the relative positioning of subsequent objects (by NEXT, LASTMAX and MAX) in vertical and horizontal direction is not quite correct. With 7.6 Papyrus DocEXEC has an additional parameter that allows to suppress the adding of white space and therefore print the object area of the symbol more precisely. Because the parameter can cause a very deviating page layout it has to be explicitly set. For more information, see chapter "DEPDF417_REMOVEBORDER / PDF417_REMOVEBORDER" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 8.11 Papyrus Objects (WebControl/WebRepository)
8.11.1 Papyrus Adapters and Typemanagers l File adapter: 32 character file-extension limit removed Until V7.6 the extension (i.e the part after the first dot in a file name) was limited to 32 characters and the rest was cut off. Now the entire filename is parsed no matter where the first dot is located. The total limit of 255 characters is still imposed as this is a restriction on multiple operating systems.
l Consolidated documentation for Papyrus e-mail adapters The documentation of all Papyrus e-mail adapters can now be found in the "Papyrus E-Mail - Solutions Architecture and Administrator Guide". For details, see chapter "Papyrus e-mail adapters" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)".
getstartede V7.6 SP3 64/389 Main updates in V7.6
8.11.2 Papyrus Depot l Full Text Search (FTS) improved With V7.6 two additional media types are supported: application/pdf and application/vnd.openxmlformats-officedocument.wordprocessingml.document (=docx). The process of creating the necessary indexes is greatly eased by a new wizard. Furthermore the Depot search workplace now also supports FTS. For details, see "Full Text Search (FTS) - Make objects' textual content searchable" in "WebRepository Application Developer Guide (pwride)" and "Full Text Search (FTS) settings" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Depot search workplace: result root navigation Quite often you are not only interested in the found data object itself, but also the context it was stored in. Thus with V7.6 there is the option to navigate somewhere based on the found object. Suppose, for instance, that the data object was checked into a depot. Then, typically the index object (its parent) also contains information of relevance, and it can be beneficial to show it and all its child objects instead of only the found data object. This is configured via the Settings Explorer by an administrator. For details, see "Result root navigation" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Depot search workplace: selection of index classes as search index fixed Under certain conditions not all classes that should have been selectable based on the configuration in the Settings Explorer were shown. This has been fixed with V7.6.
8.11.3 Papyrus EYE Widgets l Improved style sheet Alternatively to the default style sheet Papyrus Blue (formerly called Default) a new style sheet Papyrus Blue V2 has been prepared which offers the following advantages: u For a clean design, unnecessary distracting elements (borders, separators, etc.) have been removed, to better focus on important content. u For a better usability and readability, UI elements and font sizes have been slightly increased. u The consistency to the previous style has been preserved, using the same spacing (margins and padding), to have the same look & feel. The new style sheet Papyrus Blue V2 will become the default style sheet in v7.7. Therefore, we encourage you to already test the new style sheet in v7.6 to verify that it meets your requirements. In case you extended the default style sheet Papyrus Blue provided by Papyrus Software with own styles and make use of them in elements of your custom workplaces, we recommend replacing these styles by the new ones we prepared in style sheet Papyrus Blue V2, because they are designed to be harmonized with all UI elements. For details, see "Ensure that styles of custom workplaces are harmonized with "Papyrus Blue V2"" in "EYE Widgets Developer Guide (popeyewdge)".
8.11.4 Papyrus Objects System
8.11.4.1 Information relevant for developers l Parameter macro TMPLOGFILE to modify binary attributes by external application even if it ends with error Binary attributes (binary data inside Papyrus Objects) can be modified outside Papyrus Objects via a shell method using parameter macros. The TMPFILE macro generates a temporary file for this purpose. After modifying and saving the temporary file (external application terminates), its content saved back to the binary attribute in Papyrus Objects. The new parameter macro TMPLOGFILE, which is available with v7.6, does the same as TMPFILE, but it writes back the temporary file to the binary attribute even if the external tool has ended with an error. For details, see "Access binary attributes as temporary files via the operating system" in "WebRepository Application Developer Guide (pwride)".
getstartede V7.6 SP3 65/389 Main updates in V7.6
8.11.4.2 Information relevant for administrators l User login sped up Activating option Use user status object of the User Collection avoids that common rules checking the user object are triggered too often, leading to a slow login. This option has already been available since 7.4. For details, see "User Collection - General attributes" in "WebRepository and WebControl Installation and Administrator Guide (poinste)".
l Modifying password settings in the User Collection no longer blocks user creation During the modification of password settings like increasing the minimal password length on the User Collection, no user could be created. This problem has been fixed by adapting the password checking common rules and by activating new attribute Force password change of the user object, it is possible to enforce a password change at login. This problem was already fixed in 7.4. For details, see "User object - Password attributes" in "WebRepository and WebControl Installation and Administrator Guide (poinste)".
l New kernel command line parameter InstallDat for custom installation data file for the node generation So far the node generation expected installation data file install.dat in the kernel directory. With the new command line parameter it is possible to instruct the kernel to use an installation data file with a different name and/or path. For details, see "InstallDat" in "WebRepository and WebControl Installation and Administrator Guide (poinste)".
8.11.5 Papyrus Ontology Framework l Ontology mapping definitions The new edit mode in the Ontology Designer allows to create the ontology mappings in the ontology graph. The mapping editing enables to select the mapping classes/templates and expressions for the ontology entities in user interface. Multiple mappings over the same ontology can easily edited with one click. See "Ontology mapping with the Papyrus Ontology Designer" in "WebRepository - Ontology Framework Business Analyst and Developer Guide (pontbadge)" for more details.
l New view: Ontology Manager The new view Ontology Manager provides the overview of the existing ontologies together with their related mappings. See "The creation of an ontology and the Ontology Manager" in "WebRepository - Ontology Framework Business Analyst and Developer Guide (pontbadge)" for more details.
l Ontology mapping validation The new validation feature integrated in the Ontology Designer evaluates all the definitions included in the ontology mapping and detects inconsistencies, missing elements and errors. The found errors are described and the related ontology entities are highlighted for each of them. See "Mapping validation" in "WebRepository - Ontology Framework Business Analyst and Developer Guide (pontbadge)" for more details.
8.11.6 Papyrus Query Language (PQL)
8.11.6.1 Information relevant for developers l Compare images using PQL function $compareImages() The new PQL function $compareImages() allows to compare two image files and shows the difference as a difference image. For details, see "$compareImages()" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)".
getstartede V7.6 SP3 66/389 Main updates in V7.6
8.11.7 Papyrus Resource Collection l Description of resource management in Resource Collection: the structure of this chapter has been changed The Resource management in Resource Collection has been restructured to present the contents in a more simple and ordered way. Many of the sub-chapters are updated with new headings and their order has been changed. For more details, see chapter "Resource management in Resource Collection" in "Resource Library Reference Guide (reslibrge)"
8.11.8 Papyrus WebPortal
8.11.8.1 Information relevant for administrators l Web server settings: changed default SSL protocol The default value of attribute SSL Protocol Level (Minimum) of the web server configuration object HttpServerSettings has been changed to TLSv1.2 with v7.6. This has no effect on existing installations and in new installations with up to date web clients from major vendors. Only if you have web clients that do not support TLSv1.2 or higher, attribute SSL Protocol Level (Minimum) has to be adapted. For more details, see "Web server configuration object (class HTTP SERVER SETTINGS)" in "WebPortal Installation and Developer Guide (powpidge)". 8.12 Papyrus Server
8.12.1 AFP to PDF l Submit and Reset button in PDF forms: additional options A submit button sends the filled-in data, or the entire PDF-form (depending on definition), to the address defined by the PDF creator. A reset button sets all values of the form to their default values, which were defined during AFP document design. With V7.6 an additional parameter "Button TTF Font" was introduced, which allows having special characters as button caption. For more details, see chapter "Submit and Reset buttons" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)".
l Importing bookmarks of PDFs which were embedded in the AFP possible With V7.6 the new parameter "Import PDF with bookmarks" was introduced. It defines whether the bookmarks of a natively (IOB/PDF) imported PDF are imported or ignored. A Papyrus PDF-in product authorization is required to use this feature. For more details, see chapter "Import PDF with bookmarks (PDFtIobPdfImportBookmark)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)".
l PDF forms: rotation of prompts supported With V7.6 rotated prompts (entry fields) are supported. For more details, see chapter "Import PDF with prompts (PDFtIobPdfImportPrompts)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)".
l Splitting an AFP and converting into PDFs: new optimization option The parameter Resource via documents allows to keep already converted resources in memory across split documents for later re-use during AFP to PDF conversion. With V7.6 there is a new option that considers the fact that in a productive environment no new versions can be generated. For more details, see chapter "Resource via documents (PDFtResViaDocs)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)".
getstartede V7.6 SP3 67/389 Main updates in V7.6
l Multi-language support for PDF/UA Until V7.6 the default language could only be defined for the entire document. Now it can be defined for each page, based on a page index. This is especially beneficial in scenarios with multi-document AFPs, which are then split for an international audience, where the first document is in English, the second in Spanish, the third in German etc. For more details, see chapter "Multi-language support for PDF/UA" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)".
l PDF/A-3 supported PDF/A-3 allows embedding of arbitrary file formats into PDF/A conforming documents. One prominent use case is the embedding of electronic invoices following the German ZUGFeRD standard (Zentraler User Guide des Forums elektronische Rechnung Deutschland). Thus data can be exchanged in a structured and standardized way. This is especially relevant in business to business communication. In V7.6 the parameter "Additional Metdadata" was added to define the XMP file to embed. For more details, see chapter "Additional Metadata (PdftFileAttachmentsMetadata)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)".
l Change in internal PDF structure Due to requirements for PDF/A-3 and the ZUGFeRD validation in particular, the way files are embedded were changed with V7.6. These modifications to the internal structure of the PDF have no impact on the viewing experience. However if you used a 3rd party tool to extract files, you should verify if it still works. For more details, see chapter "Additional Metadata (PdftFileAttachmentsMetadata)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)".
8.12.2 AFP to Thumbnail l Supported input file format: Thumbnails from overlays Thumbnails can also be created from overlays with v7.6. Until this version only the creation of thumbnails from AFP documents was possible. Thumbnail conversion from overlays is only supported as file-based batch process at the moment, not within Papyrus Objects context.
8.12.3 E-mail l Papyrus E-Mail - Solutions Architecture and Administrator Guide (pemailsole): new document This manual is the successor to "E-Mail - Solutions and SMTP Reference Guide (pseemrge)". It was extended with a description of all available e-mail adapters. These information were moved from "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)" into this manual.
l MAPI tool for Microsoft MSG import Until V7.6 only EMLs were supported. Now also the MSG format can be processed. Processing means that the "physical document structure" is extracted i.e. e-mail body and the attachments are separated. This is necessary for Capture categorization. For details, see chapter "MAPI tool for Microsoft MSG import" in "Papyrus E-Mail - Solutions Architecture and Administrator Guide (pemailsole)". 8.13 OverView Image Editor l Possibility to define resolution for imported page segments With the new profile parameter RESOLUTIONFORDOCUMENT administrators can set a different resolution than the default resolution of 1440 for page segment resources containing Object Area Definitions with positions different than zero. For more details, see chapter "Special profile parameters" in "Image Editor Online Help (O_IE_ENG)".
getstartede V7.6 SP3 68/389 Updates in V7.6 SP1
9 Updates in V7.6 SP1 9.1 Papyrus Designer, Papyrus DocEXEC
9.1.1 Information relevant for DOCDEF developers l Text/Textprompt command: SUPERCRIPT/SUBSCRIPT text in combination with STRIKETHROUGH, UNDERLINE and BACKGROUNDCOLOR Papyrus DocEXEC and Papyrus Designer versions between V7.5 and 7.5 SP2 did not correctly calculate the placement of the text subcommands STRIKETHROUGH, UNDERINE and BACKGROUNDCOLOR when used in combination with superscript or subscript fonts (text subcommands SUPERSCRIPT and SUBSCRIPT). The calculation has been corrected in V7.6 SP1.
9.1.2 Information relevant for administrators l Compatibility parameters:
V723_COMP_SUPERSCRIPT_PARAGRAPH_START: placement of the baseline with superscript fonts The V723_COMP_SUPERSCRIPT_PARAGRAPH_START compatibility parameter has been implemented because of the corrected placement of superscript fonts. Under certain, but rarely applicable conditions, the baseline of superscript fonts was placed at a wrong position. This had an effect on the height a text block and thus on the layout of a document. Affected are projects developed with Papyrus DocEXEC and Designer versions between V7.1 SP9 and V7.2 SP3. The placement has been corrected in general, and the compatibility parameter, which is available with V7.6 SP1, allows to change back to the reaction of Papyrus DocEXEC and Designer versions between V7.1 SP9 and V7.2 SP3. For more information, see chapter "DEV723_COMP_SUPERSCRIPT_PARAGRAPH_START / V723_COMP_SUPERSCRIPT_PARAGRAPH_START" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)".
V752_COMP_SCRIPT_PLACEMENT: linespacing calculation with superscript and subscript fonts The V752_COMP_SCRIPT_PLACEMENT compatibility parameter has been implemented because of the corrected linespacing calculation for superscript and subscript fonts. Under certain, but rarely applicable conditions, the linespacing of superscript and subscript fonts was calculated so that a text block's height was not correctly calculated and thus affected the layout of a document. Affected are all projects developed with Papyrus DocEXEC and Designer versions prior to V7.6 SP1. The calculation has been corrected with V7.6 SP1 in general, and the compatibility parameter allows to change back to the reaction of Papyrus DocEXEC and Designer versions prior to V7.6 SP1. For more information, see chapter "DEV752_COMP_SCRIPT_PLACEMENT / V752_COMP_SCRIPT_PLACEMENT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 9.2 Papyrus Objects (WebControl/WebRepository)
9.2.1 Papyrus WebPortal
9.2.1.1 Information relevant for administrators l Papyrus WebPortal: security improvement With V7.6 SP1, a security improvement for the Papyrus webserver was implemented. Update to Papyrus WebPortal V7.6 SP1 is recommended.
getstartede V7.6 SP3 69/389 Updates in V7.6 SP2
10 Updates in V7.6 SP2
This delivery includes Papyrus products in release level V7.6 SP2. 10.1 General changes l End of Adobe Flash Player support - videos embedded in PDF are blocked Adobe Flash Player support ended 31.12.2020 for security reasons. Thus SWF and MP4 files embedded in PDF are blocked by Acrobat Reader and cannot be used anymore. Showing these file types required an embedded Flash player. Several Papyrus products and solutions deal with the creation of PDF with embedded files such as Papyrus DocEXEC, Papyrus Server AFP to PDF and Papyrus Business Correspondence Solution, and producers of PDF output must be aware that limitation. MP4 and SWF files still can be attached to a PDF. Showing them requires an additional external media player like VLC. For more details, see Adobe Flash Player End of Life statement. l Positioning of rotated outline fonts fixed Programs and conversion routines, that make use of the AFPRES.DLL to render fonts graphically, might have positioned rotated outline fonts incorrectly. This could have resulted in overlapping text. The effects might become visible in products that interpret AFP to an image format, such as Papyrus Client (not Papyrus Client AFP Viewer), the TIFF conversion in the context of Papyrus WebArchive or Papyrus Server Fax 3G, or the thumbnail of Papyrus Server AFP to Thumbnail. PDF generation by Papyrus Server AFP to PDF or conversion of AFP to other formats with their own font rendering are not impacted. The error in AFPRES.DLL is fixed with V7.6 SP2. 10.2 Papyrus Adaptive Case Management Solution
10.2.1 Information relevant for business users l Additional filter option in 'My Tasks' view In Papyrus Client the task's 'status' is a new filter option for the task list of the 'My Tasks' view of the Inbox workplace. For more details, see chapter "Task list and search" in "Papyrus Business Designer and Papyrus Client - Adaptive Case Management User Guide (poacmuge)".
l Import of case templates The import of processes in XPDL-file format defined in other BPM-tools has been enabled in order to migrate existing process definitions into ACM case templates. For more details, see chapter "Import a case template" in "Papyrus Business Designer and Papyrus Client - Adaptive Case Management User Guide (poacmuge)".
l New category for People Workplace The new category 'Department' is available for selection in the People Workplace. The structure of departments and multiple combinations of their cases and tasks can be viewed. For more details, see chapter "People workplace" in "Papyrus Business Designer and Papyrus Client - Adaptive Case Management User Guide (poacmuge)".
l Changed search behavior on login V7.6 SP2 disables in the Cases workplace a default search on login for performance reasons. Users have to enter search arguments and explicitly call to search.
getstartede V7.6 SP3 70/389 Updates in V7.6 SP2
10.3 Papyrus Analysis Toolkit
l Papyrus AFP Compare: Erroneous color difference In some cases, Papyrus AFP Compare found color difference in the image patterns when the compared images actually were identical. The reason for this was that the color values of the images had been incorrectly initialized and filled with random hexadecimal numbers like 0x32302D30 which represent no possible color code. This has been fixed in the version v7.6 SP2. 10.4 Papyrus Automated Document Factory Solution
10.4.1 Information relevant for administrators and developers l Full Text Search & Depot search workplace: Displaying unlimited number of results fixed In Settings Explorer in the Depot search settings the number of results shown can be limited with the setting Maximum result count. Entering 0 is supposed to mean no restriction. However, in case of a Full Text Search no results were displayed. This has been fixed in V7.6 SP2. l Queue cockpit workplace: Open ACM cases from ADF Tasks If a Task relates to a certain ACM-case V7.6 SP2 allows to connect to the ACM case, which can be opened in a separate tab and worked with using standard ACM views. This feature has to be enabled in the Settings Explorer. For details, see chapter "ADF queues cockpit" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)".
10.4.2 Information relevant for business users l Full Text Search & Depot search workplace: Displaying unlimited number of results fixed In Settings Explorer in the Depot search settings the number of results shown can be limited with the setting Maximum result count. Entering 0 is supposed to mean no restriction. However, in case of a Full Text Search no results were displayed. This has been fixed in V7.6 SP2. l Queue cockpit workplace: Open ACM cases from ADF Tasks If a Task relates to a certain ACM-case, V7.6 SP2 allows to connect to the ACM case, which can be opened in a separate tab and worked with using standard ACM views. For details, see chapter "Queue cockpit workplace" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)". 10.5 Papyrus Business Capture Solution
10.5.1 Information relevant for administrators and developers l Capture sample solutions: Reco engine Tesseract4 replaces Omnifont10 As of the version v7.6 SP2 the recognition engine FineReader10 (Omnifont10) by Abbyy has been replaced by the recognition engine Tesseract4 in the Capture sample solutions provided in the Library. The sample solution affected by this change are: n Capture document samples - solution n Capture personal documents - solution
l Capture UI: Document search fails if document label is set The search for Capture documents in the Capture UI (Capture workplace, Capture administration workplace) failed to return results, if the attribute Document label had been set on the Capture document definition. This has been fixed in the version v7.6 SP2. Now, the Capture document search also works when a document label is set.
getstartede V7.6 SP3 71/389 Updates in V7.6 SP2
l Capture idex extraction definition: Document types of extraction definition not correctly displayed When the extraction definition contained more than one document type, then the attribute 'Name' did not display all document types of the extraction definition. This has been fixed in the version v7.6 SP2. l Reco engine Tesseract4: When extracted with Capture server letter used as reject When extracted with Papyrus Capture Server, it happened that a letter was used as reject instead of the reject mark "?". This has been fixed in the version v7.6 SP2. Now, a character with confidence 0 is displayed as reject "?" as expected.
10.5.2 Information relevant for business users
Information relevant for Papyrus Client Capture users l Completion view: Zoom factor reset after first token selected If the zoom factor of a document in the image viewer of the Completion view is increased and then the feature 'Select content with mouse' is applied, then, after the first token is confirmed in the data entry field, the zoom factor is reset to its value specified in the respective Capture (BDC) Eye Widgets settings. This has been fixed in the version v7.6 SP2.
l All Capture views: Office macro formats (DOCM, XLSM, PTTM) not supported Office macro formats (DOCM, XLSM, PTTM) were not supported by all Capture views (Scan, Document workplace, Completion, Administration workplace). This has been fixed in the version v7.6 SP2.
Information relevant for Papyrus Business Designer for Capture users l Capture business administrator workplace: Document types alphabetically ordered As of the version v7.6 SP2 the document types displayed in the document types list of the Capture business administrator workplace are alphabetically ordered. For details, see the chapter "Create a new document type" in "Papyrus Business Designer Document Capture Business Administrator Guide (popcfbdae)".
l Capture Business Administrator workplace: New form field not displayed Sometimes it happened that a newly created field was not displayed on the form, when a document type had been deleted immediately before. The form field was displayed only after refresh. This has been fixed in the version v7.6 SP2.
l Capture Business Administrator workplace: Function 'Delete training data on this sample and retrain' did not work correctly When the feature 'Delete training data on this sample and retrain' was applied to a form field, then all other untrained fields were trained as well. This has been fixed in the version v7.6 SP2.
l Capture Business Administrator workplace: Node dumps after adding additional training keyword for table header and training Under certain conditions there was a dump during training when on another sample an additional training keyword for the table header was added. This has been fixed in the version v7.6 SP2.
l Capture Business Administrator workplace: Deletion and merge of elements are no done correctly in private change management In private change management, when an element was deleted and subsequently the document type completed, then the merge was not done correctly in the private change management. This has been fixed in the version v7.6 SP2.
l Capture Business Administrator workplace: Error when selecting table cell of a document type with two tables On a document type, a table was defined on one sample and other table defined using another sample document. When selecting a cell of the first table an error was raised. This has been fixed in the version v7.6 SP2.
getstartede V7.6 SP3 72/389 Updates in V7.6 SP2
l Capture Business Administrator workplace: After training a table definition columns not displayed on new sample document When a table has been defined and trained and then the document type was applied to an unused sample, then the table columns were not displayed, if the table tab was selected. This has been fixed in the version v7.6 SP2.
l Capture Business Administrator: Field type 'Text' of dialog 'Create a new field' automatically selected As of the version v7.6 SP2, in the dialog 'Create a new field', the field type 'Text' of the Field group 'Simple element' is automatically selected. 10.6 Papyrus Business Correspondence Solution
10.6.1 Information relevant for business users Improvements are provided with this service pack and affect the following use cases: l Barcode design building block: an Extended Channel Interpretation (ECI) code can be selected for a QR barcode For the definition of a QR barcode, an ECI number can be selected, which tells the barcode reader details about the used references for encoding the data in the symbol. Introduced in V7.6 SP2. For more details, see "Define ECI code for a QR barcode" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)".
l Settings: changes in the user session configuration lead to error message After changes in the user session configuration, e.g. changes to the Available language attribute for a business user from two languages to one language, business users clicking the Settings button will see an error message. This is fixed with V7.6 SP2.
l Stickers:
n Stickers created for documents may disappear Clerks and Supervisors working with stickers created as floating stickers or as building block stickers may find that some stickers are deleted randomly. This is fixed with V7.6 SP2.
n Context menu for building block stickers is not updated After a building block sticker was added and deleted again, the context menu for building block stickers is not updated and does not show the expected option to add a sticker. This is fixed with V7.6 SP2.
l Release and Change Management: Deletion of a release also deletes the default project When the release manager deletes a release in the Release and Change Management, also the default project was deleted so that e.g. the text module of a created text variant was removed. This is fixed with V7.6 SP2.
l Translations: several German translations were added and corrected Missing German translations were added and some translation were corrected in the Correspondence Framework. For example, the German translation of the term "area code" was changed from the wrong translation "PLZ" to the correct translation "Vorwahl". Introduced in V7.6 SP2.
l Wizards: translation of Name assigned to wrong language When a translation is entered for the name of a wizard in the Translate content of dialog, the translation was not assigned to the correct language. This is fixed with V7.6 SP2.
l Attachments:
getstartede V7.6 SP3 73/389 Updates in V7.6 SP2
n Order of multiple attachments may be incorrect With more than one attachment for a document, the pages of the second attachment may be shown in incorrect order. This is fixed with V7.6 SP2.
n Natural Language Rules (NLR) may not be evaluated correctly Rules that are defined on documents which are using attachments and used in a multi-part document may not be evaluated correctly so that the attachments are not properly printed depending on the rules. This is fixed with V7.6 SP2.
10.6.2 Information relevant for administrators and developers Improvements are provided with this service pack and affect the following use cases: l Data reading XML input data (clerk): showing the full path variable names The FullPathVariableNames attribute for the CF_DC_DATAREAD_DEFINITION_MAPPING is only available for XML input data. The default value for FullPathVariableNames attribute is checked (true). For existing CF_DC_DATAREAD_DEFINITION_MAPPING that have been created before the FullPathVariableNames feature was available the attribute value was set to invalid. When the UpdateDFACode operation is performed by the system administrator the invalid is taken as unchecked (false) and should have been checked (true). This is fixed with V7.6 SP2.
l Release and Change Management (release manager): deletion of a release also deletes the default project Template administrator using Adaptive Case Management (ACM) will be created with a default project that is not associated with a specific release. When the release manager deletes a release, with a default project that only contains a text module (IMP) it will also result in the default project being deleted too. This has been corrected so that the default project is no longer deleted. This is fixed with V7.6 SP2.
l Language settings (business user): removing available language from language setting The language settings object is used to determine the available languages that can be selected in the Settings option by the business user. If a language is removed from the language settings object that was previously available then this resulted in an error. This is fixed with V7.6 SP2.
10.7 Papyrus Reporting Solution
10.7.1 Information relevant for administrators, developers and business users l Document designer:
Table details not updated The table details of the Reporting building blocks have not always been updated to the latest version of the table content. This has been fixed in the version v7.6 SP2.
Nested groups not correctly supported Nested group were not correctly supported. This has been fixed in the version v7.6 SP2.
getstartede V7.6 SP3 74/389 Updates in V7.6 SP2
l Dashboard view:
Table supports double click to open additional widget As of the v7.6 SP2, the table of a dashboard supports double click to open an additional widget (e.g. cases in an ACM view). For details, see the chapter "Open widget with double-click on dashboard table" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)".
Settings possibly damaged if table columns renamed The settings of the Dashboard view could have been damaged, if data table columns were renamed. This has been fixed in the version v7.6 SP2.
Grouped ID value not displayed if group (count) column hidden The grouped ID value could not be displayed, if the group (count) column was hidden. As of the version v7.6 SP2 the group (count) column can be hidden and grouped ID values are displayed.
Source type "Same data as frame" did not work correctly The source type Same data as frame did not work as expected. This has been fixed in the version v7.6 SP2.
Reset columns of the widget Table retrieves invisible columns The button Reset columns of the widget Table retrieved all columns from the report table, even columns set to invisible. This has been fixed in the version v7.6 SP2, now only visible columns are displayed in the dashboard table.
l Report tables:
Grouping, ordering and formatting tables not possible if column names changed In report tables and Dashboard view tables grouping, ordering and formatting was not possible, if column names had been changed. This has been fixed in the version v7.6 SP2.
Joined table now supports more join types As of the v7.6 SP2, joined tables support the join types: left, right, inner and full (outer) join. For details, see the chapter "Create a joined table" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)".
l Content view: Apply changes replaces Save changes As of the version v7.6 SP2, on the content view of report tables the button Save changes has been replaced with the button Apply changes. This new button only triggers the saving of changes but also refreshes the data of the related table.
l Reporting workspace:
Report type definition unversioned object As of the version v7.6 SP2, the Report type definition is an unversioned instance which allows for configuration changes of report workspaces exported into another domain. For details, see the chapter Versioning of the Reporting Solution in WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge).
Multiple parents for Report type definition As of the version v7.6 SP2, a Report type definition can be referenced to multiple parents (Reporting scopes) which allows to use the same report for multiple Reporting scopes.
l Reporting user settings: New attributes As of the version v7.6 SP2, the following new attributes have been implemented for the Reporting user settings: n Report view default n Collapse tree layout
getstartede V7.6 SP3 75/389 Updates in V7.6 SP2
n Show advanced filter n Enable table search filter For details, see the chapter "Reporting user settings" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". 10.8 Papyrus Client l Positioning of rotated outline fonts fixed Documents that use outline fonts to display rotated text sometimes had errors in the positioning of the text. For example, overlapping text could occur. The cause was an error in the AFPRES.DLL, which is used by some programs and conversion routines for the graphical rendering of fonts in AFP documents. This error in the AFPRES.DLL is fixed with V7.6 SP2. 10.9 Papyrus Client AFP Viewer l Corrected display of indices in the Document tree window Under certain conditions it could happen that multiple instances of the same index were displayed in the Document tree window. This behavior was fixed with v7.6 SP2. For more details, see chapter "Document tree window" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". 10.10 Papyrus Designer, Papyrus DocEXEC
10.10.1 Information relevant for DOCDEF developers l Barcode:
EAN8 and EAN13 barcodes: treatment of invalid checksums at barcode generation in BCOCA mode corrected With EAN8 or EAN13 barcode, the string to be coded can be entered together with a checksum character (string length is 8 respectively 13 characters) or without checksum character (7 respectively 12 characters). Entered without checksum character, Papyrus DocEXEC calculates and adds the checksum character. When the string is entered with checksum character, and the entered checksum is wrong, then Papyrus DocEXEC displays a message: PPDE6024W Suspicious barcode data ' Data Matrix barcode: symbol size and garbage characters Due to implementation changes, Data Matrix barcodes created with Papyrus DocEXEC or Papyrus Designer versions between V7.1 SP5 and V7.6 SP1 may experience size changes compared to previous versions. Another side effect was the addition of so-called garbage characters to the value to be encoded. With version 7.6 SP2 this behavior is corrected, so that the barcode symbol is again created as in versions before V7.1 SP5. getstartede V7.6 SP3 76/389 Updates in V7.6 SP2 l Bar charts: new option to define text position With the new option TextAlwaysBottom for column bar charts you can change the placement of text in the chart. By default, these values are placed at the bottom of the chart in the same horizontal position. But if TextAlwaysBottom is used, then these values are placed at the bottom of the columns as close to the base of the columns as possible. The new barchart parameter is available with V7.6 SP2. For more details on the ChartInfo parameter, see "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)". l Define PDF output definition: end of Adobe Flash Player support - videos are blocked Adobe Flash Player support ended 31.12.2020 for security reasons. Thus SWF and MP4 files embedded in PDF are blocked by Acrobat Reader and cannot be used anymore. Showing these file types required an embedded Flash player. The Define PDF output parameters PDFTSWFFILESFORMP4 and FLASHSTICKERS are now obsolete. MP4 and SWF files still can be attached to a PDF with parameter PDFTFILEATTACHMENTS. Showing them requires an additional external media player like VLC. For more details, see Adobe Flash Player End of Life statement. l Font command: TrueType font (TTF) concatenation when both AFP fonts and TTF are specified Early implementations of the TTF support (V7.0 SP2) could require both the specification of AFP font and TTF in certain situations. This means that both the specification of the Member and the MDR name fields in Papyrus Designer Font definition dialog were required. In this case the user was able to define by means of the MDR gen. parameter in the Application output format which type of font should be used for the AFP generation. By default, the AFP font name was used, that is the font name specified in Member. But if MDR gen. was set, then the full TTF name as specified in MDR name was written to the MDR record. If MDR gen. was set and the fonts were to be written to a resource group, then these TTF fonts were not included in the resource group even if their names were specified in the MDR record of the AFP. The result was erroneous output, where these resources were missing. While the result appeared correct in the Papyrus Designer view, the generated AFPDS had certain characters missing (those that were contributed by TTF). This is fixed with V7.6 SP2. Note that this issue did not occur in situations where only one method (either Member or MDR name) was used. With current versions of Papyrus DocEXEC it is anyway only required to specify either AFP font or TTF. l Outimage command: can be used now in document applications that retrieve data from an input data file (by Record/Variable) The Outimage command helps to create barcode for HTML output. Prior to V7.6 SP2, the Outimage command could only be used in document definitions that did not retrieve data from an input data file (by Record/Variable). This is fixed with V7.6 SP2. l Text command: Unexpected line break with "continued" Text commands In the Papyrus DocEXEC versions 7.6 and 7.6 SP1 the line break reaction with "continued" Text commands was not correct. The Text command Continue option allows to appended a Text command's string of text of a to the string of text of an immediately preceding Text command at the current position. This creates the impression of uninterrupted continuous text across multiple Text commands. In a certain situation the formatting results of "continued" text in 7.6 and 7.6 SP1 are different from the results of prior versions: When the leading text string ends with one or more space characters and the text string to be appended does not start with a space character and the first word of the trailing text string causes a line break, then the last word of the leading text string (in the first Text command) was incorrectly placed at the next line. This is fixed with V7.6 SP2. Right-to-left (RTL) script: line breaks and background color With RTL script, line breaks were in some cases incorrect, and the background color did to match the text area for which it was defined. These issues are fixed with V7.6 SP2. getstartede V7.6 SP3 77/389 Updates in V7.6 SP2 l Call OMS command: Papyrus Designer did not save all parameters The Call OMS command is used to call a method in Papyrus Objects through Papyrus DocEXEC. The versions of Papyrus Designer before V7.6 SP2 could save the specification of the Call OMS command only up to the first parameter, which was not explicitly defined. If Call OMS contained a parameter that was not explicitly specified, all subsequent parameter specifications were not copied when saved. With V7.6 SP2, all parameters are saved, even if there are some among them that are not explicitly set. 10.11 Papyrus FontConverter l New prefix TZ for .CDP files for outline fonts With V7.6 SP2, the .CDP files for outline fonts get a new prefix - TZ instead of T1. For details, see chapter "Generating DBCS Unicode outline fonts" in "FontConverter Online Help (fc)". 10.12 Papyrus Objects (WebControl/WebRepository) 10.12.1 Papyrus Depot l Full Text Search & Depot search workplace: Displaying unlimited number of results fixed In Settings Explorer in the Depot search settings the number of results shown can be limited with the setting Maximum result count. Entering 0 is supposed to mean no restriction. However, in case of a Full Text Search no results were displayed. This has been fixed in V7.6 SP2. 10.12.2 Papyrus Objects System 10.12.2.1 Information relevant for administrators l Support for changing network environments Switching a certain machine between LAN and WAN network connectivity was improved in V7.6 SP2. Prior to V7.6 SP2 it could happen that a connection change could cause a loss of the kernel-to-kernel communication. A typical use case is the use of a laptop with both WLAN and LAN adapters where network connections are switched due to a mobile work style. l Considering network adapter priorities In case a computer has multiple network adapters which have a certain priority assigned on operating system level, Papyrus Objects kernel versions prior to V7.6 SP2 did not consider the priority assigned. With SP2 the access to network adapters was changed to consider the defined adapter priority to find the right adapter for the kernel-to-kernel communication. This is especially relevant for computers using Microsoft's Hyper-V technology or when virtual adapters where selected wrongly instead of the expected physical adapters. For details, see chapter "Network connection requirements" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". Important: With V7.6 SP2, the priority assigned to network adapters at operating system level may impact the kernel-to-kernel communication of existing Papyrus Objects installations. Therefore, the priority must be carefully checked and redefined, if necessary, by system administrators before rolling out the new version. 10.13 Papyrus PrinterDriver l New command line parameter /PROFILE to move the printer configuration file In case of write protected product folders, you can use this parameter to move the used printer configuration file isisdrv.pd to a different location, where it can be modified. This parameter is available with v7.6 SP2. For details, see chapter "Configuring the printer descriptor file" in "PrinterDriver Online Help (isisdrv.hlp )". getstartede V7.6 SP3 78/389 Updates in V7.6 SP2 10.14 Papyrus Server l Positioning of rotated outline fonts fixed Programs and conversion routines, that make use of the AFPRES.DLL to render fonts graphically, might have positioned rotated outline fonts incorrectly. This could have resulted in overlapping text. The effects might become visible in products that interpret AFP to an image format, such as Papyrus Client (not Papyrus Client AFP Viewer), the TIFF conversion in the context of Papyrus WebArchive or Papyrus Server Fax 3G, or the thumbnail of Papyrus Server AFP to Thumbnail. PDF generation by Papyrus Server AFP to PDF or conversion of AFP to other formats with their own font rendering are not impacted. The error in AFPRES.DLL is fixed with V7.6 SP2. 10.14.1 AFP to PDF l End of Adobe Flash Player support - Videos are blocked Adobe Flash Player support ended 31.12.2020 for security reasons. Thus SWF and MP4 files (which required an embedded Flash player to be shown) are blocked and cannot be used anymore. The file based ICD parameter "PDFTSWFFILESFORMP4" and "FLASHSTICKERS" are now obsolete. The Papyrus Objects attributes "Flash stickers", "MP4 player files" and "Use MP4player files from ResColl" are also obsolete. MP4 and SWF files still can be attached to a PDF with parameter "PDFTFILEATTACHMENTS". Showing them requires an additional external media player like VLC. For more details, see Adobe Flash Player End of Life statement. getstartede V7.6 SP3 79/389 Updates in V7.6 SP3 11 Updates in V7.6 SP3 This delivery includes Papyrus products in release level V7.6 SP3. 11.1 General changes l Timezone issue in SUSE Linux Enterprise Server (SLES) 12 SP5 Because of a timezone issue in SLES 12 SP5, time display and time saving in Papyrus applications that run on 32-bit nodes may be incorrect. Instead of the respective local time zone, only the UTC is passed on to the kernel by the operating system. This affects all time queries made by the respective kernel. As a result, changes in objects are stored with the incorrect time. For example, if user interfaces based on Papyrus EYE Widgets access such objects, the time will then also be displayed incorrectly. One way to get around this mistake is to set the environment variable TZ to the UTC offset for the current local time. The calculation of the time zone for TZ uses positive offsets for locations to the west and negative to the east of UTC. For example, set the environment variable to export TZ=UTC-1 in order to get Central European Time (CET). Consider also the current daylight saving when setting the variable. In order to get the correct CET in summer, for example, set export TZ=UTC-2. Another way to get around the problem is to install a timezone database in "fat" format, which is supported by the 32-bit Linux library glibc. The actual technical reason for the issue is a inconsistent installation for 32-bit processes and relates to SUSE's 32-bit runtime library glibc (respectively the format of the timezone database files). The 32-bit glibc cannot read the "slim" format of the current timezone database files and thus assumes UTC. (For a 64-bit glibc the "slim" format is supported and 64-bit processes successfully determine the correct timezone.) 11.2 Papyrus Adaptive Case Management Solution 11.2.1 Information relevant for business users l Content list of cases The refresh behavior of object trees in the content view of cases has been improved when adding content objects. l Completion of service tasks Sometimes service tasks stayed in state 'Active' event though the connected material is already completed. This is fixed with V7.6 SP3. getstartede V7.6 SP3 80/389 Updates in V7.6 SP3 11.3 Papyrus Automated Document Factory Solution 11.3.1 Information relevant for administrators and developers Automated Document Factory Solution l Quality check feature: Setup script extended Voting during the quality check is done with an ACM application. The setup script was extended to select or create an ACM depot to store the related case (=voting) data. If you have already used the script in a version prior to V7.6 SP3, you can configure this setting manually. For details, see chapter "Setup script" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l MQ Send and ADF communication problem fixed Under certain circumstances a task with an erroneous MQ material was moved to the Completed queue instead of the Error queue. This has been fixed in V7.6 SP3. Depot search workplace l Update Depot search settings to latest index visible to user via button Whenever a new version of an index is created, its object ID changes. Thus it is necessary to update the following attributes in Depot search settings: Index selection, Select search attributes, Select return attributes, Select export attributes and Select details attributes to reflect this change. Starting with V7.6 SP3 this can be done more conveniently by the new button Update Depot search settings in the Settings Explorer, which is available in the top right when the Depot search settings are selected. For details, see chapter "Define indexes to use" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Index selection dependent on workplace fixed In previous versions the Default index dependent on workplace setting did not work in some cases. This has been fixed with V7.6 SP3. Furthermore it is now possible to also set the index with a finer granularity. It can not only be set for an entire workplace but also for an application within it, thus allowing to set different indexes for a super workplace which contains multiple searches. An example would be an ADF workplace that has a depot search and a bounce workplace which use different indexes. Bounce Solution l Extended internal/external bounce error classification configuration available Different e-mail sending applications recognize a problem at different stages in the sending process. Some might recognize an invalid e-mail already before sending - classifying the error as internal - while others realize the problem only later. For this case the new attribute Set source task to error was added to the Print and e-delivery bounce settings in V7.6 SP3. Activating this option results in the source (email) task also being set to error in case of an external bounce. l Extended auto-response (Out of office) handling So far the out of office use case only was triggered if: - Enable out of office extraction on the PED Bounce Extractor tool is activated. - Keywords defined in attribute Out Of Office Keywords of the PED Bounce Extractor have been found in the email. - The original outgoing mail is found in the unresolved queue. Now also the use case that a recipient is using out of office keywords without a matching source mail is handled. For details, see chapter "Out of office handling/recognition" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". getstartede V7.6 SP3 81/389 Updates in V7.6 SP3 11.3.2 Information relevant for business users Bounce Solution l Bounce actions can no longer be skipped without confirmation Until V7.6 SP3 it was possible to skip the execution of the bounce action. If now an action for a bounce reason is available, the user must click OK in a confirmation dialog, if the bounced task should be set to resolved without executing a bounce action. 11.4 Papyrus Business Capture Solution 11.4.1 Information relevant for administrators and developers l Capture document samples solution: Tokens not generated for two document types Previously, tokens were not generated for the document types CreditCardChangeForm and CreditCardBlockingForm of the Capture document samples solution. As of the version v7.6 SP3 tokens are created for these document types. l Rule folder Routing rule not linked after method "Check rules" After the execution of the method Check rules on a new document type, in certain cases, the routing rule was not referenced from the document type GENERAL to the new document type. This has been fixed in the version v7.6 SP3. Method "Check rules" fails The method Check rules of the Rule folder did not work when executed on a Rule folder with an existing active version. This has been fixed in the version v7.6 SP3. l Document extraction: Layout extraction does not work if already set on document instance When a capture document already was extracted once and additionally to the document type also a document layout was set on it, then it was not extracted again (but skipped), if the capture task was restored (or a new task created using the same capture document instance) and processed a second time in the extraction queue. This has been fixed in the version v7.6 SP3. l Document extractor tool: Start Capture Designer from extraction definition When the Capture Designer is started with the method Design from an extraction definition below the Document extractor tool, as of version v7.6 SP3, there are several options to load sample documents: n Test sample folder of the corresponding document type n Capture document from a task in a queue if the extraction definition has been referenced into the queue n Capture image folder linked as child of the extraction definition For details, see the chapter "Load sample documents into the Papyrus Designer Capture" in "Designer Capture Application Developer Guide (pcddge)". getstartede V7.6 SP3 82/389 Updates in V7.6 SP3 l Extraction definition Language specific keywords not returned When the binary path contained a dot somewhere, then the *.wfl language files where not found by the Capture Designer, which resulted in a failure to find language specific keywords. Fixed in the version v7.6 SP3. Region anchor-based pattern extraction An extraction definition defining the extraction of repetitive text blocks used a region anchor to define the region of the text blocks in an auxiliary field. This auxiliary field in turn was used as data root for a document class. An element of this document class searched for an amount within the repetitive text blocks, which was not successful because the input of the data root was not looped correctly. This has been fixed in the version v7.6 SP3. l Text processors: New attribute for "Split text" As of the version v7.6 SP3, the text processor Split text has been provided with an additional attribute Split mode which now allows to split a text block into sub-blocks depending on the distance between lines. For details, see "Split text" in "Designer Capture Application Developer Guide (pcddge)". l Internal rules New attributes for "useBiggest" As of the version v7.6 SP3, the internal rule useBiggest has been added the new attributes MergeNeigbourLineMode and MergeNeighbourMaxDist which allow to merge adjacent lines when this processor is used. For details, see "UseBiggest" in "Designer Capture Application Developer Guide (pcddge)". New attribute for "useSmallest" As of the version v7.6 SP3, the internal rule useSmallest has been added the new attribute InLine which allows to select matches in different lines. For details, see "UseSmallest" in "Designer Capture Application Developer Guide (pcddge)". 11.4.2 Information relevant for business users Information relevant for Papyrus Client Capture users l Completion view Manual setting of zoom factor failed Manual setting of the zoom factor of the data viewer by typing in the new value did not work on the Completion view and the Extended Completion view of the Capture UI "Capture workplace". This has been fixed in the version v7.6 SP3. Zoom factor settings ineffective If the Capture BDC Eye Widgets settings attribute "Completion view page zoom mode" was set to 5: Custom Zoom Factor, then the additional attribute "Completion view page zoomf actor" is shown which allows the setting of the zoom factor to be used. But this setting has no effect. Regardless of this setting the previously used zoom factor is used after relogin. This has been fixed in the version v7.6 SP3. l Extended completion view: Source document selected after split According to the specification, when a document has been split, then none of the resulting documents should be selected. Instead, the remainder of the source document was selected on the Extended completion view. This has been fixed in the version v7.6 SP3. l Capture administration workplace: Button "Unlock document" not available If a document was locked on the extended completion view and unlocked on the Documents view of the Capture administration workplace, then again locked on the extended completion view, then the button "Unlock document" was not available. This has been fixed in the version v7.6 SP3. getstartede V7.6 SP3 83/389 Updates in V7.6 SP3 Information relevant for Papyrus Client Scan application users l Scanned items thumbnails viewer Wrong buttons displayed When a document was linked below another one in the Scanned items panel of the Scan view, wrong buttons were displayed on the toolbar of Scanned items due to incomplete evaluation of preconstraints. This has been fixed in the version v7.6 SP3. Document and page count empty When there were no documents in the staging queue of the Scan receiver, then the document and page count of the Scanned items thumbnails viewer was empty. As of version v7.6 SP3 the document and page count is 0. Information relevant for Papyrus Business Designer for Capture users l Capture business administrator workplace Warning message during extraction During the extraction of a document on the Capture business administrator workplace the form is locked. Before unlocking it, sometimes an inconsequential warning message was displayed for a brief moment. This has been fixed in the version v7.6 SP3. Content view folder cannot be collapsed If an object on a lower level was selected in a Content view folder, then the parent folder could not be collapsed. This has been fixed in the version v7.6 SP3. Wrong locking information If a document type filter was applied that excluded the previously selected document type, then the previous locking information was displayed after filtering. This has been fixed in the version v7.6 SP3. JPG samples could not be trained Due to transformation issues, sometimes it was not possible to train (extract) certain JPG samples. During training a warning message was issued that the data could not be re-read. This has been fixed in the version v7.3 SP3. l Capture business designer solution: Method "Check rules" fails When a new document type and elements were created with Capture business designer, the method "Check rules" which provides the rules for new elements, did not work properly. This has been fixed in the version v7.6 SP3. l Table definition Multi-line column header supported As of the version v7.6 SP3, the table definition of the Capture Business Designer supports the selection of text that covers more than one line as keywords for column headers. For details, see "Define all non-key columns of the table" in "Papyrus Business Designer Document Capture Business Administrator Guide (popcfbdae)". Column header names must be unique in multi-table definitions For the version v7.6 SP3 the following restriction applies: When defining more than one table in a document type definition, the column header names must be unique for all defined tables, otherwise the column headers will not be correctly trained and the extraction will deliver incorrect results. getstartede V7.6 SP3 84/389 Updates in V7.6 SP3 11.5 Papyrus Business Correspondence Solution 11.5.1 Information relevant for administrators and developers Improvements are provided with this service pack and affect the following use cases: l Data read settings (CF Developer): Retrieve data values from a line data object or data read setting When the useDataInfo check box is selected, the data values are retrieved from the data read setting. If the useDataInfo check box is not selected the data values are retrieved from the line data object located on the DOCUMENT material. This is fixed with V7.6 SP3. l Papyrus Business Designer authorization (CF Template Administrator): Papyrus Business Designer authorization not freed on exit The product authorization was not freed on exit under certain circumstances like opened tabs. This is fixed with V7.6 SP3. l PDF Form submit button (CF Clerk): Submit button displayed with the wrong characters An unrecognizable character set was used for the Submit button text for the PDF (dataPdfBinary object). This is fixed with V7.6 SP3. 11.5.2 Information relevant for business users Improvements are provided with this service pack and affect the following use cases: Papyrus Business Designer for Correspondence l Table design building block: n Font and color options for Output building block were not applied When the template administrator used a Table design building block and selected options from the Color and Font drop-down lists on the Expert tab for the Output building block, the color and font were not applied. This is fixed with V7.6 SP3. n Calculation of subtotal was not correct When the template administrator used a Table design building block, the subtotal was not calculated correctly. This is fixed with V7.6 SP3. l SIT and UAT test phase: comment subject for test items was not editable When testers working with items of a release changed the user interface language to a language other than English, it was not possible to edit the subject of a comment. This is fixed with V7.6 SP3. l Wizards: n Changes to default name deselected the existing translations When template administrators edited an existing wizard and changed the entry in the Default field of the Translate dialog for the wizard name, the existing translations were deselected. This is fixed with V7.6 SP3. n Adding a building block with variables to a wizard step was not possible If a building block containing variables that were already used in the wizard document was added in a wizard step, the building block action was not shown in the wizard. This is fixed with V7.6 SP3. l Settings: adding a new language for a user led to error message After a new language was added for a CF Template Administrator user, an error message was displayed when the user changed to or used this language. This is fixed with V7.6 SP3. getstartede V7.6 SP3 85/389 Updates in V7.6 SP3 l Simple search: single quotation marks in search field led to error message When template administrators started a search with single quotation marks in the search field of the Simple search and then created or duplicated a building block, an error message was displayed. This is fixed with V7.6 SP3. l Document preview: "Paragraph" toolbar was not shown with all buttons after login When template administrators or clerks logged in and edited a text variant or worked in an input field, trying to use the Paragraph toolbar, not all buttons were displayed. This is fixed with V7.6 SP3. l Layouts: editing a document with a layout using a text variant defined as user input field led to error message When a document used a layout containing a text variant that was defined as user input field (prompted), an error message was displayed. This is fixed with V7.6 SP3. l Text variants: links defined with an expression (variable) did not show the variable value When a link was inserted by clicking the Insert link button and selecting the Enable expressions check boxes for the link and the tooltip, the variable name was shown and not the content of the variable. This is fixed with V7.6 SP3. Papyrus Client for Correspondence l Stickers: were not saved when document was closed When clerks and supervisors created stickers for a document and then closed the document and edited it again, the stickers were gone. This is fixed with V7.6 SP3. l Document preview: "Paragraph" toolbar was not shown with all buttons after login When template administrators or clerks logged in and edited a text variant or worked in an input field, trying to use the Paragraph toolbar, not all buttons were displayed. This is fixed with V7.6 SP3. 11.6 Papyrus Mobile Solution 11.6.1 Information relevant for administrators l Renamed ACM mobile applications setting: Restful ACM Settings To ensure that the desired ACM Application Libraries are displayed in ACM-related dashboard applications, e.g. Cases Dashboards of the mobile app, one or more libraries have to be selected in the Restful ACM Settings. This setting was previously called Mobile ACM Dashboard Settings. This setting has the following two attributes: n ACM Dashboard Application access: To display the desired ACM Application Libraries in the ACM-related dashboard applications n Inbox Content Form Attributes: To define the attributes to be shown in the Content Details form For more details see "Filter ACM application libraries" in "Mobile Application Administrator Guide (pomaage)". 11.7 Papyrus Reporting Solution 11.7.1 Information relevant for business users Papyrus Business Designer for Reporting getstartede V7.6 SP3 86/389 Updates in V7.6 SP3 l Report document administration workplace Deselect items of document properties listboxes failed If document properties were used to select a batch table for serial letter generation it was not possible to deselect it on the Report document administration workplace. Fixed in the version v7.6 SP3. Adding new reporting building blocks to active document template failed When trying to add additional building blocks to an activated document template, it was not possible on the Reporting UI. Fixed in the version v7.6 SP3. l Dashboard view: Settings stored obsolete data When performing several changes in the dashboard view settings it could happen that obsolete data, e.g. table reference kept stored in the dashboard view settings, which might trigger an error when later trying to delete this table from the report. Fixed in the version v7.6 SP3. 11.8 Papyrus Client AFP Viewer l Corrected rotation of Human Readable Information (HRI) information in barcodes In some cases it could happen that characters in the barcodes using HRI were rotated incorrectly. This issue was solved with v210522_v763 and now all characters with HRI information are displayed correctly. getstartede V7.6 SP3 87/389 Updates in V7.6 SP3 11.9 Papyrus Designer, Papyrus DocEXEC 11.9.1 Information relevant for administrators l Papyrus Designer: Display of command tree improved The display of the command tree in Papyrus Designer's Format group definitions and Document format definitions windows was improved with regard to the display of the Text command content. This is fixed with V7.6 SP3. Font selection in the "Font definitions" dialog improved The Papyrus Designer font selection option in the Font definitions dialog did not display the correct AFP raster fonts in some cases. Under certain conditions, also fonts were displayed whose resolution did not match the defined resolution of the AFP. This is fixed with V7.6 SP3. Display of imported PDF in the generated output AFP Papyrus Designer option Generate and view did not display imported PDF in the generated AFP in some cases. (The Generate and view as PDF option has always shown imported PDF.) The issue is fixed with V7.6 SP3. "End document" in "Outline section" causing endless loop in Papyrus Designer If an End document command was placed in the middle of an active Outline section, which had an AFTERBREAK or FOOTER section, then it caused an endless loop. Papyrus Designer froze with abnormal termination but without dump. The issue is fixed with V7.6 SP3. Abnormal Papyrus Designer termination at generation of PDF with entry fields Between V7.6 and V7.6 SP2, Papyrus Designer could run into abnormal termination when a PDF with text entry fields (prompts) was generated by Generate and View. The issue is fixed with V7.6 SP3. Resource file creation in wrong directory at secondary AFP output generation Papyrus Designer did create the resource files, which were not to be concatenated, of a secondary AFP output file (Define output definition) in the wrong directory. Papyrus Designer created the reasource files in the working directory of the program instead of the output directory, where also the primary AFP file was written to. This is fixed with V7.6 SP3. l Compatibility parameters V719_COMP_PDF_MULTILINEPROMPT The compatibility parameter V719_COMP_PDF_MULTILINEPROMPT sets back Papyrus DocEXEC's behavior of processing single line or multiline prompts in PDF to the behavior of DocEXEC versions 7.1 SP9. The parameter did not work correctly with 7.6 SP1, but this was fixed with V7.6 SP3. For more information, see chapter "DEV719_COMP_PDF_MULTILINEPROMPT / V719_COMP_PDF_MULTILINEPROMPT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". getstartede V7.6 SP3 88/389 Updates in V7.6 SP3 11.9.2 Information relevant for DOCDEF developers l Bar charts: "ChartInfo" option "InVal" was corrected and enhanced In case of small columns it could happen that the values inside the columns were not easily readable and distinguishable. In versions before 7.6 SP3, the values were placed in the middle of the column anyway. Now, this behavior was corrected, and in case of small columns, the values are placed above or below the columns. If there is not enough space for all values, the unreadable values are omitted at all. For more details on ChartInfo, see "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)". Endless loop with certain combinations of "LineThickness" and "3D_DepthAngle" in cylinder charts In certain combinations of LineTickness and 3D_DepthAngle values in cylinder charts, Papyrus Designer and Papyrus DocEXEC ran into endless loop and froze without dump. The loop happened when the lines were overlapping, which can be the case with certain 3D_DepthAngle values in combination with a line thickness definition. The issue is fixed with V7.6 SP3. l Resource group: Resource group not correctly created when resources imported by IOBDLL were involved In certain situations, the resource group was not formed correctly when resources imported by IOBDLL (e.g. PDF objects or images) should be included. Although in Application output format dialog the PSG flag had been set for the Resource group, the resources imported by IOBDLL were not imported when a resource from another resource type was written to the resource group for the first time after the IOBDLL resource had been imported and the other resource type was not defined being part of the resource group. For example, the Application output format dialog has set the PSG flag and it has not set the FON flag. This means the resource group should contain resources imported by IOBDLL among others but not font resources. Assume the formatting process places some text in a certain font on a certain page and an IOBDLL-imported image. And on a page following, the formatting process places more text but this time in another font and the font is used here for the first time. In this situation the IOBDLL-imported image was not included in the resource group although it should have been according to the definition. Whether or not the resource file was concatenated did not matter. The issue was present between V7.5 SP2 and V7.6 SP2, and is fixed with V7.6 SP3. l PDF generation: Increasing memory consumption by GenerateTags="YES" When a project generated PDF without PDF/UA but DocEXEC main profile parameter GenerateTags was set to "YES", then the memory consumption was constantly increasing during generation. Both Papyrus Designer as well as Papyrus DocEXEC suffered from the increasing memory demand. GenerateTags is set to create the structure information in the AFP necessary for creating PDF/UA-compliant PDF documents. The issue was present between V7.5 SP2 and V7.6 SP2, and is fixed with V7.6 SP3. getstartede V7.6 SP3 89/389 Updates in V7.6 SP3 l Variable representation: Represented variables referencing each other cause PPDE7365E error message The Description command allows to define socalled represented variables. Represented variables are used in Papyrus Client Canvas within a Papyrus Business Correspondence Solution in order to output a variable value not just as such but as a string with a potential complex formatting. The Description command allows to define the formatting pattern for such represented variables. In case there are two such formatting patterns with mutual references, the PPDE7365E Representation handling for VAR1 has a cyclical recursion is displayed, as soon as the variables are used in a output command like Text, Text prompt, Output or Place. "Mutual referencing" means that the one variable is used in the formatting pattern of the other variable. Mutual referencing of represented variables is a situation which should be avoided in general. Papyrus DocEXEC and Papyrus Designer versions prior to V7.6 SP3 reacted differently to this situation. Not only did they display the error message but also had abnormal terminations or wrong calculation of the represented variables' values. The issue is fixed with V7.6 SP3. Incorrect PPDE7365E error message display when represented variable was used more than once in a condition If a represented variable was used more than once in a condition - which is a valid definition - then the PPDE7365E Representation handling for VAR1 has a cyclical recursion was displayed. This error message was misleading. Given that the variable 'A' is a represented variable, a condition statement like IF A>1 AND A<5 would have caused the incorrect display of the message. This incorrect reaction was present between V7.6 and V7.6 SP2 and is fixed with V7.6 SP3. 11.10 Papyrus Objects for WebRepository/WebControl 11.10.1 Papyrus Depot Depot search workplace l Update Depot search settings to latest index visible to user via button Whenever a new version of an index is created, its object ID changes. Thus it is necessary to update the following attributes in Depot search settings: Index selection, Select search attributes, Select return attributes, Select export attributes and Select details attributes to reflect this change. Starting with V7.6 SP3 this can be done more conveniently by the new button Update Depot search settings in the Settings Explorer, which is available in the top right when the Depot search settings are selected. For details, see chapter "Define indexes to use" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Index selection dependent on workplace fixed In previous versions the Default index dependent on workplace setting did not work in some cases. This has been fixed with V7.6 SP3. Furthermore it is now possible to also set the index with a finer granularity. It can not only be set for an entire workplace but also for an application within it, thus allowing to set different indexes for a super workplace which contains multiple searches. An example would be an ADF workplace that has a depot search and a bounce workplace which use different indexes. getstartede V7.6 SP3 90/389 Updates in V7.6 SP3 11.10.2 Papyrus Objects System 11.10.2.1 Information relevant for administrators l Timezone issue in SUSE Linux Enterprise Server (SLES) 12 SP5 Because of a timezone issue in SLES 12 SP5, time display and time saving in Papyrus applications that run on 32-bit nodes may be incorrect. Instead of the respective local time zone, only the UTC is passed on to the kernel by the operating system. This affects all time queries made by the respective kernel. As a result, changes in objects are stored with the incorrect time. For example, if user interfaces based on Papyrus EYE Widgets access such objects, the time will then also be displayed incorrectly. One way to get around this mistake is to set the environment variable TZ to the UTC offset for the current local time. The calculation of the time zone for TZ uses positive offsets for locations to the west and negative to the east of UTC. For example, set the environment variable to export TZ=UTC-1 in order to get Central European Time (CET). Consider also the current daylight saving when setting the variable. In order to get the correct CET in summer, for example, set export TZ=UTC-2. Another way to get around the problem is to install a timezone database in "fat" format, which is supported by the 32-bit Linux library glibc. The actual technical reason for the issue is a inconsistent installation for 32-bit processes and relates to SUSE's 32-bit runtime library glibc (respectively the format of the timezone database files). The 32-bit glibc cannot read the "slim" format of the current timezone database files and thus assumes UTC. (For a 64-bit glibc the "slim" format is supported and 64-bit processes successfully determine the correct timezone.) l Alternative domain search protocol: TCP instead of UDP By default UDP is used for the domain search between the domain controller and its client nodes. If your network has UDP not enabled, it is possible to change the protocol for the domain search from UDP to TCP with command-line parameter ChangeDomainSerachProtocol. This feature is available since v7.6. For details, see "ChangeDomainSearchProtocol" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". 11.11 Papyrus Server 11.11.1 AFP to PDF l Papyrus Server AFP to PDF available in 64-bit mode With 7.6 SP3, Papyrus Server AFP to PDF is also available in 64-bit mode. For more information, see "64-bit Software Installation Installation and Administrator Guide (gen64iage)". l Convert PDF description fields to UTF-8 (codepage 1202) by new parameter With 7.6 SP3, the new PdftDescriptionCdp parameter was introduced. If set to a positive value it converts the following PDF description fields to UTF-8: Title, Subject, Author and Keywords. UTF-8 enables you to enter country-specific or special characters in the descriptive fields. Otherwise the system codepage is used. This parameter is only available for the creation of direct PDF output by Papyrus DocEXEC or Papyrus Designer. When using the Papyrus Server AF to PDF always the system codepage is used for coding these fields. For more details, see chapter "PdftDescriptionCdp" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". getstartede V7.6 SP3 91/389 Updates in V7.6 SP3 l PDF/UA generation improved With V7.6 SP3, PDF/UA document generation became significantly faster and uses less memory, thus avoiding potential dumps and crashes. In general PDF/UA is intended for small documents directly sent to end users who might be needing the assistive technologies and not for high volume jobs producing thousands of pages. Generating PDF/UA-compliant documents will always cost performance, require more runtime memory and produce larger files than generating non-PDF/UA-compliant documents. l Single line or multiline text prompts in a PDF The compatibility parameter V719_COMP_PDF_MULTILINEPROMPT sets back Papyrus DocEXEC's behavior of processing single line or multiline prompts in PDF to the behavior of DocEXEC versions 7.1 SP9. As the parameter was not correctly working with 7.6 SP1, this has been fixed with V7.6 SP3. For more information, see chapter "DEV719_COMP_PDF_MULTILINEPROMPT / V719_COMP_PDF_MULTILINEPROMPT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 11.11.2 PCL l lpr job name - new parameter This parameter allows to define a string that is printed on the banner page. It was added with V7.6 SP3. For details, see chapter "lpr job name (PCLLprJobName)" in "Papyrus Server - PCL Reference Guide (psepclrge)". 11.12 OverView Image Editor l Solution to a printing problem due to a Windows 10 update available Due to a Windows 10 update from March 2021 it might happen that, if you print via "Microsoft print to PDF" or via "PDF24", only a blank page is generated with an increased file size compared to the correct output. A solution to this problem can be easily performed. For more details, see chapter "File | Print" in "Image Editor Reference Guide (oierge)". getstartede V7.6 SP3 92/389 Appendix: main updates in V7.5 12 Appendix: main updates in V7.5 If you upgrade from an earlier version to the newest version, use the appendix to see a history of all changes that have accumulated. Note that the cross-references in the appendix refer to chapters in documents of the same version. This means that some of the History of Changes entries in the appendix may include cross-references to chapters that do not exist anymore in the newest version of the document or whose information was updated in the meantime. If you are in such a case interested in the details you will need to access the documents of exactly that version. 12.1 Main updates in V7.5 This delivery includes Papyrus products in release level V7.5. 12.1.1 General changes l Papyrus software in 64-bit version The 7.5 release includes following software components also as 64-bit version in the standard delivery: n Papyrus DocEXEC - Fully available in 64-bit n Papyrus Archive module (WebArchive AFP Splitter and Check-in) - AFP document database check-in using PAS DLL n Papyrus Objects Kernel for - Domain Controller - IPAS - Application Server Nodes (Papyrus Portal, Papyrus Type Manager) The installation and configuration of software components is described in a separate document, which is released with 7.5 for the first time. For more information,see "64-bit Software Installation Installation and Administrator Guide (gen64iage)". l New document: Papyrus WebRepository - Ontology Framework Business Analyst and Developer Guide (pontbadge) This document describes how to design, create and work with Papyrus business ontologies. Ontologies enable business users to query application data with the businessies terminology used in the specific domain instead of technical jargon. In the language that an ontology defines, you can also write business rules for adaptive workflows that must fulfill business constraints or regulatory requirements. l New document: Papyrus WebRepository - DOCDEF Migration to Correspondence User Guide (pocfmage) This document provides guidance for system administrators on how to migrate a file-based DOCDEF application to a Papyrus WebRepository, to create a Papyrus Business Correspondence Solution. This can be a Papyrus Objects solution based upon Papyrus WebRepository, or creation of a hybrid solution that uses Papyrus WebRepository and the Correspondence Framework, or solution that sees the initial migration to Papyrus WebRepository, then a further integration with the Correspondence Framework. l New document: Papyrus Designer Capture Application Developer Guide (pcddge) This document describes the newly released Papyrus product Papyrus Designer Capture which combines the power of the Papyrus products Papyrus Capture Designer/FixForm and Capture Designer/FreeForm. The new product allows the Capture developer to create document types (document definitions) for any kind of input documents. FixForm projects are seamlessly usable in the Papyrus Designer Capture whereas FreeForm projects have to be migrated. getstartede V7.6 SP3 93/389 Appendix: main updates in V7.5 l New document: Papyrus Business Designer Document Capture Administrator Guide (popcfbdae) This document describes installation and usage of the new Papyrus Product Papyrus Capture Business Designer which allows the business user to define document types for a Capture solution without requiring expert knowledge. l Papyrus Server PDF-in renamed to Papyrus PDF-in The module was renamed to reflect its much wider range of application. The corresponding PDF manual is now called Papyrus PDF-in Reference Guide (ppdfinrge).pdf and can be found in a new separate Papyrus PDF-in folder. It still covers all the parameters required for successfully converting PDF documents into AFP documents and resources. Papyrus PDF-in is also required if generated PDF documents should have PDF resources embedded natively (i.e not as images). Two typical use cases, which are covered in their respective manuals, are: n Papyrus DocEXEC direct PDF output, when a PDF is imported during the DocEXEC run n Papyrus Server AFP to PDF conversion process, when the AFP contains a PDF l Spellchecking: suppress highlighting of compound words with SpellcheckCompoundWords Parameter SpellcheckCompoundWords allows to switch the spellcheck of compound words. This means the spellchecker should either highlight (=mark as misspelled) or not highlight compound words. Compound words are words that consist of single words known to the spellchecker, for example: "Thisisalongpieceoftext" is a compound word. For more information, see chapter "SPELLCHECKCOMPOUNDWORDS" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)" and "Overview of spellchecking and hyphenation parameters on DOCUMENT material" in "Spellchecking and Hyphenation Installation Guide (spellhyphe)". 12.1.2 OverView Image Editor l New functionality: Select all With the newly implemented functionality Select all in the Tools menu, you can select the whole image at once. Alternatively, you can press [Ctrl]+[A]. For more details, see chapter "Tools | Select all" in "Image Editor Reference Guide (oierge)". l New functionality: Crop With the newly implemented functionality Crop in the Image menu or the new button in the Drawing toolbar, you can remove a white frame around an image. For more details, see chapter "Image | Crop" in "Image Editor Reference Guide (oierge)". 12.1.3 Papyrus Adaptive Case Management Solution 12.1.3.1 Information relevant for business users l Introducing ACM Business Designer The user guide "Papyrus Client - Adaptive Case Management User Guide" was renamed into "Papyrus Business Designer and Papyrus Client - Adaptive Case Management User Guide" in order to reflect the introduction of the Papyrus Adaptive Case Management Business Designer and release and change management for ACM with version 7.6. 12.1.4 Papyrus Analysis Toolkit l AFP Lister: new command line parameters As of this version two new command line parameters are available: /x and /o. For details, see chapter "Call from the command line" in "Analysis Toolkit Application Developer Guide (pandge)". getstartede V7.6 SP3 94/389 Appendix: main updates in V7.5 l AFP Lister: structured fields output BPT/EPT instead of BCT/ECT Until the previous version the Lister output displayed structured field BCT/ECT (Begin/End composed text) instead of BPT/EPT (Begin/End presentation text) which had been renamed quite some time ago, but Lister still displayed the old names. Now Lister displays BPT/EPT. For details, see chapter "Selected AFP structured fields" in "Analysis Toolkit Application Developer Guide (pandge)". l PUC settings: Custom theme colors PUC settings have been extended by a new set of attributes for customized color themes used by UC Compare classes. For details, see chapter "PUC (PAPYRUS UNIVERSE COMPARE) (UcSettings)" in "Analysis Toolkit Application Developer Guide (pandge)". 12.1.5 Papyrus Automated Document Factory Solution 12.1.5.1 Information relevant for business users ADF workplaces l Completely redesigned user interface The new user interface introduces separate workplaces for ADF jobs and ADF queues, replacing the previously used tabs with a better structure and organization of use cases. These new workplaces offer many new features like a task creation wizard and greatly increased monitoring capabilities. Furthermore they have been optimized for a more intuitive user experience. For details see chapter "Job operations workplace" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)" and "Queue cockpit workplace" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)". Depot search workplace l Filter in search results The business user is now able to narrow down the search by entering criteria in the fields above each column of the result list. For details, see chapter "Depot search workplace" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)". l Hide details tab This new setting allows to control whether the details tab is part of the result details or not. The details tab displays the index object that belongs to the hit you selected in the result list. In a lot of cases the business user should only see the objects below the index object (e.g. a PDF document) and not the index itself. For details, see chapter "Depot search workplace" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)". l PDF View no longer blocks typing in the search mask In a previous release viewing a PDF on the right side of the Depot search could prevent the search mask from accepting any input. This has been fixed. l Simple vs. Advanced search Switching between these two modes is now done via the More menu instead of a drop-down list. l Details tab is now cleared after a search without hits In a previous release the Details tab showed the index object of the last search. This has been fixed. getstartede V7.6 SP3 95/389 Appendix: main updates in V7.5 Bounce handling workplace l "Preview of the outgoing communication" area fixed In a previous release the "Preview of the outgoing communication" area showed in some rare cases the error message "invalid index in array". This has been fixed. l "Resolved" and "Suspended" button visibility fixed In a previous release these two buttons were sometimes not visible, when they were required. This has been fixed. l Recognition and handling of "Out of Office" improved In a previous release auto reply messages (=bounces) that were recognized as out of office messages, were marked as such, but still moved to the unresolved queue. Now they are immediately moved to the Out of Office queue. Messages in the Out of Office queue still can be moved to the Unresolved queue and follow-up actions can be triggered. Furthermore the parsing of bounces was improved to recognize more messages as Out of Office. 12.1.5.2 Information relevant for administrators and developers Automated Document Factory Solution l Workplaces: migration to a new Papyrus EYE Widget workplace engine with V7.5 As of V7.5 a new engine for running UIs based on Papyrus EYE Widgets has been introduced. The new engine is called Papyrus EYE Widgets v5 and brings improved maintainability, performance, reliability and component handling as well as iterative design and easier reuse of data interfaces. Already existing applications on Papyrus EYE Widgets v4 remain compatible but an update to v5 can be made. For more details about the migration, see chapter "Migration to Papyrus EYE Widgets v5 engine" in "EYE Widgets Developer Guide (popeyewdge)". l New workplaces for ADF operators These new workplaces offer many new features like a task creation wizard and greatly increased monitoring capabilities. This leads to new options that have to be configured using the Settings Explorer and a slightly modified user creation wizard. For details see chapter "Configuration in Settings Explorer" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)" and "Creation of user accounts" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". getstartede V7.6 SP3 96/389 Appendix: main updates in V7.5 Print and E-Delivery Solution l Ignore missing indexes This attribute was introduced on the PedScheduledActionBundle class. It is selected per default and allows the Print and E-Delivery Solution to operate more fault tolerant during bundle runs. For details see chapter "Configure a scheduled action" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l PED CSV importer via method call A method was introduced to create and configure a PED CSV importer. This is an alternative to clicking the method button on the PED PQL collection and manually configuring the importer. For details see chapter "PED CSV importer" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Split email address This new attribute was added on the PedRuleDefinition class to improve bounce handling in case a PED task contains multiple e-mail addresses. When activated it creates a separate task for each address allowing individual tracking. For details see chapter "PED rule setup" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Flexibility of SMS outbound channel increased The text and telephone number can now be read from an index, which allows to use one rule for multiple purposes. For details see chapter "SMS" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Bounce Handling Solution l Distinguish manual and automatic extraction In case an undelivered message was set to resolved, there was no possibility to differentiate between automatically processed bounces and manual intervention. As this can be of relevance for reporting an additional attribute "Extracted by" was introduced on the AdfBounceTask class. For details see chapter "Reporting ready" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Depot search workplace l Index classes as search index Until V7.5 the search index was solely selected from the index templates in depot search application container. With V7.5 it is additionally possible to define index classes to use as search index. By selecting an index class all index templates using this class are used for the search. Furthermore a default index can be enabled for each workplace. For details, see chapter "Define indexes to use" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Indexes in development for search The methods EnableDevelopmentVersions and DisableDevelopmentVersions were implemented on the DepotSearchContainer. Thus it is no longer necessary to write a PQL, but instead click on the method button on the Depot search container of the user. For details, see chapter "Provide the workplace to business users" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". getstartede V7.6 SP3 97/389 Appendix: main updates in V7.5 12.1.6 Papyrus Business Capture Solution 12.1.6.1 Information relevant for administrators and developers l New product Papyrus Designer/Capture As of version v7.5 Papyrus Capture Designer/FixForm and Papyrus Designer/FreeForm are replaced with Papyrus Designer/Capture. Likewise, Papyrus Capture Server/FixForm and Papyrus Server/FreeForm are replaced with Papyrus Recognition Server. The documentations for Papyrus Capture Designer/FixForm and Capture Designer/FreeForm are still delivered in English. For more details, see chapter "Migration from FixForm/FreeForm to Papyrus Designer Capture and Capture Recognition Server" in "Designer Capture Application Developer Guide (pcddge)". l Papyrus Designer Capture/Papyrus Recognition Server: Reco engine "Omnifont4" not delivered any longer As of version v7.5 the recognition engine Omnifont4 ceases to be delivered because Abbyy stopped the support. This change also affects the reco processor FullPage which uses Omnifont. Customers that use Omnifont can continue to use it. However, Papyrus Software recommends to switch to another available recognition engine. l Reco processor "Colors": added grey-scale recognition In addition to colors now recognition processor "Colors" also can be configured to recognize grey-shades. The following new attributes have been added to enable grey-shade recognition: mode, min. grey brightness, max. grey brightness, and max. grey saturation. For details, see section "Colors" in "Designer Capture Application Developer Guide (pcddge)". l Normalization processor "Color depth/recognize and tag colors": added grey-scale recognition Now normalization processor "Color depth / recognize and tag colors" can also be used to tag grey-shades and having them selected with processor "Color depth/select tagged color". The following new attributes have been added to enable grey-shade recognition: mode, min. grey brightness, max. grey brightness, and max. grey saturation. For details, see section "Color depth / recognize and tag colors" in "Designer Capture Application Developer Guide (pcddge)". l Reco processor "Tesseract4": new parameter "MergeResults" The new parameter MergeResults has been added to the reco processor Tesseract. Additionally, the values of parameter PageSegmentMode have been reduced to four options. For details, see "Tesseract4" in "Designer Capture Application Developer Guide (pcddge)". l Reco processor "FullPageNew": new parameters The new parameters Inversion detector and Delta have been added to the reco processor FullPageNew. Additionally, the parameter Validate handprint too has been removed. For details, see "FullPageNew" in "Designer Capture Application Developer Guide (pcddge)". l Papyrus definition set for invoices: improved features Papyrus definition set for invoices has been improved for better performance (ZIP code pattern and address detection extended; additional keywords for date locator in multiple languages (English, German, Italian, Dutch); extended patterns for IBAN and BIC). getstartede V7.6 SP3 98/389 Appendix: main updates in V7.5 l Workplaces: migration to a new Papyrus EYE Widget workplace engine with V7.5 As of V7.5 a new engine for running UIs based on Papyrus EYE Widgets has been introduced. The new engine is called Papyrus EYE Widgets v5 and brings improved maintainability, performance, reliability and component handling as well as iterative design and easier reuse of data interfaces. Already existing applications on Papyrus EYE Widgets v4 remain compatible but an update to v5 can be made. For details about workplace replacement, see chapter "Migration of Eye Widgets workplaces from Eye Widgets v4 to Eye Widgets v5" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". For more details about the migration, see chapter "Migration to Papyrus EYE Widgets v5 engine" in "EYE Widgets Developer Guide (popeyewdge)". l Capture Solution utilities: Capture Reporting Version v7.5 introduces the feature Capture Reporting which allows the Capture administrator real-time status monitoring of an operative Capture Solution. For details, see chapter "Capture reporting" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Test sample folder/Training sample folder: add test sample/training sample by drag and drop Now it is possible to add a test sample/training sample to Test sample folder/Training sample folder of a document class simply by drag and drop of a Capture document onto the Test sample folder/Training sample folder. For details, see chapter "Sample folder (CapSampleFolder)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Add adapter to solution wizard: Check for tenant A check for tenant has been added to add adapter to solution wizard to list only solutions as possible target of the adapter instantiation which have a tenant set.. Up to this version a solution without tenant could be selected but the wizard would have run into error. For details about Add adapter to solution wizard, see "Setup a Capture Solution with the Capture solution creation wizard" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Administration workplace: Document depot search on all nodes Until now the search in the document depot on Depot depot view of Capture administration workplace was done exclusively on the depot node(s). Now also the workflow node(s) and scan node(s) are included in the search, thus returning also documents which are not yet committed but still in local staging queues or documents of import adapters which are located on the workflow node and not yet relocated. l Tool Document-to-PDF: new parameter attributes The material Capture convert Doc to PDF (CapConvertDocToPdf) corresponding to the tool Doc to PDF (DocToPdf) has been provided with to additional parameter attributes PdfCompliance and TextEncoding for special use cases. For details, see chapter "DOC TO PDF (DocToPdf)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". 12.1.6.2 Information relevant for business users Information relevant for Papyrus Client Capture users l Capture Business Designer user interface: Capture clerk Version v7.5 introduces the new Capture Business Designer application. Capture Business Designer UI Capture clerk is the user interface of this new application for the user type Capture clerk. For details, see chapter "Capture Business Designer UI "Capture business clerk"" in "Papyrus Client - Capture User Guide (popcfuge)". getstartede V7.6 SP3 99/389 Appendix: main updates in V7.5 l New Papyrus product Version v7.5 introduces the new Papyrus Capture Business Designer application. This new Papyrus application based mainly on Capture Framework as well as ACM (Adaptive Case Management) enables the business user to design document types for a Capture Solution without requiring technical knowledge. l Capture business designer solution: known issues in version v7.5 When installing a new Capture business designer solution, two minor issues have to be minded: WebServer Eye and Document depot on different nodes WebServer Eye and Document depot of Capture business designer solution must not be instantiated on the same node. For details, see chapter "Prerequisites for the setup with the "Create Capture Business Designer Solution" wizard" in "Papyrus Business Designer Document Capture Business Administrator Guide (popcfbdae)". Local settings of default user Capture release manager If default Capture Business Designer users are deployed, then after instantiating a new Capture Business Designer solution two settings have to be provided manually on user level for the Capture release manager, because these settings are not automatically performed after the instantiation of the Capture Business Designer Solution. For details, see chapter "Create users with "Create Capture Business User" wizard" in "Papyrus Business Designer Document Capture Business Administrator Guide (popcfbdae)". 12.1.7 Papyrus Business Correspondence Solution 12.1.7.1 Information relevant for administrators and developers l Document and Inbox states: transition states for CfTask The document MATERIAL and CfTask have a state model that is used to control the transition of a document within the correspondence workflow. The state model has been modified and extended with further transitions. For more details, see chapter "Document content and workflow states" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Papyrus Canvas: paragraph style tabulators for Papyrus Canvas Tabulator entries delivered with the Correspondence Framework are defined with default values. Specific paragraph styles containing tabulators can be defined by the system administrator. For more details, see chapter "Create a formatting tabulator style for a text variant" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Automate steps: Wizards for Correspondence Definition Collection Entries for the Correspondence Definition Collection can be optionally created using wizards. These wizards automate the creation of entries and their values. For more details, see chapter "Configuring resource settings for document and business users" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Images: business users can import images from ACM Change Management Case Business users can insert images into text input fields during document creation, and these images can derive from the artifact of an ACM Change Management Case. For more details, see chapter "Configure insert image into text prompt" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 100/389 Appendix: main updates in V7.5 l Data type: use line data during simulation The Upload MimeType Collection can be extended allowing business users to perform simulation testing for different data types. For more details, see chapter "Configure external data types for document generation and simulation" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Single-source document (SSD): embedding image files in HTML using Base64 Images can be embedded in the email content using Base64 or stored externally on a web server. For more details, see chapter "Create internal embedded and external image resources for HTML Email content" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Papyrus Designer: invoke Papyrus Designer from Papyrus Business Designer Consultants, developers and business users that construct document templates and building blocks can invoke Papyrus Designer from Papyrus Business Designer allowing them to considerably extend document functionality. For more details, see chapter "Configure to start Papyrus Designer in Papyrus Business Designer" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Group building block: group positioning elements can be created and edited directly in the structure tree Template administrators working with a document template, group, and layout can create and edit a group positioning element directly in the structure tree by clicking the More button and dragging elements from the tree into the group. For more details, see chapter "Enable group edit in document/group/layout" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l CF2: update Details and Tab register views of CF2 perspective views (SDI mode) This only needs to be addressed in the perspective views, the precursor of Papyrus EYE Widgets, because the following MetaClass methods have been set obsolete since V7.1 SP8: 20160212.v718: ···obsolete··· Detail (use PQL table view instead) (DesktopViewDetail) ···obsolete··· TabRegister view (use dedicated view instead) (DesktopViewTabRegister) In the custom class from which these instances are derived (e.g. framework base class or custom task class), override the above MetaClass methods to reactivate them, activating option Valid for instance. l Change Management: automatic creation of allocation groups If upgrading a Papyrus Business Correspondence Solution that is prior to V7.3 SP2 then the manual conversion of allocation groups must be performed as part of the upgrade process. Allocation Groups are automatically created and are no longer manually created. Existing Allocation Groups must be converted to ensure that business user access performance is maintained. For more details, see chapter "Application node storage" in "". l Language: configure text direction We can define the direction of text entry for a business user for a specific language variant as needed e.g. for Hebrew language writing from right-to-left. For more details, see chapter "Configure direction for text entry based upon the language variant" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Correspondence integration: show AFP preview as alternative to PDF when calling Papyrus Desktop/EyeWDG via a URL string If the task and document are in QCMode, a preview of the AFP document will be displayed as alternative to the PDF format. For more details, see chapter "Configure Show AFP Preview for Papyrus Desktop/EyeWDG" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 101/389 Appendix: main updates in V7.5 l Papyrus Business Designer: renamed Business Designer Policy to Business Designer BC Policy We have renamed the Policy and Role for those business users that use the Papyrus Business Designer. For more details, see chapter "Conversion of business users to have a Business Designer BC Role" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Workplaces: migration to a new Papyrus EYE Widget workplace engine with V7.5 As of V7.5 a new engine for running UIs based on Papyrus EYE Widgets has been introduced. The new engine is called Papyrus EYE Widgets v5 and brings improved maintainability, performance, reliability and component handling as well as iterative design and easier reuse of data interfaces. Already existing applications on Papyrus EYE Widgets v4 remain compatible but an update to v5 can be made. For more details about workplace replacement, see chapter "Updating business user Papyrus EYE Widget workplace" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". For more details about the migration, see chapter "Migration to Papyrus EYE Widgets v5 engine" in "EYE Widgets Developer Guide (popeyewdge)". l Concatenation of resources in AFP: 'Write resource GUIDs' side effect on resource concatenation cleared Application output format parameter Res. GUID makes the GUIDs of resources be written to the generated AFP. In a Papyrus Business Correspondence Solution you can overrule this setting, which is defined in the underlying DOCDEF, by a settings parameter: on CF scope configuration by Write resource GUIDs. Before 7.5, the Write resource GUIDs switch had a side effect: When Res. GUID was not set in the DOCDEF but Write resource GUIDs was activated and resources should be concatenated, then all resources were concatenated to the AFPs independent from the resource group definition. This means that even if the resource group definition included only a certain group of resources (e.g. only page segments) all types of resources that were used in the document were concatenated to the AFP (page segments, overlays, fonts, imported resources, ...). This had a negative impact on AFP size and performance. Version 7.5 clears this side effect of Write resource GUIDs. If setups should deliver the same result like before V7.5 the resource group definitions have to be adapted accordingly. l Compatibility settings: "Switch condition" available Provides an alternative execution path for handling non existent variables. If the variable does not exist then the deselected default setting will result in the default-case being executed. If selected then the first case statement following the switch statement will be executed and ensures that it is backward compatible. For more details, see chapter "Configuring correspondence compatibility settings support for previous releases" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". "Table width priority" available Setting is used to determine if the column width definition should be altered or remain unchanged. For more details, see chapter "Configuring correspondence compatibility settings support for previous releases" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l All editors in Business Designer: details area can be configured to be displayed also when item is edited Business users editing a document or building block have the details area hidden by default. System administrators can define now that the details area is displayed not only when an item is created anew, but also when an existing item is opened for edit. When the details area is shown, business users can then hide the details area if required. For more details, see chapter "Configure expand and collapse business user workplace details area" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 102/389 Appendix: main updates in V7.5 12.1.7.2 Information relevant for business users l Single-source document creation: images in HTML output variants can be embedded If images are used in an HTML output variant, these images are either external (saved on the webserver) or internal (embedded into the HTML file), depending on what the system administrator has selected in the CF scope SSD creation settings. For more details, see chapter "Images: How images are inserted into web and email variants" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Release and Change Management: release managers can complete building blocks Release managers can now complete a building block on the Release Management workplace by clicking the Supervisor Complete button. Previously, only a template administrator was able to complete a building block when they finished editing by clicking the Complete button on the Correspondence Management workplace. For more details, see chapter "Complete locked items in private development" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Administrator main view: version history of building blocks available Template administrators can view a release-oriented overview of all changes for the selected building block by clicking the History tab on the Administrator main view. On the History tab, the template administrator can compare versions and then go back to a previous version. For more details, see chapter "View the version history of a building block" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Document templates, groups, layouts: n Multiple positioning elements can be selected and removed from the structure tree Template administrators can select more than one positioning element in any sequence in the structure panel and remove them from the tree by clicking the Remove button. For more details, see chapter "Remove a positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". n Papyrus Designer can be opened directly DOCDEF developers and consultants working in Business Designer can open Papyrus Designer directly from the document template, group and layout by clicking the Open document with Papyrus Designer button. For more details, see chapter "Open Papyrus Designer" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Group positioning elements: n Can be created and edited directly in the structure tree Template administrators working with a document template, group, and layout can create and edit a group positioning element directly in the structure tree by clicking the More button and dragging elements from the tree into the group. For more details, see chapter "Creating a group positioning element in the document structure" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". n Individual prompting can be enabled for repeated groups Template administrators working with group positioning elements that are repeated can now define that prompting is enabled for all occurrences. For more details, see chapter "Repeat a group positioning element with text input fields (prompts)" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 103/389 Appendix: main updates in V7.5 l Text positioning elements: for shading and frame, different colors can be selected Template administrators working with a document template, group, and layout can select a different color for the shading and the frame defined for a text positioning element. Previously, the same color was used for frame and shading. For more details, see chapter "Add shading and frame to a text positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Check boxes: a fill color can be selected for a check box Template administrators working with a Checkbox design building block in a document template, group, and layout can define a fill color on the Experts tab for the check box, which is displayed regardless of the color of the table or shading defined for the positioning element where the check box is placed. For more details, see chapter "Define attributes on the "Expert" tab for a check box" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Text variants: n Last empty lines caused by empty variables can be suppressed Template administrators working with a text variant can suppress the last empty line in the text caused by an empty variable by selecting the Suppress last line if empty check box on the Expert tab. Previously, an empty line was shown if the variable was empty. For more details, see chapter "Remove last blank or empty line caused by empty variables" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". n Specific paragraph styles with default tabulator values available Template administrators working with text variants can use a default value for tabulators that is different to 0.5 inch, if the paragraph style defined by the system administrator contains a tabulator definition. For more details, see chapter "Formatting paragraphs" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". n Text input direction RTL supported for Hebrew and Arabic New buttons in the Text input and Paragraph toolbar enable to change the text input direction between left to right (LTR) and right to left (RTL). For more details, see chapter "Define right-to-left (RTL) text input direction" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Document preview: switch between duplex and simplex view Business users working with text variants and documents can use the new drop-down menu Facing view mode in the View toolbar for duplex documents to switch between duplex and simplex view. For more details, see chapter "Change view mode for duplex documents" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". 12.1.8 Papyrus Reporting Solution 12.1.8.1 Information relevant for administrators, developers and business users l Workplaces: migration to a new Papyrus EYE Widget workplace engine with V7.5 As of V7.5 a new engine for running UIs based on Papyrus EYE Widgets has been introduced. The new engine is called Papyrus EYE Widgets v5 and brings improved maintainability, performance, reliability and component handling as well as iterative design and easier reuse of data interfaces. Already existing applications on Papyrus EYE Widgets v4 remain compatible but an update to v5 can be made. For more details about the migration, see chapter "Migration to Papyrus EYE Widgets v5 engine" in "EYE Widgets Developer Guide (popeyewdge)". getstartede V7.6 SP3 104/389 Appendix: main updates in V7.5 l Reporting chart: attribute "Groups" The new attribute "Groups" of the building block Reporting chart allows to specify column variables for grouping. For details, see "Reporting chart" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". l Reporting user settings: format data New attributes added to Reporting user settings allow to format data (numeric, date, string) on data tables or dashboards. For details, see chapter "Reporting Solution settings" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". l Dashboard: bar caption direction Now the direction the captions of the bars of a bar chart on a dashboard can either be set to horizontal or diagonal depending. This allows better use of the available space. For details, see chapter "Reporting Solution settings" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". l Reporting administration: Export CSV into file system This new feature allows to export source tables and data tables as CSV files into file system irrespective of their source type (e.g. PQL based table). For details, see chapter "View and export tables as CSV files" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". l Reporting Solution: Instance versioning While until the previous version Reporting Framework used unversioned objects for all its components (apart from Report document templates), as of version v7.5 Reporting Framework uses versioned instance objects for configuration components, only the data remain unversioned objects. For details, see chapter "Versioning of the Reporting Solution" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)" and chapter "Migration of an unversioned reporting workspace to a versioned one" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". l Reporting users: Reporting user templates changed As of version v7.5 the Reporting user templates in the Library have changed. Reporting simple user template has been removed and Reporting business user template has been renamed to Reporting user template. The new Reporting user has the same capabilities as the prior Reporting business user. For details, see chapter "Create Reporting users" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". 12.1.9 Papyrus Client Document Creation (Canvas) l Default values for tabulators in text input field can now be defined arbitrarily It is now possible to define default values for tabulators at will, which until now were defined hard-coded to 0,5 inch and had to be changed for each tab stop. For more details, see chapter "Define default tabulator stops" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Text input direction right-to-left supported for Hebrew and Arabic New buttons in the Text input and Paragraph toolbar enable to change the text input direction between left-to-right (LTR) and right-to-left (RTL). For more details, see chapters "Insert control characters to influence text direction" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)" and "Text orientation" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". getstartede V7.6 SP3 105/389 Appendix: main updates in V7.5 l New feature: Switch between duplex and simplex view With the new drop-down menu in the View toolbar you can switch between duplex and simplex view. For more details, see chapter "Facing view mode" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Variables of type PQLSet supported The Variables window displays the variables that are available for the currently active input field. Also variables of type PQLSet are supported. For more details, see chapter "Variables window" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". 12.1.10 Papyrus Designer, Papyrus DocEXEC 12.1.10.1 Information relevant for DOCDEF developers l PDF and TIFF import and barcode creation by 'Invoke DLL': PDF import: native PDF representation implemented for z/OS (USS and native) In the past there was a limitation when AFP with imported PDF files should be converted to PDF: on z/OS (USS and native) the native PDF representation was not supported while all other platforms did support native PDF representation. The import of a PDF file into an AFPDS is done by Invoke DLL command calling IOBDLL library. 'Native PDF representation' means that an imported PDF file is kept as native PDF in the target PDF. If the conversion process took place on z/OS in earlier Versions the imported PDF file was transformed into an image instead. The conversion process itself is done either by Papyrus Server AFP to PDF or by Papyrus DocEXEC direct PDF output. For more information about PDF import, see chapter "Inserting PDF files with IOBDLL(IOB_INFO) and IOBDLL(IOBDEFS)" in "DocEXEC Reference Application Developer Guide (pdedge)". TIFF import with CREATEOBJECT IOBDLL(TIFF_IMPORT): image size calculation changes when one dimension parameter is not defined IOBDLL(TIFF_IMPORT) is used for importing TIFFs and allows to map the image to a defined object area, which needs not necessarily to have the original image dimensions. If there is a defined ObjectMapping and only one of the size parameters (XObjectAreaSize or YObjectAreaSize) is defined then the value of the parameter that is not defined is automatically calculated. The calculation is based on the original aspect ratio of the image, and the image size is modified accordingly. In versions prior to V7.5 the image was not resized and its original size was used. This change is not backward compatible. For more information, see chapter "CREATEOBJECT IOBDLL(TIFF_IMPORT)" in "DocEXEC Reference Application Developer Guide (pdedge)". CUSTBARC barcode with CREATEOBJECT BAROBJ(CUSTBARC): print Japanese postal code even if it's 'representative code' CUSTBARC barcode routine supports a new parameter: PRINITREPRESENTATIVECODE. This parameter allows to print Japanese postal code even if it's 'representative code'. 'Representative code' means that the last two digits of the 7-digit postal code are '00'. The parameter is a compatibility switch for document applications implementing this type of barcode that were developed on Papyrus Designer/Papyrus DocEXEC versions between V6.1 (31/05/2010) and V7.4 SP2. The CUSTBARC routine of these versions did not suppress the printing of postal code with 'representative' numbers. If you need to have 'representative code' printed, set 'PRINTREPRESENTATIVECODE'='1'. For more information, see chapter "CREATEOBJECT BAROBJ" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 106/389 Appendix: main updates in V7.5 l Recording functions: Line delimiter for HTML output has changed from LF (x'0A') to CRLF (x'0D0A') Recording functions _TEXT_START(), TEXT_STOP(), _TEXT_SUSPEND() and _TEXT_RESTART() allow for recording of TEXT and TEXTPROMPT content converted to HTML. The line delimiter for the HTML, which used to be line feed (x'0D'), has been changed to carriage return and line feed (x'0D0A'). For more information, see chapter "Recording functions" in "DocEXEC Reference Application Developer Guide (pdedge)". Suppress generation of formatting commands in AFP/PDF/Word but not in HTML and plain text: _SET_GENERATE() Function _SET_GENERATE() suppresses the generation of formatting commands in all output channels except for output that is generated through recording functions or by LISTOUT/WRITERECORD/PUT. Output generated through recording functions is HTML/plain text/DFA code generated by _TEXT_START(), TEXT_STOP(), _TEXT_SUSPEND() and _TEXT_RESTART(). _SET_GENERATE is complementary to the functionality of the recording functions and replaces the application of the PURGE command. For more in information, see chapter "_SET_GENERATE" in "DocEXEC Reference Application Developer Guide (pdedge)". l XML reading: PQL set function FROMXML() Function FROMXML() reads an XML file and creates a PQL set, which can be parsed by PQL set functions. The function is similar to FROMJSON(), which creates a PQL set from JSON file. For more information, see chapter "FROMXML" in "DocEXEC Reference Application Developer Guide (pdedge)". l Application output format dialog: disappearing descriptive text Descriptive text on the Application output format dialog could sometimes be presented incompletely so that parts of words disappeared. Version V7.5 has fixed this flaw. l Entry fields for variables: background color for check boxes and radio buttons The VARPROMPT command, which creates entry fields for variables in document applications, allows to define a background color for check boxes and radio buttons by means of parameter BoxFillColor. For more information, see chapter "VARPROMPT command" in "DocEXEC Reference Application Developer Guide (pdedge)". l Right-to-left writing: simplified handling of mixed RTL and LTR language scripts In a right-to-left language script (abbreviated "RTL", as opposed to "LTR" for left-to-right scripts), writing starts from the right of the page and continues to the left. Arabic, Hebrew, Persian, Urdu, and Sindhi are the most widespread RTL writing systems in modern times. Papyrus has always supported RTL. The challenge with RTL is mixed text where a RTL script contains phrases of a LTR script or numbers or acronyms, that is when visual text order is conflicting with the logical text order. With V7.5 Papyrus has simplified the handling of the logical and visual text order. This handling can be activated by three new options in the Use command. see chapter "USE command" in "DocEXEC Reference Application Developer Guide (pdedge)" getstartede V7.6 SP3 107/389 Appendix: main updates in V7.5 l Chart creation by 'Chart DLL': Donut charts: new parameters SmallImages, TextColor, ChartMiddleText and ChartMiddleTextFontName SmallImages allows to use images instead of text in the chart if ChartInfo option Text is set and ImageMode is Image. TextColor allows to define three different colors for text, value figures, legend text and group name text. ChartMiddleText allows to define text and its color which is placed automatically into the middle of the donut chart. ChartMiddleTextFontName allows to define the name of the font which is to be used for the text defined by ChartMiddleText. The fonts can be specified as a physical SBCS/DBCS name, without extension (for example X0AR00(5,100)) or as TTF/OTF name (for example /*Arial Bold). For more information, see chapter "CHARTEX DLL for pie charts" in "DocEXEC Reference Application Developer Guide (pdedge)". Donut charts: parameter 'ChartInfo', option 'Number inside' displays segment value instead of segment number ChartInfo parameter option Number inside used to display the segment number, which is consecutive. This has been changed to display the segment's value plus a percentage symbol. Note that the Number inside option is available for several chart types where its implementation produces different results. For more information, see chapter "CHARTEX DLL for pie charts" in "DocEXEC Reference Application Developer Guide (pdedge)". Radar charts: new parameter DrawAllValues changes chart layout DrawAllValues displays all values in the charts and draws chart axes as dashed lines instead of solid lines. For more information, see chapter "CHARTEX DLL for radar charts" in "DocEXEC Reference Application Developer Guide (pdedge)". l New protected DOCDEF keywords with version 7.5: ICUAUTO ICU_LTR ICU_RTL OUTIMAGE RETURNASPQLSET TABDEFAULT Protected DOCDEF keywords must not be used as names in applications (e.g. variable name, font name, document format name a.s.o.). If new protected keywords were implemented, customers should check their applications whether these protected keywords are used in their applications as names. If an existing application does contain a name which has become a protected keyword with this version, Papyrus Designer/Papyrus DocEXEC displays error message PPDE9999E ( getstartede V7.6 SP3 108/389 Appendix: main updates in V7.5 12.1.10.2 Information relevant for administrators l Compatibility parameter for table width definition: TABLEWIDTHPRIORITY Table width calculation in certain situations has been corrected with version V7.2 SP2. TABLEWIDTHPRIORITY allows now to switch back to pre-V7.2 SP2 behavior and applies only to tables created by TABLE command. If a table specifies both table and column width and the specifications provoke a contradiction, DocEXEC has to give priority to one of the specifications. "Contradiction" means, for example, when the table width is greater than the sum of column widths. In versions prior to V7.2 SP2, in some situations the resulting relation of table and columns was not satisfying and therefore the calculation had to be corrected. For more information, see chapter "DETABLEWIDTHPRIORITY / TABLEWIDTHPRIORITY" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l Spellchecking: suppress highlighting of compound words with SPELLCHECKCOMPOUNDWORDS Parameter SPELLCHECKCOMPOUNDWORDS allows to switch the spellcheck of compound words. This means the spellchecker should either highlight (= mark as misspelled) or not highlight compound words. Compound words are words that consist of single words known to the spellchecker, for example: "Thisisalongpieceoftext" is a compound word. For more information, see chapter "SPELLCHECKCOMPOUNDWORDS" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l Concatenation of resources to AFP: 'Write resource GUIDs' resp. APPOUT_RESGUID side effect on resource concatenation cleared Application output format parameter Res. GUID makes the GUIDs of resources be written to the generated AFP. In a Papyrus Business Correspondence Solution you can overrule this setting, which is defined in the underlying DOCDEF, by a settings parameter: on CF scope configuration by Write resource GUIDs. Before 7.5, the Write resource GUIDs switch had a side effect: When Res. GUID was not set in the DOCDEF but Write resource GUIDs was activated and resources should be concatenated, then all resources were concatenated to the AFPs independent from the resource group definition. This means that even if the resource group definition included only a certain group of resources (e.g. only page segments) all types of resources that were used in the document were concatenated to the AFP (page segments, overlays, fonts, imported resources, ...). This had a negative impact on AFP size and performance. Version 7.5 clears this side effect of Write resource GUIDs. If setups should deliver the same result like before V7.5 the resource group definitions have to be adapted accordingly. For more information about parameter APPOUT_RESGUID, see chapter "APPOUT_RESGUID" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 12.1.11 Papyrus Objects (WebControl/WebRepository) 12.1.11.1 Papyrus Objects System Information relevant for administrators l Settings Explorer: variant search filter keys copied to new default definitions In earlier versions of Settings Explorer, if a new default variant was defined while a variant search filter was active, the key selections of the filter were mistakenly added to the new definition. That problem has been fixed in the latest version of Settings Explorer, so that no variant keys are automatically selected in new defaults. l HTTP Server Settings getstartede V7.6 SP3 109/389 Appendix: main updates in V7.5 n SSL protocol deprecated, replaced by TLS The cryptographic protocol that Papyrus applications use for HTTPS communication is specified in the "SSL protocol level" attribute of the HTTPServerSettings class. Previously, one could choose either SSLv3 (Secure Sockets Layer - version 3) or some version of TLS (Transport Layer Security) for that setting. Because SSL is now deprecated, SSLv3 is no longer selectable. The protocol is set to TLSv1.0 by default, but can be changed to later versions through TLSv1.3. Existing applications configured to use SSLv3 will automatically use the new default. n New classes for certificates and private keys HTTPServerSettings and LoadBalancer objects originally stored HTTP certificates and private keys in dedicated attributes. That information is now stored in separate Certificate and PrivateKey child objects, for which dedicated child references have been defined in the former classes. Both new classes are subclasses of PKI. For more details, see "Prepare the web server to accept HTTPS connection" in "WebPortal Installation and Developer Guide (powpidge)" and "Set up load balancing" in "WebPortal Installation and Developer Guide (powpidge)". l WebPortal: private key passwords must have at least 4 characters WebPortal applications encrypt HTTPS communications by means of RSA private keys, which can optionally have passwords. Previously, such passwords had to contain at least three characters. Now that a third-party toolkit (OpenSSL) has been upgraded to version 1.1.1, however, private key passwords must have at least four characters. If any private keys in your WebPortal setup have three-character passwords, they will no longer work with this release. To fix the problem, simply update the affected private keys with passwords of the required length. l PCSLog: Selected messages forwarded to operating system Starting in V7.41, fatal errors occurring on any Papyrus node are routinely forwarded to and logged by its operating system. By setting two PCS variables on a particular node, you can additionally notify its OS whenever specific non-fatal message events occur there. For details, see "Fatal error messages" in "Product Messages Reference Guide (ipmrge)" and "Logging to the Operating System" in "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)". Information relevant for developers l Settings Collection: new methods for private, local & central settings The Settings Collection now features methods to store, get and clear private, local and central settings. Among other things, you can use these methods to make settings retrievable for transient object instances. For details, see the online help for the SettingsCollection class, or "Tasks of the framework developer" in "WebRepository Application Developer Guide (pwride)". l GetEffectiveSettings(): variants returned with no filter specified In earlier releases of Papyrus Objects, calls to GetEffectiveSettings() with no filter specified also returned settings variants defined for a specific filter. That problem has been fixed in the latest release of the Settings Framework, so that only default variants are returned by such calls. l TMPFILEEXT: new binary file macro The TMPFILE and CONCATFILE macros convert binary attributes to temporary files that the filesystem can manipulate in shell methods. Whereas TMPFILE requires one to specify the file extension as a string literal, the new TMPFILEEXT macro enables you to name a string attribute whose value supplies the file extension. For details, see "Access binary attributes as temporary files via the operating system" in "WebRepository Application Developer Guide (pwride)". getstartede V7.6 SP3 110/389 Appendix: main updates in V7.5 12.1.11.2 Papyrus Depot l Depot check-in: Depot-check-in with OMS account In some set-ups it may occur that particular accounts can release and put on hold the check-in object of a depot that do not have the privileges to handle objects in the depot. To ensure in such a case that the check-in has access to all possible objects an OMS account can be added to the check-in object of the depot. For details, see chapter "Depot check-in with OMS account" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l New features and changes for the Eye Widgets Depot search workplace n Index classes as search index Until V7.5 the search index was solely selected from the index templates in depot search application container. With V7.5 it is additionally possible to define index classes to use as search index. By selecting an index class all index templates using this class are used for the search. Furthermore a default index can be enabled for each workplace. For details, see chapter "Define indexes to use" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". n Indexes in development for search The methods EnableDevelopmentVersions and DisableDevelopmentVersions were implemented on the DepotSearchContainer. Thus it is no longer necessary to write a PQL, but instead click on the method button on the Depot search container of the user. For details, see chapter "Provide the workplace to business users" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". n Filter in search results The business user is now able to narrow down the search by entering criteria in the fields above each column of the result list. For details, see chapter "Enable search result filter" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". n Hide details tab This new setting allows to control whether the details tab is part of the result details or not. The details tab displays the index object that belongs to the hit you selected in the result list. In a lot of cases the business user should only see the objects below the index object (e.g. a PDF document) and not the index itself. For details, see chapter "Hide details tab" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". n PDF View no longer blocks typing in the search mask In a previous release viewing a PDF on the right side of the Depot search could prevent the search mask from accepting any input. This has been fixed. n Simple vs. Advanced search Switching between these two modes is now done via the More menu instead of a drop-down list. n Details tab is now cleared after a search without hits In a previous release the Details tab showed the index object of the last search. This has been fixed. getstartede V7.6 SP3 111/389 Appendix: main updates in V7.5 12.1.11.3 Papyrus Query Language (PQL) Information relevant for developers l $unTagLocally() no longer supported Objects reserved with $tagLocally() or $tryTagLocally() during a particular transaction once had to be un-reserved by calling the $unTagLocally() PQL function. That is no longer necessary, because the kernel now automatically un-reserves those objects at the conclusion of the transaction. Now that it serves no purpose, support for $unTagLocally() has been discontinued. l pqlpdf library: new $officeToPDF() function The pqlpdf extension library now enables you to generate PDFs from complete or excerpted Microsoft Word documents. For details, see "pqlpdf: Papyrus PQL PDF generator library" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". 12.1.11.4 Papyrus Resource Collection l Wizards: New wizard views available for resource import and export In V7.5, new wizard views are available to change the default values of Resource Adapter Dispatch Profile, Resource Import, Resource Library Import and Resource Export. For more details, see chapters "Setting up the resource import/creation adapter using wizard" in "" sowie "Exporting resources from Resource Collection" in "Resource Library Reference Guide (reslibrge)" l Resource Proxy Management: Resource Proxy Management can be configured by using a wizard In V7.5, a wizard view is available to configure the Resource Proxy Management for the selected Resource Group. For more details, see chapter "Configuration of a resource proxy management with wizard" in "". l Wizards: New wizard view available to update the existing Resource Group In V7.5, a new wizard view is available to update the existing Resource Groups. In previous versions, the Update Resource Groups PQL was used for this purpose. In V7.5, you can either instantiate the PQL template Update Resource Groups or invoke the wizard by clicking on the Update Resource Groups method from the context menu of the Resource Group. Even though this wizard was available in V7.5, it is announced in the V7.5 SP2 for the first time. For more details, see "Adjust existing Resource Groups" in chapter "Relocating resources from the domain controller to the resource node" in "". 12.1.11.5 Papyrus EYE Widgets 12.1.11.6 Papyrus WebPortal Information relevant for administrators l HTTP Server Settings n SSL protocol deprecated, replaced by TLS The cryptographic protocol that Papyrus applications use for HTTPS communication is specified in the "SSL protocol level" attribute of the HTTPServerSettings class. Previously, one could choose either SSLv3 (Secure Sockets Layer - version 3) or some version of TLS (Transport Layer Security) for that setting. Because SSL is now deprecated, SSLv3 is no longer selectable. The protocol is set to TLSv1.0 by default, but can be changed to later versions through TLSv1.3. Existing applications configured to use SSLv3 will automatically use the new default. getstartede V7.6 SP3 112/389 Appendix: main updates in V7.5 n New classes for certificates and private keys HTTPServerSettings and LoadBalancer objects originally stored HTTP certificates and private keys in dedicated attributes. That information is now stored in separate Certificate and PrivateKey child objects, for which dedicated child references have been defined in the former classes. Both new classes are subclasses of PKI. For more details, see "Prepare the web server to accept HTTPS connection" in "WebPortal Installation and Developer Guide (powpidge)" and "Set up load balancing" in "WebPortal Installation and Developer Guide (powpidge)". l WebPortal: private key passwords must have at least 4 characters WebPortal applications encrypt HTTPS communications by means of RSA private keys, which can optionally have passwords. Previously, such passwords had to contain at least three characters. Now that a third-party toolkit (OpenSSL) has been upgraded to version 1.1.1, however, private key passwords must have at least four characters. If any private keys in your WebPortal setup have three-character passwords, they will no longer work with this release. To fix the problem, simply update the affected private keys with passwords of the required length. 12.1.12 Papyrus PrinterDriver l Papyrus PrinterDriver File Receiver: extended PrinterDriver functionality Papyrus PrinterDriver File Receiver is an extension to Papyrus PrinterDriver and supports data received as a binary stream (raw data), which is then saved in a local file. For details, see chapter "Papyrus PrinterDriver File Receiver" in "PrinterDriver Administrator and User Guide (pdrauge)". l Newly designed GUI buttons The buttons of the graphical user interface have been given a new look and embody the general Papyrus GUI design. 12.1.13 Papyrus Server 12.1.13.1 AFP to PDF l PDF import: native PDF representation implemented for z/OS (USS and native) In the past imported PDF files were transformed into images. Given that you have the Papyrus PDF-in product authorization, PDFs are now embedded natively. For more information about PDF import, see chapter "Inserting PDF files with IOBDLL(IOB_INFO) and IOBDLL(IOBDEFS)" in "DocEXEC Reference Application Developer Guide (pdedge)". l Generate Hash - new parameter This parameter allows to generate a MD5 128-bit hash value for the generated PDF output file, which can be used as a checksum to verify data integrity against unintentional corruption. For more details, see chapter "Generate Hash (PDFtGenerateHash)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Import PDF with prompts - new parameter This parameter defines whether the prompts of a natively (IOB/PDF) imported PDF are imported or ignored. A Papyrus PDF-in product authorization is required to use this feature. For more details, see chapter "Import PDF with prompts (PDFtIobPdfImportPrompts)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Import PDF/UA - new parameter This parameter defines whether the PDF Universal Accessibility information of a natively (IOB/PDF) imported PDF are imported or ignored. A Papyrus PDF-in product authorization and a Papyrus PDF Extended product authorization are required to use this feature. For more details, see chapter "Import PDF/UA (PDFtIobPdfImportPDF_UA)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". getstartede V7.6 SP3 113/389 Appendix: main updates in V7.5 12.1.13.2 AFP to Text l Line break (TxtNewLineFlag) - new parameter This parameter specifies the end-of-line code. Different platforms expect different end-of-line codes. AFP to Text is sometimes used to generate an input file for other applications. Thus this parameter allows to format the text in a form suitable for the operating system the other application runs on. CR, LF and CR+LF are selectable. For more details, see chapter "Line break (TxtNewLineFlag)" in "Papyrus Server - AFP to Text Reference Guide (psetxtrge)". 12.1.13.3 PCL l Spool data type - new parameter With Windows Server 2012 / Windows 8 Microsoft introduced a new driver model for the printing subsystem called version 4 drivers. The V4 printer driver model uses XPS. Thus RAW cannot be used anymore in Queue mode as it generates 0 byte spool files. This parameter allows to set the spool data type to XPS. For more details, see chapter "Spool data type (PrintSpoolDataType)" in "Papyrus Server - PCL Reference Guide (psepclrge)". l Grouped parameters to match tabs on tool The manual now reflects the order of the parameters on the tool in Papyrus Objects. 12.1.13.4 PostScript l Spool data type - new parameter With Windows Server 2012 / Windows 8 Microsoft introduced a new driver model for the printing subsystem called version 4 drivers. The V4 printer driver model uses XPS. Thus RAW cannot be used anymore in Queue mode as it generates 0 byte spool files. This parameter allows to set the spool data type to XPS. For more details, see chapter "Spool data type (PrintSpoolDataType)" in "Papyrus Server - PostScript Reference Guide (psepsrge)". 12.1.13.5 HTML l Papyrus Server HTML available for Linux In addition to Windows, Solaris and AIX, the module is now also available for Linux. getstartede V7.6 SP3 114/389 Appendix: main updates in V7.5 12.2 Updates in V7.5 SP1 12.2.1 General changes l Processing PDF: enhanced support for TrueType CID fonts with Identity-H encoding Several Papyrus products or solutions support functions for processing PDF. For example, to convert PDF into other file formats or for embedding PDF objects in an AFPDS. To do so the products make use of a PDF parser module. In some cases the PDF parser was not able to process the PDF properly. If the PDF files contained a special type of TrueType CID fonts, then 'unknown exceptions' could happen while parsing the file and PDF conversion and display failed. Version 7.5 SP1 has enhanced TrueType CID font support so that now also fonts with Identity-H encoding are covered. This module is used by following products and solutions: - Papyrus Business Document Capture Solution: load a PDF file in the Document workplace view of Papyrus Client Capture in order to classify the document manually; calling SaveToTiff function in the Capture administration workplace view of Papyrus Client Capture in order to convert the PDF to TIFF - Papyrus PDF-in: convert PDF to AFP resources - Papyrus DocEXEC: produce AFP with IOB-embedded PDF (i.e. AFP with PDF documents embedded by CREATEOBJECT IOBDLL) - Papyrus Client AFP Viewer: display AFP with IOB-embedded PDF l Processing PDF: support for JPEG2000 images carrying a color table The PDF parser has been improved so that with V7.5 SP1 also PDF documents containing JPEG2000 images carrying a color table can be processed. New document l Papyrus and Third-party Software General Information This new document is aimed at software administrators and license managers and gives an overview of third-party software that is used in conjunction with Papyrus products. It specifies which Papyrus products require certain third-party licensed components, where the software is installed and and where the license agreements for this software can be found. The document is not part of the regular delivery but it is available on demand and can be requested via [email protected]. The document is updated within the scope of Papyrus software release cycles on a regular base. 12.2.2 Papyrus Automated Document Factory Solution 12.2.2.1 Information relevant for administrators and developers l ADF/PED e-mail template design n Avoid line feed (LF) without carriage return (CR) in e-mails Recently some e-mail servers started marking messages that contain a line feed (LF) without a carriage return (CR) as spam or stopped delivering them. Thus be conscious about this when designing e-mail templates and also verify existing templates. For more details, see Encoding considerations in RFC 2854. 12.2.2.2 Information relevant for business users l ADF workplaces n ADF workplaces renamed "ADF jobs" was renamed to "Job operations". "ADF queues" was renamed to "Queue cockpit". n ADF workplaces: Inconsistent update of controls of queues/tools in adapter view Under certain circumstances buttons did not update in case something changed. This has been fixed in V7.5 SP1. getstartede V7.6 SP3 115/389 Appendix: main updates in V7.5 l Depot search workplace n Incorrect index usage during search In case a workplace contained multiple workplaces with search functionality, and these workplaces used different search indexes, some inconsistencies occurred. This could have happened, for example, in an ADF workplace with Depot search workplace and Bounce handling workplace. This has been fixed in V7.5 SP1. n Unwanted doubling of details tab A double click on a search result item lead to the index details tab being shown twice. This has been fixed in V7.5 SP1. A simple select (one click or up/down key) did not cause this problem. n Search without arguments produced incorrect result A search without arguments showed the result of the previous search. With V7.5 SP1 the entire database, limited by max number of results set by your administrator, is shown. n First search with '*' after a Login produced empty result If you searched with '*' after a login the result was empty. After using a different search criterion, '*' worked. With V7.5 SP1 '*' works all the time. n Clear button in search mask had no effect Previously all fields had to be emptied manually. With V7.5 SP1 the Clear button works and all fields can be emptied with a single click. n Switching the index type from template to class and vice versa caused login problems If users changed the index type in General settings this could result in them being no longer able to successfully login to the EYE Widgets workplace. Important objects from the DepotSearchAttributeSelectionContainer were removed. With V7.5 SP1 this is prevented. 12.2.3 Papyrus Business Correspondence Solution 12.2.3.1 Information relevant for administrators and developers Improvements are provided with this service pack and affect the following use cases: l Testing items (SIT testers): changing the setting has the desired effect When system administrators change the Enable vote for all items attribute in the CM workplace settings, this has an effect for testers voting on items on the Test Management workplace. Without this service pack, deselecting or selecting the Enable vote for all items check box in the CM workplace settings has no effect for the SIT testers. l Data reading (clerks): data is cached for data reading When a business user creates a document instance with dynamic data, the data reading functionality has been improved so that it only retrieves the information that is required to complete its operation. A persistent object cache has been implemented, which reduces the amount of data that is transferred during a data reading operation with OMS_PREREAD DocEXEC function. 12.2.3.2 Information relevant for business users Improvements are provided with this service pack and affect the following use cases: getstartede V7.6 SP3 116/389 Appendix: main updates in V7.5 l Attachments: the position of an attachment can be changed Template administrators inserting an attachment into a document can now change the position of the attachment within the document with the Inline attachment design building block. Without the service pack, the attachment's position at the end of the document cannot be changed. For more details, see chapter "Change the position of an attachment in the document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Comparing text variants: special characters are displayed correctly When two versions of a text variant building block are compared, special characters are displayed correctly. Without this service pack, special characters may lead to issues when two versions of a text variant are compared. l Text positioning elements: overlapping issues with "Suppress empty prompt lines" are fixed When template administrators select the Suppress empty prompt lines check box, the following building blocks are now displayed as expected. Without the service pack, in case the prompted value is empty the occupied area will be used as negative offset for the next building block, resulting in overlapping texts. For example, a document with two text positioning elements where the first one is prompted and has the Suppress empty prompt lines check box selected, the text might be shown overlapping. l Scheduled disabling: disabling date is now shown for all interval types When template administrators select scheduled disabling, the disabling date is now shown in the Disable items dialog, regardless of the interval type chosen in the Scheduler. Without this service pack, the disabling date is not shown if the Interval type is set to Monthly or Yearly in the Scheduler. l Wizards: value of prompted wizard document is saved after clicking "Back to wizard" For clerks going through a wizard with a prompted document, the prompted content is now saved when they return to the wizard by clicking the Back to wizard button. Without the service pack, the prompted content is not saved when they click the Back to wizard button. l Input fields in Papyrus Client Canvas plugin: Selected text can be saved as text building block Clerks working with a document can select text in an input field (prompt) and save the selection as a new IMP object by clicking the Save as text building block button from the Text input toolbar. Without this service pack, the IMP object is not created when clerks click the Save as text building block button. 12.2.4 Papyrus Business Document Capture Solution 12.2.4.1 Information relevant for administrators and developers l POP3 adapter: error messages improved Prior to v7.5 SP1 there was only a general error message in case of failed connection with server (PPOP8904E Could not login. Please check Hostname, User and Password). As of version v7.5 SP1 there is an error message for each case. l Capture template solution: Adapter "Import (File)" fails to import JPG and TIFF files with certain file extensions Adapter "Import (File)" of "Capture template - Capture Solution" failed to instantiate files with .jpg and .tif extension due to an omission in the PQL match rule. This has been fixed in version v7.5 SP1. l Capture template solution: Capacity of Buffer depot checkin queue changed The queue length of Buffer depot checkin queue of "Capture template - Capture Solution" changed from 5 to 0, so that the number of tasks is not limited. getstartede V7.6 SP3 117/389 Appendix: main updates in V7.5 l Document classification: Last document of a batch classified without confirm If a document class has been configured with "Confirm" for classification, then, after a document has been classified as belonging to this class, the confirmation is required before the document is assigned the respective class. In case of batch processing, this did not work for the last document of a batch. This document was assigned the determined document class immediately after classification instead of preceding confirmation. This has been fixed in version v7.5 SP1. l Papyrus Designer Capture: Newly created region invisible A newly created region had the parameters 0/0/0/0 which made it invisible in the image viewer. This has been fixed in version v7.5 SP1. Now a newly created region is displayed in the top-left corner of the image viewer. l Papyrus Designer Capture: Clearing attribute values impossible Failure when trying to clear attribute values. It was not possible to remove attribute values. This has been fixed in version v7.5 SP1. l Papyrus Designer Capture: Subpatterns returned although no match for main pattern In certain cases, subpatterns were returned although the main pattern did not match. This has been fixed in version v7.5 SP1. l Papyrus Designer Capture: Right step counter arrow not displayed if Papyrus Designer Capture started from PO with multi-page images If Papyrus Designer Capture was started from Papyrus Objects with multi-page images, then the right step counter arrow was not displayed. This has been fixed in version v7.5 SP1. l Papyrus Designer Capture: Dump when Capture Designer using Invoice definition set is closed When Papyrus Designer Capture used in connection with Invoice definition was closed, then a dump was created. This has been fixed in version v7.5 SP1. l Papyrus Designer Capture: Amount formatter returns unexpected results Text processor "Amount formatter" returned unexpected results (e.g. including leading zeros). This has been fixed in version v7.5 SP1. l Document extractor: Normalization processor "Rotate" not working Normalization processor "Rotate" did not work correctly. This has been fixed in version v7.5 SP1. l Papyrus Designer Capture: Incomplete results of full page extraction In some cases, full page extraction did not return all data. This has been fixed in version v7.5 SP1. l Papyrus Designer Capture: New parameter "condition element" for anchor references Anchor of region has been extended by the new optional parameter attribute condition element which may contain the reference of another element. For details, see "Settings of anchors" in "Designer Capture Application Developer Guide (pcddge)". 12.2.4.2 Information relevant for business users Information relevant for Papyrus Client Capture users l Display and conversion of PDF documents: enhanced support for TrueType CID fonts with Identity-H encoding In certain situations display or conversion of PDF files failed and an empty PDF page was shown instead, accompanied by error message POIM0014E Failed to load the data in attribute 'TargetName' on object ' getstartede V7.6 SP3 118/389 Appendix: main updates in V7.5 l Papyrus Client Capture: Error message for missing Tenant Selection If Capture workplace or Capture Administration workplace is started by a user the session of which does not contain a Tenant Selection object or if the Tenant is not specified, then as of this version the following error message is displayed: Tenant settings are not specified or not available under the current session. l Capture administration workplace: Export batch documents failed In Document depot view of Capture administration workplace button Export failed for batch documents. This has been fixed in version v7.5 SP1. Information relevant for Papyrus Scan users l Scan view: Scan receiver error message incompletely displayed If scan receiver goes in error, then an user information is displayed in the right-most field on the toolbar of scan view and an info icon button allows to display the full message. In the previous version the info button triggered only a shortened text. This has been fixed in version v7.5 SP1. l Scan view: Scan profile attribute "JPG quality" renamed "Color images" Section "JPG quality %" on tab "Expert" of the dialog "Profile settings" of Scan view has been renamed "Compression quality (%)". Attribute JPG Quality % has been renamed "Color images". l Scan view: Deletion of pages throws error after reverse multi-page selection If a page with a higher number was selected in a multi-page document in the thumbnails viewer of Scan view, then a page was added with a lower number with [CTRL]-key, then a split operation was executed and then pages unsucessfully deleted, then an error was thrown. This has been fixed in version v7.5 SP1. l Scan view: Excess pages loaded in thumbnails viewer If setting "Thumbnails wrap" is disabled, then the thumbnails viewer of Scan view is supposed to display only thumbnails of pages that fit into a row of the thumbnails viewer. Other pages to the right are displayed only if the user scrolls to the right. In the previous version thumbnails viewer loaded all pages of a multi-page document irrespective of the space available in a row. This has been fixed in version v7.1 SP1. l Scan view: File scan fails with long file paths File scan failed to access files in file system with very long file paths. This has been fixed in version v7.1 SP1. l Scan view: Button Classify enabled for documents selected on search panel If a document was selected in the search panel of Scan view, then the button Classify was displayed enabled on the "Inspector" panel but it should be disabled. This has been fixed in version v7.1 SP1. l Scan view: Missing synchronization between scan adapter and scan receiver in case of certain errors If there was no role below the the adapter or the scan profile not accessible, then the scan receiver remained in state "Waiting for adapter" instead of going into error. l Scan view: Incorrect page display in thumbnails viewer if "Thumbnails wrap" is enabled If setting "Thumbnails wrap" is enabled, a multi-page document is displayed and then the splitter is moved to the left so that the last page(s) is moved to the next row, then pages of the new row are not correctly displayed. This has been fixed in version v7.1 SP1. l Scan view: Incorrect thumbnails wrapping If setting "Thumbnails wrap" is enable and thumbnail size is medium or large, then thumbnails wrap did not work correctly. Pages that should have been wrapped to the next row remained invisible. This has been fixed in version v7.1 SP1. Information relevant for Capture Business Designer users getstartede V7.6 SP3 119/389 Appendix: main updates in V7.5 l Extraction definition: Barcode, data matrix and QR code not correctly created Barcode, data matrix and QR code extraction definitions were not correctly created by training when a defined region was used. This has been fixed in v7.5 SP1. l Extraction definition: No elements created for empty region When a defined region did not contain a value, i.e. an empty region, extraction definitions where not properly created during training. This has been fixed in v7.5 SP1. l Capture Business Designer nodes: Incorrect training data When the web server was located on the same node as the data depot which is used for storing the training data, two data objects were created for the same element. This has been fixed in v7.5 SP1. l Capture Business Designer UI: Rearrange button visible in rearrange mode Rearrange button remains visible after switching into rearrange mode instead of disappearing. This has been fixed in v7.5 SP1. l Capture Business Designer UI: Wrong initial message after loading a sample After loading a new sample and clicking Extract an incorrect initial message is displayed (Please select a content in the document view and drag and drop it here to create a new field.). This has been fixed in v7.5 SP1. l Capture Business Designer UI: New document type with existing name If a user creates a new document type using an already existing name only a general error message displayed. With v7.5 SP1 different messages are displayed for different use cases. l Capture Business Designer UI: New field of type IBAN not displayed If a new field of the field type IBAN was created, then the new field was not displayed on the form. This has been fixed in v7.5 SP1. l Capture Business Designer UI: Field groups and field types changed The content of field groups has been changed. Additionally, the names of some field types have been changed. For instance, the field group "Simple elements" includes the values Text, Number, Date, Time, Amount with v7.5 SP1. l Capture Business Designer UI: Error after applying "Disable training" In certain cases an error was thrown after applying the context menu entry "Disable training" on an element. This has been fixed in v7.5 SP1. l Capture Business Designer UI: Fields dropped on document type "GENERAL" Form did not prevent fields from being dropped on "GENERAL" after deletion of a document type. This has been fixed in v7.5 SP1. l Capture Business Designer UI: "all pages" replaced by "any page" during training When "any page" was selected on the UI searching for a pattern, all pages where processed even after a match was already found. As of v7.5 SP1, processing stops after the first match was found. l Capture Business Designer UI: Selection "any page" excludes option "same region" If "any page" is selected, then option "same region" is disabled and if "same region" is selected, then "any page" is disabled. This behavior is active with v7.5 SP1. 12.2.5 Papyrus Reporting Solution 12.2.5.1 Information relevant for business users l Reporting business user workplace: Button "Refresh" not displayed In some cases, button "Refresh" of Reporting business user workplace was not displayed, e.g. when a new version of a dashboard is created. This has been fixed in version v7.5 SP1. getstartede V7.6 SP3 120/389 Appendix: main updates in V7.5 l Reporting administrator workplace: Umlauts not correctly represented with CSV upload Due to an unsuitable codepage umlauts were not correctly transmitted with CSV upload. This has been fixed in version v7.5 SP1. l Reporting administrator workplace: Lookup with 2 parameters returns wrong result Lookup with 2 parameters returned wrong result, there was always a row missing. This has been fixed in version v7.5 SP1. l Reporting administrator workplace: Scheduler table update triggered multiple updates The scheduled procedure "Table update" triggered multiple updates instead of one. This has been fixed in version v7.5 SP1. l Reporting administrator workplace: Filter options "contains", "equals", "is not equal to" do not work as expected The filter options "contains", "equals", "is not equal to" used in NL expressions by data table filter and on dashboard with string variables did not work as expected. This has been fixed in version v7.5 SP1. l Reporting workplaces: New filter option "does not include" A new filter option "does not include" has been added to dashboard and data table filter options. l Report document workplace: Some parameters of document template building blocks cannot be changed as expected In the following reporting building blocks parameter values could not be changed as required: Reporting Chart BB n Values parameter keeps initial value, can not be changed n Groups parameter keeps initial value, can not be changed n Line chart default line type is solid, but chart shows different line type n Default data source "parent group" does not get any data from the parent group initially, only after refresh or reselection of "parent group" as datasource Reporting Table BB n Subtotal parameter keeps initial value, can not be changed n Default data source "parent group" does not get any data from the parent group initially, only after refresh or reselection of "parent group" as datasource Reporting Group BB n Default data source "parent group" does not get any data from the parent group initially, only after refresh or reselection of "parent group" as datasource All reported shortcomings have been fixed in version v7.5 SP1. 12.2.6 Papyrus Client AFP Viewer l New parameter: Specify that the sticker text is always visible With the new parameter ShowStickerText you can define that the sticker text is always displayed with the sticker without having to click or point on the sticker. This parameter replaces the drop-down menu in the View toolbar in version 7.5 that offered the same functionality. For more details, see chapter "ShowStickerText" in "Papyrus AFP Viewer Freeware Installation and Reference Guide (pavfirge)". getstartede V7.6 SP3 121/389 Appendix: main updates in V7.5 12.2.7 Papyrus Designer, Papyrus DocEXEC 12.2.7.1 Information relevant for DOCDEF developers l Line breaks in continuous text: SPACEBREAK(OFF) did not work as expected The SPACEBREAK subcommand in a TEXT or TEXTPROMPT command has an effect on the line breaking of the text to be printed. With SPACEBREAK(OFF), a line break can happen at any character and not only at space characters. Line breaks might happen in the middle of a word or a number. SPACEBREAK(OFF) in combination with SPACEBREAK(ON) can be used to keep an array of words on the same line. Papyrus DocEXEC in V7.5 did not react accordingly. This has been fixed in V7.5 SP1. For general information about SPACEBREAK, see chapter "SPACEBREAK" in "DocEXEC Reference Application Developer Guide (pdedge)". l AFPDS with resource GUIDs: reliable writing of resource GUIDs Application output format parameter Res. GUID makes Papyrus DocEXEC write GUIDs of resources from the Resource Collection into NOP records when generating the AFPDS. With resource GUIDs it is possible to exactly determine and use the right version of the resources for further processing like viewing, archiving or postprocessing (AFP import). Under certain conditions (e.g. empty resource cache) it could happen that not all resource GUIDs were written to the resource group. This has been fixed with V7.5 SP1. For more information about resource GUIDs, see chapter "APPLICATION-OUTPUT-FORMAT command" in "DocEXEC Reference Application Developer Guide (pdedge)". l New protected DOCDEF keywords with version 7.5 SP1: there were no new keywords introduced Protected DOCDEF keywords must not be used as names in applications (e.g. variable name, font name, document format name a.s.o.). If new protected keywords were implemented, customers should check their applications whether these protected keywords are used in their applications as names. If an existing application does contain a name which has become a protected keyword with this version, Papyrus Designer/Papyrus DocEXEC displays error message PPDE9999E ( l Papyrus Designer USE command: listing high number of includes takes too long Due to a change in V7.4 SP1, listing of include files (INC) in the Use command dialog took too long, if there was a high number of includes (20.000 - 30.000). This has been fixed with V7.5 SP1. l Generating PDF (DEFINEPDFOUTPUT): copy and paste from generated PDF improved PDF fonts can have a custom mapping. In this case copied text was not always pasted correctly in other Windows products. This has been fixed with V7.5 SP1 by enforcing a Unicode mapping table. l Papyrus Business Correspondence Solution: performance improvement by optimized object data caching When a business user in a Papyrus Business Correspondence Solution creates a document instance, function OMS_PREREAD is being executed. This function retrieves object data from the Object Space. The data reading functionality has been improved so that it only retrieves the information that is required to complete its operation. A persistent object cache has been implemented, which reduces the amount of data that is transferred during a data reading operation. For more information, see chapter "OMS_PREREAD" in "DocEXEC - Access to WebRepository Developer Guide (pdeoadge)". getstartede V7.6 SP3 122/389 Appendix: main updates in V7.5 12.2.8 Papyrus Objects (WebControl/WebRepository) 12.2.8.1 Papyrus Desktop l Object/Policy View - "Set all values" and "Clear all values" fixed When changing all values of a column by selecting Set all values or Clear all values", some rows that are not in the visible area were left unchanged. This problem has been fixed in V7.5 SP1. l Deleting states problem solved in state machine Deleting a state failed even if all state transitions have already been deleted. This problem has been fixed in V7.5 SP1. 12.2.8.2 Papyrus Objects system l Connection problem to Domain Controller of other broadcast domain solved Papyrus Objects kernel running as Windows Service could not connect to a Domain Controller in another broadcast domain (e.g. via VPN). This problem has been fixed in 7.5 SP1. 12.2.8.3 Papyrus Query Language (PQL) l $error no longer reset too early Using $ie to suppress error messages by the system, $error can be checked in the user-defined error handling to react if a problem occurs. In the 32-bit variant of Papyrus Objects Kernel $error was sometimes reset too early. This problem has been fixed in V7.5 SP1. For details on using $error, see "Error handling" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l PQL web library: pqlweb now handles an HTTP response from the web server even if sending the corresponding HTTP request is still in progress Before this correction pqlweb did not continue the HTTP protocol properly due to the seemingly too early sent response data. For details on load library pqlweb, see "pqlweb: Papyrus PQL web library" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l PQL editor: consistent use of UTF8 codepage for interpreting PQL source code The PQL editor used to interpret PQL source code in an inappropriate codepage. The source code was interpreted in the ISO-8859-1 codepage, but it should have been interpreted in UTF8. This had an effect on the correct handling of internal parameters. In one special case the PQL editor was unable to identify particular characters in the source code at opening of a data interface and issued error message PPCS0153E: Invalid ASCII Character 0xdf replaced with '?'. This problem has been fixed in V7.5 SP1. 12.2.8.4 Papyrus Depot l Depot search workplace n Incorrect index usage during search In case a workplace contained multiple workplaces with search functionality, and these workplaces used different search indexes, some inconsistencies occurred. This could have happened, for example, in an ADF workplace with Depot search workplace and Bounce handling workplace. This has been fixed in V7.5 SP1. getstartede V7.6 SP3 123/389 Appendix: main updates in V7.5 n Unwanted doubling of details tab A double click on a search result item lead to the index details tab being shown twice. This has been fixed in V7.5 SP1. A simple select (one click or up/down key) did not cause this problem. n Search without arguments produced incorrect result A search without arguments showed the result of the previous search. With V7.5 SP1 the entire database, limited by max number of results set by your administrator, is shown. n First search with '*' after a Login produced empty result If you searched with '*' after a login the result was empty. After using a different search criterion, '*' worked. With V7.5 SP1 '*' works all the time. n Clear button in search mask had no effect Previously all fields had to be emptied manually. With V7.5 SP1 the Clear button works and all fields can be emptied with a single click. n Switching the index type from template to class and vice versa caused login problems If users changed the index type in General settings this could result in them being no longer able to successfully login to the EYE Widgets workplace. Important objects from the DepotSearchAttributeSelectionContainer were removed. With V7.5 SP1 this is prevented. 12.2.8.5 Papyrus Adapters and Typemanagers l IMAP receiver: Support for file type "Multipart/Appledouble" IMAP receiver has been provided with support for Content-Type header value of multipart/appledouble. With V7.5 SP1, e-mail attachments, for example, JPEG with MIME type "image/jpeg" inside header "multipart/appledouble" can be imported. l SMTP/EWS/MAPI adapter: Avoid line feed (LF) without carriage return (CR) in e-mails Recently some e-mail servers started marking messages that contain a line feed (LF) without a carriage return (CR) as spam or stopped delivering them. Thus be conscious about this when designing e-mail templates and also verify existing templates. For more details, see Encoding considerations in RFC 2854. l LDAP adapter: Initialization of OpenSSL corrected The implementation of a new OpenSSL version caused an error in the initialization process of the LDAP adapter, which could make the Domain Controller dump in turn. This has been fixed in version v7.5 SP1. 12.2.8.6 Papyrus EYE Widgets l HTML editor widget: problem with image removal solved Removing an image by selecting it and pressing [Ctrl] + [X] sometimes lead to a dump. This problem has been fixed in V7.5 SP1. l When working in a view of a user interface message POEW0044W Unknown system attribute $NextVersion found is displayed When working in a view of a user interface based on Papyrus EYE Widgets (e.g. the 'Template Administrator' view in a Correspondence Solution) the error message POEW0044W Unknown system attribute $NextVersion found could be displayed. Although this message was reported during operation in an Correspondence-releated user interface, the user interfaces of all solutions (Correspondence Solution, Capture Solution, Reporting Solution, ACM Solution, ADF Solution) could be concerned as well under certain conditions. The cause for this message can be the event handling routines in Papyrus EYE Widgets. In 64-bit versions of the portal kernel that serves the user interfaces, the event handling routines did not pay attention to all supported attributes. This has been fixed in V7.5 SP1. getstartede V7.6 SP3 124/389 Appendix: main updates in V7.5 12.2.8.7 Papyrus WebPortal l Portal node: dumps because of memory overwrite under high load Under high load with parallel access to objects from a tool (e.g. web server), a memory overwrite could occur, which led to a dump. The memory overwrite has been fixed in V7.5 SP1. l Web server: inconsistent reaction of HTTP header Connection corrected Papyrus web server handled the HTTP header Connection inconsistently. By setting by HttpServerSettings attribute NonPersistentConnections the network connection will be closed after the response has been sent (HTTP header Connection: close is sent). Yet web server sent the HTTP header Connection: keep-alive. This reaction had the effect that in environments with multiple web servers some web servers suffered from ostensible loss of data. This means the web servers seemed to receive fewer requests than were sent. This problem has been fixed in V7.5 SP1. 12.2.9 Papyrus Server 12.2.9.1 AFP to PDF l Generate PDF/UA - parameter also on tool With this service pack the parameter was added to the tool. In previous versions the parameter only existed on the material. This allows for a more convenient activation. No need to change all materials but only update once on tool. For details, see chapter "Generate PDF/UA (PDFtGeneratePDF_UA)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Copy and paste improved PDF fonts can have a custom mapping. In this case copied text was not always pasted correctly in other Windows products. This has been fixed by enforcing a Unicode mapping table. 12.2.9.2 IPDS l Starting IPDS jobs manually now also possible under Linux/Unix So far manually starting an IPDS job via drag and drop onto an IPDS tool was not possible under Linux/Unix, causing errors POKN0172E and PPIP2056F, leaving the task in its running step state. This problem has been fixed in V7.5 SP1. 12.2.9.3 E-Mail l Avoid line feed (LF) without carriage return (CR) in e-mails Recently some e-mail servers started marking messages that contain a line feed (LF) without a carriage return (CR) as spam or stopped delivering them. Thus be conscious about this when designing e-mail templates and also verify existing templates. For more details, see Encoding considerations in RFC 2854. getstartede V7.6 SP3 125/389 Appendix: main updates in V7.5 12.3 Updates in V7.5 SP2 12.3.1 General changes l Font resources: keyword $SystemFont$ searches for fonts in user font folder and system font folder On Windows operating systems, the $SystemFont$ keyword enables Papyrus products to use TrueType and OpenType fonts from the Windows operating system. The keyword can be entered in the resource library profile (default.lbp) and in resource specification attributes in Papyrus Objects, for example in the Resource library attribute of AFPDS data objects. A recent change in Windows operating systems regarding the storage of fonts made a change in the keyword's search sequence necessary. With Windows 10 1809, users can install fonts not only in the system folder C:\Windows\Fonts but also in C:\Users\ 12.3.2 Papyrus Automated Document Factory Solution 12.3.2.1 Information relevant for administrators and developers l Automated Document Factory Solution n Automated Document Factory Solution Workplaces: migration to a new Papyrus EYE Widget workplace engine with V7.5 V7.5 saw a new generation of engines for Papyrus EYE Widget workplaces. Although introduced in V7.5, the change has been announced for V7.5 SP2 for the first time. For more information, see chapter "Information relevant for administrators and developers" in "Papyrus Software - Getting Started and News General Information (getstartede)". n ADF bundling - robustness improved Previously nothing was returned when no job matched the bundling criteria. This could cause an error. With V7.52 this has been fixed and an empty set is returned. l Bounce Handling Solution n Alternative PED rule can be called in ExecuteBounceAction Previously a bug prevented the execution of an alternative rule if it was defined as an action type. This has been fixed in V7.5 SP2. l Depot search workplace n Settings Explorer: result limit handling corrected Previously the user could configure a higher value than the administrator defined in Settings Explorer. This has been fixed in V7.5 SP2. If the user enters a higher value, it is automatically changed to the maximum the administrator allowed. getstartede V7.6 SP3 126/389 Appendix: main updates in V7.5 n Customization of search results display: functional enhancements and fixes In the Depot search settings it is possible to define a component to display the search result on the right hand side. - In previous versions the 'Details' tab was not shown if a 'Class defined component' was used. This has been fixed in V7.5 SP2. (Since V7.5 the 'Details' tab changes its name to the name of the index of the selected found item.) - In previous versions Expert mode and 'Class defined component' did not work at the same time. This has been remedied in V7.5 SP2. - In previous versions invalid 'Class defined component' settings caused an error. With V7.5 SP2 there is a fallback to the default behavior (i.e normal view). For details, see chapter "Customize display of search results - Component selector" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". 12.3.2.2 Information relevant for business users l ADF workplaces n Queue cockpit and Job operations - buttons renamed Based on user feedback some button captions were changed to more business user friendly terms. l Depot search workplace n Search in attributes that are arrays is now possible Usually an attribute is a single value like a name or a number. Sometimes however multiple values are stored in a single attribute. The data type of this attribute is called array. Entering the first value to search for is done just like in any other field. In order to add an additional value a green plus icon is available. Removing values is done with a red minus icon. In V7.5 SP2 these values are concatenated with OR. Thus if the array contains any of the values you entered, the item will be found. In V7.6 there will be an option to also use AND. In this case only items that contain all the criteria you entered for the attribute will be found. n CSV export: functional enhancements and fixes - Export of arrays is now supported. The values of the array attribute are saved within curly brackets, separated by a comma. - The CSV preview is now updated immediately, when changing the columns to export. - Under certain conditions the CSV export was empty. - Changes to export settings were saved although Cancel was clicked. All changes and fixes have been implemented in V7.5 SP2 n Incorrect focus changes Previously the focus changed to the first item in the result list after editing a different item. There were also some problems when only a single item was found. This has been fixed in V7.5 SP2. n Viewer plugin handling Previously the wrong plugin was loaded if the object contained an unknown extension. This caused some problems. With V7.5 SP2 no plugin is loaded in this case. PDF, DOCX, DOC, ODT, HTML etc. are reliably recognized if the correct data class was used. 12.3.3 Papyrus Business Correspondence Solution 12.3.3.1 Information relevant for business users Improvements are provided with this service pack and affect the following use cases: l Template library: "Reset to previous version" button was not visible After a new version is created in the Template library area on the Administrator main view, the Reset to previous version should be displayed, which was under certain circumstances not the case. This is fixed with V7.5 SP2. getstartede V7.6 SP3 127/389 Appendix: main updates in V7.5 l Searching: search functionality was not working as expected When template administrators switch between the Simple search and the Advanced search, the results of the Simple search are not shown properly after switching from Advanced search back to Simple search. This is fixed with V7.5 SP2. l Release Management workplace: shortcut [Ctrl]+[N] to create a release was not working Pressing [Ctrl]+[N] on the Release Management workplace did not reliably open the Release templates dialog, which is fixed with V7.5 SP2. l Check boxes in PDF documents: check boxes were synchronized if "Keep form names" is selected If synchronized user input for PDF documents is defined (Keep form names check box is selected for the PDF data object), check boxes are not synchronized anymore. Without V7.5 SP2, selecting or deselecting a check box in a prompted PDF document selects or deselects all other check boxes in the PDF document. l Stickers: sending a document using a sticker to the supervisor was not working Clerks can add a sticker to a document and then send the document to the supervisor by clicking the Done button. Without V7.5 SP2, the document using a sticker cannot be moved to the Supervisor Queue because an error message is displayed after the Done button is clicked. l Image variants n Colors changed after upload When template administrators upload image resources of a certain size in the image variant editor, the colors could be unexpectedly changed, which is fixed with V7.5 SP2. n Overlay image in document defined as dynamic image generates error message When template administrators use an overlay image (OVL) in an image variant and then change it to a dynamic image by defining a variable name for it, they can use the image variant in a document. Without V7.5 SP2, an error message is displayed when the image is used in the document. 12.3.3.2 Information relevant for administrators and developers Improvements are provided with this service pack and affect the following use cases: l Object Space update to V7.5 SP2: Error during import of system and application frameworks During the import of system and application frameworks, a misconfiguration in 0490_BC_CORE_BusinessCorrespondence_Core can cause the following transfer files going into error. This prevents the upgrade of the Domain by the system administrator. n 1850_BC_WDG_BusinessCorrespondence_EyeWidgets n 1880_BC_WIZ_WDG_BusinessCorrespondence_Wizard_EyeWidgets n 1980_BC_CM_WDG_BusinessCorrespondence_ChangeManagement_EyeWidgets n 2220_WBC_WDG_WordToBusinessCorrespondence_EyeWidgets In the case that this issue arises then the 0490_BC_CORE_BusinessCorrespondence_Core must be removed and re-imported after the object cache size was increased to 350 MB minimum. l Extension to PQL data read routine: use of data interface Document material supports the implementation of a data interface allowing for dynamic data replacing the direct use of a PQL set. This is enhancement was already implemented with V7.4 SP1 but is announced with V7.5 SP2 for the first time. getstartede V7.6 SP3 128/389 Appendix: main updates in V7.5 12.3.4 Papyrus Business Document Capture Solution 12.3.4.1 Information relevant for administrators and developers l Capture document definition: Methods for definition set handling The class Capture document definition has been provided with methods (toolbar buttons) which allow to add, delete and edit a definition set. For details, see chapter "Add, design and delete a definition set of a Capture document definition" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Capture document depot: Depot key definition of derived class ignored If a depot key was defined for a class and another depot key for a class derived from this class, then it was not ensured for the derived class that always the correct depot key (depot key of the derived class) was used. Fixed in the version v7.5 SP2. l Document extractor: Recover tool method missing for state "Intervention required" If the Document extractor tool was in state "Intervention required", then an appropriate method to recover to the tool was missing. Fixed in version v7.5 SP2. l Capture adapters: Tenant cannot be changed If a Capture Solution had two or more tenants, then it was not possible to change the tenant of an adapter. Fixed in version v7.5 SP2. l Capture solution wizard: Minor improvements n When a Capture solution is duplicated, then all rules of the duplicate are enabled. n Previously, some objects were only referenced instead of duplicated, when a Capture Solution was duplicated. As of the version v7.5 SP2 it is ensured that all objects are duplicated. n If a document definition of a Capture solution is empty, i.e. it contains no child objects, then it will be initialized, i.e. provided with the default folders. l MS DOC processing: Image rendering of an MS Word 2003 file produces different results depending on the printer driver Rendering an image of an MS Word 2003 file produces different images depending on the default printer driver set on the local machine resulting in differences in the line wrapping. This can be solved by installing the printer driver "Generic/Text" or Papyrus Printer Driver as local printer. For details, see the chapter "Image rendering of Microsoft Word file produces different results depending on the printer driver" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l IMAP adapter: IncaMail secured emails cause IMAP crash Emails secured with IncaMail (an email security service operated by Swiss post) caused crashes of IMAP adapter. Fixed in version v7.5 SP2. l IMAP adapter: E-mails with formatted subjects cause dumps E-mails with certain (unusual) formatting of subjects forced IMAP adapter to dump. Fixed in version v7.5 SP2. l Definition set "Invoice": Available for all document classes Previously, the definition set "Invoice" could only be used for document classes named "Invoice". As of the version v7.5 SP2 the definition set "Invoice" can be selected for any document class. l Definition set "Invoice": Usage of the reco engine Tesseract4 Previously, the definition set "Invoice" used the reco engine Finereader 10 (Omnifont10). As of the version v7.5 SP2 the definition set "Invoice" uses the reco engine Tesseract4. 12.3.4.2 Information relevant for business users Information relevant for Papyrus Client Capture users getstartede V7.6 SP3 129/389 Appendix: main updates in V7.5 l Completion view: Return attribute of parent class in Lookup not used When searching for a record in the table lookup of the Completion view of the Capture GUI "Capture workplace", return attributes referring to a parent class attribute, did not return a result. This has been fixed in version v7.5 SP2. Information relevant for Papyrus Scan users l Scan view: Button "Split" does not work correctly The button "Split" of the Scan view did not work as expected if the Document depot node of the Capture Solution was offline. This has been fixed in the version v7.5 SP2. l Scan view: Button "Insert scanned file before" does not work correctly The button "Insert scanned file before" did not work as expected if different file types (TIFF, PDF, etc.) were used as sources. Depending on the file type, the files were inserted before or after the selected item. Fixed in version v7.5 SP2. Information relevant for Capture Business Designer users l Capture Business Designer: Improvements of the training algorithm The training algorithm of the Capture Business Designer has been improved in the version v7.5 SP2. l Capture business administrator workplace: New content not updated during multi-user training If two users were using the same case on the Capture business administrator workplace and one of them added new content, then the content view was not updated for the other user. Fixed in the version v7.5 SP2. 12.3.5 Papyrus Reporting Solution 12.3.5.1 Information relevant for administrators, developers and business users l Workplaces: migration to a new Papyrus EYE Widget workplace engine with V7.5 V7.5 saw a new generation of engines for Papyrus EYE Widget workplaces. Although introduced in V7.5, the change has been announced for V7.5 SP2 for the first time. For more information, see chapter "Main changes in V7.5" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". 12.3.6 Papyrus Designer, Papyrus DocEXEC 12.3.6.1 Information relevant for DOCDEF developers l Protected DOCDEF keywords: there were no new keywords introduced with version 7.5 SP2 Protected DOCDEF keywords must not be used as names in applications (e.g. variable name, font name, document format name a.s.o.). If new protected keywords were implemented, customers should check their applications whether these protected keywords are used in their applications as names. If an existing application does contain a name which has become a protected keyword with this version, Papyrus Designer/Papyrus DocEXEC displays error message PPDE9999E ( getstartede V7.6 SP3 130/389 Appendix: main updates in V7.5 12.3.7 Papyrus Objects (WebControl/WebRepository) 12.3.7.1 Papyrus Adapters and Typemanagers l IMAP receiver and SMTP sender: Certified e-mails - improved support PEC (Posta Elettronica Certificata) is an e-mail standard commonly used in Italy, Switzerland and Hong Kong. It plays a crucial role in these countries, because all legally impacting official e-mail communications between organizations and companies (either public or private ones) should take place through PEC mailboxes (e.g. for exchanging contracts, invoices, GDPR complaints, etc.). Papyrus is able to interface with external third-party PEC systems, but does not provide any built-in/native PEC services. The following two use cases are supported with V7.5 SP2: Importing certified e-mail (PEC) messages via IMAP receiver adapter and sending certified e-mail (PEC) messages from Papyrus WebRepository through a third-party legally approved PEC provider via SMTP sender tool. 12.3.7.2 Papyrus Depot l Depot search workplace n Search in attributes that are arrays is now possible Usually an attribute is a single value like a name or a number. Sometimes however multiple values are stored in a single attribute. The data type of this attribute is called array. Entering the first value to search for is done just like in any other field. In order to add an additional value a green plus icon is available. Removing values is done with a red minus icon. In V7.5 SP2 these values are concatenated with OR. Thus if the array contains any of the values you entered, the item will be found. In V7.6 there will be an option to also use AND. In this case only items that contain all the criteria you entered for the attribute will be found. n CSV export: functional enhancements and fixes - Export of arrays is now supported. The values of the array attribute are saved within curly brackets, separated by a comma. - The CSV preview is now updated immediately, when changing the columns to export. - Under certain conditions the CSV export was empty. - Changes to export settings were saved although Cancel was clicked. All changes and fixes have been implemented in V7.5 SP2 n Settings Explorer: result limit handling corrected Previously the user could configure a higher value than the administrator defined in Settings Explorer. This has been fixed in V7.5 SP2. If the user enters a higher value, it is automatically changed to the maximum the administrator allowed. n Incorrect focus changes Previously the focus changed to the first item in the result list after editing a different item. There were also some problems when only a single item was found. This has been fixed in V7.5 SP2. n Viewer plugin handling Previously the wrong plugin was loaded if the object contained an unknown extension. This caused some problems. With V7.5 SP2 no plugin is loaded in this case. PDF, DOCX, DOC, ODT, HTML etc. are reliably recognized if the correct data class was used. getstartede V7.6 SP3 131/389 Appendix: main updates in V7.5 n Customization of search results display: functional enhancements and fixes In the Depot search settings it is possible to define a component to display the search result on the right hand side. - In previous versions the 'Details' tab was not shown if a 'Class defined component' was used. This has been fixed in V7.5 SP2. (Since V7.5 the 'Details' tab changes its name to the name of the index of the selected found item.) - In previous versions Expert mode and 'Class defined component' did not work at the same time. This has been remedied in V7.5 SP2. - In previous versions invalid 'Class defined component' settings caused an error. With V7.5 SP2 there is a fallback to the default behavior (i.e normal view). For details, see chapter "Customize display of search results - Component selector" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". 12.3.7.3 Papyrus Resource Collection l Automatic clean-ups: "Resource Creation Queue" added to the list of queues and folders for clean-up In Resource Settings, the Automatic clean-ups attribute contains the list of queues and folders that will be deleted automatically by a scheduled action. With V7.5, Resource Creation Queue was added to the above list of queues and folders. Even though this was available in V7.5, it is announced in the V7.5 SP2 for the first time. For more details, see "Resource Settings" in chapter "Setting up the resource import/creation adapter using wizard" in "" l Wizards: New wizard views available for Resource Group management In V7.5, a new wizard view is available to update the existing Resource Groups. Even though this wizard was available in V7.5, it is announced in the V7.5 SP2 for the first time. For more details, see "12.1.11.4 Papyrus Resource Collection". 12.3.8 Papyrus Postprocessing/Printpool 12.3.8.1 Papyrus Tuner l IOB PDF page dimension - new parameter This parameter allows to define a limit to the page size. It should only be used to prevent dumps in conjunction with AFP files containing PDF files with a very large page size. For details, see chapter "IOB PDF page dimension (IobPdfPageDimension)" in "Papyrus Tuner Reference Guide (ptunrge)". 12.3.9 Papyrus Server l New parameter: IOB PDF page dimension With this service pack the parameter was added to the tools of AFP to Thumbnail, Fax G3, HTML, PCL and Postscript. This parameter allows to define a limit to the page size. It should only be used to prevent dumps in conjunction with AFP files containing PDF files with a very large page size. For details, see chapter "IOB PDF page dimension (IobPdfPageDimension)" in "Papyrus Server - PostScript Reference Guide (psepsrge)". 12.3.9.1 IJPDS l Bug in transparency mask fixed Adjacent images were sometimes rendered incorrectly. They were separated by unwanted white vertical bars. This has been fixed in V7.5 SP2. getstartede V7.6 SP3 132/389 Appendix: main updates in V7.4 13 Appendix: main updates in V7.4 If you upgrade from an earlier version to the newest version, use the appendix to see a history of all changes that have accumulated. Note that the cross-references in the appendix refer to chapters in documents of the same version. This means that some of the History of Changes entries in the appendix may include cross-references to chapters that do not exist anymore in the newest version of the document or whose information was updated in the meantime. If you are in such a case interested in the details you will need to access the documents of exactly that version. 13.1 Main updates in V7.4 This delivery includes Papyrus products in release level V7.4. 13.1.1 General changes l Business Designer: new product available Papyrus Business Designer (short: Business Designer) is now available as a product for business users to provide all the functions that are required to create and deliver business correspondence. Business Designer requires a separate product authorization and can be used only with a concurrent product authorization. For more details, see chapter "Specific prerequisites" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Papyrus Client - Business Correspondence User Guide (pocfuge): new document name In alignment with the new product available as Business Designer, the document formerly called "Papyrus Client - Business Correspondence User Guide (pocfuge)" is now called "Business Designer and Papyrus Client - Business Correspondence User Guide (pocfuge)". For more details, see "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Tenant 'ISIS' changed to 'Papyrus' Papyrus solutions implement tenants in order to separate discrete departmental structures or customers, which require individual settings. ISIS Papyrus employs a tenant for running sample applications. This tenant used to be named 'ISIS' in Papyrus software versions prior to V7.4. With 7.4 the tenant's name changes to 'Papyrus'. With version 7.4 SP1 the name change is announced for the first time. The name change has only an impact on Papyrus sample applications. Customer applications should in any case always employ custom tenants and never use the 'Papyrus' (respectively 'ISIS') tenant. Customer-specific tenants ensure that customer applications are spared in the event of changes to the 'Papyrus' tenant. For more details, see chapter "General changes" in "Papyrus Software - Getting Started and News General Information (getstartede)". 13.1.2 Papyrus Adaptive Case Management Solution 13.1.2.1 Information relevant for administrators and developers l Cancel / Delete buttons grouped To avoid accidental cancelling or deleting of cases, the buttons for cancelling and deleting were grouped. Additionally a dialog allows the user to enter a reason for cancelling. For more details, see chapter "Delete a Case" in "". getstartede V7.6 SP3 133/389 Appendix: main updates in V7.4 l New Case Reopen Functionality A manually closed or cancelled case can be reopened. Reopening automatically reactivates those tasks which were cancelled by the former case closing/cancellation. For more details, see chapter "Reopen a Case" in "Papyrus Client - Adaptive Case Management User Guide (poacmuge)". 13.1.2.2 Information relevant for business users l Cancel / Delete buttons grouped To avoid accidental cancelling or deleting of cases, the buttons for cancelling and deleting were grouped. Additionally a dialog allows the user to enter a reason for cancelling. For more details, see chapter "Delete a Case" in "". l New Case Reopen Functionality A manually closed or cancelled case can be reopened. Reopening automatically reactivates those tasks which were cancelled by the former case closing/cancellation. For more details, see chapter "Reopen a Case" in "Papyrus Client - Adaptive Case Management User Guide (poacmuge)". 13.1.3 Papyrus Automated Document Factory Solution l Depot Search Workplace The following improvements were implemented. While the improved Save button behavior is automatically available to the business user (e.g. in the ADF workplace), the other two features have to be set up by the administrator/developer in the Depot search settings in the Settings Explorer. Save button only available if changes were made The Depot Search UI allows to configure a lot a of parameters. Now the Save button is greyed out until changes were made. Also search in attributes of child classes In the Depot search settings the attributes "Select search attributes", "Select return attributes", "Select return attributes" and "Select details attributes" have the new column Include Class Tree Attributes. By setting this value to true attributes of child classes are also selectable as search criteria. For more details, see chapter "Search in attributes of child classes" in "". Customize result display with own components Via the Depot search settings it is possible to define a component to display the search result on the right hand side. In addition to the default view a user or class dependent component can be loaded. This allows for instances to display an ACM case within the Depot Search. For more details, see chapter "Customize display of search results - Component selector" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l New icons Papyrus Software started modernizing and applying a new concept to several icons. Adapters, Tasks, Agents, Data, Tools, Materials, Queues and Folders are benefiting. The system of status bars and badges allows to quickly recognize the current state of affairs. These improvements are not only visible in Papyrus Desktop but also in the business user interfaces. Not all icons and screenshots are updated yet. For details, see chapter "Iconography" in "WebRepository Application Developer Guide (pwride)". getstartede V7.6 SP3 134/389 Appendix: main updates in V7.4 13.1.4 Papyrus Business Capture Solution 13.1.4.1 Information relevant for administrators and developers l Capture lookup: Type manger DB for Objects single line lookup Objects single line lookup not only can use a Papyrus depot as data source but also an external database by means of Type manager DB. For details, see chapter "Type manager DB for Capture" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Capture Solution setup wizards: feature extensions n Select existing depots Now already existing Basedata depot and document depot can be selected for the Capture solution. For details, see "Setup a Capture Solution with the Capture solution creation wizard" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". n Add adapter to solution This simple wizard allows to add additional adapters to the Adapter folder of an already existing Capture solution. For details, see "Setup a Capture Solution with the Capture solution creation wizard" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Papyrus Capture Server: specification of page processing mode Attribute "Page strategy" of Papyrus Capture Server (~ FixForm extractor or FreeForm extractor) allows to specify the page processing mode of the extraction tool. For details, see section "EXTRACTOR (CapExtractor)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l New Capture (BDC) Eye Widgets settings attributes The following new Capture (BDC) Eye Widgets settings attributes have been added: n Scan view thumbnail size allows to change the thumbnail size of thumbnails viewer of Scan view n DWP view thumbnail size allows to change the thumbnails size of thumbnails viewer of Document workplace n Admin View thumbnail size allows to change the thumbnails size of thumbnails viewer of Capture administration workplace n Scan view image viewer toolbar allows to activate/deactivate particular features of the image viewer of Scan view n Completion view image viewer toolbar allows to activate/deactivate particular features of the image viewer of Completion view n Administration view image viewer toolbar allows to activate/deactivate particular features of the image viewer of Capture administration workplace n Highlight validated fields document states allows to specify document states for which validated (corrected) fields a highlighted in color For details, see chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Class Capture Document: new methods Class Capture Document (CapDocument) has been provided with two new methods: - Get cache data: allows to retrieve the extraction data for a dedicated page - Get parent document: Returns object Id of TopRoot For details, see Papyrus WebRepository online help. getstartede V7.6 SP3 135/389 Appendix: main updates in V7.4 l Papyrus Capture Designer FixForm: new color processors The following color-related processors are available in order to recognize colored regions on document pages. Normalization processors: - color depth/recognize and tag colors - color depth/select tagged color and the recognition processor Colors. For details, see "Normalization" in "Designer Capture Application Developer Guide (pcddge)", "Color depth / select tagged color" in "Designer Capture Application Developer Guide (pcddge)", and "Colors" in "Designer Capture Application Developer Guide (pcddge)". l FixForm normalization processors: new attribute color depth/color space conversion Normalization processor Color Depth/Color Space Conversion has been provided with new attribute "preserve lower color depth". If this attribute is set, if set, the color space will not be converted if the image has already a "lower" color space which results in a performance improvement. For details, see section "color depth / color space conversion" in "Designer Capture Application Developer Guide (pcddge)". l Papyrus Capture Server recognition engines n New "Tesseract4" recognition engine Tesseract4 is an open source recognition engine for printed characters under Apache 2.0 license which can be used as alternative to the OmniFont engines. As of version v7.4 Tesseract4 is available and installed by default with Capture applications. The product authorization for Tesseract4 is included into the Capture packages, thus no additional product authorization is required. The reco engine Tesseract4 is supported by the following Capture applications: u Papyrus Capture Designer/FixForm u Papyrus Capture Designer/FreeForm® u Papyrus Capture Server/FixForm u Papyrus Capture Server/FreeForm® u Papyrus Categorizer u Papyrus Scan Receiver For details, see chapter "Tesseract4" in "Designer Capture Application Developer Guide (pcddge)". n New default for full page recognition This new recognition processor combines the features of the engines "tesseract4" and "standard" and allows to extract samples that contain printed text as well as handwritten text. For details, see chapter "FullPageNew" in "Designer Capture Application Developer Guide (pcddge)". l FixForm designer option "Extract current page only" This new option allows to restrict the extraction in Papyrus Capture Designer/FixForm to the page currently selected in the image viewer. For details see, chapter "Menu "Options"" in "Designer Capture Application Developer Guide (pcddge)". l FixForm design: table definition A new chapter about creating a table definition with Payprus Capture Designer/FixForm has been provided. For details, see chapter "Table definition" in "Designer Capture Application Developer Guide (pcddge)". l FixForm design: multiple table definitions Now it is possible to define more than one table definition in a document class definition. For details, see section "Multiple table definitions in a document class" in "Designer Capture Application Developer Guide (pcddge)". 13.1.4.2 Information relevant for business users Information Relevant for Papyrus Client Capture Users getstartede V7.6 SP3 136/389 Appendix: main updates in V7.4 l Capture workplace: menu entry "Open email" The menu "Document" of "Document workplace" view as well as of "Completion" view of the Capture UI "Capture workplace" has been provided with a new entry "Open email", which allows to open an e-mail of a document with an e-mail client. For details, see section "Document | Open email" in "Menu "Document"" in "Papyrus Client - Capture User Guide (popcfuge)" . l Capture administration workplace: menu "Documents" The tab "Document Depot" of "Capture Administration Workplace" has been provided with an additional menu "Documents" the entries of which can alternatively used to the same functions available on the toolbar of the thumbnails viewer of this tab. For details, see section "Menu bar" in "Papyrus Client - Capture User Guide (popcfuge)". l Completion view: multi-table display on tabs Now "Completion" view supports multi-table display on tabs, i.e. each extracted table is displayed in a separate tab in the frame "Form/Table" of "Completion" view as well as on "Document Depot" view of "Capture administration workplace". For details, see section "Multiple table tabs" in "Papyrus Client - Capture User Guide (popcfuge)". l Document workplace: import files from file system by drag and drop The scope of the feature "Import files from file system by drag and drop" has been extended. Until this version, files could only be dropped on pages of a document in thumbnails viewer of "Document workplace" view. Now it is also possible to drop files from file system onto documents in thumbnails viewer. For details see, section "Import files from file system by drag and drop" in "Papyrus Client - Capture User Guide (popcfuge)". l Document workplace view: button "Split" supports multiple splitting Button "Split" of "Document workplace" view now alsow supports multiple splitting of a document in thumbnails viewer. For details, see section "Button "Split"" in "Papyrus Client - Capture User Guide (popcfuge)". l Document workplace view: change thumbnail size The new settings attribute "DWP view thumbnail size" allows to select between three different sizes for the thumbnails in the thumbnails viewers of Document workplace view. For details, see chapter "Thumbnail viewer" in "Papyrus Client - Capture User Guide (popcfuge)". l Capture administration view: change thumbnail size The new settings attribute "Administration view thumbnail size" allows to select between three different sizes for the thumbnails in the thumbnails viewers of Capture Administration workplace. For details, see chapter "Frame "Thumbnails"" in "Papyrus Client - Capture User Guide (popcfuge)". l Document workplace view: activate/deactivate features of image viewer The new settings attribute "DWP view image viewer toolbar" allows to activate/deactivate particular features of image viewer of Document workplace view. For details, see chapter "Image viewer (data viewer)" in "Papyrus Client - Capture User Guide (popcfuge)". l Completion view: activate/deactivate features of image viewer The new settings attribute "Completion view image viewer toolbar" allows to activate/deactivate particular features of image viewer of Completion view. For details, see chapter "Image viewer" in "Papyrus Client - Capture User Guide (popcfuge)". getstartede V7.6 SP3 137/389 Appendix: main updates in V7.4 l Capture administration workplace: activate/deactivate features of image viewer The new settings attribute "Administration view image viewer toolbar" allows to activate/deactivate particular features of image viewer of Capture administration workplace. For details, see chapter "Frame "Details/Page view/Extraction"" in "Papyrus Client - Capture User Guide (popcfuge)". l Completion view: feature "Highlight validated fields" for any document state The new settings attribute "Highlight validated fields document states" allows to specify the document states for which validate (corrected) fields are highlighted with colors on "Completion" view of the Capture UI "Capture Workplace". For details, see section "Highlight validated fields" in "Papyrus Client - Capture User Guide (popcfuge)". Information Relevant for Papyrus Scan Users l Scan view: button "Split" supports multiple splitting Button "Split" of "Scan" view (views "Scanned items" and "Search") now supports multiple splitting of a document in thumbnails viewer. For details, see section "Button "Split"" in "Capture Scan Administrator and User Guide (poscanauge)". l Scan view: change thumbnail size The new settings attribute "Scan view thumbnail size" allows to select between three different sizes for the thumbnails in the thumbnails viewers of "Scan" view. For details, see chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Scan view: activate/deactivate features of image viewer toolbar The new settings attribute "Scan view image viewer toolbar" allows to activate/deactivate particular features of image viewer. For details, see chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". 13.1.5 Papyrus Business Correspondence Solution 13.1.5.1 Information relevant for administrators and developers l Icons: Icons in Papyrus Desktop consolidated redesign for better user experience All icons in Papyrus Desktop have been redesigned to present a modern and consistent look. With the new icons, system users can complete their tasks of configuration and extending a Papyrus Business Correspondence Solution. Please note that some of the figures in this user guide may still show the old icons or logos. Updating icon instances that contain references to the previous icon The icon references of the instances will be updated after the execution of the Installation/update finalization for all frameworks PQL script. It is important to ensure that all operational nodes and even those nodes used for background processes are available so that icon reference updates to instances existing before the upgrade process are applied in a consistent and timely manner across the whole domain environment. For more details, see chapter "Installation and update finalization scripts for all frameworks" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 138/389 Appendix: main updates in V7.4 l Include Files: updating Variable Include (INC) Files After the upgrade process it is important that the variable include files (INC) are regenerated. This is to ensure that the correct version of the include file is used. This operation must be directly performed after the upgrade process has been performed. For more details, see chapter "Update variable include files" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Calendar controls for date form element: show month names depending on region The calendar controls on Papyrus Business Designer and Papyrus Business Designer/HTML are available now with a regional language. For example, the regional language definition for DEU can be set to de_DE so that the first month of the year is named "Januar", as opposed to the regional language definition de_AT, which would show "Jänner". For more details, see chapter "Define regional languages for calendar control month based upon available languages" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Workplace operations: custom methods can be defined for clerks and supervisors The clerk and supervisor workplace views can be extended to include additional method operations. For more details, see chapter "Create custom methods in the Clerk and Supervisor views" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Fillable Text Fields in PDF: can be synchronized On the PDF object, the Keep form names check box can be selected if values entered into a user input field should be taken over into other fields in the document. For more details, see chapter "Synchronize fillable text fields in PDF" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Execution points: supported in multi-part documents Execution points can now also be used in multi-part documents by adding them under the Multipart Document Output Options. For more details, see chapter "Develop custom code entry points in a document structure and DOCUMENT material" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l "Execute" building blocks: variable groups can be selected to make variables available for simulation For an Execute building block, you can define which variable groups are used so that these variables are then available for the business user in the simulation. For more details, see chapter "Define variables for simulation of execute building blocks" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Fonts: combine into font groups In order to configure fallback fonts, a font can be defined as being part of a font group by entering a value into the Font group attribute. For more details, see chapter "Define fallback fonts" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Settings dialog: Correspondence-specific settings can be made available The system administrator can configure an additional tab in the Settings dialog that provides Correspondence-specific settings to the business user. For more details, see chapter "Define custom settings for the business user" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 139/389 Appendix: main updates in V7.4 l Compatibility settings: "No variable representation" available If cleared, for comparing variable number formats, two values are used now in order avoid issues in IF conditions or custom includes. For more details, see chapter "Configuring correspondence compatibility settings support for previous releases" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". "Ignore widow and orphan in table" available If selected, widow and orphan control settings are ignored for text in tables. For more details, see chapter "Configuring correspondence compatibility settings support for previous releases" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". "Use margin definition from current page" available If cleared, items in layouts are positioned depending on the current margin definition. For more details, see chapter "Configuring correspondence compatibility settings support for previous releases" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". 13.1.5.2 Information relevant for business users l Business Designer: new product available Papyrus Business Designer - Correspondence (short: Business Designer) is now available as a product for business users to provide all the functions that are required to create and deliver business correspondence. Business Designer requires a separate product authorization and can be used only with a concurrent product authorization. For more details, see chapter "Specific prerequisites" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Business Designer and Papyrus Client - Business Correspondence User Guide (pocfuge): new document name This is the first edition of the "Business Designer and Papyrus Client - Business Correspondence User Guide (pocfuge)". The document was formerly called "Papyrus Client - Business Correspondence User Guide (pocfuge)". l Icons in Business Designer: consolidated redesign for better user experience All icons in Business Designer and Papyrus Client have been redesigned to present a modern and consistent look. With the new icons, business users can complete their everyday tasks of designing documents and building blocks faster and more efficient. Please note that some of the figures may still show the old icons or logos. For more details, see chapter "Business user interface" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Release activation: can be canceled for releases in Close pending stage Release managers can cancel activation for releases that are in Close pending stage. If activation is canceled, the release goes back to the test supervisor. For more details, see chapter "Cancel activation for a release in close pending stage" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 140/389 Appendix: main updates in V7.4 l Continue with next: different delimiters can be defined for concatenating text positioning elements Template administrators are now able to define specific delimiters for combining text positioning elements in a document template, e.g. "," or no delimiter at all. In the past, the text positioning elements were always separated by a blank. For more details, see chapter "Combine text positioning elements (Continue with next)" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Widow and orphan control: is also applied to a page break in a table Widow and orphan control defined for texts now also applies to paragraphs in tables. If required, widow and orphan control can be ignored for tables, as it was before. For more details, see chapter "Define widow and orphan control in tables" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l All workplaces: details area can be hidden Business users working in building block editors can hide the details area in the left panel with the Name and Description fields in order to increase the size of the preview area. For more details, see chapter "Show and hide details area in building block editors" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Bug reports and comments: are moved with the item between releases If production hotfix release managers move an item to another release, the bug report is moved with the item. If an unedited item with a bug report is deleted, the bug report is moved back to the bug reporting container. For details, see chapter "Working with bug reports" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Comments: are moved with the building block If template administrators or release managers move an item to another release, any comments added to this item are moved too. For more details, see chapter "View and add building block comments" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l PDF prompts: synchronize text user input fields in PDF Template administrators can define that values entered into a user input field in the PDF document are automatically taken over into other fields in the document. For more details, see chapter "Synchronize text prompts in PDF" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l User input fields: define for serial letters (batch) Template administrators defining user input fields in document templates for serial letters can now define whether the clerk has to fill out all the input fields per document or if the clerk can fill out the document once and the values are taken over for all other documents. For more details, see chapter "Define text input fields for serial letters (batch)" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Variables: custom formats can be defined for negative and zero values Template administrators working with variables can now define custom format for negative and zero values of integer and float types. For more details, see chapter "Number formats in variables" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Multi-part documents: Execution points are supported Execution points defined by the system administrator under multi-part document output options are supported. For more details, see chapter "Create a multi-part document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 141/389 Appendix: main updates in V7.4 l Settings dialog: additional tab may be available If defined by the system administrator, an additional tab is available in the Settings dialog that provides Correspondence-specific settings to the business user. For more details, see chapter "Define settings" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Simulation: variables used in "Execute" building blocks can be made available In order to have the variables used by an Execute building block available in a simulation, the system administrator must select the variable groups. For more details, see chapter "Introduction to simulation" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Wizard forms: table form controls are available Template administrators working with wizard forms can define tables by using the Group form element. For more details, see chapter "Define a form table" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". 13.1.6 Papyrus Reporting Solution 13.1.6.1 Information relevant for business users l Reporting Solution Tutorial A Reporting Solution Tutorial has been added to this manual which will provide the user with a quick and smooth introduction into the basic tasks and activities related to the usage of Papyrus Reporting Solution. For details, see chapter "Reporting Solution tutorial" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". 13.1.7 Papyrus Analysis Toolkit l PUC (Papyrus Universe Compare) Settings: Hide Components The PUC (Papyrus Universe Compare) settings attribute Reduce frame hiding toolbars/splitter handle allows to hide up to 5 different components of the PUC user interface. For details, see section "PUC (Papyrus Universe Compare) Settings" of chapter "Papyrus Universe Compare classes and auxiliary classes" in "Analysis Toolkit Application Developer Guide (pandge)". l Papyrus Universe Compare: Additional Color for Triple Comparison The color code for three-way comparison with PUC has been extended by the additional color "blue". For details, see section "Color code for three-way comparison" in "Analysis Toolkit Application Developer Guide (pandge)". 13.1.8 Papyrus Client Canvas l Icons have been adapted to updated icons of Business Designer Due to the new design of Business Designer, variable icons now have the same design in both applications. For more details, see chapters "Insert variable" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)" and "Highlight variables" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Extended dialog for inserting expressions With the extended Define DOCDEF expression dialog you can now save the content of the DOCDEF command DFACODE in a variable. For more details, see chapter "Insert expression" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". getstartede V7.6 SP3 142/389 Appendix: main updates in V7.4 13.1.9 Papyrus Designer FixForm and Server FixForm l Papyrus Capture Designer FixForm: new color processors The following color-related processors are available in order to recognize colored regions on document pages. Normalization processors: - color depth/recognize and tag colors - color depth/select tagged color and the recognition processor Colors. For details, see "Normalization" in "Designer Capture Application Developer Guide (pcddge)", "Color depth / select tagged color" in "Designer Capture Application Developer Guide (pcddge)", and "Colors" in "Designer Capture Application Developer Guide (pcddge)". l FixForm normalization processors: new attribute color depth/color space conversion Normalization processor Color Depth/Color Space Conversion has been provided with new attribute "preserve lower color depth". If this attribute is set, if set, the color space will not be converted if the image has already a "lower" color space which results in a performance improvement. For details, see section "color depth / color space conversion" in "Designer Capture Application Developer Guide (pcddge)". l Papyrus Capture Server recognition engines n New "Tesseract4" recognition engine Tesseract4 is an open source recognition engine for printed characters under Apache 2.0 license which can be used as alternative to the OmniFont engines. As of version v7.4 Tesseract4 is available and installed by default with Capture applications. The product authorization for Tesseract4 is included into the Capture packages, thus no additional product authorization is required. The reco engine Tesseract4 is supported by the following Capture applications: u Papyrus Capture Designer/FixForm u Papyrus Capture Designer/FreeForm® u Papyrus Capture Server/FixForm u Papyrus Capture Server/FreeForm® u Papyrus Categorizer u Papyrus Scan Receiver For details, see chapter "Tesseract4" in "Designer Capture Application Developer Guide (pcddge)". n New default for full page recognition This new recognition processor combines the features of the engines "tesseract4" and "standard" and allows to extract samples that contain printed text as well as handwritten text. For details, see chapter "FullPageNew" in "Designer Capture Application Developer Guide (pcddge)". l FixForm designer option "Extract current page only" This new option allows to restrict the extraction in Papyrus Capture Designer/FixForm to the page currently selected in the image viewer. For details see, chapter "Menu "Options"" in "Designer Capture Application Developer Guide (pcddge)". l FixForm design: table definition A new chapter about creating a table definition with Payprus Capture Designer/FixForm has been provided. For details, see chapter "Table definition" in "Designer Capture Application Developer Guide (pcddge)". l FixForm design: multiple table definitions Now it is possible to define more than one table definition in a document class definition. For details, see section "Multiple table definitions in a document class" in "Designer Capture Application Developer Guide (pcddge)". getstartede V7.6 SP3 143/389 Appendix: main updates in V7.4 13.1.10 Papyrus Designer FreeForm and Server FreeForm l Recognition engine: Tesseract4 Tesseract4 is an open source recognition engine for printed characters under Apache 2.0 license. As of version v7.4 Tesseract4 is available and installed by default with Capture applications. The product authorization for Tesseract4 is included into the Capture packages, thus no additional product authorization is required. The reco engine Tesseract4 is supported by the following Capture applications: n Papyrus Capture Designer/FixForm n Papyrus Capture Designer/FreeForm® n Papyrus Capture Server/FixForm n Papyrus Capture Server/FreeForm® n Papyrus Categorizer n Papyrus Scan Receiver For details, see section "Tesseract4" in chapter "Text" in "Capture Designer FreeForm® Application Developer Guide (ffddge)". l Recognition engine: FullpageNew This new recognition processor combines the features of the engines tesseract4 and standard and allows to extract samples that contain printed text as well as handwritten text. For details, see section "FullpageNew" in chapter "Text" in "Capture Designer FreeForm® Application Developer Guide (ffddge)". 13.1.11 Papyrus Designer, Papyrus DocEXEC 13.1.11.1 Information relevant for DOCDEF developers l PQL set: variety of PQL set functions implemented A variety of functions was implemented that allow creation and manipulation of PQL sets locally in DocEXEC. Together with these functions a new variable type was introduced. The main use case for this type of functions is within Papyrus Business Correspondence Solution. Function FROMJSON imports a JSON file from file system or binary attribute and creates a PQLset variable containing the content. PQLSET creates an empty PQLset variable in DocEXEC. FIELDSOFEXP creates an array with the PQL set field names. TYPEOFEXP returns the type of a particular field in the PQL set. TOARRAY creates an array from a particular field's values. PQLSCRIPT locally executes a PQL script. Function MAXINDEX was enhanced to also operate on PQLset variable types. For more information, see chapter "PQL set functions" in "DocEXEC Reference Application Developer Guide (pdedge)". l Data encryption: Private key encryption supported in _ENCRYPT() function Function _ENCRYPT(), which can, for example, be used for encrypting data for DataMatrix barcode data encryption, was enhanced so that data can also be encrypted with the private key. Prior to this change _ENCRYP supported only public key encryption. For more information, see chapter "_ENCRYPT" in "DocEXEC Reference Application Developer Guide (pdedge)". CRC32 hash value creation from memory variable type by _CRC32() function Function _CRC32 creates an integer hash value from a memory type variable. The function's return value can, for example, be used for creating checksums for barcodes. For more in formation, see chapter "_CRC32" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 144/389 Appendix: main updates in V7.4 l Fonts: Fall back font definition for TrueType and CID OpenType fonts The Font definitions dialog now enables assigning particular fonts to a certain font group. By font groups it is possible to define fall back fonts which can be applied if particular characters are not printable in the selected font but in the fall back font. The shape of such fall back font characters might be slightly different, but the character itself can be displayed. A fall back font is in many cases considered the better solution as compared to general replacement characters like question marks or rectangles. Fall back fonts can only be defined for TrueType and CID OpenType fonts and if the font is rescalable. Font codepage must be Unicode, that is 1200 or 1201. In order to activate fall back font usage DocEXEC main profile parameter FONTFALLBACK="YES" has to be set. For more information on the definition of font groups, see chapter "Define fallback fonts" in "DocEXEC Reference Application Developer Guide (pdedge)". For more information on FONTFALLBACK DocEXEC main profile parameter, see chapter "DEFALLBACKFONT / FALLBACKFONT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". New functions for checking whether characters can be printed with certain font The functions ISPRINTABLE() and ISPRINTABLE2() help to check whether certain characters or symbols are available in and printable with a certain font. The difference is that ISPRINTABLE2() also considers characters and symbols in the fall back font. ISPRINTABLE() has been present since v6.20 but is documented for v7.4 for the first time. For more information, see ISPRINTABLE and "ISPRINTABLE2" in "DocEXEC Reference Application Developer Guide (pdedge)". l Entering text, expressions and images in TEXTPROMPT command: Add compression level and header information when pasting images in TEXTPROMPT Function MEM_ZIP was enhanced so that it allows now for compression level selection and header inclusion. MEM_UNZIP allows now for header recognition. For more in formation, see MEM_ZIP and "MEM_UNZIP" in "DocEXEC Reference Application Developer Guide (pdedge)". New TEXT/TEXTPROMPT command functions NATIVECODE and NATIVECTRLCODE for entering text w/o text controls NATIVECODE and NATIVECTRLCODE retrieve flat ASCII text from a variable into TEXT/TEXTPROMPT. NATIVECTRLCODE is able to interpret control characters such as CRLF, FF (form feed) and TAB, NATIVECODE does not. Together with DFACODE and HTMLCODE these functions are related to the 7.4 extension of Papyrus Client Canvas that enables users to enter DOCDEF expressions in text input fields. For more information, see chapter "TEXT command" in "DocEXEC Reference Application Developer Guide (pdedge)". Handling mode parameter for DFACODE and HTMLCODE TEXT/TEXTPROMPT command functions DFACODE and HTMLCODE have been enhanced by a handling mode parameter, which allows to switch display of a DOCDEF expression itself and the parsed text to which it resolves. This parameter is only important for application in Papyrus Client Canvas when DOCDEF expressions should be entered. This enhancement is related to the 7.4 extension of Papyrus Client Canvas that enables users to enter DOCDEF expressions in text input fields. Also the new TEXT/TEXTPROMPT functions NATIVECODE and NATIVECTRLCODE have this parameter. For more information, see chapter "TEXT command" in "DocEXEC Reference Application Developer Guide (pdedge)". l HTML output creation in TEXT/TEXTPROMPT command: support of HTLM4 and HTML5 Function _TEXT_START was enhanced by a parameter that allows to select the HTML version to be created: either HTML4 or HTML5. HTML4 is default. For more in formation, see chapter "_TEXT_START" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 145/389 Appendix: main updates in V7.4 l Signature fields in PDF: signature mandatory and signature text as tooltip The Sticker functionality for creating socalled empty signature fields in PDF was enhanced. The signature can now be defined as mandatory - the user must enter a signature, and the Sticker text will displayed as tooltip in PDF. For more information, see chapter "Create signature fields in PDF" in "DocEXEC Reference Application Developer Guide (pdedge)". l PDF417 barcode: MacroPDF417 barcodes support The new parameters File ID, File name, and Gap allow to generate MacroPDF417 barcodes for the encoding of large amounts of data into multiple PDF417 barcode units. For more information, see chapter "CREATEOBJECT PDF417(PDF417)" in "DocEXEC Reference Application Developer Guide (pdedge)". l Variable prompting in PDF: VARPROMPT command supports comb fields for PDF forms With the VARPROMPT command it is now possible to produce comb fields. Comb fields are PDF form fields displaying a grid and positioning digits centered. For more information, see chapter "VARPROMPT command" in "DocEXEC Reference Application Developer Guide (pdedge)". l DESCRIPTION command: support of variable output format definition and representational expressions By selecting for Type the option NUMPICTURE in the Description command it is possible to define an output format for a variable. By selecting for Type the option REPRESENT in the Description command it is possible to define a representational expression. Such a representational expression can combine arbitrary strings with variables, for example, '"ten times "!$ACTVAR*10!" is"'. These new features can be used in situations where not only a particular variable output format is required, but also access to a variable's value itself is needed, e.g. for evaluating conditions. The main use of these features is the Papyrus Business Correspondence Solution. For more information, see chapter "_DESCRIPTION command" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 146/389 Appendix: main updates in V7.4 13.1.11.2 Information relevant for administrators l Compatibility parameters: Line spacing: USEACTUALLINESPACE The object positioning behaviour for a special situation has been corrected. An Outline/Printline will not be positioned correctly in situations where automatic line spacing is defined within the Outline/Printline and prior to the Outline/Printline fixed line spacing is used. When a Linespace Auto command is set in an Outline/Printline but prior to the Outline/Printline fixed or default line spacing is used, the Outline/Printline will be positioned with an unjustified leading. Compatibility parameter USEACTUALLINESPACE=YES corrects this behaviour. The parameter is set to USEACTUALLINESPACE=NO by default, which means that the standard behavior that has been there ever since is continued. For more information, see chapter "DEUSEACTUALLINESPACE / USEACTUALLINESPACE" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Line breaking for Asian languages: NEWLINEBREAKING Some Asian languages (Japanese, Chinese, Korean...) contain many special characters which cannot be placed at the end of a broken line in case of a line break. Correction of earlier line break rules required the implementation of the NEWLINEBREAKING compatibility parameter. The parameter has been implemented with 7.1 SP7 but described with 7.4 for the first time. For more information, see chapter "DENEWLINEBREAKING / NEWLINEBREAKING" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Line space calculation for Asian languages: ONLYDBCSTEXTUSEDEFAULTSBCSFONT The line spacing calculation was improved in a special situation if a TEXT command contains both SBCS and DBCS fonts. The improvement required the implementation of the ONLYDBCSTEXTUSEDEFAULTSBCSFONT compatibility parameter. The parameter has been implemented with 7.1 SP7 but described with 7.4 for the first time. For more information, see chapter "DEONLYDBCSTEXTUSEDEFAULTSBCSFONT / ONLYDBCSTEXTUSEDEFAULTSBCSFONT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l Fallback font definition: FONTFALLBACK parameter In order to use the 7.4 font grouping feature, which enables the definition of fallback fonts, DocEXEC main profile parameter FONTFALLBACK="YES" has to be set. For more information, see chapter "DEFALLBACKFONT / FALLBACKFONT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)"see chapter "DEFALLBACKFONT / FALLBACKFONT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)"see chapter "DEFALLBACKFONT / FALLBACKFONT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 13.1.12 Papyrus FontConverter l New LOGPATH parameter: possibility for changing the log path The new LOGPATH parameter in the FCCV.prf profile can be used to change the log path. For details, see chapter "Installation of the standalone product" in "FontConverter Online Help (fc)". getstartede V7.6 SP3 147/389 Appendix: main updates in V7.4 13.1.13 Papyrus Objects (WebControl/WebRepository) 13.1.13.1 Papyrus Objects System Information relevant for administrators l Login settings: password hashing The section on user authentication now shows how to upgrade user password encryption from SHA1 to SHA512. For details, see "Selecting a password hashing algorithm in WebRepository and WebControl Installation and Administrator Guide (poinste)". Information relevant for developers l Tenant Collection: GetTenants() no longer returns $displayName Prior to v7.30 2018-10-22, the method TenantCollection::GetTenants() returned a PQL set containing the $logicalGUID and $displayName of found tenants. $displayName is no longer returned in that set because its computation incurs considerable overhead, while most callers of the method do not actually need it. ISIS Papyrus applications have already been updated with this change, but some custom implementations that call GetTenants() might need to be adapted. A custom PQL script using the $displayName returned by that method would instead have to call $reload to obtain that attribute. E.g.: ... @Tenants = fromMem(@TenantCollection.GetTenants().return1); @Tenants = @Tenants\$reload.$logicalGUID,$displayName; ... Modification date: v7.30 2018-10-22 l Dynamic icons: status bars & badges To modernize its desktop and business user interfaces, Papyrus Software is incorporating a new theme into its icons for Adapters, Tasks, Agents, Data, Tools, Materials, Queues and Folders. A new system of status bars and badges enables users to assess the current state of processing more quickly and accurately. Not all icons and screenshots have yet been upgraded. For details, see "Iconography" in "WebRepository Application Developer Guide (pwride)". 13.1.13.2 Papyrus Depot l Depot search workplace The following improvements were implemented. While the improved Save button behavior is automatically available to the business user (e.g. in the ADF workplace), the other two features have to be set up by the administrator/developer in the Depot search settings in the Settings Explorer. n Save button only available if changes were made The Depot Search UI allows to configure a lot a of parameters. Now the Save button is grayed out until changes were made. n Also search in attributes of child classes In the Depot search settings the attributes "Select search attributes", "Select return attributes", "Select return attributes" and "Select details attributes" have the new column Include Class Tree Attributes. By setting this value to true attributes of child classes are also selectable as search criteria. For more details, see chapter "Preconfigure attributes available for search, result views and export" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". n Customize result display with own components Via the Depot search settings it is possible to define a component to display the search result on the right hand side. In addition to the default view a user or class dependent component can be loaded. This allows for instances to display an ACM case within the Depot Search. For more details, see chapter "Customize display of search results - Component selector" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". getstartede V7.6 SP3 148/389 Appendix: main updates in V7.4 l Depot PQL cleanup: parameter "Flag condition" The new parameter "Flag condition" of the Depot PQL Cleanup allows to define an arbitrary condition as additional criterion for depot objects to be deleted. Additionally, the parameter "Use max. objects per run" allows to limit the number of deleted objects. For details, see section "Depot administration with depot stored procedures (depot PQL)" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Depot partition group wizard: define partition groups Depot creation wizard has been extended by additions forms for the detailed definition of partition groups. For details, see chapter "Depot partition group wizard" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Depot administration: depot check-in with specified role In some cases it may be advisable to restrict the ability to check-in data into a particular depot instance. The new concept of the "Depot service role" allows to connect the depot check-in with a particular role. For details, see chapter "Depot check-in with specified role" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". 13.1.13.3 Papyrus Adapters and Typemanagers l ActiveMQ Adapter - easier setup of failover configuration The definition of a failover is greatly eased and done partly automatic. For this purpose 3 new classes were introduced (Repository/ActiveMQ Additional Setup). For details see chapter "Failover configuration" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l New icons Papyrus Software started modernizing and applying a new concept to several icons. Adapters, Tasks, Agents, Data, Tools, Materials, Queues and Folders are benefiting. The system of status bars and badges allows to quickly recognize the current state of affairs. These improvements are not only visible in Papyrus Desktop but also in the business user interfaces. Not all icons and screenshots are updated yet. For details, see chapter "Iconography" in "WebRepository Application Developer Guide (pwride)". 13.1.13.4 Papyrus EYE Widgets l Image viewer widget: support of text extraction and paste In the image viewer widget it is now possible to activate the extract and paste feature. This feature enables the user to select a part of the image with the mouse and by this extract the contained text on the fly. The selected region can be dragged/dropped from the image viewer widget (displaying an image or a document like a PDF) either into a form field of the widget workplace itself or into any external text editor (email, Notepad, etc.). This feature is relevant for Papyrus Capture applications. In order to make use of this feature, the following product authorizations are needed: Papyrus Client - Capture product authorization Papyrus Server Capture product authorization (Papyrus FixForm and Papyrus FreeForm) For details, see chapter "Image viewer widget" in "EYE Widgets Developer Guide (popeyewdge)". l Display of the title of a component used as modal dialog So far the title of components was not displayed. For modal dialogs (component with attribute Type = 2: Modal Dialog) it makes sense to define a title, but then the title(s) of its widget(s) should be hidden (displayed as blue ribbon(s)). Therefore the option Has Frame of the related frames in the layout of the component have to be deactivated. For details, see chapter "Component widget" in "EYE Widgets Developer Guide (popeyewdge)" and chapter "Custom layout" in "EYE Widgets Developer Guide (popeyewdge)". getstartede V7.6 SP3 149/389 Appendix: main updates in V7.4 13.1.14 Papyrus Printer Driver l Possibility to install or remove the PrinterDriver via PowerShell commands It is now possible to install or remove the Printer Drivers file- and Objects-based easily via PowerShell command scripts delivered with the printer installation files. This new installation possibility was especially designed for users, who are not allowed to install or remove a printer via the Windows printer installation, e.g. due to organizational restrictions. For details, see chapter "Alternative second step: Automatic installation via PowerShell command scripts" in "PrinterDriver Administrator and User Guide (pdrauge)". l Two new output format options for OVL/PSEG images available: AS/400 and File transfer Overlay/page segment images can now be generated in the appropriate AFPDS format for further usage on AS/400 or host. For details, see chapter "Image mode details dialog" in "PrinterDriver Online Help (isisdrv.hlp )". 13.1.15 Papyrus Server 13.1.15.1 AFP to PDF l Font Substitution - additional option With the keyword CID2TTF it is possible to substitute an AFP CID keyed outline font with a TTF font. For more details and an example, see chapter "Font substitution tables - TTF" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Keep form names - new parameter In the context of PDF forms this parameter determines whether a text written into a text prompt is synchronized to all form fields using the same VARPROMPT name. For more details, see chapter "Keep form names (PdftKeepFormNames)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Reset button - new parameter A reset button allows to set all values of a PDF form to their default values. This parameter defines position, size and label of reset button(s). For more details, see chapter "Reset button (PdftResetRect)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". 13.2 Updates in V7.4 SP1 13.2.1 General changes l Tenant 'ISIS' changed to 'Papyrus' Papyrus solutions implement tenants in order to separate discrete departmental structures or customers, which require individual settings. ISIS Papyrus employs a tenant for running sample applications. This tenant used to be named 'ISIS' in Papyrus software versions prior to V7.4. With 7.4 the tenant's name changed to 'Papyrus'. With version 7.4 SP1 the name change is announced for the first time. The name change has only an impact on Papyrus sample applications. Customer applications should in any case always employ custom tenants and never use the 'Papyrus' (respectively 'ISIS') tenant. Customer-specific tenants ensure that customer applications are spared in the event of changes to the 'Papyrus' tenant. For more information about the tenant concept, see chapter "Papyrus application settings" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". getstartede V7.6 SP3 150/389 Appendix: main updates in V7.4 13.2.2 Papyrus Automated Document Factory Solution 13.2.2.1 Information relevant for administrators and developers l Automated Document Factory: auto delete functionality improved Previously auto delete was done by loading all tasks of one queue and then deleting each. The loading is now done in packages to prevent a potential memory overload. This problem occurred in conjunction with large JSON files. l Print and E-Delivery: bundling information set correctly Under certain conditions the status information of a bundle job was not updated. This has been fixed. l Bounce Solution: internal bounces now multi-tenant capable In case of an internal bounce the corresponding email task ends in error right away as the email is not sendable (e.g. due to an incorrect email address syntax). A bounce task has to be instantiated. To know where to find the corresponding queue for instantiation, the system now checks the tenant attribute of the input-/index-object and asks for settings. Thus it is possible to use different queues dependent on the tenant. Previously only domain-wide settings were usable. l Bounce Record Validation tool: time span customizable A bounce message has to be linked to a previously sent email and is usually received at a close interval to that email. Due to incorrect time zone difference depiction, situations can arise in which the bounce appears to have been received much later or apparently even "before" the actual message. With the new attributes Time span from and Time span to you can define an interval in hours in which the outgoing message must have been sent relative to the bounce. Previously, only outgoing messages sent 1 hour before or after receiving the bounce message were considered. For details, see chapter "Installation" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". 13.2.2.2 Information relevant for business users l Bounce Solution: robustness improvements - The state transition of a bounce (e.g moving it from "Unresolved" to "Out of Office") can no longer cause a locked form - The arrival of a new task at an inopportune moment can no longer cause an UI-glitch. - Refresh issues with displaying the original communication were solved. - Original communication being in another attribute no longer causes a portal error. - Under certain conditions a wrong date was extracted from a bounce. This has been fixed. - Bounce extraction tool can now handle longer subjects which are split across multiple lines. - Informational, warning and error messages have been improved. - Last result is always cleared from search form. 13.2.3 Papyrus Business Correspondence Solution 13.2.3.1 Information relevant for administrators and developers Improvements are provided with this service pack and affect the following use cases: getstartede V7.6 SP3 151/389 Appendix: main updates in V7.4 l Business Designer users: streamlined role structure and dedicated role available In alignment with the Papyrus Business Designer product introduced with Papyrus V7.4, a dedicated Business Designer Role was introduced and the role structure for users of Business Designer was streamlined in SP1. This allows to resolve issues that could happen with the usage of the Business Designer's product authorization, depending on the individual user's role assignment. It is mandatory to adapt the users of Business Designer by linking the Business Designer Role or by running the User Conversion Wizard. For more details, see chapter "Conversion of business users to have a Business Designer BC Role" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Composition of complex documents: content entered into the document did not appear in the generated document The creation of such complex documents may come along with increased communication between Papyrus DocEXEC and the Papyrus Objects kernel, which takes place by means of transactions. Papyrus DocEXEC could handle 32 open transactions, a count which was not enough for certain document applications. With this Service Pack the default is set to 128 open transactions that can be handled by Papyrus DocEXEC, which should prevent above described effects. To learn more about DocEXEC's transaction handling, see chapter "Transaction handling" in "DocEXEC - Access to WebRepository Developer Guide (pdeoadge)". 13.2.3.2 Information relevant for business users Improvements are provided with this service pack and affect the following use cases: l Generating AFP documents containing page segments and overlays: performance has been improved When loading AFP resources such as page segments and overlays from the Resource Collection, these resources which are kept in the cache, can easily be found in the cache and re-accessed from there, which was not always possible in the past. With this service pack, all reused AFP resources are retrieved from the cache, thus, performance is improved. l Complex documents with many open transactions: content entered in user input fields was not contained in document For complex documents with a high number of transactions, it could happen that content entered into the document in user input fields did not appear in the generated document. With this service pack, these documents will be generated correctly. l Paragraph surrounded by a frame: improved behavior in case of a page break inside the paragraph If a page break occurred in a paragraph surrounded by a frame, the frame sizes were calculated as without a page break and therefore not displayed correctly. Now this behavior is fixed and the frame around the paragraph is displayed correctly. l PNG and Alpha channel TIFF images: insertion into a text input field supported PNG images and TIFF images with Alpha channel can be inserted into text input fields by using the Insert image function. Without this service pack, they cannot be used. l Style connection key for text positioning elements If a style connection key is used, this service pack is mandatory because it contains improvements for connecting styles across a document. getstartede V7.6 SP3 152/389 Appendix: main updates in V7.4 n Positioning changes for a text positioning element with style connection key are applied Template administrators using a style connection key in a document template can define attributes (e.g. alignment, widow and orphan control, page breaks, etc.) for the first element with the style connection key. The following elements with the same style connection key take over the definitions. Without the service pack, any changes to the Alignment attribute and other attributes for a text positioning element with a style connection key are not applied. For more details, see chapter "Connecting numbering and styles across text positioning elements" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". n List elements can be moved to a lower level Template administrators using a style connection key to continue lists across a document template can move an element to a lower list level by inserting -1 into the Decrease sublevel by field. With -1, the style used in the text variant connected with the previous one is not removed and if it is a sublevel style, the paragraph numbering level goes one level down. Without the service pack, it is only possible to move a list to a higher level. For more details, see chapter "Connecting numbering and styles across text positioning elements" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". 13.2.4 Papyrus Business Document Capture Solution 13.2.4.1 Information relevant for administrators and developers l Capture Solution wizard/Add adapter to solution wizard: improvements and bugfixes n Improvements: The following changes have been applied to Capture Solution wizard and/or "Add adapter to solution" wizard: u Help texts of the wizards have been improved. u Property "Edit type" of depot selection parameter attributes changed from "EditComboBox" to "Combobox". u Import buffer queues and relocate queues of instantiated adapters are referenced into queue control folder. n Target node of relocate tool incorrect If only one adapter was instantiated and this adapter had a relocate queue within its child queue tree, then the target node of the relocate tool was set incorrectly. This has been fixed in version v7.4 SP1. n Queue of adapter "Import manifest (File)" not correctly linked When adapter "Import manifest (File)" was instantiated, then its queue "Import buffer (File)" was linked to Task factory queue instead to "Buffer manifest" queue. This has been fixed in version v7.4 SP1. n DocState "SCN" missing in process mapping table DocState "SCN" was missing in the table of attribute "Process mapping" of Capture (BDC) general settings in the code for the automatic generation of the Capture settings of Capture Solution wizard. This might have caused issues, if, for instance, the document class was changed for a document in DocState 'SCN' and a DocState to be displayed in document depot search of "Capture administration workplace" requires a process mapping entry. This has been fixed in version v7.4 SP1. l Papyrus Capture Server/FreeForm : Server fails after Windows update installation Papyrus Capture Server/FreeForm and Document fails to extract documents after installation installation of certain updates on certain Windows versions. For details how to fix this issue, see chapter "Papyrus Capture Server/FreeForm® fails after Windows update installation" in "Capture Designer FreeForm® Application Developer Guide (ffddge)". getstartede V7.6 SP3 153/389 Appendix: main updates in V7.4 l Papyrus Capture Server/FreeForm: Designer start fails after Windows update installation Papyrus Capture Designer/FreeForm and Document structure designer cannot be started after installation of certain updates on certain Windows versions. For details how to fix this issue, see chapter "Papyrus Capture designer start fails after Windows update installation" in "Capture Designer FreeForm® Application Developer Guide (ffddge)". l Scan receiver: after activation of scan profile new classes ignored When the scan profile was activated (restored or deleted), then new classes for schema definition and extraction definition (CapScanReceiverExtractionDefinition and CapDocumentSchemaDefinition) were ignored and stayed in deployment state "Development". This has been fixed in version v7.4 SP1. l POP3 adapter: memory leak A memory leak in POP3 adapter was detected and closed. This issue occurred only, if attribute "Leave messages on server" (LEAVEONSERVER) of POP3 mailbox of the POP3 receiver was activated. This has been fixed in version v7.4 SP1. l Export to TIFF/Export to PDF: various bugfixes n Export to TIFF/ PDF: ASCII files not correctly exported When larger ASCII files (5 pages or more) were exported with the feature "Export to TIFF" or "Export to PDF", then the resulting PDF and TIFF files were not accurately generated. The first pages were in order but then a page was repeated and the expected content missing. This has been fixed in version v7.4 SP1. n Export to TIFF/PDF: different layout for multi-page ASCII file exported as TIFF and PDF When an ASCII file is exported with the feature "Export to TIFF" and "Export to PDF", then the exported TIFF and PDF files had not the same layout, the PDF file had a larger line spacing in comparison to the same TIFF file. This has been fixed in version v7.4 SP1. n Export to TIFF: control character This has been fixed in version v7.4 SP1. n Export to TIFF: SaveToTiff fails to work for batch documents with user-defined PQL Method SaveToTiff() of class Capture document failed to work correctly for batch documents, if called by a custom PQL without complete parameter list. Calls in the Capture user interfaces were not affected. This has been fixed in version v7.4 SP1. For details, see chapter "Export TIFF to file system (SaveToTiff)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Papyrus Capture Designer: FixForm Designer start fails after installation of Windows update Papyrus Capture Designer/FixForm and Document structure designer cannot be started after installation of certain updates on certain Windows versions. For details how to fix this issue, see chapter "Papyrus Capture designer start fails after Windows update installation" in "Capture Designer FreeForm® Application Developer Guide (ffddge)". l Papyrus Capture Designer/Server: PQL to retrieve remaining Omnifont license volume A new PQL script allows to quickly display the remaining volume of an Omnifont license on Papyrus Desktop. For details, see chapter "PQL script to retrieve the remaining volume of an Omnifont license" in "Capture Designer FreeForm® Application Developer Guide (ffddge)". getstartede V7.6 SP3 154/389 Appendix: main updates in V7.4 l FixForm table definition: not all column results returned if there were disabled columns If an extraction definition contained a table definition and one or more columns had been disabled, then the extraction result did not return the values of all enabled columns. After fixing this issue the values of all enabled columns are returned. 13.2.4.2 Information relevant for business users Information relevant for Papyrus Client Capture users l Capture administration workplace: button "Cancel" of attribute editor has to be clicked twice In some cases the button "Cancel" of the attribute editor of Capture cockpit view of Capture administration workplace had to be clicked twice in order to take effect. This issue has been solved in version v7.4 SP1. l Completion view: "Paste into field" causes execution error The feature "Paste into field" causes execution error when the value was pasted from internal table into data entry field, if the source and target document had been the same. This issue has been solved in version v7.4 SP1. l Papyrus Client Capture: export as PDF to file system (SaveToPdf) - default output page size changed The page size of the PDF output of the method SaveToPdf() of the class Capture document (CapDocument) used for export of documents to file system as PDF in Document depot view of "Capture administration workplace" partiallly depends on the page size of the input format. For file types with an explicit page size such as image file types (TIFF, PNG, etc.) SaveToPdf keeps the size of the input file. For file types with no page size such as HTML, TXT, CSV SaveToPdf generates A4 portrait pages. This means that the default output has changed because until now the default output of SaveToPdf was generally A4 portrait. Information relevant for Papyrus Scan users l Papyrus Scan: split not possible in particular situation If two or more pages had been moved from another document, it was not possible to split these pages without changing the page selection between move and split (not split button available). This issue has been solved in version v7.4 SP1. l Papyrus Scan: button "Split" displayed if document and page are selected If a document had been selected in "Scanned item" view or "Search" view of "Scan" and then another page was added to the selection with [CTRL] key, then the button "Split" was displayed on the toolbar of the respective view. If button "Split" was clicked in this situation, then an error was raised.This issue has been solved in version v7.4 SP1. l Papyrus Scan: export as PDF to file system (SaveToPdf) - default output page size changed The page size of the PDF output of the method SaveToPdf() of the class Capture document (CapDocument) used for export of documents to file system as PDF used in the thumbnails viewers of "Scan" view partiallly depends on the page size of the input format. For file types with an explicit page size such as image file types (TIFF, PNG, etc.) SaveToPdf keeps the size of the input file. For file types with no page size such as HTML, TXT, CSV SaveToPdf generates A4 portrait pages. This means that the default output has changed because until now the default output of SaveToPdf was generally A4 portrait. getstartede V7.6 SP3 155/389 Appendix: main updates in V7.4 13.2.5 Papyrus Mobile Solution 13.2.5.1 Information relevant for administrators l New Settings "Mobile ACM Dashboard Settings" for ACM Mobile Applications The new "Mobile ACM Dashboard Settings" is introduced for ACM Mobile Applications. In this Settings, the Application Id of the dashboard applications and the ACM Application Libraries that should be displayed in the corresponding dashboard applications are provided in a table format. For details, see "Filter ACM application libraries" in "Mobile Application Administrator Guide (pomaage)" 13.2.6 Papyrus Client Document Creation (Canvas) Improvements are provided with this service pack and affect the following use cases: l Generating AFP documents containing page segments and overlays: performance has been improved (only relevant for Papyrus Client Canvas in a Business Correspondence Solution) When loading AFP resources such as page segments and overlays from the Resource Collection in a Papyrus Objects environment, these resources which are kept in the cache, can easily be found in the cache and re-accessed from there, which was not always possible in the past. With this service pack, all reused AFP resources are retrieved from the cache, thus, performance is improved. l PNG and Alpha channel TIFF images: insertion into a text input field supported PNG images and TIFF images with Alpha channel can be inserted into text input fields by using the Insert image function. Without this service pack, they cannot be used. l Complex documents with many open transactions: content entered in user input fields was not contained in document (only relevant for Papyrus Client Canvas in a Business Correspondence Solution) For complex documents with a high number of transactions, it could happen that content entered into the document in user input fields did not appear in the generated document. With this service pack, these documents will be generated correctly. l Paragraph surrounded by a frame: improved behavior in case of a page break inside the paragraph If a page break occurred in a paragraph surrounded by a frame, the frame sizes were calculated as without a page break and therefore not displayed correctly. Now this behavior is fixed and the frame around the paragraph is displayed correctly. getstartede V7.6 SP3 156/389 Appendix: main updates in V7.4 13.2.7 Papyrus Designer, Papyrus DocEXEC 13.2.7.1 Information relevant for administrators l Page break handling: Compatibility parameter PARAGRAPHSPACEBEFOREBREAK changes TEXT/TEXTPROMPT subfunction PARAGRAPHSPACEBEFORE() reaction In versions up to V7.4, PARAGRAPHSPACEBEFORE(<>) always added the defined paragraph right after a page break. This paragraph space would not be deleted. This resulted in an incorrect placement, as the actual text started only after this paragraph space on the new page. This reaction has changed with V7.4 SP1, but it has to be activated with DocEXEC main profile parameter PARAGRAPHSPACEBEFOREBREAK=YES. By default the parameter is set PARAGRAPHSPACEBEFOREBREAK=NO, which means that the paragraph space at the beginning will not be deleted, in order to stay backwards compatible. With this service pack the parameter is available for the first time. For more information, see chapter "DEPARAGRAPHSPACEBEFOREBREAK / PARAGRAPHSPACEBEFOREBREAK" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". To learn more about TEXT/TEXTPROMPT subfunction PARAGRAPHSPACEBEFORE , see chapter "PARAGRAPHSPACEBEFORE" in "DocEXEC Reference Application Developer Guide (pdedge)". 13.2.7.2 Information relevant for DOCDEF developers l PNG and Alpha channel TIFF images: can be inserted by TEXT command's IMAGE subcommand PNG images and TIFF images with Alpha channel can be inserted into a TEXT/TEXTPROMPT command using the IMAGE subcommand. Without the service pack, these image formats cannot be inserted. For more information about IMAGE subcommand, see chapter "IMAGE" in "DocEXEC Reference Application Developer Guide (pdedge)". l Text paragraph surrounded by a frame: improved behavior in case of a page break inside the paragraph TEXT/TEXTPROMPT commands allow to define frames around paragraphs by subcommand _FRAME. If a page break occurred in a paragraph surrounded by a frame, the frame sizes were calculated as without a page break and therefore not displayed correctly. This service pack fixes this behavior, and the frame around the paragraph is displayed correctly. For more information about _FRAME subcommand, see chapter "_FRAME" in "DocEXEC Reference Application Developer Guide (pdedge)". l Papyrus Designer GUI: incorrect drawing of GUI when moving toolbars The display of the Papyrus Designer GUI had some shortcomings like frame line duplication when toolbars were moved. These effects could be observed especially on Windows 10. This service pack fixes these effects.' l EXTRACTALL() function: no change of internal attribute status anymore when function is called If a Papyrus Objects attribute was extracted by EXTRACTALL(), the attribute's internal status was changed to 'non existing'. As a consequence, subsequent attribute checks with EXIST() returned wrong values ('0' meaning non-existent) for such attributes. EXTRACTALL() was fixed so that it does not change attribute states anymore. For more information on EXTRACTALL(), see chapter "EXTRACTALL" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 157/389 Appendix: main updates in V7.4 l Generating AFP documents containing page segments and overlays: performance improvement When a document application is loading AFP resources such as page segments and overlays from the Resource Collection by means of GETRESOURCES command, they are kept in the local DocEXEC cache, so that re-accessing them is more efficient. In certain situations identification of such resources in the local resource cache was hampered. This lead to performance decrease, because resources were loaded again and not used from the cache. This service pack optimizes resource identification and, thus, improves performance. To learn more about the GETRESOURCES command, see chapter "GETRESOURCES" in "DocEXEC - Access to WebRepository Developer Guide (pdeoadge)". l Composition of complex documents: content entered into the document did not appear in the generated document For complex documents built with Papyrus Business Correspondence Solution, it could happen that content entered into the document did not appear in the created document. The creation of such complex documents may come along with increased communication between Papyrus DocEXEC and the Papyrus Objects kernel, which takes place by means of transactions. Papyrus DocEXEC could handle 32 open transactions, a count which was not enough for certain document applications. With this Service Pack the default is set to 128 open transactions that can be handled by Papyrus DocEXEC, which should prevent above described effects. To learn more about DocEXEC's transaction handling, see chapter "Transaction handling" in "DocEXEC - Access to WebRepository Developer Guide (pdeoadge)". 13.2.8 Papyrus FontConverter l Changed codepage files to reflect the new Japanese Reiwa era On May 1, 2019, a new Japanese emperor was elected, leading to a new time counting in Japan. The name and character of this new era is Reiwa and was defined by the Unicode consortium at code point 0x32FF. To use this character also in the Japanese codepages 1390/1399, modified codepage files were created for the Papyrus DVD and Papyrus FontConverter was adapted to create fonts with this character. 13.2.9 Papyrus Objects (WebControl/WebRepository) 13.2.9.1 Papyrus Objects system l Agents: delay to avoid multiple execution of stateless tool/material methods Any class defining a tool or material method should additionally define a state machine that prevents agents from executing that method multiple times in rapid succession. When classes are not designed in accordance with that principle, a potential has remained for their methods to be repeatedly executed when called automatically. Now, however, if an object lacks a state machine, an agent will no longer execute any of that object's tool/material methods more than once within any 5-second interval. This precaution might slow down some existing setups; for more details, see "State machine" in "WebRepository Application Developer Guide (pwride)". Though it defines no state machine, the Session class does define ConnectToDesktop() as a tool method. Thus, the automatic connection of a user's active session to Papyrus Desktop can likewise trigger this 5-second delay. For more details, see "ConnectToDesktop()" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". This change in Agent behavior was introduced in v7.1 SP 9 and is being announced for the first time in v7.4 SP 1. getstartede V7.6 SP3 158/389 Appendix: main updates in V7.4 l Method TransferAddFrameworkSettings adds all nodes of the framework children The method TransferAddFrameworkSettings (called when dragging a framework onto a transfer, selecting Add to export (including children) the framework ... on ...) now adds all nodes of the framework children. This ensures that the framework export also works correctly in other domains without the need to adapt framework attribute Include objects on nodes (IncludeNodes). In domains other than the one where the framework originates, it is usually the case that the nodes are different, thus framework attribute Include objects on nodes (IncludeNodes) had to be adapted. Be aware, that references from all other nodes are now ignored, if the framework contains objects from nodes other than the Domain Controller. Only references from nodes of the objects of the framework and from the node of the framework instance itself are recorded and those defined in the framework attribute Include objects on nodes (IncludeNodes). For details, see chapter "Add objects to framework" in "WebRepository Application Developer Guide (pwride)". l PCSLog: Selected messages forwarded to operating system Fatal errors occurring on any Papyrus node are now routinely forwarded to and logged by its operating system. By setting two PCS variables on a particular node, you can additionally notify its OS whenever specific non-fatal message events occur there. For details, see "Information relevant for administrators". 13.2.9.2 Papyrus Query Language (PQL) l Agents delay automatic connection to desktop The Agent class implementation has been changed in a way that might prevent the timely automatic execution of desktop view methods. That would occur only if an Agent's first attempt to connect via Session::ConnectToDesktop() failed, or if the initial connection were prematurely disconnected. Desktop methods triggered manually through the user interface are not affected by this behavior. Before the change, automatic connections were reattempted with no limit on the number of retries. However, to prevent agents from executing tool/material methods multiple times in rapid succession, the Agent class was modified so that it will no longer execute any such methods more than once within any 5-second interval. Because ConnectToDesktop() is a tool method of Session, it is now subject to 5-second delays in the event of connection difficulties. For details, see chapter "ConnectToDesktop()" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". For details on the operation of state machines, see "State machine" in "WebRepository Application Developer Guide (pwride)". This change in Agent behavior was introduced in v7.1 SP 9 and is being announced for the first time in v7.4 SP 1. l pqlweb: HTTP request timeout Some HTTP request and reply functions cannot execute until a reply has been received from the HTTP server. The timeout for receiving that reply was previously hardcoded to 1 hour, potentially preventing the timely shutdown of nodes with pending requests. Now, however, pqlweb allows applications to specify a shorter timeout period. Furthermore, different timeouts can be individually specified in each call to a waiting function. For more details, see "HTTP request timeout" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l New function: $isAccessibleExtended() This function indicates whether or not the current user can read the specified object, and shows what errors would result if an actual read were attempted. The latter information is supplied only by this function, and not by $isAccessible() or $isAccessibleForRole(). For more details, see "$isAccessibleExtended()" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". getstartede V7.6 SP3 159/389 Appendix: main updates in V7.4 13.2.9.3 Papyrus Depot l Depot data key definition: different separators between fields Now it is also possible to define different separator characters between the fields of the field list of a depot key definition. In this case, the initial separator contains the empty string. For details, see chapter "Define depot data key string for multiple-value index" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Depot data key definition: attribute "Auto index handling" If the template of a depot data class contains settings for attribute "Auto index handling" of the depot data key definition and the depot instance (button "Administration") contains different settings for this attribute, then the settings of the template overrule the settings of the depot. This is nothing new. However, to avoid conflicts in the future from this version on attribute Auto index handling will be set invisible on the template, even if attribute "Show Depot data features" is activated. For details about depot key definition with depot administration, see chapter "Define depot data key string for multiple-value index" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Depot search workplace: robustness improvements - Switching from simple to advanced search and vice versa resulted in an incorrect first search result. This has been fixed. - Availability issues of 'Save' and 'Cancel' button in the settings dialog have been fixed. 13.2.9.4 Papyrus Adapters and Typemanagers l ISDN Fax receiver/sender: modifications of messages The messages output by ISDN Fax receiver/sender have been updated and complemented: n Status codes (Adapter FXI messages) The status codes written into attribute "Final status" of the ISDN Fax material have been partially modified. For details, see section "Additional Papyrus Adapter FXI messages" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". n PCS messages A number of new messages has been added to the PCS messages logged by ISDN Fax receiver/sender. For details, see section "Job log activation instructions" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". n New attributes for ISDN Fax receiver Class ISDN Fax Receiver has been provided with the following new attributes: u Image compression u Attempted calls handling u Max bit rate u Initial data mode timeout u Data mode timeout u Physical link connection timeout u Network control timeout u Call instantiation mode u Suppress ECM For details, see section "Components of sample set-up "ISDN - send Fax sample"" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". getstartede V7.6 SP3 160/389 Appendix: main updates in V7.4 13.2.10 Papyrus Postprocessing/Printpool 13.2.10.1 Papyrus Tuner l Inline object container manipulation: new parameter AFPDS which were generated by non-Papyrus products can contain "inline" object containers. Not all printers and viewers support inline object containers. This parameter converts inline object containers into regular object container resources, which are supported by Papyrus products. For details, see chapter "Inline object container manipulation (TUNObjectContainerInline)" in "Papyrus Tuner Reference Guide (ptunrge)". l Invoked object container manipulation: new parameter Not all printers support object containers, specifically when carrying Adobe PDF files. This parameter converts object containers to RGB page segments. This image type is supported by all IPDS printers. For details, see chapter "Invoked object container manipulation (TUNObjectContainerInvoked)" in "Papyrus Tuner Reference Guide (ptunrge)". 13.2.11 Papyrus Server 13.2.11.1 AFP to PDF l PDF forms: additional button configuration option In a PDF form a submit (to send the form) and a reset button (to set the fields to their default values) can be used. In addition to text, size and position of the button it is now also possible to define the font size. For details, see chapter "Submit button (PdftSubmitRect)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)" and "Reset button (PdftResetRect)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". 13.2.11.2 PJL l PJLTryOnOpenError: new parameter Under certain conditions it took the PJL tool longer to go to error than the period specified in the timeout parameter. With the help of PJLTryOnOpenError the maximum number of attempts on an open connection failure can be defined. This leads to a faster reaction if a printer address is (temporarily) not available. Thus shortening the period the tool/queue is blocked. For details, see chapter "PjlTryOnOpenError" in "Papyrus Server - PJL Reference Guide (psepjlrge)". 13.2.11.3 IPDS l AFPs with medium maps and page offset The offset defined in the medium map was not propagated to the IPDS command 'logical page position'. Thus the page was always positioned at (0;0). This has been fixed. l Tx socket buffer size: new parameter This parameter allows to limit the maximum amount of bytes transmitted in a single send() operation, therefore avoiding transmission bottlenecks. For details, see chapter "Tx socket buffer size (IPDSTxSocBufferSize)" in "Papyrus Server - IPDS Reference Guide (pseipdsrge)". 13.2.12 OverView Font Editor l Updated shortcut for menu item Font | Close: [Ctrl]+[C] The shortcut for the menu item Font | Close was updated. To close an open font, press [Ctrl]+[C]. getstartede V7.6 SP3 161/389 Appendix: main updates in V7.4 13.3 Updates in V7.4 SP2 13.3.1 Papyrus Adaptive Case Management Solution 13.3.1.1 Information relevant for business users l Papyrus EYE Widgets improved If Papyrus EYE Widgets user interface is used, this Service Pack is recommended because it contains improvements preventing an error message at the start of the user interface. getstartede V7.6 SP3 162/389 Appendix: main updates in V7.3 14 Appendix: main updates in V7.3 If you upgrade from an earlier version to the newest version, use the appendix to see a history of all changes that have accumulated. Note that the cross-references in the appendix refer to chapters in documents of the same version. This means that some of the History of Changes entries in the appendix may include cross-references to chapters that do not exist anymore in the newest version of the document or whose information was updated in the meantime. If you are in such a case interested in the details you will need to access the documents of exactly that version. 14.1 Main updates in V7.3 14.1.1 General changes This delivery includes Papyrus products in release level V7.3. 14.1.2 ISIS Papyrus Product Authorization Service (IPAS) l F-Security products preventing proper authorization of Papyrus products Due to a known bug of F-Secure products, authorization requests from Papyrus products to the IPAS may not be answered. This bug affects Papyrus products and IPAS prior to V7.3. With V7.3 a workaround was implemented so that F-Security products do not react on the information exchange of Papyrus products and IPAS anymore. In general it must be said that Network security control products can cause conflicts with IP and HTTP communication between Papyrus processes. Therefore it is recommended that these products are disabled. 14.1.3 Papyrus Adaptive Case Management Solution 14.1.4 Papyrus Automated Document Factory Solution 14.1.4.1 Information relevant for administrators and developers l New CallPrintAndEdelivery method This method on the ADF data-interface (DiAdf) offers another way to control Print and E-Delivery externally. Unlike all other PED methods it accepts an entire array of index objects. It can be used for instance to perform tests without changing or or activating the test mode and is very useful in the context of campaigns. For details, see chapter "CallPrintAndEdelivery" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". getstartede V7.6 SP3 163/389 Appendix: main updates in V7.3 l Bounce Solution Imagine you are doing a marketing campaign. Probably a few (email) addresses in your database are no longer valid or temporarily do not accept new mails, because the mailbox is full or the other company's mail-server is not reachable etc. The corresponding error messages, usually in the form of a mail from another mail-server, are called bounces. When physical letters are involved the term paper return is used. These error messages should not only be analyzed and acted upon to increase the number of people reached with the current campaign but also to improve the quality of your database. Updating your database benefits future campaigns and upholds the reputation of your mail-server. If too many messages cannot be delivered, the chances that emails sent from you get marked as spam, increase. In case of paper returns future sending costs will be reduced. The Bounce Solution greatly eases that process by providing a new dedicated EyeWidgets workplace and special classes and methods which are customizable and extendable. The Bounce Solution builds on an existing Print and E-Delivery environment and can be extended with the upcoming Campaign Solution. For details, see chapter "Bounce Solution" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Display PED information in Depot Search If activated in the Depot search settings in the Settings Explorer the data of the PED information object will be displayed in result details tab of the depot search. For details, see chapter "Depot search" in "". 14.1.5 Papyrus Business Capture Solution 14.1.5.1 Information relevant for administrators and developers l Inheritance of Elements in Derived Document Classes As of version v7.3 there is no longer automatic inheritance of elements defined in parent classes to derived classes. Now, elements to be inherited in a derived class from a parent class have to be explicitly defined. For details, see chapter Inheritance of elements in child document classes in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l Deactivating a Capture Document Definition Now the Capture administrator can deactivate a document type definition in Document Definition of a Capture Solution, if it is no longer used. For details, see chapter "Deactivating a Capture document definition" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l CSV Format Supported Now Capture products and the feature Export to file system as PDF/Export to file system as TIF also support CSV files. For details, see chapters "Supported document formats" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)" and "Export documents" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Capture Solution Wizard The new Capture Solution wizard allows the Capture administrator to instantiate a Capture Solution template by just filling attributes of a wizard - all the rest (instantiation of all components on their respective nodes, referencing into the Solution, Capture Solution settings, etc.) is done automatically. No more tedious deleting and referencing of components required. For details, see chapter "Setup a Capture Solution with the Capture solution creation wizard" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". getstartede V7.6 SP3 164/389 Appendix: main updates in V7.3 l Capture Depot Instantiator As of this version the Depot folder (Distributed depot folder) of Capture Solution templates does no longer contain Depot templates. Instead, Depot-related Solution folder contain templates of Depot instantiators for Capture basedata depot and Capture document depot. When a Capture Solution template is instantiated, then the Depot instantiators trigger the instantiation of the Depot defined on the Depot instantiators. For details, see chapter "Depot instantiators for Capture depots" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". 14.1.5.2 Information relevant for business users Information relevant for Papyrus Client Capture Users l Additional Supported Data Types: CSV, MS Office with Macro Now, additionally the data types CSV and MS Office file types with macro (DOCM, PPTM, XLSM) are supported. l Data Entry via Drag and Drop in Completion View from External Applications Now, character strings can be entered into the data entry field of Completion view via drag and drop from external applications (e.g. Notepad). For details, see section "Data Entry from External Applications via Drag and Drop" and chapter "Data entry from external applications via drag and drop" in "Papyrus Client - Capture User Guide (popcfuge)". l Page Display of Multi-Page Documents in Thumbnails Viewer: "Thumbnails Wrap Enabled" Now it is possible to display the pages of multi-page documents in the thumbnails viewer of "Document workplace" and the thumbnails viewer of "Document depot" view of "Capture administration workplace" also in "wrap mode". For details see section "Page Display for Multi-Page Documents in Thumbnails Viewer" in chapter "Page display for multi-page documents in thumbnails viewer" in "Papyrus Client - Capture User Guide (popcfuge)". l DocState Filter for Feature "Enable data drag and drop from Windows Explorer" Now the additional settings attribute Allowed document states enables to filter the possible targets of this feature with respect to its document state. For details, see attribute Allowed document states in "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Disable Confirmation for "Split" and "Duplicate" Now it is possible to skip the confirmation dialog for the features Split and Duplicate in Document Workplace. For details, see attribute Document workplace dialog configuration in "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Settings Attribute "Direct Classification" Renamed "Classification/Validation Guidance" The settings attribute Direct Classification has been renamed Classification/Validation Guidance and provided with an additional option. For details, see attribute Classification/Validation Guidance in "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Completion View Event Fields Now it is possible to associate different events with fields of Completion view. For details, see attribute Completion View Event Fields in "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". getstartede V7.6 SP3 165/389 Appendix: main updates in V7.3 l Rotate some or all Pages of a Document in one go (Document Workplace) Now the menu entry Document | Rotate selected items of "Document workplace" view allows to rotate selected pages or all pages of a document in one go. For details, see section "Menu "Document"" in "Papyrus Client - Capture User Guide (popcfuge)". l Rotate all Pages of a Document in one go (Completion View) Now the menu entry Document | Rotate all pages of "Completion" view allows to rotate all pages of a document in one go. For details, see section "Menu "Document"" in "Papyrus Client - Capture User Guide (popcfuge)". Information relevant for Papyrus Scan Users l More Supported File Types for File Scan The feature "file scan" now additionally supports the file type CSV and the office file types DOC, DOCX, ODT, PPT, PPTX, ODP, XLS, XLSX, ODS. For details, see chapter "Tab "Standard" of the dialog "Profile settings"" in "Capture Scan Administrator and User Guide (poscanauge)". l Page Display of Multi-Page Documents in Thumbnails Viewer Now it is possible to display the pages of multi-page documents in the thumbnails viewer of "Scan" view also in "wrap mode". For details see section "Anzeige der Seiten mehrseitiger Dokumente in der Miniaturansicht" in "Capture Scan Administrator and User Guide (poscanauge)". l Disable Confirmation for "Split" Now it is possible to skip the confirmation dialog for the method Split of the thumbnails viewers of "Scan" view (tab "Scanned items" and tab "Search") For details, see attribute Scan view dialogues configuration in "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Auto-Shutdown Scan Receiver New settings attribute Auto-shutdown scan receiver allows automatic shutdown of scan receiver, if user logs out or shuts Papyrus Eye Widgets Desktop. For details, see attribute Auto-shutdown scan receiver in "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". 14.1.6 Papyrus Business Correspondence Solution 14.1.6.1 Information relevant for Administrators and Developers l Disabling of obsolete building blocks possible on a scheduled date Template administrators can now also select a future date for disabling a building block. Configuration requires a Scheduler, disabling settings and allowing disabling for users. For more details, see chapter "Configure disabling of obsolete building blocks" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l NL configuration to disable the "guessing" of user input when variables are not matching the value type In the construction of Natural Language Rules (NLR), automatic logic attempts to resolve any typos or mistakes that have been created by the template administrator. For more details, see chapter "Configure automatic guessing logic of NLR" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 166/389 Appendix: main updates in V7.3 l Suspending a Change Management Release A release can be suspended and this entails manual intervention to perform further clean up operations. For more details, see chapter "Correcting bugs in a production environment" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Resource handling controlled by 'CF scopeconfiguration' settings (Application Output Format) Set of attributes that can be configured without having to change DFA code. For more details, see chapter "Configure control values for compressed AFP generation" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Move a variable to another variable group We can move a variable that has no previous versions to another variables group. For more details, see chapter "Move a variable to another variable group" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Determine when a document is generated by the supervisor and clerk Generation can be performed on Done and Approve operations by the business user. For more details, see chapter "Configure Clerk and Supervisor to generate AFP output" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l ASSIGN building block with recalculated index ASSIGN building block can be used with an index. Index can be recalculated before it it is used again by setting the Recalculate index check box. For more details, see chapter "Collating information for summary data output using assign index" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Additional execution points (100, 1000, 4000, 4005, 4010, 4015) Execution points allow the system user to place additional functionality into the DFA code allowing a business to execute his own custom code. For more details, see chapter "Develop Execution Points to extend document templates in the Correspondence Framework" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Clerk: Use document lock in 'CF Scope Document Creation' settings Use document lock check box in 'CF Scope Document Creation' settings. Default behavior (unset/false) is like before, every clerk could click Done on other clerk's documents. When the setting is set, the user does not get the Done button, if the document is currently edited by another user. For more details, see chapter "Lock document in use by another business user" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Manage both private and group development projects Switching between default projects in private and group development projects should be avoided once the setup is already in use. For more details, see chapter "Business users working with Private and Group Development Projects" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Business Correspondence Solution checklist Checklist contains the key elements that can be used in gathering statistical information on the operational performance of a Business Correspondence Solution. For more details, see chapter "Appendix A: correspondence framework checklist" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)" and "Performance and tuning of Papyrus Business Correspondence Solution" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Separation of wizards and release cases per tenant Document wizards and ACM release cases can be separated by tenant. For more details, see chapter "Create Tenant separation for document wizards and release cases" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 167/389 Appendix: main updates in V7.3 l Style definition for mapping between COR style and HTML style We can create a mapping to make a correspondence style available in HTML, which could be made available for single source document (SSD) For more details, see chapter "Create a settings style to map correspondence to HTML" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". 14.1.6.2 Information relevant for Business Users l New release template for immediate development change management available Release managers have an additional release template available for creating a release: Release (Immediate Development). This one-stage change management process contains only one development stage and no test stage. For more details, see chapter "Immediate development change management process" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Simulation of documents and building blocks extended with additional functionality Document simulation for business users has been enhanced with additional features such as layout simulation and improved usability. For more details, see chapter "Simulating documents and building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l New attribute "Recalculate subtotal" for "Table" design building block available Template administrators working with tables built with the Table design building block can select the Recalculate subtotal check box in order to recalculate the subtotal for the table in a document or in a group, if the Subtotal variable attribute and not the Assign building block is used for the calculation. For more details, see chapter "Recalculate subtotal of table used in a document or group" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l For list boxes in wizard, the number of items to select can be defined Template administrators working with list boxes in wizard forms can now define how many items can be selected. For more details, see chapter "Define number of selectable listbox options" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Releases can be grouped into release packages with a common activation date In order to activate several releases at the same time, release managers can create release packages and add releases to them. For a release package, an activation date can be defined, which is valid for all releases added to the release package. This way dependencies are automatically resolved during activation. For more details, see chapter "Working with a release package" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Search for open and for closed releases available Release managers can now search for open and for closed releases. For more details, see chapter "Search for releases" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Option "Recalculate index" available for the Assign design building block With the Recalculate index check box, the Assign design building block can be used with an index that is recalculated before it is used again. For more details, see chapter "Assign a value to a variable" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 168/389 Appendix: main updates in V7.3 l Order of tabs on the workplace can be changed Business users on all Correspondence workplaces can change the order of tabs by dragging a tab to another position. For more details, see chapter "Correspondence Management workplace" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Repeated table header can be defined in tables With the new Repeat header check box on the Table properties dialog, business users working with tables in Papyrus Client Canvas specify that the table header should be repeated on the next page in case a page break occurs inside the table. For more details, see chapter "Specify header and repeat header" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Table rows can be kept together With the new Keep with next row check box on the Table properties dialog, business users working with tables in Papyrus Client Canvas can specify that the selected row is kept together with the following row in case a page break would occur between these two rows. For more details, see chapter "Keep table rows together" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Location of attachments in a multi-part document template can be defined Template administrators working with multi-part documents can now move attachments to another position. For more details, see chapter "Move attachments in a multi-part document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l New inserts and attachments can be added to a multi-part document template Template administrators working with multi-part documents can now add new inserts and attachments. For more details, see chapter "Add inserts and attachment in a multi-part document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Guessing logic for Natural Language Rules (NLR) can be disabled For business users defining conditions with NLR, guessing logic can be disabled. If guessing logic is enabled, this may result in rules that are automatically corrected in the background without making the user aware of the correction. For more details, see chapter "Automatic logic and guessing of NLR in the background" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)"". l The "Done" button may not be available for documents currently being edited by another clerk If configured by the system administrator, a clerk cannot send a document currently being edited by another clerk for sign off because the Done button is not displayed. For more details, see chapter "Send a document for sign off" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l For dynamic tables, language variants can be defined Template administrators can define language variants for dynamic tables, similar to text variants or image variants. For more details, see chapter "Add a language variant to a dynamic table" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Variables can be moved by template administrator to another variable group Template administrators can move a variable that is not used yet in another building block to another variable group. For more details, see chapter "Move a variable to another variable group" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 169/389 Appendix: main updates in V7.3 l New options available for "Change layout" design building block When template administrators use the Change layout design building block in a document template, they can now define whether the new layout should be applied on the next page or after an enforced page break. For more details, see chapter "Link more than one layout to a document template" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Disabling of obsolete building blocks possible on a scheduled date Template administrators can now also select a future date for disabling a building block. Alternatively, it is still possible to disable a building block immediately. For more details, see chapter "Disabling obsolete building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Recommendations available on different ways to build a document based on the clerk's interaction Best practice information is available when to use a document template with user input or a wizard-based document template or a combination of the two. For more details, see chapter "Using document templates with user input (Prompt) and wizards" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Define which Text and Checkbox are Promptable in a PDF document Promptable text and checkboxes can be ignored on generation so that they are not promptable in the PDF document. For more details, see chapters "Inserting a check box into a document" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)" and "Define text input for a text positioning element" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". 14.1.7 Papyrus Client AFP Viewer l New profile parameter PDF417_USE_UTF8 By using this new parameter, you can make special characters coded in PDF417 standard codepage 437 readable by using 1202 UTF-8 as target codepage. For more details, see chapter "PDF417" in "AFP Designer Application Developer Guide (oaddge)". l Improved interpretation of DBCS blanks at OGL compilation The new profile parameter OglSaveMode was implemented to correct incorrect DBCS output on the host that differs from the original display in OverView AFP Designer. In case you have incorrect results with DBCS characters when compiling on the host, set this parameter accordingly. For more details, see "File | OGL compiler" in "AFP Designer Online Help (OVERVENG)". 14.1.8 Papyrus Designer FixForm and Server FixForm l New Object Structure for FixForm Extractor The object tree of FixForm extractor now contains a Capture extraction definition folder instead of the XSD data binary object previously used to store the extraction definition. The new folder contains a Capture Idex extraction definition object for the FixForm extraction definition of each document type in Document Defnition of the Capture Solution. For details, see chapter "Papyrus Designer Capture in Papyrus WebRepository" in "Designer Capture Application Developer Guide (pcddge)". See also "Migration from obsolete FixForm configuration object structure to new object structure" in "Designer Capture Application Developer Guide (pcddge)". l Replacement String for Keywords Now it is possible to define a replacement string for each keyword of pattern search processor. For details, see attributes list of keywords and specific replacement strings in chapter "Pattern search" in "Designer Capture Application Developer Guide (pcddge)". getstartede V7.6 SP3 170/389 Appendix: main updates in V7.3 l Additional Supported Data Types: CSV, MS Office with Macro Now, additionally the data types CSV and MS Office file types with macro (DOCM, PPTM, XLSM) are supported. 14.1.9 Papyrus Designer, Papyrus DocEXEC 14.1.9.1 Information relevant for DOCDEF developers l Repeated header for tables created by TEXT subcommand _TABLE Tables created by TEXT subcommand _TABLE allow now for definition of a header row that is repeated after every page break. For this purpose the subcommand _ROW has to be specified as _ROW(HEADER REPRINTHEADER). For more information, see chapter "_TABLE" in "DocEXEC Reference Application Developer Guide (pdedge)". l Function _SYS_ENVIRONMENT retrieves environment variables from operating system _SYS_ENVIRONMENT retrieves operating system's environment variables, either from the user or from the system environment. The function works similar to the ENVIRONMENT function that retrieves environment variables from the DocEXEC environment (defined in project, ICF file or on the material object). For more information, see chapter "_SYS_ENVIRONMENT" in "DocEXEC Reference Application Developer Guide (pdedge)". l Set of available tagging functions for PDF/UA enhanced The set of tagging functions was enhanced by several new functions. Tagging functions help you to define and manipulate tags for PDF/UA usage. For a list of available functions see chapter "Tag functions" in "DocEXEC Reference Application Developer Guide (pdedge)". For instructions how to create PDF/UA tags, see chapter "Creating PDF with universal accessibility (PDF/UA)" in "DocEXEC Reference Application Developer Guide (pdedge)"". l Functions for encryption and decryption of RSA-2048 data strings The functions _ENCRYPT() and _DECRYPT() facilitate encryption and decryption of RSA-2048 data strings. The Data Matrix barcode generator supports an option to suppress codepage conversion for data strings to be created as barcode. This option aims at data strings that were coded with these functions. For more information, see chapter "_ENCRYPT" in "DocEXEC Reference Application Developer Guide (pdedge)" and the description of the corresponding function "_DECRYPT". l Data Matrix barcode generator accepts encrypted data strings The command for Data Matrix barcode generation - Invoke DLL (DATAMATX DATAM) resp. CREATEOBJECT DATAMATX(DATAM) - allows to switch off codepage conversion so that encrypted data can be generated as barcode without corrupting encryption. For more information, see chapter "CREATEOBJECT DATAMATX(DATAM)" in "DocEXEC Reference Application Developer Guide (pdedge)". l AFP import parameter "Implement subgroup" now allows correct handling of suppressed text in the AFP to import With the "Implement subgroup" definition it is now not only possible to import overlays that are defined in the FormDef of the AFP to be imported but also suppressed text that is contained in the AFP to import. For more information, see chapter "AFPIMPORT command" in "Postprocessing/Printpool General Information and Developer Guide (pppdge)". getstartede V7.6 SP3 171/389 Appendix: main updates in V7.3 14.1.10 Papyrus Objects (WebControl/WebRepository) 14.1.10.1 Papyrus Objects System l Struct Handling Added new "Struct Handling" section to "Define attributes with structured Data (OMS structs) in WebRepository Application Developer Guide (pwride)" showing how to manipulate structs via PQL. l Instance-specific Translation Extended section "Instance-specific translations of displayed text in WebRepository Application Developer Guide (pwride)" with PQL samples that determine whether an object instance already has such translations. l Tenant Collection: GetTenants() no longer returns $displayName Prior to v7.30 2018-10-22, the method TenantCollection::GetTenants() returned a PQL set containing the $logicalGUID and $displayName of found tenants. $displayName is no longer returned in that set because its computation incurs considerable overhead, while most callers of the method do not actually need it. ISIS Papyrus applications have already been updated with this change, but some custom implementations that call GetTenants() might need to be adapted. A custom PQL script using the $displayName returned by that method would instead have to call $reload to obtain that attribute. E.g.: ... @Tenants = fromMem(@TenantCollection.GetTenants().return1); @Tenants = @Tenants\$reload.$logicalGUID,$displayName; ... Modification date: v7.30 2018-10-22 l Instance-specific translation Extended section "Translation of individual object names & attribute values in WebRepository and WebControl Installation and Administrator Guide (poinste)" with links to PQL samples that determine whether an object instance already has such translations. l APA - Default behavior changed Now all processes are registered to the APA Net Broker by default, if ISIS_PCS_APANET_BROKER is set up in a certain way. For more details, see chapter "Prerequisites for analyzing a process using APA" in "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)". 14.1.10.2 Papyrus Depot l Preconfigure values for search attributes in Depot Search In the Depot search settings the 2 new attributes Default search attributes values (global) and Settings specific default search attribute values can be used to preconfigure values for search attributes in Depot search workplace. This can be done on a scope and on application level. For more details, see chapter "Preconfigure the workplace in Settings Explorer" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". 14.1.10.3 Papyrus Adapters and Typemanagers l REST Adapter The available REST interfaces have been documented in chapter "REST adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". getstartede V7.6 SP3 172/389 Appendix: main updates in V7.3 14.1.10.4 Papyrus Query Language (PQL) l Instance-Specific Translation Extended section "Framework Developer Use Cases in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" with new article "Access instance-specific translations via PQL in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l pqlpdf Library Enhancements Added support for new MIME types (.CSV & .DOCM files) and for embedded .PDF files. RotationAngle now applicable to all resource types; PageSize formats with '-:' now applicable to all layers. Improved performance for JPEG images using DCTDecode,100. 14.1.10.5 Papyrus Resource Collection l Import upper limit per project - new attribute This new attribute has been added to the Resource Settings object to specify the maximum number of resources added to the Resource Import Project. For more details, see chapter "Setting up the resource import/creation adapter using wizard" in "". 14.1.10.6 Papyrus EYE Widgets l Breadcrumb Widget This widget allows you to display a path-like information in hierarchical data. For instance, the currently selected object in a tree can be displayed as path. For details, see "Breadcrumb widget" in "EYE Widgets Developer Guide (popeyewdge)". getstartede V7.6 SP3 173/389 Appendix: main updates in V7.3 14.1.11 Papyrus Server 14.1.11.1 AFP to PDF l PDF/A-2a - supported Part 2 of the standard addresses some of the new features added with versions 1.5, 1.6 and 1.7 of the PDF Reference. This format supports transparency effects and layers, the embedding of Open Type Fonts OTF, provisions for digital signatures in accordance with the PDF Advanced Electronic Signatures - PAdES standard, the option of embedding PDF/A-1a files as attachments to facilitate archiving of sets of documents with a single file. For more details, see chapter "PDF/a (PdftPDF_A)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l PDF/A - Forms supported PDF/A allows TrueType and Open Type fonts in text prompts. Additionally check boxes can use characters of AFP Outline fonts. For more details, see chapter "PDF/A using text input fields and check box fonts" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l PAdES - supported PAdES (PDF Advanced Electronic Signatures) is a set of restrictions and extensions to PDF and ISO 32000-1 making it suitable for Advanced Electronic Signature. PAdES specifies precise profiles making it compliant with the European eIDAS regulation (electronic IDentification, Authentication and trust Services). eIDAS is legally binding in all EU member states since July 2014. For more details, see chapter "PAdES" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l AES 256 bit - supported It is now possible to encrypt documents with the 256-bit Advanced Encryption Standard. For more details, see chapter "Encryption level (PDFtEncryptionLevel)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l PDF Forms and rotation - improved behavior In case AFP Form Definitions contain duplex tumble, the PDF page rotation using parameter PdftRotation has been improved. For equal rotation of all pages set PdftDuplex="2" to ignore the tumble. l Inherit zoom to internal page hyperlink (PreserveZoomInLinks) - New Parameter This parameter determines whether the current zoom level is kept or changed to "Zoom to Page Level" after clicking a document internal link. For more details, see chapter "Inherit zoom to internal page hyperlink (PreserveZoomInLinks)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". 14.2 Updates in SP1 Improvements are provided with this Service Pack and affect the following products and solutions: getstartede V7.6 SP3 174/389 Appendix: main updates in V7.3 14.2.1 Papyrus Adaptive Case Management Solution 14.2.2 Papyrus Automated Document Factory Solution 14.2.2.1 Information relevant for administrators and developers l Parallel processing optimized/fixed In some rare scenarios a task with multiple materials of the same type could be moved to early. For details see chapter "Processing tasks with multiple materials in same queue" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l PedOcEmail - new features The syntax check for e-mail addresses, which was introduced in V7.3, caused some problems with e-mail lists and aliases. Thus an option to deactivate it, or replace it with a customer specific PQL, was added. Additionally there is the possibility to do a character mapping. Suppose a database has [at] in its entry, and you need to convert it to @ to send the e-mail. For details see chapter "E-Mail" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". 14.2.2.2 Information relevant for business users l ADF Workplaces - Naming The Window Bar names were changed to be more informative and match their names in the Library. The Workplace names were shortened to provide more space for other relevant information. For details, see chapter "ADF users" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)". l Expired tasks and Expiring tasks - fixed Certain situations could cause these 2 views in the "Task overview" tab to become unresponsive and even effect the Portal node the user was connected to. This has been fixed. For details, see chapter "Task overview" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)". l UI improvements The new standard Papyrus workplace switcher is now available for the ADF workplace to switch between it, the Depot Search workplace and the Bounce Handling workplace. Furthermore a few missing German translations were added. For details, see chapter "Old ADF workplace" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)". l Depot Search - A few translations have been reworked and some German translations were added. - The "Edit" button in the result details view works again. - A simple search can now also be triggered by pressing 14.2.3 Papyrus Business Correspondence Solution 14.2.3.1 Information relevant for administrators and developers Improvements are provided with this Service Pack and affect the following use cases: getstartede V7.6 SP3 175/389 Appendix: main updates in V7.3 l Variable list is not updated in Papyrus Desktop The removal of a variable group using Papyrus Desktop did not result in the variable list in Papyrus EYE Widgets being updated for the template administrator. Instead, the GUID of the variable group was shown to the template administrator. In addition, each text variant maintained a reference to any variables that were used in the text. Now, this behavior is corrected. On removal of a variable from or addition to the text, the system will update the variable list associated with the text variant. 14.2.3.2 Information relevant for Business Users Improvements are provided with this Service Pack and affect the following use cases: l Use existing dynamic tables with multi-language support If you want to use dynamic tables that were created before V7.3 and you want to use multi-language support introduced in V7.3 for dynamic tables, this Service Pack is mandatory. Without the Service Pack, the content of both the original and the new language could be lost if the template administrator edited or duplicated an existing dynamic table created in a version before multi-language support and then switched the language. l Simulation of building blocks and document templates If simulation of building blocks and document templates is used, this Service Pack is recommended because it contains several improvements for simulation. n Layout simulation for a group with tables If a group with tables is simulated and the table flows across pages, this may have led to the table not being split in the right location and to content being repeated. Now simulation for a group with tables shows correct output on all pages. If a group with tables is simulated and a table cannot be placed on the page, Papyrus Client Canvas does not loop but stops and displays an information message. n Editing text variant with variables during simulation If a text variant having variables was edited during a simulation, the variables were removed from the text variant after pressing [F2]. Now pressing [F2] in a text variant having variables during a simulation does not remove the variable. l Keyboard shortcut Undo [Ctrl]+[Z] in Papyrus Client Canvas Undoing an action by pressing [Ctrl]+[Z] in Papyrus Client Canvas after a variable was inserted removed the variable but afterwards the shortcut could not work anymore. This was corrected. l Dynamic table with a high number of entries Formatting dynamic tables with many entries in Papyrus Client Canvas and DocEXEC is now faster due to performance optimizations. 14.2.4 Papyrus Business Capture Solution 14.2.4.1 Information relevant for administrators and developers l Email adapters: Invalid XML character (Unicode 0x1A) Unicode 0x1A is an invalid XML character which prevents instantiation of email tasks if present in email text causing error message ("PPQL2021E XML parser error: Invalid character (Unicode: 0x1A) (12/54) "). This has been fixed. Explanation: invalid control character 0x1A in XML is a known issue. There is a lot information in the www. l FixForm Designer: Text recognition attribute "Force recognition" For modified recognition processors the attribute "Force recognition" failed to work correctly. This has been fixed. getstartede V7.6 SP3 176/389 Appendix: main updates in V7.3 l Capture Solution Creation Wizard Capture solution creation wizard has been improved with version v7.3 SP1. l Papyrus Client Capture: Completion view After confirmation of the last child document of a batch a Physical document with a Filtered data created as sibling of the child documents. Fixed in version v7.3 SP1. l Shutdown of kernels with Capture installation A case has been reported where kernels after trying to shutdown entered an endless loop. The kernels were running in batch mode and could not be stopped with CTRL+C. This has been fixed. 14.2.4.2 Information relevant for business users Information relevant for Papyrus Client Capture Users l Capture workplace/Completion view: Client controller After updating to version v7.3 from version v7.19#5 (or merely updating the binaries to v7.3) when Papyrus Eye Widgets Desktop is started, no log-in but an error message ("Client controller error - Method 'Call' not supported in command") is displayed. This is relevant for Completion view where the Client Controller is used for view customization and where this controller calls the method SetApiTriggerSet(). Fixed in v7.3 SP1. l Papyrus Client Capture: Completion view token display In cases when emails with embedded images have been imported, Completion view displayed tokens incorrectly. Fixed in version v7.3 SP1. l Papyrus Client Capture: Thumbnails missing in Document workplace In cases when upgrading from version v7.1 SP9#6 to v7.3, thumbnails are missing on Document workplace (error message: "PPQL2005E Invalid object reference used for object path"). Capture documents are not allowed to be used without the tenant. Nevertheless, it should not prevent the other documents to be loaded in the views. Fixed in v7.3 SP1. l Customized user interfaces with Capture A new command is available for custom implementations of combined user interfaces to set the focus into the capture scope when working with the Completion view integrated into other views/customer views. l Papyrus Eye Widgets Desktop: Login failed When trying to login on Papyrus Eye Widgets Desktop it could happen that login failed with the following error message "Login failed - Error downloading". This happened because Session had not been closed properly after leaving Papyrus Eye Widgets Desktop in previous sessions. This has been fixed. Information relevant for Papyrus Scan Users l Papyrus Scan: Scan profile not updated When scan profile is closed on a tab other than "Standard", after re-login profile is not loaded correctly. Fixed in version v7.3 SP1. l Papyrus Scan: File scan Improved handling of resolutions for different file formats for 'File scan' in the Scan view. It helps to avoid errors in some rare combinations for different formats. l Papyrus Scan: Scan view appearance = legacy style Shortcut CTRL+E caused an error when working in the default mode of the Scan view (in this mode no search and no depot documents are shown). This has been fixed in version v7.3 SP1. getstartede V7.6 SP3 177/389 Appendix: main updates in V7.3 14.2.5 Papyrus Client Document Creation (Canvas) l Wrong display of tables in a text input field after page break corrected If two tables were inserted in a text input field, and a page break occurred in the first table, the part of this table following the page break was displayed incorrect. Now this behavior has been corrected and the part of the table after the page break is displayed correctly. l Display of inner horizontal table lines corrected If you created a table in a text input field and changed, for example, the color of the inner horizontal lines, the horizontal lines were no longer displayed, but only the vertical lines. Now this behavior has been corrected and the inner horizontal lines are displayed correctly after the change. 14.2.6 Papyrus Designer, Papyrus DocEXEC 14.2.6.1 Information relevant for administrators l Limit the number of cached filtered objects to avoid memory overload: FILTERCACHELIMIT TEXT or TEXTPROMPT commands that use subcontrol FILTER or DFACODE create objects that are stored in cache. In versions prior to 7.3 SP1, the number of cached objects was set to unlimited by default if the length of such text blocks was smaller than 246 characters. With 7.3 SP1 the number of cached objects can be limited by DocEXEC main profile parameter FILTERCACHELIMIT and even completely deactivated by DFACACHEMODE. Because parsing of these TEXT objects is done during runtime (which is time consuming) the cache which stores the already parsed TEXT objects can help to reduce CPU time on the one hand. On the other hand cached objects are stored in the memory, so the memory consumption is higher if a great number of objects is cached. The default value is a good compromise between memory usage and speed, but the performance gain which can be potentially reached is very project-dependent. If the parsed TEXT command is long and complex then the cache has greater effect than in case of short and simple TEXT commands. Of course, the cache has real effect only if the used TEXT commands are identical for many documents. If the parsed TEXT commands are different in every document then the filter cache does not help to reduce the CPU time. In situations where projects use many TEXT commands with FILTER or DFACODE, and the parsed text block is relatively long and the project generates a great number of documents, the formatting process could cause a memory overload. In such situations FILTERCACHELIMIT can be used to limit the number of cached objects. For more information, see chapter "FILTERCACHELIMIT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l Switch on/off object caching by FILTER and DFACODE: DFACACHEMODE TEXT or TEXTPROMPT commands that use subcontrol FILTER and/or DFACODE create objects that are stored in cache. In versions prior to 7.3 SP1, object caching by FILTER or DFACODE was always active and the number of objects cached was set to unlimited. With 7.3 SP1 caching can be switched off so that commands using FILTER or DFACODE do not create cache object keeping memory consumption low. If by DocEXEC main profile parameter DFACACHEMODE is activated (set to "YES", which is the default), objects will be cached and their maximum number can be controlled by FILTERCACHELIMIT. If DFACACHEMODE is set to "NO", the object cache is completely deactivated. For more information, see chapter "DEDFACACHEMODE / DFACACHEMODE" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 14.2.6.2 Information relevant for DOCDEF developers l Codepage parameter value '0' in MEM_TO and MEM_FROM functions MEM_TO and MEM_FROM accept as first parameter the number of a codepage. If this parameter is set to '0' no codepage conversion is made. MEM_FROM does no codepage conversion but saves the string as hex values according to the current source codepage and saves them to a memory variable. MEM_TO creates a string from a memory variable. The string is build according the saved hex values. The '0'-option has been present ever since but is described with 7.3 SP1 for the first time. For more information, see chapter "MEM_TO" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 178/389 Appendix: main updates in V7.3 14.2.7 Papyrus Objects (WebControl/WebRepository) 14.2.7.1 Papyrus Objects System l Transfer Template for Framework Upgrade For the import of frameworks a transfer template has been prepared (was already available, but documented only now in v7.3 SP1). It has to be defined in the import settings to benefit from it. This transfer template is for minor/major release framework upgrades (e.g. 7.2 to 7.3 or 7.2 to 8.0) but not for service pack upgrades (e.g. 7.2 SP1 to 7.2 SP2). For details, see "Preparations for framework upgrades" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". l New View with List of Imported Versions to Merge To simplify the import, there is now a view to get a list of imported versions that have to be merged. For details, see "Merge imported versions" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". 14.2.7.2 Papyrus Depot l Depot Exporter Previously, the Depot PQL "Depot exporter" could only be run from the DCC of the partition of a distributed depot. Now Depot PQL "Depot exporter" can also be called from the distributed DCC of a distributed depot. For details about the Depot PQL "Depot exporter", see chapter "Depot exporter" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Depot Search - A few translations have been reworked and some German translations were added. - The "Edit" button in the result details view works again. - A simple search can now also be triggered by pressing 14.2.7.3 Papyrus EYE Widgets l Application Switcher has new width The width of the application switcher (blue bar on the left with icons for widget applications) has been reduced to 52px. Workplaces provided by Papyrus Software are not affected, but in case you have own workplaces with icons not fitting, a horizontal scrollbar is displayed. It might be necessary to reduce the size of your icons used for widget applications to fit in the new application switcher. 14.3 Updates in SP2 Improvements are provided with this Service Pack and affect the following products and solutions: 14.3.1 General changes l Spellchecking and hyphenation: new set of TRF files For using spellchecking and hyphenation in solutions based on Papyrus WebRepository TRF files are a medium to import the required libraries and profiles into the Object Space. With release 7.3 SP2 names and structure of the TRF files have changed. However, these files can not only be imported in Object Spaces since this release but also in Object Spaces prior to the 7.3 SP2 release state. For more information, see chapter "Install Proximity technology by transfer file (Resource Collection usage)" in "Spellchecking and Hyphenation Installation Guide (spellhyphe)". getstartede V7.6 SP3 179/389 Appendix: main updates in V7.3 14.3.2 Papyrus business Capture Solution 14.3.2.1 Information relevant for administrators and developers l Capture Solution templates missing in Library folder The Library folder Library/Application frameworks/Capture/Capture frameworks missed some Capture Solution templates in the previous release v7.3 SP1. The missing templates have been restored in version v7.3 SP2. l IMAP receiver disconnecting IMAP receiver keeps disconnecting and reconnecting to IMAP server approximately every 3 minutes, if the attribute "Processing folder" of the IMAP receiver has not been specified. This has been fixed in version v7.3 SP2. l Capture UI views: HTML/Text documents invisible If HTML/Text documents (e.g. e-mails) processed before version v7.20 are loaded in Capture UI views running on systems upgraded to version v7.20 or newer, then it may happen that the documents are empty or not correctly displayed in thumbnail viewer and data viewer of Capture views. To be able to display HTML/Text documents created before version v7.20 on systems upgraded to version v7.20 or newer a special script has to be run to convert the old storage format into the new one. For detailed information about the conversion script required for your data, please contact ISIS Papyrus Support. l FixForm Designer: Creating or loading definition sets not possible Due to a change of the object structure of the extraction definition in Papyrus Objects it was not possible to create a new definition set (DefSet) or load an existing one with Papyrus Capture Designer/FixForm. This has been fixed in version v7.3 SP2. l Loading AFP file in FixForm Designer fails In some cases loading an AFP file into Papyrus Capture Designer/FixForm failed with the following error message: "XFileFormat: No suitable Decoder registered for this type of file". This has been fixed in version v7.3 SP2. l Standard recognition processor: Extraction fails when "analyze page" is set after reading empty region When Standard recognition processor with "analyze page" set has been called on a region containing no characters, then the respective document could not be extracted. This affected not only empty regions but also empty page using fullpage processor. This has been fixed in version v7.3 SP2. 14.3.2.2 Information relevant for business users Information relevant for Papyrus Client Capture Users l Completion view: Page navigation shortcuts fail If Completion view has been used as component of Capture business user workplace and the form view has been hidden, then the navigation shortcuts (next page/previous page) did not work. This has been fixed in version v7.3 SP2. l Document workplace view: Nothing selected after deletion of single document When for Document workplace view of Capture workplace a guided classification option has been set and a single document was deleted, then nothing has been selected in thumbnails viewer although the correct document is displayed. This has been fixed in version v7.3 SP2. Now the top-most document in thumbnails viewer will automatically be selected as expected. Information relevant for Papyrus Scan Users getstartede V7.6 SP3 180/389 Appendix: main updates in V7.3 l Scan View: Export all - some exported Tiff files incomplete If a number of documents has been exported with the feature "Export all" as TIFF in Scan view of Capture workplace or Document depot view of Capture administration workplace, then sometimes some of the exported TIFF files were rendered incomplete. This has been fixed in version v7.3 SP2. 14.3.3 Papyrus Business Correspondence Solution 14.3.3.1 Information relevant for Administrators and Developers Improvements are provided with this Service Pack and affect the following use cases: l ACM Change Management - Automatic Creation of Allocation Groups Allocation Groups are automatically created and are no longer manually created. Existing Allocation Groups must be converted to ensure that business user access performance is maintained. For details on converting existing allocation groups, see chapter "Application node storage" in "". 14.3.3.2 Information relevant for Business Users Improvements are provided with this Service Pack and affect the following use cases: l Setting a variable value with the Assign design building block If you create a variable with a certain variable format, e.g. of Float type with the format #,##0.00, and then use the Assign building block to set a value, the variable format mapping is not taken into account. This means that the number is not shown as e.g. 95,000.00 but incorrectly as 95000. To take over the variable format mapping, this Service Pack is mandatory. 14.3.4 Papyrus Client l Printing a document containing GOCA elements with white color When printing a printer driver generated overlay, which contains the GOCA white color, on Windows print, PCL 3 and PCL 4 monochrome printers, GOCA white was printed as black bar. Now this behavior was corrected and GOCA white is output as expected. 14.3.5 Papyrus Client AFP Viewer l An error message is displayed if no printer is defined If no printer at all is defined in the Windows system, a dump occurred, when trying to print an AFP file. Now this behavior was corrected and an error message informs users in case no printer is available. getstartede V7.6 SP3 181/389 Appendix: main updates in V7.3 14.3.6 Papyrus Designer, Papyrus DocEXEC 14.3.6.1 Information relevant for administrators l Charts with GOCA fill patterns: GOCAPATTERNMAPPING backward compatibility parameter Charts that use GOCA fill pattern mode show a difference in the representation of these patterns in print if the AFPDS was produced by different versions of DocEXEC. For example, the print result will be different if an AFPDS was produced by a DocEXEC version prior to v6.09a and by a version after this release state. GOCA fill patterns are symbols repeated, both in the horizontal and vertical directions, to fill a chart's areas. GOCA fill patterns were extended in the past (2004) and the change was not backwards compatible. You activate the GOCA fill pattern mode by setting a chart's ImageMode parameter to Goca Vector and select for ShadeMode one of Mono pattern, Color pattern, True Color pattern or Highlight pattern. With ShadeList you can assign particular patterns by means of an additional parameter, for example by RGB(58,38,20,1);RGB(58,38,20,2);RGB(58,38,20,3). Papyrus DocEXEC profile parameter GOCAPATTERNMAPPING allows to set the mapping of each GOCA pattern index to achieve the printing results of any DocEXEC version. For more information, see chapter "DEGOCAPATTERNMAPPING / GOCAPATTERNMAPPING" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l Papyrus Designer profile (pddw3.prf): retaining security settings The update method of the Papyrus Designer profile was changed so that its specific security settings are retained even when the same profile is used by different users. The Papyrus Designer profile stores the setting of Papyrus Designer (window position, used files, etc.) and is updated when Papyrus Designer is closed. Prior to version 7.3 SP1 the whole file was replaced applying security settings of the user who closed the file. Therefore it could happen that this file's security settings changed over the course of time when the file was shared among different users. Since version 7.3 SP1 only the file's content is updated, retaining the files security settings. The update method was already modified in 7.3 SP1, but the modification is reported with 7.3 SP2 for the first time. For more information about the Papyrus Designer profile, see chapter "Configuring Papyrus Designer" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 14.3.6.2 Information relevant for DOCDEF developers l XMLREAD command: type mapping with restrictions in XML Schema Definition (XSD) DocEXEC versions prior to 7.3 SP2 ignored the restriction property for type mapping in XML Schema Definitions (XSD). This has been fixed in version v7.3 SP2. Element definitions like the following were not correctly used: l PDF/A: color profiles (ICC files) embedded in PDF/A documents When PDF/A documents were produced and the pages created only contained imported PDF pages but no other page objects, then color profiles (ICC files) were not embedded. Color profiles, however, are necessary for PDF/A validation. The command used for importing PDF is Invoke DLL calling IOBDEFS function of IOBDLL library. The issue has been fixed in version v7.3 SP2 so that ICC files are now embedded. For information on Invoke DLL command used for PDF import, see chapter "CREATEOBJECT IOBDLL(IOBDEFS)" in "DocEXEC Reference Application Developer Guide (pdedge)". For information on the production of PDF/A, see chapter "PDF/A creation" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". getstartede V7.6 SP3 182/389 Appendix: main updates in V7.3 l Bar charts: rotated axis description text of bar charts The positioning of descriptive chart axis text was incorrect in some situations when the text was rotated. In versions up to 7.3 SP2 the positioning of axes text was dependent on column thickness. If the text was rotated (i.e. in angular or perpendicular position to the axis) it could happen that it was placed at an incorrect position if the column thickness changed. The parameter which determines the rotation angle is Chartdll parameter XTextDirection. This has been fixed in version v7.3 SP2. For more information on chart parameters, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)". l TEXT command: image duplication and distortion by SEGMENT(REFERENCE( 14.3.7 Papyrus Objects (WebControl/WebRepository) 14.3.7.1 Papyrus EYE Widgets l Desktop: custom login dialog and loading screen It is now possible to change the logo, the background colors, and some other elements of the login screen and it is also possible to customize the please wait image, the progress bar animation, and the background color of the loading splash screen. For details, see "Custom login and loading screen" in "EYE Widgets Developer Guide (popeyewdge)". l Desktop: Improved message text for expired password When a user log in fails due to an expired password, so far only "Error Code: 1" was displayed in the message dialog of Papyrus Desktop/EYE Widgets (HTTP, HTTPS, and direct connection). The error message text has been improved to clarify that the password has expired. 14.3.8 Papyrus Server 14.3.8.1 Papyrus Server IPDS l Adjust character box size - New Parameter This parameter was introduced to deal with printers handling the width/height definition of character boxes in the FNM structured field differently. Correctly set it prevents some IPDS printers from crashing or printing characters with corrupted shape, rendered as blurred and distorted stripes. For details, see chapter "Adjust character box size (IPDSPatchCharBoxSize)" in "Papyrus Server - IPDS Reference Guide (pseipdsrge)" 14.3.8.2 Papyrus Server PCL l GOCA white output fixed for PCL 3 and 4 GOCA white was printed as black box on monochrome printers. PCL 5 was not affected. getstartede V7.6 SP3 183/389 Appendix: main updates in V7.3 14.3.8.3 Papyrus Server PDF l ICC files and PDF/A ICC files (color profiles), which are necessary for PDF/A validation, are now correctly appended. There was a bug in case the source AFP only consisted of IOB imported PDF objects. getstartede V7.6 SP3 184/389 Appendix: main updates in V7.2 15 Appendix: main updates in V7.2 If you upgrade from an earlier version to the newest version, use the appendix to see a history of all changes that have accumulated. Note that the cross-references in the appendix refer to chapters in documents of the same version. This means that some of the History of Changes entries in the appendix may include cross-references to chapters that do not exist anymore in the newest version of the document or whose information was updated in the meantime. If you are in such a case interested in the details you will need to access the documents of exactly that version. 15.1 Main updates in V7.2 15.1.1 General changes This delivery includes Papyrus products in release level V7.2. 15.1.1.1 Information about main updates before V7.2 This document contains information about main updates in V7.2. For information about major updates before V7.2, see previous editions of this document. 15.1.1.2 New platform codes A new platform code for z/OS native is introduced in V7.2 to clearly distinguish between z/OS Unix and z/OS native: u3/u6 - z/OS Unix 32 and 64 Bit m3/m6 - z/OS native 32 and 64 Bit The new platform code is only displayed in log file entries. Executable and product folder names still use mu. Examples (log file entries): PSEM3FARC/mainthread ... PPCS8040L ... Version V7.2/m3 of '2018-04-01 (build:7.20.0.18320) pocu3knl/mainthread ... PPCS8040L ...Version V7.2/u3 of '2018-04-01 (build:7.20.0.18320) 15.1.1.3 New documents l Mobile Application Administrator Guide This new document is addressed to Papyrus Objects system administrators and guides through the basic configuration steps for creating mobile user accounts, utilizing the generic Papyrus Enterprise App which is available for all leading mobile devices. It also provides an overview of various, prefabricated Business Applications designed for specific business requirements to support different Papyrus Solutions and shows how to create individual Business Applications. For details, see "Mobile Application Administrator Guide (pomaage)". 15.1.2 Papyrus product installation l New information available about installation in silent mode New information is available about running the Papyrus Installation Routine in silent mode such as required directory structure and running a silent installation using CMD or PowerShell. For more details, see chapter "Running the Papyrus Installation Routine in silent mode" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". getstartede V7.6 SP3 185/389 Appendix: main updates in V7.2 15.1.3 ISIS Papyrus product authorization service l New information available about Papyrus in the cloud New information is available regarding protocols that must be supported by the cloud solution/provider. For more details, see chapter "System requirements" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". l New information available about proxy compatibility for IPASaaS-Protection New information is available about defining proxy settings for IPAS as a Service - Protection. For more details, see chapter "IPASaaS-Protection proxy compatibility" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". l New information available about Hardlock Key drivers A new troubleshooting chapter describes the availability of matching Hardlock Key drivers, providing a link to the vendor website for driver installation. For more details, see chapter "Hardlock Key driver issues" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". 15.1.4 Papyrus Adaptive Case Management Solution 15.1.5 Papyrus Automated Document Factory Solution l Local Instantiation With more and more solutions using Print and E-Delivery and an increasing complexity in customer implementations, often with multiple ADF setups, explicit load balancing became a desirable feature. Furthermore a local instantiation can greatly increase the performance and responsiveness of the system. For details, see chapter "Local instantiation and load balancing" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Flexible Attachment Selection via PQL Typically email attachments are added by adding a child object of the index object to the email-task. However there are scenarios where more flexibility is desirable and achieved by using PQL. For details, see chapter "E-Mail" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Improvements for Bundling in multiple Environments A new attribute was introduced to distinguish from which depot a certain task originated. For details, see chapter "Multiple PED environments and bundling" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Use non AFP index data to trigger Print and E-Delivery Usually AFPs are checked into a Print and E-Delivery depot. Based on the index information in these AFPs certain PED rules are triggered. However there are scenarios, where an AFP is not part of the workflow. For details, see chapters "InsertData" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)" and "PED importer" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)" in the developer section. There is also a ready to use "PED CSV importer" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Allow other Application to control Print and E-Delivery Until now Print and E-Delivery was an inner closed framework. The evolution and ever increasing feature set of other solutions required the implementation of a bi-directional communication layer. For details, see chapter "Allow other applications to control PED" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)" in the developer section. getstartede V7.6 SP3 186/389 Appendix: main updates in V7.2 l Use a subset of productive data for test runs Before launching a campaign, and sending out all the emails, it is strongly recommended to verify that everything looks as planned. For these tests (parts of) real productive data should be used. The Print and E-Delivery Solution now offers a very convenient way to create these runs. For details, see chapter "Test with subset of productive data" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Improved Support for Complex Bundling Scenarios New especially for Print and E-Delivery derived classes from Depot archive status are available. They greatly ease the bundling based on a certain JobID or to apply selection and filter criteria. They are described in the context of bundling in a separate article. For details, see chapter "Bundling" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Gather Queue Information If Print and E-Delivery is triggered, a task is instantiated into a queue. The task is navigating through different queues "on its own". Therefore, when instantiating there is no information which queues will be used, nor anything about the current load of the queues. In order to remedy this situation some methods were added For details, see chapter "Gather queue information" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)" in the developer section. l Useful methods - new chapter in developer section In this chapter various methods or groups of methods are introduced. They are presented in the context of a certain use case or code snippet. This information can be helpful when extending the Print and E-Delivery functionality or doing non standard customizations. For details, see chapter "Useful methods" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Bounce Solution - new workplace available The Bounce handling workplace is described in a new extra chapter. For details, see chapter "Bounce handling workplace" in "Papyrus Client - Automated Document Factory User Guide (poadfuge)". l Display PED information in Depot Search If activated in the Depot search settings in the Settings Explorer the data of the PED information object will be displayed in result details tab of the depot search. For details, see chapter "Depot search" in "". l Reorganization of PDF manual The Introduction was extended to discuss ADF, Print and E-Delivery and Bounce in a little bit more detail. The chapter "General Elements of the ADF Framework" was removed, because it had very little relevance for the business user. For complete and thorough theory see the respective chapters in WebRepository - Automated Document Factory Solution Administrator Guide (poadfage). 15.1.6 Papyrus Business Correspondence Solution 15.1.6.1 Information relevant for Business Users l New buttons available in Papyrus Client Canvas for saving document as Word document Business users can save a document template or a document as a Word file (.DOCX) using the new Generate Word and Generate and view Word buttons on the Generation toolbar. For more details, see chapter "Save as Word document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 187/389 Appendix: main updates in V7.2 l Single-source document template creation available for print, web, and e-mail Template administrators can create one document template for different output channels such as document variants for print, web, and e-mail. For more details, see chapter "Creating a single document template for print, web, and email" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l New button available in Papyrus Client Canvas for double underline only words In the Papyrus Client Canvas plugin, business user can use a new button on the Font toolbar to double underline only words but not spaces. For more details, see chapter "Format characters" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Help button available also for clerks on Papyrus Desktop/EYE Widgets If this is configured by the system administrator, clerks and supervisors can find a Help button also on the Papyrus Desktop/EYE Widgets. For more details, see chapter "Accessing online help and information" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Table border definition can be converted to cell border definition in dynamic tables Template administrators working with dynamic table building blocks can convert table border definitions to the cell border definitions. For more details, see chapter "Convert table border definition to cell border definition" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Images with the same name as existing resources can be uploaded in image variant editor Template administrators working with image building blocks can now upload a file having the same name as an existing resource in the Library. If the upload is confirmed, the file is uploaded and a timestamp is appended to the name. For more details, see chapter "Upload an image from the file system" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l PNG files supported in image variant editor Template administrators working with image building blocks can now upload also PNG files. For more details, see chapter "Support for different image types" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Overview of different table types A new chapter is available outlining different types of tables for template administrators and the difference between them. For more details, see chapter "Using tables in document templates" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Formatting of list numbers possible Business users defining numbered lists can change the numbering format such as color, size, and font without changing the format of the text in the list. For more details, see chapter "Format list numbering" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". 15.1.6.2 Information relevant for Administrators and Developers l Single-source document template creation can be configured for print, web, and e-mail Single-source creation can be configured so that business users can create one document template for different output channels such as output variants for print, web, and e-mail. For more details, see chapter "Configuring Single-Source document template creation for Print, Web, and E-Mail" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 188/389 Appendix: main updates in V7.2 15.1.7 Papyrus Business Capture Solution 15.1.7.1 Information relevant for business users l Navigating through thumbnails viewer of Document workplace view with arrow keys: Documents and pages of thumbnails viewer of Document workplace an be navigated with the keys [ARROW LEFT] AND [ARROW RIGHT] For details, see "Thumbnail viewer" in "Papyrus Client - Capture User Guide (popcfuge)". l New shortcuts for image viewer: Images in the image viewer of Document workplace view as well as Completion view can also be rotated with the following shortcuts: n Rotate left: [CTRL]+[L] n Rotate left: [CTRL]+[R] l New shortcut for Document workplace view: n Button Classify: [CTRL]+[Y] l Search results table of Completion view: Changeable columns and rows: The row height of the search results table of can be modified. The order of columns in table can be changed as well. Changes will persist after relogin. l New shortcuts for toolbar buttons of Scan view: n Commit: [ALT]+[C] n Scan: Commit: [CTRL]+[S] n Delete: [ALT]+[DEL] or [ALT]+[SHIFT]+[DEL] n Delete all: [CTRL]+[DEL] or [CTRL]+[SHIFT]+[DEL] n Split: [CTRL]+[S] or [CTRL]+[SHIFT]+[I] n Start: [CTRL]+[ALT]+[S] n Shutdown: [ALT]+[T] n Reset: [ALT]+[E] n Connect: [CTRL]+[ALT]+[C] n Disconnect: [CTRL]+[ALT]+[D] n Stop scan: [CTRL]+[SHIFT]+[T] n Size: [ALT]+[SHIFT]+[S] n Scan file: [ALT]+[S] n Rescan: [ALT]+[SHIFT]+[X] (scan queue), [CTRL]+[ALT]+[SHIFT]+[X] (search) n Insert scan before: [ALT]+[D] (scan queue), [ALT]+[SHIFT]+[D] (search) n Export: [ALT]+[X] (scan queue), [CTRL]+[ALT]+[X] (search) n Export all: [ALT]+[SHIFT]+[X] (scan queue), [CTRL]+[ALT]+[SHIFT]+[X] (search) l New shortcuts for image viewer: Pages in the image viewer of scan view can be rotated with n Rotate left: [CTRL]+[L] n Rotate left: [CTRL]+[R] l New shortcuts for dialog "Profile Settings" n Apply permanently: [F12] n Edit: [ALT]+[E] n Delete profile: [ALT]+[DEL] n New profile: [ALT]+[N] n Duplicate profile: [ALT]+[D] n Restore profile: [ALT]+[R] n Select scanner: [ALT]+[S] n Settings: [ALT]+[P] getstartede V7.6 SP3 189/389 Appendix: main updates in V7.2 l Navigating through thumbnails viewer with arrow keys: Documents and pages of thumbnails viewer (scanned items and search) can be navigated with the keys [ARROW LEFT] AND [ARROW RIGHT] For details, see "Scanned items area" in "Capture Scan Administrator and User Guide (poscanauge)". 15.1.7.2 Information relevant for administrators and developers l Support of Native Office Documents in Papyrus Capture Papyrus Capture supports processing native office documents without requiring conversion. For details, see chapter "Processing office documents with Capture Solution" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". 15.1.8 Papyrus Client AFP Viewer l New Antialiasing button The new Antialiasing button in the View toolbar helps to correct display inaccuracies that may occur with neighboring areas with shaded or colored background or lines of minor thickness. For details, see chapter "Antialiasing" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". 15.1.9 Papyrus Client Document Creation (Canvas) l Generate and view Word document With the new Generate Word and Generate and view Word buttons in the Generation toolbar users can generate a Word document, view it and save it in the file system. For more details, see chapter ""Save as Word document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)"". l New Antialiasing button The new Antialiasing button in the View toolbar helps to correct display inaccuracies that may occur with neighboring areas with shaded or colored background or lines of minor thickness. For details, see chapter "Antialiasing" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". l Double underline words only A new button in the Font toolbar enables users to double underline only the selected words, but not the spaces. For more details, see chapter "Font toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Format list numbering Users can change the numbering format in a list without making changes to the text in the list. For example, apply a different font color or font size for the numbering. For more details, see chapter "Defining lists" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". 15.1.10 Papyrus Designer, Papyrus DocEXEC 15.1.10.1 Information relevant for administrators l Parameter for changing the order of concatenated index and resource group sections INDEXATFIRST allows to change the order of concatenated BDI/EDI and BRG/ERG entries in a generated AFPDS. For more details, see "DEINDEXATFIRST / INDEXATFIRST" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". getstartede V7.6 SP3 190/389 Appendix: main updates in V7.2 15.1.10.2 Information relevant for DOCDEF developers l Microsoft Word document output (*.docx) from DocEXEC Apart from AFPDS, PDF and HTML format, Papyrus DocEXEC is now able to create Microsoft Word documents (*.docx) as direct output format by means of the DEFINEWORDOUTPUT command. Similar to PDF, this output type can be triggered by SELECTOUTPUT. With Papyrus DocEXEC main profile parameter FORCEWORD and DEFORCEWORD, the Word document format can be set as default output format. With Papyrus Designer option "Tools | Generate Word" test documents in Word document format can be created. A use-case the Word output creation is also available. For more details, see "DEFINEWORDOUTPUT command" in "DocEXEC Reference Application Developer Guide (pdedge)", FORCEWORD/DEFORCEWORD, "Creating Microsoft Word output" in "DocEXEC Reference Application Developer Guide (pdedge)" and "Enable DOM output (DEUSEMODELBASEDOUTPUT) / MODELBASEDOUTPUT)" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l Indexing description enhanced The description of how to create indices was enhanced and illustrated with diagrams. For more details, see "Indexing documents" in "DocEXEC Reference Application Developer Guide (pdedge)". l Building frames around paragraphs in TEXT command The _FRAME subcontrol of the TEXT command allows to build a frame lines around paragraphs. You can define lines to the top, bottom, left or right border of a single paragraph and lines between a group of paragraphs. For each line type you can specify individual color and thickness. For more details, see "_FRAME" in "DocEXEC Reference Application Developer Guide (pdedge)". l CLOSE command integration with Papyrus Depot The CLOSE command was considerably enhanced for integrating output generation with the Papyrus Depot. The command's definition dialog allows now to specify a particular Papyrus Depot, the index object which should be linked to the created output, which index names and values should be used on the index object, and several further archiving and storing options. For more details, see chapter "CLOSE Command" in "DocEXEC Reference Application Developer Guide (pdedge)". l Text column synchronization after page break OUTLINE, TABLE and PRINTLINE command support an option - SYNCHRONIZE - which helps to avoid unwanted situations at page breaks, when printing text in two or more columns. This option set has an effect on sublevel objects if the sublevel objects print column-like text and one of the sublevel commands triggers a page break. In certain situations the starting position of the sublevel commands after the page break can be shifted in vertical direction. With SYNCHRONIZE the output commands start always at the same vertical offset. For more details, see chapter "OUTLINE, TABLE, PRINTLINE synchronized" in "DocEXEC Reference Application Developer Guide (pdedge)". l TEXTSTYLE command allows to specify a class name for a style to be used in CSS Style definitions allow now to specify a class name for each style, which will be used for the translation of the style into a CSS representation when creating HTML output. For more details, see chapter "TEXTSTYLE command" in "DocEXEC Reference Application Developer Guide (pdedge)". l Suppress VARPROMPT and TEXTPROMPT for PDF form VARPROMPT and the TEXTPROMPT commands can now be suppressed for PDF form by means of an extra flag. Before it was only possible to create PDF prompts from all or none of the defined commands. Now individual commands can be selected. For more details, see "VARPROMPT command" in "DocEXEC Reference Application Developer Guide (pdedge)" and "TEXTPROMPT command" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 191/389 Appendix: main updates in V7.2 l Changing Z axis position of page objects (layering) Function _SET_ZORDER allows to change the layer of page objects (text, images, charts, barcode, aso.). The term "layer" refers to a page object's position on the Z axis. Layering changes are, for example, required when you want to place an overlay on the background of an imported AFP page. For more details, see chapter "_SET_ZORDER" in "DocEXEC Reference Application Developer Guide (pdedge)". 15.1.11 Papyrus Designer FixForm and Server FixForm l Language Classification Two new text processors find Languages and classify languages have been implemented for language classification. They can be used to determine the language or languages the text of document or page contains. For general information about language classification, see chapter "Language classification" in "Designer Capture Application Developer Guide (pcddge)". For a description of the new text processors, see "Find languages" in "Designer Capture Application Developer Guide (pcddge)" and "Classify languages" in "Designer Capture Application Developer Guide (pcddge)". 15.1.12 Papyrus Word to Correspondence 15.1.13 Papyrus Objects (WebControl/WebRepository) 15.1.13.1 Papyrus Objects System l Full-Text Search (FTS) FTS allows users to search for text contained in binary as well as string attributes. Full text search is only available for the 64-bit version, which is not part of the standard delivery but only available on demand. For details, see "Full Text Search (FTS) - Make objects' textual content searchable" in "WebRepository Application Developer Guide (pwride)". l Switch off issuing performance warnings The new Boolean attribute Switch off issuing performance warnings (IssuePerformanceWarningOff) of class AGENT allows to suppress user account reload messages. For details, see section "Suppress Issuing Performance Warnings for Agent" of chapter "Role of the agent" in "WebRepository Application Developer Guide (pwride)". 15.1.13.2 Papyrus Depot l Enable Automatic Indexing In the Depot search settings the administrator predefines parameters for Depot search workplace. The additional attribute Enable automatic indexing was provided. For more details, see chapter "Preconfigure the workplace in Settings Explorer" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". 15.1.13.3 Papyrus Adapters and Typemanagers l EWS Adapter EWS adapter/receiver is used for the direct retrieval of e-mails from a specified e-mail account on an MS Exchange Server with Exchange Web Services support. For more details, see chapter "EWS adapter" in "Papyrus E-Mail - Solutions Architecture and Administrator Guide (pemailsole)". getstartede V7.6 SP3 192/389 Appendix: main updates in V7.2 l Switch off issuing performance warnings The new Boolean attribute Switch off issuing performance warnings (IssuePerformanceWarningOff) of class ADAPTER allows to suppress user account reload messages. For details, see section "Suppress Issuing Performance Warnings for Adapter" of chapter"Role of the adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". 15.1.13.4 Papyrus Query Language (PQL) l $hexEncode() & $hexDecode() These functions interconvert between a memory buffer or raw data string and a hexadecimal string representing the data. For more details, see "$hexEncode() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" and "$hexDecode() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $htmlEncode() & $htmlDecode() These functions interconvert between HTML special characters and their UTF-8 equivalents. For more details, see "$htmlencode() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" and "$htmldecode() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $makeVirtual() This function converts an object-based PQL set to a synthetic set that does not provide backdoor access to objects. For details, see "$makeVirtual() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Logging functions These functions are used to insert and modify log entries in applications that customize the application event logging functionality. For details, see "$addLogRecord() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$log() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" and "$logActive() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $currentMethDef This system variable provides information concerning the currently executing method. For details, see "Current status variables in WebRepository Application Developer Guide (pwride)". l KeyFields parameter of mathematical PQL set functions This parameter enables you to specify which fields should be used to compare the records of object-based PQL sets. For details, see "Perform mathematical set operations on non-ID fields in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $detectCodepage() This function enables you to export the contents of a memory buffer or binary attribute without knowing the codepage of its contents beforehand. For details, see "$detectCodepage() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $pqlCreateCondition() & $pqlParseCondition() The latter function constructs an execution tree from a string containing a PQL conditional expression; the former function does the reverse. For details, see "$pqlCreateCondition() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" and "$pqlParseCondition() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". getstartede V7.6 SP3 193/389 Appendix: main updates in V7.2 l SSL Digest functions These new functions replace those that were previously provided for MD5 digest computation. They enable you to calculate digests using the MD5 algorithm as well as many others. For details, see "Data hashing & digital signature functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". 15.1.13.5 Papyrus EYE Widgets l New parameter: ApplicationParameters This command line parameter and the environment variable ISIS_EYEWDG_ApplicationParameters allow to pass parameters to the EYE widget application. For details, see "/ApplicationParameters = { parameter list }" in "WebRepository and WebControl Installation and Administrator Guide (poinste)" l New location of the QT Resource compiler's source code For details, see "Papyrus EYE Widgets troubleshooting checklist" in "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)" Available with DVD 7.2 SP1 15.1.13.6 Papyrus WebPortal l Automatic Session Selection This feature allows automatic session selection based on the web server a user connects to. For details, see chapter "Automatic session selection based on web server" in "WebPortal Installation and Developer Guide (powpidge)". 15.1.14 Papyrus Server 15.1.14.1 AFP to PDF 15.1.14.2 PDF-in l Practical Examples rearranged and extended There is a new sample showing how to create GOCA vector page segments. For details, see chapter "Create GOCA vector page segments" in "Papyrus PDF-in Reference Guide (ppdfinrge)". 15.1.14.3 SMTP/E-mail l Remove HTML Comment This new parameter allows to remove HTML comment from the HTML body of an e-mail before sending. For details, see chapter "Remove html comment (EmailRemoveHtmlComment)" in "Papyrus E-Mail - Solutions Architecture and Administrator Guide (pemailsole)". 15.1.15 OverView AFP Designer l In case of resizing a text box, hyphenation is supported in overlay mode When you generate overlays, spellchecking is supported. In addition, when you resize a text box, also hyphenation is supported for the text inside the box. For more details, see chapter "OverView AFP Designer" in "Spellchecking and Hyphenation Installation Guide (spellhyphe)". getstartede V7.6 SP3 194/389 Appendix: main updates in V7.2 15.1.16 Papyrus best practices 15.1.16.1 Sample applications l New technical DOCDEF sample about layering of page objects The sample presents some options for changing the order of page objects like text, images, overlays or charts that are printed on top of each other. By means of a function the layering of such objects can be changed. For more details, see chapter "Layering Sample (SAMPLE_LAYERING)" in "Sample Applications Reference Guide (isasie)". l Enhanced technical DOCDEF sample about image import The sample that presents image import was enhanced. The sample now shows various options how to insert images in DOCDEF applications. The discussed commands include SEGMENT, CREATEOBJECT IOBDLL calling the routines IOBDEFS, IOB_INFO, TIFF_INFO, TIFF_IMPORT and COMMAND, CREATEOBJECT HPGL2(READHPGL) and OVERLAY. Imported image format are page segments, PNG, BMP, JPEG, TIFF and PDF. For more details, see chapter "Image Sample (SAMPLE_IMAGE)" in "Sample Applications Reference Guide (isasie)". 15.2 Updates in SP1 15.2.1 Papyrus Adaptive Case Management Solution 15.2.1.1 Information relevant for administrators and developers 15.2.2 Papyrus Business Correspondence Solution Improvements are provided with this Service Pack and affect the following use cases: l Include (INC) file for Group Building Block If you want to use group building blocks within a document structure this Service Pack is mandatory. l Release Creation using Papyrus EYE Widgets Desktop Buttons for the creation of a release by a release manager are now enabled. l Accessing a Document Layout via Document Edit View The Document Layout modal dialog will now close on exit. 15.2.3 Papyrus Designer, Papyrus DocEXEC l Parameter for changing the order of concatenated index and resource group sections Although already available in prior versions of Papyrus DocEXEC, the INDEXATFIRST parameter is published for the first time with V7.2 SP1. For more details, see "Information relevant for administrators" in "Papyrus Software - Getting Started and News General Information (getstartede)". l Building frames around paragraphs in TEXT command Although already available in prior versions of Papyrus DocEXEC, the TEXT subcontrol _FRAME is published for the first time with V7.2 SP1. For more details, see "15.1.10.2 Information relevant for DOCDEF developers". getstartede V7.6 SP3 195/389 Appendix: main updates in V7.2 15.2.4 Papyrus Objects (WebControl/WebRepository) 15.2.4.1 Papyrus EYE Widgets l New location of the QT Resource compiler's source code For details, see "Papyrus EYE Widgets troubleshooting checklist" in "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)" Available with DVD 7.2 SP1 15.3 Updates in SP2 15.3.1 Papyrus Adaptive Case Management Solution 15.3.2 Papyrus Business Capture l SP2 upgrade mandatory The installation of SP2 is mandatory for Capture Solution applications. l Java Advanced Imaging API (JAI) This Service Pack introduces an improved image handling of HTML and MS-office format document types for Papyrus Capture Solutions, which requires the installation of Java Advanced Imaging API (JAI). For details see, "Installation of Java Advanced Imaging API" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". 15.3.3 Papyrus Business Correspondence Solution Improvements are provided with this Service Pack and affect the following use cases: l Resources not found after import of Frameworks - rebuild of Papyrus Database indexes needed As part of the upgrade process to v7.19 or v7.20 a new index for RC_RESOURCE will be imported via the System Framework. This requires the re-creation of Papyrus Objects database indexes which must be performed by the System Administrator who executes a "Rebuild indexes" operation on the Domain Controller. After an upgrade to SP2 it will be done automatically. l Creation of Variable Group without a Tenant being specified The creation of a Variable Group using an external XML file has been enhanced so that the Tenant no longer has to be specified during the Variable Group creation process via Papyrus Desktop. l Creation of Header and Body columns for Dynamic Table The field for specifying the number of columns for Dynamic Tables stays now available during several iterations. l Indentation feature in Dynamic Table The indentation is now working properly. l Batch runs of documents using layouts This Service Pack is mandatory if your application uses document templates with different layouts in batch. Each set of data from the input data creates a separate document which may use one of these different document templates, which are dynamically switched depending on the input data. l Business User Tester is able to add Comments During the testing of a release the Tester is now able to add comments again. getstartede V7.6 SP3 196/389 Appendix: main updates in V7.2 15.3.4 Papyrus Client Document Creation (Canvas) l Table width calculation improved Tables created by TABLE and COLUMN commands showed unfortunate table/column proportion in certain situations. When both commands TABLE and COLUMN (i.e. each COLUMN in that table) had explicit width definitions and the TABLE width was larger than the sum of all COLUMN width definitions, then the resulting table displayed disproportionate columns: The width of the last column always filled the gap till the defined table width. Now the sum of the COLUMN width definitions dominates a defined table width, which results in a harmonized table/column relation display. l Presentation of indented text in HTML output using text styles improved The depiction of indented text in HTML, where the indented text was created by means of text styles (TEXTSTYLE command) was in certain cases incorrect. In ordered or unordered lists, for example, text indentation was corrupted for the second and all following lines of a list item. Now list items in HTML output have the same indent for the first and all following lines. l Wrong character in alternate text in Hebrew for PDF/UA corrected When alternate text in Hebrew for PDF/UA was created, the last character (in right-to-left text orientation the first character) set was incorrect. With this service pack the right character is set. 15.3.5 Papyrus Designer, Papyrus DocEXEC l Presentation of indented text in HTML output using text styles improved The depiction of indented text in HTML, where the indented text was created by means of text styles (TEXTSTYLE command) was in certain cases incorrect. In ordered or unordered lists, for example, text indentation was corrupted for the second and all following lines of a list item. Now list items in HTML output have the same indent for the first and all following lines. l Incorrect renaming of resources at AFP import AFP import (by AFPIMORT command) can be defined in a way that the AFP is imported with or without resources. When the AFP import included resources (Use embedded resources ticked), Papyrus DocEXEC renamed imported resources even if they were identical with resources that were already present through an earlier import. Now Papyrus DocEXEC only imports resources that are not yet present and prevents that identical resources will be imported twice. l Table width calculation improved Tables created by TABLE and COLUMN commands showed unfortunate table/column proportion in certain situations. When both commands TABLE and COLUMN (i.e. each COLUMN in that table) had explicit width definitions and the TABLE width was larger than the sum of all COLUMN width definitions, then the resulting table displayed disproportionate columns: The width of the last column always filled the gap till the defined table width. Now the sum of the COLUMN width definitions dominates a defined table width, which results in a harmonized table/column relation display. l Wrong character in alternate text in Hebrew for PDF/UA corrected When alternate text in Hebrew for PDF/UA was created, the last character (in right-to-left text orientation the first character) set was incorrect. With this service pack the right character is set. 15.3.6 Papyrus Objects (WebControl/WebRepository) 15.3.6.1 Papyrus Objects System l Automatic update of Papyrus Objects Database indexes after Transfer import If a new Papyrus Objects database index definition for a certain class is imported in the context of Transfer Files, it will now trigger automatically the recreation of database indexes. Before "Rebuild index" had to be called manually on the Domain Controller's Index Collection. getstartede V7.6 SP3 197/389 Appendix: main updates in V7.2 l Resources not found after import of Frameworks - rebuild of Papyrus Database indexes needed As part of the upgrade process to v7.19 or v7.20 a new index for RC_RESOURCE will be imported via the System Framework. This requires the re-creation of Papyrus Objects database indexes which must be performed by the System Administrator who executes a "Rebuild indexes" operation on the Domain Controller. After an upgrade to SP2 it will be done automatically. getstartede V7.6 SP3 198/389 Appendix: main updates in V7.1 16 Appendix: main updates in V7.1 If you upgrade from an earlier version to the newest version, use the appendix to see a history of all changes that have accumulated. Note that the cross-references in the appendix refer to chapters in documents of the same version. This means that some of the History of Changes entries in the appendix may include cross-references to chapters that do not exist anymore in the newest version of the document or whose information was updated in the meantime. If you are in such a case interested in the details you will need to access the documents of exactly that version. 16.1 Main updates in V7.1 SP9 16.1.1 General changes This DVD includes Papyrus products in release level V7.1 SP9. 16.1.1.1 New documents Papyrus Filesystem Synchronization Framework Developer and Administrator Guide This new document describes structure, functionality and usage of the new Filesystem synchronization framework which allows to import files and directories from file system into Papyrus WebRepository. Imported directories and files are automatically kept in sync with their originals in file system and can also be shared with other nodes and users. For details, see "Filesystem Synchronization Framework Developer and Administrator Guide (pofsfwdage)". Papyrus Monitoring, Analyzing, Troubleshooting and Tuning Guide This new document is addressed to Papyrus Objects system administrators as well as to application developers to learn about monitoring and analyses techniques of a Papyrus Objects Domain. The core component for that is the Papyrus Application and Performance Analyzer (APA). Since each organization has individual requirements, this document explains how the default setup can be customized in order to meet the organization's requirements best. For details, see "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)". Capture Solution Tutorial The new Capture tutorial shows how to instantiate and configure a ready-to-use sample Capture Solution from Library, provides interesting insights in development tasks related to classification definition and extraction definition and presents the most important features of the Capture user interfaces "Capture Workplace" and "Capture Administration Workplace". For details see "Capture Solution Tutorial Guide (popcftut)". Papyrus Server - AFP to Text Reference Guide This new document describes Papyrus Server AFP to Text and explains how to convert an AFP stream to an editable text file. The converted text stream is saved as Unicode (UTF-8) into a text file if run outside Papyrus Objects, or as a content of an ASCII class instance if run in Papyrus Objects. For details, see "Papyrus Server - AFP to Text Reference Guide (psetxtrge)". Papyrus Server - AFP to Thumbnail Reference Guide This new document describes Papyrus Server AFP to Thumbnail and explains how to covert AFPs into images that cannot exceed 70% of the original image dimensions. One image per page is generated, and the image formats PNG, JPG, GIF and TIF are supported. For details, see "Papyrus Server - AFP to Thumbnail Reference Guide (psetnrge)". Smart Document Application Design Architecture Guide This new document provides general best practice guidelines about the integration and connection of external business applications like SAP, Archive systems, etc. with the Papyrus platform as recommended by ISIS Papyrus. For details, see "Output Management Applications Architecture Guide (pomarcge)". getstartede V7.6 SP3 199/389 Appendix: main updates in V7.1 Best Practices - Connect and Integrate with Papyrus A new document that addresses Document Designers, System Architects, Application Analysts and Application Developers who plan to utilize the capabilities of the Papyrus Document Management system. It provides an overview of the Papyrus Document Solutions and its related products. For details, see "Papyrus Best Practices Data Formats and Integration Solutions with Papyrus (bpintegrate)". HTML Document Applications Developer Guide HyperText Markup Language, abbreviated and more commonly known as HTML, is used to create web pages and in an ever increasing amount e-mails. This document provides an overview of the solutions that ISIS Papyrus offers in this context. It demonstrates the possibilities of converting existing HTML files to DocFormat and shows how HTML can be generated with Papyrus products. Use cases range from a pure conversion of an AFP document to the generation of JSON files and their integration into existing projects to produce individualized responsive web pages. For details, see "HTML Document Applications Developer Guide (phtmldadge)". The readme file cafp_eng.txt, which describes the CAFPDS utility for z/OS, has been integrated in the "Codepage and Cross Platform Considerations General Information (cdpgie)". The text file was removed from \document\general. 16.1.1.2 Discontinued documents AFP Designer AS-400 Support Application Developer Guide This document is discontinued and will not be delivered anymore. Its content was included in the document "AFP Designer Application Developer Guide (oaddge)". Design and Tuning of Papyrus WebRepository Applications Developer and Administrator Guide This document is discontinued and will not be delivered anymore. Its content was included in the new document "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)". Papyrus DocEXEC and Document Designer Tips and Notes This document is discontinued and will not be delivered anymore. Its content was included in the "DocEXEC Reference Application Developer Guide (pdedge)" and the "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 16.1.1.3 New platform codes A new platform code for z/OS native will be introduced in V7.2 to clearly distinguish between z/OS Unix and z/OS native: u3/u6 - z/OS Unix 32 and 64 Bit m3/m6 - z/OS native 32 and 64 Bit Before, the platform code mu was used for both z/OS Unix and z/OS native. The new platform code will be introduced in two phases: l Phase 1: version V7.1 SP9 since DVD V7.1 SP9 2016-10-31 l Phase 2: version V7.2 getstartede V7.6 SP3 200/389 Appendix: main updates in V7.1 Phase1: version V7.1 SP9 since DVD V7.1 SP9 2016-10-31 The product directories and products delivered in version V7.1 SP9 since DVD V7.1 SP9 2016-10-31 still use the old platform code mu. However, in anticipation of the new platform codes, all log file entries already show the new platform code with the old one in brackets. Examples: PSEMFARC/mainthread ... PPCS8040L ... Version V7.1 SP9/m3(mu) of '2016-08-08 (build:7.19.0.16320) pocmuknl/mainthread ... PPCS8040L ...Version V7.1 SP9/u3(mu) of '2016-08-08 (build:7.19.0.16320) Phase 2: version V7.2 The product directories and products delivered in V7.2 use the new platform codes: u for z/OS Unix and m for z/OS native. All log file entries show only the new platform code. Examples: PSEM3FARC/mainthread ... PPCS8040L ... Version V7.2/m3 of '2016-08-08 (build:7.20.0.16320) pocu3knl/mainthread ... PPCS8040L ...Version V7.2/u3 of '2016-08-08 (build:7.20.0.16320) 16.1.2 ISIS Papyrus Product Authorization Service l New chapter available about Papyrus in the cloud A new chapter describes how to use Papyrus products in cloud solutions and explains the installation, system requirements and product authorization for this scenario. For more details, see chapter "Papyrus in the cloud" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP9 2017-10-31 l Disaster Recovery IPAS with IPASaaS-Protection available Disaster Recovery IPAS is supported by IPAS as a Service - Protection, which requires an IPASaaS-Protection KeyFile and a related KeySet (LIC) file. For more details, see chapter "Backup (Quota) IPAS with IPASaaS-Protection" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP9 2017-03-10 l Backup (Quota) IPAS with IPASaaS-Protection available Backup (Quota) IPAS is supported by IPAS as a Service - Protection, which requires an IPASaaS-Protection KeyFile and a related KeySet (LIC) file. For more details, see chapter "Disaster recovery IPAS with IPASaaS-Protection" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP9 2017-03-10 l New sample script available for starting IPAS automatically on Linux A sample start script delivered on the Papyrus Software DVD can be adapted to your needs and used to automatically start the IPAS as a daemon on system start. For more details, see chapter "Starting IPAS automatically on Linux" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP9 2016-10-31 getstartede V7.6 SP3 201/389 Appendix: main updates in V7.1 l New authorization mechanism for the IPAS available: IPAS as a Service - Protection IPAS as a Service - Protection (IPASaaS-Protection) is an operation mode where the IPAS is installed at the customer's site and authorized by a service operated by ISIS Papyrus. For more details, see chapter "Installing IPAS as a Service - Protection (IPASaaS-Protection)" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP9 2016-10-31 16.1.3 Papyrus Adaptive Case Management Solution 16.1.4 Papyrus Automated Document Factory Solution l Depot Search Workplace A completely reworked depot search workplace is available. It offers even more features and is easier to set up. This workplace uses EYE Widgets technology thus providing the business user with a familiar graphical interface to comfortably query depots. It replaces the Depot search tab in ADF workplaces and is available via a workplace switcher. For details, see "Depot search workplace" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)" and "ADF depot search" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Available since DVD V7.1 SP9 2017-10-31 l Staggered Send - Packetise Sending many e-mails in a very short interval might result in a bad sending reputation with big e-mail providers. This leads to a higher likelihood of your messages being marked as spam or not delivered to the recipient at all. In order to prevent this factor from harming your e-mail sending the Packetise Queue was introduced. It builds packets (piles) of e-mails and sends them at definable intervals thus throttling and delaying the process. By setting the packet size to 1 and defining the interval you can effectively control the sending rate. For details, see chapter "Staggered send - packetise" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Available since DVD V7.1 SP9 2017-10-31 l ADF and PED Tutorial In this tutorial an interested user (typically a system administrator) learns to do setup, configuration and even simple development tasks by executing detailed step-by-step instructions. The curriculum starts with creating the necessary Papyrus Objects infrastructure, continues with migrating an existing DocDef application, demonstrating how to use existing rules and build new ones to finally give a quick start on building basic reporting. For details, see chapter "Tutorial" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Available since DVD V7.1 SP9 2017-06-30 l Enhanced PED Navigation Each object within Print and E-Delivery collection now holds the methods GetCollection() and GetCollectionRoot(). In order to use these methods instances which were created with an older framework version need to be updated by using check objects. For details, see chapters "Enhanced PED navigation" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)", "Upgrading" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)" and "CheckObjects" in "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)". Available since DVD V7.1 SP9 2017-03-10 getstartede V7.6 SP3 202/389 Appendix: main updates in V7.1 l New PED PQL collection This collection contains scripts which ease the testing and cleaning-up of a PED solution. For details, see chapter "PED collections" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Available since DVD V7.1 SP9 2017-03-10 l Additional features for Bundled Jobs Jobs which were not bundled yet, but are in the queue to be spooled, can be visualized with the "View Jobs" button. A bundle-job can be retriggered with a button. For details, see chapter "Administration of scheduled actions" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Available since DVD V7.1 SP9 2017-03-10 l PED environment collection In some cases it is advisable to have a single Print and E-Delivery Collection which is used by multiple environments (ADF Setups) to reduce the maintenance effort. A typical scenario is the sharing of a single PED Collection by the Development, Test and Production environment. For details, see chapter "PED environment collection setup" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Available since DVD V7.1 SP9 2016-10-31 l PED language collection With the help of this collection it is possible to send a personalized cover letter in a different language than the main document even if you have not planned for that possibility during the generation of the original document. This is achieved by rules that select appropriate HTML templates. For details, see chapter "EmailHyperlink" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Available since DVD V7.1 SP9 2016-10-31 l ADF/PED Setup script improved A new PQL template is available - with attributes for configuration arranged on separate tabs - that eases the installation and configuration of the ADF and PED solutions. For details, see chapter "Scripted setup" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". Available since DVD V7.1 SP9 2016-10-31 l Documentation has been reorganized All aspects dealing with Print and E-Delivery have been combined into a single section after the Automated Document Factory description. A chapter explaining the inner workings of PED has been added. For details, see chapter "Outbound channel handling via PED PQL methods" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)". l Depot Search Workplace A completely reworked depot search workplace is available. It offers even more features and is easier to set up. This workplace uses Eye Widgets technology thus providing the business user with a familiar graphical interface to comfortably query depots. It replaces the Depot search tab in ADF workplaces and is available via a workplace switcher. For details, see "Depot search workplace" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)" and "Depot search" in "". Available since DVD V7.1 SP9 2017-10-31 l Eye Widgets GUI improvements Eye Widgets GUI and its terms have been improved to cater for the needs of business users. The manual has been updated to reflect these changes. The GUI is also available in German, Italian and French. Available since DVD V7.1 SP9 2016-10-31 getstartede V7.6 SP3 203/389 Appendix: main updates in V7.1 16.1.5 Papyrus Business Correspondence Solution l Creation and use of a transparent Overlay (OVL) in a Page Layout For more details, see chapter "Creating and using a watermark in a page layout" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Extending Execution Points for FormatGroup Definitions Inclusion of Begin PRINTFOOTER and End PRINTFOOTER For more details, see chapter "Extend document template using CF_DC_EXECUTE_EP object to extend formatgroup definitions" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-10-31 l Consolidation of upgrade scripts Fewer scripts are required to be executed for the upgrade of a Business Correspondence Solution For more details, see chapter "Installation and update finalization scripts for all frameworks" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Support for previous Service Packs (SP) Support for 2D barcodes in all service packs provided For more details, see chapter "Configuring correspondence compatibility settings support for previous releases" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-10-31 l Maintaining a consistent naming between AFP and PDF When the clerk renames a document instance the CfTask, the DOCUMENT Material and document content objects are also renamed. For more details, see chapter "Generating PDF and AFP output" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-10-31 l Search task location configurable Search tasks for clerks and supervisors make location to store the search tasks configurable. This is mandatory and must be set. For more details, see chapter "Configure business user workplace search location for document instance creation" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-10-31 l Identification of Language Variant names For a text or a image variant the CF3_1_GET_MODULES_RESOURCES module is used to identify those related language variants (IMP) For more details, see chapter "Identification of a building block name" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-10-31 l Expose attribute settings for Application Output Format Parameters for APPLICATION-INPUT-FORMAT Command can be configured using CF Scope configuration. For more details, see chapter "Configure control values for compressed AFP generation" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-10-31 l Print and E-Delivery integration Detailed instructions are provided on how to integrate a Print and E-Delivery (PED) with a Business Correspondence Solution. For more details, see chapter "Integration of Print and E-Delivery (PED) output options with a Papyrus Business Correspondence Solution" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 204/389 Appendix: main updates in V7.1 l New attribute on CF scope workplace allows clerks to delete documents from other users If Allow document cleanup is selected, clerks/supervisors can delete document instances created by other users. For more details, see chapter "Remove a document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Business Correspondence Tutorial In this tutorial, business users can follow detailed step-by-step instructions to assemble a document template and a wizard template with building blocks and use the document templates for the creation of an actual document. For more details, see chapter "Tutorial: insurance contract document" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-06-30 l "Default release" field can be defined as read-only The Default release field on the Correspondence Management workplace can be defined as read-only so that template administrators cannot change the default release. For more details, see chapter "Define default release field as read-only" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-06-30 l Define Business User "Inline Prompting" behavior for Check boxes Configurable "Inline Prompting" has been extended to support check boxes. For more details, see chapter "Configure Inline Prompting for Check boxes" in "". Available since DVD V7.1 SP9 2017-06-30 l KeepLanguageForPreview setting extended to support editing The current language, system language and keep language attributes also support editing. For more details, see chapter "Configure Papyrus Business Designer workplace language settings" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-06-30 l Creating and using a Canvas Toolbar (CTB) object CTB is a resource object that allows the system user to make changes to the Papyrus Canvas Toolbar used by business users. For more details, see chapter "Structure and working with Canvas Toolbar (CTB)" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Generating Documents with Assisting Technology for Visually Impaired Users (PDF/UA) PDF documents can be generated in a way to support assisting technology for visually impaired users. For more details, see chapter "Configuring documents with assisting technology for visually impaired users (PDF/UA)" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-06-30 l Data Reading and Data Setting Chapter available that covers how to integrate data reading routines and configuration settings within the Correspondence Framework For more details, see chapter "Create data reading routines and data types" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-06-30 l Client Correspondence HTML - Redirect after document has finished on external call After a document has finished, it can be redirected. For more details, see chapter "Redirect business user to an HTML page" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 getstartede V7.6 SP3 205/389 Appendix: main updates in V7.1 l Using Resource Groups in Papyrus EYE Widgets Defining and using resource groups in Papyrus EYE Widgets. For more details, see chapter "Create a resource group for a organizational structure" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l XML data mapping to CF variables XML tags can be mapped to differently named variables using settings For more details, see chapter "How to map input data to variables of a data variable group using data reading settings" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l DataRead Routine for PQLSets Accessing PQL sets using data read routine. For more details, see chapter "Reading data from a PQLSET and memory attributes" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Handling upgrade with CF Scope Configuration Explains what to do with existing versioned CF Scope Configuration objects after an upgrade. For more details, see chapter "Scope Setting Definition Changes" in "". Available since DVD V7.1 SP9 2017-06-30 l Configuration of Content and Design tabs for a Business User Details are provided on how to extend the search and selection criteria of Content and Design tabs. For more details, see chapter "Configuration of Content and Design tabs for a business user" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Instances of Document Supervisor need an ACMUser to run wizards The business user supervisor must be extended with the ACMUser object allowing ACM based wizards to be run. For more details, see chapter "Extend business user to run ACM based wizards" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Correspondence color definition to support CMYK values in percentage CMYK can be represented in a percentage value using color definition settings. For more details, see chapter "Define CMYK color in percentage values" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l External invocation support for Papyrus EYE Widgets Clerk using a browser can invoke operations using Papyrus EYE Widgets. For more details, see chapter "Business user call of document template and Wizard Case via a URL" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Reading Data from a PQLSet and Memory Attributes Configuration and development amendments to allow data to be read from a PQLSet. For more details, see chapter "Reading data from a PQLSET and memory attributes" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Enable and disable fully qualified names in XML Read variable names Data can be processed with or without a fully qualified name. For more details, see chapter "Enable and disable fully qualified names for input data" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 getstartede V7.6 SP3 206/389 Appendix: main updates in V7.1 l How to use decimal and thousand separators in CF for input and output Using scope settings we can define different character separators. For more details, see chapter "Use of decimal separators for different languages" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l How to switch the language in documents depending on input data Details the mechanism to create a document instance that matches the incoming language. For more details, see chapter "Use input data to control target language for the document instance" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Logging of user actions while using a change management process Use of logs to determine what actions have been performed on items. For more details, see chapter "Logging of business user actions" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Configuration of restricted promotion for a change management release Restrict promotion of a release by verifying the status of elements. For more details, see chapter "Define Restricted Promotion" in "". Available since DVD V7.1 SP9 2017-03-10 l CF scope configuration setting not versioned anymore The CF scope configuration is no longer versioned and does not require a project. For more details, see chapter "Correspondence Framework configuration settings" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l For saving a text input field as text file, a path can be predefined The path for saving the content of a text input field as text file in the file system can be predefined by the system administrator. The path is displayed in the dialog if a business user clicks Save text as | Save as text file. Moreover, the system administrator can define whether any changes to the path made by the business user are saved and shown the next time the dialog is opened. For more details, see chapter "Define a path for saving user input fields as text file" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2017-03-10 l Extending FormatGroup Definition commands Instructions on how to extend FormatGroup Definition commands are available. For more details, see chapter "Extend document template using CF_DC_EXECUTE_EP object to extend formatgroup definitions" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Assigning a Resource Group to a Tenant Updating the Tenant Collection to use resources from a Resource Group. For more details, see chapter "Create a resource group for a organizational structure" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Replace of Business User Workplaces during upgrade process Instructions on how to replace the business user workplaces are available. For more details, see chapter "Updating business user Papyrus EYE Widget workplace" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Construction of PDF/A functionality Implementation of PDF/A to support the creation of PDF documents. For more details, see chapter "Identify processing requirements for different PDF/A document types" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 getstartede V7.6 SP3 207/389 Appendix: main updates in V7.1 l Define Roles and Policy for a Department Updated the definition for the separation by Role and Policy. For more details, see chapter "Define roles and policy for a department" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Allocation Group informative message for Release Manager Informative messages generated informing the Release Manager that they should create an Allocation Group. For more details, see chapter "Assignment of Business Users to an Resource Allocation Group" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Redirect HTML Client Business User on Document Done Business User completes task and is redirected to a HTML page For more details, see chapter "Redirect business user to an HTML page" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Modify the HTML Client behaviour when a Clerk cancels a Wizard When a clerk cancels a Wizard operation they are returned to the Inbox and not edit document this only applies to the HTML Client For more details, see chapter "Configure cancel operation during wizard creation" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Show additional attributes in Papyrus EYE Widgets Desktop Attributes can be added to the Standard and Expert tabs for use by the template administrator For more details, see chapter "Create and expose attributes to business users" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Informative message to the Business user using HTML Client Events created from the canvas toolbar by the business user can be used to display informative messages For more details, see chapter "HTML client informative message for business user" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Variable groups can be displayed in a find-as-you-type list for selection in text variants When configured the template administrator can use a find-as-you-type list instead of check boxes to select variable groups for a text variant. For more details, see chapter "Change the variable with group control in Papyrus business designer" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Navigate with Breadcrumbs in Wizards Bread crumb navigation enables the clerk to traverse the execution steps of a wizard. For more details, see chapter "Configure breadcrumb navigation settings for wizard operations" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Enable building Blocks in the Administrator main view Building block types can be added to the business user view. For more details, see chapter "Configure available building block types for business users" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 getstartede V7.6 SP3 208/389 Appendix: main updates in V7.1 l Extending View and Print operations in the Papyrus Canvas Actions invoked by the business user are interpreted by correspondence execution points to extend the correspondence framework. For more details, see chapter "Define functionality for business User formatting and print operations" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Creating Library folders in Business User interface The template administrator is able to create Library folders that are used to hold document template references. For more details, see chapter "Create departmental structures using shared libraries" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Configuring the different Barcode types Provides an overview of the how to configure the DATAM barcode type using attribute values. For more details, see chapter "Configure barcode using attribute values" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". Available since DVD V7.1 SP9 2016-10-31 l Sticker comment content save configuration Saving of comments entered into stickers is configurable. For more details, see chapter "Save configuration for sticker comment" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Document instance name read only Using a scope configuration we can prevent business users from renaming document instances. For more details, see chapter "Prevent document instance being renamed" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Provide identifiers for comments when used in stickers Comments that are added into stickers can be configured to contain unique identifiers that are visible in the outgoing document. For more details, see chapter "Configure stickers for business users" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Using a SCBS Font for the Check box Template administrators can define a Checkbox to use a Single byte character set (SCBS). For more details, see chapter "Define font and text font for a check box building block" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Change Management - Cancel private version while being in group development The instantiation of business users results in a private default ACMProject being created. If the business organization is only using the Release (Simple) template the business user's default project must be referenced within a group development ACMProjectManagement project. For details, see chapter "Select default project type for business users using ACM release template" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Enable separate tabs for PDF and AFP document generation and view For more details, see chapter "Generating PDF and AFP output" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Disable building blocks, document and wizard templates that should no longer be used in the creation of elements For more details, see chapter "Allow Handling of Disabled Building Block types" in "". getstartede V7.6 SP3 209/389 Appendix: main updates in V7.1 l Retain voting rights made by the tester For more details, see chapter "Business user types for Acm Change Management Extended (Sample)" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Language feature available in Forms Designer Individual object translations can be enabled for the form element attributes Tooltip and Placeholder Text. For more details, see chapter "Configure translation dialog for document and building block types" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Customer data object in a document The clerk and supervisor are able to use data objects within a document to store content. For more details, see chapter "Creation and configuration of a customer data object" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Enhanced Table properties dialog Business users working with tables in the Papyrus Client Canvas plugin can take advantage of improved handling in the Table properties dialog. For example, defining borders and shading for the whole table and for individual cells is now more intuitive. For more details, see chapter "Inserting tables" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-12-07 l New attributes available for continuing lists and styles across text positioning elements Template administrators working with document templates, layouts and groups can continue numbering and styles across text positioning elements by defining a style connection key. For more details, see chapter "Connecting numbering and styles across text positioning elements" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l New attribute "Use edit formats" available for TextComposition Template administrators using a TextComposition building block in a document template can select the Use edit formats check box to have the user input shown in the format that is defined on the variable variant itself. For more details, see chapter "Use edit formats" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Check boxes available in document structure to indicate use of positioning elements Template administrators working with document templates, layouts and groups now see a check box next to each positioning element in the document structure. If the check box is selected, its use in the document is enabled; if the check box is deselected, its use is disabled. The check boxes in the document tree reflect the status of the Use check box on the Standard tab and can be deselected/selected directly in the tree to quickly change the usage status. For more details, see chapter "Disable the use of a positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l In a multi-part document, all variables used in the documents and their building blocks and from selected variable groups are available for rules and simulation Template administrators editing a multi-part document have all variables available that are used in the documents and their building blocks as well as unused variables of selected variable groups. For more details, see chapter "Use variables in a multi-part document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 getstartede V7.6 SP3 210/389 Appendix: main updates in V7.1 l New formatting attribute available for dynamic tables Template administrators can enter a value into the Snap range (vertical lines) field in the dynamic table editor to have the table widths automatically aligned. For more details, see chapter "Automatically align table widths" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Improvements in the variable group editor Template administrators can use the improved UI of the variable group editor, for example: Description fields with more space to enter content; intuitive variant input fields; Date/Time picker for variables of Date type. For more details, see chapter "Working with variable groups" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Read-only mode for variable groups available Template administrators can open variable groups in read-only mode, for example to view active building blocks without creating a new version. For more details, see chapter "Viewing building blocks in read-only mode" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Options available to define frame corner rounding for "Box" design building block Template administrators can define frame corner rounding options for the Box design building block used in a document, layout or group. For more details, see chapter "Insert a box into a document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Repeat attribute available on group positioning element only For template administrators, the Repeat field is available only on the group positioning element of document templates, but not in the group building block editor anymore. For more details, see chapter "Repeat a group" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Searching for variables is possible with Advanced search If the variable group of a variable is not known, template administrators can now search directly for variables using the Advanced search. For more details, see chapter "Find variables with advanced search" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Document language can be overruled for text positioning elements When editing a document template, template administrators can overrule the document language for text positioning elements, displaying a variant in a language that is different than the language set for the whole document. For more details, see chapter "Overrule the document language for a text positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Clerks/supervisors can delete documents created by other users If defined by the system administrator, clerks and supervisors can remove documents that were created by other users. For more details, see chapter "Remove a document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 getstartede V7.6 SP3 211/389 Appendix: main updates in V7.1 l Unused variables can be made available Template administrators can select variable groups in document templates, groups, and layouts to make also those variables available for use in conditions and Assign building blocks that are not already used within the document. For more details, see chapter "Use variables in a document template" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Resources of image variants can be renamed When editing an image variant, template administrators can rename image resources created by themselves that are in development and not used. For more details, see chapter "Rename a resource of an image variant" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Resources of image variants can be deleted When editing an image variant and if configured by the system administrator, template administrators can delete image resources created by themselves that are in development and not used. For more details, see chapter "Delete an image resource via the image variant editor" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l Image variant can be reset When editing an image variant, template administrators can reset the image variant, thereby cleaning the filename and image type attribute. For more details, see chapter "Remove a resource from an image variant" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-10-31 l "Use Edit Formats" attribute of "Assign" building block set to true by default The Use Edit Formats attribute of the Assign design building block is set to true by default. Before, it was set to false. This does not influence existing documents because the Assign building block is duplicated on usage. However, it must be considered on new usage. For more details, see chapter "Assign a value to a variable" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-06-30 l Business Correspondence Tutorial available A tutorial is available where business users can follow detailed step-by-step instructions to assemble a document template and a wizard template with building blocks and use the document templates for the creation of an actual document. For more details, see chapter "Tutorial: insurance contract document" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l If defined, the default release cannot be changed Depending on the configuration, template administrator may not be able to select a different release as the default release because the Default release field may be defined as read-only. For more details, see chapter "Define a default release for new building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-06-30 l Check box can be selected inline or in "User input" window Depending on the configuration, clerks can select a check box directly in the text ("inline prompting") or in the User input window. For more details, see chapter "Prompting inline or in user input window" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-06-30 getstartede V7.6 SP3 212/389 Appendix: main updates in V7.1 l A frame can be inserted around a paragraph in a user input field In a user input field, business users can insert a frame around one or two paragraphs and define its color and line width in the Papyrus Client Canvas Plugin. For more details, see chapter "Insert a frame" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-06-30 l Document templates can be created for PDF/UA-compliant documents Template administrators can create PDF/Universal Accessibility-compliant documents by defining alternative texts and a document title and by changing the reading order. For more details, see chapter "Creating PDF/UA-compliant documents" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-06-30 l Field for defining NL Rules is a multi-line element Definition of Natural language rules (NLR) is easier because the field is now a multi-line element and not a single line anymore. For more details, see chapter "Defining conditions with Natural Language Rules (NLR)" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-06-30 l A group building block can be repeated in one document with different data Template administrators can now define that a group is repeated in one and the same document using different variable data. For more details, see chapter "Repeat a group positioning element with different variable data" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-06-30 l Different building block types can be added to a wizard step in a building block action In a wizard step, template administrators can now add not only text building blocks, but also image variants, groups, dynamic tables or chart variants in a building block action. For more details, see chapter "Add a building block action to a wizard step" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-06-30 l Integrated simulation available for multi-part documents Simulation is now available also for multi-part documents. Template administrators can use the Simulation accordion tab in the building block editor to display the simulation area and define simulation data. For more details, see chapter "Simulating documents and building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 l Pencil icon available for editing entries in Overview lists or of bookmark folders Business users can change an entry in an overview list such as the name and description of a building block or the name of a bookmark folder more easily by clicking the pencil icon that is displayed when you point to the entry. For more details, see chapter "Change the name and description in the results list" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 getstartede V7.6 SP3 213/389 Appendix: main updates in V7.1 l Page bar available in the results list of the Administrator main view In the results list, template administrators can define how many records are displayed per page and they can browse the results list by clicking the next and previous buttons of the page bar on the Administrator main view. For more details, see chapter "Browse overview list" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 l Actions such as moving and completing of items as well as finishing stage are handled with asynchronous processing in the background When business users move or complete items or finish the stage of a release, the actions are now processed in an asynchronous way in the background. With a new icon and a dialog that is displayed if clicked on, business users can view the status of the actions started by them. For more details, see chapter "Actions processing in the background" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 l Improvements for Checkbox design building block available When a document administrator inserts the Checkbox building block from the Design tab of the Library area into the document template, several improvements are available (e.g. check box is larger; check box character for the PDF is always taken directly from the PDF object). For more details, see chapter "Inserting a check box into a document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 l The release name of each building block is shown in the search results of the Administrator main view Template administrators can find out to which release a building block by looking at the release name displayed in the Release column of the results list after a simple search. Clicking the release name displays a dialog with a list of all the building blocks in the release. For more details, see chapter "Find out the release of a building block" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 l For a text positioning element, frame line width with float value and frame padding options are available In a document template, group and layout, template administrators can use a float value to define the frame line width as well as configure frame padding options. For more details, see chapter "Add shading and frame to a text positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 l For saving a text input field as text file, a path can be predefined The path for saving the content of a text input field as text file in the file system can be predefined by the system administrator. The path is displayed in the dialog if a business user clicks Save text as | Save as text file. Moreover, the system administrator can define whether any changes to the path made by the business user are saved and shown the next time the dialog is opened. For more details, see chapter "Save text input field as text file" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 l Promotion of a release may require all items to be in Passed status due to restriction defined SIT or UAT test supervisors may find the Promotion button displayed only if all items are in Passed status. This is due to a promotion restriction defined on the user interface for system users. For more details, see chapter "Promotion is prevented by a release restriction" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 getstartede V7.6 SP3 214/389 Appendix: main updates in V7.1 l Breadcrumb trail in wizards shows only user steps A breadcrumb navigation path displayed for clerks running wizards on the Papyrus Desktop/HTML shows only steps requiring data entry from the clerk. For more details, see chapter "Navigate with breadcrumbs in wizards" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2017-03-10 l New icon design on the business user interface The icons for buttons on the business user interface were redesigned in a flat style. Available since DVD V7.1 SP9 2016-10-31 l Accordion elements in building block editors Building block editors provide accordion elements, which can be displayed and hidden as required. For more details, see chapter "Building block editors" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Read-only mode for most building blocks available Template administrators can open text variants, image variants, groups, layouts, dynamic tables, and chart variants in read-only mode, for example to view active building blocks without creating a new version. Read-only mode for document templates has been available since V7.1 SP8. For more details, see chapter "Viewing building blocks in read-only mode" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Search and replace for texts in text building blocks available Template administrators can quickly find every occurrence of a specific word in text building blocks and replace it with a specified text. For more details, see chapter "Searching and replacing text in text building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Simulation is integrated into document template editor Document simulation is not run on a separate tab anymore but it is integrated into the document template editor. Template administrators can use the Simulation accordion tab directly in the editor to display the simulation area and define simulation data. For more details, see chapter "Simulating documents and building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Integrated simulation available in most building block editors Simulation is now available also for text variants, image variants, groups, layouts, dynamic tables, and chart variants. Template administrators can use the Simulation accordion tab in the building block editor to display the simulation area and define simulation data. For more details, see chapter "Simulating documents and building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Popup message if clerks click the DONE button If this is defined by the system administrator, a popup message may be displayed on the Papyrus Desktop/HTML when a clerk clicks the DONE button. For more details, see chapter "Information displayed before you send for sign off" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 getstartede V7.6 SP3 215/389 Appendix: main updates in V7.1 l Display value of form elements can be translated Template administrators can translate display values for wizard form elements. If translation is not activated, translations from the Translation Collection are used. For more details, see chapter "Define a display value for a form element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Breadcrumb trail for wizards available If defined, a breadcrumb navigation path is displayed for clerks running wizards on the Papyrus Desktop/HTML. For more details, see chapter "Navigate with breadcrumbs in wizards" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Locked items can be reassigned to another template administrator Release managers can reassign an item that is locked (i.e. not completed) to another template administrator if they work in group development. For more details, see chapter "Reassign locked items in group development" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Number format of values for X and Y axis can be defined in line chart variants Template administrators can define the number format for values to be displayed on the X and/or Y axis of line chart variants. For more details, see chapter "Define how values are displayed in line charts" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Orientation of X axis can be defined for bar chart variants Template administrators can define the orientation of the x axis for bar chart variants and chart building blocks. For more details, see chapter "Define orientation of X axis for bar charts" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Height, start position and segmentation extraction can be defined in Pie3D chart variants Template administrators can configure the look of the pie with additional options of Pie3D chart variants, such as where the segmentation starts, if the segments are extracted, as well as the height of the pie. For more details, see chapter "Define extraction details for pie3d charts" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l [Ctrl] and [Alt] keys can be pressed with drag&drop of items in the document tree Template administrators and clerks can press the [Ctrl] key for duplicating and [Alt] key for referencing items while dragging them into or within the document tree. For more details, see chapter "Moving, duplicating and referencing building blocks in the document structure" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Variable groups can be displayed in a find-as-you-type list for selection in text variants If this is configured by the system administrator, template administrators can use a find-as-you-type list instead of check boxes to select variable groups for a text variant. For more details, see chapter "Add variables to a text variant" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 getstartede V7.6 SP3 216/389 Appendix: main updates in V7.1 l Margins can be ignored for Barcode building blocks Template administrators can ignore margins in positioning definitions for barcodes in document templates, groups, and layouts. For more details, see chapter "Ignore margins for a barcode" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Cancelling a wizard on Papyrus Desktop/HTML leads to Inbox If clerks execute a wizard on the Papyrus Desktop/HTML, the Inbox is displayed and not the document editor. For more details, see chapter "Document based on wizard" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Optimized support for completion and moving of items For completion (template administrators) and moving (template administrators and release managers) of items, these users have now more opportunities while being guided by safety checks and informative messages. For more details, see chapter "Complete a building block that uses other building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Documents can be duplicated Clerks can duplicate an existing document (based on a document template or a wizard. For more details, see chapter "Duplicate a document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Language variants of text building blocks can be removed Template administrators can remove language variants from a text building block. At least one language variant must be available. For more details, see chapter "Remove a language variant from a text" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Language variants of image building blocks can be removed Template administrators can remove language variants from an image building block. If required, all language variants can be removed. For more details, see chapter "Remove a language variant from an image" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l If blank lines are added before a text positioning element, tabulator and alignment can be kept Template administrators can define that the tabulator and alignment definitions of a text positioning element are kept even if blank lines are added before. For more details, see chapter "Keep tab stops and alignments in texts" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-10-31 l Labels of form elements can be translated Template administrators can translate label names for wizard form elements. If translation is not activated, translations from the Translation Collection are used. For more details, see chapter "Define a label for a form element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 getstartede V7.6 SP3 217/389 Appendix: main updates in V7.1 l Help information with info button for form elements can be defined Template administrators can define rich text help information for a form element used in a wizard. An info button is displayed in the wizard for the clerk, which they can click to view the help information. Available on the Papyrus Desktop/HTML only. For more details, see chapter "Define information for info button" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 l Personal building blocks can be removed Clerks can remove personal building blocks so that they are not available anymore. For more details, see chapter "Remove a personal building block" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 l New icon for simulation data collections with external data Data collections with external data for simulating documents show a new icon (with arrows and a data sheet), which makes it easier to differentiate them from data collections with manual input (arrows without data sheet). For more details, see chapter "Variables: Upload an external data file" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 l A maximum and minimum height for a text positioning element defined as text input can be set In a document template, template administrators can set a maximum height and/or minimum height for a text positioning element, if the text positioning element is defined as a text input field. For more details, see chapter "Define a maximum and minimum height for a text positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 l A frame can be added to a group positioning element In a document template, template administrators can add a frame to a group positioning elements and define its color, corner rounding, and line width. For more details, see chapter "Add a frame to a group positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 l Releases overview show also empty releases In the Releases overview, template administrators see all available releases, which are either empty or in a development stage. For more details, see chapter "Move a building block to another release" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 l Template administrators can cancel private changes in Group Development In the extended change management process, template administrators can cancel their private changes to an item in Group Development before they complete the item. For more details, see chapter "Cancel your private changes in group development" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 l A layout assigned to a document template can be edited from the document template If template administrators click the name of the assigned layout in a document template to display a layout preview, the dialog provides a button to open the layout in the layout editor for modification. For more details, see chapter "Link a layout to a document template" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Available since DVD V7.1 SP9 2016-06-30 getstartede V7.6 SP3 218/389 Appendix: main updates in V7.1 l Obsolete building blocks can be disabled If this is configured by the system administrator, template administrators can disable building blocks. Disabled building blocks cannot be used for the creation of new document templates and wizards but are still available for existing document templates and wizards. For more details, see chapter "Disabling obsolete building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Option available to force a page break at the visual or logical beginning of a document Template administrators can force a page break at the visual and logical beginning of a document by selecting the Empty page if no output check box for a Page Break building block in the document structure of a document template. For more details, see chapter "Inserting a manual page break" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Option available to suppress empty line for empty text input field Template administrators can define for a text input field that no empty line will be displayed in the document if the text input field is empty. To define this, template administrators must select the Suppress empty prompt lines check box for a text variant building block in the document structure of a document template. For more details, see chapter "Defining text input for a text positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Custom variable format can be defined Template administrators can define a custom variable format (e.g. for a date) for each variable language variant by typing the format into the Format field. For more details, see chapter "Define a custom variable format" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Previous voting results are kept after the release is returned for retest If items or a release are returned for retest, previous voting results are kept and shown to the tester or they are cleared so that a complete retest is enforced, depending on the circumstances. If at least one voting result is missing, the existing voting results are kept, with the voting buttons enabled, and only the test cases with missing results are required to be voted. For more details, see chapter "Return all or selected items for retest" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Only items that are not in status Passed or Failed will be returned for retest if no item is selected If the SIT Test Supervisor or the UAT Test Supervisor does not select an item and clicks the Retest button, only those items not in status Passed or Failed are sent to the tester for retest. For more details, see chapter "Return all or selected items for retest" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Help text for form elements can be defined Template administrators can define a short help text as a placeholder for a form element used in a wizard. A placeholder is text in gray font that is displayed in a field and disappears as soon as the clerk starts to enter something. For more details, see chapter "Define help texts for a form element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Tooltip and placeholder texts for form elements can be translated Template administrators can define translations of tooltip and placeholder texts for a form element used in a wizard. The translation will be displayed as soon as the user interface language is changed to this language. For more details, see chapter "Define help texts for a form element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 219/389 Appendix: main updates in V7.1 16.1.6 Papyrus Business Document Capture Solution 16.1.6.1 Papyrus Client Capture l Capture (BDC) Eye Widgets Settings The visible name of Capture Views Settings (CaptureViewsSettings) has been renamed "Capture (BDC) Eye Widgets Settings". For details, see chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Extended Feature "Send To Supervisor" By means of two new attributes of Capture (BDC) Eye Widgets Settings now the user can specify the reason for sending a document to SOP. For details see attributes Check supervisor info field and Supervisor info field name of "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Highlight Validated Fields New settings attribute Highlight validated fields allows to highlight fields validated by the user, validated by Module Extract and invalid fields in different background colors. For details, see chapter "Highlight validated fields" in "Papyrus Client - Capture User Guide (popcfuge)". l New Shortcuts for "Completion" View "Completion" view of "Capture Workplace" has been provided with the following new shortcuts: [POS1], [END], [CTRL]+[POS1], [CTRL]+[END], [ALT]+[POS1], and [ALT]+[END]. For details, see chapter "Features shared by all views of "Capture Workplace"" in "Papyrus Client - Capture User Guide (popcfuge)". l Change Password Removed from Menu "File" The menu entry "Change password" of menu "File" has been removed from the menus of "Document Workplace" view and "Completion" view. Now this functionality has been moved to the log-in view of Papyrus EYE Widgets desktop where a button "Change password" triggers the display of the respective modal dialog. l Confirm Modal Dialogs with Key [ENTER/RETURN] Now the modal dialogs of "Document Workplace" view and "Completion" view can also be confirmed with the key [ENTER/RETURN]: "Document Workplace": split, delete, copy, classify document "Completion": cancel (document), delete all data (table), insert multiple rows (table) l New Attributes for Capture (BDC) Eye Widgets Settings The following new attributes have been added to Capture (BDC) Eye Widgets Settings: - Completion view field zoom factor [%] - Direct classification - Show newly created documents - Completion correction layout For details, see chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Document Workplace View: New Buttons "Cancel" and "Confirm" Toolbar of Document Workplace view has been provided with two additional buttons Cancel and Confirm. For details, see chapter "Thumbnail viewer toolbar" in "Papyrus Client - Capture User Guide (popcfuge)". getstartede V7.6 SP3 220/389 Appendix: main updates in V7.1 l Document Workplace View: Button "Copy" Renamed "Duplicate" The toolbar button previously named "Copy" is now labeled "Duplicate" offering the same function. For details, see chapter "Thumbnail viewer toolbar" in "Papyrus Client - Capture User Guide (popcfuge)". l Capture Administration Workplace: New View "Adapter Control" Capture Administration Workplace has been provided with a new view "Adapter Control" which has been implemented as one of two tabs of "Capture Cockpit". For details, see chapter ""Capture cockpit/Adapter control" view" in "Papyrus Client - Capture User Guide (popcfuge)". Available since DVD V7.1 SP9 2017-06-30. l New Attributes for Capture (BDC) Eye Widgets Settings The following new attributes have been added to Capture (BDC) Eye Widgets Settings: - Auto-connect to scan receiver - Auto-disconnect from scan receiver - Maximal number of document levels - Prompt file scan settings - Admin attributes editor default mode For details, see chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Single line lookup This new lookup type of Completion view allows to define multiple value search queries in a single search string. For details, see "Single line lookup" in chapter "Single line lookup" in "Papyrus Client - Capture User Guide (popcfuge)". Available since DVD V7.1 SP9 2017-11-30 l Import Files from File System by Drag and Drop This new feature allows to import files from file system into Document Workplace by drag & drop. For details, see chapter "Additional features of the thumbnail viewer" in "Papyrus Client - Capture User Guide (popcfuge)". Available since DVD V7.1 SP9 2017-11-30 l Export Unsupported File Types in Document Workplace This feature allows to export documents of unsupported file types from Document Workplace into the file system. For details, see chapter "Additional features of the thumbnail viewer" in "Papyrus Client - Capture User Guide (popcfuge)". Available since DVD V7.1 SP9 2017-11-30 l Export Documents on Capture Administration Workplace This feature allows to export documents from Document Depot view of Capture Administration Workplace to file system. For details, see chapter "Frame "Thumbnails"" in "Papyrus Client - Capture User Guide (popcfuge)". Available since DVD V7.1 SP9 2017-11-30 16.1.6.2 Papyrus Scan l Capture (BDC) Eye Widgets Settings The visible name of Capture Views Settings (CaptureViewsSettings) has been renamed "Capture (BDC) Eye Widgets Settings". For more details, see chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". getstartede V7.6 SP3 221/389 Appendix: main updates in V7.1 l New Settings Attribute "Display private container information" For more details, see chapter "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Private Container ("My work area") Now the user can move scanned documents from scanned items area of "Scan" view to a private container (temporary storage called "My work area") instead of committing them. This allows one user to interrupt their work with the Scan Receiver without leaving unfinished documents in the Local storage queue and thus bothering other users of the same Scan Receiver. For more details, see chapter "Menu "Documents"" in "Capture Scan Administrator and User Guide (poscanauge)". l Confirmation Dialogs with [ENTER/RETURN] Key Now the confirmation dialogs of "Scan" view (delete, delete all, split, attribute picker of Inspector) can not only be confirmed with their respective affirmative key ([OK], [Split], [Save], etc.) but also with the [ENTER/RETURN] key. For more details, see chapter "Thumbnails viewer buttons" in "Capture Scan Administrator and User Guide (poscanauge)". l Index Data Extraction Up to three index data elements can be defined in the FixForm definition of a scan profile, extracted during scanning and stored for further use. For more details, see chapter "Index Data Extraction" in "Tab "Advanced" of dialog "Profile settings"" in "Capture Scan Administrator and User Guide (poscanauge)". Available since DVD V7.1 SP9 2016-10-31. l Profile Settings Toolbar: Button "Copy Profile" Renamed "Duplicate Profile" The toolbar button previously named "Copy profile" is now labeled "Duplicate profile" offering the same function. For details, see chapter "Toolbar of the dialog "Profile settings"" in "Capture Scan Administrator and User Guide (poscanauge)". l New Scan View-Related Attributes of Capture (BDC) Eye Widgets Settings Capture (BDC) Eye Widgets Settings have been extended by the following new attributes: - Scan Receiver search template - Relocate moved scanned items - Scan view appearance For more details, see "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Variants of Scan View Layout Capture (BDC) Eye Widgets Settings attribute Scan view appearance allows to select between four different layouts for Scan view. For details, see "Variants of the scan view layout" in "Capture Scan Administrator and User Guide (poscanauge)". l Search Document Depot with Scan View Scan view has been provided with search functionality that enables to retrieve documents from Document Depot of the Capture Solution. For details, see "Search area" in "Capture Scan Administrator and User Guide (poscanauge)". l Rescan, Insert scan before, Insert scan after The Scanned items area toolbar on the Scan view has been extended by three new buttons Rescan, Insert scan before, Insert scan after. For more details see chapter "Thumbnails viewer buttons" in "Capture Scan Administrator and User Guide (poscanauge)". getstartede V7.6 SP3 222/389 Appendix: main updates in V7.1 l Rescan file, Insert scanned file before, Insert scanned file after Same functions as Rescan, Insert scan before, Insert scan after but used for Scan mode = Scan file. For more details see chapter "Thumbnails viewer buttons" in "Capture Scan Administrator and User Guide (poscanauge)". l New Scan View-Related Attributes of Capture (BDC) Eye Widgets Settings Capture (BDC) Eye Widgets Settings have been extended by the following new attributes: - Auto-connect to scan receiver - Auto-disconnect from scan receiver - Maximal number of document levels - Admin attributes editor default mode - Prompt file scan settings For more details, see "Capture (BDC) EYE Widgets settings (CaptureViewsSettings)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Export Scanned Documents to File System This feature allows to export scanned images into files system in several file types out of Scan view. For details, see chapter "Thumbnails viewer buttons" in "Capture Scan Administrator and User Guide (poscanauge)". 16.1.6.3 Papyrus Business Document Capture Solution l DOC To PDF Conversion Tool This new tool converts office documents into PDF files. For details, see chapter "DOC TO PDF (DocToPdf)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Routing Version 2 used for Batch Routing in "Capture Base - Solution" As of version v7.1 SP9 Routing version 2 is applied for batch routing in "Capture Base - Solution". For details, see chapter "Define custom routing rules" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Adapter "Import eMail (IMAP)" Now also e-mails from an IMAP server can be imported into a Capture Solution. For details, see chapter "Adapter "Import email (IMAP) (CapBatchImportAdapter)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Settings Attribute "Process mapping" Capture (BDC) General Settings have been extended by new attribute Process mapping. For details, see section "Set Capture (BDC) General Settings Attribute 'Process Mapping'" in chapter "Capture Solution settings" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)" l Save To PDF, Save To Tiff There are new methods for exporting Capture Document image data into file system: Save to Pdf and Save to Tiff. They are slightly differently implemented than the methods ExportToPdf and ExportToTiff. Note that the methods ExportToPdf and ExportToTiff can still be used. For details, see Export documents in WebRepository - Capture Solution Administrator and Developer Guide (popcfade) and Export documents in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). getstartede V7.6 SP3 223/389 Appendix: main updates in V7.1 l Capture Solution Tutorial A new Capture tutorial has been provided on the ISISDVD. This tutorial shows how to instantiate and configure a ready-to-use sample Capture Solution from Library, provides interesting insights in development tasks related to classification definition and extraction definition and presents the most important features of the Capture user interfaces "Capture Workplace" and "Capture Administration Workplace". For details see chapter "Capture Solution tutorial" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Troubleshooting Chapter A new chapter "Troubleshooting" has been added this manual. It informs the reader about some extraordinary situations which may occur and how to fix them. For details see "Capture Solution troubleshooting" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Objects Single Line Lookup This new Lookup type allows to query the Basedata Depot with multi-value queries with the lookup function of Completion view of the Capture user interface "Capture Workplace". For details, see Objects single line lookup (CapObjectsSingleLineLookup) in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l Update Data in Basedata Depot with Depot Key String for Objects Single Line Lookup If there already exists a Basedata Depot with data and an Objects single line lookup is to be defined subsequently, then Depot Index objects used for the Objects single line lookup have to be provided with a Depot key string. For details, see Update data in basedata depot with depot key string for Objects single line lookup in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l Capture Event Logging Capture event logging allows to log process events produced during the execution of a Capture Solution. For details, see "Capture event logging" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". 16.1.6.4 Papyrus Capture Categorizer l Positive Keyword: Regular Expression Now also regular expressions can be used as keywords in keyword definitions. For details, see chapter "Classification definition - details" in "Capture Categorizer Administrator and User Guide (popcfcatauge)". l Data Converter Doc2Idxl Data class filter of Idxl2Text feature extractor has been extended by the additional Data converter Doc2Idxl which allows to classify documents of the file types DOC, DOCX, and ODT. Attribute Allowed classes of Data class filter accordingly has been added the values DataDocBinary, DataDocxBinary, and DataOdtBinary. The Solution templates "Capture Base - Solution" and "Template - Solution" have been provided with the new Data converter Doc2Idxl. For more details about Data class filter and Data converter see chapter Extraction Definition. getstartede V7.6 SP3 224/389 Appendix: main updates in V7.1 16.1.7 Papyrus Reporting Solution l Dashboard: Transform to document Now it is possible to create document templates directly from dashboards. For details see section "Dashboard definition" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". Available since DVD v7.1 SP9 2017-11-30 l Business user workplace: Edit sources This feature allows the Reporting business user to edit source tables. For details see, section "Reporting clerk workplace" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". Available since DVD v7.1 SP9 2017-11-30 l Reporting Ontology Query workplace This additional workplace for the Reporting administrator application workplace allows the Reporting administrator to to create and edit Ontology tables and dashboards and report documents based on Ontology queries. For details, see chapter "Reporting Ontology query workplace" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". Available since DVD v7.1 SP9 2017-11-30 l Fix columns and unfix columns New buttons on toolbar of the column definition table on tab "Column definitions". Method Fix columns "freezes" the columns of a table, i.e. even if the source table has been modified, the columns remain unchanged. Unfix columns releases fixed columns. For details, see "Tab "Column definitions"" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". Available since DVD v7.1 SP9 2017-11-30 l Fix expression New button of dialog "Ontology expression search" (defines Ontology query). Method Fix expression"freezes" the expression base of an Ontology query, i.e. a business user can only add additional specifications of the query but not change the basic concept. For details, see "Create an Ontology table" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". Available since DVD v7.1 SP9 2017-11-30 l Dashboard: Reset columns This new button on the toolbar of Column settings on the definition panel of a dashboard frame, allows to reset the respective table to the original state. For details, see chapter "Dashboard definition" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". Available since DVD v7.1 SP9 2017-11-30 l Automatic Creation of Group Value Columns In the column definition table of a table definition it is possible to define additional columns for group values. For details, see chapter "Tab "Column definitions"" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". Available since DVD v7.1 SP9 2017-10-31 l Ontology Tables To utilize an ontology as data source, it is possible to define an ontology table. For details, see chapter "Create an Ontology table" in "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". Available since DVD v7.1 SP9 2015-11-12 16.1.8 Papyrus Analysis Toolkit l Papyrus AFP Compare: Ignore Area The syntax for the specification of ignored areas has been slightly changed. For details, see ICD parameter "IgnoreArea" in "Analysis Toolkit Application Developer Guide (pandge)". getstartede V7.6 SP3 225/389 Appendix: main updates in V7.1 l Papyrus AFP Compare: SecondPageFrom, SecondPageTo, OrderAfpObjects AFP Compare has been provided with additional optional paramers SecondPageFrom, SecondPageTo, OrderAfpObjects. For details, see ICD parameters "SecondPageFrom" in "Analysis Toolkit Application Developer Guide (pandge)", "SecondPageTo" in "Analysis Toolkit Application Developer Guide (pandge)", "OrderAfpObjects" in "Analysis Toolkit Application Developer Guide (pandge)". l New Features for AFP Analyze Papyrus AFP Analyze has been enriched by the following features: - Start Papyrus AFP Analyze on command line with parameters - Load AFP into Papyrus AFP Analyze by drag'n'drop - Not only AFPDS can be analyzed but also other stream types (e.g. overlays, fonts) For details, see chapter "Papyrus AFP Analyze" in "Analysis Toolkit Application Developer Guide (pandge)". l PUC Settings Visible name of the settings class UCSettings changed from "Universe Compare Settings" to "PUC (Papyrus Universe Compare)". For details, see "Papyrus Universe Compare classes and auxiliary classes" in "Analysis Toolkit Application Developer Guide (pandge)". l New PUC Settings Attributes The settings class PUC (Papyrus Universe Compare) has been extended by the following new attributes: - Use Monospace font in Text View - Hide ObjId and DeploymentState in Class Comparison - Hide SortId In Class Comparison For details, see "Papyrus Universe Compare classes and auxiliary classes" in "Analysis Toolkit Application Developer Guide (pandge)". l Local PUC Settings Apart from the global settings object PUC (Papyrus Universe Compare) of the scope "Domain-wide" it is also possible to make use of local settings assigned to a particular PUC object which is very convenient, if you want to make quick changes of settings. For details, see "Usage of local PUC settings" in "Analysis Toolkit Application Developer Guide (pandge)". 16.1.9 Papyrus Client AFP Viewer l New chapter with practical user instructions A new documentation chapter with numerous step-by-step instructions for working with Papyrus Client AFP Viewer helps users to perform their tasks easily and targeted. For details, see chapter "Using Papyrus Client AFP Viewer" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". l Status bar displays AFP page information A new button in the status bar enables you to display or hide AFP page information about number of document, number of page, Medium Map, Copygroup, and Subgroup. By using the editable fields in the status bar you can navigate to the entered page or document. For more details, see chapter "Status bar" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". Available since DVD V7.1 SP9 2016-10-31 l New icon design All buttons were redesigned in a stylish blue and flat design. Available since DVD V7.1 SP9 2016-10-31 getstartede V7.6 SP3 226/389 Appendix: main updates in V7.1 l Properties toolbar removed Buttons of the Properties toolbar can now be found in the Options toolbar, as the Properties toolbar was removed. Available since DVD V7.1 SP9 2016-10-31 l Direct printing with copy control The Print with copy control dialog was enhanced with new setting controls. Users now can do settings and start the print in one place without having to open an additional dialog. For details, see chapter "Print now with predefined settings" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". 16.1.10 Papyrus Client l New parameter GetAuthorization implemented If set to '1', the parameter triggers individual plugin IPAS requests (one per user session) in order to retrieve the value for the maximum page limit from the IPAS. For more details, see chapter "Product authorization" in "Papyrus Client Application Integration Developer Guide (pcldge)". Available since DVD V7.1 SP9 2017-10-31 16.1.11 Papyrus Client Document Creation (Canvas) l Enhanced Table properties dialog With this newly arranged dialog, users can define or change table and cell properties in a simple and user-friendly way. For more details, see chapter "Creating tables" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP9 2017-12-07 l New parameter StickerCloseonExit If the new profile parameter is set to 'yes', the sticker text is saved even if users did not save the sticker text before the sticker is closed. For more details, see chapter "StickerCloseonExit" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP9 2017-10-31 l New button for inserting a paragraph frame A new button in the Paragraph toolbar enables you to set a frame around one or more paragraphs and define line thickness and line color. For more details, see chapter "Insert frame" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP9 2017-06-30 l New icon design All buttons were redesigned in a stylish blue and flat design. Available since DVD V7.1 SP9 2016-10-31 l Properties toolbar removed Buttons of the Properties toolbar can now be found in the Options toolbar, as the Properties toolbar was removed. Available since DVD V7.1 SP9 2016-10-31 l Change the column width and row height You can change the column width and row height by dragging the vertical and horizontal table lines with the mouse. For more details, see chapter "Change the column width and row height" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 227/389 Appendix: main updates in V7.1 l Define width and position of a table either as percentage or as value A new check box was implemented into the Table Properties dialog. By using this check box, you can now specify the table width and the table position inside of a text input field either as a percentage or as a value and a unit. For details, see chapter "Define the table width" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Blue UI Style In accordance with the general blue ISIS Papyrus UI style, the default color settings for highlighting user input fields were changed. Now text and variable input fields are highlighted in blue to be easily distinguishable from text that cannot be changed. l Direct printing with copy control The Print with copy control dialog was enhanced with new setting controls. Users now can do settings and start the print in one place without having to open an additional dialog. For details, see chapter "Print now with predefined settings" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". 16.1.12 Papyrus Designer, Papyrus DocEXEC l Parameters defining shape of check boxes for VARPROMPT command VARPROMPT command was enhanced by a set of parameters that define display, size, position and text position of check boxes. These parameters come into play when the variable type for VARPROMPT is radio button or checkbox, and they have only effect on OUTPUT prompts, as used for PDF prompting. For more details, see "VARPROMPT command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2017-11-30 l "As is" option in SEGMENT command ASIS in the SEGMENT command helps to calculate the correct object size of images that are rotated by LOGICALPAGE direction. The option only shows effect if page segments' names are entered literally, for example SURF_0, SURF_1, SURF_2, SURF_3. When the "@"-placeholder is used (SURF_@) for name specification, the object size has always been correctly calculated. For more details, see "SEGMENT command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2017-06-30 l APPLICATION-OUTPUT-FORMAT enhancement: WRITERESOURCENAMES WRITERESOURCENAMES YES in the APPLICATION-OUTPUT-FORMAT definition is the equivalent to WRITERESOURCEGUIDS YES. With the parameter set path and filename of each resource used in the AFPDS is written to an NOP record. The parameter helps to access resources which are neither concatenated to the AFPDS in a resource group file nor can be accessed by a resource library profile. For more details, see "APPLICATION-OUTPUT-FORMAT command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2017-06-30 l _SPLIT function instead of EXTRACTALL _SPLIT works similar to EXTRACTALL but with the benefit of unified return values in case special situations: delimiter not found, input string is empty and in case of only one extracted element For more details, see "_SPLIT" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2017-06-30 getstartede V7.6 SP3 228/389 Appendix: main updates in V7.1 l Parameter "Disable numbering" implemented in STICKER dialog If an additional numbering is added to flash stickers by setting DocEXEC Main profile STICKERNUMBERING to yes, the defined path would be incorrect and would cause an error and an unusable PDF. Therefore the new parameter Disable numbering is implemented into the STICKER dialog to prevent a false file path entry. For more details, see "STICKER command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2016-07-01 l ICC profiles must be included in a resource group concatenated to the AFPDS Such profiles are also referred to as CMR resources and can be selected as a particular resource group in the APPLICATION-OUTPUT-FORMAT command. Because some PSF printers depend on profile names that follow a particular naming convention, the name of such profiles will always be modified when entered in the AFPDS. With a modified name, however, such profiles cannot be identified anymore in the resource library or Resource Collection. This is why ICC profiles must be included in a resource group which is concatenated to the AFPDS. For more details, see chapter "CMRPROFILE command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2016-10-31 l Rotate X axis descriptive text for bar, line and area charts For these chart types parameter XTextDirection allows to rotate the descriptive text in 90 degree steps. For more details, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2016-10-31 l Creating PDF/UA documents Support for creating PDF documents with universal accessibility features (PDF/UA standard) has been introduced. For more details, see chapter "Creating PDF with universal accessibility (PDF/UA)" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2016-10-31 l IOBDLL(IOBDEFS) parameter DropResource Use this parameter to remove a PDF or PSEG resource from the resource catalogue to save memory. For more details, see chapter "CREATEOBJECT IOBDLL(IOBDEFS)" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2016-10-31 l Tower charts support values printed inside of columns The tower chart implementation was extended to allow printing values (with optional units) inside the tower columns. For more details, see chapter "Print values inside vertically stacked bars" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2016-06-30 l Support for different formatting of X and Y axis in line charts The new parameter NumPictureDefX allows to define a separate format for the X axis of line charts. Attention, changed behavior: A format defined using parameter NumPictureDef is now only applied to the Y axis. In earlier versions, it was applied to the Y axis and the X axis. For more information, see chapter "CHARTEX DLL for line charts" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP9 2016-06-30 getstartede V7.6 SP3 229/389 Appendix: main updates in V7.1 l CALCWORKDAY more flexible at workday calculation The syntax of the cal.txt configuration file, which defines holidays and workdays to be considered by PDECON subroutine CALCWORKDAY, has been enhanced. It comes now with a general and a special part. In the general part particular days of the week can be defined as workday or holiday, while the special part defines single days of the year. For more information, see chapter "CALCWORKDAY" in "DocEXEC Reference Application Developer Guide (pdedge)". l Royal Mail 2D Mailmark and 4-state Mailmark barcode support Royal Mail 2D Mailmark barcode can be created with a new function in the Data Matrix DLL: CREATEOBJECT DATAMATX(CMDM). For more information, see chapter "CREATEOBJECT DATAMATX(CMDM)" in "DocEXEC Reference Application Developer Guide (pdedge)". The DLL for linear barcode creation, BAROBL DLL, was enhanced by a new function for Royal Mail 4-state Mailmark barcode: CREATEOBJECTS BAROBJ(RM4SMAILMARK). For more information, see chapter "CREATEOBJECT BAROBJ" in "DocEXEC Reference Application Developer Guide (pdedge)". For the general specification of Royal Mail Mailmark barcodes, see http://www.royalmail.com/mailmark/technical [2016-06-13] l Split multi-page PDF or TIFF files into single pages at import CREATEOBJECTS IOBDLL(IOBSDEFS) enables the import of PDF or TIFF files into AFPDS. With parameter SPLITPERPAGE it is now possible to split multi-page PDF or TIFF files into single pages ("Single-page Objects") at import. The parameter was implemented because some printers are not able to handle large PDF or TIFF resources - often multi-page documents - which are concatenated as one big resource entry in the AFP. Page splitting creates a resource entry for each page, and concatenates only those pages to the resource group that are really included. Thus the parameter may also help to reduce file size. For more information, see chapter "CREATEOBJECT IOBDLL(IOBDEFS)" in "DocEXEC Reference Application Developer Guide (pdedge)". l REPRESMSG parameter was enhanced The REPRESMSG parameter, which influences the number of error or warning messages displayed in case of resource-related issues, was enhanced. It supports now also messages that relate to fonts; prior versions did not support font-related messages. For font-related messages it is also possible to define the maximum number of displayed messages relating to the same text element. Defining the maximum number of font messages, however, is only supported in Papyrus Designer, not in Papyrus DocEXEC. For more details see chapter "REPRESMSG" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2017-06-30 l Backward compatibility parameter to set back 2D barcode symbol size calculation: 2DBARCODESIZECOMP The 2D barcode size calculation algorithm (the routines AZTEC, DATAMATX, MAXICOD, PDF417, QR) was improved with release DVD V7.1 SP9 2017-10-30. This improvement can be activated with 2DBARCODESIZECOMP=NO in 7.1. SP9. Future releases will have the improvement activated by default. Prior to release DVD V7.1 SP9 2017-10-30 changing a project's output resolution to another value (for example from 240 to 300 ppi) might have resulted in deviating size of the printed barcode symbol. However, even if the algorithm was optimized there can be minor size deviations in some situations due to the rounding calculation, which have to be accepted. For more details see chapter "Barcode (legacy size calculation - SP9) (DE2DBARCODESIZECOMP) / 2DBARCODESIZECOMP" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2017-10-30 getstartede V7.6 SP3 230/389 Appendix: main updates in V7.1 l Backward compatibility parameter to set back page break properties of TEXT subcommand _TABLE: TABLEPAGEBREAKTOLERANCE The page break property of tables created by TEXT subcommand _TABLE was improved. The TABLEPAGEBREAKTOLERANCE parameter changes the new default page break property of tables back to the status prior to release DVD V7.1 SP9 2017-11-30. By default a table page break considers the amount of text in all columns of the table when setting the break. This default corresponds to TABLEPAGEBREAKTOLERANCE=NO. With TABLEPAGEBREAKTOLERANCE=YES, which sets back the page break property to the status prior to release DVD V7.1 SP9 2017-11-30, only the amount of text in the rightmost column is considered for calculating the page break. This situation might have caused table text being written beyond the bottom margin of a logical page. TABLEPAGEBREAKTOLERANCE is also implemented as Business Correspondence Framework Settings parameter on "CF Compatibility setting". For more details see chapter "Consider a table page break tolerance (DETABLEPAGEBREAKTOLERANCE) / TABLEPAGEBREAKTOLERANCE" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2017-11-30 l Backward compatibility parameter to set back ENDGROUP FLUSH default reaction regarding 'flushing' formatted pages into document copies: FLUSHHASNOCOPY This parameter changes the default reaction of ENDGROUP FLUSH regarding flushing formatted pages into document copies. By default FLUSH writes formatted pages into all specified copies of a document. The first ENDGROUP FLUSH encountered also determines the number of copies for all subsequent ENDGROUP and ENDGROUP FLUSH commands. With FLUSHHASNOCOPY=YES, ENDGROUP FLUSH does not support document copies. FLUSH is only executed for the first document copy. This does also mean that the first ENDGROUP FLUSH encountered does not determine the number of copies to be created. Deviating COPY definitions in other ENDGROUP commands will not be overruled by the COPY value of the ENDGROUP FLUSH command encountered first. This was the reaction of ENDGROUP FLUSH in Papyrus DocEXEC versions prior to V7.1 SP7 (2014-05-03) For more details see chapter ""DEFLUSHHASNOCOPY / FLUSHHASNOCOPY" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)"". Available since DVD V7.1 SP9 2017-10-31 l Backward compatibility parameter to reset MARGIN definition: PRINTFOOTER_USE_SET_MARGIN This parameter corrects MARGIN handling in a particular situation with LOGICALPAGE PRINTFOOTER execution. For more details see chapter "DEPRINTFOOTER_USE_SET_MARGIN / PRINTFOOTER_USE_SET_MARGIN" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2017-06-30 l "Used Settings..." window in Papyrus Designer Papyrus Designer has now an "Used Settings..." window displaying all parameters set for Papyrus Designer, the project and DocEXEC Main profile. The window can be opened by "Help | Used Settings..." For more details see chapter "Configuring Papyrus Designer" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2016-10-31 l Application-Output-Format parameter WRITERESOURCENAMES as command line parameter: APPOUT_RESNAME APPOUT_RESNAME writes resource file path and filename into NOP records and overrules Application-Output-Format definition parameter WRITERESOURCENAMES. These parameters help to access resources in the file system without resource group file or Resource Library profile. For more details, see chapter "APPOUT_RESNAME" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2017-06-30 getstartede V7.6 SP3 231/389 Appendix: main updates in V7.1 l Output format parameter OUTPUTSYNTAX OUTPUTSYNTAX switches the display of variables. If set to YES, the variable names will be displayed instead of their content. For more details, see chapter "OUTPUTSYNTAX" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2017-06-30 l Backward compatibility parameter STYLECLOSEPARAGRAPH STYLECLOSEPARAGRAPH allows to switch to a more HTML-like treatment of paragraph style when using TEXTSTYLES. When set to YES, Papyrus DocEXEC closes the current paragraph so that the intended style (called by _STYLE keyword) can immediately take effect. For more details, see chapter "STYLECLOSEPARAGRAPH" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2017-06-30 l Output format parameter DEFFNT2 allows for TTF definition DEFFNT2 defines the default DBCS font to be used for output. The parameter now allows for definition of a TrueType font as default DBCS font, including the point size. For example, DEFFNT2="Arial,14" For more details, see chapter "Default DBCS font (DEDEFFNT2) / DEFFNT2" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2017-06-30 l Output format parameter: GENERATETAGS Defines whether or not to generate the structure information in the AFP necessary for creating PDF/UA-compliant PDF documents (PDF documents with universal accessibility features). For more details, see chapter "Generate tags (DEGenerateTags) / GenerateTags" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP9 2016-10-31 l Translation of attribute values when accessing Papyrus WebRepository A new command was introduced to define whether to translate attribute values when accessing Papyrus Objects from Papyrus DocEXEC. For more details, see chapter "OMS_USE_TRANSLATION" in "DocEXEC - Access to WebRepository Developer Guide (pdeoadge)". Available since DVD V7.1 SP9 2016-10-31 16.1.13 Papyrus Designer and Server - FixForm l Form Design Guidelines New chapter "Form Design Guidelines for Optimal Recognition" has been provided. This chapter explains in detail how to design forms that are user-friendly as well as best suited for accurate and fast Capture recognition. For details, see "Form design guidelines for optimal recognition" in "Designer Capture Application Developer Guide (pcddge)". l Definition and Activation of Token Data "Completion" view of the Capture user interface "Capture Workplace" enables the user to select text items ("tokens") in the image viewer and copy them directly into the data entry field and the selected field in Form/Table viewer of "Completion" view. This feature has to be enabled in Capture Extract material of the Capture Solution. For FixForm documents additionally token data have to be defined in the extraction definition of the FixForm project. For details see, chapter "Definition and activation of token data ("Tokenize" feature)" in "Designer Capture Application Developer Guide (pcddge)". getstartede V7.6 SP3 232/389 Appendix: main updates in V7.1 l Index Data Extraction with Scan Receiver Up to three index data elements can be defined in the FixForm definition of a scan profile, extracted during scanning and stored for further use. For details see, chapter "Index data extraction definition for scan profile" in "Designer Capture Application Developer Guide (pcddge)". Available since DVD V7.1 SP9 2016-10-31. l Processor Normalize form/detect/photo rectification: estimate from print Attribute document size of the processor normalize form/detect/photo rectification has been provided with an additional value "estimate from print" which tries to estimate the size of the document. For details, see section "form / detect / photo rectification" in chapter "Normalization" in "Designer Capture Application Developer Guide (pcddge)". l Recognition Processor "Fullpage" The new recognition processor "Fullpage" combines the features of Omnifont and standard. So it is possible to accurately recognize mixed texts (proportional, mono space and hand print). For details, see "Fullpage" in "Designer Capture Application Developer Guide (pcddge)". l Correct Arithmetic The scope of the internal rule "Correct arithmetic" has been extended. For details, see section "Correct arithmetic" in "Designer Capture Application Developer Guide (pcddge)". 16.1.14 Papyrus Designer and Server - FreeForm l Enable Tokenize Feature in PO "Completion" view of the Capture user interface "Capture Workplace" enables the user to select text items ("tokens") in the image viewer and copy them directly into the data entry field and the selected field in Form/Table viewer of "Completion" view. This feature has to be enabled in Capture Extract material of the Capture Solution. For details, see chapter "Enable tokenize feature in Papyrus WebRepository" in "Capture Designer FreeForm® Application Developer Guide (ffddge)". 16.1.15 Papyrus Objects (WebControl/WebRepository) 16.1.15.1 Papyrus Objects l Changed recommendation for initial installations and update installations From DVD V7.1 SP9 2016-10-31 all initial Papyrus WebControl/WebRepository installations use the Application Object Space containing all Papyrus Objects frameworks. When performing an update installation, always upgrade all application frameworks independent whether they are currently in use in order to have all frameworks on the same homogeneous release level. For more details, see "Software installation" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". l SPNEGO-based single sign-on The description of the platform availability for the single sign-on feature based on SPNEGO in Papyrus Objects has been improved. For more details, see "SSO Based on SPNEGO using Papyrus Objects" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". getstartede V7.6 SP3 233/389 Appendix: main updates in V7.1 l Agents: delay to avoid multiple execution of stateless tool/material methods Any class defining a tool or material method should additionally define a state machine that prevents agents from executing that method multiple times in rapid succession. When classes are not designed in accordance with that principle, a potential has remained for their methods to be repeatedly executed when called automatically. Now, however, if an object lacks a state machine, an agent will no longer execute any of that object's tool/material methods more than once within any 5-second interval. This precaution might slow down some existing setups; the workaround for a special case of that problem is described in a separate manual. For details, see "Changes in V7.4 SP1" in "". This change in Agent behavior was introduced in v7.1 SP 9 and is being announced for the first time in v7.4 SP 1. l Papyrus Application and Performance Analyzer The APA tutorial video has been updated. The video now shows a general introduction, configuration, and functional overview of APA. A nice animation is provided to demonstrate the APA Net concept. A link to the video is now included in the chapter "Papyrus application and performance analyzer" in "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)". l Application Event Logging The new Log framework allows to log arbitrary processing information produced by any Papyrus application. For details, see "Application event logging - LOG Framework" in "WebRepository Application Developer Guide (pwride)". Available since DVD V7.1 SP9 2017-11-30 l XRM Tutorial The subject XRM - Extended Relation Management is explained by performing a practical example. The XRM framework will be initiated and set up. A simple data base for persons and companies will be created depicting available variants. For details, see chapter "XRM tutorial" in "WebRepository Application Developer Guide (pwride)". Available since DVD V7.1 SP9 2017-10-31 l Ontology Model Items Ontology concepts and attributes can be created in a 'Model Mode' to suit the technical needs of the ontology without disturbing the business view of the ontology. For details, see chapter "Ontology mapping with the Papyrus Ontology Designer" in "WebRepository - Ontology Framework Business Analyst and Developer Guide (pontbadge)". Available since DVD V7.1 SP9 2017-03-10 l Ontology Tutorial In this new chapter the subject ontology is explained by performing a practical example. An ontology is planned and created depicting available modelling and mapping variants. For details, see chapter "Tutorial" in "WebRepository - Ontology Framework Business Analyst and Developer Guide (pontbadge)". Available since DVD V7.1 SP9 2016-10-31 l Local Common Rules: Additional Execution Point Apart from Execution point = "50: Before commit of main transaction" for Local Common Rules also the new value "15: On execute Common Rule" can be selected. For details, see section "Time of execution (execution point)" in "WebRepository Application Developer Guide (pwride)". getstartede V7.6 SP3 234/389 Appendix: main updates in V7.1 l XRM - eXtended Relation Management This new chapter presents XRM, a low level framework, building a fundament for widely used data structures which can be used in different frameworks and customer applications. XRM shall lower the effort during development by reusing ready to use enterprise object definitions. For details, see chapter "Extended relationship management - XRM Framework" in "WebRepository Application Developer Guide (pwride)". Available since DVD V7.1 SP9 2016-06-30 l Agents: delay to avoid multiple execution of stateless tool/material methods Any class defining a tool or material method should additionally define a state machine that prevents agents from executing that method multiple times in rapid succession. When classes are not designed in accordance with that principle, a potential has remained for their methods to be repeatedly executed when called automatically. Now, however, if an object lacks a state machine, an agent will no longer execute any of that object's tool/material methods more than once within any 5-second interval. This precaution might slow down some existing setups Though it defines no state machine, the Session class does define ConnectToDesktop() as a tool method. Thus, the automatic connection of a user's active session to Papyrus Desktop can likewise trigger this 5-second delay. For more details, see "Changes in V7.4 SP1" in "Papyrus Software - Getting Started and News General Information (getstartede)". This change in Agent behavior was introduced in v7.1 SP 9 and is being announced for the first time in v7.4 SP 1. l OTP Second Factor Authentication It is now possible to extend the login process with a second factor authentication, where the user not only has to enter login name and password, but in a second step has to enter an OTP verification code (OTP = one time password). For more details, see chapter "Second-factor authentication via one-time password" in "WebRepository and WebControl Installation and Administrator Guide (poinste)" Available since DVD V7.1 SP9 2016-11-15 l Custom Proxy Settings for Plugins It is now possible to override the system proxy settings (handled by default by the IqtOmsHttpConnection module). For more details, see chapters: "/ISIS_EYEWDG_PROXYENABLED = { yes | 1 | no }" in "EYE Widgets Developer Guide (popeyewdge)" "/ISIS_EYEWDG_PROXYHOST = { host | IP address }" in "EYE Widgets Developer Guide (popeyewdge)" "/ISIS_EYEWDG_PROXYPORT = { port }" in "EYE Widgets Developer Guide (popeyewdge)" Available since DVD V7.1 SP9 2016-11-15 l New Settings Interface Methods The new settings interface methods allow to access and manipulate settings: GetCentralSettings, StoreCentralSettings, ClearCentralSettings GetPrivateSettings, StorePrivateSettings, ClearPrivateSettings GetLocalSettings, StoreLocalSettings, ClearLocalSettings Make use of these methods in your own framework-specific PQL methods that should for instance create a new tenant and also define settings for it. For more details, see chapter "Tasks of the scope developer" in "WebRepository Application Developer Guide (pwride)". Available since DVD V7.1 SP9 2017-03-28 getstartede V7.6 SP3 235/389 Appendix: main updates in V7.1 l Application Event Logging The new Log framework allows to log arbitrary processing information produced by any Papyrus application. For details, see "Application event logging" in "WebRepository and WebControl Installation and Administrator Guide (poinste)" Available since DVD V7.1 SP9 2017-11-30. l Users without passwords no longer supported For security reasons it is no longer possible to assign an empty password (empty string) to a user account. For more details, see chapter "User administration" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". Available since DVD V7.1 SP9 2017-09-30 Note: While setting an empty password was disabled with V7.1 SP9 2017-09-30, logging in with a user account having no password was already disabled in V7.1 SP9 2017-07-01. 16.1.15.2 Papyrus Adapters and Typemanagers l ActiveMQ Sender/Receiver The new ActiveMQ Sender/Receiver expands the MQ interfacing capabilities of Papyrus WebRepository: ActiveMQ Sender/Receiver is a bidirectional interface used for receiving messages and sending messages between Apache ActiveMQ Broker and Papyrus WebRepository via Java Message Service (JMS) using the OpenWire communication protocol (or STOMP as an alternative). For more details, see chapter "ActiveMQ adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". Available since DVD V7.1 SP9 2017-10-31 l Filesystem Synchronization Adapter The Filesystem Synchronization Adapter is part of the new filesystem synchronization framework which allows to import files and directories from file system into Papyrus WebRepository. Imported directories and files are automatically kept in sync with their originals in file system and can also be shared with other nodes and users. For more details, see chapter "Filesystem synchronization adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". Available since DVD V7.1 SP9 2017-03-10 l Migrating a SOAP setup from previous releases Papyrus Software DVD V7.1 SP9 contains Papyrus SOA framework V4. The updated documentation provides migration steps from previous versions to this new version of the SOAP framework. For more details, see chapter "Manual migration of a SOAP setup to the most recent SOAP framework version" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l New SOAP web service endpoint soa.oms The new endpoint soa.oms allows handling of transient tasks and does not require task matching. For more details, see chapter "Components of SOAP Adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l Customization of SOAP endpoints SOAP web service endpoints can now be customized by provider in the SOAP Settings. For more details, see chapter "SOAP settings definition" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". getstartede V7.6 SP3 236/389 Appendix: main updates in V7.1 l Information passing between all SOAP framework components The SOAP framework now allows parameters passing/receiving between a client application and the customized scripts defined on the webservice WSDO tree. For more details, see chapter "SOAP framework - parameters passing between elements" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l SOAP authentication modes The SOAP framework now supports two authentication modes, "Basic HTTP Authentication" and "SOAP WS-Security UserToken". For more details, see chapter "SOAP security and authentication modes" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l SOAP fault message handling A new chapter was introduced into the documentation which explains how to handle the SOAP fault message structure. For more details, see chapter "SOAP fault messages" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l SOAP client synchronous mode The HTTP SOAP client can now be operated in synchronous mode (direct PQL method call) or in asynchronous mode (tool/material matching). For more details, see "HTTP SYNC SOAP REQUEST" in chapter "SOAP adapter classes in Repository" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l SOAP applications and concurrency handling The documentation was enhanced with information on how to deal with parallel calls of the same SOAP client performed by different users. For more details, see chapter "Components of SOAP Adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l SOAP Adapter: WS-Security Header in WSDO Chapter "WS-Security" describes how WS security header can be added to SOAP messages in WSDO tree. For more details, see chapter "WS security" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l Supported Oracle database versions The list of supported Oracle versions has been updated for all available platforms except Itanium. Older versions whose extended vendor support ended are not supported anymore. For a complete list of supported database versions, see chapter "Prerequisites" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". Available since DVD V7.1 SP9 2016-10-31 l SMS Adapter A description has been added. For details, see chapter "SMS adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l CMIS Adapter The description has been extended and updated. For details, see chapter "Papyrus CMIS adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". l IMAP Receiver: Secure Connections Now IMAP Receiver also supports the secure connections IMAPS or STARTTLS. For details see attributes Port and Secure type in "Attributes of IMAP receiver" in "Papyrus E-Mail - Solutions Architecture and Administrator Guide (pemailsole)". Available since DVD V7.1 SP9 2016-06-30 getstartede V7.6 SP3 237/389 Appendix: main updates in V7.1 l IMAP Receiver: New Attributes The new attributes Inbox folder, Processing folder, Finished folder, and Error folder allow to move an e-mail after import into another folder of the IMAP account. For details, see chapter "Attributes of IMAP receiver" in "Papyrus E-Mail - Solutions Architecture and Administrator Guide (pemailsole)". Available since DVD V7.1 SP9 2016-06-30 l SecurityEdit Testing Tool ISIS Papyrus provides the DLL PapyrusMqExitTest.dll in the MQSeries Server for testing the correct operation of SecurityExit. For details, see chapter "PapyrusMqExitTest - Security exit testing tool" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". Available since DVD V7.1 SP9 2017-01-10 l Use Cases for the XML Adapter A new chapter with use cases for the XML adapter has been added. For details see: "Usage of XML adapter/receiver" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". 16.1.15.3 Papyrus Query Language (PQL) l PQLWEB function library Functions to generate HTTP & FTP sessions and requests. For details, see "pqlweb: Papyrus PQL web library in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Case sensitivity options Options to specify case sensitivity of string comparisons, functions and queries. For details, see "Case sensitivity options in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Print availability options Options for specifying the availability of printing on different nodes. For details, see "Output & logging options in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Language options Options to specify the language of a GUI component or resource. For details, see "Translation options in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $keyValueStore queries Query the key/value store of a root object for keys & values matching the specified conditions. For more details, see "$keyValueStore query in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $parentTreeStructured queries This query keyword combines the previously existing $parentTree and $treeStructured queries. For more details, see "Relational queries in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $currentProcessAddress This system variable stores the address of the process where the PQL script is currently executing. For more details, see "System variables in WebRepository Application Developer Guide (pwride)". getstartede V7.6 SP3 238/389 Appendix: main updates in V7.1 l $unmodifiedValue This attribute property supplies an attribute's original value prior to its modification. For more details, see "$unmodifiedValue in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Framework-specific transaction variable accessor functions Functions to define and retrieve global variables in the scope of the current transaction and framework. For details, see "Transaction variable accessor functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $isMethodImplemented() Checks whether the specified C++ member function is defined by the implementer of this object. For more details, see "$isMethodImplemented() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $isFunctionDefined() This function indicates whether or not the named routine has been registered as a PQL function. For more details, see "$isFunctionDefined() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP9 2017-03-10. l $isRefModified() This function indicates whether or not a reference has been modified. For more details, see "$isRefModified() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $joinSets() This function returns the join of two PQL sets. For more details, see "$joinSets() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $randomBytes() This function returns random bytes. For more details, see "$randomBytes() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP9 2016-06-30. l $clearError() This function clears the $Error system variable. For more details, see "$clearError() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $deleteByValue() This function removes array entries having the specified value. For more details, see "$deleteByValue() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP9 2016-06-30. l $deleteFields() This function removes one or more fields (columns) from a PQL set. For more details, see "$deleteFields() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP9 2017-06-30. getstartede V7.6 SP3 239/389 Appendix: main updates in V7.1 l $subArray() This function extracts the specified subrange of the input array. For more details, see "$subArray() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP9 2016-10-31. l $revertArray() This function reverses the elements of an array. For more details, see "$revertArray() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP9 2017-06-30. l PQL condition-parsing functions These functions create the execution tree for a PQL condition string and vice versa. For more details, see "$pqlCreateCondition() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" and "$pqlParseCondition() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP9 2017-03-10. l Object method descriptions moved Descriptions of internally implemented methods have been moved to a dedicated appendix. For details, see "Appendix: Papyrus Objects method catalog in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP9 2017-11-30. l Agents delay automatic connection to desktop The Agent class implementation has been changed in a way that might prevent the timely automatic execution of desktop view methods. That would occur only if an Agent's first attempt to connect via Session::ConnectToDesktop() failed, or if the initial connection were prematurely disconnected. Desktop methods triggered manually through the user interface are not affected by this behavior. Before the change, automatic connections were reattempted with no limit on the number of retries. However, to prevent agents from executing tool/material methods multiple times in rapid succession, the Agent class was modified so that it will no longer execute any such methods more than once within any 5-second interval. Because ConnectToDesktop() is a tool method of Session, it is now subject to 5-second delays in the event of connection difficulties. For more details, see "Changes in V7.4 SP1" in "Papyrus Software - Getting Started and News General Information (getstartede)". This change in Agent behavior was introduced in v7.1 SP 9 and is being announced for the first time in v7.4 SP 1. 16.1.15.4 Papyrus Resource Collection l Exporting Resources from the Resource Collection The Resource Export Object has been updated as the the resource export class has been changed in v7.19. For more details, see "Adjust existing Resource Groups using PQL Script" in chapter "Exporting resources from Resource Collection" in "Resource Library Reference Guide (reslibrge)". l Importing Resources into the Default Resource Group "*" A ready-to-use Resource Adapter for importing resources into the default Resource Group "*" is now available below the Resource Group * in the Resource Group Collection. For more details, see chapter "Importing resources into the default Resource Group *" in "Resource Library Reference Guide (reslibrge)". Available since DVD V7.1 SP9 2017-03-10 getstartede V7.6 SP3 240/389 Appendix: main updates in V7.1 l New Wizard to set up a Resource Adapter A wizard is now available to set up a new Resource Adapter below a newly created Resource Group in the Resource Group Collection. For more details, see chapter "Importing resources into the Resource Collection" in "Resource Library Reference Guide (reslibrge)" 16.1.15.5 Papyrus EYE Widgets l Cards View The Cards View is now available, which is actually a Form widget with a form definition whose Arrangement attribute is set to option 3: Wrap (Horizontal with line breaks). For more details, see chapter "Cards view" in "EYE Widgets Developer Guide (popeyewdge)". l Collapsible Form Element Groups It is now possible to display form elements collapsed. The new Collapsible attribute of groups in form definitions allows to define whether the child form elements shall be displayed collapsed, expanded, or not collapsible/expansible (= default). For more details, see chapter "Cards view" in "EYE Widgets Developer Guide (popeyewdge)". l Token Edit It is now possible to display suggestions for user input in list form element that is turned into tokens. This is more comfortable than letting the user choose an item from a long list. For more details, see chapter "Cards view" in "EYE Widgets Developer Guide (popeyewdge)". l Ontology Search Widget Allows to provide a search widget that utilizes an ontology search. For more details, see chapter "Ontology search widget" in "EYE Widgets Developer Guide (popeyewdge)". l Consistency Checker In addition to the debugger that allows to analyze the run-time tree of widget workplaces, the new consistency checker allows to automate the analysis of widget workplaces and their components. It returns a list of found issues that guide the UI designer directly to the concerned object that should be improved. For more details, see chapter "Consistency checker - improve performance and integrity of widget workplaces" in "EYE Widgets Developer Guide (popeyewdge)". l Funnel Chart Widget Allows to display data with a funnel chart. For details, see chapter "Funnel chart widget" in "EYE Widgets Developer Guide (popeyewdge)". Available since DVD v7.1 SP9 2016-05-31 l Support for URL Query Parameters (aka Call Parameters) Allows to process parameters added to the URL that calls the workplace in the web browser (using Papyrus EyeWdg Plugin). For details, see chapter "External call parameters - URL query parameters" in "EYE Widgets Developer Guide (popeyewdge)". Available since DVD v7.1 SP9 2016-06-30 l New system trigger $AboutToPollGetters for Component Controller This system trigger is called after all setters and commands have been processed and before the getters are polled. It allows you to execute code which has longer execution times. For details, see chapter "Component controller" in "EYE Widgets Developer Guide (popeyewdge)". Available since DVD v7.1 SP9 2016-11-24 getstartede V7.6 SP3 241/389 Appendix: main updates in V7.1 l New way of dynamically adding components/widgets using API object With the API object it is possible to programmatically add components/widgets, similar to the widget binding object where they are added triggered by high level events. For details, see chapter "API object to dynamically add components/widgets" in "EYE Widgets Developer Guide (popeyewdge)". Available since DVD v7.1 SP9 2017-01-31 16.1.15.6 Papyrus WebPortal l New request type "rest.oms" This request type is needed for user interfaces of Papyrus Desktop/HTML which use the REST interface of the web server of Papyrus WebPortal. For details see: "Request Types of the Web Server" in Define web server requests in WebPortal Installation and Developer Guide (powpidge). 16.1.15.7 Papyrus Word to Correspondence 16.1.16 Papyrus Database Interfaces l Supported database versions The database interface modules were extended, now also the Oracle client V12.C on Solaris is supported whereas old versions 8, 9, 10, whose extended vendor support ended, are not supported anymore. For a complete list of supported database versions, see chapter "Supported database client versions" in "Database Interfaces Developer and Administrator Guide (pdbdage)". Available since DVD V7.1 SP9 2016-10-31 16.1.17 Papyrus Host l JCLs starting Papyrus Host (QFSSMAIN call) cannot define temporary datasets by SYSTMP 16.1.18 Papyrus PrinterDriver l Shortcut for starting the PrinterDriver Server available For an easy start of the local print server, a shortcut is created in the Windows Start menu at installation. The shortcut can also be pinned to the taskbar. For details, see chapter "Third step: Start the local print server" in "PrinterDriver Administrator and User Guide (pdrauge)". Available since DVD V7.1 SP9 2017-10-31 l JPEG compression level can be defined For IOCA FS45 JPEG images the compression level can be individually defined. For details, see chapter "Images definition dialog" in "PrinterDriver Online Help (isisdrv.hlp )". Available since DVD V7.1 SP9 2017-06-30 l Document generation mode set differently Document generation mode (text mode or image mode) is now set for the file-based and the Objects-based PrinterDriver in the Properties dialog of the respective printer. For details, see chapter "Document generation mode" in "PrinterDriver Online Help (isisdrv.hlp )". Available since DVD V7.1 SP9 2017-03-10 l Updated user interface Several items of the graphical user interface (dialogs, names of buttons, entry fields, and check boxes) were renamed or rearranged to support users with a more intuitive interface. Available since DVD V7.1 SP9 2017-03-10 getstartede V7.6 SP3 242/389 Appendix: main updates in V7.1 l New chapters with practical user instructions New documentation chapters for file-based and Objects-based usage with numerous step-by-step instructions help users to perform their tasks easily and targeted. For details, see chapters "File-based usage" in "PrinterDriver Administrator and User Guide (pdrauge)" and "Objects-based usage" in "PrinterDriver Administrator and User Guide (pdrauge)". Available since DVD V7.1 SP9 2017-03-10 l MCF2 format for AFP raster fonts As the MCF (MCF1) format is deprecated, Papyrus PrinterDriver creates since v160413.v719 AFP raster fonts with MCF2 format. The MCF2 format for outline fonts remains unchanged. For details, see chapter "MCF format" in "PrinterDriver Online Help (isisdrv.hlp )". Available since DVD V7.1 SP9 2016-04-13 l New resource ID generator The new resource ID generator in Papyrus Objects ensures that all generated resources have unique IDs and grants concurrency, because the access to the resource ID generator is controlled. For details, see chapter "ID for new resources" in "PrinterDriver Administrator and User Guide (pdrauge)". l New documentation structure The new structure of the manual provides chapters addressed to administrators and chapters targeted at business users for an easy entry point to the required information. 16.1.19 Papyrus Postprocessing/Printpool and WebArchive AFP Splitter l AFP -> HTML Now Archive Server Module can also be used to split an AFPDS file and convert into HTML. In Papyrus WebRepository split AFP and convert to HTML is implement as tool AFP -> HTML which uses the material Archive AFP that has been enhanced by HTML related attributes. AFP -> HTML is available for Windows and AIX. For details see, "Papyrus Papyrus Server - HTML Reference Guide (psehtmlrge)" and the chapters "AFP -> HTML (ArchiveAfpHtml)" in "Papyrus Postprocessing/Printpool and WebArchive AFP Splitter and Check-in Reference Guide (psearcrge)", "ARCHIVE AFP" in "Papyrus Postprocessing/Printpool and WebArchive AFP Splitter and Check-in Reference Guide (psearcrge)". Available since DVD V7.1 SP9 2016-10-31. l Tiff JPEG Quality New TIFF parameter. For details see, "TiffJpegQuality" in "Papyrus Postprocessing/Printpool and WebArchive AFP Splitter and Check-in Reference Guide (psearcrge)". 16.1.20 Papyrus PostCalc l Supported Platforms and Databases The list of supported operating system versions and database management systems has been updated in the documentation. For more details, see chapter "Prerequisites and installation" in "PostCalc - Postage Calculation and Optimization Reference Guide (ppcrge)". Available since DVD V7.1 SP9 2016-10-31 getstartede V7.6 SP3 243/389 Appendix: main updates in V7.1 16.1.21 Papyrus Server 16.1.21.1 General l Redirecting messages from a server module running stand-alone Information on how to perform this logging method has been added. For more details, see chapter "Using Papyrus Server with ICD File" in "". l Additional information on the individual server modules The availability of server modules on different platforms is listed in "Specific prerequisites" in "Papyrus Server General Installation and Administrator Guide (pseiae)". The article "Directory and file structure of the Server modules" in "Papyrus Server General Installation and Administrator Guide (pseiae)" has been extended with links to the corresponding manuals. 16.1.21.2 AFP to PDF l TTC Font characters as text In previous versions characters from TrueType Collections were converted to bitmaps. The parameter "TTC Font as image" offers the possibility to create them as text. This can result in smaller documents and has the additional benefit that the text can be copied and pasted. For more details, see chapter "Generate TTC characters as image (PDFtTTCFontAsImage)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP9 2017-10-31 l PDF/UA support for z/OS native and z/OS Unix Available since DVD V7.1 SP9 2017-10-31 l Additional features for submit button(s) It is now possible to create multiple submit buttons within one document and customize the labels (i.e. not always "submit"). For more details, see chapter "Submit button (PdftSubmitRect)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP9 2017-03-10 l Creating PDF/UA documents Support for creating PDF documents with universal accessibility features (PDF/UA standard) has been introduced. For more details, see chapter "Universal accessibility (PDF/UA)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP9 2016-10-31 l Vertical Offset for Prompts - Extended PDFtGenPrompts parameter/attribute Generate Prompts now allows to define a vertical offset in millimeters in addition to a scaling of the used font. For details, see chapter "Generate Prompts (PDFtGenPrompts)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP9 2016-06-30 16.1.21.3 AFP to text Initial release 16.1.21.4 AFP to thumbnail Initial release getstartede V7.6 SP3 244/389 Appendix: main updates in V7.1 16.1.21.5 Tuner l New example demonstrating RemoveArea In this example a certain area of the first page of a document is painted over with a white rectangle. For more details, see chapter "Practical examples" in "Papyrus Tuner Reference Guide (ptunrge)". Available since DVD V7.1 SP9 2017-03-10 l Description for TLE Manipulation added With these parameters existing Page Groups can be reshaped and extended to create new group index elements. For more details, see chapter "TLE manipulation" in "Papyrus Tuner Reference Guide (ptunrge)". Available since DVD V7.1 SP9 2017-03-10 l Description for Group Manipulation added With these parameters logical documents can be created from a "flat" print file by interpreting information on the first page. For more details, see chapter "Group manipulation" in "Papyrus Tuner Reference Guide (ptunrge)". Available since DVD V7.1 SP9 2017-03-10 l Manual overhaul The parameters have been grouped to match the tabs in Papyrus Objects. Manipulation has been split into the four major use cases: TLE Manipulation, Group Manipulation, Remove Area and White Space Management. Available since DVD V7.1 SP9 2017-03-10 16.1.22 OverView AFP Designer l Download resources from iSeries Resources as character sets, codepages, coded fonts, page segments, overlays, form and page definitions can be downloaded from an IBM iSeries machine to the Windows workstation running OverView AFP Designer. An import tool is available to convert the AFPDS resources into a readable format on the Windows workstation. For details, see chapter "Download resources" in "AFP Designer Online Help (OVERVENG)". Available since V7.1 SP9 2017-10-31 l Updated Edit color dialog For the IBM OCA color model, the color option None can be selected, which can be defined as color of the medium. For details, see chapter "IBM OCA" in "AFP Designer Online Help (OVERVENG)". Available since V7.1 SP9 2017-04-14 l New RescalableIOCA parameter With the new RescalableIOCA parameter you can rescale the generated IOCA image for the printing process when the printer resolution is different from the image resolution. For details, see chapter "Image options tab" in "AFP Designer Online Help (OVERVENG)". Available since V7.1 SP9 2017-01-16 l iSeries profile created automatically A new iSeries profile iSeries.Hpr is created automatically. The path to this profile is inserted automatically into the new ISERIESPROFILE parameter. For details, see chapter "iSeries tab" in "AFP Designer Online Help (OVERVENG)". Available since V7.1 SP9 2017-01-16 getstartede V7.6 SP3 245/389 Appendix: main updates in V7.1 l MSI Installation Package available In case you want to install OverView AFP Designer on many machines, an MSI package is available on demand. For details, see chapter "MSI installation package" in "AFP Designer Application Developer Guide (oaddge)". Available since V7.1 SP9 2016-11-15 l Upload/Download to iSeries Upload and download of applications from OverView AFP Designer to IBM iSeries was implemented. For details, see chapter "OverView AFP Designer for iSeries (AS/400)" in "AFP Designer Application Developer Guide (oaddge)". Available since DVD V7.1 SP9 2016-10-31 l Migrating from InfoPrint Designer to OverView AFP Designer You can easily migrate applications that have been designed with InfoPrint Designer to OverView AFP Designer. For details, see chapter "Migrating from InfoPrint Designer to OverView AFP Designer" in "AFP Designer Application Developer Guide (oaddge)". Available since DVD V7.1 SP9 2016-10-31 16.1.23 OverView Image Editor l Saving images with color profiles as PSEG The AFP File parameters dialog was extended for the special case that you want to save a JPEG, TIF, or PNG with a color profile as PSEG. It offers two options for dealing with color profiles, as the original color profile cannot be embedded into the output AFP image. For more details, see chapter "Save as AFP image" in "Image Editor Online Help (O_IE_ENG)". Available since DVD V7.1 SP9 2016-10-31 16.1.24 Papyrus best practices 16.1.24.1 Interactive PDF documents l PDF/UA A description of PDF Universal Accessibility and its configuration and usage in Papyrus Designer and the Business Correspondence Solution has been added. For more details, see chapter "Creating PDF/UA documents with Papyrus software" in "Interactive PDF Documents Developer Guide (pipdfddge)". Available since DVD V7.1 SP9 2017-10-31 16.1.24.2 Project management guidelines 16.2 Main updates in V7.1 SP8 16.2.1 General changes This DVD includes Papyrus products in release level V7.1 SP8. New documents available: Interactive PDF documents This document intends to kindle your creativity on how Papyrus Designer can support your business processes by creating interactive multimedia PDF documents. It is targeted towards marketing people (especially the introductory chapter) and DOCDEF developers. For details, see "Interactive PDF Documents Developer Guide (pipdfddge)". Output Management Applications Architecture Guide getstartede V7.6 SP3 246/389 Appendix: main updates in V7.1 A new document is available that provides a high-level overview of solutions with regard to Output Management. The document describes Papyrus Output Management components and options and is addressed to system architects and application developers. For details, see "Output Management Applications Architecture Guide (pomarcge)". Papyrus Server Capture Reference Guide A new document is available that describes Papyrus Capture Server, an ISIS Papyrus application that extracts data out of input documents from file system based on FixForm or FreeForm document type specifications. For details, see "Papyrus Server - Capture Reference Guide (psecaprge)". 16.2.2 Papyrus product installation l New video tutorial is available: Getting Started with Papyrus Products The video gives an overview of the installation process, the concept of product authorization, where to find product documents and how to get support. The video is installed with the ISIS Papyrus Installation Routine and can be opened from the Windows Start menu: Start | All Programs | ISIS Papyrus Tutorial Videos | ISIS Papyrus - Getting Started with Papyrus Products l Updated list of supported browsers for Papyrus Browser Plugins The list of supported browsers for Papyrus Browser Plugins was updated. For more details, see chapter "Supported browsers" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". 16.2.3 ISIS Papyrus Product Authorization Service l Hardlock Key driver for Windows in new location The Hardlock Key driver for Windows can now be found under the platform-specific subfolder: \install\keydriver\Windows For more details, see chapter "Manually installing and uninstalling Hardlock Key drivers" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". l New names of transfer files required for IPAS update The names of transfer files required for an IPAS update have changed. Three transfer files instead of two are now needed for an IPAS update. For more details, see chapter "Upgrading standalone IPAS" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". 16.2.4 Papyrus Adaptive Case Management Solution 16.2.5 Papyrus Automated Document Factory Solution l Integration of Print and E-Delivery Into Business Correspondence The Print and E-Delivery Output Options were introduced which allow the integration of the Papyrus Print and E-Delivery Solution into the Papyrus Business Correspondence Solution. For details, see chapter "Integration into Business Correspondence Solution" in "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)" and "Enable Print and E-Delivery (PED) output options" in "". Available since DVD V7.1 SP8 2015-07-01 16.2.6 Papyrus Business Correspondence Solution l High-level details on the contents of the correspondence framework For more details, see chapter "Papyrus Business Correspondence Solution overview" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 247/389 Appendix: main updates in V7.1 l Presentation of the business user interface Regardless of how the Papyrus EYE Widgets Desktop is accessed the presentation of the user interface does not alter. For more details, see chapter "Business users accessing Papyrus Business Designer" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Release and Change Management process The Release and Change Management process based on Adaptive Case Management (ACM) has seen the reintroduction of the Simple Change Management process. For more details, see chapter "Release and change management" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Initial installation of a node architecture Provides a description of the minimum set of nodes that are required for a Business Correspondence Solution. For more details, see chapter "Initial installation of a Papyrus Business Correspondence Solution" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Creation of a WebServer - Papyrus EYE Widgets and REST/HTML Information on how to setup a REST/HTML WebServer has been included. For more details, see chapter "Installation and configuration of a Papyrus WebServer on a Portal Node" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Implementation of REST/HTML client Instructions on the requirements for a REST/HTML client are provided. For more details, see chapter "Client workplace implementation" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Automated scripts used for initial configuration - Tenant Automated scripts have been developed to handle a number of tasks that would have been previously performed manually. For more details, see chapter "Creation of a Tenant in the Tenant Collection" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Automated scripts used for initial configuration - Translation Dialog Automated scripts have been developed to handle a number of tasks that would have been previously performed manually. For more details, see chapter "Enabling the translation dialog for existing building blocks" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Creating resources using the Correspondence Definition Collection The collection is used to define settings containers that are referenced by Scope Settings object. For more details, see chapter "Create Correspondence Definition Collection resources automatically" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Recording and tracking document issues Business users within a production environment can report on issues that they identify when using document templates. Production hotifx's can be applied to document templates using the information contained in bug reports For more details, see chapter "Configuring comments and problem reporting" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Extending a Business Correspondence Solution Main headline article that pulls together reference information and administrate a Business Correspondence Solution based on use cases. For more details, see chapter "Configuring document creation and business user workflows using correspondence scope settings" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 248/389 Appendix: main updates in V7.1 l How to create search criteria for the Design and Content tabs A new chapter describes how to extend the content of the Design and Content tabs with new search criteria. For more details, see chapter "Configuration of Content and Design tabs for a business user" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Name and description of building blocks can be translated by business users Chapter describes how to configure the translation dialog and the various ways that this can be used. For more more details, see chapter "Configure translation dialog for document and building block types" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Using Scope settings for individual document templates Provides an overview of scope settings that are available for configuration of an individual document template. For more details, see chapter "Modify document properties for clerks" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Creation of Departmental structures within a Tenant based on the use of policies Chapter describes how to create a departmental structure based upon the use of policies ensuring separation between different departments. For more details, see chapter "Create departmental structures using policies" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Extend workflow allowing Clerks to approve documents Using configuration settings Clerks can be allowed to approve documents so that they move to the complete queue. For more details, see chapter "Extend business user workflow" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Provide online Help to the Business User Using configuration settings online Help can be provided by linking to a external website and providing help text. For more details, see chapter "Provide online help to a business user" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l External invocation of Document Templates and Wizards Describes how to invoke external document templates and wizards based on REST/HTML WebServer. For more details, see chapter "Business user call of document template and Wizard Case via a URL" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Creation of Group Indexes for Correspondence Documents Shows how to create Group Indexes for document using settings. For more details, see chapter "Create indexes for correspondence documents" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Exposing Fonts to the Business User interface Using settings define Fonts that are available in the business user interface. For more details, see chapter "Expose fonts to the business user interface" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". l Rich text support in PDF Documents Describes how to create promptable areas within PDF documents. For more details, see chapter "Enabling Building blocks for use in Interactive PDF Documents" in "". l Creating document instances based upon the data input Details how to extend the DOCUMENT class so that it retrieves the CF_DOCUMENT_CONTENT based upon input data. For more details, see chapter "Data driven usage of dynamic document template in batch mode" in "WebRepository - Business Correspondence Solution Administrator and Developer Guide (pocfdage)". getstartede V7.6 SP3 249/389 Appendix: main updates in V7.1 l Read-only mode available for document templates Template administrators can open document templates in read-only mode, for example to view active document templates without creating a new version. For more details, see chapter "Viewing building blocks in read-only mode" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l New testing statuses available for SIT and UAT testers and supervisors New testing statuses are provided for test items in the SIT and UAT release stages. For more details, see chapter "Overview of testing statuses" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Template administrators can define settings for a document template Template administrators can define specific settings for a document template on the business user interface, such as the document edit view for the clerk. For more details, see chapter "Modifying document settings for clerks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Template administrators can hide individual document templates and building blocks from clerks By removing policies from a building block and assigning a departmental policy, template administrators on the business user interface can define that this building block will be available to clerks of this department only. For more details, see chapter "Hiding a building block from clerks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Name and description of building blocks can be translated by business users Then content of the building block name and description can be translated by the business user and is then displayed according to the user interface language. For more details, see chapter "Activate translations of names and descriptions" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l More than one simulation collection with manual input data can be selected When several collections with written values for variables are available, more than one collection can be selected. In the document preview, one document for each collection is displayed or generated as PDF. For more details, see chapter "Run a simulation" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Rules can be defined for attachments and inserts When you define output options for a document template or document, you can add rules with NLR to inserts and attachments that determine under which condition the insert or attachment is added to the document. For more details, see chapter "Defining output options for a document" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l A new release template with shorter release cycle is available A new release template called Release (simple) is available, which provides only two stages: Group Development and System Integration Test. The original release template for the extended change management with two development and two test stages is called Release (extended). For more details, see chapter "Change management process" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Building blocks can be deleted by the template administrator If configured by the system administrator, template administrators can remove items on the Correspondence Management workplace. For more details, see chapter "Deleting building blocks" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". getstartede V7.6 SP3 250/389 Appendix: main updates in V7.1 l Icon for positioning reference in document template/group/layout structure When positioning information is referenced for a building block in the structure of document templates, groups or layouts, this is indicated by a sheet icon next to the building block. For more details, see chapter "Define a positioning reference for duplication" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l Icon for rule definition in document template/group/layout structure When a rule is defined for a building block in the structure of document templates, groups or layouts, this is indicated by a signpost icon next to the building block. For more details, see chapter "Define a rule for a positioning element" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". l New chapter about activities in the Papyrus Client Canvas Plugin A new chapter contains easy-to-follow instructions showing you how to preview, edit, format, print, and manage texts in the Papyrus Client Canvas Plugin. For more details, see chapter "Editing texts with the Papyrus Client Canvas plugin" in "Papyrus Business Designer and Papyrus Client Business Correspondence User Guide (pocfuge)". Description available since DVD V7.1 SP8 2015-07-01 16.2.7 Papyrus Business Document Capture Solution l Capture Result Storage: Capture Result Storage 3 Attribute Capture Result Storage of Capture Framework General Settings has been provided with an additional value Capture Result Storage 3 adding another storage type for the Capture Result Document. This Capture result storage type 3 is very similar to storage type 2, except that several fields of the result PQL set have been eliminated ($name, $internalname, $displayname are redundand because of the field ElementName; InputXRes, InputYRes, XScaleFactor, YScaleFactor, XOffset, YOffset, Rotation, RegionXOffset, RegionYOffset, RegionRotation have also been removed - Transformation and RegionTransformation are used instead). For details see Capture (BDC) general settings (CaptureFrameworkGeneralSettings) in WebRepository - Capture Solution Administrator and Developer Guide (popcfade) and section "Capture Storage Mode" in Capture document in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l New Attributes for Capture Views Settings Capture Views Settings has been provided with the following new attributes: - "No page information for new rows" - "Hidden workplace commands" - "Completion view maximum numbers of new rows" - "Disable split for single page documents" For details see Capture (BDC) EYE Widgets settings (CaptureViewsSettings) in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l Capture Workplace v2 The usage of Capture Result Storage 3 for the creation of Capture Result Documents resulted in the addition of a new template "Capture Workplace v2" to be used for the views of the Capture user interface "Capture Workplace". For details see Capture EYE Widgets workplaces in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l Capture Admin Depot Search The PQL Search Task template "Document Depot Search" required for Capture Views Settings has been replaced by the template "Capture Admin Depot Search". For details see Capture (BDC) EYE Widgets settings (CaptureViewsSettings) in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). getstartede V7.6 SP3 251/389 Appendix: main updates in V7.1 l Depot Collection A new "Depot Collection" has been provided in Storage which is to contain references of the Depot Control Centers of all Depots used in the domain. As the references are automatically created after instantiation of the Basedata Depot and the Document Depot (Depot partitions if a Distributed Depot is used) no user intervention is required. However, there must no be references of Depot Control Centers with the same Depot Id in the Depot Collection. For details see Depot Collection in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l Capture Document Index Templates A new set of Index templates has been provided for Capture Document searches in Document Depot. For details see Capture Document Index Templates. l New Adapter "Import eMail (POP3)" The new Adapter template "Import eMail (POP3)" has been provided in Library. Thus, now also e-mails from POP3 servers can be imported into a Capture Solution. For details see Adapter "Import email (POP3) (CapBatchImportAdapter) in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l Web Service Objects Simple Lookup This new Capture Lookup class enables data validation by means of a web service. For details see Web service objects simple lookup (CapWebServiceObjectsSimpleLookup) in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l Export PDF, Export Tiff Class Capture Document (CapDocument) now provides the methods ExportToPdf() and ExportToTiFF() which enable to export document images from a Capture Solution into file system as PDF and Tiff files, respectively. For details see "Export documents" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)", "Export documents" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Capture Validation Root Rule The structure of the validation rules of a document class has been changed. Now the Module Rules previously children of Rule Folder are children of the new Capture Validation Root Rule. For details see: "Common rules and validation" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". 16.2.8 Papyrus Analysis Toolkit l Papyrus AFP Analyze New tool for listing AFP documents with result display in a GUI. For more details see: Papyrus AFP Analyze in Analysis Toolkit Application Developer Guide (pandge) l UC Settings Visible name changed from UC SETTINGS to UNIVERSE COMPARE SETTINGS. l UC Settings New attribute Highlight path to differences in ClassDef view For more details see: attributes of PUC (PAPYRUS UNIVERSE COMPARE) (UcSettings) in Analysis Toolkit Application Developer Guide (pandge). getstartede V7.6 SP3 252/389 Appendix: main updates in V7.1 l UC Settings New attribute Ignore Whitespaces in Text Comparison For more details see: attributes of PUC (PAPYRUS UNIVERSE COMPARE) (UcSettings) in Analysis Toolkit Application Developer Guide (pandge). l Papyrus Universe Compare - 3 Way Comparison As of this version PUC not only compares two objects but also three objects (except for PUC CANVAS which compares two AFP documents). For more details see: Compare three objects with PUC in Analysis Toolkit Application Developer Guide (pandge)". l Papyrus Universe Compare - Breadcrumb Navigation in UC Compare Class Definition Now the views of UC Compare Class Definition allow to navigate in the definition tree with breadcrumb navigation. For more details see: Breadcrumb navigation (UC compare class definition) in Analysis Toolkit Application Developer Guide (pandge). l Papyrus PDF Compare - Compare different pages of two PDF files Now the page range of the reference PDF and the PDF to compare can be specified differently. For more details see: Papyrus PDF Compare in Analysis Toolkit Application Developer Guide (pandge). l Papyrus PDF Compare - Compare password-protected PDF files Now also password-protected PDF files can be compared with Papyrus PDF Compare. For more details see: Papyrus PDF Compare in Analysis Toolkit Application Developer Guide (pandge). l PUC Compare Text with HTML Rendering and dual view Now PUC Compare Text displays HTML source highlighting HTML syntax and additionally in wsysiwig view, if certain conditions are met. For details see: Text comparison: HTML rendering and dual view in Analysis Toolkit Application Developer Guide (pandge). l PUC Compare: Compare Struct Definitions and Struct Attributes Now also struct definitions as well as object instances and templates containing attributes defined with type "Struct" can be compared. For details see: "Compare struct definitions and attributes of type "Struct" in Analysis Toolkit Application Developer Guide (pandge)". 16.2.9 Papyrus Client Document Creation (Canvas) l New features for inserting links, comments, bookmarks, and references Updated dialogs for inserting external links to webpages or e-mail addresses, bookmarks and references enable you to easily define jump labels in the document and to insert expressions into the defined links. For details, see chapter "Inserting links and bookmarks" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Updated text break behavior for Asian Languages A new Space break button was implemented that supports line breaking when using DBCS or mixed SBCS/DBCS fonts, which is especially of advantage when printing Asian language text. For details, see chapter "Font toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l New chapter with practical user instructions A new documentation chapter with numerous step-by-step instructions helps users to perform their tasks easily and targeted. For details, see chapter "Editing documents" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". getstartede V7.6 SP3 253/389 Appendix: main updates in V7.1 l New parameter PromptGenerate If this parameter is set to "yes", the Generation and Print toolbars are also available when you edit an input field, which is not the case by default. With this setting you can generate or print an AFP or PDF document also during the editing process. For details, see chapter "PromptGenerate" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Edit object properties in the Canvas Design area You can now edit all properties of the objects inserted into the Design area directly in the User input window. For details, see chapter "Canvas (design area) toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Adjustment of output generation for AFP and PDF documents The capability to create AFP and PDF documents were aligned. With a Papyrus Client/Desktop authorization AFP documents as well as PDF documents with up to 100 pages can be produced. 16.2.10 Papyrus Designer and Server - FixForm l Date Formatter Attribute formats allowed of Text processor "Date Formatter" has been provided with additional options: MY | YM. For details see: Date formatter in Designer Capture Application Developer Guide (pcddge). l UseLeftMostInLine/UseRightMostInLine New internal rules "UseLeftMostInLine/UseRightMostInLine" have been implemented. For details see: UseLeftMostInLine in Designer Capture Application Developer Guide (pcddge). l Existence New internal rule "Existence" has been implemented. For details see: Existence in Designer Capture Application Developer Guide (pcddge). l LinkedToTop/LinkedToLeft New attribute "LinkedToTop/LinkedToLeft" for anchors has been implemented. For details see: Settings of anchors in Designer Capture Application Developer Guide (pcddge). l Check Digit Validation The new text processor "Check Digit Validation" enables to validate the check digit of a character string. For details see: "Check digit validation" in "Designer Capture Application Developer Guide (pcddge)". l Omnifont 10 Core License Now alternatively to the page volume model of Abbyy also the Core license mode is available. For details see: "Abbyy license models" in "Capture Designer FreeForm® Application Developer Guide (ffddge)". l Force Recognition New attribute for all recognition processors of type "Text". In enables to force extraction if there is already an extraction result, either from text input or from data root. For details see e.g.: "Standard" in "Designer Capture Application Developer Guide (pcddge)". getstartede V7.6 SP3 254/389 Appendix: main updates in V7.1 16.2.11 Papyrus Designer, Papyrus DocEXEC l Changed behavior of system DocFormat $_CATCHERROR 1) The calling method of DocFormat $_CATCHERROR was changed so that it is always called as a sublevel DOCFORMAT. It is not possible anymore to use main level objects within $_CATCHERROR. 2) DocFormat $_CATCHERROR is not called anymore immediately after an error occurs, but only after the causing command has been completely executed. For more information, see chapter "DOCFORMAT command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP8 2016-02-01 l XMLSET enhancement The XMLSET command has been enhanced and supports now an option for creating variables from tag attributes. For more information, see chapter "XMLSET command" in "DocEXEC Reference Application Developer Guide (pdedge)". l New chart type: Cylinder chart Cylinder charts are a modified, specific form of column-type bar charts. They use cylinder-shaped items to show data. For more information, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP8 2014-11-18 l New chart type: Donut The donut (sometimes also spelled doughnut) chart is a variation on the pie chart with a blank center. Compared to the regular pie chart it adds advanced formatting capabilities with 4 additional parameters that give more flexibility for designing the torus by splitting it into 3 rings. These parameters are called SLICEDISTANCES, SLICECOLORS, SEPARCOLOR and SEPARLINECOLORMODIFIER. For more information, see chapter "CHARTEX DLL for pie charts" in "DocEXEC Reference Application Developer Guide (pdedge)". l Improved Profit/Loss chart The parameter EXTRATOPMINMAXINFO has been extended and the parameter BARTOPINFO added to provide even more possibilities to place information within the chart. For more information, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)". l New function NUMTOWORD NUMTOWORD returns a natural language string for a numerical value using ICU (International Components for Unicode) language rule files. For example, the function changes "25,3476" to "twenty-five thousand three hundred seventy-six". For more information, see chapter "_NUMTOWORD" in "DocEXEC Reference Application Developer Guide (pdedge)". l New function SYSTIMESTAMP SYSTIMESTAMP returns the current system time in format 'YYYY/MM/DD hh:mm:ss:lll zz:zz'. For more information, see chapter "SYSTIMESTAMP" in "DocEXEC Reference Application Developer Guide (pdedge)". l New function DATEPICTURE DATEPICTURE returns a date/time format string in a defined format from an input string in 'YYYY/MM/DD hh:mm:ss:lll zz:zz' format. For more information, see chapter "DATEPICTURE" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 255/389 Appendix: main updates in V7.1 l New function DATEPARSE DATEPARSE returns a date/time format string 'YYYY/MM/DD hh:mm:ss:lll zz:zz' created from a date/time format string following an other composition scheme. For more information, see chapter "DATEPARSE" in "DocEXEC Reference Application Developer Guide (pdedge)". l Create Signature Fields in PDF The Sticker command supports creation of signature fields in PDF. Signature fields allow to sign documents with a digital ID. For more information, see chapter "Create signature fields in PDF" in "DocEXEC Reference Application Developer Guide (pdedge)". l New System DocFormat $_CATCHERROR The $_CATCHERROR system DocFormat allows to take action to as soon as an information, warning or error message is displayed. As soon as DocEXEC processes a command that causes such a message, $_CATCHERROR DocFormat is called. Within this DocFormat it is possible to define further actions, for example, display messages or output text. For more information, see chapter "DOCFORMAT command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP8 2015-07-01 l Create JSON Data Structure With JSON Function With the JSON function a JavaScript Object Notation representation (also JSON "document" or JSON "object") can be created from a structured variable. For more information, see chapter "JSON" in "DocEXEC Reference Application Developer Guide (pdedge)". l READLINE Implementation Changed The implementation of the READLINE routine, that can be used for reading additional input data, was improved. In its new implementation READLINE opens files in binary mode instead of text mode, which makes the reading mechanism more robust so that files that contain incorrect line delimiters can not cause erroneous situations anymore. There is, however, one situation where backward compatibility problems might occur: On z/OS native, before the implementation change, READLINE read input data only delimited by record length, independent from whether the input data contained line-delimiting characters. After the change READLINE recognizes such line-delimiting characters. Therefore it is recommended that input data for READLINE on z/OS native should be cleared of line delimiters \n(0x'15'), \r (0x'0d') or \f (0x'0c') (codepage 273). For more information, see chapter "READLINE, READFILE, READCLOSE - secondary input data file access" in "DocEXEC Reference Application Developer Guide (pdedge)". l Improved installation description for z/OS native The installation description for Papyrus DocEXEC on z/OS native was improved and describes the required steps with examples. For more information, see chapter "Installing Papyrus DocEXEC on z/OS native operating system" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l APPLICATION-INPUT-FORMAT and APPLICATION-OUTPUT-FORMAT parameters as line commands Several further parameters of the input format definition and of the output format definition were implemented as command line parameter. New APPLICATION-INPUT-FORMAT line commands: APPINP_FMT, APPINP_DEL, APPINP_RL, APPINP_CC, APPINP_TRC, APPINP_CACHELIMIT, APPINP_OMSCACHE New APPLICATION-OUTPUT-FORMAT line commands: APPOUT_IMAGEMODE, APPOUT_RESGUID, APPOUT_BOUNDEDFONTS, APPOUT_FONTCOMPRESS, APPOUT_VIEWSTICKERS For more information, see chapter "Input format parameters" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)" and "Output format parameters" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". getstartede V7.6 SP3 256/389 Appendix: main updates in V7.1 l Reformat source code The Papyrus Designer menu was enhanced by another entry: "File | Reformat sources...". This option allows you to convert the source code of earlier resource versions (usually DFA, TXT, IMP, INC) into the current version's source format. With the converted source code you can do a file compare of resources that identifies relevant source code differences. For more information, see Papyrus Designer online help. l Correction for images with "white stripes" If you import images with CREATEOBJECT, then images can show "white stripes" on some occasions. With parameter IMAGECELL such white stripes can be avoided. For more information, see chapter "DEIMAGECELL / IMAGECELL" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". 16.2.12 Papyrus Objects (WebControl/WebRepository/IPAS) 16.2.12.1 General l New names of transfer files for system and application frameworks The names of transfer (.TRF) files for system and application frameworks have changed and now use the following syntax: l New document available about Reporting Solution A new document is available that describes the Reporting Solution provided by ISIS Papyrus, which allows you to set up various data sources to use them for the generation of report documents and for query user interfaces called dashboards. For more details, see "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". l Object export/import transfer process enhancements V7.1 SP8 2015-10-29 introduces new class definition properties for translating the visible names of objects and creating complex Struct data types: the two system attributes $ClassUsage and $TranslateName, and the class definition properties for Structs (OmsStruct and OmsStruct with binaries). For more details on translation, see chapter "Provide multiple translations of text" in "WebRepository Application Developer Guide (pwride)". For more details on Structs, see chapter "Define attributes with structured Data (OMS structs)" in "WebRepository Application Developer Guide (pwride)". Once an application starts using these new properties, care must be taken when exporting its objects to younger domains; TRFs containing any objects with these properties will have a different structure that is not recognized by kernels older than V7.1 SP8 2015-10-21. When kernels that do not support the new features attempt to import such TRFs, the error message "POTR0257E Transfer: file So long as a TRF does not contain any objects using the new properties, kernels older than V7.1 SP8 2015-10-21 can still import it. The importing node must be able to handle the specific transfer file version/format, and the target node(s) to which the objects are being deployed must be able to operate the new features. The indicator for the nodes' compatibility with the new features is "45:Handling of ClassUsage, TranslateName and Binary Attributes in structures", which is set in the Supported Features attribute of a Node object. If Objects to import references $ClassUsage, $TranslateName, OmsStruct or OmsStruct with binaries, the importing node as well as the target node(s) must have this feature. getstartede V7.6 SP3 257/389 Appendix: main updates in V7.1 16.2.12.2 Papyrus Depot l PAS Functions Moved PAS functions are used for Depot data retrieval. All PAS functions were moved into class "DiDepot" (the Depot data interface). Previously, they were implemented as methods of the class "Depot Control Center". For details, see chapter "Depot data retrieval" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". Available since DVD V7.1 SP8 2015-07-01 l Improved Configuration of the Immutability of Archived Objects Additional attributes were introduced to exclude certain Depot objects from a change of storage state and/or storage type during Depot check-in. For details, see chapter "Depot check-in with AFP splitter" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". Available since DVD V7.1 SP8 2015-07-01 l Depot Search UI Workplace A new end user workplace based on Papyrus EYE Widgets technology is available to perform search queries on Papyrus Depot. For details, see chapter "Depot search workplace" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". Available since DVD V7.1 SP8 2015-07-01 l Extended Distributed Depot Concept The structure of a Distributed Depot has been extended. Now Depot partitions can be grouped into partition groups. Additionally, partitions of document Depot can be split into index partitions and data partitions. To improve performance it is now possible to create proxy partitions of existing partitions. For details see: "Extended distributed depot concept" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)" and "Structure of a distributed depot" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Depot Collection Now the Depot Control Center of each Depot (DCC or dDDC, respectively) is referenced into Depot Collection. For details see: "Depot collection" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l Simplified Procedure of Distributed Depot Installation The procedure required for the installation of a Distributed Depot has been considerably simplified and now requires less parameter specifications than it used to. For details see: "Installation of a distributed depot" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". l System Management Tools Now Library provides two templates of System management tools which enable the system administrator to delete an empty Standard Depot or an empty partition of a Distributed Depot including all references. For details see: "Deletion of a local depot or depot partition" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". getstartede V7.6 SP3 258/389 Appendix: main updates in V7.1 l Data Interface Class DEPOT (DiDepot) The new data interface class DEPOT (DiDepot) provides a number of methods that allow to access a Depot or to search, insert and update data in a Papyrus Depot. The methods of this data interface class can be used for the definition of user-defined Depot PQLs. For details see: "Depot data interface class" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)". 16.2.12.3 Papyrus Objects l Application Configuration with Settings Explorer The concept description of the Settings Explorer has been revised and extended. For details see: "Papyrus application settings" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". Note: The enhanced views must be activated, to enable the new enhanced Settings Explorer. Invoke therefore the Settings dialog using menu item Options | Settings and activate option Use enhanced views. l New State Machine for Class USER Class USER has been provided with a new state machine. Section "State-related methods for security administrator in WebRepository and WebControl Installation and Administrator Guide (poinste)" explains the resulting methods for Security Administrator. l Notification Framework The Notification Framework enables users to create centrally managed notification definitions that react to system events with predefined actions, e.g. emailing an administrator when a tool or queue throws an error. Each action can be scheduled or event-driven, firing after an arbitrary delay, at an arbitrary point in time or at arbitrary intervals. For details, see chapter "Notification - NTFY Framework" in "WebRepository Application Developer Guide (pwride)". l Ontology This new feature provides a formal representation of a set of concepts within a domain and the relationships between those concepts. It is used to define the domain and to provide a common language and structure as basis for users and tools that require structured semantic information about the domain. For details, see chapter "Ontology" in "WebRepository Application Developer Guide (pwride)". l UTA - User-Trained Agent This patented tool learning from actions performed by the user and creating suggestions for the user has been revised and improved. For details, see chapter "User-trained agent" in "WebRepository Application Developer Guide (pwride)". l Settings and Scope Development for Settings Explorer The Settings Explorer has been revised and improved. To enable the new enhancements, open the Settings dialog from the Options | Settings menu and tick "Use enhanced views". For details, see chapter "Settings & scopes - BASE|Settings Framework" in "WebRepository Application Developer Guide (pwride)". l Edit Properties There are two new keywords for attribute property "Edit Properties": EditMethod() and Methods(). EditMethod( getstartede V7.6 SP3 259/389 Appendix: main updates in V7.1 l Data Type "Struct" Papyrus Objects allows the declaration of struct data types, that may be composed of attributes and methods. The attribute property "Type" has been added the new value "Struct" which designates the new complex data type. More information provides section "Define attributes with structured Data (OMS structs) in WebRepository Application Developer Guide (pwride)". l Property "Class usage" "System attribute" of class editor has been provided with the additional property Class usage which enables to define a class as a struct. More information provides section "Define attributes with structured Data (OMS structs) in WebRepository Application Developer Guide (pwride)". l Language Specific Values of Attributes and Visible Names This new feature introduced in this version allows translation of visible names and attribute values by the user of user interfaces. For details with respect to the class definition see "Provide multiple translations of text in WebRepository Application Developer Guide (pwride)". l Attribute Property "Translate content" The value range of this attribute property is now represented by a combo box instead of a check box. For details see "Attribute properties in WebRepository Application Developer Guide (pwride)" l Object start: Translate name Object start of class editor has been extended by the new property Translate name. This new property is used for the translation of $name in user interfaces. For details see section "Object Start Properties" in "Class editor in WebRepository Application Developer Guide (pwride)". 16.2.12.4 Papyrus Query Language (PQL) l AttrDefKey manipulation functions PQL functions to type-check, convert and construct AttrDefKey values and arrays: $isAttrDefKey(), $toAttrDefKey(), $attrDefKeyArray(), $isAttrDefKeyArray(), $toAttrDefKeyArray(). For details, see "Array functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "Type check functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "Type conversion functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Transaction variable accessor functions PQL functions to define and retrieve variables for the current transaction. For details, see "$getGlobal() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$setGlobal() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $paramDef, $effectiveParamDef New object properties that enable the querying of PQL method parameter definitions. For details, see "Member properties in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l PqlSet bulk update functions PQL functions that facilitate the bulk updating of PQL sets with large amounts of data. For details, see "$fieldIndexes() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$setRecordValuesByIndexes() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$appendArrayToSet() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". getstartede V7.6 SP3 260/389 Appendix: main updates in V7.1 l Relative complement functions Two new functions to calculate the complement of two PQL sets and two arrays, respectively. For details, see "$complement() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$complementArray() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l HMACSHA encryption functions Two new functions that provide encryption within PQL scripts. For details, see "Data encryption & compression functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Struct manipulation functions PQL functions to type-check, convert and create Struct values and arrays. For details, see "Struct functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $modify queries This query keyword allows one to modify a subset of the values in a PQL set. For details, see "$modify in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $vector queries This query keyword creates a one-row PQL set with specified fields. For details, see "$vector in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l PQLPDF function library The new PQLPDF library can be used by any PQL script to generate PDFs from specified resources. For details, see "pqlpdf: Papyrus PQL PDF generator library in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l JSON <--> PqlSet conversion functions Functions that interconvert between a PQL set and a JSON string. For details, see "$pqlToJSONString() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$parseJSON() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Supported PQL features These functions reveal which PQL features are supported by the binaries currently in use. For details, see "$supportedfeatures() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$supportedfeaturedetails() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Timezone location functions These functions reveal which string descriptors are associated with actual timezones. For details, see "$getTimezoneLocations() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$isValidTimezoneLocation() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $currentTransactionID A new system variable that identifies the currently active transaction. For details, see "System variables in WebRepository Application Developer Guide (pwride)". l $isCommonRuleTriggeredForObject() For details, see "$isCommonRuleTriggeredForObject() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". getstartede V7.6 SP3 261/389 Appendix: main updates in V7.1 l Functions to record used objects Functions that indicate which objects were read or modified during a certain period. For details, see "$collectUsedObjectsBegin() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" & "$collectUsedObjectsEnd() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Binary type check functions For details, see "$isBinary() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$IsBinaryRemote() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l ProcAddr type functions Functions that type-check and convert to process addresses. For details, see "$isProcAddr() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)", "$toProcAddr() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Class definition attributes Attributes that characterize the object-orientation of class definitions; they include $abstract, $accessibility, $classUsage & $final. For details, see "System attributes in WebRepository Application Developer Guide (pwride)". l Object access status attributes These system attributes include $viewable, $editable, $lockedForEdit, $modifiedOnNodes. For details, see "System attributes in WebRepository Application Developer Guide (pwride)". l Miscellaneous system attributes $user, $language, $currentTransactionId, $keyValueStorePhysicalGUID. For details, see "System attributes in WebRepository Application Developer Guide (pwride)". 16.2.12.5 Papyrus Resource Collection l Update Resource Groups The ready to use PQL template Update Resource Groups has been updated by adding the attributes Excepted groups and Restricted groups. The Expand setup attribute is now obsolete. For more details, see "Adjust existing Resource Groups using PQL Script" in chapter "Relocating resources from the domain controller to the resource node" in "". 16.2.13 Papyrus Server 16.2.13.1 AFP to PDF l AFP files with IOB structures containing native PDF objects AFP files with IOB structures containing native PDF objects are resolved in the generated PDF output as native PDF structures providing better quality and reducing the PDF output file size. Former Papyrus Server AFP to PDF versions converted IOB-embedded PDF objects into images. The native PDF representation was implemented on all platforms (Windows and UNIX) except for z/OS (USS and native). IOB structures with native PDF are created by means of the DocEXEC command CREATEOBJECT IOBDLL(IOBDEFS) in the AFP file to be converted. l Signature Field from sticker (EmptySignatureStickers) new attribute/parameter This parameters allows to create from Sticker definitions in AFP empty signature fields in PDF. These signature fields can be filled by a user within Adobe Reader 11 or newer. For details, see chapter "Signature Field from sticker (EmptySignatureStickers)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)" and "Create signature fields in PDF" in "DocEXEC Reference Application Developer Guide (pdedge)" Available since DVD V7.1 SP8 2014-11-18 getstartede V7.6 SP3 262/389 Appendix: main updates in V7.1 l Configuration files as binary objects in Papyrus Objects Ini files, mapping tables, signature, configuration files and other similar ASCII files can now be stored either in the file system or as binary objects in Papyrus Objects. The configuration is based on 3 attributes: a switch, which tells the system which version to use, an attribute that points to a location in the file system and an attribute that points to a binary object. It has been implemented for Font substitution table in Papyrus Server - AFP to PDF Reference Guide (psepdfrge), Font substitution tables - TTF in Papyrus Server - AFP to PDF Reference Guide (psepdfrge), Viewer preferences profile in Papyrus Server - AFP to PDF Reference Guide (psepdfrge) and Digital signature files in Papyrus Server - AFP to PDF Reference Guide (psepdfrge). Available since DVD V7.1 SP8 2015-07-01 l PDF Linearization (PDFtLinear) has been renamed to Fast Web View Fast Web View restructures a PDF document for page-at-a-time downloading from web servers. This allows to immediately view the first pages of a PDF document whilst the remaining pages are being downloaded. For details, see chapter "Fast Web View (PDFtLinear)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Medium OVL to PDF layer (PdftLayers) new attribute/parameter Medium OVL to PDF layer (PdftLayers) controls the conversion of medium OVL(s) into switchable PDF layer(s). For details, see chapter "Medium OVL to PDF layer (PdftLayers)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP8 2015-10-29 l MP4 player files (PdftSwfFilesForMP4) new attribute/parameter MP4 player files (PdftSwfFilesForMP4) defines a flash player and a "skin" for operating the player. The MP4 file itself is defined as flash sticker. For details, see chapter "MP4 player files (PdftSwfFilesForMP4)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP8 2015-09-14 l PDF attachments new attributes/parameter PDF attachments can be of any data type and are embedded as stream objects. Thus you can add a PowerPoint presentation, Excel spreadsheet, a video or whatever you desire to your PDF. For details, see chapter "PDF attachments" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP8 2015-09-14 l Metadata from Index (PDFtMetaData) new attribute/parameter Metadata from Index (PDFtMetaData) allows to create PDF metadata from an AFP index (TLE). For details, see chapter "Metadata from Index (PDFtMetadata)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP8 2015-10-29 l Rich Text Format enabled prompts It is now possible to use the Form Field Text Properties in Adobe Acrobat Reader to change the formatting (font type, size, color,...) of the text entered into a text prompt. For details, see chapter "Generate Prompts (PDFtGenPrompts)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP8 2016 l Disable scrollbars for multiline fields (PdftScrollMultilineFields) new attribute/parameter This attribute (parameter) defines whether Multiline textfields are generated with the ability to scroll. For details, see chapter "Disable scrollbars for multiline fields (PdftScrollMultilineFields)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP8 2016 getstartede V7.6 SP3 263/389 Appendix: main updates in V7.1 16.2.13.2 HTML l Configuration files as binary objects in Papyrus Objects Ini files, mapping tables, signature, configuration files and other similar ASCII files can now be stored either in the file system or as binary objects in Papyrus Objects. The configuration is based on 3 attributes: a switch, which tells the system which version to use, an attribute that points to a location in the file system and an attribute that points to a binary object. It has been implemented for HTML font substitution in Papyrus Server - HTML Reference Guide (psehtmlrge). Available since DVD V7.1 SP8 l New Tips in the Troubleshooting Section Solutions for: Automatic Highlight on iOS having undesired effects on Formatting, A HYPERLINK image does not navigate to the target URL in Firefox and AFP text loses the boldface/italic style when converted to HTML. Details can be found in the chapter Troubleshooting in Papyrus Server - HTML Reference Guide (psehtmlrge). Available since DVD V7.1 SP8 16.2.13.3 PCL l Formdef count for reprint offset (CountFDF) new attribute/parameter The attribute allows to calculate a more precise offset for re-print. For more details, see chapter "Formdef count for reprint offset (CountFDF)" in "Papyrus Server - PCL Reference Guide (psepclrge)". Available since DVD V7.1 SP7 2014-07-11 (ICD) Available since DVD V7.1 SP8 (PO) l Configuration files as binary objects in Papyrus Objects Ini files, mapping tables, signature, configuration files and other similar ASCII files can now be stored either in the file system or as binary objects in Papyrus Objects. The configuration is based on 3 attributes: a switch, which tells the system which version to use, an attribute that points to a location in the file system and an attribute that points to a binary object. It has been implemented for Color mapping table in Papyrus Server - PCL Reference Guide (psepclrge) and Font mapping table in Papyrus Server - PCL Reference Guide (psepclrge). Available since DVD V7.1 SP8 16.2.13.4 PDF-in l Use Unicode Output (PINUseUnicodeOutput) This parameter influences how AFP fonts are created. If the AFP is further converted to HTML using unicode fonts eases that process. For more details, see chapter "Use Unicode output (PINUseUnicodeOutput)" in "Papyrus PDF-in Reference Guide (ppdfinrge)". l Do not generate text (PINtakeoffTxt) Do not generate text (PINtakeoffTxt) allows to skip the text generation for the Overlay generation of a PDF page. This eases the handling of PDF Forms. All Overlay parameters are now handled within one tab. For details, see chapter "Do not generate text (PINtakeoffTxt)" in "Papyrus PDF-in Reference Guide (ppdfinrge)". Available since DVD V7.1 SP8 2015-11-30 getstartede V7.6 SP3 264/389 Appendix: main updates in V7.1 l Resource ID Generator As of this version Resource ID Generator in System Collection is used by default for the generation of unique names for fonts and images created by PDF-in server into the Resource Collection instead of Printer Driver which still can be used (backward compatibility). For details, see chapter "Font names in Papyrus WebRepository" in "Papyrus PDF-in Reference Guide (ppdfinrge)" and "Page segment names in Resource Collection" in "Papyrus PDF-in Reference Guide (ppdfinrge)". l Convert Bookmarks through PQL (PINBookmarksPqlScript) This option of parameter PINGetPdfIndex allows to convert the bookmarks of a PDF into AFP TLE or page indices by means of a customizable PQL script. This feature is available in Papyrus WebRepository and batch mode. For details, see chapter "Convert Bookmarks Through PQL" in "Papyrus PDF-in Reference Guide (ppdfinrge)". 16.2.13.5 Postscript l Formdef count for reprint offset (CountFDF) new attribute/parameter The attribute allows to calculate a more precise offset for re-print. For more details, see chapter "Formdef count for reprint offset (CountFDF)" in "Papyrus Server - PostScript Reference Guide (psepsrge)". Available since DVD V7.1 SP7 2014-07-11 (ICD) Available since DVD V7.1 SP8 (PO) 16.2.14 OverView AFP Designer l Updated application developer guide The whole documentation has been reworked and the new structure supports users in finding their topics quickly. Updated chapters with step-by-step instructions helps users to perform their tasks easily and targeted. For details, see chapters "Creating and editing overlays" in "AFP Designer Online Help (OVERVENG)" and "Creating and editing PPFA objects" in "AFP Designer Online Help (OVERVENG)". 16.2.15 OverView Image Editor l Updated dialog for changing colors into highlight colors An updated mapping feature helps users to change all non-highlight colors according to the highlight base color definition into highlight colors. For details, see chapter "Change color to highlight dialog" in "Image Editor Reference Guide (oierge)". l Enhanced functionality to shade images Images and also text can be shaded with a user-defined transparency. For details, see chapter "Shading images" in "Image Editor Online Help (O_IE_ENG)". l Close all images at once A new feature enables users to close all open images with one single mouse click. For details, see chapter "File | Close all" in "Image Editor Reference Guide (oierge)". l New chapter with practical user instructions A new documentation chapter with numerous step-by-step instructions helps users to perform their tasks easily and targeted. For details, see chapter "Editing images" in "Image Editor Online Help (O_IE_ENG)". getstartede V7.6 SP3 265/389 Appendix: main updates in V7.1 16.3 Main updates in V7.1 SP7 16.3.1 General changes This DVD includes Papyrus products in release level V7.1 SP7. In order to identify the service pack more clearly the new notation "V7.1 SP7" was introduced, which reads as follows: V Papyrus Server Topcall Fax no longer shipped As Papyrus Server Topcall Fax is no longer shipped as of release level V7.1 SP7, the publication of the "Papyrus Server - Fax Reference Guide (psefaxrge)" document will be discontinued as well. getstartede V7.6 SP3 266/389 Appendix: main updates in V7.1 16.3.2 Papyrus business user interfaces in V7.1 SP7 In V7.1 SP7, the ISIS business user interfaces based on Papyrus EYE Widgets have been generally redesigned to meet the requirements of business users. With this redesigned interfaces, business users find it easier and more intuitive to do their daily work. The redesign is part of a wider UI initiative to standardize ISIS business user interfaces and to address User Experience from a holistic point of view of the business user. In a first step of the initiative, the graphical user interface was redesigned in a flat style as opposed to a 3-D-style. Flat style helps to consider accessibility aspects as specified by W3C because it supports better distinction of available GUI elements and the color contrast improves recognizability of text and elements. The following screenshots highlight the main items that were redesigned: (1) Color background The consistent white background contributes to a balanced perception of the view. Colored background is only used in the tab bars to separate the active tab from inactive tabs. (2) Clickable elements The color blue is used as base color so that users are able to immediately identify which elements can be clicked or used for actions, whereas information text and activated items (like the main tab in the picture) are colored in dark grey. (3) Visibility of splitter The splitter is well recognized because of its shape, coloring and a dedicated grip area, vertically and horizontally, and easy to handle. getstartede V7.6 SP3 267/389 Appendix: main updates in V7.1 (4) Color contrast The colors that are used on different backgrounds fulfill the accessibility requirements (W3C) for the level AA. Users with color vision deficiency will be able to work with this UI without any problems. (5) Toolbar The toolbar of ISIS Plugins like the Papyrus Client Canvas uses also a white background. Thus, all buttons are better recognized. The toolbar and its content can easily be distinguished due to the grey frame around the toolbar. 16.3.3 ISIS installation routine l Use "uninstall.exe" for manual or silent uninstallation For a manual or silent uninstallation of Papyrus products, use uninstall.exe (instead of setup.exe) in the \install directory. For more details, see chapter "Uninstalling Papyrus products" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2015-05-18 l New option for installation in additional environment available In the Papyrus Installation Routine, you can select the option Install | Products in additional environment to create an isolated installation of Papyrus products for test and demo purposes that does not affect an existing installation. For a regular installation, confirm the default selection Install | Products in standard environment. For more details, see chapter "Installing products in an additional environment" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". l New color design of the Papyrus Installation Routine The Papyrus Installation Routine features a new graphical design with a modern "flat" style. For more details, see chapter "Papyrus Installation Routine" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-07-11 getstartede V7.6 SP3 268/389 Appendix: main updates in V7.1 l Hardlock Key driver installation The incl. Hardlock Key driver check box is not selected by default in the Papyrus Installation Routine anymore. If the IPAS is installed, the Hardlock Key driver is also automatically installed. For more details, see chapter "Including Hardlock Key driver" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-03-20 l Option to create network installation removed The Create network installation option was removed from the Papyrus Installation Routine. ISIS Papyrus products must be executed from a local drive. For more details, see chapter "Selecting target path for installation" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-03-20 l Option to select authorization mode available A new option to set authorization mode to IPAS or to Hardlock Key is available in the Papyrus Installation Routine. It is used for setting the ISIS_KEY_MODE environment variable automatically during installation. For more details, see chapter "Selecting authorization mode" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-03-20 l ISIS_KEY_MODE set automatically during installation The ISIS_KEY_MODE environment variable is set automatically in the background during installation and not prompted in the Papyrus Installation Routine anymore. The variable is set to ONLYOMS for product installations and to ALL for IPAS installations. For more details, see chapter "Setting environment variables" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-03-20 l ISIS_USE_PCSLOG set to 2 automatically during installation The ISIS_USE_PCSLOG environment variable is set to 2 automatically in the background during installation. For more details, see chapter "Environment variables" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-03-20 l Installation ID file to avoid version check Information on using a special installation ID file (isis_id_no_versioncheck.id) to avoid version check during installation is available. For more details, see chapter "Installing products of a previous version" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Description available since DVD V7.1 SP7 2014-03-20 l PCS64HELPER tool available ISIS provides PCS64HELPER, a Windows console tool that helps determining if setting a maximum system file cache size fixes performance problems. For more details, see chapter "Setting a maximum system file cache size limit to fix performance problems" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-03-20 l Hard-coded default value of ISIS_USE_PCSLOG is 2 for all products For the ISIS_USE_PCSLOG parameter, the hard-coded default value of 2 is defined for all Papyrus products. This default value means that all logs are written to the central PCS log file. For more details, see chapter "Environment variables" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". getstartede V7.6 SP3 269/389 Appendix: main updates in V7.1 16.3.4 ISIS product installation l Modifying Papyrus Browser Plugin MSI files The description was updated to explain how to edit browser plugin MSI files with an MSI database table editor in order, for example, to add components to the MSI file. For more details, see chapter "Configuring MSI installer files" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Description available since DVD V7.1 SP7 2014-08-11 16.3.5 ISIS Product Authorization Service l Hypertext links in PDF document to IPAS tutorials The IPAS tutorials on installation and administration of the IPAS can be opened directly from the PDF document when you click the hypertext links. For more details, see chapter "About this document" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-08-11 l Setting Unix access rights The information on how to set user, directory, and file rights on Unix was updated and extended. For more details, see chapter "Unix access rights" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Description available since DVD V7.1 SP7 2014-07-11 l Setting environment variables on z/OS Native New information is available on how to enclose lines with hex'00' values. For more details, see chapter "IBM C++ compiled products" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Description available since DVD V7.1 SP7 2014-07-11 l Product authorization on z/OS native: recommended ISIS_KEY_MODE settings When using product authorization on z/OS with IPAS, set ISIS_KEY_MODE=ONLYOMS. When using z/OS native product authorization, set ISIS_KEY_MODE=ALL. For more details, see chapter "Product authorization on z/OS native" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Description available since DVD V7.1 SP7 2014-05-21 l New chapter on authorization in remote access environments This chapter provides information on authorization aspects when Papyrus products are installed on a server but accessed from a client. For more details, see ""Authorizing Papyrus products with concurrent authorizations in remote connection environments" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Description available since DVD V7.1 SP7 2014-05-21 l Dedicated option to install the Papyrus Desktop of IPAS only A new installation option to install only the Papyrus Desktop of IPAS is available. The other options to install the IPAS on each platform provide installation without the Papyrus Desktop of IPAS. For more details, see chapter "IPAS and Papyrus Desktop of IPAS" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-03-20 getstartede V7.6 SP3 270/389 Appendix: main updates in V7.1 l Allowed characters for attributes For Allowed requesters and Forbidden requesters attributes, additional information such as allowed characters is provided. For more details, see chapter "Concurrent authorizations: Defining Requester Groups" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Description available since DVD V7.1 SP7 2014-03-20 l New location of offline program authorization files The offline program authorization files offlicw3.exe and offlicw3.icd can now be found under \ISIS\Tools\win\offlic. For more details, see chapter "Offline product authorizations" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". Available since DVD V7.1 SP7 2014-03-20 16.3.6 Papyrus Adaptive Case Management solution 16.3.7 Papyrus Automated Document Factory Solution l Print and E-Delivery Solution The Automated Document Factory has been enhanced by the Print and E-Delivery Solution. This enhancement allows handling of outbound channels (output channels) in a centralized way. The Print and E-Delivery Solution is an extension of various solutions and can not only be combined with ADF but also with the Business Correspondence solution, for example. For details, see chapter "Print and E-Delivery" in "". Available since DVD V7.1 SP7 2014-03-20 16.3.8 Papyrus Business Correspondence Solution The V7.1 SP7 release contains the following main enhancements: l Support for different Graphical User Interface's (GUI) based on industry standard's l Initiative GUI's that are focused on improving business user productivity l Common look and feel for all business user workplaces l Fully integrated goal-orientated Change Management solution based on Adaptive Case Management (ACM) l Ability to mirror a business organization using Tenant and Scope Settings within Papyrus Objects l Support for third party change management solutions l Configurable release management process allowing for flexible extensions to be applied l Scheduling of the activation process of a release l Support for multiple test stages and production hot-fixes l Scope settings providing configuration at different heirarcchy levels l Separation between business users using roles and policies ensuring security l Potential for work group development l Use of impact analysis highlighting the consequence of development changes l Ability to preview and execute document test simulations based on default data l Support for different data standards and interfaces l Creation and use of dynamic data within correspondence allowing personalization l Controlling Logic constructs within correspondence l Standard set of document and building block templates enabling re-useability l Automation of document creation by using wizards l Fully supportable language variants in the correspondence and the workplace l Management of correspondence using standard delivered workflows l Long-term archive and retrieval to support legal and customer requirements l Adaptable workflows allowing the business user to select different workflows l Support and inclusion for all data types within correspondence l Inclusion of inserts, attachments and support for different delivery options l Extendable functionality based upon the Correspondence Framework getstartede V7.6 SP3 271/389 Appendix: main updates in V7.1 16.3.9 Papyrus Business Document Capture Solution In the first release of version v7.1SP7 Papyrus Business Capture Solution comes forward with two significant modifications. l Capture Solution User Interfaces Just like all other Papyrus frameworks that include graphical user interfaces Capture GUIs now present a quite different look in comparison to version v7.16. The base color of all views changed from green to blue now offering better contrast. Additionally, the design of EYE Widgets applications changed to "flat style" design, i.e. reduced forms of objects and there are no more 3D components. The reduced design facilitates orientation on the user interface and thus the user can work more efficient. For details see the corresponding ISIS documents "Papyrus Client - Capture User Guide (popcfuge)" and "Capture Scan Administrator and User Guide (poscanauge)". l New Data Structure of Capture Results In this version Capture Solution adopted a quite different data structure for Capture Result Elements. Until version v7.17 the extraction results have been stored for each field in an object of its own, the Capture Result Element. Now the results are stored as memory buffer in a single PQL set providing a row for each result field. This changes of the data structure comes along with a considerable improvement of performance. To ensure backwards compatibility the old way of result data storage is still available as settings attribute "Capture Result Storage" = "1: Capture Result Element" while the new storage mode is "Capture Result Storage" = "2: Capture Result Storage" which also is the default setting for this attribute. For details see section Capture document in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). l New Core Validation Source The source values of Core Rule validation now are stored in attributes of Elements in Element Folder of the document definition instead directly in the attributes of the Core Rule of an element. This change also results in better performance of validation. For backwards compatibility the old way of Core Rule validation via Core Rule attributes is still available as settings attribute "Core Rule Validation Source" = "1: Common Rule" whereas the new mode requires the setting "Core Rule Validation Source" = "Element Definition". For details see section "Core Rule Validation" in chapter "Common rules and validation" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Custom Rule Development A new chapter "Custom Rule Development" has been added. This chapter provides information for the Capture Developer concerning the development of Custom Rules for categories of a Capture Solution. For details see: Custom rule development in WebRepository - Capture Solution Administrator and Developer Guide (popcfade). getstartede V7.6 SP3 272/389 Appendix: main updates in V7.1 16.3.10 Papyrus Reporting Solution The Reporting Solution provided by ISIS allows to set up various data sources (external database, PQL, CSV, etc.) to use them for the generation of report documents and for end-user friendly query user interfaces, called dashboards (e.g. to get all transactions of a certain customer). The solution comes with a fully integrated user interface based on Papyrus EYE Widgets. For details, see "WebRepository - Reporting Solution Administrator, Developer and User Guide (rpaduge)". 16.3.11 Papyrus Targeted Messaging Framework l New UI design for the Targeted Messaging Management workplace The Targeted Messaging Management workplace now uses the newly developed flat graphical user interface design language with a blue base color. The new design improves accessibility and makes user interaction simpler and more efficient. For more details, see "Papyrus Client - Targeted Messaging User Guide (potarmuge)". Available since DVD V7.1 SP7 2014-07-11 l Enhanced attachment type support for attachment messages Attachment messages can now additionally use attachment types PDF or CANVAS. Previously, only PSG, JPG, TIF and OVL were available. PDF attachments are embedded directly into the AFP data stream. CANVAS attachments can be edited directly on the screen. For more details, see chapter "PDF attachment messages" in "WebRepository - Targeted Messaging Framework Developer and Administrator Guide (potarmdage)" and see "Papyrus Client - Targeted Messaging User Guide (potarmuge)". Available since DVD V7.1 SP7 2014-07-11 16.3.12 Papyrus Analysis Toolkit l Edit/Merge Functionality of PUC Classes As of V7.1 SP7 Papyrus Universe Compare classes (except for UC COMPARE AFP CANVAS) enable edit and merge of items of compared objects provided certain conditions are met. For details see: "Edit/Merge functionality of PUC classes" in "Analysis Toolkit Application Developer Guide (pandge)". Available since DVD V7.1 SP7 2014-03-20 l Papyrus PDF Compare As member of the Papyrus Analysis Toolkit the new tool Papyrus PDF Compare is now available. It's design is very similar to Papyrus AFP Compare enabling to compare two input PDF documents. A graphical user interface helps to provide the required parameters and displays the differences in two windows. There are also implementations for batch as well as Papyrus Objects. For details see: "Papyrus PDF Compare" in "Analysis Toolkit Application Developer Guide (pandge)". 16.3.13 Papyrus Client AFP Viewer l Display of PDF files included in AFP file Papyrus AFP Viewer is able to display PDF files that are included in an AFP file. The PDF files are referenced from within the AFP by means of the Include Object (IOB) structured field. Available since DVD V7.1 SP7 l Usage of Stylesheets You can use stylesheets for the appearance of your GUI elements either by loading a predefined CSS file or by designing your own stylesheet definition. For details, see the parameters "StyleSheet" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)" and "StyleSheetEditor" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". Available since DVD V7.1 SP7 2015-02-09 getstartede V7.6 SP3 273/389 Appendix: main updates in V7.1 l New dialog to open files In addition to opening an AFP file, in the new dialog under File|Open you can also open an overlay or change settings such as resource library, resolution or codepage. For details, see chapter "Menu bar" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". l Enhanced user interface Several items of the graphical user interface (button names, tooltips, toolbar names, windows) were adapted to support users with a more intuitive interface. Available since DVD V7.1 SP7 2014-05-21 l Print with copy control The Print toolbar contains the new Print with copy control button, which enables the user to perform advanced settings as paper tray selection and copy control for different Copygroups when printing AFP documents. For details, see chapter "Print toolbar" in "Papyrus AFP Viewer Freeware Installation and Reference Guide (pavfirge)". Available since DVD V7.1 SP7 2014-05-21 l List with GUI element names The document was enhanced with a list of GUI element names that helps the administrator to hide or disable GUI elements that shall not be available for the business user. For details, see chapter "GUI element names" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". 16.3.14 Papyrus Client Document Creation (Canvas) l Usage of Stylesheets You can use stylesheets for the appearance of your GUI elements either by loading a predefined CSS file or by designing your own stylesheet definition. For details, see the parameters "StyleSheet" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)" and "StyleSheetEditor" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". Available since DVD V7.1 SP7 2015-02-09 l New parameter UseStickerFile By setting this parameter can be defined, if the stickers provided in the passed sticker file are generated into the AFP file. For details, see chapter "UseStickerFile" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2015-02-09 l New parameter IgnoreStickerOutputDefinition By setting this parameter can be defined, that stickers should also be displayed in the generated PDF files. For details, see chapter "IgnoreStickerOutputDefinition" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2015-02-09 l New parameter CommentCreate This parameter defines the RGB colors that users can select for their text-based stickers (comments). For details, see chapter "CommentCreate" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2015-02-09 getstartede V7.6 SP3 274/389 Appendix: main updates in V7.1 l Text-based stickers Stickers can be defined relative to the text they are associated with. If the related text is moved to another position, the sticker position will change as well. For details, see chapter "Sticker" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2014-10-28 l Enhanced user interface Several items of the graphical user interface (button names, tooltips, toolbar names, windows) were adapted to support users with a more intuitive interface. Available since DVD V7.1 SP7 2014-05-21 l Insert images into text input fields Images from the file system can be inserted into a text input field with the Insert image button. This button opens the Image properties dialog, which was extended with a Files tab for inserting images from the file system. For details, see chapter "Text input toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2014-03-20 l Extended table properties The Table properties dialog was extended and now offers on three different tabs various properties for specifying line color, line thickness, background color, or alignment of the table. Additionally, these setting can also be defined separately for the table cell. For details, see chapter "Text input toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2014-03-20 l New buttons in the Font toolbar The following buttons were integrated in the Font toolbar for offering more formatting possibilities to the user: - Strikethrough - Double underline For details, see chapter "Font toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2014-03-20 l Print with copy control The Print toolbar contains the new Print with copy control button, which enables the user to perform advanced settings as paper tray selection and copy control for different Copygroups when printing AFP documents. For details, see chapter "Print toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2014-05-21 l Structured variables Structured variables can contain multiple other variables, other structured variables or array. They can be used for variables generated out of XML data to reflect the same hierarchical structure. For details, see chapter "Variables window" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". Available since DVD V7.1 SP7 2014-03-20 l New Parameter SHOWERRORSONSTRIPE This parameter enables the administrator to display a pink banner also in case of normal errors. By default, it is displayed only in case of fatal errors. For details, see chapter "Controlling the display of error messages" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". getstartede V7.6 SP3 275/389 Appendix: main updates in V7.1 l List with GUI element names The document was enhanced with a list of GUI element names that helps the administrator to hide or disable GUI elements that shall not be available for the business user. For details, see chapter GUI Element Names. 16.3.15 Papyrus Designer and Server - FixForm l Improved barcode recognition For the recognition of Code128, EAN13, EAN8 and UPCA barcodes, the new attributes "Code128 tolerance" and "EAN/UPCA tolerance" were implemented. For details, see chapter "Barcode" in "Designer Capture Application Developer Guide (pcddge)". Available since DVD V7.1 SP7 2014-09-02 16.3.16 Papyrus Designer, Papyrus DocEXEC l Output format parameter: STICKERNUMBERING This parameter adds a number to the generated stickers that will be visible in front of the sticker text, and defines the used type of numbering. For more information, see chapter "STICKERNUMBERING" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP7 2015-03-04 l V620_COMP_TEXT_FORMAT_IF_CONTINUE backward compatibility parameter Switches the default for formatting TEXT commands with set CONTINUE option back to the behaviour of early 6.20 Papyrus DocEXEC versions. Early 6.20 versions of Papyrus DocEXEC used to format the content of a TEXT command with CONTINUE after execution of each TEXT command. Since a change in 6.20, Papyrus DocEXEC versions have been formatting the contents of such TEXT command conglomerates not until the last TEXT command is closed and executed. For more information, see chapter "DEV620_COMP_TEXT_FORMAT_IF_CONTINUE / V620_COMP_TEXT_FORMAT_IF_CONTINUE" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l Barcode height calculation improved The algorithm for creating Code 128 barcode with the BAROBJ DLL was optimized. Height calculation is now completely independent from HRI definition and font size. As this improvement can cause deviating results for Code 128 printing in present applications customers are asked to check those applications that use CREATEOBJECT BAROBJ with the CODE128 barcode routine and make sure whether the results achieved with Papyrus Designer/DocEXEC versions since V7.1 SP7 (2014-10-16) are acceptable. For more information, see chapter "Incompatibilities in V7.1 SP7" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l TESTPAGE parameter This parameter takes effect if Papyrus DocEXEC is run with test authorization. A supplement to the TESTSTRING and TESTMODE parameter, TESTPAGE specifies whether the "Test" string is placed randomly on the pages of the documents or on each page. For more information, see chapter "Testpages (TESTPAGES) / TESTPAGES" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.1 SP7 2014-03-20 l DEENVIRONMENT parameter The description of parameter DEENVIRONMENT, which allows to pass environment variables to Papyrus DocEXEC, was improved. The description provides a list of specification examples. For more information, see chapter "Environment variables (DEENVIRONMENT)" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". getstartede V7.6 SP3 276/389 Appendix: main updates in V7.1 l Create PieceInfo entries in PDF files With a particular specification of INDEX and GROUPINDEX it is possible to create PieceInfo entries in PDF. Such entries are used to build page-piece dictionaries that hold private data in the PDF file. For details, see chapter "INDEX and GROUPINDEX at PDF creation" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2015-04-20 l Enhancement of APPLICATION-OUTPUT-FORMAT command: VIEWSTICKERS The commands that define the default and alternative AFP output, APPLICATION-OUTPUT-FORMAT and DEFINEOUTPUT, were enhanced by a parameter that allows to make a selection among the stickers that should be written into the AFP. The parameter specifies the colors of the stickers to be written into the AFP. For details, see chapter "APPLICATION-OUTPUT-FORMAT command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2015-02-11 l Enhancement of TEXT and TEXTPROMPT sub command: _LINK The _LINK command supports another keyword for creating comments. These comments stick to the text in case the position of the text changes. For details, see chapter "Defining a comment to a Textprompt with _LINK" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-12-03 l New system variables: $LP_XPOS, $LP_YPOS These variables contain the horizontal respectively vertical position of the current LOGICALPAGE in PELs. For details, see chapter "Miscellaneous system variables and contents" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-09-24 l ENDGROUP: specification of both COPY and FLUSH Both COPY and FLUSH can now be specified for the same ENDGROUP command so that not only the document pages of the primary output channel but also the pages of the document copies can be flushed. Prior versions only allowed either one or the other. For details, see chapter "ENDGROUP command" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-07-11 l Background images for QR barcode The QR barcode creation function allows import of PSEG, JPEG or TIFF images. These images serve as background image for the barcode depiction. Three parameters, ImageFileName, ImageObjectType and BarcodeQuality, specify the image to be imported, its format and the degree of predominance of barcode pattern over image. For information on how to import QR barcode background images, see chapter "CREATEOBJECT QR(QR)" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-07-11 l New TEXT sub command: STRIKETHROUGH The STRIKETHROUGH command allows text to be formatted in a style in which characters are crossed out by a single or double horizontal line. For details, see chapter "STRIKETHROUGH" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l Enhancement of TEXT sub command: UNDERLINE The UNDERLINE command now also supports text to be underscored with double lines. For details, see chapter "UNDERLINE" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 getstartede V7.6 SP3 277/389 Appendix: main updates in V7.1 l New function FIELDSOF FIELDSOF returns the number and the names of a structured variable's fields. For details, see chapter "FIELDSOF" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l New function TYPEOF The TYPEOF function returns the type of the variable. Often used to determine the type of a structured variable's fields. For details, see chapter "TYPEOF" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l Structured variables Structured variables come into effect in the Variable Window of Papyrus Client Canvas. They are a means for the visual representation of the hierarchical relation of variables and display these relations in form of an expandable tree. For information on how to declare such variables, see chapter "Create structured variables" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l New function EXISTENV Checks whether or not an environment variable exists. Returns 1 if the environment variable is present, 0 if not. The former method for checking whether an environment variable is present was using a condition in combination with function ENVIRONMENT: IF ENVIRONMENT('VAR')<>'VAR'. This method delivered correct results in most cases. However, if the value of the environment variable was also the name of the variable, then this method failed. For details, see chapter "EXISTENV" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l New barcode type AZTEC The Papyrus Designer Invoke DLL dialog (DOCDEF CREATEOBJECT command) calling the AZTEC library supports creation of 2-D AZTEC barcode. For details, see chapter "CREATEOBJECT AZTEC(AZTEC)" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l New barcode type GS1_128 The Papyrus Designer Invoke DLL dialog (DOCDEF CREATEOBJECT command) calling the BAROBJ library supports creation of GS1_128 barcode. For details, see chapter "CREATEOBJECT BAROBJ" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l Pattern color support for barcodes Color support was implemented for all barcode types that can be created with the Papyrus Designer Invoke DLL dialog (DOCDEF CREATEOBJECT command). That is all one-dimensional barcode types that can be created with the BAROBJ DLL and all two-dimension barcode types created by ATZEC, DATAMATX, MAXICOD, PDF417 and QR DLL. All of these libraries have an additional COLOR parameter allowing pattern color definition for the barcode. Any regular color definition format is supported, for example, RGB( getstartede V7.6 SP3 278/389 Appendix: main updates in V7.1 l Width specification for Data Matrix barcode The Papyrus Designer Invoke DLL dialog (DOCDEF CREATEOBJECT command) calling the DATAMATX library supports creation of 2-D Data Matrix barcode. The additional parameter BARCODEWIDTH allows to define the edge length of the barcode symbol in millimeters. For details, see chapter "CREATEOBJECT DATAMATX(DATAM)" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l Color remapping for monochrome pagesegments The subroutine IOBDEFS of IOBDLL library, which can be invoked by Papyrus Designer Invoke DLL dialog (DOCDEF CREATEOBJECT command), allows import of images such as pagesegments, TIFF, JPEG and PDF. With the additional parameter REMAPCOLOR is it possible to remap the color of monochrome pagesegments at import. Any regular color definition format is allowed, for example, RGB( l Transparency for images The subroutine IOBDEFS of IOBDLL library, which can be invoked by Papyrus Designer Invoke DLL dialog (DOCDEF CREATEOBJECT command), supports image transparency. The additional parameter TRANSPARENCY allows or suppresses transparency for the imported image. Prerequisite is that the image has transparency mask defined (a transparency flag set). For details, see chapter "CREATEOBJECT IOBDLL(IOBDEFS)" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l Import of PDF files into AFP The Papyrus Designer Invoke DLL dialog (DOCDEF CREATEOBJECT command) calling the IOBDLL library supports import of multi-page PDF into AFP. The library has been enhanced with the IOB_INFO routine with allows to analyze the PDF file in a first step and then import the file with IOBDEFFS routine in a second step. PDF import work similar to the import of multi-page TIFF files. For details, see chapter "CREATEOBJECT IOBDLL" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l Space break handling according to general rules for DBCS and SBCS fonts The space break handling in TEXT command was changed so that it follows the general rules for DBCS and SBCS fonts. As this change requires implementation of additional calculation and filtering algorithms performance decreases can be observed in particular situations, for example when printing Asian language text. Contrary to V7.16, Papyrus DocEXEC versions of V7.1 SP7 have significantly better performance when it comes to printing Asian language text consisting of DBCS or mixed SBCS/DBCS fonts. For details, see chapter "SPACEBREAK" in "DocEXEC Reference Application Developer Guide (pdedge)". Available since DVD V7.1 SP7 2014-03-20 l Create text entries with multiple lines in barchart legends The MultiLineTexts option of barcharts, which allows to display descriptive text with multiple lines, was enhanced by a third parameter. This parameter controls how text with multiple text should be displayed in the chart legend. Before, the option only controlled the text display next to the chart axes. For details, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 279/389 Appendix: main updates in V7.1 16.3.17 Papyrus FontConverter l Asian Composite font conversion support Papyrus FontConverter supports the conversion of Asian composite fonts. With the Use composite font check box in the Options dialog, AFP font creation from Asian composite fonts is optimized. For details, see chapter "Options dialog" in "FontConverter Online Help (fc)". l Magnetic Ink Character Recognition (MICR) font support Papyrus FontConverter supports the conversion of MICR fonts. With the Use MICR flag check box in the Options dialog, AFP fonts can be created that are designed for MICR applications. For details, see chapter "Options dialog" in "FontConverter Online Help (fc)". Available since V7.1 SP7 2014-3-20 16.3.18 Papyrus Host l CICS - Papyrus Host communication sample added A sample was added to the CICS sample library that demonstrates the communication of a customer's CICS program which calls Papyrus Host in order to start a Papyrus DocEXEC formatting process and write the output back into a VSAM table. The involved sample members are contained in the PPHFM710.CICSSAMP dataset of the DVD delivery. For more information, see chapter "Communication customer system with Papyrus Host" in "Papyrus Host Administrator Guide (phfage)". getstartede V7.6 SP3 280/389 Appendix: main updates in V7.1 16.3.19 Papyrus Objects (WebControl/WebRepository/IPAS) 16.3.19.1 Papyrus Objects l New method properties and system attributes V7.1 SP7 2014-07-21 introduces the two class definition properties $ExecuteWithOmsAccount and $ExecuteWithOmsAccountScript which are used for method execution by a different user. For more details, see chapter "OMS account - Execute methods with different role or user" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". As soon as these components come into operation the storage version of the Object Space that owns such objects increases (to 801). This handling plays a key role in introducing future system functionality. TRFs that contain objects using the new method properties can not be imported by kernels older than V7.1 SP7 2014-07-21. Important: Using the aforementioned new features triggers an irreversible Object Space version upgrade within V7.1 SP7. Therefore exercise caution when upgrading within V7.1 SP7. If an Object Space should be updated to version V7.1 SP7 2014-07-21 or later in combination with a new set of ISIS Frameworks which do use at least one of the aforementioned new features, special preliminary measures are necessary. Before you upgrade within V7.1 SP7, make a consistent backup of all relevant nodes. The upgrade will lead to non-reversible changes to the storage version of the Object Space that would prevent a simple rollback by just replacing the underlying program software by the previously used version. Client nodes, which do not own data, etc., need no backup because they can be easily created anew from templates. Background information Usually upgrades within the same service pack, here V7.1 SP7, can easily be managed because an upgrade includes only exchanging the program software and importing new system and application frameworks. Resetting the Object Space to the old state would be achieved simply by suspending the new frameworks and restoring the program software. Since V7.1 SP7 2014-07-21, the program software supports the class definition properties as mentioned above. Some of the delivered ISIS Frameworks make use of this handling and thus will activate the storage version upgrade. This increment does not lead to a record structure conversion but results in a compatibility change in order to avoid that older kernels can work with such Object Spaces causing incorrect behavior. Downgrading from this storage version and consequently changing back to an older version of the program software is not possible unless all objects making use of the new feature would be removed. Such objects can be identified by kernel menu "T. Tools | D. Read all objects | 5. List all objects with system attributes or definition properties which caused an upgrade of storage version to 801". For more details, see chapter "Appendix: Papyrus Kernel console" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". Because the automatic storage version change will happen after the program software upgrade individually on every node when it makes use of Framework objects which apply the new functionality, the system should not go productive until tests are finished and the new version was approved. l Domain Controller Installation The ISIS Installation Routine provides a dedicated option to install the Papyrus Desktop for the Domain Controller. If only one of the other options to install the Domain Controller for a specific platform is selected, the Domain Controller will be installed without the Papyrus Desktop. For more details, see chapter "Domain controller node installation" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". l Scheduler automatically switched off during service function "CheckObjects" For details, see sections CheckObjects and Scheduler in "Command-line parameters" in "WebRepository and WebControl Installation and Administrator Guide (poinste)" l Scope-based Settings New scope based settings used for all setups (e.g. in the "External Monitoring Framework" chapter). getstartede V7.6 SP3 281/389 Appendix: main updates in V7.1 l Import and Export of Objects and Frameworks The revised "Import and Export of Objects and Frameworks" chapter describes how objects and frameworks from one Papyrus Objects Domain can be transferred to another. In previous release versions, this chapter was a part of "WebRepository Application Developer Guide (pwride)". For more details, see chapter "Transfer between domains: import and export of objects and frameworks" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". l Scheduled Action Attribute Interval type of Scheduled Action has been provided with additional four options for the specification of the interval of reiterated actions. For details see: "Create a scheduled action" in "WebRepository and WebControl Installation and Administrator Guide (poinste)". l New enhanced Settings Explorer The Settings Explorer was improved: the Explorer comes with an user-friendly and simplified window layout which was reduced to three frames. For developer details see: "Settings & scopes - BASE|Settings Framework" in "WebRepository Application Developer Guide (pwride)" For administrator details see: "Papyrus application settings" in "WebRepository and WebControl Installation and Administrator Guide (poinste)" Note: The enhanced views must be activated, to enable the new enhanced Settings Explorer. Invoke therefore the Settings dialog using menu item Options | Settings and activate option Use enhanced views. 16.3.19.2 Papyrus Depot l Depot Exporter New implementation of Depot Stored Procedure "Depot Exporter (DPql)". While the previous implementation "Depot Exporter (STP - LDV)" exported only Capture Documents without adjustments, "Depot Exporter (DPql)" can cope with any Depot Index class. Apart from other novelties the most interesting feature of "Depot Exporter (DPql)" is the possibility to use XSD files to control document export. For more information see: Depot exporter in WebRepository - Depot Framework Developer and Administrator Guide (podepotdae). Available since DVD V7.1 SP7 2014-07-11 l Automatic Installation of Distributed Depot A variety of new features of Distributed Depot now enable automatic installation of a Distributed Depot. Just a few parameters to configure and everything else is done automatically on instantiation of the Distributed Depot, even the first partition of the Distributed Depot is instantiated on a specified node or on a newly created one depending on the configuration. For more information see: Installation of a distributed depot in WebRepository - Depot Framework Developer and Administrator Guide (podepotdae). Available since DVD V7.1 SP7 2014-07-11 16.3.19.3 Papyrus Query Language (PQL) l $applyStringTemplateToSet() New PQL function used to fill the placeholders of a string template. For details, see "$applyStringTemplateToSet() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $javaScriptEncode(), $javaScriptDecode() PQL functions for encoding and decoding JavaScript escapes. For details, see "String functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". getstartede V7.6 SP3 282/389 Appendix: main updates in V7.1 l Attribute "Remove Accent" This extension of class INDEX enables indexed string queries to disregard character accents. For more details on indexed search, see "Performance in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". For details on likeNch and likeNchCs, see "String pattern operators in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $toBin(), $fromBin() New PQL type conversion functions for binary attributes. For details, see "Type conversion functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $loadPqlLibrary() This new PQL function loads DLLs implementing external PQL functions. For details, see "$loadPqlLibrary() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Data Hashing & Digital Signature Functions For details on these PQL functions, see "Data hashing & digital signature functions" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Data Encryption & Compression Functions For details on these PQL functions, see "Data encryption & compression functions" in "WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Block Statement This statement enables the developer to combine a group of statements in a PQL script. For details, see "Flow control constructs in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". 16.3.19.4 Papyrus Frameworks l Private/Public Development Framework revised The Private/Public Development Framework was revised. Its configuration is based on scopes, which provide a means for centralized and framework-independent configuration. For more information, see chapter "CM_PPDE | Core" in "WebRepository Application Developer Guide (pwride)". Available since DVD V7.1 SP7 2014-07-11 l Framework Development A new sub chapter "Framework Development" is added in the main chapter "Papyrus WebRepository Design and Development Concepts". The Framework Development describes how to create a new Framework for customer-defined application setups. For more information, see chapter "Framework guidelines" in "WebRepository Application Developer Guide (pwride)". Available since DVD V7.1 SP7 2014-07-11 16.3.19.5 Papyrus Adapters l Type Manager DB Following new templates are now available in Library: - TM DB PAS - TM DB PAS WebArchive - TM DB with Credentials For details see: "Type manager DB" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". getstartede V7.6 SP3 283/389 Appendix: main updates in V7.1 l File Adapter The File Adapter is able to issue trace messages about incoming files of the Control Folder. These messages are created before and after the file is moved from one directory to another. For details see: Trace Messages About Incoming Files of the Control Folder in WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage). l LDAP Adapter A new template "Active Directory Authentication with Nested Groups" is available. This template allows to automatically retrieve CN, DN, upn and groups membership for all of the external users. Groups are now synchronized in the LDAP GROUP COLLECTION. For details see: LDAP adapter in WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage). l HTTP Client The documentation was enhanced with information on using the Papyrus HTTP Client in synchronous mode. For more details, see chapter "Synchronous usage of HTTP client" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". Available since DVD V7.1 SP7 2014-05-21 l Papyrus Social Adapter The documentation was extended to cover the Papyrus Social Adapter, which facilitates connecting with various popular social networks. The description provides practical samples for the OAuth Token Requester Adapter and the Twitter Client. For more details, see chapter "Papyrus social adapter" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". Available since DVD V7.1 SP7 2014-05-21 16.3.19.6 Papyrus Resource Collection l Resource Import/Creation Adapter (ICD) The objects Resource Import/Export and Resource Import Manager (Storage/System Collection/Resource Collection Management/Resource Import Manager) are now obsolete as the Resource Import/Creation Adapter (ICD) is now used for importing resources to Papyrus Objects Space. l Resource Extractor Tool The Resources Extractor tool allows to export resource objects from the Resource Collection to the file system.The resource objects of the specified Resource Group will be exported into the paths as specified by resource library profile (default.lbp). l Resource Library Import class New class Resource Library Import to import all the resources from the file system as specified in the default.lbp library file to the Papyrus Objects Domain. l Revised description of resource import into Resource Collection Removed the sub chapter "5.2 Components of the Resource Collection". Added new sub chapters - "6.1 Resource Group", - "6.2 Resource Access from Resource Collection", - "6.3 Create and Use Individual Resource Groups", - "6.4 Resource Explorer". l Configure New Resource Node PQL A ready to use PQL "Configure New Resource Node" is available in Library to automatically instantiate and configure the Resource Import/Creation Adapter (ICD) on the Resource Node. l Update Resource Groups A ready to use PQL template "Update Resource Groups" is available to adjust the existing Resource Groups (in development state "Active"). getstartede V7.6 SP3 284/389 Appendix: main updates in V7.1 16.3.19.7 Papyrus WebPortal l Load Balancer The article about Load Balancer has been extended. Now it includes the description of all possible configuration scenarios, e.g. required settings, if several web servers are installed on different machines. For details see: Set up load balancing in WebPortal Installation and Developer Guide (powpidge) l AccessLog (POHX2701) Class HTTP SERVER SETTINGS has been extended by new attribute AccessLog (POHX2701). This attribute controls the output of the HTTP access log. For details see: section Write trace messages for debugging in WebPortal Installation and Developer Guide (powpidge). 16.3.20 Papyrus Postprocessing/Printpool l Additional parameter for AFPIMPORT: IMPLEMENTSUBGROUP IMPLEMENTSUBGROUP allows the import of overlays that are embedded in a form definition (FormDef). Import of regular page overlays has been supported ever since, but not the import of overlays that come with a FormDef. The AFPIMPORT as such cannot import the FormDef, which was used to create the initial AFP. Up to now it was not possible to import overlays that were contained in this FormDef. For more information, see chapter "AFPIMPORT command" in "Postprocessing/Printpool General Information and Developer Guide (pppdge)". Available since DVD V7.1 SP7 2014-09-24 l Additional global variables for AFPIMPORT (&& 16.3.21 Papyrus PrinterDriver 16.3.21.1 Papyrus PrinterDriver batch Papyrus PrinterDriver Batch is a new product on this DVD. It is designed as an extension of the Papyrus PrinterDriver and collaborates with it. Papyrus PrinterDriver Batch offers an automated conversion and generation process for input files like MS Word (DOC, RTF), text files, etc. into AFP documents. It internally calls Papyrus PrinterDriver that prints the generated AFP documents in batch mode. Papyrus PrinterDriver Batch can be installed with the ISIS Installation Routine and is available for Windows. For more information, see "PrinterDriver Batch Administrator Guide (pdrbage)". getstartede V7.6 SP3 285/389 Appendix: main updates in V7.1 16.3.21.2 Papyrus PrinterDriver l Overlay optimization with margin definition The Overlay optimization dialog was enhanced and offers now, in addition to the cropping functionality, also the possibility to define margins after the overlay has been cropped. For details, see chapter "Advanced setup dialog" in "PrinterDriver Online Help (isisdrv.hlp )". Available since DVD V7.1 SP7 2014-03-20 l Enhanced output generation mode A new check box was added to the Configuration dialog. When selected, Papyrus PrinterDriver converts graphical objects to PTX structured fields whenever this is possible. By this, the output size of the AFP file can be reduced considerably. For details, see chapter "Document generation mode" in "PrinterDriver Online Help (isisdrv.hlp )". Available since DVD V7.1 SP7 2014-05-21 16.3.22 Papyrus Server 16.3.22.1 IPDS l Practical Example of an IPDS Data Stream The reference guide was enhanced with an example showing the creation of an IPDS data stream. A simulation of an IPDS data stream, by means of sending data to a virtual printer is demonstrated, as well sending the IPDS data stream to an IPDS printer. For more information, see chapter "Practical example" in "Papyrus Server - IPDS Reference Guide (pseipdsrge)". 16.3.22.2 PDF-in l Reduce Page size (PINReducePageSize) The parameter allows to resize individual PDF pages that exceed a selectable format. For more details, see chapter "Reduce page size (PINReducePageSize)" in "Papyrus PDF-in Reference Guide (ppdfinrge)". l Use composite font (PINUseCompositeFont) Activating this parameter improves the handling of some Asian/Arabic fonts. For more details, see chapter "Use composite font (PINUseCompositeFont)" in "Papyrus PDF-in Reference Guide (ppdfinrge)". l Force Blending On All Images (PINForceBlending) Sometimes the background of a page is not recognized, resulting in unexpected colors. Activating this parameter remedies this problem. For more details, see chapter "Force Blending On All Images (PINForceBlending)" in "Papyrus PDF-in Reference Guide (ppdfinrge)". getstartede V7.6 SP3 286/389 Appendix: main updates in V7.1 l Font mapping - Default font mapping table ISIS Papyrus provides a default for the font mapping process for PDF. The default is hard-coded and substitutes the 14 standard fonts in PDF readers by 14 Adobe Type 1 fonts. These font files are located in a subfolder of the ISIS common libraries. The exact location is - after a standard installation - \isiscomm\ l Init Information on data reference (PINInitInfoOnDataRef) Init data reference (PINInitDataReference) In Papyrus Objects environment you can select between receiving the font mapping information from a file (Initi file) or from an object. The two parameters allow to select the one or the other option and to define an object which contains the font mapping information. For more details, see chapter "Font mapping" in "Papyrus PDF-in Reference Guide (ppdfinrge)". Available since DVD V7.1 SP7 2014-07-11 l True Type fonts handling (PINTrueTypeFontsHandling) The parameter defines how external TrueType fonts should be processed. The user can now define that external TrueType or OpenType fonts are kept as they are, that is not converted to AFP fonts. For more details, see chapter "True Type fonts handling (PINTrueTypeFontsHandling)" in "Papyrus PDF-in Reference Guide (ppdfinrge)". Available since DVD V7.1 SP7 2014-07-11 l Rasterize PDF Font (PINForceCharImage) The parameter was enhanced by a third option, which allows to define that only CID-encoded PDF fonts should be rasterized. For more details, see chapter, see chapter "Rasterize PDF font (PINForceCharImage)" in "Papyrus PDF-in Reference Guide (ppdfinrge)". Available since DVD V7.1 SP7 2014-07-11 l Set transparency threshold (PINTransparencyThreshold) Der Parameter (Attribute) is used to specify how images containing the alpha-channel (opacity level) should be managed. For more details, see chapter "Transparency threshold value (PINTransparencyThreshold)" in "Papyrus PDF-in Reference Guide (ppdfinrge)". Available since DVD V7.1 SP7 2014-07-11 16.3.22.3 HTML The manual has been overhauled: getstartede V7.6 SP3 287/389 Appendix: main updates in V7.1 l Parameter descriptions regrouped Parameter descriptions have been regrouped in a logical order and details added to clarify their usage and effects. For details, see chapter "Parameter Description" in "Papyrus Server - HTML Reference Guide (psehtmlrge)". l New Practical examples Practical examples for Papyrus WebControl / WebRepository and Standalone have been added. With this ready to use example it is possible to verify the installation process. For details, see chapter "Practical examples" in "Papyrus Server - HTML Reference Guide (psehtmlrge)". l New troubleshooting section A new troubleshooting section helping to avoid common pitfalls has been added. For details, see chapter "Troubleshooting" in "Papyrus Server - HTML Reference Guide (psehtmlrge)" 16.3.22.4 PageEXEC l TRIGGER parameter enhanced Allows to define more than one trigger condition, by using the "&" or "|" operator. For more details, see chapter "Index trigger (TRIGGER)" in "Papyrus Server - PageEXEC Reference Guide (pseperge)". l FIELD parameter enhanced The value range of the parameter was enhanced. Allowed values are not only printline positions but also literal values, that can be entered into the index. Available since DVD V7.1 SP7 2015-02-11 For more details, see chapter "Index field(s) (FIELD)" in "Papyrus Server - PageEXEC Reference Guide (pseperge)". 16.3.22.5 AFP to PDF l PDFtRadioButtonRound new parameter Radio buttons are now available also in a round shape. For details, see chapter "PDFtRadioButtonRound" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP7 2014-12-17 l Media Box (PDFtMediaBox) attribute/parameter enhancement Now the lower left corner of the MediaBox is definable and x and y coordinates are not automatically set to 0. If you defined different starting coordinates in old projects these settings will affect newly generated PDF documents. For more information, see chapter "Media Box (PDFtMediaBox)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". Available since DVD V7.1 SP7 2014-10-28 l Object position enhancement Older versions internally used - independent of what was selected in Application-Output-Format - a 300 units per inch precision while generating PDF documents. This caused very small objects (<1/240 inch) to be invisible in the PDF. Now 1440 units per inch precision (native AFP resolution) is possible. Available since DVD V7.1 SP7 2014-12-18 l PDF Linearization (PDFtLinear) new attribute/parameter The first page of a PDF document, generated with this parameter enabled, is already viewable while the download is still in progress. Available since DVD V7.1 SP7 2014-09-24 getstartede V7.6 SP3 288/389 Appendix: main updates in V7.1 16.3.23 Papyrus WebArchive l Papyrus WebArchive based on external database (TMDB) This new chapter provides all information required for the usage of Papyrus WebArchive based on external database (TMDB) which enables to archive documents to and retrieve from external databases using the interface Type Manager DB (TMDB). For details see: "WebArchive based on external database (TMDB)" in "WebArchive Installation and Administrator Guide (pwaiage)". 16.3.24 OverView AFP Designer l Options for printing QR barcode enhanced Printing QR barcode requires the string to be coded in ASCII format. Therefore the string to be coded has to be re-translated from EBCDIC to ASCII for printing on z/OS. The dialog provides a list of EBCDIC and ASCII codepages from which the user can make a selection. Available since DVD V7.1 SP7 2014-07-11. For details, see chapter "QR" in "AFP Designer Application Developer Guide (oaddge)". 16.4 Main updates in V7.16 This DVD includes ISIS products in release level V7.16 (v140522). Language handling of ISIS technical documents From this release level onwards the language handling of ISIS technical product documentation including online help will be gradually improved and standardized as follows: l Technical product documentation is classified into: n Application developer and administrator documentation n Business user documentation l Application developer and administrator documentation will be provided in English only. l Business user related documentation will be provided in English and German capturing also screenshots of related business user UIs in the related language. Online Help in Microsoft Compiled HTML Help (CHM) Several ISIS products have an online help based on the Microsoft help format. Since V7.16, these products are delivered with online help in the Microsoft Compiled HTML Help (CHM) format. Due to a Security Update introduced by Microsoft, CHM help files may not be displayed correctly if the help file is located on a network share. For more details, see chapter "Microsoft compiled HTML help (.chm)" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". 16.4.1 Important notes Certain Windows Updates lead to product crashes Due to an incompatible Windows function change, the installation of the following Windows Updates can lead to product dumps at product termination. This applies also to all processes started by the Papyrus Objects Kernel and is valid for all 7.16 ISIS releases prior to V7.16 DVD v131211. - Windows Update KB2862973 - Windows Update KB2882822 - Windows Update KB2875501 To prevent ISIS processes from abnormal termination caused by the incompatible Windows function change, either uninstall the Windows Update or install an ISIS-version of V7.16 DVD v131211 or newer. getstartede V7.6 SP3 289/389 Appendix: main updates in V7.1 16.4.2 ISIS product installation l Script register_icf.sh must be run in all Unix installations. For all Unix installations, the following following script is required and must be executed: /isiscomm/ 16.4.3 ISIS Product Authorization Service l Two IPAS tutorials are available. They demonstrate how to install and configure the IPAS and how to administer and maintain product authorizations. The tutorials are installed with the ISIS Installation Routine and can be opened from the Windows Start menu: Start | All Programs | ISIS Tutorial Videos | IPAS Tutorial Part 1 (Installation and Configuration) Start | All Programs | ISIS Tutorial Videos | IPAS Tutorial Part 2 (Administration and Maintenance) l Detailed instructions on how to install Papyrus Desktop of IPAS are available. Instructions on how to set up the Papyrus Desktop of IPAS on Windows and on Unix are available and can be found in chapter "IPAS and Papyrus Desktop of IPAS" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". 16.4.4 Papyrus Adaptive Case Management Solution improvements and new features 16.4.5 Papyrus Automated Document Factory Solution - improvements and new features Initial release. The Automated Document Factory Solution provided by ISIS offers businesses an intelligent end-to-end automation of their print and mail-shop production processes that are normally handled manually. The Solution comes with a fully integrated operator user interface based on Papyrus EYE Widgets. For details, see "WebRepository - Automated Document Factory Solution Administrator Guide (poadfage)" and see "Papyrus Client - Automated Document Factory User Guide (poadfuge)". getstartede V7.6 SP3 290/389 Appendix: main updates in V7.1 16.4.6 Papyrus Business Correspondence Solution improvements and new features This first V7.16 release does not fully cover the Correspondence Solution and thus, must not be applied for correspondence installations. The following features will become available with the next release: l Introduction of a new extended change management concept with support for multiple test stages and hotfixes l The template administrator workplace has been updated to include different ways of retrieving data l To assist in the creation of correspondence users a set of CF users templates have been created l Introduction of Papyrus EYE Widgets V4 workplaces with support for wizards l Support for the creation of variables via Papyrus EYE Widgets Desktop 16.4.7 Papyrus Business Document Capture Solution improvements and new features l Import Data into Basedata Depot Configuration changed due to new Depot Stored Procedure "DepotPql Import into the Depot" See: "Import data into basedata depot" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)" l Type Property for Depot Index Type property of Depot Index attribute is used for mapping table column onto Depot Index attributes See: "Type property of depot index attribute" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)" l Adapter "Import Doc-Xls (File) New Adapter for import of MS documents (DOC and XLS) See: "Processing office documents via conversion into AFP with printer driver" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)" , "Adapter "Import doc-xls (File)" (Adapter)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)", "Adapter for generating AFPs in printer driver (Adapter)" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)" l Substitution Lookup New article describing how to create a Substitution Lookup to assist data entry in "Completion" view of "Capture Workplace" See: "Substitution Lookup" in "Capture lookup objects" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". l Changed configuration of Layout Definition In comparison to the previous release of this document the configuration of Layout Definition has undergone considerable change. See: "Create a mask definition" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)" l IBAN and BIC for Payment Validation Additional information about the usage of IBAN and BIC for Payment Validation has been provided See: "IBAN and BIC for payment validation" in "WebRepository - Capture Solution Administrator and Developer Guide (popcfade)". getstartede V7.6 SP3 291/389 Appendix: main updates in V7.1 16.4.8 Papyrus Campaign Management Solution improvements and new features Initial release. The Papyrus Campaign Management Solution has first become available with release level V7.16. The Papyrus Campaign Management Solution allows the central management of marketing messages for any type of targeted communication. For details, see "WebRepository - Targeted Messaging Framework Developer and Administrator Guide (potarmdage)" and see "Papyrus Client - Targeted Messaging User Guide (potarmuge)". 16.4.9 Papyrus Client AFP Viewer l New Document Tree window Introduced in v131113.v716 The Document Tree window displays the page groups in an AFP in case the AFP contains multiple documents. For details, see chapter "Document tree window" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". 16.4.10 Papyrus Client Canvas l Export project Clicking the Export project menu item opens a file dialog to specify the directory where to save the zip file. The zip file contains the project and all required resources as well as a *.trc file with all Papyrus Objects accesses. For details, see chapter "Options toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Insert images into text input fields Introduced in v130304.v715 Images (TIF, BMP, JPG) from the file system can be inserted into a text input field by drag-and-drop. For details, see chapter "Text input toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l New buttons in Paragraph toolbar The Paragraph toolbar was extended with the following new buttons: - Join paragraph - Indent left / right - Paragraph background color - Widow / Orphan - Line spacing mode / Line spacing For details, see chapter "Paragraph toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l New button Show/Hide ruler This new button in the View toolbar activates/deactivates the ruler on top and to the left of the document window. By usage of a context menu the unit of the ruler can be changed. For details, see chapter "View toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". getstartede V7.6 SP3 292/389 Appendix: main updates in V7.1 l New behavior of variable input fields of type DATE Introduced in v130201.v71x If no default value is set, the current date is displayed. If the default value is set to an empty string, the date field remains empty and in a list box the first applicable date is preselected. If the field is empty and the user presses a number key, this number is taken as suggestion for the closest date to the current date. For details, see chapter "Variable input field" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Sticker frame Introduced in v20130423.v715 The sticker definition was extended with an option to define a border width. When defining the border, the sticker is displayed as frame of the defined width. For details, see chapter "StickerCreate" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". 16.4.11 Papyrus Designer, Papyrus DocEXEC l New functions: _TEXT_START, _TEXT_SUSPEND, _TEXT_RESTART, _TEXT_STOP Introduced in v130621.v716 These functions write the content of the TEXT and TEXTPROMPT commands to system variables. The content is available in the following formats: HTML, TXT and DFA. These functions were implemented to meet special requirements of Business Correspondence applications. After a TEXT/TEXTPROMPT command is executed, each variable contains content which allows to build secondary output with letter content. This content can be used, for example, to accomplish text search (TXT), to provide text to third parties (TXT), or to provide bodies for multipart email sending (TXT & HTML). For the function's description, see chapter "Recording functions" in "DocEXEC Reference Application Developer Guide (pdedge)". l New function NOP_ANALYZE Introduced in v130422.v716 Retrieves the properties of a STICKER (position, dimension, color, content), which is embedded into an AFP file, and writes these properties into variables. STICKERs are stored in the AFP documents in NOP records, which are analyzed and read by the NOP_ANALYZE function. The function meets the requirements of campaign management applications, where the space for the marketing messages is marked by STICKERs. For the function's description, see chapter "NOP_ANALYZE" in "DocEXEC Reference Application Developer Guide (pdedge)". l New function GETGUID Introduced in v130420.v716 Generates and return the a GUID value in format: {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}. It can be used to output the value or to check in the variable list. If you use it to check a specific variable, it should contain a GUID afterwards. For the function's description, see chapter "GETGUID" in "DocEXEC Reference Application Developer Guide (pdedge)". l CREATEOBJECT (PDF417) command extension Introduced in v130510.v716 You can define the target codepage that is desired to be shown in the PDF. There is a list provided with the target codepage values: For the function's description, see chapter "CREATEOBJECT PDF417(PDF417)" in "DocEXEC Reference Application Developer Guide (pdedge)". getstartede V7.6 SP3 293/389 Appendix: main updates in V7.1 l CREATEOBJECT (QR) command extension Introduced in v130510.v716 You can define the codepage that the QR code is desired to be displayed. There is a provided list with the ECI values. The default Codepage is 932 For the function's description, see chapter "CREATEOBJECT QR(QR)" in "DocEXEC Reference Application Developer Guide (pdedge)". l STICKER command extension Introduced in v130423.v715 _ COVER l CALL command extension Introduced in v130426.v716 New functions to handle the PQL type checks. This applies to parameters given to the CALL command. The new type checking in PQL makes it necessary to provide the types of the parameters. The following functions have been implemented: TOObjref(), TOInt(), TOInt32(), TOBoolean(), TODouble(), TOString(), TOTimestamp(), TODate(), TOTime(), TOGUID() For the function's description, see chapter "CALL" in "DocEXEC - Access to WebRepository Developer Guide (pdeoadge)". l TEXT subcommand COLUMN extension "section join" Introduced in v130319.v715 COLUMN( l External DOCFORMATS for XMLREAD and XMLSET Introduced in v130305.v715 It is possible to define the standard DOCFORMATs of the XMLREAD and XMLSET commands as external DOCFORMATs. There is a new checkbox available on the XMLREAD and XMLSET dialogs "Docformat on Tagbegin" and "Docformat on Tagend" and on the XMLREAD dialog "Docformat on Tagbegin": External Docformat. If the checkbox is selected, the DOCFORMATs are expected to be external and thus taken from an *.INC resource. For the function's descriptions,see chapter "DOCFORMAT supplementary commands" in "DocEXEC Reference Application Developer Guide (pdedge)". l Resource management in AFPIMPORT Introduced in v130305.v715 Papyrus Designer and Papyrus DocEXEC do not rename a resource anymore at AFPIMPORT if "Use embedded resource" is selected and the resource is not available in the Resource Collection or resource library. The old method was not optimal because it would rename the resources unnecessarily. For more information on resource management, see chapter "AFPIMPORT command" in "Postprocessing/Printpool General Information and Developer Guide (pppdge)". getstartede V7.6 SP3 294/389 Appendix: main updates in V7.1 l CHARTDLL command, new options for BARCHART, "ChartType" Introduced in v120716.v712: 1. "BarConnectingThicknessColor" - The thickness and color of the connecting line can be set using this function. To connect two subsequent bars, use "DrawBelt". 2. "0AxisPosColor" - The position and the color of the X-axis (0-axis) can be changed independently from the grid color. For the attributes' description, see chapter "CHARTEX DLL for bar charts" in "DocEXEC Reference Application Developer Guide (pdedge)" l Space break handling according to general rules for DBCS and SBCS fonts Introduced in v130628.v716 The space break handling in TEXT command was changed so that it follows the general rules for DBCS and SBCS fonts. For more information, see chapter "SPACEBREAK" in "DocEXEC Reference Application Developer Guide (pdedge)". As this change requires implementation of additional calculation and filtering algorithms performance decreases can be observed in particular situations, for example when printing Asian language text. l Backward compatibility parameter: V702_COMP_BALANCEPAGEEND The algorithm for balancing columns at page breaks in TEXT or TEXTPROMPT commands was improved for Papyrus Designer and DocEXEC starting with early v712 versions and the branches following. This new algorithm, however, produced in rare cases non-compatible results, which materialized as text columns exceeding the bottom margin. Meanwhile the algorithm was corrected. V702_COMP_BALANCEPAGEEND allows to switch back to the improved yet not fully compatible algorithm, which was implemented in v712-v717 till the final correction in release date 2014-04-01. For more information, see chapter "V702_COMP_BALANCEPAGEEND" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l New AFPIMPORT parameter INDEXINGMODE Introduced in v130621.v716 The INDEXINGMODE parameter is a compatibility parameter that is used in a special situation at creation of an index table on defined indexes. If the index name from which the index table should be created is not consistently used in all documents (page groups), misleading results may be produced at page calculation for the individual documents. INDEXINGMODE helps to cope with such situations. For more information, see chapter "AFPIMPORT command" in "Postprocessing/Printpool General Information and Developer Guide (pppdge)". 16.4.12 Papyrus Designer and Server - FixForm l Internal rule Condition The internal rule Condition can be used for selection (classification) or specific processing. Conditions can access the properties and parameters of the image, the document or the result and compare them against a limit or range. For details, see chapter "Condition" in "Designer Capture Application Developer Guide (pcddge)". l Creating and Editing of Definition Sets Definition Sets can be created, edited, and saved in the Definition Set Designer/FixForm window. For details, see section "File | Definition Sets..." in chapter "Menu "File"" in "Designer Capture Application Developer Guide (pcddge)". l Generating a FixForm application in OverView AFP Designer A FixForm application can already be generated in OverView AFP Designer after finalizing a FormsFill definition, which saves additional work at the Capture document definition, because the fields defined for the OverView AFP Designer form can also be applied for Capture extraction definition, thus it is not required to define the fields twice. The FixForm definition created in the OverView AFP Designer can be opened in Papyrus Designer/FixForm and used for extracting the completed forms. For details, see chapter "Tool | Programs | Generate FixForm" in "AFP Designer Application Developer Guide (oaddge)". getstartede V7.6 SP3 295/389 Appendix: main updates in V7.1 16.4.13 Papyrus FontConverter l Support of font-fallback substitution for missing/misplaced characters. For more information, see chapter "Fallback mechanism at font conversion" in "FontConverter Online Help (fc)". 16.4.14 Papyrus Server 16.4.14.1 General l ISIS_USE_PCSLOG parameter set to 2 for Server modules. For Server modules running "standalone" without Papyrus Objects, the old logging behavior (ISIS_USE_PCSLOG=0) was applied by default. Since V7.16 DVD v131113, the ISIS_USE_PCSLOG parameter is set to 2 in the start scripts for the Server modules. For more details, see chapter "Environment variables" in "Software Installation and Product Authorization Installation and Administrator Guide (iinste)". 16.4.14.2 AFP to HTML l E-mail tracking A number of parameters/attributes have been introduced to allow tracking of HTML e-mails generated by the AFP to HTML Converter Module. For details, see chapter "E-Mail Tracking" in "Papyrus Server - HTML Reference Guide (psehtmlrge)". l Custom headers Two parameters have been introduced to allow adding of custom markup into the HTML generated by the AFP to HTML Converter Module. These parameters are currently only available for the AFP to HTML Converter Module running standalone. For details, see chapter "Adding Custom Headers" in "Papyrus Server - HTML Reference Guide (psehtmlrge)". l Html generate forms (HTMLGenPrompts) Introduced parameter/attribute Html generate forms (HTMLGenPrompts) to enable the generation of fillable HTML forms. For details, see chapter "Generating Fillable HTML Forms" in "Papyrus Server - HTML Reference Guide (psehtmlrge)". l Html codepage source (HTMLCodepageSource) is obsolete Since 20130628.v716 this parameter is not used anymore by the HTML converter. Instead, the HTML converter reads codepage information from the AFP stream and the AFP fonts. In case no such information is found, the IBM-internal default codepage (500) is used. If explicit codepage definition is needed in order to override this behavior, use a font mapping file and define the codepage field for each font. For details, see chapter "Obsolete Parameters" in "Papyrus Server - HTML Reference Guide (psehtmlrge)". 16.4.14.3 AFP Tuner l New parameter TUNGocaBWMode Specifies the mode for converting GOCA objects to black and white images. For details, see chapter "TUNGocaBWMode" in "Papyrus Tuner Reference Guide (ptunrge)". l New parameter TUNGOCAKnockout Specifies whether or not to apply knockout to (overlapping) GOCA objects. For details, see chapter "TUNGocaKnockout" in "Papyrus Tuner Reference Guide (ptunrge)". getstartede V7.6 SP3 296/389 Appendix: main updates in V7.1 16.4.14.4 IPDS l Banner data handling in Papyrus Server IPDS enhanced Variables $TIME, $ELAPSEDTIME, $RETURNCODE, $OMS(STARTTIME), $OMS(DATE), $OMS(ENDTIME), $OMS(STARTTIME), $OMS(CURRENTPAGE), $OMS(PRINTEDPAGE), $OMS(STARTTIME), $OMS(CURRENTSHEET), $OMS(CPUTIME) can be used on banner pages with Papyrus Server IPDS. For more details, see chapter "Print start and end banner pages" in "Papyrus Server - IPDS Reference Guide (pseipdsrge)". 16.4.14.5 PDF l AFP to PDF Conversion Sample With Bookmark Creation The reference guide was enhanced by an example showing simple AFP to PDF batch conversion, embedding fonts and full-color images and creating PDF bookmarks from group indices. For more information, see chapter "PDF bookmarks from AFP indices" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Submit button (PdftSubmitRect) attribute/parameter enhancement The page number where the submit button should be placed in the form can be optionally specified. For details, see chapter "Submit button (PdftSubmitRect)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Generate Prompts (PDFtGenPrompts) attribute/parameter enhancement The font size of the text entry field of the PDF form can be defined. For details, see chapter "Generate Prompts (PDFtGenPrompts)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". 16.4.14.6 PDF-in l Examples of Font resource generation in Papyrus WebRepository In Papyrus WebRepository there are different possibilities to create and store font resources. Combining the settings of the attributes Force font creation in the Resource Collection (PINForcePOStoring) and Generate external AFP fonts (PINExternFont) mutual dependencies can be created and different results achieved. For more details, see chapter "Font resource generation - parameter matrix" in "Papyrus PDF-in Reference Guide (ppdfinrge)". 16.4.15 Papyrus Objects (WebControl/WebRepository/IPAS) 16.4.15.1 Papyrus EYE Widgets l Support for parameters underneath Widget Binding. Now more than one parameter can be passed by a Widget Binding. For details, see chapter "Passing parameters of widget binding to component/widget invoked by it" in "EYE Widgets Developer Guide (popeyewdge)". l Named High Level Event Parameters. Now parameters can be accessed by their internal names instead of specifying their index. For details, see chapter "Named high level event parameters" in "EYE Widgets Developer Guide (popeyewdge)". l Broadcast Channel based communication allows communication across component boundaries. For details, see chapter "Communication across components - broadcast channel based communication" in "EYE Widgets Developer Guide (popeyewdge)". l Listen to Widget Attribute Change Event. Now, it is possible to monitor modifications on widget attributes. For details see chapter "React on widget attribute modifcations" in "EYE Widgets Developer Guide (popeyewdge)". getstartede V7.6 SP3 297/389 Appendix: main updates in V7.1 l Enhanced selection and multiselection support. For details see chapter "Selection and multiselection support" in "EYE Widgets Developer Guide (popeyewdge)". l Enhanced focus support. For details see chapter "Handling the focus of form elements" in "EYE Widgets Developer Guide (popeyewdge)". l Completion suggestions are supported by using the Setter API. For details see chapter "Auto complete" in "EYE Widgets Developer Guide (popeyewdge)". l The High Level Event Router allows to route an event which was triggered on one widget to another widget. For details see chapter "High level event router" in "EYE Widgets Developer Guide (popeyewdge)". l The Widget Method Caller is an interface to the widgets which allows to call methods easily while hiding their complexity. For details see chapter "Widget method caller" in "EYE Widgets Developer Guide (popeyewdge)". l With a Listener it is possible to monitor asynchronous processes (e.g. long running task) to react on them later on in the GUI. For details see chapter "Listener" in "EYE Widgets Developer Guide (popeyewdge)". l Modal dialogs are temporarily opened windows for user input. For details see chapter "Modal dialog" in "EYE Widgets Developer Guide (popeyewdge)". 16.4.15.2 Papyrus Query Language (PQL) l $getObjectsFromSet() New PQL set function providing array of Object IDs. For details, see "$getObjectsFromSet() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP4 2013-03-04. l Functions to modify arrays For details, see "$insertValue() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" and "$setValue() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l MD5 Functions Functions for calculation of MD5 hash value.". For details, see "Data hashing & digital signature functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Memory buffer functions Functions to create, read from and write to memory buffers. For details, see "Memory buffer functions in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l Minimum/Maximum constants Constants for the minimum and maximum values of PQL data types. For details, see "Constants in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l $treeStructured queries New query keyword similar to $tree. Unlike $tree it also returns duplicates. For more details, see "Tree-Type queries in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". l XML <--> PqlSet conversion functions New functions for the conversion of PQL sets to XML files and vice versa. For details, see "$pqlToXML() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)" and "$xmlToPql() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". getstartede V7.6 SP3 298/389 Appendix: main updates in V7.1 16.4.15.3 Papyrus Depot l Depot Check-in Versioned Depot check-in of versioned objects See: "Depot check-in of versioned objects" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)" l Type property for Depot Index Type property of Depot Index attribute is used for mapping table column onto Depot Index attributes See: "Type property of depot index attribute" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)" l Depot Importer Depot Stored Procedure "DepotPql import into the Depot" replaces Depot STP "Import into the Depot" Data import via PQL instead of DocEXEC which causes considerable changes of configuration See: "Appendix 2: Depot PQLs for data import (Depot importer)" in "WebRepository - Depot Framework Developer and Administrator Guide (podepotdae)" 16.4.15.4 Papyrus Objects Kernel l Extended method property Visible in Tool Box, which now not only allows to define if method button is displayed or not, but also whether the button is displayed with the method name or the method icon or with both. Introduced in v131118.v716. l New method parameters syntaxhighlight and create_utf8 for HTML editor plugin, which allow to switch on syntax highlighting in plain text mode and specify that the text shall be stored as UTF8 instead of local8Bit. Introduced in v130610.v716. 16.4.15.5 Papyrus Desktop l Class diagram displayed for overloading methods in Class Editor. Instead of displaying a list of methods in the context menu, now a separate window with the class diagram is invoked which even allows to search for methods. Introduced in v131119.v716. 16.4.15.6 Papyrus Adapters l HTTP Client Papyrus HTTP Client (HTC Receiver) supports SSL client certificate authentication over HTTPS. For more details, see chapter "Configuration of HTTP client with client certificates" in "WebRepository - Adapter and Type Managers Developer and Administrator Guide (poadaptmdage)". Available since DVD V7.16 2013-12-11 16.5 Main updates in V7.15 This DVD includes ISIS products in release level V7.15 (v130522). It is an intermediate release, that means it does not cover all products on all platforms but only those that are listed below. Thus, the documentation has not consistently been lifted to 7.15 level. The DVD contains a mix of documents related to products either to 7.14 or 7.15 release level. Only for the products denoted below documentation on 7.15 release level is available. 16.5.1 ISIS installation routine l New version of Hardlock Key driver under \install\keydriver\haspdinst.exe. This version supports the installation of the Hardlock Key driver on Windows 8 and Windows Server 2012. getstartede V7.6 SP3 299/389 Appendix: main updates in V7.1 16.5.2 Papyrus Business Document Capture Solution improvements and new features Version V7.15 contains the following noticeable changes: l Considerable changes of Papyrus EYE Widgets v4 workplace "Capture Workplace" ("Completion View Workplace" in v7.14) including new Scan view. l "Capture Administration Workplace" Papyrus EYE Widgets v3 replaced by "Capture Administration Workplace" Papyrus EYE Widgets v4. l Changes of "Capture Framework General Settings" and new "Capture View Settings" in Scope Collection of Settings Collection. l New Scan Receiver in V7.15 (not yet available in V7.14). 16.5.3 Papyrus Designer, Papyrus DocEXEC l Changed default value for LONGNAMESUPPORT Only in v715 the default value of the LONGNAMESUPPORT parameter has been set to YES. This change has been made because it solves the unfavourable situation that the short name was assumed although the long name specified. For example, was it possible to choose the long name of a pagesegment in the SEGMENT command but Papyrus Designer or Papyrus DocEXEC then took the pagesegment with the short name (if one was available). If the resource library contained a S1PIC000.PSG and a S1PIC0001.PSG, it was possible that although the PIC0001 was specified in the SEGMENT dialog the PIC000 was eventually inserted into the document. For the parameters' descriptions, see chapter "LONGNAMESUPPORT" in "" and "Long name support (DELONGNAMESUPPORT) / LONGNAMESUPPORT" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". Available since DVD V7.15 2013-05-03 16.5.4 Papyrus Objects (WebControl/WebRepository/IPAS) 16.5.4.1 Papyrus EYE Widgets l Support for custom menus and shortcuts, which can be assigned to a widget workplace. For details about custom menus, see chapter "Custom menu" in "EYE Widgets Developer Guide (popeyewdge)". For details about custom shortcuts, see chapter "Shortcuts" in "EYE Widgets Developer Guide (popeyewdge)". 16.5.5 OverView AFP Designer l Support of QR barcodes in Data Placement Mode (PPFA). Introduced in v130313.v715 For details, see chapter "QR" in "AFP Designer Application Developer Guide (oaddge)". getstartede V7.6 SP3 300/389 Appendix: main updates in V7.1 16.6 Main updates in V7.14 This DVD is the first release which includes all ISIS products in release level V7.14 (v130422). 16.6.1 General changes l Since version V7.14 the layout of ISIS Papyrus technical documentation is provided with an optimized layout and aligned to common standards of electronic document publishing and omits duplex layout. This means that the same print space is used for both front and back pages. l The method how PCS log files are handled and written was changed between V7.13 and V7.14. Should an environment employ processes of V7.13 or prior versions and V7.14 or later versions, and make them log into the same PCS log, then the consecutive numbering of PCS log files and order of log messages would be destroyed. Because a disarranged log message order is a major obstacle for system analysis, such mixed log situations are anyway evidently unfavorable and should be avoided. In such a case the setup has to be configured so that the processes of V7.13 (and prior) and V7.14 (and after) use individual PCS log files. This can be done by parameter ISIS_PCS_LOGDIR. 16.6.2 Papyrus AFP PrinterDriver l New default project management The default project management for the PrinterDriver has been improved to make it easier to add new versions to the project. For details, see chapter "Set up the virtual PrinterDriver" in "PrinterDriver Administrator and User Guide (pdrauge)". Available since v130117.v713 with COS v130118 l Delivered as signed version For Windows 7 the Papyrus PrinterDriver will be delivered as signed version (Publisher: ISIS Papyrus Europe AG). At a first installation it is necessary to activate the Always trust software from "ISIS Papyrus Europe AG" check box in the Windows Security dialog. For details, see chapter "Second step: Windows printer installation process" in "PrinterDriver Administrator and User Guide (pdrauge)". Available since v130405.v714 16.6.3 Papyrus Business Correspondence Solution improvements and new features The following is a concise list of the available features that are introduced with the release of Papyrus V7.14 featuring the GUI in Papyrus Eye Widget V4. In addition to the new features below, performance has been significantly improved due to the introduction of Papyrus Eye Widget Version 4. Wizards and Forms are still using Widgets V3 and will follow soon. l The Change Management is now separated from the Business Correspondence GUI allowing the administrator to select the appropriate Change Management solution, which could be either the Adaptive Case Management (ACM) based Change Management or using the Private Public Development Environment (PPDE) l Images can now we also directly pasted into the Papyrus Client Canvas document text editor. This is an alternative to retrieval from the Resource Collection l Using the new Preview Mode (Normal, All and Conditions) the document can be interrogated with different views showing also the underlying logic within the document template l The multi-document assembly allows a Material object to have more than one document template structure referenced, which will allow a single input data source to be depicted in various formats l There is full type-support for variable variants allowing different formats to be supported and not just String. l Visibility of variable content can be restricted based upon the User's role l The Duplex handling has been improved allowing the content of duplex documents to be viewed side-by-side for a better representation of the final document production getstartede V7.6 SP3 301/389 Appendix: main updates in V7.1 l The cover sheet for multi-copy handling is now optional l Within the document template structure the explicit data reading building blocks are no longer required, which allows the document to easily make use of different data sources if required l For upgrading an older Business Correspondence Solution a set of migration tools are available that will perform an integrity check to see if the upgrade can precede l The provided online and batch samples have been updated for use in performance testing of a Business Correspondence Solution l Finer granularity is provided of the positioning of building blocks and is no longer restricted to mm l Table of content has been extended to allow for an extra summary of a table of figures, Tables and References Incompatibilities Existing installations using Wizards and Forms based on Eye Widgets V3 can upgrade to Papyrus V7.14, but will require to continue to use them in combination with Papyrus EYE Widget Version 3. 16.6.4 Papyrus Client Canvas l Search & Replace in expressions in text input fields Introduced in v121029.v714 Search & Replace in text input fields was extended to handle expressions, if Output Syntax is enabled. For details, see chapter "Find and replace dialog" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Image property dialog enhancement Introduced in v121123.v714 The Image property dialog was extended with a preview of the image in the lower right, and editable fields for setting parameters regarding image properties. For details, see "Image property dialog" in chapter "Text input toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Select text block dialog enhancement Introduced in v121123.v714 The Select text block dialog was extended with a preview of the text block (.imp file) in the lower panel. For details, see "Select text block dialog"in chapter "Text input toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". l Sticker functionality was extended to be transparent or solid Introduced in v121112.v714 Stickers can be defined as covering the elements underneath, either in the DOCDEF code or by creation in Papyrus Client Canvas or Papyrus Client AFP Viewer by defining a sticker color: e.g. StickerCreate="Warning C [128,255,128] Transparent T [128,255,128]" If a sticker is defined without parameter T or C, by default a transparent sticker is generated. For details, see chapter "StickerCreate" in "Papyrus Client AFP Viewer Administrator and Reference Guide (pavarge)". l Paste images from clipboard into text input fields Introduced in v121210.v714 A context menu enables the user to select the used image format for inserting images. - BMP for uncompressed insertion - JPG-LOW for 75% compression - JPG-MID for 85% compression - JPG-HIGH for 95% compression For details, see icon Image mode in chapter "Text input toolbar" in "Papyrus Client Document Creation (Canvas) Administrator and Reference Guide (pcnarge)". getstartede V7.6 SP3 302/389 Appendix: main updates in V7.1 16.6.5 Papyrus Designer, Papyrus DocEXEC l New backwards compatibility parameter V702_COMP_POSITIONKEYWORDSINASSIGN Introduced in v130227.v714 V702_COMP_POSITIONKEYWORDSINASSIGN={0|1|2|3} default:0 0: v712 behavior without warning (valid for all versions since v712) 1: v712 behavior with warning, if the ASSIGN set is not the same as was before (valid for all versions since v712) 2: v702 behavior no warning 3: v702 behavior with warning The option works as a compatibility switch for the fix of the corrected handling of ASSIGN commands with positional keywords (LASTMAX, etc...). The warnings will help DOCDEF developers to find the concerned places in their code to fix them. The return value of an ASSIGN was dependent on the previous command and could either be the horizontal component or the vertical one. This has been changed, so that always the vertical component is returned. This parameter is described in "DEV702_COMP_POSITIONKEYWORDSINASSIGN / V702_COMP_POSITIONKEYWORDSINASSIGN" in "DocEXEC and Document Designer Installation Administrator Guide (pdeage)". l The rotated and inlined page segment handling has been improved. Introduced in v130222.v712 A fix was introduced concerning inlined rotated page segments. If a page segment was inlined and rotated, the clipping rectangle was calculated incorrectly (always with 0° rotation). This behavior has been corrected. Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Synchronized charts were changed in regard of the relation of legend to chart Introduced in v121217.v714 The legend frame size is now calculated as 1/4 of the chart. l The limit of the EAN128 barcodes was increased from 50 to 128 characters Introduced in v130304.v714 l QR barcode size and pattern changed Introduced in v121029.v714 Due to a bug fix, the barcode size for strings to be coded of 21-25 character is increased. Also for strings shorter than 21 characters, a size increase is possible, if the barcode is using high error correction level. Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. l CTC-triplet (Composed Text Control) will be omitted Introduced in v121031.v714 Reference: Mixed Object Document Content Architecture (MO:DCA) Reference, AFPC-0004-08, Ninth Edition (July 2011), p.566 getstartede V7.6 SP3 303/389 Appendix: main updates in V7.1 l Expressions can be used in LANGUAGESET command Introduced in v121112.v714 The "Decimal separator" and the "Thousand separator" specification accept expressions and not just string values. In case the expression contains more than one character, the first character will be interpreted. For the description of the LANGUAGESET command, see chapter "LANGUAGESET command" in "DocEXEC Reference Application Developer Guide (pdedge)". l TEXT subcommand SEGMENT extension Introduced in v121119.v714 SEGMENT( l New TEXT subcommand IMAGE Introduced in v121210.v714 IMAGE( 16.6.6 Papyrus Designer and Server -FixForm l New internal rule Apply geometrical relations This internal rule returns text regions with geometrical relations selected by the user in relation to reference elements provided by the user. For details, see chapter "Apply geometrical relations" in "Designer Capture Application Developer Guide (pcddge)". l New internal rule SplitAt This internal rule can be used to split text and potentially remove or replace it at text regions found before. For details, see chapter "SplitAt" in "Designer Capture Application Developer Guide (pcddge)". l New internal rule ReplaceAt This internal rule can be used to replace text in specified text regions by a user defined replacement text. For details, see chapter "ReplaceAt" in "Designer Capture Application Developer Guide (pcddge)". getstartede V7.6 SP3 304/389 Appendix: main updates in V7.1 l New Keyword locator and Phrase locator These two locators were implemented in the text processor Pattern search. The Phrase locator is used to find complex phrases consisting of matched pattern in the text, the Keyword locator is used to find predefined keywords within one or more text regions. For details, see chapter "Pattern search" in "Designer Capture Application Developer Guide (pcddge)". 16.6.7 Papyrus Objects (WebControl/WebRepository/IPAS) 16.6.7.1 Papyrus Objects Kernel l Implementation of individual versioning of instances via the new system attribute $InstanceVersioning Introduced in v121029.v714. l Support separation of processor (groups) via CPU affinity and PCSDATA shared memory Introduced with v121029.v714. Using this separation might improve performance on powerful Windows machines with many processors/cores running many processes in parallel. Documented in pcscfg43.ini (available in isiscomm\w3) in chapters ISIS_PCS_AFFINITY, ISIS_PCS_AFFINITY_ACROSS_NUMA, ISIS_PCS_AFFINITY_WARN_PARTIAL_NUMA. l Support of pipe and socket connection between Papyrus Eye Widget Desktop and Papyrus Objects Kernel Introduced with v121029.714. Before this the connection between Widget Desktop and Kernel was always via HTTP like in the Widget Plugin. l PQL pre-constraints have access to parameters passed to method Introduced in v121024.v714. The parameters that are available for PQL methods are now also available in their PQL based pre-constraints ($Param1-12, $Tool, $Material, etc.). 16.6.7.2 Object Space l GetInstanceVersioning method Introduced in v121029.v714. This new method can be called on a class, template or instance to get versioning information: Class/Template: Returns information how an instance would be versioned if created from this class or template. Instance: Returns the information how the instance versioning is handled for this instance. 16.6.7.3 Papyrus EYE Widgets l This V7.14 release introduces V4 Widgets for further improved performance experiences. l Migration from Widgets V3 to V4 can be performed with migration scripts and some manual steps assisted by ISIS experts. l It is possible to run V3 and V4 widget workplaces in parallel. The first widget workplace below the user's Session matching the available kernel version is taken. l The designing of widget workplaces has not been changed much, the main difference is that versioned instance instead of template trees are used. getstartede V7.6 SP3 305/389 Appendix: main updates in V7.1 16.6.7.4 Papyrus Query Language (PQL) l $setFieldValue() Sets the specified PQL set element to the specified value. Creates records and/or fields if the passed record and/or field index is out of range. For more details, see "$setFieldValue() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP4 2012-11-19. l $parseCSV() Parses given CSV and returns its data in a PQL Set. For more details, see "$parseCSV() in WebRepository - Papyrus Query Language (PQL) Developer Guide (popqldge)". Available since DVD V7.1 SP4 2012-11-19. 16.6.8 Papyrus Server 16.6.8.1 PDF l Digital signature production using HSM Luna SA 5.0 following PKCS11 standards Introduced in v130405.v714. For details on the parameters involved and how to specify them, see chapter "Create digital signature with HSM/PKCS#11" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l New parameter "Forms and signature font (PdftDigitalSigFormsBaseFont)" The parameter (attribute) defines an AFP outline font or a PDF Base 14 font for the purpose of filling data into PDF forms as well as producing a digital signature string. Introduced in v130405.v714. For more information, see chapter "Forms and signature font (PdftDigitalSigFormsBaseFont)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". l Sending AFP to PDF form data by mail Papyrus Server AFP to PDF module allows production of PDF forms whose data can be sent by mail. There have been implemented three parameters for this purpose: Submit button (PdftSubmitRect) Form data receiver (PdftSubmit FormAddr) Formdata mime type (PdftSubmitFormType) For more information, see chapter "Submit button (PdftSubmitRect)" in "Papyrus Server - AFP to PDF Reference Guide (psepdfrge)". 16.7 Main updates in V7.13 16.7.1 Main updates in V7.13 (DVD v131212) Certain Windows updates lead to product crashes Due to an incompatible Windows function change, the installation of the following Windows Updates can lead to product dumps on product termination. This applies also to all processes started by the Papyrus Objects Kernel and is valid for all 7.13 ISIS releases prior to this release. - Windows Update KB2862973 - Windows Update KB2882822 - Windows Update KB2875501 To prevent ISIS processes from abnormal termination caused by the incompatible Windows function change, either uninstall the Windows Update or install the present ISIS version (V7.13 DVD v131212). getstartede V7.6 SP3 306/389 Appendix: main updates in V7.1 16.7.2 Main updates in V7.13 (DVD v121119 ) 16.7.2.1 Release of Papyrus EYE Widgets The Papyrus EYE Widgets technology allows to design platform and target independent Graphical User Interfaces (GUIs) by combining Widgets. Widgets are ready-to-use mini GUIs each of which can be used to visually display and retrieve data in various ways. The tasks of a user for instance can be displayed in a Table Widget. Selecting one of these tasks, their details can be displayed for instance in a Form Widget next to it. 16.7.2.2 Overview AFP Designer l Support for TTF/TTC/OTF usage in PPFA mode (DOFONT command) Introduced in v120830.v713 l "Compiler Options..." dialog has implemented a new checkbox: "No backgr. merge" Introduced in v120922.v713 If the checkbox 'PSEGs in overlay' is activated, "No backgr. merge" provides an additional compile option. If activated, there will be no CMYK color conversion (CMYK -> RGB -> CMYK) during the compilation which allows color fidelity. The PSEG will be copied into the overlay instead of drawing it. The checkbox is not enabled or activated by default ('old behavior'). l "Barcode Options" dialog Introduced in v120919.v713 If "Options | Use property sheet dialogs" is activated, "Field properties | Bar code | Barcode options" will allow to define barcode colors with different color models. 16.7.2.3 Papyrus Client Canvas l New parameter Toolbar Introduced in v120531.v713 Toolbar={legacy|ribbon}, default=ribbon This parameter defines the appearance of the Canvas toolbars: legacy... toolbars are displayed as usual ribbon... toolbars are displayed in ribbon style (toolbars are placed on tabs in a tab bar) l Large resource handling optimization Introduced in v120703.v713 The handling of large AFP resources has been improved. Previously, AFPs with large resources, e.g. images with high resolution, could lead to view and processing problems. l Offline authorization for Papyrus Canvas and Papyrus Canvas plugin Introduced in v121119.v713 getstartede V7.6 SP3 307/389 Appendix: main updates in V7.1 16.7.2.4 Papyrus Designer, Papyrus DocEXEC l TEXT subcommand SUPERSCRIPT/SUBSCRIPT Introduced in v120920.v713 New handling of used fonts for superscript and subscript. In older versions (till v712) superscript- and subscript-fonts were treated differently. They were a bit smaller and this caused in case of bitmap fonts up to two not necessary font definitions. With e.g. v702 or v712: In listed AFPs this looks like a duplicated font. In v713 this additional font information is omitted. l Enhancement of the dialog font in Papyrus Designer Introduced in 121019.v713 l New routine implemented in PDECON.DLL: PAUSE Introduced in v120806.v713 Stops DocEXEC processing for a defined time. Sample: CONVERT('PDECON','PAUSE','300') ... Pauses execution for 300 ms 16.7.2.5 Papyrus Server Color to B/W conversion l New parameter TUNPatternBWMode Introduced in v120913.v713 Defines whether OCA colors are either dithered to default FS10MMR (b/w) images or are set to OCA color black. The default is setting OCA colors to black (TUNPatternBWMode="0"), which is backward compatible behaviour. IPDSAcknowledgeInterval="{0|1}" PDF l Optimization of embedded TrueType fonts on Unix Introduced in v121019.v713. TrueType fonts referenced in AFP are converted to embedded TrueType fonts in PDF. Font optimization (subset fonts) for embedded TrueType fonts was at first only supported on Windows but not on Unix. Since v121019.v713 font optimization is also available on Unix. 16.7.2.6 Papyrus Objects (WebControl/WebRepository/IPAS) General information Since v7.13 we provide now two Object Spaces: l objects_system_and_application.tar (on DVD under ISISCD03\objects\) l objects_system.tar (on DVD under ISISCD04\objects\) The installation routine offers them as follows: l PAPYRUS WEBREPOSITORY/WEBCONTROL n V7.1 for Windows - first installation Application Object Space n V7.1 for Windows - first installation System Object Space (install individual TRF) n V7.1 for Windows - update getstartede V7.6 SP3 308/389 Appendix: main updates in V7.1 Papyrus Objects Kernel l Improved performance for searches in auditing results Introduced in v120709.v713. Adapter l Multiple MQ Adapters can connect to a single MqQueue Introduced in v120912.v713. Using multiple MQ Adapters connected to the same MqQueue enables a load balancing to improve the performance if otherwise too many MQ messages had to be processed coming from one MqQueue. l SOAP Adapter Enhancements n Support for: u namespaces split across multiple XSD files u import of schemes embedded with Object Space l User Node Node dedicated for the storage of user accounts, which is used in big installations with several thousand users, to relieve the Domain Controller from the user authentication. l "Only run once" attribute of Common Rules When the monitored object is changed multiple times (e.g. common rule modifies monitored object triggering it again, etc.) it's THEN clause is executed per modification. Activate the Only run once option of the common rule, thus a modified object which is in the transaction for commit will run this common rule only once. This is valid for the THEN part of a common rule, the WHEN part may run multiple times (up to 50 times). Papyrus Desktop l Classes are now displayed in the Repository with their internal names instead of their visible names Introduced with v120806.v713. Option "Show Visible name of Classes" in the settings dialog allows to switch back to the old behavior. l New toolbar with simple search Introduced with v120806.v713. With the upper right search input field of Papyrus Desktop it is possible to search for objects by name (case insensitive with support for wildcard characters '*' and '?'). Papyrus EYE Widget desktop l Automatic Log-off for EYE Widget applications Introduced with v12083.v713. The new attribute "Log off timeout" on the user's Session is used to define this. Papyrus EYE Widget plugin l Support for HTTPS communication via the web browser Introduced in v120823.v713. To switch on NP-interface communication, which is needed for instance for the PersAuth authorization, set the environment variable ISIS_EYEWDG_InternalFlags=1. getstartede V7.6 SP3 309/389 Appendix: main updates in V7.1 Papyrus Query Language (PQL) l PQL function "SetFieldValue" Allows to change fields of a PQL set. l PQL function "GUID" Generates a GUID 16.8 Main updates in V7.12 16.8.1 Main updates in V7.12 (DVD v131216) Certain Windows updates lead to product crashes Due to an incompatible Windows function change, the installation of the following Windows Updates can lead to product dumps on product termination. This applies also to all processes started by the Papyrus Objects Kernel and is valid for all 7.12 ISIS releases prior to this release. - Windows Update KB2862973 - Windows Update KB2882822 - Windows Update KB2875501 To prevent ISIS processes from abnormal termination caused by the incompatible Windows function change, either uninstall the Windows Update or install the present ISIS version (V7.12 DVD v131216). 16.8.2 Main updates in V7.12 (DVD v120829) This DVD includes ISIS products of version V7.12. 16.8.2.1 General changes l All products supporting the "Generate & View as PDF" functionality, that is Papyrus Client in document generation mode, Papyrus Canvas and Papyrus Designer, use preinstalled Adobe Acrobat libraries as plugin from now on. They do not need the according Adobe Acrobat DLL be copied to the ISIS common libraries directory ("\isiscomm\w3\lib") anymore. l Running Papyrus Objects on z/OS Unix requires correct setting of IPCSHMMPAGES parameter It is recommended that the IPCSHMMPAGES parameter be set, which specifies the maximum number of pages for shared memory segment, to a value of at least 8192. Set the parameter either by /SETOMVS IPCSHMMPAGES=8192 command or permanently in BPXPRMxx parmlib member. A minimum of 4096 is required (i.e. IPCSHMMPAGES=4096) to be able to run the Papyrus Objects kernel. 16.8.2.2 Papyrus AFP PrinterDriver l Structure and files reduced to Version-3 Driver. 16.8.2.3 Papyrus Client Canvas l New parameter UseBrowserForTab handles presentation of Papyrus AFP Viewer plugin called by Papyrus Client Canvas The syntax of the parameter is as following: UseBrowserForTab={"YES"|"NO"} Default: "NO" Sample: file:///D:/_test_/test/txtlink/docdef/txtlink.ipj?&UseBrowserForTab=YES YES ... Clicking "Generate & View" opens the Papyrus AFP Viewer plugin in another browser tab. NO ... Clicking "Generate & View" opens the Papyrus AFP Viewer plugin in the Papyrus Canvas plugin. getstartede V7.6 SP3 310/389 Appendix: main updates in V7.1 16.8.2.4 Papyrus Designer, Papyrus DocEXEC l New TEXT/TEXTPROMPT subcommand to specify dynamic links (hyperlinks, links to pages, links to bookmarks) The functionality was introduced in v120810.v712/v120813.v713 and has the following syntax: _LINK(<'BOOKMARK'|'LINKTOBOOKMARK'|'LINKTOPAGE'|'LINKTOEXTERNAL',, l New CHECKRESOURCES option in AFPIMPORT command This extension checks all resources used - also nested resources - and displays an error message such as PPDE1019E 'C0D0GT10' resource not found (at 02B20DF0,02A65C30) RN:2 if a resource cannot be found and stops the checking of the current page. l Improvement of the EXIST function In prior versions, the EXIST function returned a positive value when an array with null or negative index was checked. Sample: EXIST(ARRAY[0]) or EXIST(ARRAY[-1]) returned value 1. As using null or negative value in an array index is considered as incorrect data, the mode of operation has been improved with v120627.v712 leading to the return value 0. l New TEXT/TEXTPROMPT/CANVASPROMPT parameter "Variable merge" The new functionality allows to avoid unintended blanks and/or empty lines. Possible values: n 0 ... No change to previous behavior n 1 ... Blanks before empty variables are omitted n 2 ... Lines containing only empty variables, blanks and tabs are omitted n 3 ... combination of point 2 and 3 l Calculation of shaded text size has been improved Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. l New chart parameter OCAColorOrder="Old"|"New" default="Old" Old ... Backward compatible color order in charts. Different objects with same OCA(x) number use different colors. E.g. OCA(3) is magenta in boxes but green in charts. New ... The same OCA(x) number leads to a same color in every object. getstartede V7.6 SP3 311/389 Appendix: main updates in V7.1 l Widow/Orphan handling improvement for COLUMN command Due to the improved page break processing in columns, the parameter COLUMNIMPLYNEWLINE was omitted. In v120723.v713/v120723.v713 the parameter was reactivated: The Papyrus DocEXEC profile parameter has the following syntax: COLUMNIMPLYNEWLINE={"Yes"|"No"} Default="No" The handling of COLUMN, which is a subcommand of the TEXT command, was improved in V7.12. In V7.02 and older V7.12 versions, COLUMN always causes a linespace. In newer V7.12 versions, a linespace is only created if paragraph data exist. COLUMNIMPLYNEWLINE has to be set to "Yes" to invoke the V7.02 mode of operation. The page break processing was changed in v120730.v712/v120726.v713: In older V7.12 versions, the amount of text was evenly distributed to the defined number of columns. Now the text is first checked for paragraph breaks and BREAK(ON) commands to break the text into the columns at that points. Only if there is no possibility to wrap the text in this way, the text is wrapped at every possible point (NEWLINE, linebreak). Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. l New system variables $ACTTIMEMS, $TIMEMS, $ACTTIME_MICROSEC, $ACTTIME_MILISEC, $TIME_MICROSEC, $TIME_MILISEC Introduced in v120403.v712. $ACTTIMEMS, $TIMEMS have a similar format than the $ACTTIME system variable. $ACTTIME_MICROSEC, $ACTTIME_MILISEC, $TIME_MICROSEC, $TIME_MILISEC have a similar format than the existing $TIME_MIN/SEC system variables. 16.8.2.5 Papyrus Designer and Server - FixForm l Implementation of text files Text files for BIC and IBAN validation can be implemented into Papyrus Designer/FixForm by applying the internal rule Payment Validation. For details, see chapter "Payment validation" in "Designer Capture Application Developer Guide (pcddge)". l New Layout check box By selecting the Layout check box in the Add Schema Element dialog, the user can define, that instead of a new child element a layout is created in the Definition frame. For details, see chapter "Menu "File"" in "Designer Capture Application Developer Guide (pcddge)". getstartede V7.6 SP3 312/389 Appendix: main updates in V7.1 16.8.2.6 Papyrus Objects (WebControl/WebRepository/IPAS) Papyrus Objects Kernel l ISIS_PCS_PERFMON This command line parameter and environment variable allows to define an alternative monitoring system. l User of the Agent As alternative to adding Role and an optional Project to an Agent, it is also possible to add a User object instead which allows it to perform its tasks as if it was this user. To enable this feature, choose an option in the Logon as client application attribute for a correct session handling. With that even system attributes like $CurrentSessionId and $CurrentUserId used in PQL scripts have values according the User object below the Agent. Note that it is not possible to specify more the type in more than one list of classes. l Target codepage parameter for MQ type properties Now it is possible to specify a target codepage for storing data in binary attributes. When storing the data to string attributes, always target codepage 1202 is used. Note that it is not possible to specify more the type in more than one list of classes. l Introduced possibility to define another directory for automatic import of TRFs Introduced in v120202.v712. By default the Domain Controller kernel checks its working directory for transfer files (*.TRF) to be imported. This check occurs during startup of the kernel (pocxxknl), every 10 minutes, and when the user clicks the "Trigger AutoImport" button of the Transfer Collection. Now it is possible to specify another directory for the automatic import of transfer files (*.TRF) in new attribute "Auto import path (AutoImportPath)" of the Import Settings. Note that it is not possible to specify more the type in more than one list of classes. l Implemented new configuration value (2) for virtual parent references 0: no virtual reference (a real link to the other object is stored) 1: virtual reference with link to Logbook collection when no other real link exists 2 virtual reference with deletion of object when no other real link exists Introduced in v120730.v712 getstartede V7.6 SP3 313/389 Appendix: main updates in V7.1 Object Space l Role of a Common Rule Without a Role, the Common Rule is authorized by the Role of the user who triggered it by his or her modification. By adding a Role to a Common Rule (supported from v7.0 onwards), it authorizes the execution of the THEN clause. As soon as a Role has been added to a Common Rule, the Use role for WHEN attribute appears, which allows to define that even the WHEN clause shall be authorized by this Role. Note that it is not possible to specify more the type in more than one list of classes. l Agent may have only one Role An Agent may only have one Role. It is anyway better to use custom Roles for Agents that authorize all their tasks. Due to versioning mechanisms using more than one PM Role might otherwise lead to an undesirable results. Note that it is not possible to specify more the type in more than one list of classes. l Context Roles Simplifies the management of user accounts regarding the versioning. Instead of referencing the PM Roles of all users that should be part of a certain Project Management below it, only one Context Role is needed that all users share, thus only this Context Role has to be referenced below the Project Management. Papyrus Desktop l Search feature of Class Diagram (UML) The search bar allows to find and highlight classes/templates in the Class Diagram (UML) based on the class/template name or the name of class properties (attributes, methods, etc.). Note that it is not possible to specify more the type in more than one list of classes. l Question button in toolbar of windows While pressing [F1] displays the help for the selected object, clicking the question button on the right-hand side of the toolbar displays the help for the view itself (e.g. settings views, version chain view, merge view, etc.). These help texts describes how the current window is constructed and how it is used (e.g. how to use the Settings Explorer). Note that it is not possible to specify more the type in more than one list of classes. l New method parameter "hidecolumns" for PQL table frame This method parameter allows to hide columns in the PQL table frame, e.g. those influencing the output style of the table rows: hidecolumns=$background,$objtype,$deploymentstate getstartede V7.6 SP3 314/389 Appendix: main updates in V7.1 Papyrus Query Language (PQL) l New PQL functions in v7.13: $Now, $NowUtc, $MilliSeconds, $MicroSeconds, $NanoSeconds, $AddMilliSeconds, $AddMicroSeconds, $AddNanoSeconds, $GetTimezoneOffset, and $SetTimezoneOffset l Exclusion of classes using the NOT operator '!' Put the negation operator '!' at the beginning of those internal class names that shall be excluded. The following PQL statement returns all types of Adapters, except Scan Adapters: return @Queue\$allchildren(Adapter, !ScanAdapter:).$name,$id; l Support for multiple type filters per PQL statement It is possible to use more than one type filter per statement by specifying them as comma delimited list, e.g. $search($classes,$templates of Task,Folder:).$displayname,$id; Note that it is not possible to specify more the type in more than one list of classes. l New PQL function "GetPQLHeader" Introduced with v120329.v712. Returns a PQL set containing the information defined in $PqlHeader.Id and $PqlHeader.Description. 16.8.2.7 Papyrus Server IPDS l New parameter IPDSAcknowledgeInterval defines after how many AFP pages an acknowledge is requested from the printer. The parameter is implemented in v120810.v712 and later versions and was introduced because of optimized performance on very fast continuous-form printers. IPDSAcknowledgeInterval=" l New parameter IPDSCutSheetEmulationMode defines to print duplex as page-by-page on roll-feed and continuous-form printers. The parameter is implemented in v120810.v712 and later versions. IPDSCutSheetEmulationMode="{ NO | YES }" l Since version v120629.v702 IOB is fully supported. AFP Tuner l New parameter TUNWhiteSpaceManagement Enables white space management mode for finding white space in an AFP. l New parameters TUNWSMFirstDocPage, TUNWSMLastDocPage, TUNWSMLeftMargin, TUNWSMRightMargin, TUNWSMBottomMargin Specifies where to search for available white space on a page. 16.8.3 Main updates in V7.12 (DVD v120329) This DVD includes ISIS products of version V7.12 with Papyrus Objects. getstartede V7.6 SP3 315/389 Appendix: main updates in V7.1 16.8.3.1 General changes l Codepage directory changed from isis\cpts to isiscomm\data\cpts - The cpts directory contains *.dat files, which include the infotrmation for using specific code pages. Most code pages are handled by the central DLL (e.g. on Windows cdpdll.dll), code pages for Asian languages are not included. - All products use the isiscomm\data\cpts directory for code page-specific files and ignore all other settings (standalone ICD files, Papyrus Objects: attributes, command line parameter). - All MSI packages were enhanced with isiscomm\data\cpts. - Customers upgrading from older version to V7.10 and using specific code page files have to copy them to isiscomm\data\cpts. l Introduction of the subnet functionality The according node settings allow to define groups of nodes and rules for allowed/not allowed connections to avoid connection timeouts. l Enhance Papyrus EYE technology with automatic caching The automatic caching improves performance with Papyrus EYE Desktop and Papyrus EYE Plugin. l Windows compliant MSI packages All MSI packages have no dialogs. They were changed to work without the ISIS installation routine. Additionally, since v120307.v712, they use by default the Win program directory for the program installation and the Win AppData directory for user data (e.g. PCS Log, cache for EYE Widget applications, Papyrus Canvas persistent cache, ...). These directories differ depending on operating system and language. Samples - program directory: C:\Program Files\Common Files\ISIS - data directory: C:\Documents and Settings\ l Spellcheck and hyphenation changes since v120120.v712: The search order for spellcheck and hyphenation was improved. For details, see "ISIS OverView and Papyrus Spellchecking and Hyphenation Installation Guide (prox_e)". Spellcheck and Hyphenation libraries can be stored in and used from the Repository. l Name of this document's file has changed from "news_e.txt" to "New Features V7 Details.pdf" It can be found on DVD under \ISISCD01\ and \ISISCD03\document\general\. l Papyrus Capture products and Recognition Engines Since v101119.v702 Capture products require a new new version of Omnifont8 Recognition Engine, which is available on the DVD. The new engine allows to run different processes on different CPUs/cores. Since 7.1, the Omnifont10 recognition engine is supported and available on DVD Since 7.1, the Recostar recognition engine is removed from DVD getstartede V7.6 SP3 316/389 Appendix: main updates in V7.1 16.8.3.2 Release of Papyrus e-mail with HTML for Windows The new product "Papyrus E-Mail with HTML" allows to convert AFP documents produced with ISIS products to HTML or EMAIL HTML (EML) documents which can then be embedded in the mail body. It requires Papyrus WebRepository and Papyrus E-Mail authorization. The conversion of 3rd party AFPs is not supported. "Papyrus E-Mail with HTML" combines Papyrus E-Mail with Papyrus HTML which can be used like any other Papyrus Server module. 16.8.3.3 WebArchive/CGI solution removed from ISIS DVD The WebArchive/CGI solution is not support any more. It is followed up by a WebRepository based solution. In case of further questions contact ISIS Support, please. 16.8.3.4 Overview AFP Designer l Support of Unicode line data and Unicode outline fonts introduced in version v120126.v712. 16.8.3.5 Papyrus Designer, Papyrus DocEXEC l TrueType Fonts (TTF) Support of usage of TrueType fonts (TTFs) for producing of AFPDS and for conversion into other formats. AFPDS is able to reference TTFs for printing and viewing. This means that it is not required to create particular AFP fonts (by means of the Papyrus Font Converter) but to directly reference external TTF located in the default directory of the operating system. Prerequisites are: 1. Output codepage must be Unicode (1200). 2. MDR generation must be enabled. 3. The default library must contain the following entry: TTF="C:\Fonts l New TEXT and TEXTPROMPT subcommand: _TABLE TEXT and TEXTPROMPT commands can contain tables. Creating and editing is possible in TEXTPROMPT. In the TEXT command tables can be created by using the subcommand _TABLE. l Profile parameter FILECACHE extended for persistent resource cache FILECACHE=P, l New CANVAS command New DOCDEF command CANVAS allows to add, rearrange and change properties of the following SL commands in Papyrus Canvas: Box, Chart, CreateObject, Output, OVL, Place, Rule, PSG, Sticker, Text, Textprompt l New Feature: Import words into the user dictionary from text file Introduced with v120228.v712. A new button (Add List) was implemented in the user dictionary dialog. The text file can be searched in the file system. The words have to be separated by whitespace characters. getstartede V7.6 SP3 317/389 Appendix: main updates in V7.1 l New command DEFAULTS to define default values for various command settings The command allows the definition of defaults like e.g. direction. l New TEXT and TEXTPROMPT subcommands _PARAGRAPHCOLOR l Support of regular expressions in DFA command Same syntax like in PQL: MATCH2( l Changed handling of OCA colors, new OCA color WHITE The new color can be defined in Papyrus Designer as OCA(WHITE) or OCA(15), in the generated AFP it will be written as STC(7) 'OCA WHITE'. In the charts all 16 OCA colors can now be defined. In some cases the result can slightly differ from old versions. In old versions only 7 OCA colors could be defined, OCA color 8 was interpreted as white, now OCA color 8 is treated as black. Note: Different behavior of older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. Changing the keywords like demonstrated in the sample assures correct behavior with any version. l Changes in handling of line thickness in the TABLE command The table line thickness was not evaluated correctly in certain cases. In certain cases line thickness is now different which causes table content to slightly move in the y direction. Note: Different behavior of older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. 16.8.3.6 Papyrus AFP Viewer l Possibility to save the displayed AFP to the file system The "Save AFP as..." function allows to save the displayed AFP to the local file system. 16.8.3.7 Papyrus Client Vanvas l Enhanced search functionality allows to search whole document as well as active TEXTPROMPTs since v120309.v712 l New CANVAS command dialog and toolbar (see the documentation for usage) l Google translator interface to help with translation of TEXTPROMPT contents 16.8.3.8 Papyrus Client l Changed Copy/Paste behavior When copying text into the clipboard it is not absolutely necessary to activate the "Unformatted" checkbox, because text and formattings can be stored independently due to an additional clipboard format (details see product documentation). When pasting the user can select, if the text shall be pasted with formattings (Ctrl+V) or without (Ctrl+Shift+V). For that purpose profile parameter PastePopup has to be set to "0". With PastePopup="1" the behavior is as before. getstartede V7.6 SP3 318/389 Appendix: main updates in V7.1 16.8.3.9 OverView Image Editor l Transparency can be used for the image types Page Segment, GIF and PNG. 16.8.3.10 Papyrus Server PDF l TrueType fonts (TTF) embedded at conversion Introduced in v120329.v712. TrueType fonts referenced in AFP are converted to embedded TrueType fonts in PDF. During the conversion process the embedded TrueType fonts are optimized (subset fonts). Optimization is only supported on Windows but not on Unix. 16.8.3.11 Papyrus AFP PrinterDriver l Create IS/3 compliant AFPs using external fonts (TTF, OTF, TTC) The "Target Filename and Mode" dialog has the new check box "Generate IS/3 Compliant doc.", the "Options | Advanced Setup" dialog has the new check box "True Type Fonts". These settings allow to create AFPs using external fonts (TTF, OTF, TTC). 16.8.3.12 Papyrus Postprocessing/Printpool PDB PDBX3O11 l New module for connection to Oracle 11 on AIX 16.8.3.13 Papyrus Host l Introduction of permanent running mode for Papyrus Archive The new PPH control parameters MAX_TASK(n) and PERMANENT(YES) and ICD parameter RunInLoop = YES cause the Archive to wait for new input after successful check-in. This increases the performance especially when running many small jobs 16.8.3.14 Papyrus Objects (WebControl/WebRepository/IPAS) Papyrus Objects Kernel l Save and export log Objects that require logging such as Nodes, Sessions, or Tasks offer the opportunity to save log information into a log object. Virtually every object is able to create such log objects. Whether or not a log object can be created depends on a specific child reference definition. The purpose of a "Saved Log" object is to keep a copy of the messages related to a certain job (Task, etc.). It is not only possible to automatically add a "Saved Log" object to a Task when it reaches certain states, it is furthermore possible to define that these job logs are also automatically exported to the file system. For more details, see "Papyrus WebRepository & WebControl Installation and Administrator's Guide (poinste)". Object Space l Scope-based settings The Settings Explorer allows to organize and define settings according to the company structure without the need to adopt the frameworks. l ID Generator for Object ID and Binary Id The ID Generator allows to create unique subsequent Object IDs and Binary IDs. getstartede V7.6 SP3 319/389 Appendix: main updates in V7.1 IPAS l Reduced authorization requests at IPAS Plugins reuse since v120217.v712 the authorization from preceding login when running in a Desktop (Classic or Eye) or in a Papyrus Objects portal application in a browser. Nodes (Kernel and Object Space since v111221.v712) handle their authorization via the Domain Controller. In case of large-scale installations with a high number of nodes and/or users working with plugins in desktop or a portal application, this reduces the authorization requests accordingly. getstartede V7.6 SP3 320/389 Appendix: main updates in V7.0 17 Appendix: main updates in V7.0 If you upgrade from an earlier version to the newest version, use the appendix to see a history of all changes that have accumulated. Note that the cross-references in the appendix refer to chapters in documents of the same version. This means that some of the History of Changes entries in the appendix may include cross-references to chapters that do not exist anymore in the newest version of the document or whose information was updated in the meantime. If you are in such a case interested in the details you will need to access the documents of exactly that version. 17.1 Main updates in V7.02 17.1.1 Main updates in V7.02 (DVD v111108) 17.1.1.1 General changes l Changed AFP image handling With v110920.v702 image optimizations were introduced for processing AFP structures. Previously sliced image data is now handled as one image (e.g. charts with patterns) which can produce different results with Papyrus AFP Compare depending on the used version (new version might show less differences). Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Carefully read the description and check if existing projects are concerned. 17.1.1.2 Papyrus AFP Compare l Potentially other differences due to changed AFP image handling. See "Changed AFP image handling" under chapter "General changes" for more information. 17.1.1.3 Papyrus Designer, Papyrus DocEXEC l Improved rounding behavior for the calculation of text positions The improved rounding behavior, introduced with v110518.v702, ensures identical results on all platforms. However, the improved behavior can cause deviation in text positioning in the range of 1 or 2 PELs. Additionally, a bug has been fixed in the field of text hyphenation and text positioning, with the result that text positioning could deviate up to several PELs. Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Carefully read the description and check if existing projects are concerned. l PDECON was extended with function READFILE The function READFILE reads a text element into a DocEXEC variable. The size limit is 4 MB, the line delimiter x'0d' is converted to a blank like in FILTER. Sample: DATA = CONVERT('PDECON','READFILE',FILE,1252) ; l New string function COPY('ARRAYNAME1','ARRAYNAME2') The function copies ARRAYNAME1 to ARRAYNAME2. If not existent, ARRAYNAME2 is created. It returns 0 if failed or the MAXINDEX value of the copied array. l Improved calculation of the BAROBJ position In certain cases the next object was placed in a wrong position if it's vertical position was CURRENT. getstartede V7.6 SP3 321/389 Appendix: main updates in V7.0 l Corrected RGB and CMYK image handling n Monochrom color bitmap was converted to RGB and was written in CMYK format. Now no unnecessary conversion is done. l IOB with color table was always written to CMYK format, not its always written in the correct format. These changes could lead to different colors in images in the generated AFP and because of the lossless conversion in case of RGB images to bigger AFP size. Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Carefully read the description and check if existing projects are concerned. 17.1.1.4 OverView Image Editor l Support of color profiles (ICC) for CMYK 17.1.1.5 Papyrus Server PDF l Hyperlinks in AFP and PDF can be added by means of sticker definitions Hypertext stickers can be used to create internal document links between pages like it is used in Table of Contents. A click on internal document link on page x will open linked page y, and vice versa, a click on internal link on page y will link back to page x. For this LinkToPage feature the name of the sticker must be "LINKTOPAGE", it is triggered by parameter HyperTextStickers, the sticker selection is done by the common color matching method. Sample for sticker name: REFERENCE('LinktoPage:'!(expression)) l New parameters FLASHSTICKERS="" and SOUNDSTICKERS="" n Flash can be embedded in a PDF by creating a sticker named RICHMEDIA. The sticker text gives the path to the flash animation (*.SWF). Currently flash is supported. n Sound can be embedded in a PDF by creating a sticker named SOUND. The sticker text gives the path to the sound (*.WAV). Currently WAV format is supported. PDF-in l New parameter PINTransparencyThreshold=[0..255] Default=255 The parameter was introduced with v110523.v702. In AFP, transparency is defined through a raster image. This parameter defines the threshold at which transparency applies, in terms of brightness. 255 represents maximum brightness (white): only white color (e.g. RGB=0,0,0) is rendered as fully transparent in AFP. 0 represents minimum brightness (black), which means that all gray levels are converted as transparent. Typically, this parameters is set to high values, near white (245-255) when fine tuning is needed on image result. 17.1.1.6 Papyrus Host l support MQ 7.0.1 since v111024.v702 getstartede V7.6 SP3 322/389 Appendix: main updates in V7.0 17.1.2 Main updates in V7.02 (DVD v110208) 17.1.2.1 General changes l Check for old shared memory files and remove them automatically Since v110316.v702 products will automatically check for old shared memory files and remove them. Shared memory files are automatically created on Unix and z/OS when ISIS products are running and removed as soon as the last product ends. In case of dumps shared memory files could stay and cause problems when starting again products. The DVD includes all z/OS native products on level v110316.v702, the other platforms will be updated later. l The tool 'shutwin.exe' has been versioned to -> 'shutwin31.exe' As the tool uses other general DLLs from '.\isiscomm\w3\lib' it had to be versioned. Be aware that existing jobs using this tool have to be adapted accordingly. l Use different directories for PCS logs of different nodes on same machine If several nodes run on the same machine it is strongly recommended to use different directories for the PCS logs. The start scripts delivered in the kernel directories on ISIS DVD were enhanced accordingly. Sample: SET ISIS_PCS_LOGDIR=%ISIS_COMMON%\logs\DC l Running more than 9 Kernels on one machine The PCS parameter ISIS_PCS_MAX_LOGDIRS defines the maximum number of directories for PCS logs and by that indirectly the number of parallel running kernels. It should be set at least to number of parallel running kernels + 1. Before v110404.702 this parameter was set by default to 10; from v110404.702 onwards, this parameter is set to ISIS_PCS_MAX_LOGDIRS=50 by default. l The PDF files of the documentation were renamed and now use the full document name l The type of this document 'DVD News Information' has been changed from plain text to PDF The PDFs 'news_e.pdf' and 'news_d.pdf' can be found on DVD under \ISISCD01\ and \ISISCD04\document\General\. 17.1.2.2 ISIS installation routine l New version of Hardlock Key driver under \install\keydriver\haspdinst.exe as successor of hldinst.exe This version supports the installation of the keydriver on Windows Server 2008 R2. Error messages during installation on Windows 2000 can be ignored, the driver will work nevertheless. Depending on the operating system a Wizard might open at first usage for finalizing the installation. If this is the case just step through the dialogs. l Check additionally for modification date in case of same version The installation routine checks the version of products to assure that newer (younger) versions are not overwritten by older versions. The installation automatically checks the version number (if empty the modification date) for files of type*.exe, *.dll and *.ocx and the modification date for other files. ISIS products include the build number in the version number of files of type *.exe and *.dll. In certain cases (bdbdll31) the build number was not enhanced with new versions which might could cause newer bdbdll31 not to be installed with older version of the installation routine. 17.1.2.3 OverView AFP Designer l New profile parameter UseLspFromField={"YES"|"NO" } Default="YES" By Default the line spacing is taken from FIELD, if set to "NO" it is taken from the PRINTLINE. getstartede V7.6 SP3 323/389 Appendix: main updates in V7.0 17.1.2.4 Papyrus Designer, Papyrus DocEXEC l Improved rounding behavior for the calculation of text positions The improved rounding behaviour, introduced with v110518.v702, ensures identical results on all platforms. However, the improved behaviour can cause deviation in text positioning in the range of 1 or 2 PELs. Additionally, a bug has been fixed in the field of text hyphenation and text positioning, with the result that text positioning could deviate up to several PELs. Note: Different behavior as compared to earlier product versions: The default behavior has changed. Upgrading from earlier product versions to the version of this DVD may lead to different results. Please carefully read the description and check if existing projects are affected by the changed behaviour. l Improved handling of ICC profiles Introduced new checkbox in APPLICATION-OUTPUT-FORMAT to define whether the ICC profile will be concatenated or not. 17.1.2.5 Papyrus Derver PCL l New parameter PclInsertEmptyPage={"YES"|"NO"} Default="YES" The parameter was introduced with v110802.v702. Empty pages caused by a duplex FormDef but missing back page (no data on page), are skipped when using PclInsertEmptyPage="NO". The Default "YES" leads to the old behavior. l Possibility to skip banner page when using PclPrintUser PclPrintUser="Operator;skipL" PS l Possibility to skip banner page when using PscrPrintUser PscrPrintUser="Operator;skipL" PDF-in l Support creation of overlays (OVL) per page into Resource Collection The new parameters PINOvlNameRoot and PINOvlAlphaCount allow a distinctive naming strategy combined with an incremented counter for the subsequently generated OVLs. IJPDS l Support 600 DPI for horizontal resolution (IjpResX="600"). Tuner l New parameter TUNPatternBWMode="0|1" With TUNPatternBWMode="0" OCA colors are dithered to default FS10MMR (b/w) images. With TUNPatternBWMode="1" all OCA colors are set to OCA color black. To be backward compatibile the default is TUNPatternBWMode="0" (dither). 17.1.2.6 Papyrus Host l Reduce CPU consumption for idle Papyrus DocEXEC in PermanentRunning mode The new pcs parameter ISIS_PCS_PASSIVE={0|1} (Default=0) was introduced to reduce the CPU consumption by disabling pcs functions not needed when running z/OS native products. In case of running Papyrus DocEXEC via Papyrus Host in Permanent-Running mode it reduces the CPU consumption in idle time. getstartede V7.6 SP3 324/389 Appendix: main updates in V7.0 17.1.3 Main updates in V7.02 (DVD v101103) This DVD includes version V7.02 with Papyrus Objects. l Update Papyrus Objects/Object Space It is mandatory to update every Object Space (Domain Controller and IPAS standalone) together with the upgrade to the product versions on this DVD. If the Object Space is already on level V7 and is not updated it might happen that nodes cannot be started. See chapter "Update Papyrus Objects/Object Space" above under "General information" for further details. 17.1.3.1 Release of Papyrus AFP Viewer and Papyrus Client Canvas l Papyrus AFP Viewer (PAV) is a new product working similar to Papyrus Client Viewer. Papyrus Canvas (PCN) is a new product working similar to Papyrus Client Extended allowing to do prompting of variables and text. The new products have a new GUI and especially in case of big documents they might provide higher performance. They do not have exactly the same functionality. In case of using certain features it has to be checked if this functionality is supported or not. The standalone versions and the plugins except the browser plugins are automatically installed when selecting Papyrus Client. Papyrus Objects uses the Papyrus AFP Viewer plugin by Default for viewing AFPs, Papyrus Designer and OverView AFP Designer when doing a Generate and View. In Papyrus Designer the plugins can be selected via Options | Plugins. Deselecting "npisispav33 (AFP)" will use the classic Papyrus Client Viewer plugin for Generate and View. Installing browser plugins requires to use either the classical plugins or the new ones as both are using the same mime types for automatic start. In directory install the new plugins are available as MSI packages l ISISPluginInstaller.msi ...... Papyrus Client plugins l ISISAFPViewerInstaller.msi ...... Papyrus AFP Viewer plugin l ISISPapyrusCanvasPluginInstaller.msi ... Papyrus Canvas plugin 17.1.3.2 Release of Papyrus AFP PrinterDriver for Windows vista and Windows 7 l Papyrus AFP Printer Driver V7.0 runs on Windows Vista and Windows 7 32 Bit and 64 Bit 17.1.3.3 Release of Papyrus IMAP Receiver l The IMAP Receiver integrated in Papyrus Objects receives mails from an IMAP Server. 17.1.3.4 Release of SPNEGO mechanism for AIX l SPNEGO allows the Single Sign-On (SSO) based on Papyrus Type Manager LDAP. getstartede V7.6 SP3 325/389 Appendix: main updates in V7.0 17.1.3.5 Papyrus HTTP server functionality requires Papyrus server/https authorization l Papyrus HTTP functionality in server mode requires the Papyrus Server/HTTPS authorization Papyrus HTTP-Adapter in portal, running portal with "nonamed" users (via anonymous login), Papyrus HTTP Receiver/Sender (pocxx700\http) and Papyrus HTTP Client (pocxx700\htc) require the Papyrus Server/HTTPS authorization when running in server mode (unlimited parallel requests). Using the HTTP functionality in single request mode (one session, i.e. one request at one time) is possible with the Papyrus Client authorization. For the single request mode the new attribute "ParallelRequestLimit" has to be set to 1, the Default is "unlimited". The concerned products (portal and HTTP Receiver/Sender at startup, HTTP Client with first request) search for the Papyrus Server/HTTPS authorization. If it is not available they automatically check for Papyrus Client authorization to run in single request mode. In many cases a portal e.g. should run without extra authorization, in this case set the new attribute "ParallelRequestLimit" to "Unused" to avoid the usage of an authorization. See the documentation for further details. Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. 17.1.3.6 General changes l Release Papyrus Color to Black and White Conversion for AIX and Solaris l Release Papyrus Image Converter for Linux x86 l Release bundling tools (\ISISCD06\pppx3700) for AIX l Updated test certificate files for Digital Signature l The files are available on DVD under \ISISCD01\demo\certificate_pdf, the certificate expires 2020. Updated test certificate files for Portal/HTTPS The files are available on DVD under \ISISCD01\demo\certificate_portal, the certificate expires 2020. l The user defined hyphenation is available on IBM host 17.1.3.7 ISIS installation routine l New installation dialog with radio button "System" (activated by Default) and "User" to select the variable type for the environment variables created/updated by the installation routine. l If a user is logged in without administrator rights, a message informs that the installation process cannot be continued. 17.1.3.8 OverView AFP Designer l New possibility to create color PSEGs 17.1.3.9 Papyrus Designer, Papyrus DocEXEC l Improved indent handling with HTML import The calculation of the first line negative and positive indent was corrected. getstartede V7.6 SP3 326/389 Appendix: main updates in V7.0 l New system variables $VAR_PREFIX and $VAR_INDEX. The two system variables can be used to optimize the DFA coding, particularly when using XML as input data. They have to be assigned to be used. In presence of groups of variables which share the same structure (similar names with a change only in the prefix), this feature can be useful to handle all the variable names at once. l New system variables working similar to error/warning but only for user messages (MESSAGE command) n &USER_GENMSG The formatted message for category 0 n &USER_INFOMSG The formatted message for category 1 n &USER_WARNMSG The formatted message for category 2 n &USER_ERRMSG The formatted message for category 3 n &USER_FATALMSG The formatted message for category 4 n &USER_RETCODE The return code of the last message l New functions STARTAREA, ENDAREA and GETAREA The new functions STARTAREA( l Enabled REFERENCE() in AFPIMPORT command l New barcode Royal Mail RED TAG This bar code is similar to the RM4SCC barcode. It uses a specially designed four-state symbol with exactly 51 bars including a RED TAG indicator printed at each end of the symbol. l 4-state barcode (Intelligent Mail Barcode) BCOCA implemented The parameter "OutputType" BCOCA is supported. l Enhancement of paragraph numbering to allow sublevels Definition with PARAGRAPH_NUMBERING( Sample: PARAGRAPH_NUMBERING($PARENT_PAR_NUMBER!'.'!$PAR_NUMBER,1) New command: PARAGRAPH_NUMBERING_CLOSE() This function closes the current sublevel paragraph numbering and continues the parent one if any. l Enhanced hyphenation functionality for compound words New parameter UseVerifiedHyphenation={"YES"|"NO" } Default="NO" n YES ... Compound words are split and the split words are analyzed by spellcheck and hyphenated n NO ... Compound words are not analyzed, in certain cases the hyphenation might be wrong (e.g. compound words with "ss" and a vowel afterwards like "Abschlussinventur"). Using the enhanced functionality might impact the performance. l Enhanced possibilities for line thickness in pie charts The existing LineThickness parameter was enhanced. Now it is possible to set the thickness of the chart text and separating lines in pels (Default: 1;1). Values have to be defined without single quotes e.g.: 5;1 or 5. Value 0 suppresses line depiction. 5;1 means that the text lines will use 5 pels and the separating lines between the pie segments will use 1 pel for line thickness. getstartede V7.6 SP3 327/389 Appendix: main updates in V7.0 l Modified behavior of CONVERT function Till now some BAROBJ DLL function was interpreted inside the CONVERT function, e.g.: CONVERT('BAROBJ','EAN',4448889990177). This type of usage was not described in the documentation. As the CONVERT function and the BAROBJ DLL are incompatible this might lead to unpredictable results. Now Papyrus DocEXEC checks the compatibility and raises an error message in case of any incompatibility e.g.: "PPDE7303E 'EAN'/'BAROBJ' is not a converter function (at 0292E1F0,018D6FC0) RN:0" The BARCODE DLL can be used inside a CONVERT function instead, e.g.: CONVERT('BARCODE','EAN',4448889990177). Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Removed GenerationType "Inlined image/IOB" from IOBDLL(TIFF_IMPORT) The IOB functionality is covered by the function IOBDEFS. Papyrus DocEXEC always produces inline image using IOBDLL(TIFF_IMPORT) independent of the parameter "GenerationType". The parameter was removed and the message PPDE6003E;"(DOC/168) RN:18 Illegal parameter 'GENERATIONTYPE'='0'" will be issued if the parameter is used. The solution is to remove the parameter "GenerationType" in the concerned DFA file. Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Improved chart layout In barcharts and linecharts the position calculation algorithm was improved. It can cause a small (1-5 pels) difference in the X-axis text and bar/line position. When using the parameter ImagePos the Y-Axis text is aligned to the axis. In older versions the text was placed in the original position and in case of big ImagePos value the distance between the text and the axis was big. l New functions ISTRUE( l Corrected behavior of ENDDOCUMENT in XMLREAD If the ENDDOCUMENT was placed in one of the XMLREAD-related DocFormat (TAGBEGIN, TAGEND, TAGERROR etc..) it was ignored by DocEXEC. Now the document creation is stopped with this command which is the correct behavior. To achieve the old (wrong) behavior, the previously ignored ENDDOCUMENT command has to be deleted. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l New function NUMTOWORDS implemented in CONVERT('PDECON',[...]) This new function validates and converts a numeric value to its representation in natural language. See the documentation for further details. Samples: n Standard conversion (OPTION=0) into English (UK) TEST = CONVERT('PDECON', 'NUMTOWORDS', '000,001.9;EN_UK;0'); result: 'one point nine' getstartede V7.6 SP3 328/389 Appendix: main updates in V7.0 n Conversion with decimals as numbers (OPTION=256) into German TEST = CONVERT('PDECON', 'NUMTOWORDS', '000,001.9;DE;256'); result: 'ein Komma 9' n Validation: decimal separator (OPTION=16 English US) INVALID TEST = CONVERT('PDECON', 'NUMTOWORDS', '789;EN_US;16'); result: '789' (same value than in input: validation not OK) n Validation: decimal separator (OPTION=16 English US) VALID TEST = CONVERT('PDECON', 'NUMTOWORDS', '789.00;EN_US;16'); result: 'seven hundred eighty-nine point zero zero' l New pie chart parameter InnerDiameter to create "ring" charts This parameter allows to create 2D "ring" charts, where the middle of the pie is empty. The parameter defines the inner diameter in mm. l Performance of SUBCHANGE() functions improved l The following DocEXEC functions for Papyrus Objects access introduce a new additional parameter, which can be 1 or 0 (Default 0): n OMS_GETATTRNAME n OMS_GETPARENTNAME n OMS_GETCHILDNAME n OMS_GETATTRIBUTE n OMS_GETMETHOD n OMS_GETSTATE Former versions of these functions - applied on templates created from classes with user defined attributes, methods or states - were not able to retrieve these user-defined properties. The new parameter set to 1 allows to access these user-defined data now. Sample: OMS_GETATTRNAME(OBJID,I,1) - applied on a template - retrieves now also the names of attributes defined by the user on the class the template was created from. < l New parameter FillLowRightCorner{"Don't Fill"|"Fill"} Default="Fill" in the datamatrix barcode If the parameter is set to "Don't Fill", it forces an empty dot in the lower right corner area of the barcode, instead of a default filled dot. The parameter has an effect only with some special constellation of the coded data and barcode size and using the Output Type IMAGE. l Changed default pattern in datamatrix barcode If the coded data does not fill the whole available area in the datamatrix barcode, Papyrus DocEXEC fills the remaining area with irrelevant pattern. This area is not interpreted by the barcode readers. The behavior of the algorithm has been changed which might lead to different pattern with certain combination of coded data and barcode size. The different pattern does not affect the coded data and the readability of the barcode. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l More accurate check of history file syntax (*.HST) The history file contains binary information and has to be transferred in binary mode from Windows to other platforms (mainframe, Unix). Now Papyrus DocEXEC checks if the history files is in binary format, raises the fatal error message "PPDE7174F;"(*/0) RN:-1 History file 'xxx.hst' cannot be opened";;" and stops if the format is not correct. Earlier versions did not perform this check, wrongly transferred (ASCII instead of binary) history files could lead to unpredictable side effects. 17.1.3.10 Papyrus Client Aligned to new DocEXEC version getstartede V7.6 SP3 329/389 Appendix: main updates in V7.0 l New parameter UseLimitedAfp={Yes|No}, Default="No" Yes...Makes it possible to view or print the first 100 pages of a project, which would generate to more than 100 pages No....Issues the known error message, that the generation was unsuccessful, when trying to view or print a project with more than 100 pages. l Enhancement of paragraph numbering to allow sublevels Paragraph styles have to be created corresponding to description of PARAGRAPH_NUMBERING for every kind of numbering (letter, Roman, bullet, ...). See also the description with same paragraph name under "Papyrus Designer V7.0, Papyrus DocEXEC V7.0" above. The new button in Style tooldialog "Decrease Par. level" decrease the selected paragraph and all following paragraphs one level: 1.1.1 Text -> 1.1 Text. l New parameter ToolbarMode={"0"|"1"} Default:"0" 0...usual toolbar with scroll buttons (and at least 1 button on the right) 1...line breaking toolbar l New parameter WinPrintMethod={0|1} Default 0 Defines rasterization operation of the bitmap with Windows printing 0...AND (v610 method) 1...COPY (compatible with monochrome devices, e.g. Fax) l Multiple user defined dictionaries can be defined in pclsc.cfg Sample: -u dict1.usr -u dict2.usr -u dict3.usr The spellcheck dialog is extended with a drop down menu, from which one can select the dictionary to be edited. l The isisweb functionality supports HTTPS/SSL on Windows. l Timings enabled with parameter DETIMINGS= 17.1.3.11 OverView Image Editor l New possibility to save true color PSEG as IOCA FS11 l New possibility to save a TIFF with photometric interpretation "Black is Zero" or "White is Zero" To create a TIFF that can be used with the TIFFG4 DLL in Papyrus Designer/DocEXEC it is required to save the TIFF with photometric interpretation "White is Zero", compression "CCITT fax4", "no strips" and fill order "Most to Least". l New possibility to remove NOPs from a Page Segment The menu command "Defaults | NOP" allows to remove application and/or user NOPs from a page segment (PSG). 17.1.3.12 OverView Font Editor l Introduce language selection The menu point "Options | Language" allows the select the language. 17.1.3.13 Papyrus AFP PrinterDriver l Possibility to create transparency color in OVL and PSG In the "AFP output image type" dialog the new check box "White as transparent" allows to convert white space to transparent color in overlays and page segments. 17.1.3.14 Papyrus Postprocessing/Printpool PAS getstartede V7.6 SP3 330/389 Appendix: main updates in V7.0 PASX3O11 l New module for connection to Oracle 11 on AIX 17.1.3.15 PapyrusPostCalc l Available for Oracle 11 on AIX (ppcx3o11) 17.1.3.16 Papyrus Server General l New parameter GocaRescalableIgnore="{0|1} Default="1" Specifies whether GOCA images shall be rescaled in any case (Default) or depending on the type of GOCA when converting a AFP with Papyrus Server modules to another format such as PCL, PDF or PS. According to the GOCA reference there are rescaleable (GDD16) or not rescaleable GOCA (Default). Rescaleable GOCA (GDD16) were introduced in Papyrus DocEXEC with CD v080317.v620. When viewing AFPs, rescaleable GOCA will be rescaled and Default GOCA is not rescaled. As not every printer supports GDD16 and certain formats have the necessity to rescale like e.g. converting a AFP with resolution 240 to a PCL datastream with 300 Papyrus Server converters by Default rescale any GOCA. To achieve same rescaling behavior like for viewing AFPs to converters, the parameter GocaRescalableIgnore has to be set to 0. Then only GDD16 will be rescaled. Be aware that in this case all resolutions have to match exactly or GDD16 needs to be used to avoid unexpected side effects like too small or too big images. The parameter was introduced with v100826.v702. PageEXEC l The new parameter INPEXIT="ASCIINP" offers a similar on the fly conversion of the line data like the IBM User-exit program "asciinp" on IBM mainframe. PCL l Possibility to print dynamic start and end-banner pages in Papyrus Objects At runtime the values of Papyrus Objects attributes and variables are written on the start and end-banner. l Improved algorithm for rescaling AFP fonts with resolution 240 to 300 PDF/Native l Support of PQL in batch mode The two new parameters PDFTConvertBookmarksThroughPQL and PDFTBookmarksPqlScript allow to define the usage of a PQL e.g. to create complex bookmark structures. This functionality requires the Papyrus WebRepository authorization. See the Papyrus PDF/Native documentation for further details. l Support interpretation of Tumble Back (rotated back pages in duplex) l PdftDigitalSigType="{0|1} Default="1" Usage of PCKS#7 filter for digitally signed PDFs by Default (1), before PCKS#1 was used (0). l Enhance PDFtPrintEmptyPages to skip empty pages from FormDef Additionally empty pages resulting from a FormDef can be skipped by selecting option PDFtPrintEmptyPages = "2". l Enhance PDFTINDEX to skip page info in index value The string "/Page nn" is added to the index value. This might cause problems for further processing therefore the option to not add this string to generated bookmarks was introduced via additional value "skip". Sample: PdftIndex = "cust-name,cust-address,order-number;skip" getstartede V7.6 SP3 331/389 Appendix: main updates in V7.0 l New parameter PDFtResViaDocs= "0|1" allows caching of PDF resources Setting the parameter to "1" will cache already converted PDF resources in memory for reuse when splitting an AFP and convert it to single PDF documents with Split & Archive. In certain cases this might considerably improve the performance. The caching of PDF resources does not work with embedded resources, with overlays and Type0 (CID-Fonts) fonts. PDF-in l Introduction of CMYK support According new values for parameter PinImageMode are n FS45TiffCmyk, FS45TiffRgb, FS45JpegCmyk, PageAsImageTiffRgb, PageAsImageTiffCmyk, PageAsImageJpegCmyk To be fully compliant to IOCA reference, there were additional changes for the image output for option FS45Jpeg and PageAsImageRgb. In v620 and v701 FS45Jpeg produced RGB output, since v702 it produces CMYK output. In v620 and v701 PageAsImageRGB produced inline images in FS45 with JPEG compression in RGB. In v702 PageAsImageRGB produces inline images in FS45 with TIFF compression in RGB. l Support PDFs with transparency PDFs including transparency are correctly converted with Papyrus Server PDFin. l Possibility to build AFP index from PDF file name The new feature is enabled by setting PINGetPdfIndex="4". Related further parameters: n PINFileNameSeparator = "_" n PINFNToGrIndexSep = "//" n PINFNToGrIndexNames = "TLEName1;TLEName2;..." l Improved vector graphic implementation (Goca Vector) Using vector graphic more frequently improves the performance and produces smaller AFP files. The default of parameter PinVectorGraphics was changed to "1" accordingly. In certain cases this might lead to side effects with further processing like e.g. converting the AFP created with Papyrus Server PDFin with Papyrus Server PCL. Related further parameters n PinLineThickness="4.0" {0.0 ... 10.0, Default 4.0} n PinRoundingMode="Round" {0|Floor,1|Round,2|Ceil} IJPDS l New parameter IJPuselogicalpagesize ="{0|1}" Default="1" If the dimension of an image is bigger than the page size assigned for this image, this parameter has to be set to "0". 17.1.3.17 Papyrus Imageconverter l New possibility to save true color PSEG as IOCA FS11 l New option to generate multi page TIFFs The new parameter PICGenTiffMultipage="{0|1}" allows to create multi page TIFFs from several input images of different type. l New possibility to remove user NOPs from a PSEG The new parameter PICRemoveNOPs="{0|1}" has to be set to "1". l New ICD parameter PICPhotometric"{0|1}" Default="1" Setting to "0" creates a TIFF with photometric interpretation "White is Zero". To create a TIFF that can be used with the TIFFG4 DLL in Papyrus Designer/DocEXEC it is required to use PICPhotometric="0" and PICCompression="2" (CCITT fax4). getstartede V7.6 SP3 332/389 Appendix: main updates in V7.0 17.1.3.18 Papyrus Objects (WebControl/WebRepository/IPAS) Papyrus Objects Kernel l Possibility to use PQL in Constraints Adapter l Changed code page handling of Papyrus HTTP Receiver/Sender With V7, the code page determination procedure of HTTP Receiver/Sender has changed. As with V7 UTF-8 is the default code page for string attributes in the Papyrus Objects system and all products interpret them accordingly, the Papyrus HTTP Receiver/Sender performs a code page conversion for data taken over into Papyrus Objects attributes in certain cases. Whether code page conversion to UTF-8 takes place depends on a variety of factors: the type of input data posted, the upload mode, and the data type of the Papyrus Objects attribute to which the data are to be stored. See the documentation "Papyrus Objects Interfaces Receivers and Type Managers Administrator's and Developer's Guide" for further details. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l New feature in XML-Receiver to handover XML files without checking the content When setting the new adapter mode "mode3" together with using xerces as parser (attribute "use xercesflag" checked) the receiver parses the file just to check for syntax errors, and sends the file content to the adapter. The attribute values from "Document tag" and "Container tag" will not be checked. Object Space l Different options for node attribute "For Production" (1=Default) n 0: no Production n 1: Production including project-versioned instances (PM ROLE's allowed) n 2: Production with normal or direct-versioned instances (no PM ROLE allowed) Option 1 allows to login on a production node with a PM role and work with versioned instances. If this is not necessary it is recommended to use mode 2. See the "ISIS Papyrus WebRepository and Papyrus Objects Developer's Guide" for further details. l Improved Defaults for Proxy Management Collection definitions for Papyrus Eye See the improved documentation of Proxy Management Collection in the ISIS Papyrus WebRepository and Papyrus Objects Developer's Guide. IPAS l Possibility to temporary offline cache authorizations This functionality allows clients to cache the authorizations offline on the client machine. During this offline period the client machine will not connect to the IPAS machine in the first 70% of the period reducing network traffic accordingly and then tries to renew the offline cache during the last 30% of the period. The following attributes were introduced in the product part of a KeySet: n Maximum cache period in minutes n Cache period in minutes: Default 0, allowed values 0 - maximum defined in previous attribute n Used cached: counter set by IPAS internally during operation n Used cached by: set by IPAS internally during operation Notes: getstartede V7.6 SP3 333/389 Appendix: main updates in V7.0 This functionality requires all concerned products and IPAS on release level v101203.v702. The Object Space used by IPAS has to be on V7.02 level as well. See chapter "Update Papyrus Objects/Object Space" under "General information" above for further details. In case of IPAS standalone the Object Space is automatically updated when installing IPAS with the ISIS installation routine. This functionality requires updated KeySets including the new attribute 'Maximum cache period in minutes'. If this attribute is not available the KeySet needs to be updated by ISIS. Please contact the ISIS Product Support. In updated KeySets the attribute 'Maximum cache period in minutes' is set to 1.440 minutes (24 hours) by default, the attribute 'Cache period in minutes' is set to 1.440 minutes (24 hours) for permanent product parts and to 0 for concurrent product parts. If all above stated requirements are fulfilled, the temporary offline cache of authorizations is switched on by default and has to be switched off if it shall not be used. See the documentation "ISIS Software Installation and Product Authorization Installation and User's Guide" for further details. 17.1.3.19 Papyrus Designer/FreeForm, Papyrus Server/FreeForm l More compact way of generic table definition (e.g. conditions) l 'unknown' -> 'GENERAL' replacement in Papyrus Objects (compatible with FixForm) 17.1.3.20 Papyrus Designer/FixForm, Papyrus Server/FixForm l New internal rule "combineLine" allows pattern extraction over multiple lines l Improved time measurement display in FixForm Designer (% relative time, s absolute time) l More settings options for image data loading parameters l New tab "test" and "Extract batch" and "Cancel Extraction" button Allows reco batch mode for FixForm in similary way like with FreeForm. l New enabled/disabled icons for doc Classes in FixForm l 'unknown' -> 'GENERAL' replacement in Papyrus Objects (compatible with FreeForm) l Page scope "any even" and "any odd" (extract only even or odd page numbers) 17.2 Main updates in v7.01 including updates since v6.20 DVD v091002 for V7.01 is the first official V7 DVD. It does not include Papyrus Objects except IPAS standalone. Papyrus Objects will be included on next V7 DVD. As the last worldwide shipment was done with CD V6.10, news_e_v620.txt and news_d_v620.txt are available on the DVD under \ISISCD01 in addition to news_e.txt and news_d.txt including the enhancements between V6.10 and V6.20. This DVD includes all products in official release state V7.01. The version part of the directory names was changed from "620" to "700", the related Windows shortcuts and Papyrus profiles were changed accordingly. V7 uses the central directory structure "ISISCOMM" like V6.20. 17.2.1 Release of User-Trained Agent, activity recorder and natural language rules l The ISIS Papyrus Platform V7 provides three new powerful application functions. The User-Trained Agent or UTA, the Activity Recorder or AR and the Natural Language Rule entry or NLR. These powerful new functions can be simply added to any existing application framework without the need to change meta-data definitions in the WebRepository. getstartede V7.6 SP3 334/389 Appendix: main updates in V7.0 l User Trained Agent (UTA) The User-Trained Agent (UTA) provides the business user with the power to train the progression of a workflow. That dramatically reduces the time and effort to analyze and encode workflows and rules. Training is however not well suited to provide sequential entering and manipulating data and threshold rules. In conventional workflow systems these functions have to be provided by programmers who create forms and logic scripts or by business rule systems with complex interface programming. The Papyrus WebRepository enables the business user to use meta-data definitions for interactive activity recording (AR) and business rule entry in natural language (NLR) without complex scripting or programming. The integrated authorization functionality of WebRepository ensures that only authorized users can create or modify activities or business rules and that these rules can only be performed within the authorization scope of the business user. Activities as well as business rules seamlessly interact and cooperate with UTA training. The UTA can be trained to call activities and the business rules set the boundaries for UTA training and recorded activities. l The Activity Recorder (AR) With the AR, business users can automate recurring activities such as adding a new customer record to the context of a business case. This replaces complex forms and logic scripting. The recorded activity can also be modified and optimized by the user. Changes to object meta-data in the repository are automatically considered upon execution of the AR and do not require changes to the defined activity. The user interface language of the activity is also enabled with the translation facility of the WebRepository. Activities can be provided as generic functions in a library or can be assigned to an object type and shown as a tool tip method. All activities follow the same principle of operation, thus the user needn't be trained to work with certain forms. l The Natural Language Rule Entry (NLR) Business users need to quickly and easily add and modify business rules for the processes that they own to either comply with changes in market conditions, business principles or regulation. The Papyrus Query Language (PQL) of the Papyrus Platform is extremely powerful, but not designed to be used by business users. The NLR editor provides the business user with single-edit-line rule entry that enables clear text, syntax free entry of business rules that are structured according to predefinable rule patterns. The NLR editor can be used in a command line environment in any view, within the Activity Recorder to enter conditions or to create rule templates. The NLR editor uses the context of the business case as functional scope and will suggest access to meta-data attributes based on that context. The user can neither access data that he is not authorized for nor can he make a mistake in using attribute names. The rules are entered in a natural language of choice supported by the translation collection and stored in a language independent format. Rules can be entered in one language and edited in another as long as the rule keywords are available in the WebRepository translation collection. The executable format of the NLR is a PQL rule object and is therefore fully compatible with normal PQL scripts. 17.2.2 Release of Papyrus Aapplication and Performance Analyzer (APA) l The Papyrus Application and Performance Analyzer is a monitoring, tracking and analysis tool that collects centralized information from all over the Papyrus Objects Domain. 17.2.3 Release of Papyrus Adapter/Soap l The Papyrus Adapter/SOAP connects Papyrus Objects as SOAP server to third party applications (SOAP Clients) through Web Services. The purpose is twofold: n Receive SOAP messages in Papyrus Objects, and convert them into activities. n Send the output of Papyrus Objects activities to third party applications through Web Services. From the point of view of Papyrus Objects, a SOAP message allows to communicate with the external world. SOAP can be transmitted over a variety of networks, and SOAP messages are typically transmitted over HTTP. Note: If Papyrus Objects has to act as SOAP Client, the SOAP Client Template setup is available in the Object Space delivered on DVD making use of the HTTP Client which is also available in V6.20. But in order to benefit from the enhanced PQL features to parse XML (e.g. XML is intensively used in the SOAP Messaging Framework), ISIS recommends to use V7 for the SOAP Client Node. getstartede V7.6 SP3 335/389 Appendix: main updates in V7.0 17.2.4 Release of Papyrus Scan Receiver l The Papyrus Scan Receiver is fully integrated in the Papyrus Objects Capture Framework. 17.2.5 Release of Papyrus MAPI Receiver/Render l The MAPI Receiver integrated in Papyrus Objects is a direct interface to MS Exchange to send and receive mails via the exchange server. It requires Microsoft Outlook 2002 with Service Pack 3 (SP3) or Outlook 2003. 17.2.6 Papyrus DocEXEC MI version not delivered anymore l Papyrus DocEXEC without Papyrus Postprocessing/Printpool was available in MI and MU mode. With V7 the MI mode is not supported anymore, MU can be used instead. available with V6.20 17.2.7 Release of ISDN fax solution on Windows l Using an ISDN fax card with 4 controllers having 2 channels each allows to send up to 8 faxes in parallel. The ISIS Papyrus FAX / G3 Module was enhanced to create one SFF (structured file format) per document which is then distributed via a queue to one of the channels of the ISDN fax card. The solution requires Papyrus Objects. 17.2.8 Release of HTTP client for Windows and AIX l The HTTP Client is provided under pocxxvvv\htc. See the documentation for further details. 17.2.9 Release of ISIS products for Windows Vista l ISIS products run on Windows Vista except Papyrus AFP Printer Driver because kernel-mode drivers are not supported on Windows Vista. 17.2.10 Netkey solution not delivered anymore l IPAS can be used instead. 17.2.11 New release of the following ISIS products for z/os Unix l ISIS Papyrus Archive Module TIFF, GIF and PDF Converters l ISIS Papyrus PCL Module l ISIS Papyrus PDF/NATIVE PDF/TIFF Module l ISIS Papyrus PageEXEC Module 17.2.12 Product updates 17.2.12.1 General changes l New graphical user interface Papyrus YE The EYE technology provides state-of-the-art GUI design for thick clients (using Papyrus Eye Desktop) as well as for portal solutions. l Improved icons in general getstartede V7.6 SP3 336/389 Appendix: main updates in V7.0 l General change of the log/trace/statistic system The central place for general messages, trace messages and statistic information is the pcsc log in isiscomm. n Description in isiscomm\w3\pcscfgnn.prt The parameter ISIS_PCS_LOGMODE can be used to change the default parameter. See the description in isiscomm\w3\pcscfg31.prt for further details: u S ... Statistic level u T ... Trace level u G ... Trace groups l The environment variable ISIS_USE_PCSLOG defines the log handling n ISIS_USE_PCSLOG=0 ... Default; old behavior for logs n ISIS_USE_PCSLOG=2 ... new; all logs are written to the pcs log When running V7 without Papyrus Objects the old behavior is the Default, running Papyrus Objects the new behavior is the Default defined in the Objects space overruling the environment variable ISIS_USE_PCSLOG. l The messages were reworked and consolidated Before V7 messages were partly included in the products. Now messages are either included in product specific message files or in the message collection in Papyrus Objects. The message identifier consists always of 9 characters "aaaannnnc" (example: "ISLB1001E") with following meaning: - aaaa: module identifier (4 alphanumeric characters) - nnnn: message number - c : message category like W for warning, E for error, I for info For trace messages the message number has following additional meaning "dgnn": - d : trace detail level - g : trace group - nn: message number See the documentation "ISIS Product Messages General User's Guide" for further details. Note: Different behavior between older and newer versions: Messages were changed. If message IDs are checked by customer scripts, these scripts might not work anymore and need to be adapted. l Introduction of message type "G"=GUI GUI messages are info messages, which are only displayed on GUI products but not automatically written into the log to improve performance and reduce the log. This change concerns messages used in Papyrus Server Modules to show the loading of resources and processing of pages. ISIS_PCS_LOGMODE=M,T5,G5 can be set to get these messages in the log as well. Sample for changed message: "AFPR0181I" -> "AFPR5502G Load '@%s@' from file '@%s@'" Note: Different behavior between older and newer versions: Messages were changed e.g. from info message to GUI message, for that reason message IDs were changed as well. If message IDs are checked by customer scripts, these scripts might noth work anymore and need to be adapted. l Support of ICC profiles ICC is the acronym for International Color Consortium. ICC profiles provide color management systems with the information necessary to convert color data between native device color spaces and device independent color spaces. ICM is the acronym for Image Color Matching profile. *.icm is the commonly used file extension for an ICC profile. n In Papyrus Designer a CMR/ICC/ICM profile is assigned to an image either within the IOB command or in the CMR (Color Management Resource) profile dialog. (new frequent command "Color profile") It is required to concatenate the resources. getstartede V7.6 SP3 337/389 Appendix: main updates in V7.0 n Path for ICC files can be defined in DEFAULT.LBP, e.g. CMR= "..\pseg l Support of PDF/A All products producing PDF support PDF/A in V7 according to ISO 19005-1 level A (PDF/A-1a) and B (PDF/A-1b) based on PDF 1.4 defined by the PDF/A Consortium. ISIS validated the PDF/A conformity with Adobe Acrobat Professional 8 (Preflight). Note: CID fonts are not yet supported with PDF/A. l Enhanced sample \docdef_tec\SAMPLE_HYPERLINK.prj The sample shows how to use stickers for hyperlink creation in AFP and PDF. The DEFINEPDFOUTPUT includes the PDF definitions. PdftPDF_A is set to create PDF/A, which requires the definition of ICC profiles via the parameter PdftICCFile. The DVD includes two samples for ICC profiles under demo\color_profile which are used for this sample for demo reason only. l Usage of resource GUIDs in AFP Papyrus DocEXEC offers the possibility to write resource GUIDs in the produced AFP. By that every AFP knows the exact resources used when generating the AFP. It is similar to concatenating the resources into the AFP but without including them. The resource GUIDs are written in NOP records. This functionality requires Papyrus Objects using the Resource Collection for storing the versioned resources, subsequent functionality like AFPIMPORT or Split & Archive allows to keep the resource GUIDs. All products reading the AFP automatically load the resources according to these resource GUIDs. l Support of Single Sign-On (SSO) SPNEGO (Simple and Protected GSSAPI Negotiation) Mechanism, enables a straightforward single sign-on (SSO) environment for WebSphere in Kerberos environments. If SPNEGO is used on Main-Portal, also the WebPortal has to run on the same machine, as the Kerberos-Token only accepts the hostname of the Main-Portal as authorized requester. Single Sign-On requires Papyrus Type Manager LDAP. l Support of IV-Header authentication WebSphere Application Server can run together with IBM Tivoli Access Manager, which supports the IV-Header authentication. l Support of user defined hyphenation The GUI products already capable to use spell check allow to define the hyphenation points when adding terms to the user defined dictionary. Apart from defining the hyphenation it allows to define terms that cannot be hyphened at all. See Papyrus Client description for further details. Notes: - V7 uses a new version of Proximity for spellcheck and hyphenation which requires updated spellcheck and hyphenation files as well. These files will be automatically sent by shipment together with the V7 DVD. Running v620 and V7 in parallel, requires that the spellcheck files are not mixed among versions. The V7 proximity directory is provided without user dictionary. Customers working with a user dictionary (e.g. GRM.USR) can copy it to the V7 proximity directory to use it with V7. When using hyphenation on IBM (z/OS) host V7 requires the dataset used for the hyphentation file to be defined with record format FB (fixed block). The user defined hyphenation is not yet available on IBM host, it is planned for next release. getstartede V7.6 SP3 338/389 Appendix: main updates in V7.0 l Support of addressing up to ~4 GB memory on Win 64 Bit V7 is compiled with LARGEADDRESS flag, which allows to address up to 4 GB memory on Win 64 Bit. available with V6.20 l Support of IOCA FS45 PSEGs with 32 Bit JPEGs Introduced with v090803.v620 (earlier versions supported JPEGs only up to 24 Bit). Note: All products writing or reading AFP support this new feature and need to be on the new release level. l Support of parameter TESTAREA by several Papyrus Server modules Since CD v061123.v620 Papyrus Designer, Papyrus DocEXEC, Papyrus Client and most of the Papyrus Server Modules write the text "TEST" into the output when running with a test authorization. The parameter TESTAREA allows to limit the area for this output. Till now it was supported by DocEXEC only, now it is supported by Papyrus Server PCL, PDF, IJPDS, PDFIN, PS and all products producing PDF as well. l Release Papyrus Type Manager DB for AIX, Linux x86, z/Linux and HP-UX Itanium For the usage of Type Manager DB the modules have to be registered. The related Kernel directories include sample registration jobs (e.g. /pocx3vvv/register_xdo.sh). See the documentation for further details. l Release Papyrus Color to Black and White Conversion This module is available as add-on to Papyrus Server modules and allows to convert an AFP produced with ISIS products including colors to a black and white AFP. l Release Papyrus Image Converter for Solaris l Release Papyrus PostCalc for Microsoft SQL Server l Release Papyrus Server PDFin for AIX and Solaris l Release Papyrus Fast Search Index generator (CD-ROM solution) for Solaris l Removed products for HP-UX on HP-RISC from the ISIS software DVDs See chapter "OPERATING SYSTEMS" for further information. l Improved authorization handling for portal applications l In older versions 2 separate authorizations of Papyrus Client Viewer were taken for the login process and the subsequently started Papyrus Client Browser Plugins. With this DVD this behavior was corrected. Notes: - IPAS, portal (Kernel on portal node) and Papyrus Client Plugins have to be updated to the DVD release level. Products like Papyrus Client Plugins require concurrent authorizations if the authorization is done via a portal solution. getstartede V7.6 SP3 339/389 Appendix: main updates in V7.0 l IOCA FS45 RGB introduced In older versions ISIS products have always created IOCA FS45 images in CMYK colors. Even if RGB colors were specified, they have been converted to CMYK. Now, Papyrus Designer, Papyrus DocEXEC, Papyrus Server PDFin and OverView Image Editor allow to create IOCA FS45 RGB. Find more details below in the particular product descriptions. Notes: - ISIS recommends to test products properly before using the new functionality as it leads to color differences of output results. When using IOCA FS45 RGB, all products reading AFPs including IOCA FS45 RGB (like Papyrus Client, Papyrus AFP Compare, Papyrus Server modules converting AFPs into a different format) need to be on a release level newer than or equal to v080215.v620 which is true for almost all concerned products on CD v080317.v620. Earlier Papyrus Client versions, for example, may not be able to display these colors properly. In case of further questions contact ISIS Product Support, please. l Release Type Manager DB for Solaris and z/OS Unix For the usage of Type Manager DB the modules have to be registered. The related Kernel directories include sample registration jobs (\pocw3vvv\register_xdo.bat, /pocmuvvv/register_xdo.sh). See the documentation for further details. l Updated test certificate files for Digital Signature The files are available on ISIS DVD under \ISISCD02\demo\certificate_pdf. l Introduced test certificate files for Portal/HTTPS The files are available on ISIS DVD under \ISISCD02\demo\certificate_portal. l Successfully tested PAS with DB2/V9 l Improved sample \docdef_tec\SAMPLE_XMLREAD.prj Shows the handling of different encodings and how to convert a XML with not supported encoding to a supported one. Environment variable $CONV controls the different behavior: n $CONV="ASCII" : Uses ASCII XML file XML.txt which works fine. n $CONV="EBCDIC": Uses EBCDIC XML file xmlebc.txt and leads to error. n $CONV="CONV" : Converts the EBCDIC-encoded XML file (xmlebc.txt) to supported UTF-8 encoding XML file at first (in $_BEFOREFIRSTDOC). Processes then the supported format by XMLREAD. l New sample \docdef_tec\SAMPLE_HYPERLINK.prj The sample shows how to use stickers for hyperlink creation in AFP and PDF. l Recommendation for installing a HP patch under HP-UX Itanium to be able to address more than 1 GB memory by one process The HP-UX patch "UNOF_malloc.depot" has to be requested from HP. The installation has to be done like any other HP-UX patch, e.g.: # swinstall -s /tmp/UNOF_HPUX.depot -x autoreboot=true \* The only dependency is PHKL_31500: The HP-UX system just needs to correspond to patch version PHKL_31500, since Sep. 2004 part of HPUX 11.23. There is no requirement to install any intermediate patch. Note: Once the PHKL_31500 patch is superseded by the new official PHKL patch, currently expected in May 2008, the UNOF should be deinstalled before installing the new official PHKL. l Implementation of the Shading part of Highlight colors In the past the Shading part of a Highlight color definition was not interpreted by ISIS products. Since v070924.v620 the shading part is implemented. Using the shading part in color definitions leads now to a different result in viewing (OverView AFP Designer, Papyrus Designer, Papyrus Client) and when converting to other formats (Papyrus Server modules like PCL, PDF etc.). getstartede V7.6 SP3 340/389 Appendix: main updates in V7.0 l The installation docu iinste.pdf and iinstd.pdf is additionally available in the root directory of the first CD. l Enhanced IPAS standalone start job with path to directory "cpts" The command line parameter "/CdpDir=..\..\cpts" for Windows and "/CdpDir=../../cpts" for Unix was added to the start jobs (run_authorization_server.bat or .sh) to assure correct access to the cpts directory if necessary. l ISISINFO tool for z/OS The tool ISISINFO collects important settings on z/OS and writes them into a log. It can be useful for problem analysis. It is available on the ISIS Software DVD under \ISISCD01\tools\unix\isisinfo\zos\ISISINFO. See the installation documentation for further details. l Write text "TEST" on output with test authorization n Papyrus Designer, Papyrus DocEXEC, Papyrus Client and most of the Papyrus Server Modules write the text "TEST" into the output when running with a test authorization. n Parameter TESTMODE="FILL|OUTLINE" (default "OUTLINE") This parameter defines the shape of the string "TEST". u With option "FILL" the string text has solid, black uppercase characters. u With option "OUTLINE" the characters are outlined with a stroke. Originally the text "TEST" was filled, with later versions the default was changed to outlined and the parameter TESTMODE was introduced to allow the definition of the test mode. Due to different version dates of different products the behavior may be different. l New parameter TESTAREA=x,y,w,h x ... horizontal position in mm y ... vertical position in mm w ... width in mm v ... height in mm The parameter TESTAREA defines the position and size of a thought rectangle and allows to restrict the position of the "TEST" string (if there are sensitive areas with e.g. barcodes, company logo etc.). If the rectangle is out of the page size, or the size of the rectangle is smaller than the size needed the definitions may be ignored by the application. A slight overlapping of the text "TEST" at the defined rectangle borders may occur, the rectangle should be defined greater than 50 x 50 mm. Currently this functionality is available with Papyrus Designer and Papyrus DocEXEC. It is planned for future releases of the Papyrus Server modules as well. 17.2.12.2 ISIS Papyrus installation routine V7.0 l Since V7 ISIS ships the products on one DVD All outbound and inbound products for all supported platforms are delivered by default on one DVD. CDs can still be provided on demand. The DVD includes subdirectories ISISCD01, ISISCD02 etc. In case of DVD references to CD n refer to the according subdirectory. l Changes due to the general change that central DLLs in isiscomm include latest version only n Existing product directories are copied to .BAK. n Product directories and isiscomm from DVD are copied over existing directories, i.e. existing files are overwritten, missing files are added. n The installation routine checks the version of products to assure that newer (younger) versions are not overwritten by older versions. The installation automatically checks the version number (if empty the modification date) for files of type .EXE, .DLL and .OCX and the modification date for other files. ISIS products include the build number in the version number of files of type .EXE and .DLL. In case an older version has to be intentionally installed, the related products needs to be uninstalled by the ISIS installation routine and then installed again from e.g. an older DVD. l V7 allows to select between English and German documentation getstartede V7.6 SP3 341/389 Appendix: main updates in V7.0 l The structure of the documentation folders was changed Below the document folder there is a folder "general" and folders per product including the English and/or German documentation. The same structure is used for the shortcuts as well. l The IPAS environment variables may be changed during the installation The installation routine allows to change n ISIS_OMS_DOMAIN n ISIS_OMS_PORT n ISIS_KEY_MODE l The name of the installation routine was changed to setup.exe l Improved IPAS standalone installation With V7 IPAS standalone will be installed to the \ipas subdirectory. There is no distinction between first and update installation. In case of existing V6.20 or V7 IPAS standalone the Object Space including the KeySets will be used and will be automatically upgraded to the latest TRF level (*.trf files provided in \pocw3700). In case of new installation the empty Object Space from DVD will be installed. available with V6.20 l The installation routine starts "set_vista.exe" by default The installation routine "set_w32.exe" is still available on first ISIS CD under \install. It has to be used for installations done on Win NT with SP less than 4. Using "set_vista.exe" a new dialog appears for the shortcut selection: n On Start | Programs (=Default) n On Desktop l Support installation on Windows Vista By default the installation routine "set_w32.exe" is started after inserting the first ISIS CD. For installation on Windows Vista the default installation routine has to be cancelled and "set_vista.exe" has to be started manually (on first ISIS CD under \install). When using "set_vista.exe" a new dialog appears for the shortcut selection: n On Start | Programs (=Default) n On Desktop l New versions of hardlock drivers under \install\keydriver\haspds_windows.dll aligned with hldinst.exe. This version supports the installation of the keydriver on Windows Vista. l System files moved The sytem files moved on first ISIS CD from \install\system into \systemfiles. l Support browser selection for Papyrus Client plugin installation See Papyrus Client below for further details. l Improved uninstall When starting the uninstall it is automatically activated in the installation routine. 17.2.12.3 Papyrus AFP Compare V7.0 l Support comparison of NOP (comment) and TLE (index) AFP commands The result of the comparison of NOPs and TLEs is not shown in the GUI but presented as text in the middle frame. available with V6.20 l Possibility to compare a page group by specifying index name and value By specifying index name and index value the comparison will only be done for the pages matching the index definition. See the documentation for further information. getstartede V7.6 SP3 342/389 Appendix: main updates in V7.0 l Registration via xregsvr required If the Papyrus AFP Compare is installed via the ISIS installation routine (by selecting Papyrus Analysis Toolkit) the registration is done automatically. When copying the panw3620 directory the registration has to be done manually: In directory "install" do the registration with e.g. "xregsvr C:\isis\panw3620\panw3afp.dll". l Ignored areas Possibility to ignore some regions of the Documents to compare. "Options | Settings" includes a new frame to select the color for such Ignored Areas. l The Dialog available from "Comparison | File | Advanced" has been redesigned by using Tabs instead of frames to better group controls by category. l It is now possible to open a new document or comparison dialog in one click without having to manually close the previous document. 17.2.12.4 OverView AFP Designer 7.0 available with V6.20 l New checkbox "Use ftp code page conversion for ASCII file transfer" in Tool| Programs | Send The transfer of source files (OGL, PPFA) uses the ASCII transfer of theftp by default including the codepage conversion done by ftp.Unchecking the new checkbox forces Overview AFP Designer to do the codepage conversion based on the codepages defined in Edit |Preferences | Code page. l Creation of XSD files for Papyrus FixForm The function "Tool | Programs | Generate FixForm" allows to create XSDfiles containing field definitions for Papyrus FixForm. See the documentation for further information. l Implementation FormDef/MEDIANAME The new FormDef parameter"Media" in FormDef | Copy Group properties | Misc. and FormDef |Subgroup Edit dialogs allows to define a "MEDIANAME". It maps aResource Local ID to the name or identifier of a media type. l Changed target resolution in PPFA mode The field "Pels perinch" was implemented in the Form Definition/Copy Group/PageDefinition/Page Format properties in the Setunit Tab to define thetarget resolution. In the PPFA Compiler Options the option "Use targetresolution" was removed. l Define reference to PageSegment/Overlay via Printline Inthe Printline properties in the Tab Overlays/Segments for both -Overlays and Segements - the new field "Variable" allows to define apart of the Printline via "Start:" and "Length:" as name for aPrintline Overlay / Page segment. This allows to dynamically referencePrintline Overlays / Page segements via the line data. l Support of the new Form-size parameters XMSIZE and YMSIZE l Enhanced image options for "Generate PSEG" (File | OGL Compiler) Imageoptions dialogs: New compression types inserted: FS45 JPEG, FS45 TIFF.The variable IOCOMP with values "JPEG" or "TIFF" is set accordingly inthe profile (overview.prf). 17.2.12.5 Papyrus Designer V7.0, Papyrus DocEXEC V7.0 l Support of user defined hyphenation See description under "Papyrus Client V7.0" below. getstartede V7.6 SP3 343/389 Appendix: main updates in V7.0 l Support of Superscript and Subscript in text definition The functions SUPERSCRIPT and SUBSCRIPT make font 2/3 of size (if outline) and move it 50% of ascender/descender up/down. NORMALSCRIPT sets back the text to normal state. l New functions STARTVARIABLETRACE(), STOPVARIABLETRACE( l Additional underline options to use fonts for the line thickness The new options "FONT" and "FONTWORD" derive the line thickness from the largest involved font. l Enhanced TIFFG4 functionality supporting JPEG encoding Due to the enhanced functionality the performance might slow down esp. in case of intensive usage of IOB TIFF. l New SUBSTITUTE TABLE in Papyrus Designer Increased table vertical size, use SpreadSheet table instead of the old list box style. Possibility to sort the table entries in three different ways: n time of the input n source alphabetically n target alphabetically l IDF incompatibility between V6.20 and V7.0 IDFs built with V6.20 cannot be used with V7. In case the COMPILE option is not activated, old IDFs have to be deleted before running V7. This procedure should anyway be done with every version update. l Improved shaded area in shaded box The shaded area starts at the middle of the top/left lines, and ended at the start of the bottom/right lines, now it ends at the middle of the bottom/right line. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this DVD may lead to different results. Please carefully read the description and check if existing projects are concerned. available with V6.20 l Changed 4-state barcode (Intelligent Mail Barcode) Sometimes barcodes could not be read with certain barcode readers. l Correct handling of codepages 1153, 1154, 1155, 1156, 1157, 1158, 1160 on z/OS native (via CDPDLL) l Optimization of objects access and transactions for Papyrus DocEXEC projects accessing many objects in Object Space (e.g. letter tasks) Recommendations for best combination of n OMSCACHE=0 ... unlimited cache for objects being read from Object Space n $_ONLYONCE ... creating a list of object IDs for later access n OMS_PREREAD ... reading all objects in one step (prevent roundtrips) in $_BEFOREFIRSTDOC or $_BEFOREDOC n GETRESOURCES and FILECACHE ... reading all INC/IMP and AFP resources resources in one step for optimized transaction handling and reduced object access are described in a new version of the "ISIS Papyrus DocEXEC Access to Papyrus Objects - Developer's Guide". getstartede V7.6 SP3 344/389 Appendix: main updates in V7.0 l New Papyrus Designer Command GETRESOURCES The command reads all defined includes, text elements and/or AFP resources in one step (avoiding network roundtrip for single element access). The new command is available via the "Special commands" tool collection. The GETRESOURCES dialog lists all used resources of a type and the user can choose from the list which resources to read. See also function OMS_GETRESOURCES below. Notes: - The function was introduced with v090217.v620 and requires a Kernel on the same level. l See note at end of Papyrus Designer section describing how to activate new commands. l New function OMS_GETRESOURCES( Definition n type : INC;IMP;PSG;FON;CDP;CHS;OVL;TIF;JPG n arrayname: List of names (e.g. retrieved by PQL) Sample: ~DUMMY = OMS_GETRESOURCES('INC','INCRES') ; The function reads all defined includes, text elements and/or AFP resources in one step (avoiding network roundtrips for single element access). In case of using it for INC and/or IMP the parameter FILECACHE has to be set as well. See also command GETRESOURCES above. Note: The function was introduced with v090122.v620 and requires a Kernel on the same level. l New DocEXEC profile parameter FILECACHE The parameter enables the caching of INC and IMP. Definition: FILECACHE= l Parameter GridLineThickness possible in MM, PELS and inch Previously only unit PELS was possible. l New XMLREAD parameter Validate XML={"Yes"|"No"} Default="No" If set to "Yes" and a XSD file is defined in the XML, the XML parser checks the attributes of the XML according to the definitions in the XSD file. In case of mismatches error messages like "PPDE7262E XML error 'Unknown element 'XXX'' in line xxx column xxx' " appear. l New parameter NoComment={"Yes"|"No"} Default="No" If set to "Yes" the BRG NOP records are not written into the AFP. getstartede V7.6 SP3 345/389 Appendix: main updates in V7.0 l The TARGETRESOLUTION parameter in CHARTDLL has no more effect if the chart parameter "ImageMode" is set to "Goca Vector" In this case the chart resolution will be the same as the target resolution defined in the APPLICATION-OUTPUT-FORMAT. l Important correction with changed default behavior: Definition of Resource Group and Concatenation taken from ICD/PO The Resource Group and the Concatenation can be defined in the APPLICATION-OUTPUT-FORMAT of a DFA application. In the past these settings were always used, since v081112.v620 the settings are overruled in standalone mode by defining DERESGROUP and DECONCATENATE in an ICD file or on the command line; in Papyrus Objects they are overruled by defining the attributes "Resource Group" (e.g. 'DFOP' for FDF, FON, OVL and PSG) and "Concatenate resources/index" in the AFP object. When running Papyrus DocEXEC in Papyrus Objects, the definition of Resource Group and Concatenation will be taken from the AFP object, the settings in the DFA object are not used anymore in this case. By default the Resource Group is not defined and the Concatenation is activated in Papyrus Objects. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l New ppde.prf parameter AUTOPADATGENERATESPACE={"Yes"|"No"} Default="No" With CD v080317.v620 the usage of option "Pad" in OUTPUT command was corrected: Padding or not padding just relies on the option "Pad" in the OUTPUT command and works independently of the "Generate spaces to AFP". In older versions leading or leading and trailing blanks remained although "Pad" was not checked if "Generate space to AFP" was set. The new parameter AUTOPADATGENERATESPACE allows to switch back to the old behavior by setting it to "Yes". Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l New ppde.prf parameter COLUMNIMPLYNEWLINE={"Yes"|"No"} Default="No" The handling of COLUMN subcommands in the text command was improved in v620. In v610 a COLUMN always causes a linespace, in v620 a linespace is only created if paragraph data exist. The parameter has to be set to "Yes" to cause the v610 behavior. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Possibility to define a central place for XSD (XML schema definition) files XML files may include references to XSD files. The new parameter XSDLIB (in Papyrus Objects attribute "XSD Directory") allows to define a central place for these XSD files. The object space was enhanced to recognize XSD objects in the Resource Collection as new resource type. To search XSD in the Resource Collection XSDLIB has to be defined like "%ResGrp/Group=Group% See also enhanced sample \docdef_tec\SAMPLE_XMLREAD.prj. l Possibility to define NOP record in SELECTOUTPUT command Defining a NOP record in the SELECTOUTPUT command will write the NOP record in the very beginning of the generated AFP document. The NOP records will be written only with the first execution of the SELECTOUTPUT. It is possible to write different NOP records with different SELECTOUTPUT. l Enhance XMLREAD to concatenate tag names See new sample \docdef_tec\SAMPLE_XML_CONC_NAMES.prj. getstartede V7.6 SP3 346/389 Appendix: main updates in V7.0 l New menu point "Options | Tree view unlimited" in Papyrus Designer By Default the tree view in the Document format definition and Formatgroup Definition windows is limited to 80 characters. Setting to unlimited will show the complete content of commands in the tree windows (introducing scrollbar if needed). Additionally the tree view of the TEXT command was changed to show the complete content (before the pure text was displayed). Changing this menu option updates the parameter TreeUnlimited={"Yes"|"No"} Default="No" in the Papyrus Designer profile accordingly. l Changes in default behavior for certain color images When producing color charts and using APPLICATION-OUTPUT/Image mode "IM" or "GOCA" and chart/Imagemode "Image" Papyrus DocEXEC creates IOCA/bicolor instead of IM or GOCA since v080625.v620 (CD v080813.v620 was concerned). With CD v081117.v620 the default behavior was changed back again. See also subsequent entries for bicolor. l Changed line spacing (LSP) for TEXT/TEXTPROMPT with DBCS under certain conditions The different behavior occurs when using TEXT/TEXTPROMPT command with DBCS font, auto line spacing, using DBCS characters only (NO SBCS char. like Sample: TEXT command using DBCS characters only, producing 5 lines, no SBCS font defined, default SBCS font has bigger LSP n Old behavior: First 4 lines use small LSP of DBCS font, between line 4 and 5 LSP of SBCS font is used due to Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l New parameter SUBSTWARNINGFOREMPTYSTRING={"Yes"|"No"} Default="No" for Papyrus DocEXEC profile and ICD If substitution table is used and the string to be substituted is empty, older versions issued the warning PPDE7034W. This warning was removed with v070823.v620. Since v080915.v620 the warning can be activated again by using the new parameter SubstWarningForEmptyString. l New command OMS_PREREAD OMS_PREREAD ( l New DOCFORMAT $_ONLYONCE The DOCFORMAT is executed once per DocEXEC run. l Correction in function DFA( getstartede V7.6 SP3 347/389 Appendix: main updates in V7.0 l Check if NOP records and index definitions are written to the output This check was introduced with v071221.v620. If a NOP record and/or index is defined at a position in the DFA where it cannot be written correctly to the output, the warning PPDE7295W will be issued, e.g.: PPDE7295W;"(CS90LTRS/3878) RN:8863 18 global indexes/nops are deleted because the group was started to write before". Solution: The NOPRECORD and/or index commands have to be moved to correct places (where the output is guaranteed). l New parameter RESOURCECHECK={"Yes"|"No"} Default="No" for Papyrus DocEXEC profile and ICD If the parameter is set to "YES", error messages for non existing resources will be generated with every occurrence of the usage of the resource. Concerned resources: AFP resources, IMP (text elements), DFA, INC, IOB (TIFF, JPEG). l New parameter LONGNAMESUPPORT={"Yes"|"No"} Default="No" for Papyrus l DocEXEC profile and ICD If set to "YES" long filenames can be used (max. 255 characters) in IOBDLL import for IOB and TIFF. Notes: - The parameter was introduced with v080630.v620, all concerned products have to be at least on this release level. This feature is supported by ISIS software only, other software like PSF is not able to read e.g. AFPs created with long filenames. l New function CLEANCACHE( VARCC = CLEANCACHE('ALL') ; ENDDOCUMENT; has to be a string containing one or more elements of the following strings: "ALL", "FON", "CDP", "CHS", "DCI", "FDF", "PDF", "OVL", "PSG", "DOC", "PAG", "TIF". The list must be separated by any not alphanumerical character like "," or " ". Sample: "FON, OVL, PSG". l New parameter TargetResolution in area, bar, pie and radar chart This parameter allows to define the resolution of the chart independent of the target resolution defined in APPLICATION-OUTPUT-FORMAT. In case of true color charts it considerably improves the performance. When defining too small values lines might disappear. If the parameter is set and the chart is a monochrome one, it will be generated as IOCA G4MMR with the bicolor extension introduced with CD v080317.v620. This format assures the image to be rescaleable. Check if your printer supports this format, see also the description of parameter IOCABICOLOR in this chapter below. l Enhanced parameter FillSide for 3D bar charts in true color This parameter defines the percentage of shading for the side part of the bars showing the 3D effect. Sample: -50% creates a lighter shading, +50% creates a darker shading of the side part compared to the top part of the bar. The new additional parameter ",2" added after the first one causes a color change instead of the shading. getstartede V7.6 SP3 348/389 Appendix: main updates in V7.0 l Enhanced parameter Optimizations in line chart The new option "Optimization with no extra line-gap" optimizes the connection lines between ChartInfo and pie segment in sense of forcing straight lines. l Check of character set / codepage inconistency at PDF generation The error message "PPPD9026E: Character definition UNIC0009 is missing from C0COUN90 characterset" or "PPPD9026E;"Character definition 09 is missing from T1GI0361 characterset." (since v080724.v620) indicate that the character referenced with codepoint "UNIC0009" (older message) resp. decimal code "09" (newer message; decimal code, e.g. 64 refers to x"40" which usually refers to the space character frequently defined as default character in AFP fonts) is not defined in the character set. In this sample the error refers to the control character "TAB". In many cases the control characters located in the line data and taken over into AFP text are the reason for this message. Therefore the solution in such cases is to remove the control characters from the input data. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Introduced IOCA FS45 RGB Charts using IOCA FS45 have always been created in CMYK format. Formerly, RGB colors defined in charts were converted to CMYK. The new parameter IOCACMYKONLY switches from IOCA FS45 CMYK to IOCA FS45 RGB image production. n "Yes" (Default) ... produce IOCA FS45 CMYK n "No" ...... produce IOCA FS45 RGB Note: Please read the general description with same title in chapter "General changes" above. l Hyperlinks in AFP and PDF can be added via sticker definitions Entering an URL (e.g.: http://www.isis-papyrus.com) or a link to a mail address (e.g.: mailto:[email protected]) into a sticker will automatically provide hyperlinks when viewing the AFP with Papyrus Client. The new parameter "HYPERTEXTSTICKERS" in the DEFINEPDFOUTPUT defines the colors for hyperlink stickers. See the description under Papyrus Server V7.0 PDF/Native below for further details. See also new sample \docdef_tec\SAMPLE_HYPERLINK.prj. l New OMS Logon functionality for Papyrus DocEXEC standalone This functionality allows Papyrus DocEXEC started standalone to connect to an Object Space. Thereby DocEXEC is able to access resources from a Resource Collection instead of using local file based resources. Following parameters have to be added to the Papyrus DocEXEC profile: n OMSSHMEM={soc: Note: On z/OS native Papyrus DocEXEC mu supports this functionality, the mi version does not. See the documentation "ISIS Papyrus DocEXEC - Installation and User's Guide" for further details. l Improved export functionality of Papyrus Designer Papyrus Designer internally creates a complete AFP and will not stop creation at 100 pages. This assures that all resources are provided in the zip file. The export does not create output files anymore. The AFP generation can be cancelled any time by clicking the STOP icon (main toolbar). getstartede V7.6 SP3 349/389 Appendix: main updates in V7.0 l Postnet barcode will interpret "WidthofElement" "WidthofElement" is interpreted. The application designer is responsible for correct usage and should check if the produced barcode can be read by the barcode reader. Note: Different behavior between older and newer versions: If the parameter "WidthofElement" is set in existing projects the behavior has changed. The new version interprets the parameter, older versions did not. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Possibility to create IOCA instead of GOCA in order to reduce file size If colors others than OCA (base or extended) are used and Papyrus DocEXEC creates bilevel images (e.g. inverted or rotated colored text) the new profile parameter IOCABICOLOR={"Yes"|"No"} Default="No" defines, if GOCA (NO) or IOCA (YES) will be produced. Producing IOCA instead of GOCA will reduce the file size. Note: Before using the new option it should be clarified if it is supported by the printer. l Possibility to create rescaleable GOCA In Papyrus Designer in APPLICATION-OUTPUT-FORMAT it can be defined to create rescaleable (GDD16) or not rescaleable GOCA (Default). Note: Before using the new option it should be clarified if it is supported by the printer. l && l Corrected color handling of 3D pie charts In case of 3D pie charts with ImageMode "Image", ShadeMode "True color" or "Highlight", usage of more than 3 colors and chart values wrong colors were shown in the chart. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Improved handling of object attributes of type "float" n The content of an object attribute of type "float" was interpreted as string with default decimal separator (".") and 5 decimals, e.g. 1.5 was interpreted as "1.50000". This led to wrong output and wrong usage in calculations when changing the decimal separator (LANGUAGESET). Using such float values in expressions to build DFACODE parts worked correctly as DFACODE always requires the decimal separator ".". n Since v080108.v620 such an attribute is interpreted as float. This leads to correct output (using the defined decimal separator) and calculation. When using such float values in expressions to build DFACODE parts, it is required to use the default decimal separator. If a decimal separator different than the default needs to be used, it is recommended to change it before usage for output and change it back to the default afterwards. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. getstartede V7.6 SP3 350/389 Appendix: main updates in V7.0 l Corrected usage of option "Pad" in OUTPUT command Padding or not padding just relies on the option "Pad" in the OUTPUT command. Since CD v080317 it works independently of the "Generate spaces to AFP". In older versions leading or leading and trailing blanks remained although "Pad" was not checked if "Generate space to AFP" was set. See also new ppde.prf parameter AUTOPADATGENERATESPACE above. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Improved handling of HTMLCODE command The interpretation of HTML code using the command HTMLCODE was improved with v080314.v620. The result is similar to the interpretation of Internet Explorer but might lead to differences compared with older versions. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Changed handling of option "Continue" in TEXT command Now, option "Continue" has to be set in ALL TEXT commands where text entries are be continued, in the preceding as well as in the continuing TEXT command. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Changed break handling with repeated outline since v050705.v610 n OUTLINE BEFORE-BREAK/AFTER-BREAK is called only if the OUTLINE to be broken is not the first or the last one. This is necessary to prevent problems when the whole OUTLINE is placed at the next page and a BEFORE-BREAK/AFTER-BREAK is coming at the current page. n Sections are handled similar to OUTLINEs. The section will be active if the OUTLINE containing the section is placed on a Logical Page. This means that the section BEFORE-BREAK/AFTER-BREAK won't be called if the OUTLINE SECTION is broken. Note: Different behavior between older and newer versions: Upgrading from older versions to newer versions may lead to different results. l Improved interpretation of data for rectangle presentation of datamatrix barcodes Note: Different behavior between older and newer versions: Upgrading from older versions to newer versions may lead to different results. l New function EXTRACTALL( n u > 0 the array will be allocated with this count u < 0 all substringt will be extracted l New parameter LineChartBasedOnBar in bar chart The parameter LineChartBasedOnBar controls the behavior of starting in a chart with invisible bars in the background and lines connecting them: n No (Default) ... no lines getstartede V7.6 SP3 351/389 Appendix: main updates in V7.0 n ConnectTo0 ..... start the first line in the chart at 0 n ConnectToPrev .. start the first line in the chart with the last value of the previous chart when connecting charts with SyncroNextChart l String functions were enhanced to include all possible codepage conversions In v070821-v071001.v620 Papyrus DocEXEC was changed to internally use the Unicode codepage for codepage conversions with string functions POS, CHANGE, SUBCHANGE, SUBSTITUTE, EXTRACT. An extensive usage of the concerned string functions might have adverse effects on performance. l Creating additional pages in PRINTFOOTER is not supported The PRINTFOOTER can be used for adding information to previously produced pages but not to produce additional pages. l Changed default settings of barcharts using 0AxisThickness=0 and NOT using YMinMaxValues With v070903.v620 the parameter YMinMaxCalcMethod was introduced: n DrawFrom0: New method (0AxisThickness only influences the line thickness); taken as default. n ApplyMinScaleValue: like previous v620 n ApplyMaxScaleValue: like v600 Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older v620 to the version on this CD will lead to a different result if 0AxisThickness=0 is used and YMinMaxValues is NOT used. l New chart type with invisible bars in the background and line chart in the foreground by combining a barchart and a linechart Defining a barchar with SyncroNextChart=PurgeChart and a subsequent line chart with SyncroNextChart=No draws lines connecting the invisible bars (top center). l Changed 4-state barcode (Intelligent Mail Barcode) Full bar height diminished, proportionally all other bars made shorter as well. l Display content of JPG and TIFF (IOB) in Papyrus Designer Papyrus Designer displays the content of JPG and TIFF images in the "View Document" windows, in older versions a shaded box was shown instead. l 4-state barcode (Intelligent Mail Barcode) With INVOKE DLL(BAROBJ) the 4-state barcode can be selected as "USPS4STATECUSTBARC". The parameter "OutputType" BCOCA is not supported and acts the same like PTX. l IOBDLL supports XAxisRotation The rotation of objects placed via IOB is now supported. This concerns the XAxisRotation as well as the placement of objects with IOBDLL on a rotated logical page, which now leads to a different result than with older versions. In this case the DFA or the object with its rotation has to be adapted accordingly. Note: If the AFP is converted with Papyrus Server module (e.g. PDF,PCL) the concerned Server module has to be aligned (>= v070611.v620) and has to support IOB. Currently this is true for Papyrus PDF. l New function SUMMARY for arrays SUMMARY( Samples: SUMMARY(MYVAR,10,MAXINDEX(MYVAR)-4) SUMMARY({TEST!'AAA'},1,20) l Support of highlight colors for line, area and radarcharts< getstartede V7.6 SP3 352/389 Appendix: main updates in V7.0 l New APPLICATION-OUTPUT-FORMAT parameter "Bounded fonts only" In case of exclusive usage of raster bounded fonts or outline fonts this parameter causes to use only X0- and XZ-Fonts and write them as X0- and XZ-Fonts to the MCF2 structured field. The default is to write them as unbounded fonts, i.e. X1-, X2-, ..., XG- and XZ-Fonts. l New SET parameter: "Only if not the same" PO attribute will only be modified if the new value differs from the current value. For projects checking the PO environment with every reformat this will save time. l New PDECON functions: n DATETOSEC: CONVERT('PDECON','DATETOSEC','2003/06/23 12:23:45') Calculates elapsed time in seconds from 1970/1/2 0:0:0 to 2003/06/23 12:23:45 n SECTODATE: CONVERT('PDECON','SECTODATE','1056363825') Calculates the date using the elapsed time in seconds with the start date 1970/1/2 0:0:0 n TIMESPTOSECSP: CONVERT('PDECON','TIMESPTOSECSP','20 03:06:23') Converts the time period in days with format 'day hh:min:sec' to seconds n SECSPTOTIMESP: CONVERT('PDECON','SECSPTOTIMESP','1739183') Converts the time period in seconds to day(s) in format 'day hh:min:sec' l New parameter "LegendReverse" in charts Allows to reverse the order of the single legend elements in charts (changes direction "up to down" into "down to up"). l Changed encoding for using TIFFs with TIFFG4.DLL Since v070312.v620 the encoding of TIFFs embedded by Papyrus DocEXEC via TIFFG4.DLL (SEGMENT command defining "TIFFG4" as Import DLL) was changed to use RIDIC 4 instead of RIDIC 1 encoding. Note: If TIFFG4 is used to create either PSEGs or AFPs with inline TIFFs via TIFFG4 all other products interpreting these PSEGs/AFPs have to be aligned like Papyrus Client for viewing and Papyrus Server modules for conversion (like PDF/PCL/PostScript). In case of further questions please contact ISIS Product Support. Using the new structure with older versions may lead to error message: "AFPR0150E IOCA: Unsupported bottom to top scanning within file". l New enhanced variable selection in TEXTPROMPT with filter possibility In TEXTPROMPT in the tab "Variable" the new button "Select" opens a new variable selection menu. The variables are listed in a table including name, value, and description. The selection can be done via double click on a row or with button "Insert" for the marked row. It is possible to filter the content of the table. The combo box next to "Select" allows to define the column for the filter, the entry field next to it is used to define the filter. Any string in the filter will restrict the table content to all entries beginning with the string in the defined column, a "*" at the begin of the string will take all entries including the string. l New possibility to predefine filter and use filter in "Load existing text element" in TEXTPROMPT Select "Name" in the combo box next to "Select" and define the filter in the entry next to it. Any string in the filter will restrict the table content to all text elements where the name of the text element starts with the string, a "*" at the begin of the string will take all text elements including the string in the name. A filter can already be predefined in the "Save parameters of a textprompt" dialog (press the button "Parameters" in the "Text prompt definition" dialog) via the new parameter "Text Filter". The filter has to be defined as expression. In case of a predefined filter the user can define an additional filter during the TEXTPROMPT as sub selection of the predefined table content. l New command "SQL Call" in "Special commands" toolbar This command allows to use the new SQLCALL function. See also PDB update below. getstartede V7.6 SP3 353/389 Appendix: main updates in V7.0 l New system variable $ACT_CHANNEL This system variable includes the channel information currently being processed. A channel code is neither an ANSI nor any other character. It is a specific hex value. $ACT_CHANNEL is an integer variable containing the decoded channel code in the following way: -1 ... '+' same record -2 ... ' ' next record -3 ... '0' skip 1 record -4 ... '-' skip 2 record -5 ... AFP record (0x5a) 1..35 ... channel code 254 ... channel string l New option "AxisGridColor" for LINECHART l New option "Print Back X-grid" in parameter "DrawAttributes" for BARCHARTS l New option "TowerMinMax" in parameter "ChartType" for BARCHARTS l Possibility to create an additional job log The definition of JOBLOG= Note that each Papyrus DocEXEC job using JOBLOG appends a new line to the job log file. l Enhanced AFPIMPORT command The new parameter "Resource Management" contains two options: n "Don't use imbedded resources" Default option. DocEXEC will use exclusively resources of the current resource library. n "Use imbedded resources" With this option DocEXEC compares imbedded resources with the resources of the current resource library or already loaded resources. In case of differences with respect to "type", "length" and "control sum", the imbedded resources are used. l Possibility to take over TIFFs via SQLQUERY from a database without the need to temporarily save them file based This can be achieved by using MAKEFILE TEMPTIFF AS 'mem:dummy' FROM TIFFIMG; where TIFFIMG refers to the SQLQUERY. See the documentation for further details. l New command "Description" in "Frequent commands" toolbar This command allows to define a description for a VARIABLE. The description is displayed as tool tip on the top right border of the "Variables" dialog and in TEXTPROMPT when selecting a variable in the "Variable" tab (when moving with cursor keys or mouse to variables in the combo box) to facilitate the selection if many variables are used. l New system variable: $SELECTOUTPUT The system variable $SELECTOUTPUT contains the currently selected output name. l More accurate syntax check of Includes (external DFA) It is checked if ML (MainLevel) commands are finished correctly, e.g. if OUTLINE and PRINTLINE have the "ENDIO;". This is required to handle subsequent ASSIGN statements correctly (ML or SL). Includes created by Papyrus Designer are not affected. If the syntax is not correct the message 'PPDE9153E;"(SAMPLE.DFA/415) An include file not properly ended";;' appears. It shows the concerned DFA with the line number. getstartede V7.6 SP3 354/389 Appendix: main updates in V7.0 l Support definition of highlight colors for viewing The new menu command "Options | Map highlight colors..." allows to map colors for the highlight colors 1 - 4. These definitions are used for the presentation of the highlight colors in the "View document" window. When closing Papyrus Designer the parameters "Highlight1", "Highlight2" etc. are updated accordingly in the concerned profile (pddw3.prf). l Support QR barcode The QR barcode is a 2D barcode used in Japan. l Support of multi page TIFFs The import of multi page TIFFs is possible by use of the IOBDLL. With CREATEOBJECT IOBDLL(TIFF_INFO) the TIFF is analyzed, with CREATEOBJECT IOBDLL(TIFF_IMPORT) it is imported. See the documentation for further details. Note: To be able to use the new commands either use the updated DAD-files (docdef.dad, textedit.dad, view.dad) delivered in the directory \userisis on the ISIS CD or update the toolbars via Windows | Toolbars | Reinit all toolbar. 17.2.12.6 Papyrus Client V7.0 Aligned to new DocEXEC version l Support of user defined hyphenation The user defined hyphenation allows to define hyphenation points using the "%" sign when adding words to the user dictionary (e.g. "sam%ple"). It is possible to define that words are not hyphenated at all (e.g. "%sample"). Following parameters in the Papyrus DocEXEC profile control the behavior of user defined hyphenation n UserDefHyphen: {"Yes"|"No"} Default="No" "No" ... Do not use user dictionary for hyphenation (Default) "Yes" ... Use user dictionary for hyphenation n SPELLLIB ... path for spellcheck files sample: SPELLLIB="..\prox\config" n HYPHENLIB ... path for hyphenation files sample: HYPHENLIB="..\prox\config" n SpellCheckerProf ... path for pclsc.cfg The pclsc.cfg may contain the filenames only, the paths are taken from SPELLLIB and HYPHENLIB. During operation user dictionary files are locally changed. When closing Papyrus Client they are written back by merging the changes to the original which allows parallel changes by several users. l New parameter ShowFirstPage={"Yes"|"No"} Default="No" "YES" ... First page of large AFPs is displayed immediately, while loading the rest of the AFP in the background "NO" ... First page of AFP is displayed after the whole document is loaded into the memory l Change of installation of browser plugins for FireFox and Netscape The only file that should reside in the browser plugins directory is npisisplugins31.dll. The ISIS installation routine deletes additional files from older versions. l Plugins are versioned Papyrus Desktop automatically uses the correct version. This allows to use different plugins in case several nodes run on the same machine (directories plugins and plugins31 in a mixed ISIS_COMMON). For the browser plugins the environment variable ISIS_PLUGIN_VERSION defines which plugin is used. If it is set to "v620", the v620 plugins are used, if it does not exist, or set to something else, the V7 plugins are used. l New button "User dict." in spellcheck tool dialog Pressing this button opens the dialog for adding words to the user dictionary. getstartede V7.6 SP3 355/389 Appendix: main updates in V7.0 l New button "Reload" in Papyrus Client Plugin Works similar like "Recalculate" but also executes $_ONLYONCE. The history is not deleted. l New parameters TextPromptCursor and VarPromptCursor These 2 parameters allow to define different cursor behavior for VARPROMPT and TEXTPROMPT. n TextPromptCursor = {"begin of prompt"|"end of prompt"|"select all"} u default = "begin of prompt" n VarPromptCursor = {"begin of prompt"|"end of prompt"|"select all"} u default = "begin of prompt" u begin of prompt ... position cursor at begin of text u end of prompt ... position cursor at end of text u select all ... selects the text, input overwrites the text l New Parameter ConfirmOnAbort{"Yes"|"No"} Default="No" Suppresses the confirmation dialog, when pressing the abort button. n "No" ... no confirmation dialog n "Yes" ... confirmation dialog: Are you sure to cancel current entries and quit prompting? [Y/N] l Extension of ShowOutputSyntax Variables containing variables or expressions which lead to variables, are now resolved in the OutputSyntax view, e.g.: TEST is a variable. A contains TEST, {A} is shown as: <{'TEST' = A}> A contains TE, B contains ST, {A!B} is shown as <{'TEST' = A> l New Parameter "StickerAuthor" When creating a sticker, the user and creation date is written into the sticker text. In Papyrus Client standalone, the name is taken from the text stored to papyrus.prf parameter "StickerAuthor". In Papyrus Objects the name is taken from the user (logged in). l New parameter "ToolBarGapsSize", Default = -1 Adjusts the gaps between the buttons in the main toolbar n ToolBarGapsSize < 0: the original distances between toolbars buttons are used n ToolBarGapsSize = 0: no distances between toolbars buttons are used n ToolBarGapsSize > 0: the original distances multiplied by ToolBarGapsSize (max 5) between toolbars buttons are used l New parameter ReformatOnOMSEvent={"Yes"|"No"} Default="No" Setting the parameter to "Yes" for any OMS access to an object in the DFA a listener is created which listens to modification events. In case of a modification event of an object, a Reformat is triggered and the modified value is used in the DFA. This setting might have a considerable impact on performance. By default modifications ob objects read in via OMS are registered only after starting a new transaction. l Profiles and ProfileObjects can be stacked hierarchically n /Profile = c:\prf\papyrus1.prf,c:\prf\papyrus2.prf,... n /ProfileObject=ObjID, ObjID, ObjID,... The profiles are evaluated from left to right. l New parameter UpdateOnPrinterMode={"Yes"|"No"} Default="No" n "Yes" ... saving of window printing/PCL3/PCL4/PCL5 parameters based on LastProgramMode n "No" ... printing parameters are not saved l New button OutputSyntaxSwitch in main toolbar The button switches from variable content to variable name display in the document frame. getstartede V7.6 SP3 356/389 Appendix: main updates in V7.0 l New Papyrus profile parameter "EnableFrameResize={0|1}", Default = "1" If the parameter is 0 it is not possible to resize the frames with the mouse. available with V6.20 l New parameter RedirectMessagesToMessageBox=" Note: Different behavior between older and newer versions: With v090122.v620 the MUSTFILL handling was changed to provide better usability for task lists. The error popup on missing MUSTFILL variables can be switched on by setting RedirectMessagesToMessageBox="10008" l New shortcut CTRL+F4 closes Client plugin windows in Papyrus Desktop l New parameter EditMouseMode={0|1} Default=0 0 ... Clicking into the white area of the document stops editing if "Document end" is present (loaded History, or PromptAutoPreview=yes) 1 ... Clicking into the white area of the document keeps TEXTPROMPT in Edit mode l New parameter CommitOnExit={"Yes"|"No"} Default="No" "Yes" ... On closing the plugin, the DFA is executed until the end, so that all changes entered in PROMPTs are commited. "No" ... The closing of the plugin does not commit changes to the currently active PROMPT unless confirmed by F2. l New parameter NewlineOnPagebreak={"Yes"|"No"} Default="No" Compatibility switch for when an edited TEXTPROMPT becomes empty after a pagebreak. Note: Different behavior between older and newer versions: The default behavior was changed. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Display of total pages count in a document Status bar shows current page/total pages. l New parameter CheckMustfillDuringClosing={"Yes"|"No"} Default="No" valid in Desktop plugin (pluginmode=2) only "Yes" ... If there are empty 'mustfill' variables left, the Close command leads to an error message and the cursor is positioned in the not yet filled PROMPT. "No" ... Plugin can be closed without filling all MUSTFILL VARPROMPTs. l Combination with parameter ShowVariablePromptCancelButton in Promptframes=0 mode: These 2 parameters can be combined to show the Cancel button, if all 'mustfill' VARPROMPTs are filled. If there are any unfilled Mustfill VARPROMPTs left in the document, the Cancel button is not displayed. New command line parameter for DesktopViewPlugin method and enhanced DesktopUser4 method for further control of the CheckMustfillDuringClosing functionality. See the documentation for further details. Note: - This function requires Papyrus Desktop >= v090122.v620. l New path handling in "Generate PDF" in combination with CHANGEENV() getstartede V7.6 SP3 357/389 Appendix: main updates in V7.0 l In file based projects, the path set in CHANGEENV() overrules the path selected in the dialog. The PDF is generated with extension PDF at the same location as the AFP. Exception: DEFINEPDFOUTPUT defines a different target which is selected by SELECTOUTPUT. l In Papyrus Objects based environments the path selected in the dialog will overrule the location defined in CHANGEENV() and the PDF will be generated in the user selected path, if the target defined in CHANGEENV() is a binary object. l New parameter VarPromptDataEntryRatio = "{No ¦ 100 ¦ .. ¦ 900}" Default="No" Specifies the proportion of the two parts of a VARPROMPT item, description and value, in Promptframes=0 (promptdialog) mode. l New parameter ShowVariablePromptCancelButton={"Yes"|"No"} Default="No" n "Yes" ... Cancel button is always displayed in prompt dialog n "No" ... when in prompt one of the following errors occurs: u "Date format error" u "Time format error" u "Not a numeric value" u "Numeric value out of range" u "Range definition error" u "Date value out of range" u "Time value out of range" u "Field must have a value" n The Cancel button is not displayed in variable prompting dialog. l New parameter HideTxtPromptControl Provides the possibility to hide buttons and dialogs in the TEXTPROMPT tool dialogs. l New parameter HideVarPromptControl Provides the possibility to hide buttons in the VARPROMPT toolbar. l New parameter ShowSelectedPromptBox ShowSelectedPromptBox means the surrounding box around the text referred to by VARPROMPTs and/or TEXTPROMPTs at selection and during prompting. 0 ... no display SelectedPromptBox 1 ... always display SelectedPromptBox (default) 2 ... display SelectedPromptBox during selection 3 ... display SelectedPromptBox during prompting l New parameters for variable highlighting in TEXTPROMPTs n VariableHighlighting={"Yes"|"No"} Default="No" n VariableColor="R,G,B" Default = "243,173,71" When working with prompt highlighting ("View | Highlight prompts") all variables used in VARPROMPTs are displayed highlighted at all places in the document view. The new parameters allow to additionally highlight the other variables in active TEXTPROMPT. They are only highlighted during editing. l Improved scrolling usability n Scrolling through the document now works over pages. n Scrolling beyond bottom/top of page shows bottom/top of next/previous page. n Scrolling can be done by mouse wheel, cursor Up/Down or Page Up/Down. l HTML paste supports font size (larger/smaller) and font color getstartede V7.6 SP3 358/389 Appendix: main updates in V7.0 l Introduced version check for browser plugin for Internet Explorer If end users download the MSI package via a Papyrus Objects Portal a version check is possible. l Revised handling of MENU.INI n Usage with /MIN command line parameter u Entries not listed in MENU.INI are not displayed in the menu bar and the toolbar. u Combination with HideXToolbarControl is not recommended. u When changing mode (e.g. from "Viewer" to "Document creation") during session, all menu entries/buttons are displayed. n Usage with MenuConfigFile parameter in profile (PAPYRUS.PRF) u Entries not listed in MENU.INI are not displayed in the menu bar, but the corresponding buttons are displayed. u To hide also buttons of functions not listed in MENU.INI, the HideXToolbarControl must be used. u The entries listed in MENU.INI are respected also when changing the mode during the session. l Proxy usage for Papyrus Client browser plugin The new parameter AutomaticProxyConfigurationURL allows to define the proxy usage: AutomaticProxyConfigurationURL={"YES"|"NO"|"URL"} Default="NO" n "NO" ... no proxy usage n "YES" ... use proxy configuration settings from Internet Explorer n "URL" ... define URL pointing to a PAC (Proxy Auto Configuration) file l Improved performance running Papyrus Client plugin in Portal Note that the Kernel running the portal and the plugin have to be on the new release level. l New Print dialog checkbox "Print As Image" Sends every page of the document as image to the printer. In case of overlappings this option may lead to a better result. As the image consumes more memory the print time is longer with this option. In PAPYRUS.PRF this option is saved in parameter PrintAsImage = {"Yes"|"No"} Default="No". l Stickers are resizeable In drag mode or resize mode different mouse pointers are displayed. l New MSI package for installation of Papyrus Client Browser Plugins The MSI package is located on the first ISIS CD under \install\ISISPluginInstaller.msi. It includes the Papyrus Client Browser Plugins with reduced isiscomm library for easy installation on machines running the Plugins only. The MSI can be provided on an ISIS portal page for download by end users. See the documentation for further details. l TEXTPROMPT/automatic REINITIALIZE did not work in previous V6.20 releases If TEXTPROMPTs contain FILTER and/or DFACODE funtions, DocEXEC builds per default (Nocheckfilters=No) up an internal filter list and checks at every prompting for a change that might have been done against this list (for instance if due to a VARIABLE input the text element was changed). In case of a change an automatic REINITIALIZE is performed, so TEXTPROMPT inputs may be overwritten. Setting the PARAMETER NOCHECKFILTERS="YES" will suppress this check and the content of the TEXTPROMPT remains unchanged. For other PROMPTs (no FILTER, no DFACODE) the REINITALIZE can intentionally be provoked using a condition with VALIDATE. l Direct HTTP communication between browser plugin and portal Since v071015.v620 the HTTP communication between Papyrus Client browser plugins and a Papyrus Objects WebPortal is done directly (not via the browser). l Copy & Paste The new Paste context menu can be switched on/off via PAPYRUS.PRF parameter and Textedit toolbar/checkbox. n PASTEPOPUP = {"0"|"1"}, Default="1" n 0 ... standard paste method, setting in PASTELAST used getstartede V7.6 SP3 359/389 Appendix: main updates in V7.0 n 1 ... popup appears If the Paste context menu is switched on and the clipboard parameter "Unformatted" is not checked, a Paste via CTRL+V or context menu will open the Paste context menu with following options: n "Use source styles" ... Keep paragraph styles n "Ignore source styles" n "Text only" n "Unformatted" ... To be used if Copy was done outside of Papyrus Client -> parameter PASTELAST = {"0"|"1"|"2"|"3"|"4"} (0...old behavior, 1...keep source style, 2...ignore source style, 3...text only, 4...unformatted), Default="1" l Omit menu items not defined in MENU.INI instead of graying them out Menu items, which are not listed in MENU.INI are not displayed. In previous versions the menu items were grayed out. l New button "PrintActualDocument" The new button in the viewer toolbar and viewer plugin toolbar prints the document selected based on the viewed actual page. n DDE & DDE plugin command; PrintActualDocument n button name: PrintActualDocument n MENU.INI: FILEPRINTACTUALDOCUMENT l PROMPT name limit increased to 256 Bytes (previously 128 Bytes) l New parameter VarPromptSpellNumber={"Yes"|"No"} Default="No" This new parameter for PAPYRUS.PRF inhibits the spellcheck of words containing numbers. The same parameter was also implemented for Papyrus Designer. l Support of Mozilla FireFox running Papyrus Client Plugins in Browser with a Portal solution The new parameter SaveImmediately={"Yes"|"No"} Default="No" has to be set to "Yes" for Mozilla FireFox. It is recommended to set StickerMerge to "No" in this case as well. l New function "Generate PDF and View" in Papyrus Client plugin n DDE & DDE plugin command: FileGenPDFView (no parameters) n button name: generatePDF&view n MENU.INI: EXTRASGENERATEVIEPDF l Extended word wise Undo/Redo Function The context menu shows a submenu for Undo/Redo for display of all undoable steps (Style changes, text changes, etc.). This Undo/Redo works word wise opposed to character wise like Undo/Redo via CTRL+Z/ CTRL+Y. l Possibility to cancel Prompting via button in text editor toolbar l Messages can be copied from Message window into the clipboard l New DDE command PromptTemporarySave Used for saving prompt content without validation of mustfill variables. No AFP generation is done in that case. l "VarPromptspell={"Auto"|"Manual"} Auto: Spellcheck dialog opens, if something misspelled is typed in the VARPROMPT and VARPROMPT is executed. Misspelled words in the active VARPROMPT are displayed in red. Manual: Misspelled words in the active VARPROMPT are displayed in red color. Right click on a red word brings up the proposal dialog. getstartede V7.6 SP3 360/389 Appendix: main updates in V7.0 l New plugin DocEXEC parameter: "documentendmessage" It allows to define the activity after F2 was pressed on end of document similar to the "generatemessage" parameter. Syntax: documentendmessage=methodname,%objid% Note that PluginMode=2 has to be set in PAPYRUS.PRF. l New Java sample for running Papyrus Client Plugin via Java Delivered on second ISIS CD in \pclDDEPlugin in folder javasample. l isisweb.prf: changed parameter Use_Dirlistfunction With Use_Dirlistfunction="N" Papyrus Client asks the HTTP-server for directory listings only if they are needed. l Take over dialog font and language from the Session If no dialog font/language is defined for the Papyrus Client Desktop plugins (DialogFont=""/Language="") the plugins take over the according settings from the active Session if CVSkins="MSOL" is set. The profiles on the CD were changed accordingly. For backward compatibility use the Papyrus Client settings: n Language="ENG" (e.g.) n DialogFont="" n CVSkins="" l Default font "Tahoma 8 point" in Papyrus Client standalone If no dialog font is defined for Papyrus Client standalone (DialogFont="") it will be automatically changed to "Tahoma 8 point" if CVSkins="MSOL" is set. For backward compatibility use the Papyrus Client settings: n DialogFont="" n CVSkins="" l Improved usability in TEXTPROMPT and/or VARPROMPT n Double click selects the complete word. n Triple click in TEXTPROMPT selects the complete paragraph. n Undo/Redo in TEXTPROMPT via CTRL+Z/CTRL+Y. n Function cut available in context menu and in the main toolbar. l New enhanced variable selection in TEXTPROMPT with filter possibility In TEXTPROMPT in the tab "Variable" the new button "Select" opens a new variable selection menu. The variables are listed in a table including name, value, and description. The selection can be done via double click on a row or with button "Insert" for the marked row. It is possible to filter the content of the table. The combo box next to "Select" allows to define the column for the filter, the entry field next to it is used to define the filter. Any string in the filter will restrict the table content to all entries beginning with the string in the defined column, a "*" at the begin of the string will take all entries including the string. l New possibility to predefine filter and use filter in "Load existing text element" in TEXTPROMPT Select "Name" in the combo box next to "Select" and define the filter in the entry next to it. Any string in the filter will restrict the table content to all text elements where the name of the text element starts with the string, a "*" at the begin of the string will take all text elements including the string in the name. See previous chapter "Papyrus Designer V7.0, Papyrus DocEXEC V7.0" how to predefine a filter. l Spellcheck proposal via context menu in TEXTPROMPT Setting the parameter "AUTO_SPELL_CHECK" in the PAPYRUS.PRF to "Manual" allows to open the spell-check proposal with right mouse click on a misspelled word (red wave underlined). The profiles on the CD were changed accordingly. getstartede V7.6 SP3 361/389 Appendix: main updates in V7.0 l Improved spell-check in VARPROMPT via context menu Right mouse click in a VARPROMPT opens a context menu including entry "Spellcheck". This function starts the spell-check of the VARPROMPT. Leaving the VARPROMPT with F2, TAB or mouse click will trigger the spell-check automatically, if the content of the VARPROMPT has been changed. l Possibility to define ratio in VARPROMPT dialogs between variable names and values The new parameters n AutoFitDataEntryRatio="No" n DataEntryColumnsAutoFit="" allow to define this ratio. See the documentation for further details. l Multiline Edit Tool toolbar Setting the new parameter "EditToolMode" to 1 (Default="0") shows the Edit Tool toolbar in two lines. If the toolbar has not enough place for all icons, it is split into two lines. Without this parameter the user would have to scroll the toolbar for the icons that are not visible. l New checkbox "Dithering" in Print Dialog The checkbox "Dithering" is enabled for PCL5 mode only. If it is set color images are converted to black and white. This may help for grayscale images if the printer does not automatically convert them correctly. l GUI Style similar to MS-Outlook The new parameter CVSkins="MSOL" (PAPYRUS.PRF) changes the appearance of Papyrus Client GUI for the displayed frames in a way similar to MS-Outlook which increases its intuitive usage for users familiar with Microsoft products. l Take over dialog font and language from the Session If no dialog font/language is defined for the Papyrus Client Desktop plugins (DialogFont=""/Language="") the plugins take over the according settings from the active Session. Papyrus Client v070129.v620 always behaves like that and updates the Papyrus Client parameters. For the next release it is planned to do this takeover only if CVSkins="MSOL" is set, i.e. for backward compatibility please use then the Papyrus Client settings: n Language="ENG" (e.g.) n DialogFont="" n CVSkins="" l Default font "Tahoma 8 point" in Papyrus Client standalone If no dialog font is defined for Papyrus Client standalone (DialogFont="") it will be automatically changed to "Tahoma 8 point". Papyrus Client v070129.v620 always behaves as described. For the next release it is planned to do this change only if CVSkins="MSOL" is set, i.e. for backward compatibility please use then the Papyrus Client settings: n DialogFont="" n CVSkins="" l The PAPYRUS profiles n \userisis\PAPYRUS.PRF (Papyrus Client standalone) n \browser\PAPYRUS.PRF (Papyrus Client Plugins in browser) were changed to use the font "Tahoma 8 point" as Default: n DialogFont="8.Tahoma$00$0" n CVSkins="MSOL" l The PAPYRUS profile n \userisis\papyrusc.prf (Papyrus Client plugins in Papyrus Objects) was changed to take over dialog font and language from the active Session: n Language="" n DialogFont="" getstartede V7.6 SP3 362/389 Appendix: main updates in V7.0 n CVSkins="MSOL" l New parameter "HideTToolBarControl" The parameter allows to hide buttons of the Edit Tool toolbar. l Improved FSI Search dialog The search result is presented in a table improving the usability. l Background of document window takes color from the work place In the past a white background with blue dashed line as document border was used, now the background is gray with a shading at right and bottom as border. l Improved usability in prompting applications n The selection or activation of a PROMPT (VARPROMPT or TEXTPROMPT) will change the focus to show the PROMPT in the document window. n In viewing mode a single click in the document or in the history list on a PROMPT selects the PROMPT. n A double click in the document or in the history list on a PROMPT saves/closes the current PROMPT and activates the new PROMPT in edit mode. n In edit mode a single click acts like a double click, i.e. activates the edit mode of the new PROMPT. n In viewing mode it is possible to browse between the single PROMPTs in the history list with the cursor keys. n A single click anywhere in the document but not on a PROMPT changes from edit mode to viewing mode. A double click on a PROMPT always changes to the edit mode. n See documentation "Papyrus Client and Plugin - Installation and User's Guide" chapter "The prompting process" for further details. l User defined accelerator list It is possible to define user specific hot keys for the Papyrus Client plugins. The definition /AA="ctrl+shift+F2,generate&print,Document end" allows that the user can start the "Generate and print" function via CTRL+Shift+F2. See the documentation "ISIS Papyrus Client - DDE Application Interface - Plugin Application Interface" for further details. l Support definition of highlight colors for viewing The new menu command "Extras | Map highlight colors..." allows to map colors for the highlight colors 1 - 4. These definitions are used for the presentation of the highlight colors when viewing AFPs, it is not supported when loading projects with Papyrus Client. When closing Papyrus Client the parameters "Highlight1", "Highlight2" etc. are updated accordingly in the concerned profile (PAPYRUS.PRF). l Double click on VARPROPMT/TEXTPROMPT Every VARPROMPT and/or TEXTPROMPT can be activated by a double click either in the document or in the history list. This is useful when working e.g. with a TEXTPROMPT application without frame mode (PromptFrames="0" in PAPYRUS.PRF) to navigate between TEXTPROMPTs on demand. When working this way the parameter GenerateDuringPrompting should be set to "Yes". l Improved installation of Papyrus Client plugins for browser The installation and registration is done automatically by the installation routine. This means: n The installation routine provides a list of all installed internet browsers to select from. This means that the Papyrus Client plugins can be installed for several browsers at once. n The next two steps are done for every selected browser. u The content of the directory "browser" (including the profiles and the help files) is copied to the browser root directory (e.g. "C:\programs\Internet Explorer"). u The plugins are copied from \isiscomm\w3\plugins to the plugins directory of the browser (e.g. "C:\Program Files\Mozilla Firefox\plugins"). Note: Since CD v071126.v620 this copy is not done anymore for Internet Explorer as Internet Explorer starts the plugins via the activex modules under isiscomm\w3\plugins getstartede V7.6 SP3 363/389 Appendix: main updates in V7.0 l The registration (activex*.dll in the plugins directory) is done automatically. Internet Explorer uses the registration for the plugins path, other browsers like Mozilla, Firefox or Netscape start the plugins automatically from the browsers plugins directory. If more than one browser is selected for installation and Internet Explorer is included, the plugins of the Internet Explorer are registered, otherwise the plugins of the first selected browser in the list are registered. This assures that every browser will start the plugins from its own plugins directory. Note: For a correct uninstallation when using Papyrus Client plugins in more than one browser the installation and uninstallation has to be done in one step for all browsers. l Toolbar Edittool The new toolbar is available since V6.20. It includes frequently used formatting settings for easy use. It can be switched on/off via "View | Edit tool" or the "Edit tool" icon in the main toolbar. The parameter EditTool in the profile (PAPYRUS.PRF) is updated accordingly. l The PAPYRUS profiles n \userisis\PAPYRUS.PRF (Papyrus Client standalone) n \userisis\papyrusc.prf (Papyrus Client plugins in Papyrus Objects) n \browser\PAPYRUS.PRF (Papyrus Client plugins in browser) were changed to use the Edittool toolbar, i.e. n Edittool="Yes" l New parameter Trace_HTTP_OUTPUT_FILE="Path" (Default: "C:\w3chttp.out") Defines the trace file, where all information concerning communication between Papyrus Client and HTTP-Server will be logged. This parameter requires the use of parameter "Trace". l New parameter ArrangeProfiles={"Yes"|"No"} Default="No" By setting this parameter to "Yes" the parameters in PAPYRUS.PRF will be sorted alphabetically. 17.2.12.7 OverView Image Editor v7.0 l Show metadata information embedded in images (XMP) The"Image Information" dialog contains the new button "Meta data". Itopens the "Meta data Info" dialog in a table view, showing meta data ofGIF, JPEG, PNG and TIFF. l Possibility to print the image The new icon "Print the active image" allows to print the image. Note: Update of OIE.DAD required. l Management of new CMR attribute for images in Resource Collection Inthe image properties a pull down menu allows to select from availableCMR resources. See also "Support of ICC profiles" in chapter"General changes" above. l Support of PNG format available with V6.20 l Introduced IOCA FS45 RGB True color images in IOCA FS45 format using RGB colors (e.g. loaded JPGor TIFF) can be saved either in RGB or in CMYK. Note: Please read the general description with same title in chapter"General changes" above. getstartede V7.6 SP3 364/389 Appendix: main updates in V7.0 l Transparency The IOCA FS45 format allows the usage oftransparency. This can be achieved by selecting "Transparency Mask"when saving a PSEG as IOCA FS45. In this case the white areas will besaved transparent. Whenpositioning this image over another one the transparent area will allowto see the underlying image. Before using Transparency all relevantfurther process steps (conversion, printing) have to be checked as theyneed to support Transparency as well. Within ISIS products transparencyis supported by Papyrus Designer, Papyrus DocEXEC, Papyrus PDF, PapyrusImage Converter, OverView Image Editor and Papyrus Client (Clientsupports viewing but not printing). Via the menu command "Defaults |Transparency Color" a color can be defined as transparent color. It mayhelp to check the result and is used for viewing only (no save). l Display OBD (Object Area Descriptor) values in the "Image properties" dialog 17.2.12.8 OverView Font Editor v7.0 l New item "Close" in file menu Allows to process several fonts without exiting Font Editor in PapyrusObjects. 17.2.12.9 Papyrus AFP Printer Driver v7.0 l The checkbox "Generate Images" in the dialog "Images definition" allows to generate images only (without text) l Possibility to setup the environment for Printer Driver Tocreate a quick test area for Papyrus AFP Printer Driver file basedclick the button "Generate Environment" and set a path for the targetdirectory. After installation the target directory will contain allnecessary files (isisres.xsl, pdr_err.log, default.lbp, isisres.xml).The same path has to be used in the Papyrus AFP Printer Driverconfiguration.--- available with V6.20 l Changed naming convention for generating OVL/PSG resources In-between(CD v080813.v620) the naming convention for OVL/PSG was different, withthis CD it was set back again to the old behavior. Samples: n "ABC" -> "O1ABC001" if prefix is requested and name is restricted to 8 characters. n "ABC" -> "ABC00001" if no prefix is requested and name is restricted to 8 characters. n "ABC" -> "O1ABC1" if prefix is requested and the name is not restricted to 8 characters. l New option "Single Page" This new option allows to define the exact name for a single OVL or PSGthat will be produced by Papyrus AFP Printer Driver. Defining the namethis way allows e.g. to produce a new version for an already existing OVL/PSG resource. l Improved handling of new versions in the Resource Collection Due to enhanced OVL and PSEG naming (new parameter "Apply namerestriction to 8 chars") it is possible either to overwrite existingOVL/PSEG or to create new versions. l Possibility to disable the AFP generation With the newparameter "Additional AFP Document" (for OVL and PSEG only), thegeneration of the additional AFP file can be omitted. l Support of IOCA FS11 Papyrus AFP Printer Driver can be configured to generate black and white images using IOCA FS11. getstartede V7.6 SP3 365/389 Appendix: main updates in V7.0 l Create MTIFF MTIFF is a multi page TIFF (one TIFF including several pages). l Create images (GIF, TIFF, JPEG, PNG) out of a document To produce images out of a document the according image format has to be selected. l New option "Crop to content" within option "Generate only IOCA-FS45 per page"Setting the checkbox "Crop to content" affects Pages Segments andOverlays. These resources are resized to the real content of the page. l Possibility to create AFP Outline fonts In the Advanced Setup Dialog under "Options" the checkbox "Generate Outline" has to checked. l New option 'Generate only IOCA-FS45 per page' The option is available in the Configure dialog of the printer driverinstallation program. Following IOCA FS45 document types are available:AFP - The AFP file to be generated contains all images of all pages.OVL - The AFP file to be generated references as many Overlays as thenumber of pages (each OVL will contain the page-image).PSEG - The AFP file to be generated references as many PSEGs as thenumber of pages (each PSEG will contain the page-image). 17.2.12.10 Papyrus FontConverter V7.0 available with V6.20 l Possibility to create Unicode (1200) AFP Outline Fonts Following steps will create a Unicode AFP Outline Font for codepage 1200: n Select the Windows font in the "TypeFace" combo box. n Select "Generate outline" n Select the codepage "Unicode -#1200" in the combo box "Font Cdp:" n Check "CID Unicode" l Possibility to concatenate several Windows fonts in one AFP font Whenusing the Unicode codepage (1200) it is possible to concatenateseveral Windows fonts (e.g. for cascading fonts) into one Unicode AFPOutline Font. The Windows font selection has to be done via the "GetFont File" functionality (icon "..." on top) by selecting the firstfont via double click and define additional fonts via the "Add" buttonin the "Font list" dialog. The other steps are the same like describedin the previous paragraph "Possibility to create Unicode (1200) AFPOutline Fonts". l New check box "Not delete Font file" for Outline fonts If the field is activated the CID and CMP files will not be deleted after the creation of the Outline font. 17.2.12.11 Papyrus PostprocessingPrintpool V7.0 PAS available with V6.20 General l Added to use "UNION" statement with "WebArchive getidmo" function for better performance. PASX3D81, PASX3D8M l New module for connection to DB2 V8.1 on AIX getstartede V7.6 SP3 366/389 Appendix: main updates in V7.0 l PAST3010 New module for connection to ORACLE 10g on HP Itanium. PDB (Stored procedure interface) l PDB (Stored procedure interface) available with V6.20 General l New SQLCALL functionality SQLCALL combines the functionality available via SQLQUERY and SLQWRITE. We recommend to use SQLCALL instead of SQLQUERY and SQLWRITE. See the documentation for further details. PDBMUD61 l New module for connection to DB1 V6.1 and above on zOS/USS 17.2.12.12 PostCalc v7.0 available with V6.20 l Extension to set the tool on hold l New parameter MaxDocsInMemory In case of processing a huge amount of documents the parameter can beused to limit the number of documents held in memory. l Update database files for Royal Mail to Mailsort Database 2009 Release 1 l The PPCInsStackAssignment parameter uses now a semicolon ";" as delimiter l New insert handling for split x-large documents l Inserts can be assigned with a priority (see inserts field definition) l PPCIdxRouteToPrintList may contain a list (with ";" as delimiter) l New PPCIdxRouteToPLDelimiter Parameter to define the delimiter inside the Printlist of the above defined field-values l PPCExtendedDeliveryID allows to have more than 999 deliveries at once l Introduced PostCalc for Microsoft SQL Server l The new mandatory field ISISPC_EINS has been added to the ISIS_IDXAR table. For further details see the script ppcxxyyy_add_index.sql scriptof the concerned operating system [xx] and DB-system [yyy]. 17.2.12.13 Papyrus Host v7.0 available with V6.20 getstartede V7.6 SP3 367/389 Appendix: main updates in V7.0 l Support of JES/SAPI interface (Sysout Application Programming Interface) l Support of REXX interface l New service functions n WLM (Work Load Manager) n ARM (Automatic Restart Manager) n Logger n Support multiple "Own System" l New parameter 'SET FILTER(filter)' This parameter can be used to suppress/display defined messages. l New parameter 'SET ENABLECAF(yes/no)' This parameter defines whether to connect to DB2 via CAF or RRS, in thepast only RRS was supported. l Support MQSeries Message Descriptor V2 l New MQSeries parameter 'OBJECTQMGR' This parameter defines the OBJECTQMGR field in the reply to the specified value. l New MQSeries parameter 'MAXMSG' This parameter specifies the maximum message length. Larger messages will be segmented. 17.2.12.14 Papyrus Server V7.0 PageEXEC available with V6.20 l Possibility to create external index file n ACIFINDEX="Yes" ... generate index file using the NDXNAME parameter "No" ... no generation of index file (default) n NDXNAME="TEST.NDX" ... name and path of index file PCL available with V6.20 l New parameter PCLPrintUser (Default: ISIS) With this parameter the owner of a print job can be added to the lprprotocol. Reasonable for printing with lpr to a print server. PDF/Native l New parameter PdftPDF_A This parameter allows to create PDF/A. See also chapter "General changes" below "Product Updates". l New parameter "PdftICCFile" Allows the usage of ICC profiles for color correction. l External TTF font substitution for DBCS Outline Fonts Theexternal TTF font substitution is now available for DBCS Outline Fontsas well, in V6.20 this was possible for SBCS fonts only. l New parameter PdftSilentPrinting Enables Acrobat Reader to print automatically when opening a PDF (withor without confirmation). available with V6.20 getstartede V7.6 SP3 368/389 Appendix: main updates in V7.0 l New parameter PdftColorTable="{0|1}" Default=1 Specifieswhether to use a color table for images up to 256 colors or not. Usageof a color table for images up to 256 colors is usually theappropriate solution. For big sized JPEG images with high resolutionand a lot of colors the usage of JPEG compression can be the betterchoice for file size reduction. See the docu for further details. l New parameter PDFtUseOrientation This parameter allows tointerpret the Media Orientation (MOT) flag in a FormDef to rotatesingle pages in PDF. For PDF creation the landscape pages are rotated,the user does not need to rotate single pages in Acrobat Reader forreading. Note that the existing parameter PDFtRotation is used forrotation of all pages on a job level. See thedocumentation for further details. l New parameter PDFtPageRotationIndex Allows to rotatesingle pages in 90 degree steps at PDF creation usinga page index for the rotation. Note that the existing parameterPDFtRotation is used for rotation of all pages on a job level. See thedocumentation for further details. l Print of empty back pages (using Duplex printing) In earlyV6.10 versions empty back pages were automatically printed andwere visible in Acrobat Reader. With the introduction of the parameterPDFtPrintEmptyPages in late V6.10 the default behavior changed. Theparameter needs to be set to print empty back pages. For PapyrusDesigner and DocEXEC the parameter was enabled with v081128.v620. Note: Different behavior between older and newer versions:The default behavior was changed. Upgrading from older versions to the version on this CD may lead to different results. Pleasecarefully read the description and check if existing projects areconcerned. l New parameter PdftViewerPreferences Introduced to support predefined Acrobat Reader settings. l Hyperlinks in AFP and PDF can be added via sticker definitions Thenew parameter "HYPERTEXTSTICKERS" defines colors for hyperlinkstickers. Stickers using an according color will automatically producea hyperlink for the sticker text in the PDF. The link is active as soonas the PDF is viewed with Acrobat Reader.Following parameters control the handling of stickers in PDF/Native: n PRINTSTICKERS="R,G,B ; ... ¦ All" (R,G,B colors range 0..255) Takes over the sticker (color) area into PDF. n VIEWSTICKERS="R,G,B ; ... ¦ All" Takes over sticker as comment into PDF. n HYPERTEXTSTICKERS="R,G,B ; ... " n All stickers with the defined colors are converted into hyperlinksin the PDF. Sample: HYPERTEXTSTICKERS="255,255,255; 255,255,0" See also new sample \docdef_tec\SAMPLE_HYPERLINK.prj. l New parameter PDFTOptimizedTree This parameter is for "tuning" the internal structure of a PDFdocument. This can be an advantage using third party software for further postprocessing (e.g. archiving). l New parameter PdftGenComments Allows to convert NOP records into comments in PDF. l Changed parameter for conversion of sticker into PDF comments The new parameter ViewStickers (instead of GenerateStickers) convertssticker into PDF comments. l Support of multilevel bookmark with password getstartede V7.6 SP3 369/389 Appendix: main updates in V7.0 l Support of Unicode Type 0 (CID) fonts Since v070227.v620the PDF converter converts Unicode (1200) AFP Outline fonts to UnicodeType 0 (CID) fonts in PDF instead of rasterizing every character. Forbig PDF files this will considerablyreduce the file size of the resulting PDF. l New parameter PDFtRasterType0="{0 ¦ 1}" (Default: "0") Thisparameter defines if Unicode (1200) AFP Outline fonts are converted toUnicode Type 0 (CID) fonts (Default) or if every characteris rasterized. l Changed syntax of parameter PDFtDigitalSigFiles n Old definition (versions before v070221.v620): PDFtDigitalSigFiles=" l Digital Signature supports PEM encoded certificate Sincev070315.v620 the pdf converter supports the use of a "Privacy EnhancedMail" (PEM) encoded certificate. The PEM stores data in aBase64-encoded DER format (Distinguished Encoding Rules), surrounded byASCII headers. Older versions need the certification file in DERformat. The file pdfrsa.cer on the ISIS CD 1 under demo\certificate_pdfwas updated to PEM format. l The parameter PDFtResViaDocs is not supported anymore l Test certificates for Digital Signature On the ISIS DVD 1under demo\certificate_pdf the certification file pdfrsa.cer and thekey file pdfrsa.key are provided for test reason with following data:Issuer: C=AT, O=Test Company, CN=Test UserValidityNot Before: Nov 24 16:26:54 2006 GMTNot After : Dec 31 16:26:54 2015 GMTSubject: C=AT, O=Test Company, CN=Test User PS available with V6.20 l New parameter PSCRNrOfCopies Specifies the number of output copies, which will be produced. l New parameter PSCRBinSetup="$ l New parameter PSCRPrintUser (Default: ISIS) With this parameter the owner of a print job can be added to the lprprotocol. Reasonable for printing with lpr to a print server. PDFin l File size reduction due to support of CID font CID-keyed fonts are now converted to AFP Outline fonts which considerably reduces the file size of the resulting AFP. Note: Requires aligned Papyrus Client for viewing. getstartede V7.6 SP3 370/389 Appendix: main updates in V7.0 l More flexible handling of definition in font ini table (PinInitFile) Clear distinction between TTF and Type1 fonts. This might requireadaptation of existing ini tables. l New parameter for image optimization n PINVectorGraphics ... force vector graphics See the documentation for further details. l Obsolete parameters with V7 n PinFineFill n PinFineStroke Not necessary anymore as automatically done by default. l Special features for font generation n PINForceCharImage ... rasterization of fonts n PINUseRasterRelative ... generate relative metric raster fonts l General performance improvements and file size reduction available with V6.20 l New parameter for image optimization n PINSymBWThreshold1,2,3,4,5 ... dither gray scale to black and white See the documentation for further details. l Enhanced index functionality: multiple group/page indexes from PDF bookmarkSee the documentation for further details. l New parameter PINUseAnnotAsNOP={"Yes"|"No"} Default="No" This parameter allows to convert "annotations" (synonymously used forcomments) into AFP NOPs (NOP is the acronym for the "No Operation"triplet in an AFP). See the documentation for further details. l Possibility to create AFP group index out of PDF bookmarks The new parameters PINBMToPageIndex, PINBMToGroupIndex and PINAFPIndexName can be used to define the usage of PDF bookmarks asbase for AFP indices (TLE). IJPDS available with V6.20 l New parameter IJPOptimizeGoca Setting this parameterwill rasterize vector graphics. This results in bigger file size.Default is the old behavior without rasterizingwhich reduces the file size but might lead to wrong color on top. l New parameter IJPEnableGocaCache={0|1} Improves performance and reduces file size in case GOCA commands areintensively used (repetitions). l Enhanced parameter IJPImagesToFonts n IJPImagesToFonts="3" ... Used for better vector graphics handling Papyrus WebArchive l Reduced memory consumption for large color TIFF getstartede V7.6 SP3 371/389 Appendix: main updates in V7.0 l New parameter ArcTimeOut Default=300 sec in Papyrus Objects Allows to change the Default setting which was hardcoded 300 sec in thepast. l New options for parameter TiffCompress n TiffCompress="4" = PACKBITS n TiffCompress="5" = LZW n TiffCompress="6" = JPEG available with V6.20 l Improved performance for Splitting and Conversion using ResourceManagement="Append"Resources are loaded only once, not for each document. l Support of isiscontrol on Unix (aix and Sun) isiscontrol allows to define pipes for parallel processing in CGI. Tillnow available only for Windows, now for Unix as well. See the documentation for further details. l New parameters [USETEMPFILE] and [TIMEOUT] for loading large PDF files in CGIThe parameters have to be set in db.ini. See the documentation for further details. l Create BNG/ENG/TLE records when splitting the document and converting itto PDFSince v071003.v620 the Archive Module always stores index informationin the temporary AFP when splitting the document and converting it toPDF. This feature was introduced in order to provide the possibility touse index values for PDF creation (e.g. for the user password definedby parameter PDFtUserPassw). As the PDF conversion step createsbookmarks from TLE records by default (PDFtIndex="*"), the resultingPDF includes bookmarks. With the new version the default behavior waschanged back. If BNG/ENG/TLE records are to be created intentionally,the new parameterAddTLEInDoc has to be set to "YES". l Improved performance for Splitting and Conversion when using ResourceManagement="Append"Resources are loaded only once, not for each document. l Implementation of color TIFF The new parameter TiffCreateColorImage allows to define the creationof color TIFFs. Default is "No". E-Mail l New parameter DocumentGroupIndex to allow multiple attachments Eachconsecutive document which should be sent with the same email holds thesame index value. The first document in the group definesthe e-mail (TO, CC, etc. addresses). If the DocumentGroup index valueremains unchanged for the next document, the next document will be alsoattached to the same e-mail. To, CC, BCC... are only used from thefirst document of the group. Each document will be additionallyconverted to PDF, etc. as defined for the whole job. l Allow reference to a group index for parameter EMAILFromIndex l New Parameter EmailDeliveryReceipt, Default=0 If the Valueis set to 1 or "Yes", the email sender gets a Delivery StatusNotification like "Successful Mail Delivery Report" in case of success,and "Undelivered Mail Returned to Sender" in case of no success. l New parameter EmailContentId for embedded mail Sample: cid:[email protected]. User should onlywrite e.g. "isis-papyrus.com" in this parameter to send email with embedded images. l Possibility to send background images with HTML E-Mail In HTML use the keyword "background=", sample: background="myfile.gif". getstartede V7.6 SP3 372/389 Appendix: main updates in V7.0 Papyrus Image Converter l Support of PNG format l Input and Output file could be data/resource instances Store converted images in Binary attribute of existing Resource image object. l Embed meta data information The Papyrus Image Converterembeds meta data information like creator tool and creation date in theconverted image, supported for GIF, JPEG,PNG and TIFF. available with V6.20 l New parameter "PicTransparency" The parameter defines the color mode (1 ... RGB, 2 ... CMYK) and thecolor (R,G,B or C,M,Y,K) that should be converted to transparency, e.g. n PICTransparency="1,255,255,255,0" ... RGB color white n PICTransparency="2,0,0,0,0" ... CMYK color white. n See also the chapter "OverView Image Editor V7.0" above. Notes: - It's required to specify all parameters required to save images as IOCA FS45 images: n Output Image Type {1=AFP} n Image Mode {5=IOCA FS45} n Compression {0=none|3=TIFF|4=JPEG} The new parameter PICTransparency is required in every run (ICD file), the existing ICD files have to be adapted accordingly. 17.2.12.15 Papyrus Objects V7.0 (WebControl/WebRepository/IPAS) Papyrus Desktop available with V6.20 l Node Explorer (DesktopViewNode) For performance reasons, it is recommended to manage the nodes of a very large domain in this view instead of expanding the Node Collection. The attributes on the "Detail" tab are filter settings to find certain nodes (e.g. all nodes not in ready state, only those currently online, last modification of offline nodes, etc.). l Changed default behavior when opening new views from the toolbar Calling a new view from the toolbar opens the view in the same or next dynamic container of the view window, older versions opened a separate window. Introduced with v081009.v620. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l Activating default project forces re-login The currently selected default Project is stored in attribute "Default project" of the user's Session object. When activating it, Session attribute "Default project" is cleared, the desktop performs an automatic re-login, and the Project disappears in the right frame of dialog "Change Active Role and/or Project" (menu "File | Change Active Role and Project"), because it is no longer in deployment state "Development". getstartede V7.6 SP3 373/389 Appendix: main updates in V7.0 l Grouping of attributes Since v070723.v620 attributes can be grouped. See the documentation for further details. l New search mask For all standard user accounts delivered on the ISIS Software CD a new enhanced search mask appears when pressing CTRL+S or selecting menu item "Tools / Search Ctrl+S". For new user accounts it is required to set up a User Search Folder and its search functions. l Miniature preview for minimized windows Moving the mouse over an icon for a minimized window (lower right corner), a miniature preview is displayed. l Quick Launch buttons In addition to the buttons in the toolbar, quick launch buttons on the right-hand side of the object can be used to start methods. For this option "Quick Launch" has to be selected in the method definition. l Two View Toolbar (TwoViewToolbarLayoutElement) This frame type is used for a user defined toolbar, which monitors the selected objects in two frames, to display matching methods as icon buttons (e.g. add button as arrow). l Second toolbar for root object In addition to the toolbar displaying methods of the currently selected object, method parameters SecondToolbar & MainToolbar allow to display a toolbar for the root object at the bottom of the window. l Option "Show Parents count" for tree view l Possibility to define the Dialog Font for the active Session With "Options | Select dialog font ..." the dialog font can be defined. To be able to change this option the Object Space has to be on the latest level, see chapter "Update Papyrus Objects/Object Space" under "Important information for all CDs". l Jump to object by typing in the first character(s) of its name By typing in the first character(s) of an object's visible name, it is automatically selected in the object tree or table view. l Icon for method buttons Method property "Icon" allows to specify an image (Icon object below "Domain Controller/Storage/Icon Collection") for the related button in the toolbar. l Possibility to define the Dialog Font for the active Session With "Options | Select dialog font ..." the dialog font can be defined. The font "Tahoma 8 point" is used as default. l Object/Policy grid - multiple selection Instead of defining the Policy for each object separately by double clicking its crosspoint, it is now possible to define/undefine it for all objects at once by double clicking the Policy in the column header. l Method "Check this object" Now it is possible to correct individual objects instead of applying service function "Check objects" to the whole Object Space of a node. Details to"Check objects" and why it should only be used in cases of emergency can be found in chapter "CheckObjects" in "Monitoring, Analyzing, Troubleshooting and Tuning Guide (pmatage)". l Method "Stop Check Objects" Allows to stop service function "Check objects" by selecting the Node and clicking button "Stop Check Objects". getstartede V7.6 SP3 374/389 Appendix: main updates in V7.0 l Method parameter "MoveToolbar" Used to switch on/off move buttons in all tree and table views of a window. l Show/hide tab register By clicking the button on the right-hand side of the tab register and selecting option "Close" at the bottom, the tab register is hidden. To bring it up again, right click the border and select "Open" or click the expand button of the register tab frame. l Show/hide methods in tab register By clicking the button on the right-hand side of the tab register, the methods to be displayed/hidden in the tab register can be selected/deselected. l Tag l Possibility to call the Layout Editor for the view window l Drag and Drop - target nodes grouped in context menu Nodes other than the Domain Controller and the one currently connected to (= the own node) are displayed in category "Other ..." of the context menu. l New method parameter "RefreshAlways" By specifying RefreshAlways="Yes" the PQLTable frame is automatically updated when a modification event is coming for objects outside this table, i.e. in a neighbor frame of this window (view layout). l Multiline functionality in PQL and table view l New method property "Icon" l New Scheduler attribute "Autostart" With option "Yes" the Scheduler will always be started at kernel start-up regardless of its previous state unless it was explicitly deactivated during start-up with kernel parameter /Scheduler=no. With option "no" the Scheduler is only started if it was started before. l New Transfer class attribute "Icon references" Controls the behavior for the import of versioned Icons (like parent or child references). l Program objects for the Unix HP Itanium 32bit platform The Library folder "HP Itanium" including Program objects has been added below "Library/System Management/Program Objects" to enable Tools for this platform. l Language support for HTML and ASCII editor l Integration of PQLEditor For editing of PQL scripts within attributes the new PQL Editor was introduced. l New shortcut CTRL+L and menu item for auto layout All open windows are maximized on the desktop without overlapping each other. Papyrus Objects Kernel getstartede V7.6 SP3 375/389 Appendix: main updates in V7.0 l $node contains now the new (owner) node after doing a relocate available with V6.20 l Generate unique Object IDs At startup the kernel builds now a unique object id with certain calculation based on the UTC time to overcome problems of reuse of the same object ids in case of restoring an object space. l Corrected behavior when using IsModified for system attributes in PQL The old wrong behavior caused the execution of rules if in the WHEN part a system attribute is checked with the IsModified PQL function and could result in unpredictable executions of the rule. l Extended connection life time to 12 hours In earlier versions the connection life time was 90 minutes. If the connection life time is reached on a node the connection to other nodes is closed and a new connection is established. When working with a network where connections between nodes are only allowed in one direction (e.g. when using NAT) and the connection is kept alive by using the KeepAlive functionality doing e.g. a ping every 9 minutes (before the connection timeout of 10 minutes is reached), the closing of the connection might cause troubles if the reconnection is started from a node who has no access to the other node. l Improved behavior of method "NewVersion" Until now the new version is created from the latest version in the version chain. Since v090217.v620 the new version is created from the latest version accessible via PM role. This is important for parallel development when the same objects can be changed in parallel by different users. l ISIS Change Management If parallel development is allowed in a project, the user now gets a message if he creates a new version of an object and a new version of this objects is already in development state. l Correct versioning handling for versioned instances with child objects Move/add/delete references from a parent object which is a versioned instance was possible in deployment state "active", since v081211.v620 it must be done by creating a new version. l Convert new strings in object attributes to UTF-8 Since v081218.v620 new strings are automatically converted to UTF-8. l Improved Batch for incremental recovery on Windows If the incremental recovery is used, the batch should be updated. l Optimization of the Proxy Management Collection The implementation of the Proxy Management Collection was optimized. It is recommended to upgrade to this CD when using PMC. l Support for MQSecurityExit Support of authentication via "MS0R WebSphere MQ Channel Security Exit" l New PQL functions "FieldCount", "FieldIndex", and "FieldName" Return the number of fields, index, and name of a PQL set. l Syntax of PQL function "Format" changed Now the parameters before and after the colon in the format string have been swapped, i.e. first the "what" and then the "how" is specified. getstartede V7.6 SP3 376/389 Appendix: main updates in V7.0 l Usage of Type Manager DB requires Object Space Update The Type Manager DB included in Papyrus WebRepository/WebControl requires changes in the Object Space. See chapter "Update Papyrus Objects/Object Space" under "Important information for all CDs" above for general information about the Object Space update. l Optimized event collection handling On large scale installations (many nodes) this optimization improves work load on nodes dealing with many events (Domain Controller, worker nodes). l Starting a Unix Kernel (pocxxknl, xx e.g. x3, s3) with "nohup" requires that the start script includes pocxxknl without path. "pocx3knl ..." works fine, "../pocx3620/pocx3knl ..." does not work. To assure that pocxxknl is not found via the PATH environment variable the start script should include "export PATH=.:$PATH". With versions greater than v071009.v620 this limitation will be obsolete. l Security features for user accounts and roles The following attributes are used by the system to lock user accounts and roles in case the specified limits are reached: n User object, User Collection, Role object, and Role Collection u Inactivity Period [days] User account / role expires after it has not been used for the specified number of days. n User object, User Collection u Max. Failed Logon Attempts Locks user account after the specified number of consecutive failed logon attempts. n User object u Password Expiration Period [days] Defines after how many days a user must change his password. l Minimum Password Length Common Rule "Password Check" ensures that users do not define passwords with less characters than specified in the "User Collection" (general setting for all users) or the respective User object. l Online Backup (/Reorg=Fatal) includes binary attributes l Incremental Recovery possible l Common Rules Global Common Rules are used to perform actions every time the objects monitored by them are modified. Local Common Rules are similar to PQL Rules, but they can be nested. l Changed handling of parameter default value of the attribute All attributes containing default values of the class are displayed with the string "Default" in parenthesis. So attributes of classes are always marked with this string, as it is only possible to define a default value in the class definition. Attributes of instances are never marked with this string, as the default value of the class is written to the attribute when the instance is generated and then it is no longer a default value. In templates both is possible, as the default value from the class can be overwritten with a new value. l Language translation for ATTRIBUTE values New attribute property "TranslateContent" allows to define that the attribute value should be translated in the user interface, but stored in the original language. This is often useful for combo boxes when the user has to select one option from a list in his user interface language. l Move Reference Before/After in Attribute Tree views Now it is possible to move objects not only in object trees but in attribute trees as well. getstartede V7.6 SP3 377/389 Appendix: main updates in V7.0 l New PQL functions "Union", "Intersection", "Diff", and "FormatMessage" PQL function "Union" concatenates PQL sets, "Intersection" generates a PQL set with the items that both PQL sets have in common, and "Diff" is the reverse function of "Intersection". PQL function "FormatMessage" is used to test a Message object and to store its message text in an attribute. l Open PQL script of method parameter in PQL Editor Select the method parameter used for the PQL script and click the PQL button to write/modify a PQL script for it in the PQL Editor. l Open PQL script of combo box attribute in PQL Editor Select the substitution field and click the PQL button to write/modify a PQL script for it in the PQL Editor. l New option $onlyvisible($ov) This option prevents adding not visible attributes (based on VisibleForEdit, ViewPrivileges and ViewConstraints) to the set when using ".*". l Automatic creation of missing Local Storage on startup of kernel l Attribute "Remove proxies of relocated objects" on the NODE object that enables the manual and automatic deletion of proxies of relocated objects. l Auto import of transfer files If transfer files are moved to the kernel directory, they are imported (at startup or later within 10 minutes) and a project is created. The files are renamed after the import to *.trf_imported_ l Enhanced node installation via install.dat The name of a node to be installed can be predefined. It is possible to takeover the machine name as node name. See the document "Installation of Papyrus Objects for Papyrus WebRepository & WebControl Installation and Administrator's Guide" for further details. l Define kernel command line parameters usable via environment variables If a command line parameter should be set in the environment, its name has to be prefixed with "ISIS_". Sample: The "/BackupDir" command line parameter is recognized in the environment if it is called "ISIS_BackupDir". Agent l Agent writes OID of the agent in $User of modified object With V7 the OID of the Agent is used instead of the OID of the Node where the Agent is running to update $User after modifications. available with V6.20 l The behavior of $User was corrected if an Agent modifies an object Previously $User contained the OID of the User who modified the object last regardless if the object was further modified by an Agent. Now $User contains also the OID of the Node were the Agent was running in case it modified the object last. Corrections of existing applications may be needed: If the User-ID of a certain process who initiated it should be logged, query $User on process start or when a certain state is entered (do activity calling a PQL) and write this information into an attribute of the associated object (e.g. Task) to save it persistently. Change the content of this attribute in the same way when another User performs activities with this object. Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. Adapter getstartede V7.6 SP3 378/389 Appendix: main updates in V7.0 available with V6.20 l New parameter Process0ByteFiles with Default=No The parameter was introduced with v090615.v620 for Windows and activated with v090731.v620 for Unix as well. To prevent the processing of empty trigger files with v070907.v620 the dispatcher was changed to not process empty files. The file size has to be at least 16 bytes, smaller files are not processed. The change in v070907.v620 concerned Windows only, now all platforms are concerned. The new parameter can be set to get the old behavior (process empty files). Note: Different behavior between older and newer versions: The default behavior was improved. Upgrading from older versions to the version on this CD may lead to different results. Please carefully read the description and check if existing projects are concerned. l New attribute "Ignore Tags" in XML-Receiver This attribute provides the possibility to bypass tags. The concerned tags can be entered as a comma separated list in the attribute "Ignore Tags", then these tags and nested tags will be ignored at parsing. This reduces the memory consumption when processing large XML files. l Type Manager LDAP supports SSL Since CD v080813 LDAP supports SSL. For secure LDAP use, specify the LDAPS protocol in attribute "Provider URL". l New attribute "XSD Directory" for the XML-Receiver The attribute allows to define a central location for XSD files referenced in XML files. See also XSD files in chapter "Papyrus Designer V6.20, Papyrus DocEXEC V6.20" above. l Registering the XOM Receiver/Sender in the SAP product database See the documentation "Papyrus Objects Interfaces / Receivers and Type Managers / Administrator's and Developer's Guide" for further details. l Empty trigger files are not processed To prevent the processing of trigger files that are not yet ready with v070907.v620, the dispatcher was changed to not process empty files. The file size has to be greater than 16 bytes, smaller files are not processed. l New attribute 'Polling Interval (Milli Sec)' in XML- and MQ-Receiver This new attribute is of type INT with default '0' and allows to define a polling interval for the 2 receivers. On CPU critical platforms it can be used to reduce the CPU usage. l Due to an internal format change MQSender/MQReceiver have to be updated together. l New "File Mapping via PQL" functionality l XML: The receiver's error messages contain visible names instead of internal names l Changed rule processing n If a rule is a template it will be instantiated but not processed. n If a rule is an instance it will be processed but will not be included (linked) in the instance generated by the Adapter. Portal available with V6.20 l getstartede V7.6 SP3 379/389 Appendix: main updates in V7.0 l l New PPL tag l Arbitrary HTTP header entries can be set with the l New parameter for img.oms requests to clip an image The parameters zoneleft, zonetop, zoneright and zonebottom can be used for image requests to clip the image. l Changed @calc/@nocalc functionality PO_OUT without using PQL returns the resolved value of %var% variables of an attribute, if the option "Contains Expression" is set in the Class (same behavior like the Desktop). n Using the function @nocalc forces PPL to NOT resolve the value of %var% variables of an attribute, even if the option "Contains Expression" is set. n Sample: l Optional timeout for l System attributes $$system.usersonline and $$system.activesessions $$system.usersonline returns the numbers of logged in users and $$system.activesessions returns the number of sessions. l New HTTPServerSettings attributes to limit number of sessions The attributes "Maximum Sessions of Server" and "Maximum Sessions per Client" have been added. l New PPL tag l @calc To resolve expressions in attributes (e.g. %ObjID%) add @calc at the end of the navigation path like in the following sample: Note: The reverse function @nocalc is no longer available. Object Space n New function to compare two files (e.g. external resources) After instantiating the new class "DifferenceMerger" it can immediately be used by specifying the external files. available with V6.20 n Improved (accelerated) common rule "Prevent multiple Resources" This Rule is triggered by the class Resource Collection Resource on every change of an existing or creation of a new resource. The PQL within this Rule is checking if another instance exists, which has similar names and attributes etc. to prevent that one resource exists twice within the Resource Collection. In case of many resources this check might be time-consuming, for that reason the PQL was improved for performance. getstartede V7.6 SP3 380/389 Appendix: main updates in V7.0 n Activate time triggered free unused proxies by Default Check attribute "Time triggered free unused proxies" and set defaulttime 12:00 in attribute "Free unused proxies time [hh:mm:ss]". n New function "Features Supported" The new node attribute "Supported Features" describes the features supported by this node and is automatically filled by the kernel. The feature "1: Compressed Node List" introduces the exchange of node information in a compressed format during the installation of new nodes. This helps to reduce network traffic in large scale installations. When updating an existing Object Space with the TRFs from this CD, the feature will be available after activation of the Base Framework and restart of the Domain Controller. This update introduces the "Network Settings" under the "Settings Collection" as well. n Change parent reference of "Local Storage" to avoid deletion Due to the virtual parent references introduced with previous CD the "Local Storage" would be deleted after running a check objects. TEMPLATES in Library Folder "Node Templates": Set on Templates "Local Storage" parent reference "Node" and uncheck "Virtual Reference". n Virtual parent references for Repository, Library and Storage The Object Space on this CD includes the objects Repository, Library and Storage with virtual parent reference definition. Upgrading existing Object Spaces will change the parent reference definition from bidirectional to unidirectional (virtual). This reduces the data exchange at node installation and the search path for methods during drag and drop activities. Note: In existing installations "check this object" needs to be done on every node when it is online to reduce the ParentCount of Storage, Library and Repository, it is not mandatory. This will replace the old bidirectional object references by the new unidirectional (virtual) ones. The PQL "'Check This Object' on all nodes" is provided on CD to support this procedure (see next entry below). n New PQL templates in Library/System Management/PQL Templates u 'Check This Object' on all nodes This PQL is included in the Base Framework. It runs the method "check this object" on all client nodes that are online and not already processed. Using a "scheduled action" allows to access the script at a certain point of time, as the method "check this object" is just effective if a desired node is online. Checked nodes are written to the attribute "Object List". To run the PQL configure the "scheduled action" attributes and enable them. The PCSA log shows which nodes were checked. On the "scheduled action" object the attribute "Count" includes the number of checked/relinked nodes. With "view parent tree" directly on Storage, Library and Repository the parents can be checked. They should disappear after the relink. u DocEXEC and Designer instances set CPT directory to '..\cpts' This PQL is included in the Tools Framework. It searches for all instances of DocEXEC and Designer tool and changes the content of the attribute "CPT directory" from "ResGrp/Group=Group" to "..\cpts". u check version chain of objects This PQL is included in the Base Framework. Formerly the PQL was named "PQL extended". It checks the version chain of the entered objects. n New attribute "Children Deployment State" in CLASS "PROJECT" The attribute shows the deployment state of the children of a project. getstartede V7.6 SP3 381/389 Appendix: main updates in V7.0 n Enhanced class DocDef to offer different IDF handling When running Papyrus DocEXEC within Papyrus Objects, the attribute "IDF directory" in the DocDef template is usually set to "..\DOCDEF Option Update "IDF directory" ------Temporary (Default) : MEM:TEMP File System : ..\DOCDEF n New class SCHEDULED ACTION Scheduled Action objects are used to periodically execute PQL scripts (e.g. run a specific maintenance procedure once a day). n New class STARTUP SCRIPT START Objects instantiated from this class may be used to start any external script with parameters. n New classes for definition of general Settings below Storage u Settings Collection m ISIS Application Settings m Correspondence Framework Settings u System Settings m PQL Settings u Tool Settings n Update class ISIS LOG Modify Pre Constraints for methods, added state "Error", attribute "ReturnCode" and method "Reset" n New attribute "Development class update mode (DevClassUpdateMode)" in Node class This attribute allows to disable the "development class update" (= automatic propagation of modifications in not yet activated classes and templates to all development and test nodes) for the whole domain and instead distribute them via the Domain Controller (like Proxy Management definition in the Proxy Management Collection. Alternatively a manually defined Proxy Management Definition is possible as well. Possible selections: "1: direct update event" ... Default, direct distribution between the nodes "2: via automatic PMC" ... distribution via DC "3: via manual configured PMC" ... no automatic distribution l Several enhancements of Depot setup n Support for distributed Depot (over nodes) n Functions for automatic check-in of NOT-Depot-objects into the Depot n Splitting additionally based on FC_Indexes inside the document instead of usage of banner/trailer documents getstartede V7.6 SP3 382/389 Appendix: main updates in V7.0 l ISIS FW Documentation Framework Allows to automatically generate a documentation (AFP and PDF) of a framework within Papyrus Objects, i.e. it outputs important properties of attributes and methods plus the help texts of all components of a framework. See the documentation for further information. l ISIS Node Documentation Framework Allows to automatically generate a documentation (AFP and PDF) for all nodes of the domain, i.e. it outputs their important settings in tables. See the documentation for further information. l ISIS Change Management Introduces private and public projects for developing in a team with structured handover between single developers and the team on the one hand and the test team on the other hand. l Improved PQL for query of resources via Resource Collection l New CLASSES FormsFill and FormsFillDEF and FormsFillerClient This provides the FormsFill functionality in Papyrus Objects. l New CLASSES ComAgent and ReceiverCom with sample l New User "Security Developer" This user can only modify the CLASSES Project, ProjectManagement, User, Role, Policy. l Client Node Keep Alive object - Node Installation under NAT Conditions This configuration object is required if there is a NAT (network-address-translation) with a firewall between client and server that is configured in a way that only the client is able to initiate a communication to the server but not vice versa. l Node Information Center Used to collect Node Information objects centrally in the Storage. l E-mail Categorizing and Forwarding template setup The purpose of this setup is to categorize incoming e-mails by kewords and stopwords found in subject and body and to forward them to the matching e-mail addresses. It consists of a POP3 Adapter/Receiver (POCxxPOP) using PQL Rules to receive the e-mails, an Categorizer (PCAxxCAT) to find the appropriate addressee, and an SMTP Sender Tool (POCxxESS) to forward them. l Common Rule "Password Check" See "Minimum Password Length" in section "Papyrus Objects Kernel" above. l General improvements of CF2 framework l PROJECT class - only owner may change deployment state This change was wrongly announced with CD v070723, it was not implemented. l WebControl View A simplified workspace for end-users of the Print Management Framework, that is focused on their area without superfluous details. The setup is described in document "Print Management Framework for ISIS Papyrus WebControl - Administrator's Guide (pwciae)". l Perspective Views in the Correspondence Framework Used to construct a workspace for a user with buttons in the lower left frame, to display the user's areas of operations. l Automatically start/stop user's Queue at login/logout The help for the SESSION class and the chapter with the same name in the manuals for Papyrus WebRepository and WebControl describe how to extend the Session to enable this feature. getstartede V7.6 SP3 383/389 Appendix: main updates in V7.0 l PROJECT class - only owner may change deployment state The PROJECT class has been modified, to ensure that only the user who created the Project may change its deployment state. The System Administrator is the only user who is allowed to override this. l Prepare export of whole Project or Framework via drag and drop Drag a Project or Framework object onto the Transfer Collection and select "Create Transfer Package" in the context menu or select the Project or Framework object and click button "Add To Transfer Collection". By this a Transfer object with the all objects of the Project or Framework is generated for export. This function requires the user System Administrator. l Correspondence Framework V2 l The Object Space on the CD contains Correspondence Framework V2. V1 is not delivered anymore. On ISIS CD 2, in directory \POUpdate, POUPdateforImport.zip includes folder "Application Frameworks" with the required transfer files. Depot available with V6.20 l Added attribute DepotID (String) for each DepotControlCenter This new feature allows to access a DepotControlCenter by "Name" and not only by Object-ID. l Extension of the check-in procedure of the Depot. Now it is possible to start a PQL script for each object to be checked-in. Additionally the objects do not only allow to set a specific storage state on index level but also on data object level. l Extension of the Data-Depot importer Supports fixed length and CSV import providing performance improvement and more comfortable handling. l Distributed Depot provides additional states for swapping out a partition and having a rolling number over partitions available with automatic partition-node creation support. l Additional PQL-based stored procudures (STD-LDs) for handling large data volumes in the Depot. IPAS l Improved IPAS standalone installation With V7 IPAS standalone will be installed to the \ipas subdirectory. There is no distinction between first and update installation. In case of existing V6.20 or V7.0 IPAS standalone the Object Space including the Keysets will be used and will be automatically upgraded to the latest TRF level (*.trf files provided in \pocw3700). In case of new installation the empty Object Space from DVD will be installed. l IPAS standalone using local isiscomm The usage of a local isiscomm within IPAS standalone makes it independent of the central used isiscomm which allows to leave IPAS standalone unchanged when updating other products. See the documentation for further details. l Bigger Object Space due to usage of EYE components available with V6.20 l New function to log the status of available product authorizations in a file The KeyAdministration view introduces new methods and attributes in the Keyset Collection to log authorizations into a file. This allows to check the status of authorizations outside of IPAS, additionally it can be viewed via Papyrus Desktop as well. getstartede V7.6 SP3 384/389 Appendix: main updates in V7.0 l Backup Product Authorization functionality n The Backup Product Authorization allows the authorization of certain products via a second IPAS with a separate Hardlock Key based on a time contingent in days (called "Quota"). It was introduced with CD v070111.v620 for Windows. Since CD v080317.v620 it is available for Linux x86 as well. n This "Backup IPAS" can be installed on a machine defined by the customer in parallel to the productive IPAS and be accessed from any machine at any time for any purpose, i.e. it does not only act as a replacement for the main IPAS in case it is down but can also be explicitly used e.g. if the customer has occasionally higher production volumes and needs to extend production to another machine. See the installation documentation "ISIS Software Installation and Product Authorization" chapter "Backup Product Authorization" for further details. l Enhanced Sub IPAS functionality for offline main IPAS See the installation documentation for further details. l With v070820.v620 the CPU usage and number of EXCPs was reduced for IPAS running on z/OS Unix. With v061103 the environment variable ISIS_SOC_POLLINTERVAL was introduced. On z/OS Unix it is recommended to set ISIS_SOC_POLLINTERVAL=5000 (Default: 100). See the documentation for further details. l New attribute "Forbidden Requester" in product part of Keyset This attribute can be used by the administrator to forbid authorization to requester groups in case of concurrent authorizations. l New attribute "Used Identifier" in Keyset Productpart This attribute allows to define which identifier should be inserted in "Used concurrent by" or "Used offline by" by the system. To run the same product on one machine in both WebControl/WebRepository AND in batch the MachineName or IP-Address has to be used. Otherwise two authorizations would be required because the batch job does not have a DomainName.NodeId. The possible values are 1: Automatic 2: Use DomainName.NodeID (or MachineName or IP-Address) 3: use MachineName (or IP-Address) 4: use the IP-Address 17.2.12.16 Papyrus Designer/FreeForm V7.0, Papyrus Server/FreeForm V7.0 l Improved integration of FreeForm projects in Papyrus Objects Integration in "Capture Framework" (tool, cases). l Navigation tool bar Page and image sequence logic improved (combo boxes for navigation). l Improved GUI Display was harmonized, new coloring and icons for definition tree, new icons in tree. l 2 new ICF Text Processing engine settings "Date" and "Amount" l New menu entry "Add Schema Item" Restores schema elements from XML file. l New methods for deleting schema elements in designer n "Delete schema Item" (XML schema and tree element) n "Delete" or "Del"/"Entf" key (tree element only) getstartede V7.6 SP3 385/389 Appendix: main updates in V7.0 l "DefSet" and "Project DefSet" Harmonized display between FFD and FXD, new coloring and icons for elements, new icons in tree and tab folders. l "Date" and "Amounts" object " l "Barcode" Recognition in PDF is now possible. available with V6.20 l Text in format *.txt and reco text in *.XML format can be used as replacement for *.tif images l *.TRG, *.RES, *.CSH are stored in XML format In case of loading a FFD project old file versions are automatically converted to XML format. However a *.TRG file is created at least with size of 1 KB. l Reco text can be copied to Clipboard via button "CopyRecotext" l Reco text can be displayed in two different ways in the "RecoResult" window. Tab "Text" displays without using fonts, tab "Data" displays using fonts. l New Boolean parameter "ClassificationMode" of type Boolean added to condition "A_Classify", it defines the language usage in all cases where no language was selected: n 0 = use all languages n 1 = use no language (only language "General"); this is the default l Parameter "Delete equal value" added to tab "PostOCR" Multiple extraction values can be excluded from the result. 17.2.12.17 Papyrus Designer/FixForm V7.0, Papyrus Server/FixForm V7.0 l Improved integration of FixForm projects in Papyrus Objects Integration in "Capture Framework" (tool, cases). l Navigation tool bar Combo box page sequence logic of FixForm now also used for FreeForm. l Improved GUI Harmonized GUI display between Designer/FreeForm and FixForm, new coloring and icons for all elements of definition tree. l New extraction zone coloring Zone color like element color, color intensive zone border. l Improved element moving in GUI (drag) (CTRL+Click, SHIFT+Click, ALT+Click. l Changed context menus (e.g. "Set Region", "Add Element") and configuration menus (e.g. "date", "amount") l "Find.." button Improved searching of currently active elements using "extended find" alias button ">>". l "X" button (delete) is general tool for the designer tree getstartede V7.6 SP3 386/389 Appendix: main updates in V7.0 l Improved "Add Element" menu for schema elements New restoring features "All elements", "All elements recursive", "single element". l "Add New Element" still creates new schema elements, now including DefSet type usage l New methods of deleting schema elements in designer n "Remove Element from Schema" (XML schema and tree element) n "Del"/"Entf" key or "X" toolbar button (tree element only) l New Designer/FixForm DefSet feature for customer specific schema types n File | Open Definition Set.. n File | DefinitionSets.. n "Add New Element" attribute "Type" allows selection. l "Modify Region" l Creating and modifying a "Region"is now called "Set Region" l Checking X/Y equal resolution is more accurate Clear error handling for asysmetric image resolutions. 300 DPI x 250 DPI images can not be processed anymore. l "preproc.line field removal" Extraction accuracy improved (better removing of a disturbing grid). Algorithm can now estimate grid size if none is set. l "preproc.print text" Processor improved (additional parameters). l "reco.Barcode" Recognition in PDF is now possible (PO and classic FXD). Barcode reco can now return position of unknown barcodes. l "reco.Line" Algorithm improved for better finding of lines. Max length and min length swap in menu. l "reco.OMR" OMR zone adjustment after extraction is now possible. l "textproc.date formatter" New configuration menu, same "Date" object like in FreeForm. l "textproc.date search" New configuration menu, same "Date" object like in FreeForm. l "textproc.amount formatter" New configuration menu, same "Amount" object like in FreeForm. l "textproc.Amount Search" (below 5.4.2 Date Search) New configuration menu, same "Amount" object like in FreeForm. 17.2.12.18 Papyrus Scan Client v7.0 l Support of TWAIN interface 17.2.13 Profile updates Updated Papyrus Client profiles: \userisis\PAPYRUS.PRF \userisis\papyrusc.prf getstartede V7.6 SP3 387/389 Appendix: main updates in V7.0 \browser\PAPYRUS.PRF Updated Papyrus DocEXEC profiles: \userisis\ppde.prf \userisis\ppde_TEC.prf 17.2.14 Limitations The following changes and/or limitations apply to certain Papyrus Products delivered with this DVD: l Hyper threading (HT) may slow down the performance of Software running on Windows Platform. It is recommended to switch off this BIOS option. l The parameter "-profile=" is not supported anymore, use "/profile=" instead. l A font with MaxDescender "-1" is interpreted correctly as zero with V6. 17.2.14.1 OverView AFP Designer l Due to a problem in V5.20 Hebrew texts were wrongly saved. If Overlays containing those texts are loaded with V5.30 or higher they may be reversely displayed and have to be manually corrected. 17.2.14.2 Papyrus PostCalc since V6.00 l Parallel PostCalc processes connected to one and the same table schema are not supported. Full parallel support can be achieved only when using separated schemes. l The parameter PDMDoResetDocsEnv does not work properly. Use PDMDoResetDocsUnPrep instead. 17.2.14.3 Papyrus WebArchive since V6.00 l The archive module (ICD parameter Archive=FileArchive) does not support the old index file *.LST anymore. It is to be replaced by the generic XML index file format or the IDX format. l Driving the archive module via Papyrus Objects (WebControl/WebRepository) in "up and running" mode (no shutdown between jobs) causes that changes of DB connection and "DBProcedure" (PUT_DOC/PUT_POSTDOC) parameters are not activated. 17.2.14.4 Papyrus Host l Coding own DocEXEC DLLs (e.g. DB access) and using Papyrus DocEXEC in "Up & Running Mode" integrated in Papyrus Host requires that those DLLs must be coded in RE-ENTRANT mode. getstartede V7.6 SP3 388/389 Support & contact information Support & contact information If you need support or general information, do not hesitate to contact ISIS Papyrus: General contact information ISIS Papyrus Europe AG Phone: +43 2236 27551 Fax: +43 2236 21081 E-mail: [email protected] Website: www.isis-papyrus.com Product & project support Phone: +43 2236 27551-111 E-mail: [email protected] We will attempt to answer all inquiries within 24 hours. Click here to open the ISIS Papyrus Product Support Request form where you can enter and submit information: www.isis-papyrus.com/support-request It will help us answer your inquiries if you send us the version number and compilation date of the relevant Papyrus products. To find out this information, choose Help | About... or Help | Product information from the main menu. By left-clicking on the version number line you can copy the data. For more details on support types and what kind of information is essential, see "Contacting ISIS Papyrus for Support General Information (supporte)". getstartede V7.6 SP3 389/389" Any error message with the code listed (comma separated) will raise an error dialog. Any other error messages will be gathered and displayed in the standard message box. Sample for error code and corresponding message: 10008, "There is still a field, which MUST be filled!"