One of the coolest new features in the Advanced Service Designer in vCAC 6.1 is the “Resource mappings”. Resource mappings is the way to tell ASD how to map a resource from vCAC’s catalog, that was provisioned by a provider other than ASD, to an inventory item in vCO, so that you can execute custom ASD resource actions over this resource. Basically this we already had this in 6.0 but only for IaaS types Virtual Machine, vCD vApp and vCD VM, but it was only for these types without the ability to map other resource types. Now if you open the resource mappings view, you will se those 3 built-in there and you will be able to add others for any resource type and this is what we will do.
So you probably know that when you request a catalog item in vCAC that is based on an ASD blueprint, some global parameters about the requestor will be provided to the workflow at execution time. This is great, but in many cases one would like to create such a workflow presentation that would allow adding constraints or filtering predefined values based on the requester, before the actual request is made (before the workflow starts the execution). Well, guess what, you can do that now with the new release of vCAC 6.1 .
How would you be able to do that? The good thing is that it is re-using well known methods in both vCO and ASD, so there’s nothing new to learn, and no hidden parameters.
One of the most important things in AngularJS is the data binding. In fact I think it is so important it should be one of the first things you should get to know if you start to write Angular apps. It should be explained more and it shouldn’t be just “the magic that we won’t cover right now”.
The real magic behind Angular’s data binding is called dirty checking. Basically every time you write
in the background a new watch for the expression
is being created that on every $digest cycle will be evaluated and if the value of the model is changed, the DOM will be updated. Thanks to this dirty checking we are also able to use plain old JS object as our model. How data binding works is explained in detail in this great article – http://angular-tips.com/blog/2013/08/watch-how-the-apply-runs-a-digest/. I also recommend to read Misko’s answer to this StackOverflow question on why dirty checking is not a bad thing, unless of course it is used in a bad way. This is why we should understand how data binding works.