Hello everyone, 

I'd like to know if any of you have found a simple and effective strategy for deploying PAW assets between different PAW environments (i.e: dev -> test -> prod). In particular, the biggest problem we have to manage is updating books that already exist in the target environment... especially when new Applications/Plan are used. 

I try to summarize the approach we use today:

• using PAW lifecycle management functionalities we migrate/export books in the target personal folder.

• folder structure is the same for all environments but it's updated separately in order to have max flexibility in managing permissions in each environment (we try as much as possible to manage permissions at folder level and not at book level).

• once assets are available in the target personal folder, we manually move 1 by 1 books to target shared folder (or subfolder).

• unfortunately if a book with the same name already exists in the target folder, we must first delete it and save the new book with the same name (update/replace function is not available).

• At this point we have an additional problem: any PAW Application/Plan link to these updated books will not work anymore unless we manually reset it.

This approach is really cumbersome especially in complex environments (too much manual steps). I'm curious to know if an of you have faced this problem and maybe found a better way to manage it.

Regards,

Luca