You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/appstore/use-content/platform-supported-content/modules/document-generation.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -376,7 +376,7 @@ If you encounter any issues while [registering your app environment](#register-a
376
376
377
377
In general, we recommend that you perform the following steps if you get any issues during runtime:
378
378
379
-
1. Temporarily set the log level of `DocumentGeneration` log node to [trace](/howto/monitoring-troubleshooting/log-levels/#level). This should give more insight at what stage the action fails.
379
+
1. Temporarily set the log level of `DocumentGeneration` log node to [trace](/refguide/log-levels/#level). This should give more insight at what stage the action fails.
380
380
2. Temporarily add the page microflow that is configured in the action to the app navigation, or make it accessible via abutton. This can help to verify that the page itself loads correctly, and can for example outline misconfiguration of entity access, widgets, etc. Make sure that you access the page with the same user you provided to the `Generate as user` parameter in the action.
at DocumentGenerationTest.ACT_TestDocument_WrongLayout (JavaAction : 'Generate PDF from page')
446
446
```
447
447
448
-
We recommend that you temporarily set the log level of the `DocumentGeneration` log node to [trace](/howto/monitoring-troubleshooting/log-levels/#level). This should give more insight at what stage the action fails.
448
+
We recommend that you temporarily set the log level of the `DocumentGeneration` log node to [trace](/refguide/log-levels/#level). This should give more insight at what stage the action fails.
## Assigning UserType for Existing Users of IAM Modules
28
30
@@ -55,41 +57,41 @@ Outlined below is an example of a module that can be used to update UserType att
55
57
In the example below, our aim is to update UserType attribute of `UserReportInfo` entity. However, the entity `UserReportInfo` is protected in the System module and has no access rules. As a result, it cannot be exposed directly in the UI pages.
56
58
Therefore, the approach we take is to create a new non-persistable entity, `UserTypeReport`, which we will populate based on the values of `UserReportInfo` to show in the UI.
2. Create a microflow `User_EvaluateAndSetUserType` which will populate the `UserType` attribute on the `UserReportInfo` entity for a given `User`.
69
71
70
72
In this example, we decide whether a user is `Internal` or `External` based on the email address of the user. To do that, we need to retrieve the email address of each user from the database. Note that the `System.User` entity itself does not have the email address. The email address is stored in specializations of `System.User`.
71
73
72
74
Here, we show how to do it for two specializations of the `System.User` entity, namely `Administration.Account` and `MendixSSO.MendixSSOUser`. In the `Administration.Account` entity, the email is in attribute named `Email`. And in the `MendixSSO.MendixSSOUser` entity, it’s in an attribute named `EmailAddress`. Hence we need to use an [Object Type Decision](/refguide/object-type-decision/) activity to split the `System.User` into `Administration.Account` and `MendixSSO.MendixSSOUser` and then fetch the email address according to the name of the attribute.
* The logic to determine whether the end-user is internal or external is up to the developer. The example below returns `true`, to indicate that the user is internal, if the user has no email address, or if the domain for their email address is `mendix.com` or `myorg.com`.
77
79
78
-
{{< figure src="/attachments/howto/monitoring-troubleshooting/populate-user-type/user-type-split.png" alt="Split: Decide if user is internal" class="no-border" >}}
80
+
{{< figure src="/attachments/deployment/general/populate-user-type/user-type-split.png" alt="Split: Decide if user is internal" class="no-border" >}}
79
81
80
82
3. Create a new microflow `User_Correct_UserType` which will use the microflows `User_RetrieveOrCreateUserReportInfo` and `User_EvaluateAndSetUserType` created above. In this microflow, we create and populate the `UserTypeReport` entity and return a list of these entities at the end of the microflow.
#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the Evaluation Guide. See Mapping to Products for more details.
7
9
# Linked from https://www.mendix.com/evaluation-guide/enterprise-capabilities/extensibility/
8
10
---
@@ -24,23 +26,23 @@ Before starting this how-to, make sure you have completed the following prerequi
24
26
* Add a Java action and open the app in Eclipse
25
27
* Read [Extending Your Application with Custom Java](/refguide/extending-your-application-with-custom-java/)
26
28
* Deploy the application for Eclipse by selecting **Deploy for Eclipse** from the app menu in Studio Pro (you should redo this every time you make changes in Studio Pro):
3. Place the cursor on the line that needs debugging, press <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>B</kbd> to enable a breakpoint. A blue dot in front of the line will appear:
{{% alert color="info" %}}With debugger options, the difference between **Step into** and **Step over** is only noticeable if you run into a function call. **Step into** means that the debugger steps into the function, and **Step over** just moves the debugger to the next line in the same Java action. With **Step return** (pressing <kbd>F7</kbd>), you can instruct the debugger to leave the function; this is basically the opposite of **Step into**. Clicking **Resume** (pressing <kbd>F8</kbd>) instructs the debugger to continue until it reaches another breakpoint.{{% /alert %}}
55
57
56
58
5. Place your cursor on any of the variables in the Java action to see its value in a pop-up window:
{{% alert color="warning" %}}A current limitation is that local variables may not be visible when debugging Java actions in Eclipse. This can affect your ability to inspect variable values during execution.{{% /alert %}}
description: "Describes some best practices to apply during development to get a better performing app. This document is created by and for the Mendix community."
0 commit comments