We are looking for a programmer to develop the integration between MS Office/Open Office documents (word, excel, etc) and the application Enterprise Forms (http://www.longnhi.com/), which is a web based workflow engine written in C#. This integration should be done according to the following requirements:
1. In the application Enterprise Forms we have created the following 2 templates:
–> 1.1. Parameters, with the following mandatory fields, among others:
—-> 1.1.1. Document Type
—-> 1.1.2. Revision Number
—-> 1.1.3. Format for the content: Office/EF Form
—-> 1.1.4. MS Office/Open Office template (Word, Excel, …) with predefined fields
—-> 1.1.5. Users that can save the MS Office/Open Office document locally
–> 1.2. Document named “Test”, with the following fields, among others:
—-> 1.2.1. Document Type
—-> 1.2.2. Title
—-> 1.2.3. Control Number
—-> 1.2.4. Revision Number
—-> 1.2.5. Status
—-> 1.2.6. Date Created
—-> 1.2.7. Date Released
—-> 1.2.8. Author
—-> 1.2.9. Launch in Office (MS Office/Open Office template (Word, Excel, …))
—-> 1.2.10. Approvers
2. When creating ANY DOCUMENT in Enterprise Forms:
–> 2.1. The Enterprise Forms document must receive the Revision Number (point 1.1.2.) and the MS Office/Open Office template (point 1.1.4), both defined in the Parameters document correspondent to the document type being created (point 1.1.). And the status field must have the value “In Process”.
–> 2.2. The Enterprise Forms document must have a button named “Launch in Office” (that is shown only if the option defined in point 1.1.3. of the Parameters document correspondent to the document type of the EF document is Office) and when clicked must launch the MS Office/Open Office attachment mentioned in point 2.1. above. The MS Office/Open Office attachment must be launched in a new window with the corresponding application (word/excel, …) and the Enterprise Forms document from were it was launched must also stay open.
–> 2.3. The MS Office/Open Office attachment launched must inherit automatically and immediately all the values of the fields from the Enterprise Forms document. These inherited fields cannot be editable in the MS Office/Open Office document (cannot be changed by anyone).
–> 2.4. The author of the Enterprise Forms document completes the content of the MS Office/Open Office document and when he saves and closes the MS Office/Open Office document it must be stored/embedded in the field “Launch in Office” of the Enterprise Forms document from where it was created.
–> 2.5. The update of the fields must be done always from the Enterprise Forms document to the MS Office/Open Office document, never from the MS Office/Open Office document to the Enterprise Forms document.
–> 2.6. Users must not be able to close the Enterprise Forms document or the application if there is an MS Office/Open Office document open. If they try to do it they must receive a message saying “You must first close the corresponding Office document”
–> 2.7. After the MS Office/Open Office document is saved the first time, every time the “Launch in Office” button (that is shown only if the option defined in point 1.1.3. of the Parameters document correspondent to the document type of the EF document is “Office”) is clicked it must open the saved/ambedded MS Office/Open Office document and not the template from the parameters document anymore. The MS Office/Open Office document must always be opened in a new window with the corresponding application (word/excel, …) and the Enterprise Forms document from were it was launched must also stay opened.
–> 2.8. Every time there is a change/update in the fields of the Enterprise Forms document the correspondent fields in the MS Office/Open Office document embedded in it must also be automatically and immediately updated, so that the fields that are common between the Enterprise Forms document and the correspondent MS Office/Open Office document have always the same values.
–> 2.9. Every time the MS Office/Open Office document is saved and closed it must update/replace the MS Office/Open Office document previously stored/embedded on the Enterprise Forms document (in the field Launch in Office).
3. After completing both the MS Office/Open Office document and the Enterprise Forms document, the Enterprise Forms document will go through an approval cycle and when approved the status field will become “Released”.
4. On the Enterprise Forms documents with the status field with the value “Released” a “New Revision” button must be made available, which when clicked must make a copy of the complete Enterprise Forms document (including the MS Office/Open Office Document embedded), and this copy should become available for editing again with the status “In Process”. In this new copy the field Revision Number (point 1.2.4.) must be incremented by 1.
5. When an Enterprise Forms document with the status “Released”or a previous version of the same document with the status “Archived” are opened, if the option defined in point 1.1.3. of the Parameters document correspondent to the document type of the EF document is “Office”, the correspondent MS Office/Open Office Document should be automatically opened in read only mode (no one can change it or save it in the Enterprise Forms document nor locally) using a corresponding viewer, and the Enterprise Forms document from were it was launched must also stay opened.
–> 5.1. In this case, the “Launch in Office” button must also be available and if it is used it must open the MS Office/Open Office Document in read only mode (no one can change it or save it locally), using a corresponding viewer, and the Enterprise Forms document from were it was launched must also stay opened.
6. When an Enterprise Forms document with a status different then “Released” or “Archived” is opened, the MS Office/Open Office Document should not be opened automatically and the users can open it manually from the “Launch in Office” button if and when they want to.
–> 6.1. In this case, when clicking the “Launch in Office” button, if the Enterprise Forms document is new and the option “Format for the content” in the Parameters document is defined as “Office”(point 1.1.3.), the MS Office/Open Office attachment/template (point 1.1.4.) defined in the corresponding Parameters document is launched in a new window, using a corresponding viewer and the Enterprise Forms document from were it was launched must also stay opened. If the Enterprise Forms document is not new and the option “Format for the content” in the Parameters document is defined as “Office” (point 1.13.), the MS Office/Open Office document previously saved/embedded in the Enterprise Forms document is launched in a new window, using a corresponding viewer and the Enterprise Forms document from were it was launched must also stay opened.
–> 6.2. When opening the MS Office/Open Office document, if the user at that moment has permissions to edit the Enterprise Forms document, the MS Office/Open Office document must be opened in edit mode and the user can change it and save it in the Enterprise Forms document, but must not be able to save it locally (except if the user is defined in the field “Users/Roles that can save the MS Office/Open Office document locally” (point 1.1.5.) of the Parameters document correspondent to the Enterprise Forms document in question). If the user doesn’t have permission to edit the Enterprise Forms document, the MS Office/Open Office document must be opened in read only mode and the user cannot change it or save it on the Enterprise Forms document nor locally.
–> 6.3. In this case, the author of the Enterprise Forms document must have also the option to delete the MS Office/Open Office document that had been saved/embedded in the Enterprise Forms document or to replace the MS Office/Open Office document that had been saved/embedded in the Enterprise Forms document with the current MS Office/Open Office document attached in the correspondent Parameters document (point 1.1.4.).
–> 6.4. The “Launch in Office” button must be hidden if when opening the Enterprise Forms document, in the Parameters document (point 1.1.) corresponding to this document the option “Format for the content” is defined as “EF Form” (point 1.1.3.).
7. This integration between Enterprise Forms documents and MS Office/Open Office documents must be available for use with any Enterprise Forms document/template if in the option defined in point 1.1.3. of the Parameters document correspondent to the Enterprise Forms document/template the value selected is “Office”. If this integration is being used for a certain Enterprise Forms document/template and the user changes the Parameters Document not to use integration for this Enterprise Forms document/template any more, from that moment on, when creating Enterprise Forms documents of that type they must not have integration any more, but the Enterprise Forms documents of that type that were created before this change must continue having integration and continue having the MS Office/Open Office document that had been saved/embedded in the Enterprise Forms document.
Regards,
Filipa Sousa
The city pages must have 2 templates: 1) customary directory (with text below listings two levels of listing) and 2) an ad boxed text based page setting (where at the bottom there are text boxes which act as referral boxes)
