Action Request System 5.1 Developing AR System Applications ...

More documents

Recommendations

Info

Action Request System 5.1The OLE Automation Active Link ActionUse the OLE Automation action to share functionality between applicationsthat support OLE. When using this action, AR System acts as an OLEautomation controller client to an OLE server.The following procedure describes how to implement OLE automationwithin AR System. Like SQL, you should debug OLE automation calls in afull OLE and COM development environment and then use that knowledgeto build the same calls in AR System Administrator.A sample exercise can be found on page 47. This example uses OLEautomation to create a form and active link to open Microsoft Word, spellcheck text in a field in that form, and return the corrected text to the field.Note: If you are designing an active link for a form that is also used by clientson platforms other than a PC, verify that the current platform is a PCas a condition of activating the DDE action. To do this, include aqualification that uses the $HARDWARE$ keyword to verify the currentplatform. See Developing AR System Applications: Basic guide for moreinformation on building qualifications.Defining the OLE Automation Active Link ActionWith the Server Window open:1 Choose File > New Server ObjectThe New Server Object dialog box appears.2 Select Active Link from the New Server Object field.3 Click OK.The Create Active Link dialog box appears.4 Set up the conditions in the Basic tab.5 Click the If Action tab, or click the Else Action tab.6 From the New Action list, select OLE Automation.42 "Chapter 2—Using Microsoft OLE Automation in Workflow
Developing AR System Applications: AdvancedThe fields required to define the OLE Automation action appear. Thefollowing figure shows these fields and an example of how an OLEAutomation active link action might look after you complete the remainingsteps in this procedure.Figure 2-1: OLE Automation Active Link Action7 If you want animated Genie assistance as you complete the rest of theprocedure, select the Genie Help check box.8 From the Automation Servers list, select the appropriate OLE server orcontrol:! OLE Local Servers—Lists the OLE servers on your machine.! OLE Automation Control—Lists the controls on your machine.Because remote automation is not supported, users can access only the OLEactive link Automation action if the same OLE components selected in ARSystem Administrator also exist on their computers.9 Double-click the appropriate server or control.The list of objects defined in the OLE server is displayed under the Typelibrary tree hierarchy.10 From the Type Library Information list, select the Objects folder.The OLE Automation Active Link Action ! 43
Page 1 and 2: PART NO: AR-512-DAAG-01Action Reque
Page 3 and 4: ContentsPreface . . . . . . . . . .
Page 5 and 6: Developing AR System Applications:
Page 11 and 12: PrefaceAudienceThis guide is writte
Page 13 and 14: Action Request System DocumentsDeve
Page 15 and 16: 1CHAPTERDefining Guides and Guide A
Page 41: 2CHAPTERUsing Microsoft OLE Automat
Page 47 and 48: Sample Exercise: Using OLE Automati
Page 63 and 64: 3CHAPTERDynamic Data ExchangeThis c
Page 89 and 90: 4CHAPTERUsing Full Text SearchThis
Page 93 and 94:
Developing AR System Applications:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Combining FTS and Non-FTS FieldsDev
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Debugging FTSDeveloping AR System A
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
5CHAPTERLocalizing AR System Applic
Page 113 and 114:
Page 115 and 116:
Tasks for Localizing AR System Form
Page 117 and 118:
Advanced TasksAdvanced localization
Page 119 and 120:
Creating a Localized View of a Form
Page 121 and 122:
Localizing View Components Through
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
6CHAPTERCreating Reports for the We
Page 143 and 144:
Page 145 and 146:
AR System Configuration Tool Option
Page 147 and 148:
AR System Report Plug-inDeveloping
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Exporting AR System Data to a FileD
Page 175 and 176:
Page 177 and 178:
7CHAPTERImporting and Exporting Obj
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
8CHAPTERImporting Data into AR Syst
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
9CHAPTERUsing Source ControlThis ch
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Exporting AR System Objects into So
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
10CHAPTERServer Events FormThe Serv
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Datatypes ValuesDeveloping AR Syste
Page 255 and 256:
11CHAPTERDefining Packing ListsPack
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
12CHAPTERCreating and Using Web Ser
Page 267 and 268:
Web Service Description Language (W
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Example 2: Consuming a Simple Flat
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
13CHAPTERUnderstanding the Alert Sy
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
14CHAPTERThe AR System ODBC DriverT
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Considerations for Join FormsDevelo
Page 373 and 374:
Using Microsoft Excel with AR Syste
Page 375 and 376:
15CHAPTERUsing the LDAP Plug-InThis
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Directory Service Attributes and Ob
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
16CHAPTERUsing Action Request Syste
Page 403 and 404:
AR System Administrator Commands an
Page 405 and 406:
Page 407 and 408:
AR System Administrator CLI Example
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
AR System Windows User Tool CLI Exa
Page 419 and 420:
AAPPENDIXSpecial System FormsThe AR
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
IndexAaccrue operatorAdvanced Searc
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
show all

Action Request System 5.1 Developing AR System Applications ...

Create successful ePaper yourself

Delete template?

Save as template?