This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
niota-docs:niota_formatting [2024/02/29 14:48] admin |
niota-docs:niota_formatting [2025/12/14 14:24] (current) admin |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| To enable grid formats and grid end user experience to your needs there is the database (based) grid edit format feature. Format of UI/grid edit pages is done on several levels and with different base objects. | To enable grid formats and grid end user experience to your needs there is the database (based) grid edit format feature. Format of UI/grid edit pages is done on several levels and with different base objects. | ||
| + | |||
| + | ==== format column collection ==== | ||
| + | A column collection is the most generic and fastest way to set user friendly formatting for table. Most of the settings from a column collection are applied dynamically on all columns with the same name of all tables where the value of "collection ID" matches between the table and and the collection entry. | ||
| + | |||
| + | {{:niota-docs:pasted:20251214-135356.png}} | ||
| + | |||
| + | ** Collection **\\ | ||
| + | ID of an collection to which this column definition is assigned. The setting is only applied if the value on table level for collection matches this value on column level. | ||
| + | By this you can have the same column name in different tables with a totally different meaning. | ||
| + | E.g. in a table that belongs to your financing system the column "workshop" means a company that repairs car. It's a local synonym for "repairshop". | ||
| + | |||
| + | But in your HR system then column "workshop" has the meaning of a meeting where you work together. If you put "workshop" in two different collections you can then assign to different descriptions to it. | ||
| + | |||
| + | On table level the collection is assigned here. | ||
| + | {{:niota-docs:pasted:20251214-140023.png}} | ||
| + | |||
| + | The default value for collection can be set in the system_defaults configuration file.\\ | ||
| + | |||
| + | -> define('CUSTOM_APPLICATION_CODE_DEFAULT', 'CUST'); | ||
| + | |||
| + | ** Columnname ** \\ | ||
| + | Physical name of the column on which this setting are applied. | ||
| + | |||
| + | ** activate **\\ | ||
| + | Active/inactive flag | ||
| + | |||
| + | ** Defaultvalue of column **\\ | ||
| + | |||
| + | ** Title of Column **\\ | ||
| + | Title of column in grid mode/form mode. In case also a semantic domain is assigned to this column, then the title is concatenated as domain title + column title. | ||
| + | |||
| + | ** Heading of Column **\\ | ||
| + | Text that is used for mouse over info. | ||
| + | |||
| + | ** Description Column **\\ | ||
| + | |||
| + | ** on/off read only **\\ | ||
| + | Flag to toggle read only property for columns with this name. Can be overwritten on level of the specific column of a table. | ||
| + | |||
| + | ** on/off hidden **\\ | ||
| + | Flag to toggle hidden property for columns with this name. Hidden means it's not visible in grid display format. Can be overwritten on level of the specific column of a table. | ||
| + | |||
| + | ** on/off hidden editable **\\ | ||
| + | Flag to toggle hidden editable property for columns with this name. If editable hidden is on, then hidden grid columns are visible in the edit form. Can be overwritten on level of the specific column of a table. | ||
| + | |||
| + | ** Domain ID Physical **\\ | ||
| + | Assign a physical domain to this column. | ||
| + | |||
| + | ** Domain ID Logical **\\ | ||
| + | Assign a logical domain to this column. | ||
| + | |||
| + | ** Domain ID Semantic **\\ | ||
| + | Assign a semantic domain to this column. | ||
| + | |||
| + | ** Lookup for Column **\\ | ||
| + | Assign a lookup definition to this column. This value is later ** copied ** to the column property setting of the table where a column with this name exists. This setting is not applied dynamically. | ||
| + | |||
| + | ** Constraint for Column **\\ | ||
| + | Assign a constraint definition to this column. This value is later ** copied ** to the column property setting of the table where a column with this name exists. This setting is not applied dynamically. | ||
| + | |||
| + | ** Security Token to apply **\\ | ||
| + | Assign a security token to this column. This value is later ** copied ** to the column property setting of the table where a column with this name exists. This setting is not applied dynamically. | ||
| + | |||
| + | ** RegEx to match **/**Regex not to match**\\ | ||
| + | The setting is only copied to columns where the column name matches the ''to match'' regular expression and not matches an optional regular expression in the ''not to match'' column. | ||
| + | By this you can define patterns where you want to apply the same column settings. E.g. you could here apply column setting for column ''Customer'' to all columns that begin with ''custom'' but not to column ''customize''. | ||
| + | |||
| ==== format object - logical domain ==== | ==== format object - logical domain ==== | ||