Showing results for 
Search instead for 
Do you mean 

How to feel secure about your user's actions in Sage #SalesLogix v8.0

by Employee on ‎01-16-2013 10:20 AM

What is an "Action":

Within the context of the SalesLogix Web Secured Action feature, an "Action" generally cooresponds to something in the Web application that can be clicked on - say a Left Navigation icon, a standard toolbar mennu item, a Save or Delete button. Less obvious actions are things like Common Task items (lower right side), Left Navigation right click pop-up menu items (aka Context Menu Items). Even less obvious are permissions to navigate to a Page (ex. Insert Opportunity page).

 

 

Applying Secured Actions to the feature:

When modifying or extending the SalesLogix Web features, various action items (buttons, toolbars, etc.) provide an optional configuration property to designate a Secured Action as being necessary to see and/or use that action. With the exception of a few features within the Administration left Navigation area, the SalesLogix v8.0 solution has Secured Actions defined and implemented for all Entities. As many new Secured Actions can be created as are needed to satisfy your customization requirements and scenarios.

 

 

Managing Users and Secured Actions via (user) Roles:

While a customizer is responsible for assigning a Secured Action to each feature/action as part of the customization process, the SalesLogi Administrative staff are responsible for determining which users should have which specific Secured Actions granted to them. To make this process easier to defined and maintain, we leverage Roles.  A Role is simply a meaningful name, a list of Secured Actions, and a list of Users.  A few Roles are defined in the base SalesLogix "out-of-box" solution like "Administrator" and "Standard User", but you are free to create additional Roles that suite your own solution management neeeds.  For example - one might create a "Campaign Management" role for the small group of Users that have permission to Create (Add), Edit, and Delete Campaigns.

 

 

 

Standard (per Entity) Actions:

The vast majority of Secured Actions are relative to each specific Entity type, while a few are relative to a non-Entity specific feature. For example securing the ability to see (View) the Administration left navigation section is a non-Entity specific Secured Action.

 

The standard entity Secured Actions that you should generally always defined and utilize for each Entity are:

  • Add
  • Delete
  • Edit
  • View

 

Use of the standard Secure Actions in customizations:

Add -

  • Save button on an Insert form
  • Save button on an Detail form
  • Add button on a datagrid
  • Permission to Access to an Insert Page

 

Edit -

  • Save button on Detail form
  • Save button on an Edit dialog window

 

Delete -

  • Delete button on the Detail form
  • Delete link on a datagrid

 

View -

  • Left Nav item for an Entity
  • Edit link on a datagrid (to launch an Edit Dialog window)
  • Hyperlink to an Entity from a datagrid
  • Permission to access a MainView (Group List + Detail) Page

 

 

Special (per Entity) Secured Actions:

You are free to create any new Secured Actions necessary to support your customization and solution management needs. For Entity specific secured actions the following naming convention is recommended for consistency with the base product.

Entities/<<EntityName>>/<<ActionName>>

ex. Entities/Account/Edit

 

An examples of special secured actions might be for Common Task items that perform bulk actions like:

Entities/Group/MergeContact

 

Another example of a special action is:

Entities/Product/LockPricing

 

 

Go forth and be secure in your actions...

Armed with this overview of Secured Actions and the patterns and practices for using them, you too can feel secure about your user's actions in SalesLogix.

 

 

Register Read Guidelines Request Partner or Employee Access

What's New in 8.1

Labels