Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Prepend from parent: While selecting prepend from parent, the parent entity along with the parent field needs to be selected. Then the value of the field of the selected parent will be appended to beginning of the field value. The applicable parent will be the immediate parent. E.g. If we have Serie1 → Serie2 → Serie3, then parent for Serie3 will be Serie2

Lets assume that prepend from parent is checked and selected parent entity is A and field is b.

...

Move and regenerate means regenerating after a move. There is a button move in the crud list. After clicking the move button user has to select objects. After selecting a pop up tree will show up. Here two types of arrow buttons can be found. One is bordered arrow and another is unbordered arrow. Unboarded arrows are used for move and regeneration, while the bored ones are used for move. If the boar boarded arrow is used, the selected objects will go under that object. If the unboarded arrow is clicked, the selected objects will be put on between the gaps of the siblings. Then the regeneration will be imposed on the siblings from the starting offset to the ending offset. And the we already know that for regeneration we have to insert a starting value. Here in move and regenerate we need a starting value. Here we don’t need to insert a start value. The value of the object of the starting offset before the move will be considered the start value. And the start value needs to comply with the field value pattern. Otherwise there will be an error. If there are more than 1 FV pattern, the move and regenerate won’t work, as we can’t regenerate both since it depends on the ordering of the entities.

What are the effects on insert?

...

There will be no effect from backend on checking the uniqueness of the field value pattern.

Effects of updating the pattern with already existing entities

If there are already existing entities (e.g. 1, 2, 3). And we update the pattern to start from 7, the next created entity will be 4, not 7. This is because we first check if this is the existing pattern (in this case, both the patterns are similar - numeric) and then check the latest value and increment from there. If we instead update the preffix, suffix or the field length, then it will be an entirely new pattern, and the value will restart accordingly.

User preference, Global preference

Patterns can be user preference or global preference. If user preference is set for a field, the global preference will be ignored for that field.

If there is a global preference, and in user preference must have same parent flag is set, but the entity does not have same parent, the field should be left blank - the global will also not be effective here.