Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Users
versago3:user_setup

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
versago3:user_setup [2022/08/02 13:54]
dlee 		versago3:user_setup [2023/11/30 11:27] (current)
dlee [Roles]
Line 37: Line 37:
 </WRAP> </WRAP>
  
 +<WRAP center round important 80% >
 +Users should set their timezone under the User Profile page in order to properly display Calendar data views.
 +</WRAP>
  
 ======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
 +{{ :versago3:sortbyselection.mp4 |}}
 +</WRAP>
 +
  
  
Line 79: Line 89:
  
 ======Implementing User Account Filters====== ======Implementing User Account Filters======
 +
 +{{ :versago3:acct_filter.mp4 |How to set up an Account Filter}}
  
 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 86: Line 98:
 ==== Create a User Account Filter ==== ==== Create a User Account Filter ====
  
-First, a Versago profile is created. The profile uses the SAP Business One salesperson table (OSLP) as the source of valid values. +First, a Versago User Account Filter is created using a connection to SAP Business One and the salesperson table (OSLP) as the datasource.
- +
-{{  :versago:rpuconfig14.png?600  |}} +
- +
-The “Profile Field Identifier” value is the field (column) name that the profile filtering process expects to see in the report data. +
- +
-==== Assign the Profile to a Versago User ==== +
- +
-Once a profile has been defined, we must tell Versago what values are valid for a given user. This is done in the user setup as described elsewhere in this document. +
- +
-{{  :versago:rpuconfig15.png?400  |}} +
- +
-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, but also the information for salespersons that report to them. In these cases you simply assign multiple profile values as shown above. +
- +
-==== 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. +
- +
-{{  :versago:rpuconfig16.png?300  |}} +
- +
-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 where the “SlpCode” value equals 3 or 5. +
- +
-**Note:** Both profiles and parameters can be used in a report +
- +
-===== Multiple Profile Values ===== +
- +
-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, we have some documents where the column to be filtered is named “SlpCode” and others where the column to be filtered is named “SlpCodeX.” As shown in the image below, we have created two profile entries. +
- +
-{{  :versago:rpuconfig17.png?700  |}} +
- +
-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. +
- +
-===== Profile Filtering by Versago User =====+
  
-When Versago Forms are being used, you may want to restrict a report that shows the records created via a form to the user that is running the report. You will need to do three things for this to work.+{{ :versago3:user_filter03.png?600  |}}
  
-==== Capture the Versago Information in the Form ====+==== Assign the User Account Filter to a User ====
  
-Third Wave suggests that when you create a Versago form you include three values: CreatedBy, CreatedById, and CreateDate. The column names are not significant; they are just suggestions. “CreatedBy” is the user name (Email). “CreatedById” is the numeric ID assigned to each Versago User. “CreateDate” is the date (or date time) the record is created. See the document “Versago Forms – Default Values” for information on how to capture these values automatically.+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.
  
-==== Create a Profile for Versago Users ====+{{  :versago3:user_filter04.png?direct  |}}
  
-Here is a sample of how a profile for this purpose would be set up.+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, but also the information for salespersons that report to them. In these cases you simply assign multiple filter values.
  
-{{  :versago:rpuconfig18.png?600  |}}+==== 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.
  
-In this case the column name being used for filtering is “CreatedBy.”+{{  ::versago3:user_filter05.png?direct|}}
  
-==== Use the Profile in the Report ====+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.
  
-Use this profile in a report of records created via a Versago form. The records will automatically be filtered based on the user running the report.+**Note:** Both User Account and User Applied filters can be used in the data view at the same time.
  
  
versago3/user_setup.1659462898.txt.gz · Last modified: 2022/08/02 13:54 by dlee

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki