Hi all:

Today I tried to use the PAW 2.1.1 (LOCAL) Lifecycle Manager to snapshot then deploy a PAW Application (created under "Applications and Plans"). Here are some observations, plus some questions.

Creating the snapshot was easy, though it was interesting to see that the Application was stored in a folder-like container in the same Shared "Reports and Analysis" area along with other PAW Books, though you can't see it from Reports and Analysis.  And ultimately I was able to Deploy the snapshot - but it took several tries. DETAILS BELOW.

Several counter-intuitive things happened on the Deploy step:

1) I was not able to Deploy (restore) my snapshot to the same PAW server until after I had deleted the original application, despite the fact that the Deploy step prompts for a Folder Name that it insists must be different from an existing application.

2) Even after I had deleted the original application, the Deploy Folder Name step would not allow me to input the name of the folder where the deleted application (used to?) live. I had to provide a new folder name. BUT when the Deploy completed successfully, the application name (in Applications and Plans) was the original application name, so clearly the folder name is not the same as the application, but it would be nice to be able to provide a different name for the application, or an option to overwrite the old one. 

3) Before I realized that I could not Deploy to REPLACE an existing application, the error message asked me to RENAME the old application before deploying. But there is no way I can see to do that.

4) When I edit the Assets tab of the restored PAW Application section, it appears that the asset paths have changed. Previously they pointed at PAW Books within a specific Shared folder (which is what I want) but now they do not display a path, so I have no idea where they are pointing without testing. The deploy created a copy folder of all the books (even though I did not explicitly include the books in my snapshot) so I am concerned that I am not pointing at the copies (I will investigate). 

Ultimately the Deploy appears successful, and I was able to delete my PAW Application and get it back by deploying it from a snapshot. But the inability to RENAME or OVERWRITE makes it confusing, and the possibility that the restored application may now be pointing at a different copy of the books kind of defeats the purpose. I need to be able to do monthly migrations of application changes, and right now it looks like I will have a mess to clean up each time.

Am I missing something?

Thanks,

A.G.

Hi AG,

Plans and Applications are all stored in the root of the 'Shared' directory in the PAW content store.  These assets types are filtered out when looking at the content in 'Reports and Analysis' and 'Data and Models'.  This means that users will need write (Edit) access to the root of the Shared directory to create new Plans and Applications.  The roadmap for PAW includes support for Plans and Applications in folders.  We also need to make some changes so that all roles can see, but not open, all asset types (e.g an Analyst should see modeling workbenches).  Once this work is complete we will be able to present a single content system to all users.  

We added the ability to replace or rename assets when copying assets into a folder with the same name asset(s) this year.  We are planning on leveraging this new functionality directly in the Lifecycle Manager feature so you can deploy assets directly to a folder and choose to replace existing assets or rename the assets being deployed into the folder.  

Hi all:

Today I tried to use the PAW 2.1.1 (LOCAL) Lifecycle Manager to snapshot then deploy a PAW Application (created under "Applications and Plans"). Here are some observations, plus some questions.

Creating the snapshot was easy, though it was interesting to see that the Application was stored in a folder-like container in the same Shared "Reports and Analysis" area along with other PAW Books, though you can't see it from Reports and Analysis.  And ultimately I was able to Deploy the snapshot - but it took several tries. DETAILS BELOW.

Several counter-intuitive things happened on the Deploy step:

1) I was not able to Deploy (restore) my snapshot to the same PAW server until after I had deleted the original application, despite the fact that the Deploy step prompts for a Folder Name that it insists must be different from an existing application.

2) Even after I had deleted the original application, the Deploy Folder Name step would not allow me to input the name of the folder where the deleted application (used to?) live. I had to provide a new folder name. BUT when the Deploy completed successfully, the application name (in Applications and Plans) was the original application name, so clearly the folder name is not the same as the application, but it would be nice to be able to provide a different name for the application, or an option to overwrite the old one. 

