No Touch, Please. Hot!...If Only My Window Seat Had a Securable Record Operation Like the "Customize Tiles" Button in the Constituent Tile Summary
Published
Please take a moment to catch your breath after reading that title.
My son is approaching 2 years of age and is mobile, so naturally he wants to touch everything in his field of view. With any non-NERF™ home, there are perils awaiting the uninitiated, and the first of ours turned out to be a propane grill in the backyard. So when my son wandered toward the grill a few months ago with an outstretched arm, I sprang into action and eloquently said, "No Touch, please. Hot!" Much to my surprise, this tactic actually worked. I had figured this parenting thing out. The next chance I had to prove that my success wasn't a fluke happened when he approached a glass of orange juice sitting on our coffee table. I stuck to the script and said, "No touch, please." He looked at me inquisitively and said, "Hot?" Not wanting to forfeit my Parent of the Year award over a stained rug, I confidently said, "Yes. Hot." This type of exchange became commonplace for a while. The produce section of the grocery store? The neighbor's fancy metal sculpture of a large crab? A random piece of gum laying on the sidewalk? These were basically lava and commanded a wide berth. Then something happened that changed the rules. My son actually learned the difference between hot and cold. I know that I was naive to think that I could keep up with this charade forever, but I guess I was just hoping that he would eventually understand that a "No touch" request isn't always driven by the temperature of the item. Yesterday, I learned the hard way that I shouldn't have left this to chance. I had just finished putting a coat of paint on a window seat (that has taken me far too long to build) when my son put down his own magical (read: dry) paintbrush and made a dash for the wet paint. His little hand had barely made contact with the damp surface when I said, "No Touch!" Only this time the jig was up. He knew it wasn't hot, and the result was far from a masterpiece.
My goal is that my son use the window seat, but not destroy it. I want him to use it. I envision him jumping on it, storing his toys inside of it, and maybe even sitting upon it to read a book if he ever decides to stop moving for a minute. I do not want my son to give it a custom paint job.
If only I had a way to keep him from making changes to how it looks, but not lock him out of using it?
That’s the same question that some of our system administrators are asking themselves about the new Constituent Tile Summary Section. For them, the goal is to give users access to use Constituent Tiles, but restrict access to altering the display. While an objective of these tiles is to give end users flexibility in the UI, locking down the Customize tiles button can make sense if you want to tailor a specific role to a limited set of functions. It also keeps your training materials accurate if you rely on custom screenshots in internal user guides. For these sys admins, the scenario plays out like this:
The good news is that there is an easy way to remove the Customize tiles button for a system role by denying permission to the Constituent Summary Selected Tiles: Update record operation:
The result for users in that role? Dry paint and less cleanup:
-Matt
My son is approaching 2 years of age and is mobile, so naturally he wants to touch everything in his field of view. With any non-NERF™ home, there are perils awaiting the uninitiated, and the first of ours turned out to be a propane grill in the backyard. So when my son wandered toward the grill a few months ago with an outstretched arm, I sprang into action and eloquently said, "No Touch, please. Hot!" Much to my surprise, this tactic actually worked. I had figured this parenting thing out. The next chance I had to prove that my success wasn't a fluke happened when he approached a glass of orange juice sitting on our coffee table. I stuck to the script and said, "No touch, please." He looked at me inquisitively and said, "Hot?" Not wanting to forfeit my Parent of the Year award over a stained rug, I confidently said, "Yes. Hot." This type of exchange became commonplace for a while. The produce section of the grocery store? The neighbor's fancy metal sculpture of a large crab? A random piece of gum laying on the sidewalk? These were basically lava and commanded a wide berth. Then something happened that changed the rules. My son actually learned the difference between hot and cold. I know that I was naive to think that I could keep up with this charade forever, but I guess I was just hoping that he would eventually understand that a "No touch" request isn't always driven by the temperature of the item. Yesterday, I learned the hard way that I shouldn't have left this to chance. I had just finished putting a coat of paint on a window seat (that has taken me far too long to build) when my son put down his own magical (read: dry) paintbrush and made a dash for the wet paint. His little hand had barely made contact with the damp surface when I said, "No Touch!" Only this time the jig was up. He knew it wasn't hot, and the result was far from a masterpiece.
My goal is that my son use the window seat, but not destroy it. I want him to use it. I envision him jumping on it, storing his toys inside of it, and maybe even sitting upon it to read a book if he ever decides to stop moving for a minute. I do not want my son to give it a custom paint job.
If only I had a way to keep him from making changes to how it looks, but not lock him out of using it?
That’s the same question that some of our system administrators are asking themselves about the new Constituent Tile Summary Section. For them, the goal is to give users access to use Constituent Tiles, but restrict access to altering the display. While an objective of these tiles is to give end users flexibility in the UI, locking down the Customize tiles button can make sense if you want to tailor a specific role to a limited set of functions. It also keeps your training materials accurate if you rely on custom screenshots in internal user guides. For these sys admins, the scenario plays out like this:
The good news is that there is an easy way to remove the Customize tiles button for a system role by denying permission to the Constituent Summary Selected Tiles: Update record operation:
The result for users in that role? Dry paint and less cleanup:
-Matt
News
Blackbaud CRM™ and Blackbaud Internet Solutions™ Blog
05/08/2015 3:51pm EDT
Leave a Comment