Web Systems Release Notes: 2017.49

Development environment preview YM site appeared with no style or formatting.

Some images were not appearing on the YM preview site.

Fixed the issue when the Takeaway was above the slideshow and pushed it down as expected but didn't push the slideshow arrows down.

Accordion section floated alongside an inline image in stories and concept articles instead of pushing below the image.

Ordered lists overlapped an inline image when floating alongside the image.

Added "- Present" for still active Professional Services in YM doctor profiles.

For organizations with dual parents, show both parent organizations in the "Related Organizations" sidebar box on department pages.

Two condition articles were inadvertently deleted, they have been restored in the system. It was not a bug.

Added a "Download to Excel" option for Concepts Management at http://prod.admin.profile.yale.edu/
YaleMedicine/Concepts/Index.

Added additional tables in a database to store previously used page names for articles, departments and users.

Prepared publish profiles for T3 Continuous Integration. This enables develpment work to be seen more quickly on our dev website.

Development and Acceptance T3 search indexes were moved into the search account which is used by other Development and Acceptance applications.

New users entered in OnCore were not syncing into profile system, so they did not appear in trials.

Added robots.txt for all environments in Web Services.

Improves the user experience when login sessions to the Profile System expire due to inactivity.

This will enable us to better manage and improve the maintenance page we display when the Profile System is down for maintenance.

Inform the user when an automatic logout from the Profile System has occurred.

Profile System users will now be warned when their session is about to expire due to inactivity, and given a chance to renew it.

Calendar date picker popup appeared larger than normal and empty.

Added interface to move calendars from one organization to another.

Eliminate using of <i> tag for icons

This task setup a second USA location based search index to improve application availability and stability. Additional steps are necessary but the search indexes are foundational.

Replaced an existing search index with a new one using the new naming convention. This is also a step in making our search indexes globally redundant.

This work completes the globalization for the search indexes.

This task takes the code developed for a concept and makes it ready for production release.

Updated YM configuration system for globalizing search indexes.

T3 dev/acceptance app services were moved to newly created app services.

Some servers are not required to run 24/7, this task setup applications to automatically start and stop servers based on a schedule. Since we only pay for servers that are running, this will help reduce our costs to run servers that are only used during development hours.

Reconfigured Azure Application Service Plans to make their use more efficient and cost effective. This is part one of this change, a separate ticket will be submitted for part two work to be completed within the next two months.

A temporary storage container was created in our development region that has become an integral part of our production SDL servers. This task moved it into the correct location in Azure so it is treated as a production entity.

Alchemy is a framework that allows us to easily add plugins to SDL. A configuration change caused the plugin to stop working which was fixed by uninstalling Alchemy and then re-installing it.

When a server is restarted, the SDL services that run workflow and publishing may not start in the correct order causing them to appear as if they are running but they are not available. This task created an application that will correct this automatically when a server is restarted.

This task made it possible to create even more complex rules.

This task moved a database into a shared resource group to help consolidate production databases for cost savings measures.

Integrate Azure CosmosDB as data storage in Signage project

Investigate Azure CosmosDB, determine benefits and drawbacks of using it in Signage project

Develop object models for storing config data in Signage project

Configure tool for checking code's formatting errors for the Signage project

Configure tool for generating client-side result bundles in the Signage project

Create basic structure of the client-side for the Signage project

Pass the main index.html file to the client-side for the Signage project

Pass screen's configs to the client-side in the Signage project

Add logic for getting screen's XML config in the Signage project

Configure library for mapping objects in the Signage project

Configure library for dependency injection in the Signage project

Create basic structure of the server-side for the Signage project