Post

3 followers Follow
2

Profile attributes that depend on Type

 

Is it possible to set up a profile attribute that depends on the matter Type? (Type being the editable field that is part of every text attribute table)

 

 

For example:

 

Mater code 1234 is type ‘LIT’, and matter code 5678 is type ‘PROP’.

 

Can we set up a new attribute – let’s call it ‘Classification’ for now – so that when you profile a new document to matter 1234, you can choose from one list of Classifications (Court, Letter, Plea, Affidavit), and when you profile a new document to matter 5678, you get to choose from a different list of Classifications (Settlement, Deed, Agreement, Title) ?

Thanks

Status: None

Please sign in to leave a comment.

4 comments

2
Avatar

Peter,

There is a way you could pull this off. Create a "classification" attribute. Link it as a parent to another attribute, something like Document Type. Add the classification name to the Matter Type column, and default Classification from Matter Type on the attribute definition dialog. This way, when users upload new documents, when they choose matter 1234, it will default to the classification LIT, which then allows them to choose Document Types belonging to LIT, or if it defaulted to PROP, they would be able to choose Document Types related to PROP. I think this is what you are looking for. However, it would only really apply to new documents. When users re-profile existing documents, for example, the classification won't be defaulted based on matter. 

2 votes
0
Avatar

Thanks Russell. That works well.

I created a new Text attribute called ClasificationScheme, which defaults from Matter Type. I populated with it values that match existing matter types (e.g. PROP. LIT, etc.) I also made it read only, because I don't want users choosing a different scheme. And then I linked my Classification attribute as a child of the new attribute.

A bit round-about, but effective.

 

0 votes
0
Avatar

Peter, 

Adding the read-only component is possible, but this would prevent users from changing the classification field later, even if the matter is changed. Even without that, the "default from" feature only applies to new documents, or those documents where the classification field is empty. If it is already completed, it won't default based on the matter.  

0 votes
0
Avatar

I believe this would be achieved by the new "Dependent Attribute" type slated for release in 17.2 in response to one of our requests.

We have issues with the Matter Type not updating properly in the profile form when the end-user specifies a new Matter number.  To address this, the Matter Type would be defined as a "Dependent Attribute" to ensure that it keys off of the Matter number.

Currently, Matter Type will default based on the Matter number but will not update if the Matter number is adjusted once the value is initially set.

In your scenario today, you could make Classification default based on Matter Code, but it would only be set correctly at the onset of filling out the profile.  If the Matter Type was changed in the course of filling out the profile, the Classification values would not update accordingly.  This is important to understand in that the profile is often pre-populated based on what is selected in the save dialogue and/or how the save action was initiated.  As such, the frequency of needing to adjust values in the profile can be higher than you might expect.

0 votes