We use the Portal Plug-In and after a library update the F Workbook currently does not get transferred to the local configurations. Thus, any new hardware that is now located in the F Workbook is not available for our users, making the library update feature useless for us.

Problems

- Foundation library changes are not propagating to end users.

- These force manual workarounds or prevents important updates from reaching the field.

- It breaks the expected behavior of centralized library management though the portal.

Expected Behavior:

When a library is published through the portal, the F Workbook should be automatically included (along with the other library components) so that template level changes are distributed to all local users.

Steps to reproduce:

1 - Make a change to the server F Workbook

2 - Use the portal to Update Library from Server

3 - Check the resulting update package on a local user machine

        - F Workbook changes not applied