Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Introduction (Roles, Profiles, Users) • Record/Payment Submission • Forms Home • Introduction (ExchangeConnector) • Introduction (Custom Menus) • Preparation
versago:role_profile_user_configuration

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
versago:role_profile_user_configuration [2019/11/13 11:07]
akoehler [Profile Details] 		versago:role_profile_user_configuration [2020/10/23 09:21] (current)
dlee [Profile Fields]
Line 149: Line 149:
 ===== Profile Details ===== ===== Profile Details =====
  
-{{  :versago:rpuconfig9.png?700  |}}+{{  :versago:rpuconfig9.png?700  |  }}
  
 All profile values are required and can be changed at any time. All profile values are required and can be changed at any time.
Line 168: Line 168:
 ==== Profile Fields ==== ==== Profile Fields ====
  
-The “Profile Fields” grid is used to identify the values (columns) in the source table that hold the filtering values. In most cases, there will only be one profile field value. However, multiple values can be defined if necessary. See [[#appendix-b-using-versago-profiles|//Appendix B – Using Versago Profiles//]] for an example of this or contact Third Wave support for assistance. +The “Profile Fields” grid is used to identify the values (columns) in the source table that hold the filtering values. In most cases, there will only be one profile field value. However, multiple values can be defined if necessary.
 The values in the Profile Fields section can be changed at any time. However, any existing user profile associations will be removed and must be reassigned. The values in the Profile Fields section can be changed at any time. However, any existing user profile associations will be removed and must be reassigned.
  
Line 185: Line 184:
   * Click on the Users link in the Admin console to begin.   * Click on the Users link in the Admin console to begin.
  
-{{:versago:rpuconfig10.png?700|}}+{{  :versago:rpuconfig10.png?700  |}}
  
 The user maintenance tool provides two functions: creation of new users and maintenance of existing users. The user maintenance tool provides two functions: creation of new users and maintenance of existing users.
Line 203: Line 202:
   * All items except **Email** can be changed at any time.   * All items except **Email** can be changed at any time.
  
-{{:versago:rpuconfig11.png?400|}}}+{{  :versago:rpuconfig11.png?400  |}}}
  
   - **Email** is the key identifier for a user.   - **Email** is the key identifier for a user.
Line 226: Line 225:
     - If the checkbox is selected the user is active and can access Versago.     - If the checkbox is selected the user is active and can access Versago.
  
-<WRAP round important 60%>+<WRAP center round important 60% >
 Your Versago license limits the number of users that can be **designated as active** at any time. If you attempt to add or activate a user that will cause you to exceed the number of licensed users, an error message is displayed. The add/update process cannot continue until another user has been made inactive or you increase the number of users for your installation. Contact your Third Wave consultant if you need to add Versago users. Your Versago license limits the number of users that can be **designated as active** at any time. If you attempt to add or activate a user that will cause you to exceed the number of licensed users, an error message is displayed. The add/update process cannot continue until another user has been made inactive or you increase the number of users for your installation. Contact your Third Wave consultant if you need to add Versago users.
 </WRAP> </WRAP>
Line 237: Line 236:
  
 {{:c:\shared\pandocconvert/media/image12.png?304x32}} {{:c:\shared\pandocconvert/media/image12.png?304x32}}
-{{:versago:rpuconfig12.png?400|}}+{{  :versago:rpuconfig12.png?400  |}}
  
   - A user must be assigned to at least one role.   - A user must be assigned to at least one role.
Line 248: Line 247:
 ==== Profiles ==== ==== Profiles ====
  
-{{:versago:rpuconfig13.png?400|}}+{{  :versago:rpuconfig13.png?400  |}}
  
   - Select the desired profile (previously defined) from the “User Profile” drop-down list.   - Select the desired profile (previously defined) from the “User Profile” drop-down list.
Line 333: Line 332:
 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 profile is created. The profile uses the SAP Business One salesperson table (OSLP) as the source of valid values.
  
-{{:versago:rpuconfig14.png?600|}}+{{  :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. The “Profile Field Identifier” value is the field (column) name that the profile filtering process expects to see in the report data.
Line 341: Line 340:
 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. 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|}}+{{  :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. 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.
Line 349: Line 348:
 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. 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|}}+{{  :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.” As shown in this example, you simple indicate the “Filter Type” as Profile and select the desired profile as the “Filter Name.”
Line 363: Line 362:
 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. 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|}}+{{  :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. 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.
Line 379: Line 378:
 Here is a sample of how a profile for this purpose would be set up. Here is a sample of how a profile for this purpose would be set up.
  
-{{:versago:rpuconfig18.png?600|}}+{{  :versago:rpuconfig18.png?600  |}}
  
  
versago/role_profile_user_configuration.1573661270.txt.gz · Last modified: 2019/11/13 11:07 by akoehler

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