Hi all,
I've been banging my head about this for a few days now and was hoping someone here might be able to help!
I have created a discussion column within a module. The module has about 1200 objects. The discussions column displays the discussions as "indicators for all discussions" i.e. the little speech bubble.
My quesion is this: is it possible to filter down only those objects which have a disucssion (open or closed)? For example if I had only 3 discussions in the whole module, how could I find those 3 without scrolling down through all 1500 objects? Is it possible?
The column filter option only has a "contains" option, which I believe requires some form of text in order to be able to fulfill its filter function.
Any help is greatly appreciated!
Cheers!
JN
JuanNil - Thu Aug 04 03:55:22 EDT 2011 |
|
Re: How to filter Discussions
SystemAdmin - Thu Aug 04 07:01:25 EDT 2011
1.) Use a another discussion column type containing some static text which you can filter on, e.g. the "Display all discussions and comments"
or
2.) Use your own Layout DXL column which display a text for objects having discussion, for example see below - you can also convert this to Attribute DXL which allows you to filter objects even when the column is not shown, based on the attribute value.
Discussion D =
null
int i = 0
for D in obj
do
{ i++
}
if (i > 0) display
"Discussion"
|
|
Re: How to filter Discussions
JuanNil - Thu Aug 04 08:07:14 EDT 2011 SystemAdmin - Thu Aug 04 07:01:25 EDT 2011
1.) Use a another discussion column type containing some static text which you can filter on, e.g. the "Display all discussions and comments"
or
2.) Use your own Layout DXL column which display a text for objects having discussion, for example see below - you can also convert this to Attribute DXL which allows you to filter objects even when the column is not shown, based on the attribute value.
Discussion D =
null
int i = 0
for D in obj
do
{ i++
}
if (i > 0) display
"Discussion"
You would think it would be possible to filter on the discussion though eh? Especially since there is the option to just use a speech bubble indicator.
Cheers!
JN
|
|
Re: How to filter Discussions
llandale - Thu Aug 04 15:56:20 EDT 2011
Never dealt with Discussions before, but it appears Pekka is on the right track. You could create a string AttrDXL perhaps "HasOpenDiscussion" with the code below, then run a filter on whether that attribute is "True" or not.
Discussion dis DiscussionFilter disf = discussionFilter(obj, OpenDiscussions) bool HasDiscussion =
false
for dis in disf
do
{ HasDiscussion =
true
}
if (HasDiscussion)
// then obj.attrDXLName =
"True"
else obj.attrDXLName =
" "
Boolean attr will work better, but if you display the attr in a column all those useless "false" displays obscure the far more important "True" displays.
|
|
Re: How to filter Discussions
kbmurphy - Thu Aug 04 19:48:48 EDT 2011
Tsk, tsk to everyone for missing the obvious.
1. Tools>Filter>Define...
2. Choose the Column tab.
3. Choose the Discussion column
4. Set contains to '.*' (without the quotes)
5. Check the Regular Expression checkbox.
6. Click Apply or OK.
7. Lavish me with praise.
|
|
Re: How to filter Discussions
kbmurphy - Thu Aug 04 19:53:21 EDT 2011 kbmurphy - Thu Aug 04 19:48:48 EDT 2011
Tsk, tsk to everyone for missing the obvious.
1. Tools>Filter>Define...
2. Choose the Column tab.
3. Choose the Discussion column
4. Set contains to '.*' (without the quotes)
5. Check the Regular Expression checkbox.
6. Click Apply or OK.
7. Lavish me with praise.
I still say no DXL required for this solution...just follow my steps above.
|
|
Re: How to filter Discussions
JuanNil - Fri Aug 05 02:45:03 EDT 2011 kbmurphy - Thu Aug 04 19:53:21 EDT 2011
Ok, my post above doesn't work with the indicator, but it does work for discussion text. Still why use the indicator when you can just put the discussion details itself in the column?
I still say no DXL required for this solution...just follow my steps above.
Thanks for the replies so far.
I'm trying to minimise the amount of DXL scripting at the moment so was hoping for a more 'simple' solution.
kb - having discussion details is suitable if there's just one or two comments, but if you have 4+ engineers adding comments then it will become extremely busy and most definitely messy. The indicator allows us to see there's a discussion open, and if needs another can be added for closed discussions etc.
Is there no way to filter on the indications then, other than DXL?
Cheers!
JN
|
|
Re: How to filter Discussions
SystemAdmin - Fri Aug 05 06:13:46 EDT 2011 JuanNil - Fri Aug 05 02:45:03 EDT 2011
Hi guys,
Thanks for the replies so far.
I'm trying to minimise the amount of DXL scripting at the moment so was hoping for a more 'simple' solution.
kb - having discussion details is suitable if there's just one or two comments, but if you have 4+ engineers adding comments then it will become extremely busy and most definitely messy. The indicator allows us to see there's a discussion open, and if needs another can be added for closed discussions etc.
Is there no way to filter on the indications then, other than DXL?
Cheers!
JN
need DXL. The scripts in Insert / Column where you insert a Layout DXL showing discussion data are
mostly unencrypted, so even those might be modified.
The basis of this is of course Telelogic's decision to implement discussions not as attributes but something else (whatever?). Thus when you add a discussion, nothing is changed in the module so you can add discussions even in baselines. But as you said, IBM / Telelogic should have implemented some kind of menu item for filtering objects with discussion, similar as exists for suspect links.
|
|
Re: How to filter Discussions
SystemAdmin - Tue Aug 16 10:15:23 EDT 2011 SystemAdmin - Fri Aug 05 06:13:46 EDT 2011
I do not see any other way of filtering objects with discussions than displaying some column with text or playing around with different DXL solutions, you might show the discussion status with DXL, do a discussion trigger or develop your own filtering dialog to filter discussions, but all of those
need DXL. The scripts in Insert / Column where you insert a Layout DXL showing discussion data are
mostly unencrypted, so even those might be modified.
The basis of this is of course Telelogic's decision to implement discussions not as attributes but something else (whatever?). Thus when you add a discussion, nothing is changed in the module so you can add discussions even in baselines. But as you said, IBM / Telelogic should have implemented some kind of menu item for filtering objects with discussion, similar as exists for suspect links.
Object o Discussion dis =
null bool accepted =
false filtering off
// following loop only accesses displayed objects
// cycle through all displayed objects
for o in current Module
do
{ accepted =
false
for dis in o
do
{ accept o accepted =
true
break
}
if (!accepted)
{ reject o
}
} filtering on
/Kristian
|
|