Integration between Enterprise Forms & MS Office/Open Office
Required skills: .NET, C#, C/C++, DotNetNuke
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/). 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
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
Posted In:C/C++.NETC#DotNetNuke |
Related projects:
Development Of Integration
rameters 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
Regards,
Filipa Sousa
Real Time Integration between Netsuite & Yahoo Store by rexie007
We have Netsuite as our accounting and order processing software and a Yahoo store as our store front. We need a programmer to do real time integration. Solution must be modular and expandable to allow for additional store fronts.
Must have Yahoo store & Netsuite knowledge. Please do not quote if you do not have previous experience with these platforms or better yet real time integration between the two.
Must have Yahoo store & Netsuite knowledge. Please do not quote if you do not have previous experience with these platforms or better yet real time integration between the two.
Nomadix XML PMS Integration
Need XML integration between webserver forms and Nomadix controller to facilitate integration between a Nomadix gateway controller and a hotel PMS interface. Have completed the XML forms. Now need assistance on XML commands to the Nomadix.
Nomadix XML PMS Integration
br />
Need XML integration between webserver forms and Nomadix controller to facilitate integration between a Nomadix gateway controller and a hotel PMS interface. Have completed the XML forms. Now need assistance on XML commands to the Nomadix.
Develope simple forms in MS Access
and the Projects details.
I have already created the tables for this applicaiton. I need someone to help me with the below
1. Designing the form layout and field validations
2. Getting the querry right
3. Add Macro actions to the forms
4. Add one derived field in the form. The derived field should be a combination of 3 other fields.
I have already created the tables for this applicaiton. I need someone to help me with the below
1. Designing the form layout and field validations
2. Getting the querry right
3. Add Macro actions to the forms
4. Add one derived field in the form. The derived field should be a combination of 3 other fields.
Integration between wp plugin cubepoints and Thumbsup
hi,
i need an integration between the wordpress plugin "cubepoints" and "thumbsup" into an existing wordpress website.
i need an integration between the wordpress plugin "cubepoints" and "thumbsup" into an existing wordpress website.
Integration between Flash Template and Flash CMS by Sunnlesaint
Integration between Flash CMS with admin panel and a Flash Template(from TemplateStore).
Flash CMS is done and web template purchased from templatemonster so is only required the integration between both parts.
I mean change the CMS template for the TemplateMonster one.
If work well done I will require the same project for many other websites.
Flash CMS is done and web template purchased from templatemonster so is only required the integration between both parts.
I mean change the CMS template for the TemplateMonster one.
If work well done I will require the same project for many other websites.
Development Of Integration
he attachment should be opened automatically in a new window, using a corresponding viewer
8.On the Approved Enterprise Forms documents a "New Revision" button should be available, which should make a copy of the complete document (including the attachment), and this copy should become available for editing again, with the status "In Process" and with the functionalities and workflow described in previous points. In this new copy the field Revision must be incremented by 1.
8.On the Approved Enterprise Forms documents a "New Revision" button should be available, which should make a copy of the complete document (including the attachment), and this copy should become available for editing again, with the status "In Process" and with the functionalities and workflow described in previous points. In this new copy the field Revision must be incremented by 1.
Development Of Integration
he attachment should be opened automatically in a new window, using a corresponding viewer
8.On the Approved Enterprise Forms documents a "New Revision" button should be available, which should make a copy of the complete document (including the attachment), and this copy should become available for editing again, with the status "In Process" and with the functionalities and workflow described in previous points. In this new copy the field Revision must be incremented by 1.
8.On the Approved Enterprise Forms documents a "New Revision" button should be available, which should make a copy of the complete document (including the attachment), and this copy should become available for editing again, with the status "In Process" and with the functionalities and workflow described in previous points. In this new copy the field Revision must be incremented by 1.
Ms Crm/rms/oa Integration
ducts involved. We cannot pay you to learn the technology and have made the mistake in the past of hiring someone who learned the technology as they went. We won't be repeating this mistake.
Don't care what technology you use as long as it works reliably (and isn't VB).
Strongly prefer past experience with integration solutions, especially if they have involved one of the 3 applications involved. Need strong communication skills and to be responsive to feedback.
Don't care what technology you use as long as it works reliably (and isn't VB).
Strongly prefer past experience with integration solutions, especially if they have involved one of the 3 applications involved. Need strong communication skills and to be responsive to feedback.
wordpress + vtiger + getresponse integration
we are looking for a developer to make a simple integration between the contact forms on our website (built on wordpress), our crm solution (vtiger) and our email marketing company (getresponse).
contacts sign at the website, their info is registered as leeds in vtiger and they are registered to our camping in getresponse.
all websites and info are in Hebrew, so we prefer someone with experience and knowledge about RTL development.
contacts sign at the website, their info is registered as leeds in vtiger and they are registered to our camping in getresponse.
all websites and info are in Hebrew, so we prefer someone with experience and knowledge about RTL development.
Integrating Open Source Apps
n available.
Impact on Our Technical Resources
Recommendations regarding needed technical resources are required. These include any needed system environment recommendations, networking recommendations, back-up and recovery recommendations, storage capacity recommendations, and bandwidth recommendations.
Glossary
<Please list any terms needing defined.>
Approvals
______________________________________________
Impact on Our Technical Resources
Recommendations regarding needed technical resources are required. These include any needed system environment recommendations, networking recommendations, back-up and recovery recommendations, storage capacity recommendations, and bandwidth recommendations.
Glossary
<Please list any terms needing defined.>
Approvals
______________________________________________
Jobsite and more-Forms & Database Integration by medstaff
Panel
Manage Member
mange the payment history
enable / disable member registration
Automated group notifications / emails to members / registration status /payment reminders etc
Online Payment set up.
I know these site specs may not be complete and nay suggestions are welcome. I have other two sites which are not included in
this price. This is my first time on this site. If i am satified, developer MAY get other projects as well.
Manage Member
mange the payment history
enable / disable member registration
Automated group notifications / emails to members / registration status /payment reminders etc
Online Payment set up.
I know these site specs may not be complete and nay suggestions are welcome. I have other two sites which are not included in
this price. This is my first time on this site. If i am satified, developer MAY get other projects as well.
Quick Paypal Integration Fix
oesn't change the newly formed account from 'inactive' to 'active' - I've been having to do it manually.
This PayPal integration problem is only an issue with new standard membership sign ups (?5 sign up fee). There have been no problems when customers place orders.
I think it is a small task and may just require a change of one or two lines of bugged coding so there is a small budget but I would like to get the problem solved as quickly as possible.
Thank you.
This PayPal integration problem is only an issue with new standard membership sign ups (?5 sign up fee). There have been no problems when customers place orders.
I think it is a small task and may just require a change of one or two lines of bugged coding so there is a small budget but I would like to get the problem solved as quickly as possible.
Thank you.
SharePoint HR
ant requests
&#61623; Creating and assigning learning programs
&#61623; Learning and Development reports
Compensations and Benefits
&#61623; Setting up compensation for job roles and positions
&#61623; Managing employee salaries, bonuses and allowances
&#61623; Creating and assigning learning programs
&#61623; Learning and Development reports
Compensations and Benefits
&#61623; Setting up compensation for job roles and positions
&#61623; Managing employee salaries, bonuses and allowances
Oracle Forms & Reports 11i - Development
d align=right style="padding-left: 20px; width: 320px">
Additional files submitted: (Files are only available for logged in users)
fdegrelle.docx
Additional files submitted: (Files are only available for logged in users)
fdegrelle.docx
E-bay Shipping Integration
ration='underline'" onmouseout="this.style.textDecoration='none'">VB.Net and delivered as source code.
I am open to changing requirement to meet specific needs for eBay. Successful completion of this project could lead to other project doing similar integration with other shopping cart and or order system both web based and pc based. We would be open to integration with any system where people are shipping valuable cargo. Shipping insurance is our main niche.
I am open to changing requirement to meet specific needs for eBay. Successful completion of this project could lead to other project doing similar integration with other shopping cart and or order system both web based and pc based. We would be open to integration with any system where people are shipping valuable cargo. Shipping insurance is our main niche.
Website With Social Media Section & Affiliate Capability
- ability to give each user a bar code and create a "fan club" type of service for mega users
26. Live Customer Service for Web Users
27. Interactive Press Kit: ability for media or potential clients to see press kit online and flip through it.
28. Affiliate Program - ability for others to sell tickets to our seminars on our behalf.
Aggressive bids will, of course, take preference.
Thank you for taking the time to read this post.
Chris
26. Live Customer Service for Web Users
27. Interactive Press Kit: ability for media or potential clients to see press kit online and flip through it.
28. Affiliate Program - ability for others to sell tickets to our seminars on our behalf.
Aggressive bids will, of course, take preference.
Thank you for taking the time to read this post.
Chris
Create a website with all the features like VRBO or HOMEAWAY
nd yahoo
Integrated html pages
admin needs to be able to reply and keep track of reservation requests, and confirmd bookings with automatic integration between pricing calculator and calendar
Internal site stats per apartment like impressions, clicks etc .....
Please adv relevant URLs (if possible with demo admin) of your work. Irrelevant portfolios will be ignored immediately.
Integrated html pages
admin needs to be able to reply and keep track of reservation requests, and confirmd bookings with automatic integration between pricing calculator and calendar
Internal site stats per apartment like impressions, clicks etc .....
Please adv relevant URLs (if possible with demo admin) of your work. Irrelevant portfolios will be ignored immediately.
Re-typing business forms into MS-Word
d.
Additional files submitted:
SvsAgrmentScan.pdf
Additional files submitted:
SvsAgrmentScan.pdf
