PBCS and Fun New Features

KScope Wrap!

G’day All,

So Kscope16 is over, done and dusted, and I’m back home. A quick thankyou to everyone who I met – was amazing to be able to put a face and a voice to the names/blogs/twitter accounts I’ve followed over the years!

For everyone else – you’ll be glad to know the likes of Jason Jones, Cameron Lackpour, Tim German and Celvin Kattookaran (and others I’ve naught mentioned for brevity, but you know who you are) are as tragically nerdy amazingly bright, excited and enthused about this space as their blogs suggest. I was very endeared by their absolute state of gregarious comradeship – a spirit of learning and challenging yourself to become better – lead to both a humbling and inspiring couple of days.

A really quick story before I get started on the actual post. I was standing in the main foyer with a few people watching the boats go by when Celvin (a Chi-City native) commented that: ‘It’s amazing you know – tour guides on the boats volunteer all their time! They don’t get paid at all, they just do it because they love the city of Chicago’. Silence reigned for a few moments – until the irony of Celvin (of all people) commenting in shocked admiration that ‘people that volunteer their time, just for the love of it’ sunk in!

Moving on…

So this will be the first in a series – perhaps not as compleat as others – looking at some of the new features in PBCS that will hopefully wend their way back to On-Premises at some point!

This is a 16.07 PBCS Test environment – released early July.

First thing I’ll be looking at is the automated Smartlist generation.

Step 1 – Nice and Easy

Nice and simple, we create a few new members. You’ll see here I’ve created a list of members under a parent Super Rates.

Create_New_Members

The keen eyed amongst you might notice one of the other changes – duplicate aliases are now in place and supported completely. Aliases can have the same name as the member (and other members!) as long as the member names are unique.  To quickly reference the release notes:

“When referencing an alias that resolves to multiple members in free-form mode, an error is returned noting that the alias cannot be resolved to a single member. You can do this either by using the Member Selector to select the correct alias name or by hand-typing the qualified name. Using the parent member name as a qualifier should be sufficient in most cases, given that only duplicate alias names are supported, not duplicate member names.”

Step 2 – Nothing Doing

Next up, create a smartlist, same as normal.

Create_Smartlist

At the bottom you’ll see the “Create From Members” Checkbox with a member selection. I’m obviously picking the descendants of Super rates rather than hard coding the list (which becomes very cool shortly.

Step 3 – Too Easy

After saving the smartlist, returning to the entries page shows the members!

Review_Smartlist_Delete

You can see that the Name is set to the Member Name, while Label has been updated to the Alias. In an earlier test I used the Aliases as the member names (because smartlist names have some limitations) – the spaces were removed as well as the special characters (%) and replaced by underscores, but the label was still correct.

Step 4 – Mixing in the Awesome

You’ll now be wondering what happens if you create a new member – well let’s have a looksee.

Adding_New_Members

Created a new fake member under Super_Rates, and upon refreshing the database…

Step 5 – Bada Bing Bada Boom

Review_Smartlist_Add

Awesome.

But there’s no point if it hangs around, so let’s see what happens if we delete the member and refresh it

Step 6 – I’ve Overdone the Pringles Thing…

Huzzah!

Manage_Smartlist

Wrapping Up

So that’s awesome and should help massively in defining smartlists going forward! Stay tuned for some more new features (as I get a chance to find them and test them!)

Cheers

Pete

 

2 Comments

  1. Pete, 1 thing about the duplicate aliases is, you cannot duplicate them under same parent, I’m assuming it uses Fully qualified name behind and gets confused when siblings also has same name.

    1. Yeah – I agree.

      it’s interesting though – the phrasing of the release notes almost implies that there is another method of defining the fully qualified name that ISN’T Parent.Child?

      “Using the parent member name as a qualifier should be sufficient in most cases, given that only duplicate alias names are supported, not duplicate member names”

      Actually – rereading it now – it could just mean that parent.child is sufficient in most cases, and if you’re one of the edge cases, tough bikkies!

Leave a Reply