3) Before I realized that I could not Deploy to REPLACE an existing application, the error message asked me to RENAME the old application before deploying. But there is no way I can see to do that.

4) When I edit the Assets tab of the restored PAW Application section, it appears that the asset paths have changed. Previously they pointed at PAW Books within a specific Shared folder (which is what I want) but now they do not display a path, so I have no idea where they are pointing without testing. The deploy created a copy folder of all the books (even though I did not explicitly include the books in my snapshot) so I am concerned that I am not pointing at the copies (I will investigate). 

Ultimately the Deploy appears successful, and I was able to delete my PAW Application and get it back by deploying it from a snapshot. But the inability to RENAME or OVERWRITE makes it confusing, and the possibility that the restored application may now be pointing at a different copy of the books kind of defeats the purpose. I need to be able to do monthly migrations of application changes, and right now it looks like I will have a mess to clean up each time.

Am I missing something?

Thanks,

A.G.

Thanks Stuart!

This is helpful, and I like the roadmap.

One question - when you say that you "added the ability to replace or rename assets" this year, does this apply to PAW 2.1.1 LOCAL? Because I can't for the life of me see it anywhere in the PAW Applications and Plans or Lifecycle Manager UI, and I think we have a pretty recent version (see screenshot). Unfortunately I have zero access to the PAW server box at this location, and no way to see the PAW content store on disk.

I would love it if it is because I am blind! ;-)

Thanks!

AG

Hi AG,

Plans and Applications are all stored in the root of the 'Shared' directory in the PAW content store.  These assets types are filtered out when looking at the content in 'Reports and Analysis' and 'Data and Models'.  This means that users will need write (Edit) access to the root of the Shared directory to create new Plans and Applications.  The roadmap for PAW includes support for Plans and Applications in folders.  We also need to make some changes so that all roles can see, but not open, all asset types (e.g an Analyst should see modeling workbenches).  Once this work is complete we will be able to present a single content system to all users.  

We added the ability to replace or rename assets when copying assets into a folder with the same name asset(s) this year.  We are planning on leveraging this new functionality directly in the Lifecycle Manager feature so you can deploy assets directly to a folder and choose to replace existing assets or rename the assets being deployed into the folder.  

Hi all:

Today I tried to use the PAW 2.1.1 (LOCAL) Lifecycle Manager to snapshot then deploy a PAW Application (created under "Applications and Plans"). Here are some observations, plus some questions.

Creating the snapshot was easy, though it was interesting to see that the Application was stored in a folder-like container in the same Shared "Reports and Analysis" area along with other PAW Books, though you can't see it from Reports and Analysis.  And ultimately I was able to Deploy the snapshot - but it took several tries. DETAILS BELOW.

Several counter-intuitive things happened on the Deploy step:

1) I was not able to Deploy (restore) my snapshot to the same PAW server until after I had deleted the original application, despite the fact that the Deploy step prompts for a Folder Name that it insists must be different from an existing application.

2) Even after I had deleted the original application, the Deploy Folder Name step would not allow me to input the name of the folder where the deleted application (used to?) live. I had to provide a new folder name. BUT when the Deploy completed successfully, the application name (in Applications and Plans) was the original application name, so clearly the folder name is not the same as the application, but it would be nice to be able to provide a different name for the application, or an option to overwrite the old one. 

3) Before I realized that I could not Deploy to REPLACE an existing application, the error message asked me to RENAME the old application before deploying. But there is no way I can see to do that.

4) When I edit the Assets tab of the restored PAW Application section, it appears that the asset paths have changed. Previously they pointed at PAW Books within a specific Shared folder (which is what I want) but now they do not display a path, so I have no idea where they are pointing without testing. The deploy created a copy folder of all the books (even though I did not explicitly include the books in my snapshot) so I am concerned that I am not pointing at the copies (I will investigate). 

