nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Can I have 10 same fileds in all my 6 custom Types

bisana

Hi
I am creating a demo for a real esstate company. They have around 30-40 folders, and the have 10 fileds to fill in.
Now the challenge for me is that, this 10 fileds are there in all the documents, but for different directories, some of the fields are mandatory and some not. When I had made the list I found that there are around 6 such comination. for eg for first folder, fiied 1,2,3 are mandatory and others not
For second folder field 3,4,5 are mandatory and other not, like this I have 6 combinations

Now in my mind, I plan to put the demo as follows, I will have 6 custom document types, where I define the field properties as mandatory or not.
If I do like this, 10 fileds will be in all six document types and will this repetation is allowed in Custom Type creation .
My ten Custom Type fields are

BuildingLocation CodeLease Start DateLease End DateCustomer NameShop NameCustomer NumberLease NumberIssue DateDocument DescriptionGuidance and Advice requested

Find more posts tagged with

Comments

mrogers

I suspect you may be better off modelling these as aspects. If something is optionally mandatory then that's a hint that the model is not quite right.

Without knowing too much about your requirement the following is only a rough sketch but it looks like your base type is building. You may want a leasable aspect To hold lease details. It sounds like you may have identified your other aspects as well.

bisana

Hi mrogers
Thanks for the advice.
I am bit not clear with

If something is optionally mandatory then that's a hint that the model is not quite right.

Also If do cusomt aspects, I have lots of codes going into share-config-custom.xml, I am trying to simplify, not sure what I think is a good idea
Thanks
Joseph John

mrogers

"if it's optional AND mandatory" then that's clearly nonsense. It may be indicating that there is something in your model that is not quite right.

On the other hand when stuff "just works properly" then it is a good sign that your model is correct.

bisana

Hi Mrogers
I underdstood, also I came to know that a filed cannot occur in more than one in Custom Aspect or Custom Type, ie I cannot define the same filed in more than one place. After lot of thinking I was not able to come up with a model. First I thought I will have different aspect with all the fields and we define which we want mandatory or not . This way of thinking did not work since the occurance of fiedls cannot be repeated.

I am thinking hard to create a model with fields, I am giving my needs here, so to get advice

(1) Building(2) Location Code(3) Lease Start Date(4) Lease End Date(5) Customer Name(6) Shop Name(7) Customer Number(8) Lease Number(9) Issue Date(10) Document DescriptionMyDM folders should have the following properties

Some folders have Field 1 and Field 9 to 10 MandatorySome folders have Fielf 1, Field 2, Field 9 , Field 10 MandatorySome folders have only Field 9, Field 10 mandatorySome folders have only Field 1 mandatory Some folders have all the field mandatoryI tried hard to design a model which will help me to full fill the above requirement.
It will be great if I could get advice

abarisone

Hi bisana,
in my experience I designed a model with all the custom types I needed applying the correspondant aspect to each.
Then, since I used a rich client application as a frontend, I put there the info about which field was mandatory or not.
You should never declare a property or aspect mandatory because it my lead to integrity issues.
Another approach would be to put a property file on the server side and with a Java backed webscript create your form getting properties and aspects from the model and applying a second layer of 'security' at this level scope in order to verify if your constraints have been satisfied.

Regards,
Andrea