SDX 6.4.x Application Library Guide > Sample Workflows > Test Directory Workflow

Test Directory Workflow

The Test Directory workflow demonstrates the use of the directory work items. The directory work items enable directory objects not immediately related to the service provisioning (User, Service, and UserServiceProfile) to be accessed from within a workflow. However, this workflow uses the directory work items to access the Service and the UserServiceProfile objects, so that you can avoid having to create other objects, such as network objects.

The objective of the Test Directory workflow (Figure 61) is to assign a value to the virtualRouterName attribute of the UserServiceProfile object. By looking at the translation table in Chapter 27, Workflow Translation Table, you can see that this attribute is not present in that object. The only alternative, then, is to access it via the directory work items. This attribute is also present in the Service object. If this attribute already has a value, the workflow completes without doing anything. If the attribute does not have a value, the workflow copies the value from the Service object. If the Service object also does not define a value for this attribute, a value of default is assigned to this attribute.

Figure 61: TestDirectoryWorkflow: Accessing the SDX Directory Directly

The components are configured as follows:

• All directory work items:

• All expert and common properties accept the default values.

• VRLookup, a directory lookup work item:

• ObjectDN—Specifies the DN of the UserServiceProfile object that triggered this provisioning request: %ServiceProfileDN%.
• TranslationTable—String array with one element, mapping the LDAP name virtualRouterName to the workflow domain name VirtualRouter: VirtualRouter=virtualRouterName.

• GetVRSvc, a directory lookup work item:

• ObjectDN—Specifies the DN of the Service object related to this provisioning request: %ServiceDN%.
• TranslationTable—String array with one element, mapping the LDAP name virtualRouterName to the workflow domain name VirtualRouter and specifying a value of default if the attribute is not defined in the object: VirtualRouter=virtualRouterName|default

• SetVRProfile, a directory update work item:

• ObjectDN—Specifies the DN of the UserServiceProfile object that triggered this provisioning request: %ServiceProfileDN%.
• TranslationTable—String array with one element, mapping the LDAP name virtualRouterName to the workflow domain name VirtualRouter: VirtualRouter=virtualRouterName.

If the VRLookup work item does not retrieve a value for the attribute, it fails and generates a proceed token for its NOK output, which is connected to the GetVRSvc work item. If this attribute already has a value and nothing needs to be done, then it connects directly to the OR work item that joins the two paths before the End State work item.

On the left path, the GetVRSvc tries to get the value for the attribute from the Service object, but specifies a default value if the attribute has not yet been defined. It generates a proceed token for its OK output, which is connected to the SetVRProfile work item. The SetVRProfile work item performs the update on the UserServiceProfile object, assigning the value to the virtualRouterName attribute.

The Test Directory workflow requires a parameter list that specifies ServiceDN and ServiceProfileDN as input parameters. The workflow and its associated parameter list are both in the samples package.