IBM SC34-4499-03 Personal Computer User Manual


 
3. Assess and implement any access control/authorization schemes necessary at this
level of implementation.
4. Open the newly initialized database.
5. Create test documents for testing.
6. Open features and defects if your database addresses these elements.
7. Determine whether existing (TeamConnection—supplied) documents,
subdocuments, and forms can be mapped into your organization’s terminology,
workflow, hierarchies, and state system.
8. Perform Customization setup, iteratively, to enact structural changes required by
your implementation. Customization enables you to address structural categories,
such as menus, document names and hierarchies, and workflow states.
See “Using the Customization setup facility” for a more detailed treatment of this
topic.
9. Assess and implement any access control/authorization schemes necessary at this
level of implementation.
10. Open the newly customized database.
11. Create test documents for testing.
12. Open features and defects if your database addresses these elements.
13. Validate as much as possible in your testing to determine the database’s
production readiness.
14. Delete all test documents, etc., and place the database in production status on a
Notes server. If you have used a test TeamConnection family to this point, it will be
necessary to specify the appropriate production family in the Customization setup.
15. Make the live database available to the appropriate user base.
Using the Customization setup facility
Use the Customization setup facility to customize the database design. Using
Customization, you can modify the default values that are provided. This requires
familiarity with the Lotus Notes environment.
Note: A Customization Wizard is available from the Setup window action bar to assist
you in customizing your database.
You can adjust or refresh values are for the following:
v Notes document names, titles, and subtitles.
v Structure of the Notes document hierarchy.
v States each Notes document may progress through.
v TeamConnection components and configurable fields information (refresh only).
v TeamConnection feature and defect attributes to store in Notes documents.
v Reconciliation of Notes and TeamConnection data.
122 User’s Guide