Clarity

I'm looking for advice about new functionality we are wanting to add to our Clarity environment  (CA PPM) .  The issue is that we need to filter on attributes not on the object we want to edit. 

Here is some background:

(Hierarchy of Objects) Project -> Impact -> Impacted Subarea  (Subareas are just basically a OOTB ROLE).  The filter attributes are on the ROLE, but tied to the Impacted Subarea object.

Filtering:

We want to use a NSQL based portlet to Filter the Impacted Subareas.  Many of the filtering attributes are on the Subarea (ROLE), not the Impacted Subarea, so that is why we use the NSQL portlet for this step.

Editing:

Then we want to be able to select one to many of resulting rows on this portlet to open an object based portlet to perform the in line edits on the attributes for the selected Impacted Subareas.  The trigger for this would be to select the rows in the Filter portlet, then click a button (EDIT?) to open a pop-up portlet.

Flow:

1) User searches in NSQL portlet for Impacted Subareas using filters from ROLE object.

2) User select 1 or many resulting rows (checkbox?) and then clicks a button (EDIT?).

3) An object list portlet in a pop-up format is displayed.  All selected rows appear in grid, editable.

4) User makes updates in this portlet and clicks SAVE and RETURN.

I have started looking into the Filter Portlet, but haven't had much experience with it.

I'm not sure this is possible in Studio, but I wanted to ask before we just add these duplicated attributes to the Impacted Subarea object.

Thanks for any ideas,

Terry

What you are trying to achieve is extremely complicate and it will create a long list of duplicate attributes (as flags I guess) to get a "fancy layout" so users don't have to navigate, extra filter or click around.

I'd strongly not go for it an educate customer/users to use CA PPM in traditional way. 

User should learn to filter and edit per "instance" level.

Hi Terry,

I think your main problem will be that with NSQL portlets you are unable to select multiple items  - there is no checkbox as such, or add buttons - such as <Edit>.

Your idea of using Filter Portlets might be the way to go, but will not solve your full requirement.

Thanks for the feedback.  I was afraid it would not be possible.  I have added those fields to the object and will populate them with a process on the create event.  That way I can search on them.  I think I will need to run a weekly job to clean up any possible changes in the data.  Not pretty, but the users will be happy.

Thanks again,

Terry