When creating new project types, base new project type on existing one
I have created 23 project types for a customer, primarily for filing purposes. However when I create each project type, I need to enable/disable document types per project type, even though they are going to be identical.
More problematic, is that due to number of document types required for the customer, in each project type, I need to configure the Show/Required for all the properties, for each document type, for every project type. This is 23 projects types, with 10 document types in each, all needing the same settings for Show/Require properties. This is a significant amount of effort resulting in 230 sets of Show/Require lists I need to configure in almost exactly the same way each time.
Ideally we should have an option to at least copy the properties setup between projects types and document types to speed up configuration and additionally reduce the chance of error.
-
Guest
- Mar 15 2021
- Will not implement
Related ideas
I have learned from Coen, that the above has been discussed, and the request is no longer necessary. Should this not be the case, feel free to add a new request.
Best regards,
Richard Waaijer
Attachments Open full size
The reason for the 23 project types is partially down to how they projects are named, and partially how the project types affects filing.
In a previous system, the customer had around 40 project types, and this has been reduced to 23 that they can work with. They have a lot of projects and therefore want to organise/group/file them in a sensible way and this is one of the drivers for the project types.
The next reason, is that they name their project using a project type code, a building number and a sequence number. e.g. MFG-04-0001 would be a manufacturing project for building 04. This project type code in the project name is important for them. The only way to get that project name format, is to use a project type to drive the code.
The alternative would be for them to create arbitrary project type codes, e.g. Standard Project with a code of STD, then use the project ID or project name field for the MFG type however then there is no control over the actual project types and the project would end up with a name of STD-MFG-04-0001.
Happy to discuss on a call if it helps.
Attachments Open full size
Hi Nick,
Thank you for your feedback. Can you elaborate a little bit more on your request? I would like to understand why you need 23 different Project Types?
Kind regards,
Coen Vromans
Attachments Open full size