Skip to main content
zezez3

LifeTime Management Console

OutSystems

LifeTime Management Console

LifeTime Management Console Release Mar.2019


Released on Mar 18, 2019

New in LifeTime Management Console Release Mar.2019

  • You can now see application warnings (for example, indicating that an application is outdated) in the deployment edit screen when planning a deployment. (RLIT-1315)
  • The Deployment Status method in LifeTime Deployment APIs v1 and v2 will only return the deployment status 'finished' after the completion of the sync operation. (RLIT-2249)
  • Updated the embedded platform server to Platform Server 11 - Release Jan.2019 Cumulative Patch 2. (RLIT-2489)

Bug Fixing

  • Fixed an issue in LifeTime that automatically set the purpose of the environment incorrectly in cloud environments. (RLIT-2415)

LifeTime Management Console Release Feb.2019


Released on Feb 25, 2019

New in LifeTime Management Console Release Feb.2019

  • Improved LifeTime cleanup process to also remove unused data from completed stagings. (RLIT-2287)
  • Added change log information to the output structure "ApplicationVersion" for methods "GET /applications/{ApplicationKey}/versions/" and "GET /applications/{ApplicationKey}/versions/{VersionKey}/" in LifeTime Deployment API v2. Added also the optional input "ChangeLogFilter" to method "GET /applications/{ApplicationKey}/versions/" to filter the returned list of versions by change logs containing the required keyword. (RLIT-2395)
  • It is now possible to delete application versions (LifeTime tags) using the new method "DELETE /applications/{ApplicationKey}/versions/{VersionKey}/" of LifeTime Deployment API v2. This feature will allow to delete in the environments the old module versions previously tagged by LifeTime. It requires Platform Server 10.0.912.0 (OutSystems 10 environments) or Platform Server 11 - Release Sep.2018 Cumulative Patch 1 (OutSystems 11 environments). Inspired by Harlin Setiadarma's idea. (RLIT-2399)
  • A new API method is now available in LifeTime Deployment API v2 for downloading the .oap file of a specific application version, "GET /applications/{ApplicationKey}/versions/{VersionKey}/content/". This method can be used to backup the code of an application version before deleting it. It requires Platform Server 10.0.1005.0 (OutSystems 10 environments) or Platform Server 11 - Release Jan.2019 Cumulative Patch 1 (OutSystems 11 environments). (RLIT-2169)
  • Added new input "TargetEnvironmentKey" to the API method "GET /deployments/" of LifeTime Deployment API v1 and v2 that allows to filter the deployments list by target environment. Improved also the return codes to differ the case when the user does not have permissions to view the requested deployments from the case when there are no deployments that match the search. (RLIT-2368)
  • In LifeTime Deployment API v2, the attribute “ModuleVersionKeys” of structure "ApplicationVersionCreate" has been deprecated and is now optional. When creating a new application version using the method "POST /environments/{EnvironmentKey}/applications/{ApplicationKey}/versions/", passing a value in attribute “ModuleVersionKeys” will behave as previously, validating the module versions. (RLIT-2369)

Bug Fixing

  • Fixed an issue in API method "POST /environments/{EnvironmentKey}/applications/{ApplicationKey}/versions/" of LifeTime Deployment API v2 that was preventing the creation of mobile apps versions. (RLIT-2410)
  • Fixed an issue in LifeTime synchronization that could cause environment features to be unavailable. (RLIT-2381)
  • Fixed a security vulnerability. CVSS v3.0 score 7.1 (High) - Full details to be released in May 2019 (RLIT-2388)
  • Fixed a security vulnerability in Platform Server. CVSS v3.0 score 7.1 (High) (RLIT-2438)
  • Fixed an issue when choosing "Mark Hotfix as Solved" for mobile apps if the application hadn't been deployed to the next environment yet. (RPD-3871)

LifeTime Management Console Release Jan.2019


Released on Jan 15, 2019

New in LifeTime Release Jan.2019

  • When deploying a mobile application to the next staging environment, LifeTime now uses the Mobile Apps Build Service (MABS) version associated with the application tag being deployed. The mobile app version and the MABS version for the deployed application are now displayed during the staging, as well as in the Application Version History page. (RLIT-2380)

