Please put ALL you bug reports in this thread

[Ashok Hingorani]

MS will look at all reports we send in but best they all be in one place.

none of us need to respond to any of the threads unless we already have a
clear solution in which case we should not wait for MS.

In principle we will ensure that MS does not miss any of the postings in
this thread, so they should best be kept to bugs only at this stage, please.

bst rgds

ashok

 

[Morten71]

The "Attachment" field in Groove 2007's Forms toll has several columns
(Name, Size, Type, Modified Date, Modified By) that seem only to be
visible "design-time".

 

[Ashok Hingorani]

Christian

could i request you to pls copy / paste that post in here or paste a link to
it. makes it easier for all

rgds

ashok

 

[Ashok Hingorani]

Form Designer errors
------------------------
1. whenever you try to hide / show fields the entire form can get corrupted.
there is no error if this is done under script control

2. changing the size allocated to a date fields, then trying to move the
field, causes the form to get totally corrupted

3. creating groups in a tab then removing them kills the form

4. adding more than one tab control to a form generates an error (non fatal
if you remove the extra tab)

5. Lookups created using the normal designer are much slower than the same
lookup in a script. Also, combo boxes refresh each time a new value is picked
up / added and this could be a few thousand.

6. Forms can take many minutes to open, specially if there are self lookups
used and more than 5,000 entries in the form.

what is totally wierd is that restoring a corrupted Form from a backup does
not help - the backup also shows the same error. not sure how this can be. is
each form / workspace instance not a totally independent one. ?

not a bug but a big problem.
---------------------------------
we have a form ProgrammingAlias Name field provided but it plays no role in
defining a lookup to another form - this is a killer as each time we need to
deploy the same forms to a new set of workspaces, all lookups need to be
manually re-done. If they were using the programmingalias, not the formURI,
then it would be far more logical and form sets could be easily deployed to
new workspaces as they would find related forms by the alias.

Huge Security Issue, posted here before
----------------------------------------------
the ability to restrict forms / fields to some users implies that the other
data is secure from them - ie no show so no access. But this is totally
misleading as a simple export to excel, will show all data in the tool.
Export should adhere to the roles and permissions and the form and field
visibility set by the user.

Of course the ability to create a duplicate of any tool / workspace defeats
all security because one becomes the manager of the new space created, with
access to all info.

users are easily misled into thinking that (lack of ) visibility on the
screen equates to non-access to that data but Grooves current philosophy is
that "you have the space, you have all it contains". This really should be
fixed or made clear in the forms designer page itself.


rgds

ashok

 

[Schultz IT Solutions]

Thanks Ashok, great idea.

I tried for quite some time to let MS know about a nasty bug in the chat
tool (but I sure do not want to pay EUR 99,00 to the support line for this ;-)


In Groove Chat Tool, there is a a vital bug (at least in the german version):
The toggle between text and freehand mode is activated NOT by the keyboard
shortcut [CTRL-T] (as it is meant to be) but by the keyboard ("very short
cut") [T].

So every time, someone wants to enter a letter [T], the chat swiches to
freehand mode. This is a major bug, as [T] is a quite common letter (only in
this message about 50 occurances).

As IT consultants, it is very annoying for us to make a Groove presentation
and have to make sure not to present the Chat Tool (or at least, avoid the
letter [T] - it would make a very bad impression to prospective customers to
see that they cannot use the Chat Tool because of this bug).

Kind Regards
Ruediger Schultz

 

[Morten71]

Styling form elements:

1) a lot of style-code is auto-generated for certain fields: ie. the
"Rich text field" field label produces:

<TD VALIGN="top" ID="idkMTtxtRichDescription_label"
CLASS="fieldLabel"><FONT CLASS="fieldLabel"> <div><p
style="text-align: left; text-indent: -0.00pt; margin-left: 0.00pt;
margin-right: 0.00pt; margin-top: 0.00pt; margin-bottom: 0.00pt"><span
style="font-family: MS Shell Dlg; font-size: 10.00pt; color: black;
font-weight: normal; font-style: normal; text-decoration: none;
line-height: 12.00pt">Describtion</span></p></div><FONT
STYLE="color:#FF0000; margin:0px 2px 0px 2px;">*</FONT></FONT></TD>

and entering a class into the classname does not help.

A 100% separation of style and html in the form tool produced html
would be really nice.

Morten

 

[Evan Venn]

http://groove.tumblr.com/post/1526935

A feaure list and response to the list above.

 

[c1sbc]

The 'Web Links' tool is missing - that's my favorite one from v3.1 and
earlier versions. This is not 'delicious' !!!
;-)

SBC

Thanks Ashok, great idea.

I tried for quite some time to let MS know about a nasty bug in the chat
tool (but I sure do not want to pay EUR 99,00 to the support line for this ;-)


In Groove Chat Tool, there is a a vital bug (at least in the german version):
The toggle between text and freehand mode is activated NOT by the keyboard
shortcut [CTRL-T] (as it is meant to be) but by the keyboard ("very short
cut") [T].

So every time, someone wants to enter a letter [T], the chat swiches to
freehand mode. This is a major bug, as [T] is a quite common letter (only in
this message about 50 occurances).

As IT consultants, it is very annoying for us to make a Groove presentation
and have to make sure not to present the Chat Tool (or at least, avoid the
letter [T] - it would make a very bad impression to prospective customers to
see that they cannot use the Chat Tool because of this bug).

Kind Regards
Ruediger Schultz


--
Groove Support @ Schultz IT Solutions

Our experience with Groove (since 2000) makes us one of the leading
consulting companies in Europe - call on us.

MS will look at all reports we send in but best they all be in one place.

none of us need to respond to any of the threads unless we already have a
clear solution in which case we should not wait for MS.

In principle we will ensure that MS does not miss any of the postings in
this thread, so they should best be kept to bugs only at this stage, please.

bst rgds

ashok