Active Directory Data Mapping¶
Data Mapping and Transformation is one of the powerful features of Connect iPaaS. When you create a workflow certain attributes of your trigger application are available to the action application for data mapping while making API calls. These attributes can be mapped to the specific attributes of the action application. This powerful capability not only allows field mapping but it also allows complex transformation using Excel-style functions to apply hundreds of formulas and operations. The choice of Excel-style function makes data mapping on Connect iPaaS a breeze for business users who are already well versed with Microsoft Excel formulas.
Example Scenario with Active Directory Trigger¶
As shown in Figure 1, Active Directory is the trigger application. You can access the following attributes of Active Directory event in any of the application actions while designing your workflow.
- CN - Common name of the User/group/list in AD
- CO - Country/region where the user is located
- Country Code - Code of the country where the user is located. It also specifies the users language of choice
- Department - Name of the department where the user works
- Department Number - Helps in identifying the department within an organization
- Distinguished Name - Unique identifier for the entry in the directory
- Employee ID - ID of an employee
- Employee Type - Job Category for an employee
- Given Name - First name of the user
- Mail - Email address of the user
- Mail Nickname - Nickname we assign to the user
- Name - Name of the entry created in directory
- Object class - A list of classes from which this class is derived.
- Physical Delivery office - Office location of user's business
- Proxy Addresses - An address by which a foreign mail system recognizes Microsoft Exchange Server recipient object
- SAM Account Name - Log in name that supports previous versions of Windows servers and clients.
- SN - Surname of the user.
- Title - The user's formal job title. For example, Senior Programmer.
- Telephone Number - The primary telephone Number
- User Principal Name - Primary logon name for a user. By convention, the UPN uses the email address of the user.
In the example shown in Figure 1, the workflow will send a message to Slack when a new member is added to a specific distribution list.
The Slack message body is generated by using Display Name, Department and Department Number as the mapping parameters from Active Directory.
Refer to How does mapping and transformation work? for more details.