Challenge Overview
The Contracts Front End (CFE) application will be a central World Wide application that will provide for the editing/management of templates and creating documents from those templates. Current contract creation processes are manual and done thru local countries specialized custom tools or through MS Word documents. Since the Corporation is legally bound to the contents of the signed contract, the Corporation needs an application that standardizes these contract formats and ensures that the Legal department controls the contract wording. The Corporation has a strategic Document Generation system today; however, the current interface and the scope of future world wide user deployment requires a simple, easy to use, easy to deploy application that can interfaces into the strategic systems and provide for the editing and contract creation process. The Corporation also needs to provide the ability to create/maintain specialized paragraphs to be included in the document at document generation. The business objectives of this project are listed below. Delivering these objectives will deliver the expected benefits of the application.
- Standardize templates formats world wide
- Standardize creation of documents from templates
- Provide controlled method to change the templates
- Provide ability to determine which specialized template paragraphs to include in document
- Allow Legal Professionals (LPs) to make simple changes to templates with minimal screens and keystrokes.
- Allow LPs to add, create and update special paragraphs (Modifications) for use in both system, standard and one off templates in real time
- Allow the End Users to easily create documents based on standard or one off templates
- Provide a common tool for all countries and all documents
Eliminate need for promote process, where applicable, to allow simple document changes to get out quickly to the customers.
This component contains several struts action implementations, which manages modifications and tests. All struts actions extend BaseAction and delegate to backend services. The dependent services are injected by Spring after initialization of these actions.
ViewSentToTestSystemTemplateListAction class is called when user enters the “List of Templates” page.
SearchSentToTestSystemTemplatesAction class is called when user enters the “List of Templates Test Mode” page, and when the “Go” buttons are pressed.
ApproveTestTemplatesAction class is called when user presses the “Approve Test Version” button in the “List of Templates Test Mode” page.
ViewModificationListAction class is called when user enters the “List of Modifications” page.
SearchModificationsAction class is called when user enters the “List of Modifications” page, when the “Go” buttons are pressed, or a selection box is entered.
ViewCreateEditModificationPageAction class is called when user enters “Create/Edit Modification” page.
CreateModificationAction class is called when user wants to create new modifications in “Create Modification” page.
EditModificationAction class is called when user wants to edit an existing modification in “Edit Modification” page.
This component is running under Struts framework, which ensures that these actions run in a thread safe mode.
Final Submission Guidelines
http://apps.topcoder.com/wiki/display/docs/Contracts+Frontend+Documents