Setting up the data for the Vendor role

You need to set up data to use the Vendor role.

Before you begin

Add the following properties to the file in the MDM/etc/default folder of the application and restart the Admin UI after the update:
  • vendor_organization_hierarchy=Vendor Organization Hierarchy
  • vendor_product_workflow=Vendor Product Introduction Workflow
  • vendor_collab_table=Vendor Collab Table
  • vendor_role_name=Vendor
  • owner_approval_workflow=Owner Approval Workflow


  1. Import the file.
  2. Verify that the Catalog ACG, Hierarchy ACG, and Vendor role are available as follows:
    • Browse to Data Model Manager > Security > Access Control Groups > Access Control Group Console, you should see Catalog1 ACG and Hierarchy1 ACG.
    • Browse to Data Model Manager > Security > Role Console , you should see Vendor role.
  3. Verify that Vendor Organization Hierarchy, Vendor Lookup Table, Vendor Collab Table, and Vendor User are available as follows:
    • Browse to Module > Please select a module to add drop-down list, you should see the Vendor Organization Hierarchy.
    • Browse to Product Manager > Lookup Table > Lookup Table Console, you should see the Vendor Collab Table.
  4. Add the Vendor Organization Hierarchy from the Modules section to the left pane as follows:
    • Browse to Module > Please select a module to add > Vendor Organization Hierarchy > +.
  5. Create Spec, Hierarchy, Catalog, and attribute collection for the catalog attributes as follows:
    • To create spec, browse to Data Model Manager > Specs/Mapping > Specs Console.
    • To create hierarchy, browse to Product Manager > Hierarchy > New Hierarchy.
    • To create catalog, browse to Product Manager > Catalog > New catalog.
    • To add the catalog to the left pane, browse to Module > Please select a module to add > Select Catalog > +.
    • To create attribute collection, Data Model Manager > Attribute Collection > New attribute collection.
  6. Add the vendor organization hierarchy as a secondary hierarchy to the catalog as follows:
    • In the left pane, right-click the catalog that you added in the previous step and browse to Catalog Attributes > add secondary hierarchy drop-down list, select Vendor Organization Hierarchy, and click Add.
  7. Add a vendor organization under the Vendor Organization Hierarchy as follows:
    • Right-click Vendor Organization Hierarchy > Add Organization, enter Vendor Name and click Save.
    The collaboration area for the newly added vendor organization is created and mapped into the Lookup table. Verify by browsing to Collaboration Area > Collaboration Areas > Collaboration Area Console.
  8. Add the user data in the Vendor User Creation job and run the report as follows:
    • Browse to Report > Report Console > Vendor User Creation Report Job, enter User Details, then browse to Save > Back, and click Report Console icon.
      Note: The User Details/Vendorname field in the user details sections for the user creation report needs to be an existing vendor category.
    Previous step adds the user as an administrator for the collaboration created.
  9. Browse to the Vendor Product Introduction Workflow and add the attribute collection that is created for the catalog attributes into all the workflow steps. Ensure to add the collection in the initial step. Similarly, add the attribute collection to the Owner Approval Workflow, along with the initial step.
  10. Create the owner approval collaboration area by running the report job as follows:
    • Browse to Report > Report Console > Owner Collab Creation Job, and select the created catalog.
  11. Verify secondary spec ‘VendorInfo’ is mapped to the vendor organization as follows:
    • Browse to Vendor Organization Hierarchy > Specs.
    Important: The items coming from the Vendor to the Owners Collaboration Area get mapped to the Vendor Organization Hierarchy and the administrator should not add, edit, or delete any other vendor hierarchy to the item. If the administrator deletes the vendor hierarchy from the Category tab, the item is lost as due to no linking. If the administrator adds other vendor hierarchy to the item, it is a security breach as one vendor's item gets mapped to the other vendor.

What to do next

Add the full admin access to the Catalog 1 ACG, which is used for the catalog that is created for the vendor.