b-b-a / bba-power

1 stars 0 forks source link

Contract Reference - should be Tender Reference #234

Closed ghost closed 11 years ago

ghost commented 11 years ago

Seems that Contract Reference should be Tender Reference. Each tender has a reference that becomes the contract reference when it is used??

Need to move the Contract ref to the selected tender in the DB.

Move the field from the new/edit contract to the new/edit tender. Change the Contract display to use the Ref from the selected tender (similar to Contract Period:)

Also remove New Termination Doc: from new contract - the termination doc has to go on the old contract!!

paulmallett commented 11 years ago

I don't think it's always the case that a tender reference becomes the contract reference. I'd need to do more investigation to find it that's true, and if so for which suppliers.

ghost commented 11 years ago

OK - after investigation by Paul: Verry often the tender reference becomes a Contract Reference. So: plan is to add a field to the tender and copy it across at tender selected if the contract field is blank.

Shaun:
ALTER TABLE tender ADD tender_reference VARCHAR( 64 ) NOT NULL AFTER tender_idSupplierPersonnel

New field in Tender (Reference:) - please add to Tender Display and Tender Edit under "Supplier". Tenders Tab on Contract Display: Please add column "Reference" 160px after "Supplier". Remove col Phone. Make Supplier and SupplierLiason cols go to SupplierDisplay.

In the "Tender Selected" update processing: When a tender is selected (current test) - also add - if the new Contract Ref. is blank copy the selected tenders ref into the contract ref.. Mark the warning TRUE.

Change the Tender Selected User warning to include Contract Reference as a field that may have been changed.

paulmallett commented 11 years ago

I'm OK with this to go ahead

shaunfreeman commented 11 years ago

Yes I will get on to this Monday.

Sent from my iPad

On 27 Jan 2013, at 16:59, paulmallett notifications@github.com wrote:

I'm OK with this to go ahead

— Reply to this email directly or view it on GitHub.