Ultimately the Deploy appears successful, and I was able to delete my PAW Application and get it back by deploying it from a snapshot. But the inability to RENAME or OVERWRITE makes it confusing, and the possibility that the restored application may now be pointing at a different copy of the books kind of defeats the purpose. I need to be able to do monthly migrations of application changes, and right now it looks like I will have a mess to clean up each time.

Am I missing something?

Thanks,

A.G.

Hi AG,

"We added the ability to replace or rename assets when copying assets into a folder with the same name asset(s) this year."  I should have clarified that this only applies to Folders, Books, Views, Workbenches (basically everything but Plans and Applications).  You will only see this ability in Reports and Analysis and Data and Models.  We still need to make changes in LCM to take advantage of this new capability.  The same capability won't show up in Plans and Applications until after we add support for folders in Plans and Applications.

Thanks Stuart!

This is helpful, and I like the roadmap.

One question - when you say that you "added the ability to replace or rename assets" this year, does this apply to PAW 2.1.1 LOCAL? Because I can't for the life of me see it anywhere in the PAW Applications and Plans or Lifecycle Manager UI, and I think we have a pretty recent version (see screenshot). Unfortunately I have zero access to the PAW server box at this location, and no way to see the PAW content store on disk.

I would love it if it is because I am blind! ;-)

Thanks!

AG

Hi AG,

Plans and Applications are all stored in the root of the 'Shared' directory in the PAW content store.  These assets types are filtered out when looking at the content in 'Reports and Analysis' and 'Data and Models'.  This means that users will need write (Edit) access to the root of the Shared directory to create new Plans and Applications.  The roadmap for PAW includes support for Plans and Applications in folders.  We also need to make some changes so that all roles can see, but not open, all asset types (e.g an Analyst should see modeling workbenches).  Once this work is complete we will be able to present a single content system to all users.  

We added the ability to replace or rename assets when copying assets into a folder with the same name asset(s) this year.  We are planning on leveraging this new functionality directly in the Lifecycle Manager feature so you can deploy assets directly to a folder and choose to replace existing assets or rename the assets being deployed into the folder.  

Hi all:

Today I tried to use the PAW 2.1.1 (LOCAL) Lifecycle Manager to snapshot then deploy a PAW Application (created under "Applications and Plans"). Here are some observations, plus some questions.

Creating the snapshot was easy, though it was interesting to see that the Application was stored in a folder-like container in the same Shared "Reports and Analysis" area along with other PAW Books, though you can't see it from Reports and Analysis.  And ultimately I was able to Deploy the snapshot - but it took several tries. DETAILS BELOW.

Several counter-intuitive things happened on the Deploy step:

1) I was not able to Deploy (restore) my snapshot to the same PAW server until after I had deleted the original application, despite the fact that the Deploy step prompts for a Folder Name that it insists must be different from an existing application.

2) Even after I had deleted the original application, the Deploy Folder Name step would not allow me to input the name of the folder where the deleted application (used to?) live. I had to provide a new folder name. BUT when the Deploy completed successfully, the application name (in Applications and Plans) was the original application name, so clearly the folder name is not the same as the application, but it would be nice to be able to provide a different name for the application, or an option to overwrite the old one. 

3) Before I realized that I could not Deploy to REPLACE an existing application, the error message asked me to RENAME the old application before deploying. But there is no way I can see to do that.

4) When I edit the Assets tab of the restored PAW Application section, it appears that the asset paths have changed. Previously they pointed at PAW Books within a specific Shared folder (which is what I want) but now they do not display a path, so I have no idea where they are pointing without testing. The deploy created a copy folder of all the books (even though I did not explicitly include the books in my snapshot) so I am concerned that I am not pointing at the copies (I will investigate). 

Ultimately the Deploy appears successful, and I was able to delete my PAW Application and get it back by deploying it from a snapshot. But the inability to RENAME or OVERWRITE makes it confusing, and the possibility that the restored application may now be pointing at a different copy of the books kind of defeats the purpose. I need to be able to do monthly migrations of application changes, and right now it looks like I will have a mess to clean up each time.

Am I missing something?

Thanks,

A.G.