Hierarchies: Configure Import Schedule feature

Products

• Clarity FedRAMP
• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

The Configure Import Schedule is not working properly when the Sub-level filter criteria uses attributes created at the custom object itself. Works well with investment level attributes

 

STEPS TO REPRODUCE

 

1. Go to Classic Administration > Studio > Objects
2. Create a custom investment object: MyCustomObject. Ensure the Include In Hierarchies checkbox is enabled
3. MyCustomObject > Attributes tab > Create a boolean attribute > MyCustomObjectBoolean
4. Go to Classic Administration > Studio > Objects > Investment object > Attributes tab
5. Create a boolean attribute > MyInvBoolean
6. MUX > Projects > Create 2 projects with names: TestingHierarchy1 and TestingHierarchy2
7. MUX > Investments > MyCustomObject
8. Create 3 instances of MyCustomObject: MyCustomObject1, MyCustomObject2, MyCustomObject3 
9. Add the parent field to grid and set TestingHierarchy1 as parent of those custom object instances
10. Go to MUX > Hierarchies > Create a hierarchy instance of Type Investment
11. Edit the hierarchy > Actions > Configure Import Schedule
12. Populate the following:
    • Days field to Monday
    • Import source: All investments and children
    • Investments filter criteria: 
      • Type:  Project
      • Add filter: Name contains Hierarchy
    • Sub-level filter criteria
      • Type:  MyCustomObject
      • Add filter: Investment > MyInvBoolean > No
    • Click Next
13. You get a screens with the estimated total investments to be added: Total of 5
14. Click Save and import now
15. TestingHierarchy1 and TestingHierarchy2 projects to be added. MyCustomObject1, MyCustomObject2, MyCustomObject3 instances to be added as the MyInvBoolean field is set to No
16. Edit the hierarchy > Actions > Configure Import Schedule 
17. Populate the following:
    • Days field to Monday
    • Import source: All investments and children
    • Investments filter criteria: 
      • Type:  Project
      • Add filter: Name contains Hierarchy
    • Sub-level filter criteria
      • Type:  MyCustomObject
      • Add filter: MyCustomObject > MyCustomObjectBoolean > No
    • Click Next
18. You get a screen with the estimated total investments to be added: Total of 2
19. Click Save and import now

Expected Results: TestingHierarchy1 and TestingHierarchy2 projects to be added. MyCustomObject1, MyCustomObject2, MyCustomObject3 instances to be added as the MyCustomObjectBoolean field is set to No

Actual Results: Only TestingHierarchy1 and TestingHierarchy2 projects are added. 

 

Notes:

• If at step 17, Sub-level filter criteria, we use the MyCustomObject > MyCustomObjectBoolean > All then the import is OK
• If we edit the Configure import schedule, we change the Import source to Children of existing hierarchy and use the Sub-level filter criteria of step 17 (MyCustomObject > MyCustomObjectBoolean > No) the data to be imported is correct

Environment

Clarity 16.4.2

Cause

This is caused by DE198985

Resolution

This is currently under analysis