Bug Fixing

  • Increased visibility on how to access a deployment plan that propagates hotfixes backward. (RPD-2789)
  • Fixed issue in LifeTime synchronization process that blocks applications from being synced. (RLIT-2379)
  • Improved the environment registration wizard UI for lower screen sizes, avoiding the overlap of screen elements. (RLIT-2374)
  • The summary step of the environment registration wizard now shows the correct value for the "Environment Position in Infrastructure". (RLIT-2372)
  • Fixed an issue in the synchronization process of environment features to LifeTime which could cause LifeTime misbehavior. (RLIT-2365)
  • Fixed a "Module with key was not found" error during the environment synchronization. (RPD-3662)
  • Decreased the time that LifeTime takes to display the error message of deployments that failed to generate the mobile app package. (RPD-3064)
  • Updated the version of Charts application distributed with LifeTime. (RLIT-2357)
  • Fixed an error in LifeTime Deployment API v2 while deploying applications to containers. (RLIT-2338)
  • We fixed a bug in Lifetime Analytics that caused low performance and time-outs in scenarios where more than one environment has monitoring enabled. We did this by correcting an internal timer responsible for harvesting and grouping data used in Lifetime Analytics. (RPD-3600)

LifeTime Management Console Release Dec.2018


Released on Dec 20, 2018

New in LifeTime Release Dec.2018

  • Improved the environment registration wizard to better guide the user when registering their environments in LifeTime. (RLIT-2285)
  • Added support for defining Mobile Extensibility Configurations in LifeTime, per Application and Environment. (RLIT-1503)
  • Added support for redeploying outdated applications using the LifeTime Deployment API v2. (RLIT-1981)
  • Improved LifeTime UI by replacing the shadows between environments with borders. (RLIT-2239)
  • When listing the applications that a user can access, Lifetime now lists also the applications that the user has been granted with access for being member of a team. (RLIT-2200)
  • Added more information in ApplicationVersion structure in LifeTime Deployment API. (RLIT-2168)

Bug Fixing

  • Users filter in the Audit Logs page is not displaying duplicated users anymore. (RLIT-2335)
  • The environments information displayed in Roles tab of User Management section is now reflecting users permissions. (RLIT-2334)
  • Fixed an issue that was causing the incorrect registration of on-premises environments in a cloud infrastructure. (RLIT-2333)
  • The information on the available database storage for cloud environments is now showing correctly. (RPD-3432)
  • Fixed an error when applying the security settings for an application. (RPD-3651)
  • The change log screen of an application is now correctly showing the name of the user that performed the change. (RLIT-2327)
  • Fixed an issue in the environment synchronization process that was incorrectly removing modules from LifeTime cache. (RPD-3607)
  • Fixed the number of applications displayed in the staging summary when the deployment plan contains more than 50 applications. (RLIT-2320)
  • Fixed the action User_ChangeUsername of LifeTime Services API that was incorrectly re-encrypting the password of the user. (RPD-3531)
  • Fixed an issue that was causing the "Deploy Now" message to be incorrectly displayed when two-stages deployment was enabled. (RLIT-2346)
  • Fixed security issue in LifeTime that allow a user to change its own username. (RPD-3595)
  • LifeTime does not log expected errors anymore when synchronizing an environment. (RLIT-2211)
  • Fixed the error message in LifeTime Deployment API about unsuccessful request for the Create Version call. (RLIT-2195)
  • Fixed the LifeTime error screen related to the missing user session. (RLIT-2191)
  • Fixed an error in accessing the LifeTime audits when a username is not defined. (RLIT-2190)
  • Fixed an error that happened after choosing the Synchronise Now option from an Environment in LifeTime, in cases where the user didn't have the correct permissions. (RLIT-2189)
  • Fixed a bug related to checking the Nativizer status that caused LifeTime to crash. (RLIT-2188)
  • Fixed the bug in LifeTime Analytics that prevented actions with long names to appear in the Screen Details. (RPD-3427)
  • Fixed a wrong message in the LifeTime staging. The users now see the correct message “you have no permission to deploy” instead of the incorrect “you have no permissions to tag”. (RPD-3319)
  • Fixed the default browser behavior to ask to save the login credentials. Now the password fields in OutSystems applications such as Service Center or LifeTime have the "autocomplete" property set to "off" by default. (RPD-3464)
  • Fixed an issue that caused an unspecified error in LifeTime when registering an environment with a higher version than LifeTime. LifeTime now prevents adding environments to the infrastructure if the environment that is being added has higher version. (RPD-3347)
  • Fixed issue in LifeTime that prevented a user with 'Reuse & Monitor' role to validate a deployment plan. (RPD-3480)
  • Fixed issue in LifeTime Deployment API that caused inconsistent data in a deployment with Tag & Deploy optioons. (RLIT-2251)
  • Fixed inconclusive exception message when there was an error creating a user in LifeTime (RLIT-2257)
  • Fixed message when there was an invalid request while creating a deployment. (RLIT-2250)
  • Changing the password of the current logged in user now requires typing the current password. (RLIT-2237)
  • Fixed an issue that was causing LifeTime not to detect missing dependencies in upgrade scenarios. (RLIT-2224)
  • Fixed an issue that was preventing the restore of LifeTime communication with an environment after changing the environment properties. (RLIT-2216)
  • Fixed a navigation error in accessing the environment change log when the environment is not defined. (RLIT-2205)
  • Fixed the lifetime bootstrap process that was failing in white labeling environments. (RPD-3523)
  • Timer to delete data from old module versions will now finish properly (without an error). (RPD-3583)
  • Fixed URL used by LifeTime to redirect users to configurations pages of environments. (RPD-3302)
  • Improved the performance of application data synchronization after 1-Click Publish. (RLIT-2236)

