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 13:22] dlee [Add/Edit User Account Filters] |
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 77: | Line 87: | ||
| - **Datasource** is the data table from the previously selected connection where the filtering values are located. | - **Datasource** is the data table from the previously selected connection where the filtering values are located. | ||
| - **Field** is the specific column from the data source that stores the filtering values | - **Field** is the specific column from the data source that stores the filtering values | ||
| + | |||
| ======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. | ||
| + | |||
| + | In SAP Business One, a salesperson is assigned an internal numeric code. The database field name is “SlpCode.” When a sales document (order, invoice, etc.) is created, the numeric code of the salesperson is included in the document record. SAP Business One’s design is such that the salesperson code field in the sales documents table is also named “SlpCode.” | ||
| + | |||
| + | ==== Create a User Account Filter ==== | ||
| + | |||
| + | First, a Versago User Account Filter is created using a connection to SAP Business One and the salesperson table (OSLP) as the datasource. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | ==== Assign the User Account Filter to a User ==== | ||
| + | |||
| + | 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. | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | 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, | ||
| + | |||
| + | ==== Use the User Account Filter in a Data View ==== | ||
| + | |||
| + | 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. | ||
| + | |||
| + | {{ :: | ||
| + | |||
| + | 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, if the user described above runs the data view, they will only see records where the “SlpCode” value equals 1. | ||
| + | |||
| + | **Note:** Both User Account and User Applied filters can be used in the data view at the same time. | ||
| + | |||
| ---- | ---- | ||