In the previous session we understood about the content and how we can create content packs right.
So basically what is the content in libraries.
We create the ad multiple content right.
We can create multiple libraries for multiple functions and then then more libraries we can add multiple
content.
Right.
So everything that we create within the library it is called as a content and one library can have many
content right.
Say for example this a sales library inside sales library like we can have many content out here like
the best duck one the last.
There is a picture to everything as a separate content and grouping together of content is called its
content back and then creating a content bang basically like weekend group content from different libraries
and we can place the content back in a particular liability.
So that is a concept for content then cut that back and add how do we access all this content go to
this content Bab and there you can access all the content
there you can access all the content from all the libraries because I say all libraries.
So it is giving me all the content from all the libraries.
And if you want to select a particular library again and go and select it say for example I'm selecting
this particular content so this is the content out here and this is in essence a library and the author's
name and if there are any tags out here and that is evolution.
So the content is just not about content.
It is about what all the features that are associated with that to enhance our experience in storing
documents.
Right.
So that is all a sense we'll see item content different from the other options out there.
The efficiency in storing the documents and how fast we can retrieve that when we need that.
So when we save a content it is just not about saving a file.
It is about the other options that are available to us in saving a file.
Say for example in real time.
Consider a user training document that we create.
So as a technical team we deliver documents to the team to the business right.
We create user training documents so that they can refer to those user training documents whenever they
need them.
So when we create use training documents like a.
Finalize the very first document.
Absolutely not.
That is in almost nearly impossible I would say so the documents that we create we update the documents.
Right.
Because it goes for multiple reviews within the technical team.
He goes for reviews with the business.
So after multiple reviews then we finally finalize the document.
But before that it goes for multiple evolutions.
So in that those scenarios we may need to store multiple versions of our document that is one scenario
in one of those scenarios maybe we may create a document for the business for some particular functionality
and I've all that does Salesforce upgrade thrice in a year.
So Salesforce may also like change the functionality to be even better functionality.
So in that scenario something may need to update some documentations that we did earlier.
So in that scenario also we may need to create new evolutions so that are again number of scenarios
where we may need to create warrens of documents.
So whenever we need to save these billions of documents it seems we'll see Adam content we can do that.
So say for example this is a best document to one and by default whenever we upload a document the upload
of content he does stored as Bush in one you can't see that it is a wash and what and here you can see
like if there are any comments added to it.
If you want to add a comment you can just say that this is version one
even the review was can add comments on documents and you can see that this is wash and one off this
document.
So now if I want to upload a wash in two off the document click upload and you wash in I to.
I love you to create a new version choose the fi
Jules blush in to
it just getting uploaded
and it says your content has been revised.
So basically we have not added a new content.
We have created a vision to offer existing content so if you go to wash ins it will show you to wash
INS basically.
So at any point of time we can always refer to the old ones as well.
We have this download option preview option so if you want to download you can download the previous
versions.
So there is basically no hassle in maintaining multiple versions of the same documents.
So there is no confusion within the team or within the business.
Everybody knows what they need to go and refer to.
So this is under the feature of content.
Apart from storing the content creating libraries for separate functionalities you know we can also
have login controlling basically visioning weekend doing content and again downloads Zia you can download
the content subscribe again subscribe to this content here is that content backs.
So you say that if this particular content is as a part of a content back.
Yes.
This is a part of the content back.
That is a new content package would give that as well.
And if you want to subscribe if you don't subscribe to that and when you when you click on subsequent
to to show that information okay.
So this is taking a while it might if you chill you in a bit.
So.
So these are the features of content.
Basically how you can create them how you can put it in a content backhaul you can subscribe to that
how you can create multiple versions of that how you can download that and all these now that we are
talking about this content versioning.
I would also like to show you how to query this and develop a console.
So open developer console
and Aguirre from the content wash and table.
So you see actually this table has got many columns I've just chosen the ones that we need the content
document idea description the record type and if that earnings tax and this custom field that we created
and the title and the washing number so execute this.
So this will show you basically all the details from the table basically all the content will be stored
here.
You know you can check that our cards off all the contents out here.
And if you want to get ready for a particular content yes you can query by the document tidy or by the
description or by the name.
So here we are giving as the test document to one.
If you see the content name is just document one and it does a two versions.
So let me again query
this is the I.T..
So let me say there I.T. equals this I.T. execute.
So it's the content document idea right.
So content document I.T. equals execute perfect.
So as you can see it does the same content but just that we have different versions of the same content.
I just wanted to show you this so that you know you can also get an understanding of how it does in
the backend so that you can use this information if you are loading information through data loaded
it into this content tuition table.
So making it you can make a note of this.
This is actually the equity.
There are many columns in this among that app chosen only those that are required to us.
And the table name is content version if you can't see that right here.
The table name is content volition and we have a specifically quoted for a particular content and we
are able to see two results.
Why two reasons.
Because there are two versions of the same content.
So basically does the same content but just that we have two different versions of the same content.
And this is all we are getting the guns of August content evolution information from the developer console.
And another important concept that we are going to learn about in content is how to deliver this content
to other users maybe to the technical team or B to the business.
How do we deliver this content.
And that we'll discuss in the upcoming video.