| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 2113.1 |  | TAMARA::CUMMINGS | Jerry Cummings, TeamLinks | Tue Apr 08 1997 09:17 | 6 | 
|  | I don't know for sure, but I doubt it. I don't recall
any changes in this area for V3. I might be wrong, so
hopefully someone more fluent in ALL-IN-1, user profiles,
and directory services will check into this.
Jerry
 | 
| 2113.2 |  | GIDDAY::JOYCE | Andy Joyce - Digital CSC Sydney | Sun Apr 20 1997 19:24 | 11 | 
|  |     
    Can someone check this out for me?
    I'd like to close this call with the customer if the problem
    is fixed in V3.0...
    
    Thanks,
    
    Andy
    CSC Sydney
    
    
 | 
| 2113.3 |  | TAMARA::CUMMINGS | Jerry Cummings, TeamLinks | Mon Apr 21 1997 04:54 | 3 | 
|  | I'll try to find someone to take a look at this.
Jerry
 | 
| 2113.4 | If no news is good news....Here is some news | XANADU::draft.zko.dec.com::manana::lawrence | TeamLinks Engineering, DTN 381-0747 | Mon Apr 21 1997 08:17 | 65 | 
|  | Andy, 
      I don't believe that it was ever the intention of the 
TeamLinks profile to update the server based profile. Perhaps this new 
functionality will be added to the OfficeServer. Currently the IPMT 
case and the PTR have been closed as this is not a bug but is in fact 
a request for new functionality. It is on the list of desireables but 
I do not know what kind of time frame. Access to the TeamLinks profile 
is part of the CFC API. I believe you have all of the tools you would 
need to write an application that would update the ALL-IN-1 profile. I 
am uncertain what access to the X.500 or DDS databases you would have 
from the PC. 
      I am pretty sure this is not the answer you were hoping for 
but at least now you don't have to wonder. I am sorry this 
functionality is not yet part of our product and I hope we can provide 
it soon. 
Cheers, 
jal
------------------------------------------------------------------------
-------
 V2.1-1 
Problem Report Display
Context is product TeamLinks Windows in domain EGP 
Problem report 11-3-33
Alternate name 1: TL_JAGUAR.00022
Abstract: CUSTOMER:PROFILE CHANGES DO NOT UPDATE DDS AS IS DONE ON VT 
CLIENT
Priority:     3
Severity:     HIGH      Status: CL        Resolution: US
Problem type: QAR       Origin: QAR       Workaround: No
Reproducible: No        Public: Yes       Waiting:    No
Active:       No
Owner responsible for resolution is TALLETT (TALLETT)
Assigned to current owner on 28-JUL-1995 00:00:00.00
Submitted on 28-JUL-1995 00:00:00.00
Submitted by PALMER (Rick Palmer)
Role of problem report creator: Administrator
Last modified on 21-FEB-1997 21:20:54.73
Last modified by CUMMINGS (Jerry Cummings)
Imported into database on 20-JAN-1997 10:52:11.98
Imported into database by ROYALTY (Dan Royalty)
Last answered on 21-FEB-1997 21:20:54.73
Last closed on   21-FEB-1997 21:20:54.73
Number of days open: 574
Number of days with last owner:  574
Number of days i
        .
        .
        .
---
   2: 21-FEB-1997 21:20  Answer by maintainer  CUMMINGS (Jerry 
Cummings)
      Remark: Closed per QRB
 | 
| 2113.5 |  | IOSG::CARLIN | Dick Carlin IOSG, Reading, England | Mon Apr 21 1997 10:03 | 14 | 
|  |     Just to add to what John has said (Hi John!):
    
    On the Teamlinks side I can't remember seeing any plans to update
    anything other than phonenumber in the server profile. As John says,
    the API to do it is there though.
    
    As far as updating DDS/X.500 is concerned, the directory interface part
    of the CFC API is read-only (search-only in fact) so the only way to do
    this would be to fire up a suitable script in the server, using the
    SUBSCRIBER or X500$ datasets.
    
    Cheers
    
    Dick
 | 
