Action Request System 5.1 Developing AR System Applications ...

More documents

Recommendations

Info

Action Request System 5.1Change the Label to User ID as shown below.Figure 15-6: The Field Properties Window, Display Tab4 Click the Database tab to display the database and vendor propertiesassociated with the field.Figure 15-7: Field Properties Window, Database Tab5 Choose Required as the Entry Mode.6 In the Name field in the Vendor Information box, enter the attribute name,uid, in the Vendor Information Name field.7 Position the field as required.8 Choose File > Save Form to save the field properties.384 "Chapter 15—Using the LDAP Plug-In
Developing AR System Applications: AdvancedMulti-Valued AttributesMost attributes within an object class are defined to support one value. Someattributes, however, can have many values. For example, a “person” objectincludes a “telephone number” attribute that allows you to specify manyphone numbers. When this attribute is retrieved, the directory service canreturn zero, one, two, or any number of telephone numbers as atomic values.This differs from typical database applications and the AR System in that acolumn or field only stores one value. If you want to store two phonenumbers in such an application, you would add a new column or field toaccommodate the additional data.To resolve this difference between the two data models, you use a specialnotation when specifying the attribute name in the Field Properties window.[*]Values associated with attribute name are concatenated into a single value inthe AR System but separated with separator string. For example, toconcatenate all values associated with the telephoneNumber attribute andseparate each value with a comma you would enter the following as theattribute name in the Form Properties window:telephoneNumber[*,]You could then define workflow to extract, add, or modify values in thecomma-separated list of telephone numbers.Identifying Objects UniquelyThe AR System uniquely identifies entries within a form through the RequestID field.Objects within a directory service define an attribute called the DistinguishedName (dn) that uniquely distinguishes one object from another. An object’sdistinguished name often consists of one or more other concatenatedattributes, for example:uid=abarnes,ou=People,o=remedy.comBuilding AR System Forms For Directory Services ! 385
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 7 and 8:
Page 9 and 10:
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 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
2CHAPTERUsing Microsoft OLE Automat
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Sample Exercise: Using OLE Automati
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
3CHAPTERDynamic Data ExchangeThis c
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
4CHAPTERUsing Full Text SearchThis
Page 91 and 92:
Page 93 and 94:
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: Developing AR System Applications:
Page 357 and 358: 13CHAPTERUnderstanding the Alert Sy
Page 365 and 366: 14CHAPTERThe AR System ODBC DriverT
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 383: Developing AR System Applications:
Page 395 and 396: Directory Service Attributes and Ob
Page 401 and 402: 16CHAPTERUsing Action Request Syste
Page 403 and 404: AR System Administrator Commands an
Page 407 and 408: AR System Administrator CLI Example
Page 417 and 418: AR System Windows User Tool CLI Exa
Page 419 and 420: AAPPENDIXSpecial System FormsThe AR
Page 425 and 426: IndexAaccrue operatorAdvanced Searc
show all

Action Request System 5.1 Developing AR System Applications ...

Create successful ePaper yourself

Delete template?

Save as template?