Suljettu

Integration between Enterprise Forms & MS Office/Open Office

We are looking for a programmer to develop the integration between MS Office/Open Office documents (word, excel, etc) and the application Enterprise Forms ([url removed, login to view]). 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

Only one of the two options is allowed.

1.1.4. MS Office/Open Office template (Word, Excel, ...) with predefined fields

Only visible if the option selected in 1.1.3. is Office.

1.1.5. Users/Roles 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 a document of the type "Test" (point 1.2.) 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 Enterprise Forms 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 as properties in the MS Office/Open Office document (standard MS Office feature). In MS Office/Open Office one can insert the properties in the content, which means that the content from Enterprise Forms document is displayed on the MS Office 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.

The Enterprise Forms documents cannot have embedded more then one MS Office/Open Office document with this feature of complete integration between MS Office/Open Office documents and Enterprise Forms documents. The Enterprise Forms documents can have other MS Office/Open Office documents but only as attachments in other fields not related to this feature of integration.

2.5. Users cannot 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.6. 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 Enterprise Forms 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.7. 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.

The MS Office/Open Office document will have:

- the property fields, which are always updated with the content of the correspondent fields in the Enterprise Forms document and if the user had changed them in the MS Office/Open Office document they will still be updated. The users know that they should not change these fields else they can loose the changes made

- the content fields, which the user can change as they are not related to the Enterprise Forms document and so they can only be updated/changed by the users manually

2.8. 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.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"

This approval cycle is already build and it is not part of the requirements for this project.

4. On the Enterprise Forms documents of the type "Test" 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.

4.1. This copy routine described on point 4. (that makes a copy of the Enterprise Forms document) must be done in a way that we can easily copy and reuse ourselves for other templates/documents at any time.

5. When an Enterprise Forms document of the type "Test" 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 Enterprise Forms 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 of the type "Test" 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 of the type "Test" 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" and it must be done in a way that we can easily clone/copy and reuse ourselves for other templates/documents at any time.

7.1. If this integration is being used for a certain Type of Document of the Enterprise Forms document/template of the type "Test" and the user changes the Parameters Document not to use integration for this Type of Document of the 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.

8. Creation of a feature to easily and at any time import existing MS Office/Open Office documents saved on the hard disk into the Enterprise Forms documents with the integration features described on this project description.

9. This integration between Enterprise Forms documents and MS Office/Open Office documents must work with any MS Office version (at least MS Office 2000 or higher) and with any Open Office version (at least Open Office 3.0 or higher).

For this project we require high proficiency in DotNetNuke and ideally Enterprise Forms.

Our process is as follows:

1. Provide your experience with DotNetNuke, C# and Enterprise Forms, including work done and its complexity

2. After receiving the bids we do a pre-selection

3. If needed we will hold a conference call with the programmers on the shortlist to review the specifications

4. To begin the work we require a non disclosure agreement by registered email and weekly progress reporting with indication of the work that can be tested by us

5. Payments are 100% on Escrow, to be released up on the full testing and acceptance of the complete delivered work

6. Communications done via Skype and Email

7. The work is to be done on our installation/server via Remote Desktop

Taidot: .NET, C-ohjelmointi, C# -ohjelmointi, DotNetNuke

Näytä lisää: where are programmers, value options, user testing review, user specifications template, user requirements specifications template, use escrow to import, use case creation, type of use case, type of programmers, two way non disclosure agreement template, time complexity in c, time complexity, the open 2009, template for non disclosure agreement, standard non disclosure form, standard form non disclosure agreement, standard escrow agreement, standard agreement format, requirements specifications template, requirements specifications document, remote excel, receive payments with escrow, receive payments escrow, programmers we do, programmers on call

Tietoa työnantajasta:
( 1 arvostelu ) Pontevedra, Spain

Projektin tunnus: #515176

21 freelancers are bidding on average $2710 for this job

krishdts

please check PMB for details.

2000 $ USD 25 päivässä
(24 arvostelua)
7.8
varun8211

Pl see PMB.

2100 $ USD 25 päivässä
(5 arvostelua)
6.4
Maestros

plz chk PMB

3500 $ USD 40 päivässä
(8 arvostelua)
6.3
nsurani

We have passion & expertise to do the same within time & budget.

3000 $ USD 21 päivässä
(12 arvostelua)
5.5
sunztech

Please see PMB.

3000 $ USD 40 päivässä
(9 arvostelua)
5.4
Core100

Just payment terms are strange other wise we would like to work on this project, please check pmb. Regards, Tarun

5000 $ USD 60 päivässä
(4 arvostelua)
5.4
YashpalSingh123

Hello, Expert Computer Engineer, having experience in ASP.net, C# , Sql2005, Can Start Work on Immediately effect. Thanx

1500 $ USD 30 päivässä
(9 arvostelua)
4.8
khawaja83

I have more than 3+ years experience in web development in dotnet technologies including aspdotnet, ajax framework, dotnetnuke and mvc dotnet in both C# and Vb dotnet by using 2.0 and 3.5 framwork. I have worked in alm Lisää

3000 $ USD 45 päivässä
(5 arvostelua)
4.6
seospider

Please see PMB...

2500 $ USD 20 päivässä
(3 arvostelua)
3.7
bhuvantrivedi

Hello, It would be a pleasure to work on your project. Regards, John

2700 $ USD 30 päivässä
(0 arvostelua)
0.0
gateascent

Hi, We are a Team of MTech Graduates from IITs. IITs, are the Premier Institutes in India. We are sure, we can do this much better than any one else. Please Visit Our Website :: [url removed, login to view] Thanks, Lisää

3000 $ USD 100 päivässä
(0 arvostelua)
0.0
jarryhancy82

I have reviewed your requirement. i can do it. i am ready here. Thanks!

2500 $ USD 10 päivässä
(2 arvostelua)
0.0
aig

Let me know your Final Price and Final Time line for this project on PM , So we have Proposal / project Execution plan for your project . Waiting for your fast response on PM.

2500 $ USD 40 päivässä
(0 arvostelua)
4.5
legendaryjack

let me do your project, i am experienced.

1500 $ USD 10 päivässä
(0 arvostelua)
0.0
ManiksIndia

We possess extensive experience of developing numerous high-end websites and are highly organized and adept at meeting tight deadlines that are so common in this industry. Please check PMB for more details. ………….

3000 $ USD 45 päivässä
(0 arvostelua)
5.6
chmuimran

just need some work

2500 $ USD 50 päivässä
(0 arvostelua)
0.0
fgtpl

********************************************************************* WILL BE DONE *************************************************** ********************************************************************* PAYMENTS ON Lisää

4400 $ USD 44 päivässä
(0 arvostelua)
0.0
mysilversir

Hello, With 7 - 8 years experience I am doing good with C# and Vb.net and as back hand I use Ms-Access and mySql. I have good skill to communicate between office and .net, so I think we can do better work. If you po Lisää

2201 $ USD 65 päivässä
(0 arvostelua)
0.0
AtlantaWeb

Hi, We are Atlanta based Web Development Firm and interested in your project. we can offer a quality product with 100% [url removed, login to view] check your PMB for more details.

3500 $ USD 40 päivässä
(1 arvostelu)
0.0
fazalbhi

5 years of exp in .net windows [url removed, login to view] in getafreelancer and looking for a [url removed, login to view] you.

1500 $ USD 30 päivässä
(0 arvostelua)
0.0