https://wiki.tsnocode.dev/api.php?action=feedcontributions&feedformat=atom&user=NunTS NoCode wiki - User contributions [en]2026-04-11T20:40:00ZUser contributionsMediaWiki 1.37.0https://wiki.tsnocode.dev/index.php?title=Codeunit/Formevents&diff=7296Codeunit/Formevents2025-06-25T14:55:13Z<p>Nun: /* FILTER event hooks */</p>
<hr />
<div>Form events fires different actions during execution of a solution<br />
<br />
== Creating the codeunit ==<br />
# Make sure that '''p2eShared.jar''' is included in the project<br />
# Create a new class that extends<br />
<br />
com.tsnocode.codeunit.CodeunitFormevents<br />
<br />
== LIST level event hooks ==<br />
<br />
public String appendListPageHead() { return ""; }<br />
public String appendListPageFoot() { return ""; }<br />
<br />
public void beforeSelectList() throws Exception {} <br />
public void beforeRenderList() throws Exception {} <br />
<br />
<br />
==== LIST execution order ====<br />
# '''beforeSelectList'''<br />
# Gather form data from database<br />
#* '''dataFilterActive > dataFilterHandler'''<br />
#* '''listFilterActive > listFilterHandler'''<br />
# '''beforeRenderList'''<br />
# Return list to user<br />
<br />
== ITEM level event hooks ==<br />
<br />
public String appendItemPageHead() { return ""; } <br />
public String appendItemPageFoot() { return ""; } <br />
<br />
public void beforeSelectItem() throws Exception {} <br />
public void beforeChangeItem() throws Exception {}<br />
public void beforeUpdateItem() throws Exception {}<br />
public void beforeRenderItem() throws Exception {} <br />
public void afterUpdateItem() throws Exception { return false; }<br />
<br />
public boolean afterUpdateRedirectActive() { return false; }<br />
public String afterUpdateRedirectContent() { return null; }<br />
<br />
<br />
==== ITEM execution order: viewing data ====<br />
# '''beforeSelectItem'''<br />
# Gather form data from database<br />
#* '''dataFilterActive > dataFilterHandler'''<br />
#* '''itemFilterActive > itemFilterHandler'''<br />
# '''beforeRenderItem'''<br />
# Return form to user<br />
<br />
==== ITEM execution order: posting data ====<br />
# '''beforeSelectItem'''<br />
# Gather form data from database<br />
# '''beforeChangeItem'''<br />
# Update field values<br />
# '''beforeUpdateItem'''<br />
# Write changes to database<br />
# '''afterUpdateItem'''<br />
# if NO OTHER ACTION: <br />
#* '''afterUpdateRedirectActive'''<br />
#* if TRUE<br />
#** '''afterUpdateRedirectContent'''<br />
# Return content to user<br />
<br />
<br />
== FILTER event hooks ==<br />
Filters will help you build customized permission schemes. They are called for '''both''' LIST and ITEM commands.<br />
<br />
@Override<br />
protected boolean dataFilterActive() {<br />
return true;<br />
}<br />
@Override<br />
protected void dataFilterHandler(StringBuilder sql) {<br />
sql.append(" AND something");<br />
}<br />
<br />
In some cases you only want the filter to trigger for '''either''' LIST or ITEM commands<br />
<br />
itemFilterActive() {}<br />
itemFilterHandler(StringBuilder sql) {}<br />
<br />
listFilterActive() {}<br />
listFilterHandler(StringBuilder sql) {}<br />
<br />
=== Examples ===<br />
The xxxFilterActive tells if the filter is active<br />
<br />
boolean dataFilterActive() { return ! s.isAdministor(); }<br />
<br />
The xxxFilterHandler modifies the SQL used to fetch data<br />
<br />
void dataFilterHandler(StringBuilder sql) { sql.append(" AND CATEGORY NOT IN (123,456,789)"); }<br />
<br />
== Event firing details ==<br />
<br />
==== Event firing global ====<br />
The following events are ALLWAYS fired<br />
* beforeSelectList<br />
* beforeSelectItem<br />
* beforeChangeItem<br />
* beforeUpdateItem<br />
* afterUpdateItem<br />
<br />
==== Event firing in UI (reserved for normal users) ====<br />
The following events will NOT be fired during imports etc.<br />
* appendListPageHead<br />
* appendListPageFoot<br />
* beforeRenderList<br />
* appendItemPageHead<br />
* appendItemPageFoot<br />
* beforeRenderItem<br />
<br />
==== Event firing in UI depending on user actions ====<br />
The following events are SOMETIMES be fired for normal users depending on navigation<br />
* afterUpdateRedirectActive<br />
** Not executed in SUBFORM mode<br />
** Not executed in during imports etc.<br />
* afterUpdateRedirectContent<br />
** Depends on a TRUE result from afterUpdateRedirectActive()</div>Nunhttps://wiki.tsnocode.dev/index.php?title=JavaScript_functions_v1.0&diff=7295JavaScript functions v1.02025-06-25T14:50:07Z<p>Nun: /* Get and set values */</p>
<hr />
<div>&nbsp;<br />
= Code placement =<br />
The following places can contain JS code<br />
* Entity header<br />
* Entity status<br />
* JavaScript field<br />
<br />
Additionally HTML with inline script can be placed in<br />
* Wrapper<br />
* Template<br />
<br />
Finally expressions can be evaluated using<br />
* Entity field dependency<br />
<br />
&nbsp;<br />
<br />
= Builtin functions =<br />
The following functions are only available for single item views (edit or show).<br />
<br />
== Get and set values ==<br />
Display values are handled using standard getter and setters<br />
* '''getValue(fieldName) '''<br />
* '''setValue(fieldName,value) '''<br />
<br />
Example<br />
<br />
<syntaxhighlight lang="javascript"><br />
let a = getValue("NUMBER1");<br />
let b = getValue("NUMBER2");<br />
setValue( "RESULT", (a-b) );<br />
</syntaxhighlight><br />
<br />
For explicitly getting a value (or ID) use<br />
* '''getDecimal(fieldName)'''<br />
<br />
Example<br />
<br />
<syntaxhighlight lang="javascript"><br />
let recordId = getDecimal("SELECTRECORD");<br />
</syntaxhighlight><br />
<br />
For explicitly getting a datetime use<br />
* '''getFieldTime(fieldName)'''<br />
<br />
Example<br />
<br />
<syntaxhighlight lang="javascript"><br />
const time = new Date(getFieldTime('DEADLINE'));<br />
</syntaxhighlight><br />
<br />
== Toggling fields (5478+) ==<br />
Note: Hide functions are NOT intended for denying access to data -it will only be hidden in the frontend, but is still accessible to savvy users.<br />
<br />
Fields can be shown or hidden calling the fieldname<br />
* '''hideField(fieldName)'''<br />
* '''showField(fieldName)'''<br />
<br />
Examples<br />
<br />
<syntaxhighlight lang="javascript"><br />
hideField("USER");<br />
hideField("StatusID");<br />
</syntaxhighlight><br />
<br />
=== Dependent toggling ===<br />
<br />
Hiding and showing fields can be made dependent on classes in the TempusServaPage<br />
* '''hideFieldForPageClass(fieldName,className)'''<br />
* '''showFieldForPageClass(fieldName,className)'''<br />
<br />
Hiding and showing fields can be made dependent on items current status.<br />
* '''hideFieldForStatusId(fieldName,statusId)'''<br />
* '''showFieldForStatusId(fieldName,statusId)'''<br />
<br />
Hiding and showing fields can be made dependent on classes in the TempusServaPage AND items current status.<br />
* '''hideFieldForPageClassAndStatusId(fieldName,className,statusId)'''<br />
*'''showFieldForPageClassAndStatusId(fieldName,className,statusId)'''<br />
<br />
In case of advanced setup consider "hide for all first and show for some later".<br />
In this example NAME should only be displayed for a few status<br />
<br />
<syntaxhighlight lang="javascript"><br />
hideField("NAME"); <br />
showFieldForStatusId("NAME",1234);<br />
showFieldForStatusId("NAME",1235);<br />
</syntaxhighlight><br />
<br />
=== Disclaimer ===<br />
The functions are the equivilant of JQuery <br />
<br />
<syntaxhighlight lang="javascript"><br />
$("#VB_DATA_"+fieldName).parent().parent().hide();<br />
$("#VB_DATA_"+fieldName).parent().parent().hide();<br />
</syntaxhighlight><br />
<br />
This means that fields are expected to be wrapped in TWO layers of html tags for the functions to work<br />
<br />
== Toggling status ==<br />
A convenience method is planned for version 7800. Untill then you can use a Jquery expression.<br />
<br />
<syntaxhighlight lang="javascript"><br />
$("#DATA_StatusID option[value='123']").remove();<br />
</syntaxhighlight><br />
<br />
==Binding to events (6734+)==<br />
The platform sends out events when a couple of events are performed. Code can be written to bind to these.<br />
<br />
===Events=== <br />
<br />
*<code>hide-field</code>, triggered when the platform hides a field (dependency or hideField-function)<br />
*<code>show-field</code>, triggered when the platform shows a field (dependency or showField-function)<br />
<br />
===How to bind ===<br />
<syntaxhighlight lang="javascript"><br />
$("tr").bind("hide-field", function(e) {<br />
// Do stuff..<br />
})<br />
</syntaxhighlight><br />
<br />
==Value dependencies==<br />
Using lookup select boxes you can set up complex dependencies between values. The target field will be filtered when the page loads and on all changes to the filter field(s).<br />
<br />
===Single dependency===<br />
<syntaxhighlight lang="javascript"><br />
lookupValueFilterOnChange(fieldNameTarget, fieldNameSource, tripleArrayOfConditions);<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="javascript"><br />
var conditions = [<br />
[ TargetValue, SourceValue ... ],<br />
];<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="javascript"><br />
var conditions = [<br />
["Ding", "Foo"],<br />
["Dong", "Foo"],<br />
["Ding", "Bar"],<br />
];<br />
lookupValueFilterOnChange("LOOKUP", "FILTER", conditions);<br />
</syntaxhighlight><br />
<br />
In the above "Ding" and "Dong" will be available to select when FILTER = "Foo"<br />
<br />
===Double dependency===<br />
<syntaxhighlight lang="javascript"><br />
lookupValueFilterDoubleOnChange(fieldNameTarget, fieldNameSource1, fieldNameSource2, tripleArrayOfConditions);<br />
</syntaxhighlight><br />
<br />
<syntaxhighlight lang="javascript"><br />
var conditions = [<br />
["Ding", "Foo", "Cat"],<br />
["Dong", "Foo", "Dog"],<br />
["Ding", "Bar", "Cat"],<br />
["Dong", "Bar", "Fish"],<br />
];<br />
lookupValueFilterDoubleOnChange("LOOKUP", "FILTERA", "FILTERB", conditions);<br />
</syntaxhighlight><br />
<br />
In the above "Ding" will be available to select when either : <br />
*FILTERA = "Foo" -AND- FilterB = "Cat"<br />
*FILTERA = "Bar" -AND- FilterB = "Cat"<br />
<br />
==Value triggers==<br />
Value triggers will make things happen when a field changes. Multiple triggers can be assigned to the same field.<br />
<br />
*'''setValueOnChange(sourceName,targetName,targetValue)'''<br />
* '''setValueOnSetValue(sourceName,sourceValue,targetName,targetValue)'''<br />
<br />
Sets the value if another field is changed. Optionally only if a ceratain value is selected (sourceValue) <br />
<br />
<syntaxhighlight lang="javascript"><br />
setValueOnChange("CATEGORY","Silver","StatusID","Customer changed")<br />
</syntaxhighlight><br />
<br />
* '''warningOnChange(sourceName,message)'''<br />
*'''warningOnSetValue(sourceName,sourceValue,message)'''<br />
<br />
Display a warning to a user if another field is changed. Optionally only if a ceratain value is selected (sourceValue) <br />
&nbsp;<br />
<br />
<br />
==Value lookups==<br />
Value lookups will copy values from other records to the current one. The normal usecase is records referring other records via parent references.<br />
<br />
*'''getValueFromLookup(SourceSagID,SourceDataID,FieldNameSource)'''<br />
<br />
*'''setValueFromLookup(SourceSagID,SourceDataID,FieldNameSource,FieldNameTarget)'''<br />
<br />
The function will <br />
#Make a call to ?SagID=''[SagID]''&DataID=''[DataID]''&command=show<br />
#Pickup the value in the page at #VB_DATA_''[FieldNameSource]''<br />
#Insert the value in the local field ''FieldNameTarget''<br />
<br />
The DataID on the remote record can be picked up automatically by specifying FieldNameTrigger. Note this will only work as long as the trigger field is in editable and the value is changed.<br />
<br />
*'''setValueFromLookupTriggered(FieldNameTrigger,SourceSagID,FieldNameSource,FieldNameTarget)'''<br />
<br />
The function will <br />
#E´xtract the DataID form the field ''FieldNameTrigger''<br />
# Same as above<br />
<br />
== Named queries ==<br />
You can add peprared statements configurations and make paramterized class to them<br />
<br />
*'''lookupNamedQuery(query,value)'''<br />
<br />
The query executed in the backend, must be stored under the configuration named: "NamedQueryLookup." + query<br />
<br />
The value will be inserted into the ? parameter an escaped properly<br />
<br />
SELECT CVR FROM data_company WHERE NAME = ?<br />
<br />
If call is made from an entity the Query will be stored in either<br />
* Entity configuration (if SagID on caller page is present in URL)<br />
* System configuration<br />
<br />
=== Example ===<br />
In the following example we want to look up a phone number from an email value in the entity 'company'.<br />
<br />
==== Client code ====<br />
Somewhere in a Javascript the following code is found<br />
<br />
var email = getValue("EMAIL");<br />
setValue( "PHONE",<br />
'''lookupNamedQuery("FindPhoneFromEmail",email)'''<br />
)<br />
<br />
==== Server code ====<br />
In the configuration '''NamedQueryLookup.FindPhoneFromEmail''' the following SQL is stored<br />
<br />
SELECT COMPANYPHONE FROM data_company WHERE COMPANYEMAIL = ?<br />
<br />
==Inspect command and users==<br />
The currect command can be examined using<br />
*'''isCommandNew()'''<br />
*'''isCommandEdit()'''<br />
*'''isCommandList()'''<br />
<br />
Note that commands are allways added as a class to the #TempusServaPage element<br />
<syntaxhighlight lang="javascript"><br />
<div id="TempusServaPage" class="TempusServaPage listCommand da_DK"><br />
</syntaxhighlight><br />
<br />
User types can be determined using<br />
<br />
* '''isUserAdmin()'''<br />
*'''isUserExternal()'''<br />
*'''isUserNormal()'''<br />
* '''isUserExclusive()''' (from version 6248)<br />
<br />
Note that special roles are allways added as a class to the #TempusServaPage element<br />
<syntaxhighlight lang="javascript"><br />
<div id="TempusServaPage" class="TempusServaPage IsAdministrator listCommand da_DK"><br />
</syntaxhighlight><br />
<br />
This allows for custom CSS for special roles<br />
<syntaxhighlight lang="css"><br />
.IsAdministrator h1 { color: red; }<br />
</syntaxhighlight><br />
<br />
==Other functions==<br />
<br />
=== selectSingleOption(fieldName) ===<br />
Will set a value if only one option is avaiable in a select box.<br />
<br />
=== warnDateAfterOtherDate( dateA, dateZ, message ) ===<br />
Alerts the user via a popup, if two dates are not after each other. Both date changes triggers the test.<br />
<br />
=== disableErrorCountInTitle() and enableErrorCountInTitle() (6734+) ===<br />
Will disable/enable displaying of numbers of errors i the page-title. Default is enabled<br />
<br />
=== changeFieldToShow(fieldName) ===<br />
Remove input and select boxes and replace them with the value in the field<br />
<br />
=== showMoreTableRows(fieldName,rowsShown,buttonLabel) ===<br />
Makes a nested table shorter by hiding lines > rowsShown. Hidden rows can be shown with the button below the table.<br />
<br />
=Control variables=<br />
TS uses a number of special variables to control the behavior of the frontend. These variables can be changed anywhere.<br />
<br />
===Opening new windows===<br />
Window default sizes are controlled by the following variables<br />
*'''tsOpenWindowHeight''' = 680;<br />
*'''tsOpenWindowWidth''' = 820;<br />
&nbsp;<br />
<br />
===Dependency hiding fields ===<br />
'''hideTableRowsForElements''' is by default true. <br />
<br />
Set to false if template structure is only in a single level.<br />
*true: Hide two parent nodes when hiding fields<br />
*false: Hide single parent node when hiding fields<br />
<br />
Example of 2 level template (default)<br />
<br />
<syntaxhighlight lang="html5"><br />
<tr><br />
<td><br />
<input ..<br />
</syntaxhighlight><br />
<br />
Example of 1 level template (special cases)<br />
<br />
<syntaxhighlight lang="html5"><br />
<div><br />
<input ..<br />
</syntaxhighlight><br />
<br />
&nbsp;<br />
<br />
=Other sources=<br />
<br />
*[[JQUERY / SCRIPT CHEATSHEET| Readonly radiobuttons, copy text in field, build selectbox from service ...]]<br />
*[[HACKING DEPENDENT VALUES| Handling dependent lookup values (showing all elements etc.)]]</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Developing_codeunits&diff=7264Developing codeunits2025-04-08T12:47:24Z<p>Nun: uddybning af beskrivelser og stavevejl.</p>
<hr />
<div>== Steps for creating a new codeunit ==<br />
<br />
# Create a new Java project in your favorite IDE<br />
# Import the p2eShared.jar in the project<br />
# Create a new class:<br />
## The abstract parts are found in: dk.p2e.blanket.codeunit<br />
## Implement all abstract methods<br />
## Code the method bodies (normally "execute")<br />
# Compile and build<br />
# Deploy to webservser: [Application]\WEB-INF\lib<br />
<br />
After first test of the codeunit a server reboot is needed for each redeployment, as there is no way of removing the loaded classes from memory.<br />
<br />
== Error handling ==<br />
<br />
Exceptions are handled by themselves using the errorRegistration(Exception e) method.<br />
<br />
In case the errors are not caught by the codeunit itself, the generic error handler takes over<br />
# Logs the error in the eventlog<br />
# Returns a standard error page to the user<br />
<br />
Other debugging options include log4j and specialized TempusServa '''Systemout.print''' functions (yes, the class name is "Systemout").<syntaxhighlight lang="java"><br />
Systemout.println("hello world");<br />
Systemout.printSql(myStatment);<br />
</syntaxhighlight><br />
<br />
== Configuration / parameters ==<br />
<br />
Parameters are delivered through the method call, packed in a nice <String> Hashtable for easy access.<br />
<br />
Please note that values are sent as-is, so make sure to escape values before DB operations using <syntaxhighlight lang="java"><br />
DbConnection.escapeSql(String s);<br />
</syntaxhighlight>Configurations can be stored using the getConfiguration methods of the command object. These values can be editedthrough the designer, depending on the Codeunit type<br />
<br />
* System configurations: Designer > Modules > Static content<br />
* Solution configurations: Designer > [Solution] > Advanced > Configurations <br />
<br />
Value names will be prefixed with Class simple name - example + "."<br />
<br />
com'''.tsnocode.MyExampleCodeunit.'''myParameter<br />
<br />
== Variables ==<br />
<br />
Variables can have a scope of either <br />
* Request<br />
* User session<br />
* Application<br />
<br />
For permanent variables user server configurations.<br />
<br />
=== Request variables ===<br />
Request scope variables should be stored in the Hashtable '''sharedObjects''' in the '''Command''' object.<br />
<br />
Note that the HTTP request parameters are stored in '''requestParameters'''.<br />
<br />
=== User session variables ===<br />
Acces the '''sessionValues''' attribute in the '''Security''' object<br />
* boolean hasSessionValue(String name)<br />
* void setSessionValue(String name, boolean value)<br />
* int getSessionInteger(String name, int defaultValue)<br />
* int getSessionInteger(String name)<br />
* void setSessionInteger(String name, int value)<br />
* String getSessionString(String name, String defaultValue)<br />
* String getSessionString(String name)<br />
* void setSessionString(String name, String value)<br />
<br />
All variables her are serilizable and will survive server restarts.<br />
<br />
Certain special user properties can also be accessed from the '''Security''' object<br />
* boolean hasProperty(String name) <br />
* String getProperty(String name)<br />
<br />
Finally it is possible to store objects in the Hashtable '''sessionObjects''' in the '''Security''' object, but be aware that data are transient and '''will not survive server restarts'''.<br />
<br />
=== Application variables ===<br />
Application variables are persistent and accessed through the '''Command''' object<br />
<br />
Their storage position depends on wether theres is a solution context or not:<br />
* Solution present: Variables are saved to the solution '''Configurations'''<br />
* None (SagID = 0): Variables are saved to the '''Static content'''<br />
<br />
Access the the variables goes through get methods with default values.<br />
* String getConfigurationValue(String name)<br />
* String getConfigurationValue(String name, String defaultValue)<br />
<br />
If the variable does not exist it will be created, and set to the default value (if present).<br />
<br />
Note that it is possible to force the use of Statis content by explicitly calling <br />
* String getSystemConfigurationValue(String name)<br />
* String getSystemConfigurationValue(String name, String defaultValue)<br />
<br />
== Different codeunit types ==<br />
<br />
Please read the: [[Codeunit reference]]<br />
<br />
Most likely you will need to create a [[Codeunit/Formevents]] that will allow specific changes for a solution, during views, updates or exports.<br />
<br />
Most interactions wil require interaction with the following objects<br />
* Security<br />
* Command<br />
* DbConnection<br />
* EventHandler<br />
<br />
== Using the provided Dev-image ==<br />
We provide a ready-to-go image of a virtual machine, running Debian 12, for [https://www.virtualbox.org/wiki/Downloads VirtualBox].<br />
<br />
The machine is set up with all the required software and helper scripts, to enable development of custom codeunits.<br />
<br />
=== Getting the image running ===<br />
The image is buildt for VirtualBox, so install that.<br />
<br />
Once you have the image downloaded, start the import wizard in VirtualBox (ctrl + i) and follow it.<br />
<br />
Now you should be able to boot the VM. The username and password for the user is noted in the comment on the VM.<br />
<br />
The machine includes the following programs:<br />
<br />
* Firefox, to access the local Tomcat server<br />
* NetBeans 11.3, to develop codeunits<br />
* DBeaver CE 24, to access the local DB<br />
<br />
=== Deploying codeunits ===<br />
To deploy your code to the local Tomcat instance do the following:<br />
<br />
# Open Netbeans<br />
#Build the project (right-click the project in the project-browser on the left and select build)<br />
# Copy the generated .jar file from <code>/home/developer/NetBeansProjects/[ApplicationName]/dist</code> to <code>/mnt/sda/deploy</code><br />
# Clear the cache (open http://localhost:8080/app/service?CacheClear) or go back to the app in firefox and select Administrator -> Services -> Cache control -> Cache clear<br />
<br />
=== Debugging codeunits ===<br />
Attach the NetBeans debugger to the local Tomat server:<br />
<br />
Click "debug" in the top-left menu -> click "attach debugger" -> click "OK", the default settings should work<br />
<br />
Add a breakpoint to your code by selecting the line number and try to invoke it from the browser.<br />
<br />
=== Updating the API and platform ===<br />
To update the local environment to the latest version of the TS-API and TS Platform, open a terminal and execute the following commands.<syntaxhighlight lang="bash"><br />
updateAPI<br />
ts -w app upgrade-alphaapp<br />
</syntaxhighlight>You will be prompted to input the password for the user.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=How_to_use_DumpFilesToDiscCLI&diff=6785How to use DumpFilesToDiscCLI2024-02-12T10:49:20Z<p>Nun: updated for running non-localhost</p>
<hr />
<div>DumpFilesToDiscCLI is a tool to run the DumpFilesToDisc codeunit directly from a Command Line Interface such as Windows Powershell. To run the command, you must have JDK 1.8 (Or probably newer) installed and set up. You must also have access to the database server you are connecting to in the case that you are not running from localhost. From here you must do the following steps:<br />
<br />
# Get war file from www.tempusserva.dk/install/nightly/TempusServa.war<br />
# Rename file ending to .zip<br />
# Unzip the file<br />
# Navigate to \TempusServa\WEB-INF\lib in zip file in a CLI such as Powershell<br />
# Run the following command, but replace the placeholder variables, including the <> characters with appropriate values for the given application you are running the tool on:<br />
<br />
java -cp "./*" com.tsnocode.codeunit.common.DumpFilesToDiscCLI <live db name> <db username> <db password> <Database server IP Address> <entity db name> <category field db name *optional*> <category entity db name *optional*><br />
<br />
Notice that all names must be the database names, not the front-end names. The database names of entities and fields can be found in the back-end in parentheses on the given entity. Depending on the number of files to be dumped, this tool may take a little while to run.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=How_to_use_DumpFilesToDiscCLI&diff=6753How to use DumpFilesToDiscCLI2024-02-06T14:24:29Z<p>Nun: </p>
<hr />
<div>DumpFilesToDiscCLI is a tool to run the DumpFilesToDisc codeunit directly from a Command Line Interface such as Windows Powershell. To run the command, you must have JDK 1.8 (Or probably newer) installed and set up. From here you must do the following steps:<br />
<br />
# Get war file from www.tempusserva.dk/install/nightly/TempusServa.war<br />
# Rename file ending to .zip<br />
# Unzip the file<br />
# Navigate to \TempusServa\WEB-INF\lib in zip file in a CLI such as Powershell<br />
# Run the following command, but replace the placeholder variables, including the <> characters with appropriate values for the given application you are running the tool on:<br />
<br />
java -cp "./*" com.tsnocode.codeunit.common.DumpFilesToDiscCLI <live db name> <db username> <db password> <entity db name> <category field db name *optional*> <category entity db name *optional*><br />
<br />
Notice that all names must be the database names, not the front-end names. The database names of entities and fields can be found in the back-end in parentheses on the given entity. Depending on the number of files to be dumped, this tool may take a little while to run.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=How_to_use_DumpFilesToDiscCLI&diff=6752How to use DumpFilesToDiscCLI2024-02-06T09:15:06Z<p>Nun: </p>
<hr />
<div>DumpFilesToDiscCLI is a tool to run the DumpFilesToDisc codeunit directly from a Command Line Interface such as Windows Powershell. To run the command, you must have JDK 1.8 (Or probably newer) installed and set up. From here you must do the following steps:<br />
<br />
# Get war file from www.tempusserva.dk/install/nightly/TempusServa.war<br />
# Rename file ending to .zip<br />
# Unzip the file<br />
# Navigate to \TempusServa\WEB-INF\lib in zip file in a CLI such as Powershell<br />
# Run the following command, but replace the placeholder variables, including the <> characters with appropriate values for the given application you are running the tool on:<br />
<br />
java -cp "./*" com.tsnocode.codeunit.common.DumpFilesToDiscCLI <live db name> <db username> <db password> <entity db name> <category field db name *optional*> <category entity db name *optional*><br />
<br />
Notice that all names must be the database names, not the front-end names. The database names of entities and fields can be found in the back-end in parentheses on the given entity. Depending on the number of files to be dumped, this tool may take a long time to run.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=How_to_use_DumpFilesToDiscCLI&diff=6751How to use DumpFilesToDiscCLI2024-02-06T09:14:00Z<p>Nun: </p>
<hr />
<div>DumpFilesToDiscCLI is a tool to run the DumpFilesToDisc codeunit directly from a Command Line Interface such as Windows Powershell. To run the command, you must have JDK 1.8 (Or probably newer) installed and set up. From here you must do the following steps:<br />
<br />
# Get war file from www.tempusserva.dk/install/nightly/TempusServa.war<br />
# Rename file ending to .zip<br />
# Unzip the file<br />
# Navigate to \TempusServa\WEB-INF\lib in zip file in a CLI such as Powershell<br />
# Run the following command, but replace the placeholder variables, including the <> characters with appropriate values for the given application you are running the tool on:<br />
<br />
java -cp "./*" com.tsnocode.codeunit.common.DumpFilesToDiscCLI <live db name> <db username> <db password> <entity db name> <category field db name *optional*> <category entity db name *optional*><br />
<br />
Notice that all names must be the database names, not the front-end names. The database names of entities and fields can be found in the back-end in parentheses on the given entity.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=How_to_use_DumpFilesToDiscCLI&diff=6750How to use DumpFilesToDiscCLI2024-02-06T08:16:53Z<p>Nun: </p>
<hr />
<div>DumpFilesToDiscCLI is a tool to run the DumpFilesToDisc codeunit directly from a Command Line Interface such as Windows Powershell. To run the command, you must have JDK 1.8 (Or probably newer) installed and set up. From here you must do the following steps:<br />
<br />
# Get war file from www.tempusserva.dk/install/nightly/TempusServa.war<br />
# Rename file ending to .zip<br />
# Unzip the file<br />
# Navigate to \TempusServa\WEB-INF\lib in zip file in a CLI such as Powershell<br />
# Run the following command, but replace the placeholder variables, including the <> characters with appropriate values for the given application you are running the tool on:<br />
<br />
java -cp "./*" com.tsnocode.codeunit.common.DumpFilesToDiscCLI <live db name> <db username> <db password> <solution> <categoryField *optional*> <categoryEntity *optional*></div>Nunhttps://wiki.tsnocode.dev/index.php?title=How_to_use_DumpFilesToDiscCLI&diff=6749How to use DumpFilesToDiscCLI2024-02-05T14:35:32Z<p>Nun: prettier</p>
<hr />
<div>DumpFilesToDiscCLI is a tool to run the DumpFilesToDisc codeunit directly from a Command Line Interface such as Windows Powershell. To run the command, you must have JDK 1.8 (Or probably newer) installed and set up. From here you must do the following steps:<br />
<br />
# Get war file with www.tempusserva.dk/install/nightly/TempusServa.war<br />
# Rename file ending to .zip<br />
# Unzip the file<br />
# Navigate to \TempusServa\WEB-INF\lib in zip file in a CLI such as Powershell<br />
# Run the following command, but replace the placeholder variables, including the <> characters with appropriate values for the given application you are running the tool on:<br />
<br />
java -cp "./*" com.tsnocode.codeunit.common.DumpFilesToDiscCLI <live db name> <db username> <db password> <solution> <sqlCategoryKey *optional*> <sqlCategoryEntity *optional*></div>Nunhttps://wiki.tsnocode.dev/index.php?title=How_to_use_DumpFilesToDiscCLI&diff=6748How to use DumpFilesToDiscCLI2024-02-05T14:31:29Z<p>Nun: Created page with "DumpFilesToDiscCLI is a tool to run the DumpFilesToDisc codeunit directly from a Command Line Interface such as Windows Powershell. To run the command, you must have JDK 1.8 (Or probably newer) installed and set up. From here you must do the following steps: 1. get war file with www.tempusserva.dk/install/nightly/TempusServa.war 2. rename file ending to .zip 3. unzip the file 4. navigate to \TempusServa\WEB-INF\lib in zip file in a CLI 5. run the following command, but..."</p>
<hr />
<div>DumpFilesToDiscCLI is a tool to run the DumpFilesToDisc codeunit directly from a Command Line Interface such as Windows Powershell. To run the command, you must have JDK 1.8 (Or probably newer) installed and set up. From here you must do the following steps:<br />
<br />
1. get war file with www.tempusserva.dk/install/nightly/TempusServa.war<br />
2. rename file ending to .zip<br />
3. unzip the file<br />
4. navigate to \TempusServa\WEB-INF\lib in zip file in a CLI<br />
5. run the following command, but replace the placeholder variables, including the <> characters with appropriate values for the given application you are running the tool on:<br />
java -cp "./*" com.tsnocode.codeunit.common.DumpFilesToDiscCLI <live db name> <db username> <db password> <solution> <sqlCategoryKey *optional*> <sqlCategoryEntity *optional*></div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Personal_views&diff=6713Features/Personal views2023-09-06T11:00:13Z<p>Nun: </p>
<hr />
<div>[[File:View options.PNG|thumb|Picture 1]]<br />
A View (also called List View) is a specific showing of a list of records from an Entity. Using the search and advanced search functions, you can choose to exclude records form the View using different parameters. The currently active parameters can be seen below the View. To save the parameters of a View for later reuse, click the 'Views' button in the functions menu and give the saved View a name in the text field as shown in Picture 1<br />
<br />
[[File:View option location.PNG|thumb|Picture 2]]<br />
Initially this saved View is a Personal View, meaning that only you will have access to it. To make it a Shared View, which every application user has access to, navigate to the back-end and select the 'List views' option from the 'Resources' dropdown menu as shown in Picture 2. Now select the name of the View and check the 'Shared' box. The Personal View is now a Shared View instead.<br />
<br />
Other users who use the Shared View are still restricted to the information available to their own user group. You can therefore not accidentally share unauthorized data by making a Shared View.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Personal_views&diff=6712Features/Personal views2023-09-06T10:59:10Z<p>Nun: </p>
<hr />
<div>[[File:View options.PNG|thumb|Picture 1]]<br />
A View (also called List View) is a specific showing of a list of records from an Entity. Using the search and advanced search functions, you can choose to exclude records form the View using different parameters. The currently active parameters can be seen below the View. To save the parameters of a View for later reuse, click the 'Views' button in the functions menu and give the saved View a name in the text field as shown in Picture 1<br />
<br />
Initially this saved View is a Personal View, meaning that only you will have access to it. To make it a Shared View, which every application user has access to, navigate to the back-end and select the 'List views' option from the 'Resources' dropdown menu. Now select the name of the View and check the 'Shared' box. The Personal View is now a Shared View instead.<br />
<br />
Other users who use the Shared View are still restricted to the information available to their own user group. You can therefore not accidentally share unauthorized data by making a Shared View.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Personal_views&diff=6711Features/Personal views2023-09-06T10:58:48Z<p>Nun: </p>
<hr />
<div>A View (also called List View) is a specific showing of a list of records from an Entity. Using the search and advanced search functions, you can choose to exclude records form the View using different parameters. The currently active parameters can be seen below the View. To save the parameters of a View for later reuse, click the 'Views' button in the functions menu and give the saved View a name in the text field as shown in Picture 1<br />
[[File:View options.PNG|thumb|Picture 1]]<br />
<br />
Initially this saved View is a Personal View, meaning that only you will have access to it. To make it a Shared View, which every application user has access to, navigate to the back-end and select the 'List views' option from the 'Resources' dropdown menu. Now select the name of the View and check the 'Shared' box. The Personal View is now a Shared View instead.<br />
<br />
Other users who use the Shared View are still restricted to the information available to their own user group. You can therefore not accidentally share unauthorized data by making a Shared View.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Personal_views&diff=6710Features/Personal views2023-09-06T10:56:21Z<p>Nun: </p>
<hr />
<div>A View (also called List View) is a specific showing of a list of records from an Entity. Using the search and advanced search functions, you can choose to exclude records form the View using different parameters. The currently active parameters can be seen below the View. To save the parameters of a View for later reuse, click the 'Views' button in the functions menu and give the saved View a name in the text field. Initially this saved View is a Personal View, meaning that only you will have access to it. To make it a Shared View, which every application user has access to, navigate to the back-end and select the 'List views' option from the 'Resources' dropdown menu. Now select the name of the View and check the 'Shared' box. The Personal View is now a Shared View instead.<br />
<br />
Other users who use the Shared View are still restricted to the information available to their own user group. You can therefore not accidentally share unauthorized data by making a Shared View.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=File:View_option_location.PNG&diff=6709File:View option location.PNG2023-09-06T10:50:23Z<p>Nun: Location of List view options</p>
<hr />
<div>== Summary ==<br />
Location of List view options</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Personal_views&diff=6708Features/Personal views2023-09-06T10:49:05Z<p>Nun: </p>
<hr />
<div>A View (also called list view) is a specific showing of a list of records from an Entity. Using the search and advanced search functions, you can choose to exclude records form the view using different parameters. The currently active parameters can be seen below the view. To save the parameters of a view for later reuse, click the 'Views' button in the functions menu and give the saved view a name in the text field. Initially this saved view is a Personal View, meaning that only you will have access to it. To make it a shared view, which every application user has access to, navigate to the back-end and</div>Nunhttps://wiki.tsnocode.dev/index.php?title=File:View_options.PNG&diff=6707File:View options.PNG2023-09-06T10:38:22Z<p>Nun: View option window</p>
<hr />
<div>== Summary ==<br />
View option window</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Personal_views&diff=6706Features/Personal views2023-09-06T10:37:33Z<p>Nun: Created page with "A View (also called list view) is a specific showing of a list of records from an Entity. Using the search and advanced search functions, you can choose to exclude records form the view using different parameters. The currently active parameters can be seen below the view. To save the parameters of a view for later reuse, select"</p>
<hr />
<div>A View (also called list view) is a specific showing of a list of records from an Entity. Using the search and advanced search functions, you can choose to exclude records form the view using different parameters. The currently active parameters can be seen below the view. To save the parameters of a view for later reuse, select</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6705Nomenclature2023-09-01T10:15:36Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Collection of fields for the purpose of access management<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
*User group: Determines who has access to which data and features<br />
*Codeunit: Java code for specialized functionality<br />
*Template: Tool for automatically creating documents and interfaces by feeding values into a predefined layout.<br />
*Interface:<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6704Nomenclature2023-09-01T10:14:57Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Collection of fields for the purpose of access management<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
*User group: Determines who has access to which data and features<br />
*Codeunit: Java code for specialized functionality<br />
*Template: Tool for automatically creating documents and interfaces by feeding values into a predefined layout.<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6701Nomenclature2023-08-28T13:00:30Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Collection of fields for the purpose of access management<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
*User group: Determines who has access to which data and features<br />
*Codeunit: Java code for specialized functionality<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6700Nomenclature2023-08-28T13:00:16Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Collection of fields for the purpose of access management<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
*User group: Determines who has access to which data and features<br />
*Codeunit: Advanced piece of Java code for specialized functionality<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6699Nomenclature2023-08-28T12:57:51Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Collection of fields for the purpose of access management<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
*User group: Determines who has access to which data and features<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6698Nomenclature2023-08-28T12:53:07Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Collection of fields<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
*User group: Determines who has access to which data and features<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6697Nomenclature2023-08-28T12:44:13Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Collection of fields<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6696Features/Duplicate prevention2023-08-28T12:25:48Z<p>Nun: /* What it is */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
A hr-management system is used to hire new employees that have to be registered with information such as name and email address. During this registration mistakes can happen where an employee is registered multiple times, creating duplicates in the system with different system ID's. To prevent this there should be some part of the data from the employee that would not impossibly exist for another employee, such as the email address which by design are unique. If you are adding a record of an employee whose email address already exists in the system, then that employee certainly already exists in the system. Other suitable types of data could be Social Security Numbers or CPR numbers, which are also unique by design. If no such suitable data field is available, two or more fields can be used, so that they in combination constitute a unique value. It is for example unlikely that two people with the same name and same date of employment should exist.<br />
<br />
== Guide ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
[[File:Field select.PNG|thumb|Picture 1]]<br />
To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.<br />
[[File:Field advanced toggle.PNG|thumb|Picture 2]]<br />
The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.<br />
[[File:Unique key.PNG|thumb|Picture 3]]<br />
Now enable the check mark as shown in picture 3.<br />
Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Status_level_dependencies&diff=6695Features/Status level dependencies2023-08-28T11:31:02Z<p>Nun: /* What it is */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
A hr-management system is used to show information on employees who are assigned to projects. These employees are either currently working on a project or between projects. Or they might be in the process of being hired and would therefore not be a full employee yet. Depending on which of these states the employee is currently in, different information about them would be made available. If they were under consideration of being hired, we should see their application. If they were working on a project, we should see their work schedule. If they were between projects, we should see the end date of their last project. Each piece of information should only be made visible for the status in question, since they make no sense or are unimportant otherwise. Status level dependencies are used to manage this visibility.<br />
<br />
== Guide ==<br />
[[File:Levels.png|thumb|397x397px|Picture 1]]<br />
Status levels are numerical categories that one or more statuses can belong to.<br />
Individual Fields in an Entity can be configured to depend on these levels such that they can be made inactive and hidden if the Entity record is not in a status with the correct level.<br />
For example can the dependency be set for all status levels above a certain value such that one or more Fields are only active and displayed for those levels.<br />
To see the status levels of an Entity's statuses, go to that Entity in the back-end and look in the column shown in picture 1.<br />
[[File:Picture 2.png|thumb|Picture 2]]<br />
To change a status's level, go to that status and edit it as shown in picture 2.<br />
[[File:Advanced toggle.png|thumb|Picture 3]]<br />
[[File:Level dependency.png|thumb|Picture 4]]<br />
To set the dependency, toggle the advanced view of the Entity panel on as shown in picture 3 and go to the bottom as shown in picture 4.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Status_level_dependencies&diff=6694Features/Status level dependencies2023-08-28T11:30:03Z<p>Nun: /* What it is */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
A hr-management system contains some employees who are assigned to projects. These employees are either currently working on a project or between projects. Or they might be in the process of being hired and would therefore not be a full employee yet. Depending on which of these states the employee is currently in, different information about them would be made available. If they were under consideration of being hired, we should see their application. If they were working on a project, we should see their work schedule. If they were between projects, we should see the end date of their last project. Each piece of information should only be made visible for the status in question, since they make no sense or are unimportant otherwise. Status level dependencies are used to manage this visibility.<br />
<br />
== Guide ==<br />
[[File:Levels.png|thumb|397x397px|Picture 1]]<br />
Status levels are numerical categories that one or more statuses can belong to.<br />
Individual Fields in an Entity can be configured to depend on these levels such that they can be made inactive and hidden if the Entity record is not in a status with the correct level.<br />
For example can the dependency be set for all status levels above a certain value such that one or more Fields are only active and displayed for those levels.<br />
To see the status levels of an Entity's statuses, go to that Entity in the back-end and look in the column shown in picture 1.<br />
[[File:Picture 2.png|thumb|Picture 2]]<br />
To change a status's level, go to that status and edit it as shown in picture 2.<br />
[[File:Advanced toggle.png|thumb|Picture 3]]<br />
[[File:Level dependency.png|thumb|Picture 4]]<br />
To set the dependency, toggle the advanced view of the Entity panel on as shown in picture 3 and go to the bottom as shown in picture 4.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Status_level_dependencies&diff=6693Features/Status level dependencies2023-08-28T11:29:17Z<p>Nun: /* What it is */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
Say we have a hr-management system containing some employees who are assigned to projects. These employees are either currently working on a project or between projects. Or they might be in the process of being hired and would therefore not be a full employee yet. Depending on which of these states the employee is currently in, different information about them would be made available. If they were under consideration of being hired, we should see their application. If they were working on a project, we should see their work schedule. If they were between projects, we should see the end date of their last project. Each piece of information should only be made visible for the status in question, since they make no sense or are unimportant otherwise. Status level dependencies are used to manage this visibility.<br />
<br />
== Guide ==<br />
[[File:Levels.png|thumb|397x397px|Picture 1]]<br />
Status levels are numerical categories that one or more statuses can belong to.<br />
Individual Fields in an Entity can be configured to depend on these levels such that they can be made inactive and hidden if the Entity record is not in a status with the correct level.<br />
For example can the dependency be set for all status levels above a certain value such that one or more Fields are only active and displayed for those levels.<br />
To see the status levels of an Entity's statuses, go to that Entity in the back-end and look in the column shown in picture 1.<br />
[[File:Picture 2.png|thumb|Picture 2]]<br />
To change a status's level, go to that status and edit it as shown in picture 2.<br />
[[File:Advanced toggle.png|thumb|Picture 3]]<br />
[[File:Level dependency.png|thumb|Picture 4]]<br />
To set the dependency, toggle the advanced view of the Entity panel on as shown in picture 3 and go to the bottom as shown in picture 4.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Status_level_dependencies&diff=6691Features/Status level dependencies2023-08-28T07:37:21Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem.<br />
<br />
== Guide ==<br />
[[File:Levels.png|thumb|397x397px|Picture 1]]<br />
Status levels are numerical categories that one or more statuses can belong to.<br />
Individual Fields in an Entity can be configured to depend on these levels such that they can be made inactive and hidden if the Entity record is not in a status with the correct level.<br />
For example can the dependency be set for all status levels above a certain value such that one or more Fields are only active and displayed for those levels.<br />
To see the status levels of an Entity's statuses, go to that Entity in the back-end and look in the column shown in picture 1.<br />
[[File:Picture 2.png|thumb|Picture 2]]<br />
To change a status's level, go to that status and edit it as shown in picture 2.<br />
[[File:Advanced toggle.png|thumb|Picture 3]]<br />
[[File:Level dependency.png|thumb|Picture 4]]<br />
To set the dependency, toggle the advanced view of the Entity panel on as shown in picture 3 and go to the bottom as shown in picture 4.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6690Features/Duplicate prevention2023-08-28T07:37:08Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== Guide ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
[[File:Field select.PNG|thumb|Picture 1]]<br />
To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.<br />
[[File:Field advanced toggle.PNG|thumb|Picture 2]]<br />
The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.<br />
[[File:Unique key.PNG|thumb|Picture 3]]<br />
Now enable the check mark as shown in picture 3.<br />
Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6689Features/Duplicate prevention2023-08-28T07:36:40Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== How to do ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
[[File:Field select.PNG|thumb|Picture 1]]<br />
To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.<br />
[[File:Field advanced toggle.PNG|thumb|Picture 2]]<br />
The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.<br />
[[File:Unique key.PNG|thumb|Picture 3]]<br />
Now enable the check mark as shown in picture 3.<br />
Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6688Features/Duplicate prevention2023-08-28T07:36:06Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== How to do ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.<br />
[[File:Field select.PNG|thumb|Picture 1]]<br />
The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.<br />
[[File:Field advanced toggle.PNG|thumb|Picture 2]]<br />
Now enable the check mark as shown in picture 3.<br />
[[File:Unique key.PNG|thumb|Picture 3]]<br />
Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6687Features/Duplicate prevention2023-08-28T07:33:03Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== How to do ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.<br />
[[File:Field select.png|thumb|Picture 1]]<br />
The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.<br />
Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6686Features/Duplicate prevention2023-08-28T07:32:38Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== How to do ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.<br />
[[File:field select.png|thumb|Picture 1]]<br />
The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.<br />
Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=File:Unique_key.PNG&diff=6685File:Unique key.PNG2023-08-28T07:30:55Z<p>Nun: </p>
<hr />
<div></div>Nunhttps://wiki.tsnocode.dev/index.php?title=File:Field_select.PNG&diff=6684File:Field select.PNG2023-08-28T07:30:44Z<p>Nun: </p>
<hr />
<div></div>Nunhttps://wiki.tsnocode.dev/index.php?title=File:Field_advanced_toggle.PNG&diff=6683File:Field advanced toggle.PNG2023-08-28T07:30:26Z<p>Nun: </p>
<hr />
<div></div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6682Features/Duplicate prevention2023-08-28T07:29:11Z<p>Nun: </p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== How to do ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.<br />
The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.<br />
Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6681Features/Duplicate prevention2023-08-28T07:28:08Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== How to do ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.<br />
The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.<br />
Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.<br />
<br />
<br />
* Entity: Check for duplicates<br />
* Field: Is part of a unique key<br />
<br />
Note checks realtime when entering data</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6675Features/Duplicate prevention2023-08-24T14:49:42Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== How to do ==<br />
To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.<br />
<br />
To set a field of an entity to be a unique key, go to that record in the back-end <br />
<br />
<br />
* Entity: Check for duplicates<br />
* Field: Is part of a unique key<br />
<br />
Note checks realtime when entering data</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6671Features/Duplicate prevention2023-08-24T14:27:34Z<p>Nun: /* What it is */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.<br />
<br />
== How to do ==<br />
* Entity: Check for duplicates<br />
* Field: Is part of a unique key<br />
<br />
Note checks realtime when entering data</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Duplicate_prevention&diff=6670Features/Duplicate prevention2023-08-24T14:17:18Z<p>Nun: </p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem.<br />
<br />
<br />
* Entity: Check for duplicates<br />
* Field: Is part of a unique key<br />
<br />
Note checks realtime when entering data</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Status_level_dependencies&diff=6645Features/Status level dependencies2023-08-11T09:08:04Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem.<br />
<br />
== How to do ==<br />
[[File:Levels.png|thumb|397x397px|Picture 1]]<br />
Status levels are numerical categories that one or more statuses can belong to.<br />
Individual Fields in an Entity can be configured to depend on these levels such that they can be made inactive and hidden if the Entity record is not in a status with the correct level.<br />
For example can the dependency be set for all status levels above a certain value such that one or more Fields are only active and displayed for those levels.<br />
To see the status levels of an Entity's statuses, go to that Entity in the back-end and look in the column shown in picture 1.<br />
[[File:Picture 2.png|thumb|Picture 2]]<br />
To change a status's level, go to that status and edit it as shown in picture 2.<br />
[[File:Advanced toggle.png|thumb|Picture 3]]<br />
[[File:Level dependency.png|thumb|Picture 4]]<br />
To set the dependency, toggle the advanced view of the Entity panel on as shown in picture 3 and go to the bottom as shown in picture 4.</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6644Nomenclature2023-08-11T08:58:29Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Controls which user groups have access to the field<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6643Nomenclature2023-08-11T08:52:02Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
**Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Controls which user groups have access to the field<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
*Template:<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6642Nomenclature2023-08-11T08:51:39Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects == <br />
<br />
*Dashboard: Front-end page<br />
<br />
*Widget: UI element in a dashboard<br />
*Section: Collection of entities<br />
*Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
*Record: Main data holding thing (This is an object in OOP)<br />
**Revision: How many times a record has been changed<br />
*Status: Configurable state a record is in<br />
**Level: Assignable number to a status<br />
**Action: Configurable behavior depending on status<br />
*Field: A single data point of a record <br />
**Block: Controls which user groups have access to the field<br />
**Validation: A check on whether or not a field has received correct data<br />
**Dependency: A field's existence can be made dependent on other things<br />
*Template<br />
<br />
==Parts==<br />
*Front-end: The system that the normal user sees<br />
*Back-end: Where the front-end is configured<br />
*Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6641Nomenclature2023-08-11T08:47:48Z<p>Nun: /* Objects */</p>
<hr />
<div>== Objects ==<br />
* Section: Collection of entities<br />
* Entity: Describes a type of record, including its behavior and datatypes (This is a class in OOP)<br />
* Record: Main data holding thing (This is an object in OOP)<br />
** Revision: How many times a record has been changed<br />
* Status: Configurable state a record is in<br />
** Level: Assignable number to a status<br />
** Action: Configurable behavior depending on status<br />
* Field: A single data point of a record <br />
** Block: Controls which user groups have access to the field<br />
** Validation: A check on whether or not a field has received correct data<br />
** Dependency: A field's existence can be made dependent on other things<br />
<br />
== Parts ==<br />
* Front-end: The system that the normal user sees<br />
* Back-end: Where the front-end is configured<br />
* Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Nomenclature&diff=6640Nomenclature2023-08-11T08:47:11Z<p>Nun: description of terms</p>
<hr />
<div>== Objects ==<br />
* Section: Collection of entities<br />
* Entity: Describes a type of record including its behavior and datatypes (This is a class in OOP)<br />
* Record: Main data holding thing (This is an object in OOP)<br />
** Revision: How many times a record has been changed<br />
* Status: Configurable state a record is in<br />
** Level: Assignable number to a status<br />
** Action: Configurable behavior depending on status<br />
* Field: A single data point of a record <br />
** Block: Controls which user groups have access to the field<br />
** Validation: A check on whether or not a field has received correct data<br />
** Dependency: A field's existence can be made dependent on other things<br />
<br />
== Parts ==<br />
* Front-end: The system that the normal user sees<br />
* Back-end: Where the front-end is configured<br />
* Database: It's a database</div>Nunhttps://wiki.tsnocode.dev/index.php?title=Features/Status_level_dependencies&diff=6635Features/Status level dependencies2023-08-11T08:03:15Z<p>Nun: /* How to do */</p>
<hr />
<div>== What it is ==<br />
<br />
Example:<br />
Say you had a management system containing employees. These employees have the following information: They have a CV, current working details, and last workday. If a given employees can be in a few different statuses then each of the fields might not make sense. If an employee is in the process of being hired, then they would not have any current work details or a specific last work day. If the employee were in the process of being fired, then their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status the record currently is in. Status level dependencies are used to solve this problem.<br />
<br />
== How to do ==<br />
[[File:Levels.png|thumb|397x397px|Picture 1]]<br />
Status levels are numerical categories that statuses can belong to.<br />
Fields in entities can be configured to depend on these levels such that they can be made inactive if the entity record is not in a status with the correct level.<br />
For example can the dependency be set for all status levels above a certain value such that the field is only shown for those levels.<br />
To see the status levels of an entity's statuses, go to that entity in the back-end and look in the column shown in picture 1.<br />
[[File:Picture 2.png|thumb|Picture 2]]<br />
To change a status's level, go to that status and edit it as shown in picture 2.<br />
[[File:Advanced toggle.png|thumb|Picture 3]]<br />
[[File:Level dependency.png|thumb|Picture 4]]<br />
To set the dependency, toggle the advanced view of the entity on as shown in picture 3 and go to the bottom as shown in picture 4.</div>Nun