LifeTime Management Console Release Sep.2018


New in Release Sep.2018

  • From this version, LifeTime needs to be installed in a dedicated environment.
  • LifeTime can manage environments with Platform Server release 10 or 11.
  • Improved the add application to a staging in LifeTime to select a default option by default. (RLIT-1993)
  • Added support for deployment to containers using LifeTime. (RLIT-1537)
  • The LifeTime Analytics has been updated so the device database information now includes recent devices, operating systems, and browsers. (RLIT-2152)
  • When an application is associated to a Deployment Zone configured to use containers as hosting technology, OutSystems platform will generate a bundle with all the assets needed to allow build and run your application in a container. (RSAT-385)
  • Added Role_GetEnvironmentPermissionsLevels method to RoleManagementService API from LifeTimeServices. Removed deprecated EnvironmentManagementService and ApplicationManagementService APIS, as well as UserManagementService\User_UpdateApplicationPermission method from LifeTimeServices. (RLIT-1561)
  • Improved LifeTime validations performance by adding a new weekly timer which deletes older cached module versions that are not longer required in the infrastructure (RLIT-1797)

Bug Fixing

  • Fixed the bug that caused the “Continue Deployment” button not to show in LifeTime. It occurred in some scenarios when multiple users were logged-in to the same Staging_Progress page. (RPD-3290)
  • Improved the description of PlatformTeams parameter of Team_List action, in TeamManagementService. (RLIT-2079)

Breaking Changes

  • LifeTime is now only supported when installed in a dedicated environment.
    • Rationale: LifeTime now has its own release cycle to allow for better and faster improvements in LifeTime. To achieve this, LifeTime must be run, installed and maintained in a separate environment from the development pipeline environments in customer infrastructures.
  • LifeTime Analytics now has a historical data retention policy. This means that, by default, LifeTime Analytics will start deleting data older than 365 days.
    • Rationale: To optimize the performance of LifeTime Analytics, OutSystems introduced a mechanism to limit the amount of data kept by Analytics in the database. This was achieved by including a clean-up process that deletes data older than N days.
    • Workaround: This policy can be removed by setting the LifeTime.Analytics.DataRetentionPeriod parameter to 0 in the OSSYS_PARAMETER table after the upgrade and before timers are switched on. Disabling data retention policy is not recommended and can cause performance degradation in Lifetime Analytics.
  • The Frontend Name used in Performance Monitor no longer follows the configuration defined in Service Center; it will always be the Machine Name in uppercase.
    • Rationale: This change was made to improve information consistency across other monitoring and log sources. It also became a required change with the introduction of containers support, since the platform no longer has control over what servers have which applications running and applications do not depend on the servers they are running on.
    • Workaround: This information is not used by any of the built-in analytics components. Any custom modules using analytics information that might be using the Frontend Name may need to be adapted.
  • The configuration parameter LifeTime.AddApplicationsExplicitly, along with the previous deployment planning implementation in LifeTime which used this parameter, were removed. From now on, LifeTime only supports the new deployment planning functionality.
    • Rationale: The new deployment planning functionality is mature and has been widely adopted. As such, the previous deployment planning implementation in LifeTime is no longer available and the configuration parameter LifeTime.AddApplicationsExplicitly is no longer needed.

 

  • Was this article helpful?