DrawMGT - V11.6
Contents
Features
Description of end-user features, that we can explain to customers or put in our public web site.
Important New Features
- Transmittal improvements
- Transmittal cover sheet preview
- Transmittal cancel
- Improved recipient selection
- Recipients can be simple email addresses, DrawMGT users or named baskets (configurable)
- Transmittals have all classification fields
- Document workflow status and dates are saved at the time of the transmittal
- Reasons for transmittal can be entered and default texts can be configured
- Transmittal emails can be sent in one or in individual messages (configurable)
- Download key and cover letter can be sent in separate email (configurable)
- Planned response date introduced
- Keyword substitution in transmittal comment
- High Performance Uploader improved
Allow Drawings and Revisions update (see Settings-HPLoader.php updateDrawing and updateRevision)
Create eventLog record for all inserted/updated Drawings/Revisions records
Create summary eventLog record for all processed files
Set matureFlag, lockedFlag and supersededFlag in all effected Revisions
- Named basket can be created for all loaded document (configurable)
- Upload and error files can be saved in an archive directory
- Password handling improved
UserPwdChange Role introduced
- Ability to suppress password change email and to disable forcing pwd change on first login implemented
- Document search
- Search for 'latest revisions' implemented
- Ability to search for documents that have not (or yes) been produced
- Drawing Quick Search with configurable search fields
- New Task - Copy implemented
- Named basket can be sorted by externalKey'
- 'XHR file upload implemented in vendor portal for Chrome, FF4+, Safari5+ - this allows to see the upload progress
- Revisions contans project phase
- Additionally max 4 upload files can be used with configurable names
- Thumbnails (configurable)
- revision files (on Drawing/Detail and Transmittal/Detail)
- comment note attachments
WorkFlow DAAAAR implemented
Other Changes
Database Model Changes
Database Model Changes Associated With New Features
- Transmittals recipients are DrawMGT users and named baskets
New table SubmittalAddresses
Table SubmittalRecipients changed
Field userId renamed to recipientId
Field downloadKey moved from table SubmittalRecipients to SubmittalAddresses
Fields name, company and externalKey removed from SubmittalRecipients (not used),
- Transmittals has all classification fields
Classification fields added to table Submittals
- projectPhaseId
- workCategoryId
- documentTypeId
- categoryId
- locationId
- workTypeId
- siteClassification1Id
- siteClassification2Id
- siteClassification3Id
- siteClassification4Id
- Vendor Portal
- New tables:
GroupClassification
UploadedFiles
UploadedFileTypeRef
- New tables:
Other Database Model Changes
Field categoryId removed from table Groups (not used).
Migration Notes
- 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);
- 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.
SubmittalRecipients can contain Basket recipients (recipient lists). The new table SubmittalAddresses contains the download key from now on. It is migrated from SubmittalRecipients.
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 );
Configure GroupClassification and set Transmittal classifications
- Remove vendor role if not used in site migration script
DELETE FROM Roles WHERE roleId = 27;