Data Security

 

 

• 2 ways to set object permission - Profile & Permission Set.
• Big picture of Profile:
  • 

• Record Level Security
  • 
  • 
  • Sharing settings = Org wide default (OWD)
  • Question:
    • https://trailhead.salesforce.com/data_security/data_security_records
    • “When object- versus record-level permissions conflict, the most restrictive settings win.”
    • If object-level is more restrictive than record-level, who win?
    • Conflict with “If the organization-wide defaults are anything less than Public Read/Write, you can open access back up to certain roles using the role hierarchy.”
  • 
  • 
  • Organization-wide defaults can never grant users more access than they have through their object permission
    • Private - Only the record owner, and users above that role in the hierarchy, can view, edit, and report on those records.
    • Public Read Only - All users can view and report on records but not edit them. Only the owner, and users above that role in the hierarchy, can edit those records.
    • Public Read/Write - All users can view, edit, and report on all records.
    • Controlled by Parent - A user can perform an action (such as view, edit, or delete) on a contact based on whether he or she can perform that same action on the record associated with it.
• Role Hierarchy
  • 
  • 

  Sharing Rules

  • Share an object to other roles, if the Org wide default of the object is less then Public Read/Write (or is set to Private).
  • 

UX: TALK TO REAL PEOPLE

Lesson 2 Chapter 4

Big Idea #3: Talk to Real People

1. Talk to users (not clients, not co-workers). Car Rental case study: 12 interviews, 2 hours each.
• Clients do not necessarily know what users want.
2. Coding is expensive. Re-coding is even worse.
3. Ask open ended questions: “How would you like to find your dinner?” vs “Do you like Taco Bell?”
4. Listen to the clues:
• Don’t ask: Do you like vertical or horizontal navigation bar?
• User: My son is diabetic and I have to plan to his meal.
• User: It’s really hard to use my phone and juggle the kids.
5. Ask the user to do something, then sit back and observe. If the user get stuck, what would the user do next?
6. Validating our assumptions about who the user is and what the user want is the reason we do user research.

UX: LIKE ‘EM

Lesson 2 Chapter 3

Big Idea #2: Like'Em

1. Help users to be awesome.
2. Focus on users goes down in the mid to end phase of project due to stress and deadline, but it's so important to focus to users that period.

Ref:

http://gymnasium.aquent.com/course/103/305

UX: How to take 'You' out of the user

Lesson 2 Chapter 2 (9/24/2015)

Big Idea #1: Finding your users and their goals

1. Client goals
• Make money
2. User goals
• Make life easier
• Save money
• Be awesome
3. What to prioritize in your project: The user is _____ who wants to _____

Ref:

Learning to Design for Your Users

Manually deploy SharePoint Integration via SharePoint 2010 UI

 

Deploy Solution

1. Go to SharePoint 2010 Central Administration > System Settings > Farm Management > Manage farm solutions

2. Click on the wsp files, then click on Deploy Solution.

3. Select the Web Application to deploy the solution to, then click OK.

4. Repeat above steps for other solution files.

Activate Feature

1. Goto the SharePoint Site > Site Actions > Site Settings > Site Collection Administration > Site collection features.

2. Click the Activate button for the features below:

a. AgilePoint Configuration List

b. AgilePoint Process Launcher

c. AgilePoint Web Parts

d. AgilePoint ListForm

Creating Extractable Exe

Here is an approaches to create self-extractable exe:

1. Create a .zip:
• 7zip. Examples are here.
• WinZip (A valid license is needed to use the command line version)
• Windows Server 2003 Resource Kit Tools
2. Create the self-extractable exe:
• Zip 2 Secure Exe

Converting Virtual PC to VMWare

 

• Uninstall virtual machine addition.
• Convert vhd to vmware
• Repair OS win 2003 (using Windows SP1 CD)
• Repair .NET 3.5 SP1 (Error Entry point not found for mscoree.dll)
• Error when building VS.NET (DBPro): culture ID 2155 is not a supported culture.
  • Apply Windows 2003 SP2. Problem solved.