Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Object subtypes #119

Closed
openlowcode opened this issue May 13, 2020 · 0 comments
Closed

Data Object subtypes #119

openlowcode opened this issue May 13, 2020 · 0 comments

Comments

@openlowcode
Copy link
Owner

openlowcode commented May 13, 2020

In current system, Data Objects all have the same fields and properties. For example, a data object 'animal' would always have the same fields and properties.

The sub-type module will provide the following:

  • Data object will get a type (e.g. 'hyena', 'lion', 'spider' )
  • For each type, potentially, a sub data object (a list of fields and properties) will be attached. For examples, all mammals ( here 'hyena' and 'lion' ) may get the sub data object 'mammal', with information like length of gestation...
  • The sub-type and families are search criteria

For any screen when there is a single data object, or all data objects are of the same family, all fields are shown, including the fields of the sub-object.

For any screen where there can be data objects of different families, only the common fields and property display elements are shown.

When creating a new object, the type is chosen first, then the screen shows both the fields of the object and sub object.

It is possible to specify different business rules even for properties on the main data object. Typically, auto-numbering and auto-naming business rules can be specific per sub-object / family.

Non objectives:

  • Change of object type outside of a family.
  • Generally, other objects will link to the data object type (e.g. animal), not the subtype ( 'hyena' ) pr the family ( 'mammal' ). Restricting links to subtypes or families may be implemented in a further ticket.
openlowcode pushed a commit that referenced this issue May 17, 2020
Kept in the main branch as it has no side effect, but not usable yet
@openlowcode openlowcode added this to the Solved v2.0.0 milestone May 25, 2020
openlowcode pushed a commit that referenced this issue Oct 8, 2020
openlowcode pushed a commit that referenced this issue Oct 11, 2020
openlowcode pushed a commit that referenced this issue Oct 13, 2020
@openlowcode openlowcode reopened this Oct 14, 2020
openlowcode pushed a commit that referenced this issue Oct 14, 2020
Calling show page for companion when relevant. Basic display of
companion on show page
openlowcode pushed a commit that referenced this issue Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant