I don’t think there is an out of the box method to do this, but you could have an equivalent New document attachment method created with a custom button to initiate the attachment function. Within this method, analyze per user which group they are in (would need to be only 1), then have a custom field related to the Person Group which sets a default document class per group.
OR
a much simpler solution is to remove the default document class so that it isn’t forced to the users and teach them to select the correct class, I would find it quite rare that each user only ever uses one document class. We did have to create a custom event based on a custom logical unit to prevent improper document class to object connections, but we’ve not seen the need to default each user to only one document class.
Hi,
I've been thinking of adding some feature to make the default document class config more flexible but we don't yet have anything that would do what you ask for.
May I ask why they think a more fine grained configuration would help them? Isn't it the content of the document that should determine which class to use? In Apps 10 we have a way to set a different class depending on what the object on the screen is.
If some users should not be creating documents of certain classes they can control that with basic data. A custom event could do it also, and even with greater flexibility.
I don’t think there is an out of the box method to do this, but you could have an equivalent New document attachment method created with a custom button to initiate the attachment function. Within this method, analyze per user which group they are in (would need to be only 1), then have a custom field related to the Person Group which sets a default document class per group.
OR
a much simpler solution is to remove the default document class so that it isn’t forced to the users and teach them to select the correct class, I would find it quite rare that each user only ever uses one document class. We did have to create a custom event based on a custom logical unit to prevent improper document class to object connections, but we’ve not seen the need to default each user to only one document class.
Thank you very Much. Issue sorted
@Nipun Gunaratne Which solution did you go for?