0
Answered

Project Template Restrictions!

Kenneth Larmer 1 year ago in Home Portal / Classic Projects updated by Jaime Zuniga 1 year ago 2

We have a particular client whose projects range from 10 languages to 28 languages, with the same vendors used in every scenario; therefore, the use of project templates should be exceptionally helpful. 

These projects starts in the “Quotes” module and then converted into a project when the client approves the quote. When approved, the template option is not available. The “Project Template” filed is not visible on the project form.


Can templates be applied to a project when the project is converted to a project or in the “Quotes” module? If not, is there another way of applying this replicated information (vendors, contacts, payables etc)?


This seems like a crazy restriction to me, especially for such a useful feature. Is there a way to enable this feature, otherwise templates are essentially useless for the vast majority of our projects!


Answer

Answer
Answered

Hi Kenneth

Classic templates are applicable only for projects. In the Product Development Ideas forum, there's already an Idea for such development. But I think you've already found that. 

I'd suggest supplementing that thread with a comment that it would be useful to add it also to the Client Portal.


In the meantime, I'd like to point out that in Home Portal any Project or Quote can be used as a template for the new Quote. For this, you can use the Duplicate or Duplicate as Quote option.

Answer
Answered

Hi Kenneth

Classic templates are applicable only for projects. In the Product Development Ideas forum, there's already an Idea for such development. But I think you've already found that. 

I'd suggest supplementing that thread with a comment that it would be useful to add it also to the Client Portal.


In the meantime, I'd like to point out that in Home Portal any Project or Quote can be used as a template for the new Quote. For this, you can use the Duplicate or Duplicate as Quote option.

Another way around this is to simply add preferred source and target language functionality. Client users could add their preferred languages to their profile and a button could be added to add them when creating new requests.