• DrawMGT116

DrawMGT - V11.6

Features

Description of end-user features, that we can explain to customers or put in our public web site.

Important New Features

1. Transmittals recipients are DreawMGT users and named baskets
2. Transmittals has all classification fields
3. Vendor portal

Other Changes

Database Model Changes

Database Model Changes Associated With New Features

1. Transmittals recipients are DrawMGT users and named baskets

   • Table SubmittalRecipients changed

     • Field userId renamed to recipientId

2. Transmittals has all classification fields

   • Classification fields added to table Submittals

     • projectPhaseId
     • workCategoryId
     • documentTypeId
     • categoryId
     • locationId
     • workTypeId
     • siteClassification1Id
     • siteClassification2Id
     • siteClassification3Id
     • siteClassification4Id
3. Vendor Portal
   • New tables:

     • GroupClassification

     • UploadedFiles

     • UploadedFileTypeRef

Other Database Model Changes

Migration Notes

1. Recipient Types added, use site specific migration if translation is needed

   INSERT INTO RecipientTypeRef VALUES (4,'TO_BASKET','To_Basket',null,'To_Basket',null);
   INSERT INTO RecipientTypeRef VALUES (5,'CC_BASKET','CC_Basket',null,'CC_Basket',null);
   INSERT INTO RecipientTypeRef VALUES (6,'BCC_BASKET','BCC_Basket',null,'BCC_Basket',null);

2. Transmittal email addresses are converted to userId
   • Cleaning up duplicates and performing the update implemented in app/schema/migrate/bin/migrate-db.sql.
   • List email addresses can not be converted (716 at IDP!!!), because no appropriate Users record found:

   select distinct replace ( substring( destination, instr( destination, '<' ) + 1 ), '>', '' )
     from SubmittalRecipients
     where recipientId is null 
     and replace ( substring( destination, instr( destination, '<' ) + 1 ), '>', '' )
         not in ( select email1 from Users )  order by 1;

   • Use cfg/idp/site/data/similar_emails.sql to find possible misstyped emails in SubmittalRecipients.

3. Add vendor contract in site migration script if Vendor Portal is used.(IDP example)

   insert into ContractRef values ( 1, 0, 'Vendor', 'Vendor Portal', null, 'Vendor', null, null );

4. Configure GroupClassification and set Transmittal classifications

5. Remove vendor role if not used in site migration script

   DELETE FROM Roles WHERE roleId = 27;

Development Notes