Conference iosg::all-in-1_v30

    Ricardo,
    
    well in the absence of a Differences Document in v3.0 you of course
    have the VBC option off CM but that's only as good as the data that
    was entered into the base changes file in the first place and in
    the case of DOCDSC the change description doesn't explain this change
    though it does describe six other changes.
    
    Regards,
    
    Andrew.D.Wicks

    
    	Well I think its because when you change drawer, the folder names
    	are probably different in that drawer, so the folder name you had
    	is probably invalid, so it was found to be annoying to default to
    	the old folder name, blank is better (except in your case where
    	you didn't actually CHANGE the drawer name, just why did you go to
    	the drawer field?)
    
    Regards,
    Paul

    Paul,
      The explanation I gave to the customer was similar to yours in .2.
    He did not like it and said he prefered it the way it
    was in 2.4, users have the option to clear the field.So I suggested CM
    if he still prefers the 2.4 style.He's considering it but insisted for 
    more explanation about the change.
    
      WHY HE WENT TO THE DRAWER FIELD ? He TYPED TOO FAST and downed arrow back
    to folder field ? 
    

All V3.0 forms which allow a user to select or create a document in a 
different drawer work in this way.  It was done for the reasons suggested 
in previous replies.  

The Folder field is only cleared when you tab forward from the Drawer 
field.  If you do want to select/create a document in a different drawer 
but with the same folder name then since the cursor is initially positioned 
on the Title field you can fill in the Title, tab backwards over the Folder 
field and then fill in the new Drawer name.


In V2.4 you could not tab backwards from the Folder field because there was
not a Drawer field on these forms.  We have added to these forms to handle
a new feature - Drawers.  You could argue that an addition is a change but
it's not quite the same as change without new features.

 
Richard

    Richard,
    
      I had explained all this to my customer (I am not the one arguing
    here) The customer does not look at it that way (added feature).
    I had explained about the DRAWER field but.... 
    Now it became an issue against DIGITAL. (I can't discuss it here).
    He's submitting an SPR.

    If the customer doesn't like it they can customize the form to make its
    behaviour different.  I fail to see why the customer is getting so
    upset about the whole thing.  Is there a hidden agenda?
    
    Tony

    
    	Hmmm. Submitting an SPR seems somewhat pointless as the code
    	is working how it was intended. I guess he could submit a
    	suggestion QAR and explain his beef. (I heard that we don't
    	get suggestion QARs in engineering so his QAR is certainly
    	not one I will loose sleep over missing).
    
    	Seems like someone should "filter out" the SPR at the earliest
    	possible opportunity to save Digital some money.
    
    	I, like Tony, don't see what all the fuss is about one line of
    	named data that can be customised out... By his own admission,
    	he only sees this when he mis-types anyhow.
    
    Regards,
    Paul

It sounds like the behavior is coded:

;;DRAWER;;

/post='get FOLDER = ""'

The customer could easily modify it to:

;;DRAWER;;

/pre='get #OLD_DRAWER = DRAWER'
/post='.if DRAWER nes #OLD_DRAWER then get FOLDER = ""'

This seems to yield the best of both worlds.  The folder won't change
unless the drawer is changed.  I would suggest that this might be a 
somewhat better solution for the base product as well, although I would
agree that it seems to be a big complaint about a minor inconvience.

When it's easy and has no potentially negative effects, why not fulfill 
the customers' most absurd requests?

Joe

    An explaination for the change.
    
    ALL-IN-1 V3.0 makes a major paradigm shift within the File Cabinet.
    Instead of a document-centered model, ALL-IN-1 now considers the
    cabinet to be a collection of drawers, local and remote, shared or
    private.  The change in emphasis and the introduction of functionality
    such as drawer access control and mail surrogacy means that all of the
    user interface has been reviewed, and many components changed to allow
    the drawer model to work effectively. 
    
    Users may find that these changes affect working habits, short-cuts, or
    UDPs. Customized versions of any form which deals with file cabinet
    objects are also likely to need changing. The new interface meets the
    needs of the majority of users, but perhaps not all. 
    
    However, as ALL-IN-1 is a customizable product, you can quickly
    customize the new forms to work in a manner that you believe is best,
    based on your experience or the needs of your organization.
    
    > End of explaination.
    
    You can provide this to your customer, together with Joe's code from
    .9, and see what they think. Or IOSG can use it in their SPR response.
    I really think the customer is making a large mountain out of a very
    small molehill.  
    
    Tony

    
     Here's a suggestion from the same customer.
     
 Extracted from IVP:

   The installation procedure for ALL-IN-1 V3.0 has now completed

   The IVP for ALL-IN-1 V3.0 takes about 30 minutes to run. This will
   vary according to the system that it is running on.

   It will first of all clear the VMS account name associated with the
ALL-IN-1 IVP account. Should the ivps fail to reset the VMS username in 
the PROFILE, then please reset it to the same as the MANAGER VMS username
as soon as possible, by doing the following:

$ALLIN1/NOINIT
 ENTER CMD:WRITE CHANGE PROFIL USER="IVP",VMSUSR="ALLIN1" 
                                                  ^^^^. 
    ______________________________________________________________________
    
    Same customer was asking if it's possible that in the next
    release "ALLIN1" must be substituted to whatever was provided during the 
    installation dialogue. In their case, ALLIN1 is not the VMSUSR.
    
      

I saw this same area of problem come up several times during a co-existent
installation, where references to account names, logical name tables and even
the "OA$MAIN.EXE" reference in A1LINK just sort of "forgetting" that my
installation environment was just a little different than the norm.

/Marty