This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
versago3:user_setup [2022/08/02 15:52] dlee [Assign the Profile to a Versago User] |
versago3:user_setup [2023/11/30 11:27] (current) dlee [Roles] |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| </ | </ | ||
| + | <WRAP center round important 80% > | ||
| + | Users should set their timezone under the User Profile page in order to properly display Calendar data views. | ||
| + | </ | ||
| ======Roles====== | ======Roles====== | ||
| Line 48: | Line 51: | ||
| - Click the [**Add Role**] button to create a new user. | - Click the [**Add Role**] button to create a new user. | ||
| - Click a row in the listing to edit the role. | - Click a row in the listing to edit the role. | ||
| + | |||
| + | |||
| + | <WRAP center round info 80%> | ||
| + | Click to the right of the Select All box to sort by selected users | ||
| + | {{ : | ||
| + | </ | ||
| + | |||
| Line 79: | Line 89: | ||
| ======Implementing User Account Filters====== | ======Implementing User Account Filters====== | ||
| + | |||
| + | {{ : | ||
| To illustrate how a user account filter works we will use the salesperson example. We will be using the SAP Business One data structures. | To illustrate how a user account filter works we will use the salesperson example. We will be using the SAP Business One data structures. | ||
| Line 94: | Line 106: | ||
| Once the UAF has been defined, we must tell Versago what values are valid for a given user. This is done in the user setup. | Once the UAF has been defined, we must tell Versago what values are valid for a given user. This is done in the user setup. | ||
| - | {{ :versago:rpuconfig15.png?400 |}} | + | {{ :versago3:user_filter04.png?direct |
| - | + | ||
| - | In some cases, a user may need to see information for more than value. This would be the case where a sales manager needs to see not only their information, | + | |
| - | + | ||
| - | ==== Use the Profile in a Report ==== | + | |
| - | + | ||
| - | Since the filtering process takes place when a report is executed, we need to also define what profile(s) to use in the report. This is done in the report maintenance process. | + | |
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | As shown in this example, you simple indicate the “Filter Type” as Profile and select the desired profile as the “Filter Name.” | + | |
| - | Using our example, if the user described above runs a report using the “SlpCode” profile, they will only see records | + | In some cases, a user may need to see information for more than one value. This would be the case where a sales manager needs to see not only their information, |
| - | **Note:** Both profiles and parameters can be used in a report | + | ==== Use the User Account Filter |
| - | ===== Multiple Profile Values ===== | + | Since the filtering process takes place when a data view is executed, we need to also define what UAFs to use in the data view. This is done in the report maintenance process. |
| - | In the examples above, the value “SlpCode” has been present in the data being reported (the sales document). So, the profile filtering works with no issues. However, there may be situations where the name of the filtering column does not match This value in the source table. This situation can be addressed using multiple values in the profile setup. | + | {{ :: |
| - | In this example, | + | The data view should include in its result set a field with the same name as that of the UAF. In this case, SplCode |
| + | Using our example, | ||
| - | {{ | + | **Note:** Both User Account and User Applied filters can be used in the data view at the same time. |
| - | One shows that the filtering column name might be “SlpCode” and the second shows that the filtering column name might be “SlpCodeX.” Now, we can use the same profile and the filtering will occur if a column name “SlpCode” or “SlpCodeX” is found. | ||
| ---- | ---- | ||