[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

575.0. "Hidden File Cabinets or Application File Cabinets" by SANFAN::LESLIE_DA (Greetings & Solutions) Mon Apr 27 1992 00:27

    My customer is contemplating using a shared file cabinet to house
    documents that are to be controlled by an application.  They don't want
    the shared cabinet to be selectable in WP or EM (or any other standard
    ALL-IN-1 document processing) by the users who will work on them (much
    less by users who don't have access).
    
    The idea is that the documents are available to the users only via the
    application.  Is this possible/do-able in ALL-IN-1 V3.0?  Any comments
    on the reasonable-ness of this request?
    
    The customer refers to this as "Hidden File Cabinets", maybe a better
    name would be "Application File Cabinets"?
    
    Thanks for the discussion that will (hopefully) take place...
Dan
T.RTitleUserPersonal
Name		DateLines
575.1ACLs?IOSG::TALLETTMaking broccoliMon Apr 27 1992 11:2512
	This sounds like a neat idea to me. Customers do come up with
	wonderful ways to use our products, don't they!?

	What form does your application take? Scripts? Code?
	Could you use some sort of file protection scheme so that
	the drawer was protected against access unless you were in
	the application? If the drawer were protected, you couldn't
	select it in WP or EM.

Regards,
Paul
575.2Same users of the document(s) in and out of the applicationSANFAN::LESLIE_DAGreetings & SolutionsWed Apr 29 1992 16:0729
    Thanks for your interest, Paul...
    
    Since the customer doesn't have a compiler (and I don't know MACRO) I
    believe I'll stick with the scripts and forms...
    
    The file protection scheme would probably have to entail granting and
    revoking an identifier on the fly.  The customer wants the user to have
    access via the "application", but NOT for WP and EM.  In other words
    we'd have to grant the identifier when they're in the "application" and
    revoke it when they leave (or something like that).  I don't think this
    is supported under VMS (but I have been shown wrong in this arena before ;*)
    
    I am unsure of where to implement this kind of thing anyway as I have
    only seen ALL-IN-1 v3.0 for a 3-day training class and the current
    system is ALL-IN-1 V2.3.
    
    The application would associate a document with a record in the
    dataset.  The customer likes the control and maintainability of
    application file cabinets, but they ONLY want the user to edit the
    document if they're getting there via the application.
    
    Hmm, maybe I can encrypt the document after it's edited (via the
    application) and decrypt it before editing (via the application).  Then
    if the user tries to access it outside of the application, they won't
    be able to...  Gee, this sounds like a lot more work than should be
    required!
    
    Thanks again for any interest...
Dan