| 2113.6 |  | GIDDAY::JOYCE | Andy Joyce - Digital CSC Sydney | Tue Apr 22 1997 19:26 | 19 | 
|  |     
    re .-1
    
 >   As far as updating DDS/X.500 is concerned, the directory interface part
 >   of the CFC API is read-only (search-only in fact) so the only way to do
 >   this would be to fire up a suitable script in the server, using the
 >   SUBSCRIBER or X500$ datasets.
    
    Correct me if I'm wrong, but doesn't TeamLinks already have a mechanism
    for submitting a script to the script symbiont queue on the server -
    namely when a Read Receipt is issued?  If this is the case then I don't
    see it as a quantum leap to submit a DDS/X500 update script after a
    TeamLinks user has changed their profile details - so presumably it
    shouldn't be too hard a change for Engineering to make?  Or am I
    missing something?
    
    Andy
    CSC Sydney
    
 | 
| 2113.7 |  | AIMTEC::ZANIEWSKI_D | Add Jean to the list of deserters! | Wed Apr 23 1997 08:30 | 3 | 
|  |         Probably the only thing missing is funding.
        
        Dave Zaniewski
 | 
| 2113.8 | We're dancing as fast as we can. | XANADU::draft.zko.dec.com::manana::lawrence | TeamLinks Engineering, DTN 381-0747 | Wed Apr 23 1997 13:24 | 25 | 
|  | re .6
	I am not entirely sure what you are driving at. There are many 
requests for new functionality both simple and complex on TeamLinks as well 
as the servers it supports. I am not sure that there is much of it that 
would require a "quantum leap" to implement. I can certainly see how you 
might feel that our not implementing it is a symbol of how little we care 
about you and your customers problems. Let me assure you that it is not. If 
we could stop what we are doing right now and implement this we would. 
Unfortunately if we were to work that way we would not be having 9-12 
month release cycles. Our quality would suffer and our direction would be 
unclear. When a new release is planed it is decided what will be added in 
order to make the most efficient use of the available resource. We do not 
have a group of engineers waiting for new functionality requests to come 
in. It would be nice if we did. Your request has been added to the list of 
desired functionality for TeamLinks and will be given due consideration 
when it comes time to plan the next release which is going on even as we 
speak. I hope it makes it. If you were going to attempt to do this yourself 
I believe that the call to submit a script is available. If you are 
interested send me some mail and I can cobble up some documentation on the 
call. It is currently unsupported.
Cheers, 
jal
 
 | 
| 2113.9 |  | GIDDAY::JOYCE | Andy Joyce - Digital CSC Sydney | Wed Apr 23 1997 19:46 | 14 | 
|  |     re .-1
    
    jal,
    
    Sorry if you misunderstood me - I'm not having a go at you Engineering 
    folks, I'm just trying to anticipate what the customer (who has made being
    pedantic into an art-from) will say.  He considers (and I agree) that
    this is a bug which, on the face of it, can be fairly easily fixed.
    All I was after is "is it already fixed in V3.0?" and if the answer is no
    (which it appears to be) then I'll submit an IPMT case.
    
    Andy
    CSC Sydney
    
 | 
| 2113.10 | 1=yes,2=no,3=don't know ;-) | ATZIS1::EHRLICH_K | Never met a Lady like her before! | Thu Apr 24 1997 06:17 | 13 | 
|  |     Hi there Andy, 
    
    	it depends really on the customer view. For my customer (CoV)
    it's really ok, NOT having the possibility to change something in X.500
    (or DDS) using TeamLinks. NO NO NO. And if yes than make it 'optional'
    e.g. by setting a flag 'MAKECHANGES' = 1,2,3 ;-)
    
    So, you see, engineerings' life is hard enough (nowadays)!
    
    All the best,
    Cheers
    Charly 
     
 | 
| 2113.11 |  | AIMTEC::ZANIEWSKI_D | Add Jean to the list of deserters! | Thu Apr 24 1997 09:07 | 5 | 
|  |         If this is a customer, this is an excellent chance for a revenue
        opportunity.  This is exactly why ALL-IN-1 and TeamLinks were
        designed the way they are.
        
        Dave Zaniewski
 |