Data structures

all entities are stored and managed in uniform, generic structures thus, only a few methods are required for read and write operations the data structure is described below not all of the listed attributes are available in all interfaces each data set (hereinafter referred to as "genericdataelement") contains the following system fields attribute type description dataid guid unique key for each record mandatorid guid id of the mandator orgunitid guid id der organizational unit userid guid id of the allocated user for this record userdisplayname string displayname of the allocated user for this record entityid guid id of the entity entrytime datetime datetime of entry isactive boolean records are not deleted, they are set to inactive modifieddate datetime date of the last modification modifiedbyid guid id of the user who last modified the record modifiedby string display name of the user who last modified the record createddate datetime creationdate of the record createdbyid guid id of the user who created the record createdby string display name of the user who created the record triggerstamp datetime time of the last change (in the format yyyy mm ddthh\ mm\ ss ffk) displayvalue string descriptive text custom string field of custom data custom displayvalue string indicates a lookupproperty the field shows the displayproperty value of the entity referenced to the guid that is used in the field without " displayvalue" custommax string field of custom data (large fields) data attributes (properties) are also supplied with the system attributes depending on the interface, these are mapped with their configured name or with the generic name the generic names can be recognized by the naming convention "custom xxx" and are always supplied as string/nvarchar if the configured name is used, the attributes are also supplied in the configured data type in addition to the custom xxx values, "displayvalues" > custom xxx displayvalue are supplied displayvalues are the display values of lookups, e g in custom 001 there is a statusid, in custom 001 displayvalue there is "finished" as status text for interfaces that provide generic values, the mapping/casting of the data must be done in the application itself if you log in to the engine4 web interface, you can use the developer tools of the browser to understand how json objects are stored and received and how their content is structured debug mode the generic names "custom xxx" can be displayed by activating the debug settings in engine4 to do this, hold down ctrl and click on the little man in the top right and then select “debug settings” tick “show genericcolumnnames”, “showdataids”, “showviewids” and close the window this will display the generic name for each field in addition, the viewid, entityid and dataid of the data record are displayed in the header area of the window pressing ctrl again and clicking on the red man deactivates this mode alternatively, the entire page can be updated using f5 and the debug mode ends automatically