Too long to translate: App Settings

content/en/docs/refguide/modeling/app-explorer/app/app-settings/certificates-tab.md

@@ -0,0 +1,52 @@
+---
+title: "Certificates Tab"
+url: /refguide/certificates-tab/
+weight: 40
+#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
+---
+
+## Introduction
+
+Certificates are used to connect to web services over HTTPS.
+
+## Certificates Tab 
+
+Certificates are used when the following requirements are met:
+
+* The server uses a self-signed certificate authority, and/or
+* A client certificate (certificate with a private key) is required
+
+These certificates can be imported into Studio Pro using the **Import** button. Certificate authority files usually have a *.crt* extension, and client certificates usually have a *.p12* or *.pfx* extension. After importing, use **View details** to get more information about the certificate.
+
+Client certificates added here will be used whenever a server accepts a client certificate. If you upload more than one client certificate, one of them will be chosen based on the requirements of the server. If you need more control over client certificates, you should not upload the certificates here, but use the [Runtime customization](/refguide/custom-settings/) *ClientCertificates*, *ClientCertificatePasswords*, and *ClientCertificateUsages* settings.
+
+{{% alert color="warning" %}}
+
+When running from Studio Pro or from Eclipse, the certificates will be used automatically to connect over HTTPS. When running on a server, the location of the certificate files has to be specified in the configuration file.
+
+{{% /alert %}}
+{{% alert color="warning" %}}
+
+Be aware that during local deployment, the certificate files will be located in the **deployment** folder, under **model/certificates**. Therefore, do not use production certificates during development.
+
+{{% /alert %}}
+{{% alert color="info" %}}
+
+Certificates can be installed in the Windows Certificate Store using the **Install Certificate** wizard in the **View details** form. This can be useful when trying to access a WSDL-file using an *HTTPS* connection which requires a client certificate.
+
+{{% /alert %}}
+{{% alert color="info" %}}
+
+When an SSLException occurs at runtime with the message `HelloRequest followed by an unexpected handshake message` or when a web service does not respond (Java 6 update 21 and above) when using the imported certificates, this is caused by either the client or server not being [RFC-5746](https://www.ietf.org/rfc/rfc5746.txt)-compatible.
+
+If updating the client and server to be compatible with RFC-5746 is not feasible, the following should be added to **Extra JVM parameters** in the **Server** tab to avoid this exception:
+
+`-Dsun.security.ssl.allowUnsafeRenegotiation=true`
+
+Be warned that this does make the client-server communication vulnerable to an exploit which has been fixed in RFC-5746.
+
+When client and server are RFC-5746 compatible at a future point in time, this JVM parameter can be removed.
+
+For background information, see [Transport Layer Security (TLS) Renegotiation Issue Readme](https://www.oracle.com/technetwork/java/javase/documentation/tlsreadme2-176330.html).
+
+{{% /alert %}}

content/en/docs/refguide/modeling/app-explorer/app/app-settings/configuration.md → content/en/docs/refguide/modeling/app-explorer/app/app-settings/configurations-tab.md

@@ -1,6 +1,9 @@
 ---
-title: "Configurations"
-url: /refguide/configuration/
+title: "Configurations Tab"
+url: /refguide/configurations-tab/
+weight: 10
+aliases:
+    - /refguide/configuration/
 #If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
 ---
 

content/en/docs/refguide/modeling/app-explorer/app/app-settings/dependencies-tab.md

@@ -0,0 +1,22 @@
+---
+title: "Dependencies Tab"
+url: /refguide/dependencies-tab/
+weight: 70
+#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
+---
+
+## Introduction
+
+This tab can be used to view the managed dependencies in your app in one place and to manage the dependencies in the userlib directory.
+
+### Overview
+
+This shows all the direct managed dependencies in your app listed by group and artifact. It shows which versions of the dependencies you have and which modules they are coming from. If your app reports multiple versions of the same group and artifact, the highest version is used, so having multiple versions of a dependency is not necessarily a problem.
+
+### Managed Dependency Exclusions
+
+This shows all the managed dependencies in your app listed by package name. This overview includes both direct and transitive dependencies. If you have conflicts between different dependencies, you can uncheck any files that you want to exclude. Ensure you leave at least one dependency which supports any calls made by your app or its dependencies.
+
+### Userlib Exclusions
+
+This shows the libraries from the userlib directory and allows you to exclude them from deployment. Use this, for example, if there is an add-on module that ships with a different version of a library that is already in your userlib folder.

content/en/docs/refguide/modeling/app-explorer/app/app-settings/languages-tab.md

@@ -0,0 +1,20 @@
+---
+title: "Languages Tab"
+url: /refguide/languages-tab/
+weight: 30
+#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
+---
+
+## Introduction
+
+Select the language you want to use in your app. For more information about using different languages, see [Language Menu](/refguide/translatable-texts/).
+
+### Default Language
+
+The **Default language** indicates the language that is used when a user has not chosen a language. The default language is also used as a fall-back language when a certain text is not translated to another language.
+
+### Languages {#languages}
+
+This is the list of languages in which your application will be available for users.
+
+For each language, you can configure whether to check that all mandatory texts have a value. The default language is always checked. If a language is not checked and certain texts are not translated in Studio Pro, the default language is used as fallback language. This means you can run your application even though you have only partially translated your interface into a new language.

content/en/docs/refguide/modeling/app-explorer/app/app-settings/misc-tab.md

@@ -0,0 +1,53 @@
+---
+title: "Miscellaneous Tab"
+url: /refguide/miscellaneous-tab/
+weight: 90
+#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
+---
+
+## Introduction
+
+These settings determine the behavior of Studio Pro for this app. The settings apply to everyone that is working on this app.
+
+### Bundle Widgets When Running Locally 
+
+{{% alert color="info" %}}
+This setting is only available in the Dojo Client version of Studio Pro, which is deprecated. For more information, see [Mendix Client](/refguide/mendix-client/).
+{{% /alert %}}
+
+When deploying to the cloud, custom widgets are bundled to optimize client-server communication. When deploying locally, this step is skipped to accelerate startup duration. In some cases, this may obfuscate errors triggered by faulty custom widgets.
+
+If this option is set, custom widgets will also be bundled locally. This mimics the production deployment, eliminating risk at the cost of start-up time.
+
+### Use Data Grid 2, Combo Box, and Image Widgets for Content Generation {#use-dg-cb-i}
+
+{{% alert color="info" %}}
+This setting is only available in the Dojo Client version of Studio Pro, which is deprecated. For more information, see [Mendix Client](/refguide/mendix-client/).
+{{% /alert %}}
+
+If this setting is enabled, modern widgets like [Data Grid 2](/appstore/modules/data-grid-2/), [Combo Box](/appstore/widgets/combobox/), and [Image](/appstore/widgets/image/) will be used when generating overview pages or the content of data views. Existing generated content remains as is. 
+
+See the list below for detailed information on which widgets are generated in various circumstances:
+
+* A Data Grid 2 module is generated instead of a Data Grid 1 module
+* A combo box is generated instead of a combination of dropdown, reference selector, and input reference set selector widgets
+* An image widget is generated instead of a static image widget and a dynamic image widget
+
+### Default Association Storage
+
+You can decide how associations are stored in the database.
+
+This option allows you to change the default for new associations. The initial defaults are as follows:
+
+* **New projects** – one-to-many and one-to-one associations are implemented as direct associations
+* **Upgraded projects** – for projects which are upgraded from an older version of Mendix, all new associations continue to be implemented as association tables
+
+For more information, including which types of association this applies to, see [Association Storage Options](/refguide/association-storage/).
+
+### Suggest Lower-Case Variable Names in Microflows
+
+When enabled, the names that Studio Pro suggests in microflows will start with a lower-case letter instead of an upper-case letter.
+
+### Activity Default Colors
+
+This table allows you to select a default color for each microflow activity type that is available in your app. The selected color will be used as the background color for all microflow activities of that type in your app. It is possible to override this default value for individual activities in the microflow editor. If you change the default color for an activity type, and there are activities of that type present in the app that have an individual background color specified, a dialog will be shown that allows you to apply the new default color to these activities as well.