udhay
I'm new here

isInReleaseStore

Jump to solution

Dear FS Team,

There is a method named isInReleaseStore() in the IDProvider FirstSpirit API.

FS Documentation states as:

Checks if this storeelement exists in the release representation of the belonging store. This method could only be called for storeelements which support release and which are in the current representation of the belonging store

The question is:

1. When will an entry be made inside the release store (for a page/pageref/media)?

2. Will release store hold multiple entries for same element (kind of versioning), if the element is released multiple times?

3. Will the entries inside release store get removed by any operation, or at any point of time?

Please clarify.

Thanks and regards,

Udhay

0 Kudos
1 Solution

Accepted Solutions
bIT_sosswald
Returning Responder

Hi Udhay,

as you possibly know FirstSpirit supports the release of entities such like content und structure pages, media, data source entities and so on. This is done to be able to modify e.g. a page without having it deployed in an unfinished state during the time you work on the page.

The “release store” is the representation of the store with all released entities in it in the state of the last release.

So let’s oifmake an example:

  1. You have created a page and release it on the 28.09.2016 at 16:33.
  2. Then you work on the same page again the day after on the 29.09.2016 but you DON’T release it.

Now if you get the page from the release store you will get this page in exactly the state it was at the moment of its last release, so for this example the state from the 28.09.2016 at 16:33.
The work which was done after the last release will not be returned from the release store.

For your questions this means:

  1. The entry will be in the release store after its first release. And it will always have the state from its last release.
  2. No. The release store will only return the entry in the state of its last release. Versioning in FirstSpirit is done with the help of the History. (See the API documentation for HistoryProvider)
  3. Yes. If you delete an entry, e.g. a page, and then release the parent folder of this entry the entry will no more be generated and therefor it is no longer in the release store.

Greetings

Sandro

View solution in original post

0 Kudos
2 Replies
bIT_sosswald
Returning Responder

Hi Udhay,

as you possibly know FirstSpirit supports the release of entities such like content und structure pages, media, data source entities and so on. This is done to be able to modify e.g. a page without having it deployed in an unfinished state during the time you work on the page.

The “release store” is the representation of the store with all released entities in it in the state of the last release.

So let’s oifmake an example:

  1. You have created a page and release it on the 28.09.2016 at 16:33.
  2. Then you work on the same page again the day after on the 29.09.2016 but you DON’T release it.

Now if you get the page from the release store you will get this page in exactly the state it was at the moment of its last release, so for this example the state from the 28.09.2016 at 16:33.
The work which was done after the last release will not be returned from the release store.

For your questions this means:

  1. The entry will be in the release store after its first release. And it will always have the state from its last release.
  2. No. The release store will only return the entry in the state of its last release. Versioning in FirstSpirit is done with the help of the History. (See the API documentation for HistoryProvider)
  3. Yes. If you delete an entry, e.g. a page, and then release the parent folder of this entry the entry will no more be generated and therefor it is no longer in the release store.

Greetings

Sandro

0 Kudos

Hi Sandro,

Your points have given a clear idea about the release store functionality. Thank you for the clarification.

Regards,

Udhay

0 Kudos