Generated by XML Authority The ADPr document currently supports two (2) types: BusinessChange and Status. The BusinessChange type indicates that the contents of the document is the result of a business process that adds, changes, or deletes a user relative to the business. The TaskStatus type indicates that the document contains a response to the Action(s) requested by a previous ADPr BusinessChange document. The ACTIONS section is an envelope that contains the administrative user and a sequence of tasks to be performed on the taget system. Note that the enocde provide a choice of repeatable tasks to ensure that you can only select on task type but perform as many of them as is deemed necessary. This element will contain all of the information necessary to properly identify the sender to the target system. It will also carry the information required for the target system to understand how to decrypt the CONTEXT and ACTIONS sections if they were encrypted. This element will contain all of the information necessary to authorize the transaction on the target system. It is used in conjunction with the information in the authentication section which identified the user. The CONTEXT defined the bounding parameters that form the environment for the transaction. For example, this element can contian information about contracts and SLAs or machine, domain, and groups. The date when the actions should have completed (be in effect) Defines the person or role to which a processing error should be escalated The HEADER contains all of the authentication, authorization, and administrative information required to support the transaction. The Transaction and Sequence attributes are used in conjunction with the ADPr ID to manage the sequence of transmission within one (1) transaction. They can be used to denote direction and flow of the conversation. Rather than containing a certificate, this element contains the name of the public key that was used to encrypt the data so that the target system can use the matching private key to decrypt it. Name of the origin system A common element of all tasks that conveys the name of the action to perform. Typical values for this field may include but are not limited to "add", "change", "delete", "enable", "disable", "suspend", "renew", etc. A task that allows the eProvisioning of resources that have been procured either manually or electronically. A task that allows adding, modifying, or deleting Exchange accounts. A task that allows adding, modifying, or deleting Notes accounts. A task that allows adding, modifying, or deleting directory entries. A task that allows adding, modifying, or deleting UNIX accounts. A task that allows adding, modifying, or deleting POP3 or IMAP4 mail accounts. A task that allows adding, modifying, or deleting Windows NT accounts. A task that allows adding, modifying, or deleting people in an HR system. A unique identifier created by the origin system and contained by all ADPr documents that relate to the same transaction. Organization Name Complete common name including prefixes and suffices Surname / Family Name without any suffices Part of the data used within the context to establish the boundaries of the transactions. Contains data identifying policies that may govern or limit the actions Descriptive Name of Policy policy descriptor and associated data Default LDAP Person Schema based on InetOrgPerson Default data elements that are required to create or maintain a Microsoft Exchange user account Default data elements that are required to create or maintain a Lotus Notes user account Default data elements that are required to create or maintain a Microsoft NT user account Proposed data elements used to convey provisioning information assiciated with an electronic or manual purchase. Default data elements that are required to create or maintain a UNIX user account Default data elements that are required to create or maintain a typical POP3 or IMAP4 account on systems like Eudora or Netscape. Contains the value that the origin system believes is currently contained by the attribute on the target system Contains the value that the origin system wants to set into the attribute of the target system RACF data A task that allows adding, modifying, or deleting entries in RACF. A unique identifier that's created by the originating system and maintained throughout the life of the transaction Contains elements that control the order of execution and reporting for all actions in the docuement. When more than one action is defined, controls whether execution is serial or parallel When more than one action is defined, controls whether the results are reported individually for each action or using one report when all actions complete